Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[NvFlash] [Recovery] With [Generated Blobs][TF300T]

OP bucket81

30th December 2013, 04:37 AM   |  #1  
bucket81's Avatar
OP Member
Thanks Meter: 6
 
78 posts
Join Date:Joined: Jan 2011
First off I want to thank @lj50036 for his time and most of all his patients in helping me bring my TF300T back to life I can't thank him enough!! His original post on the TF700T is here. Make sure you go thank him!!

You must have the NVFlash generated files from AndroidRoot.Mobi for ICS or JB.

This is what I did and it might not work for your specific situation. I performed this on a Mint 15 32 bit machine. This is very important (EDIT: This has also been done on Mint 64bit); Ubuntu might not work and would not work for me .

My situation:
I had flashed the wrong recovery (TWRP 2.6.3.0). This left me with only being able to boot into a recovery that would not mount anything but it would boot into APX mode.

What you will end up needing:
blob.bin
unlock-token.img
factory-config.img
bricksafe.img

Also needed:

Fully charged TF300T (Just plug it in, it will charge no matter what...If not, you don’t need my help!!!!)
Asus data cable
Linux Mint 15 (32 bit) PC
Stock firmware blob (from asus's website. Make sure you get the right one) Download
nvflash and wheelie Download
And fastboot for your PC

You might also need TWRP 2.5.0.0 Download


Mint

1) Lets start with Mint 15 (32 bit) Download and how to make a bootable USB. instructions this has got to be one of the easiest OS’s I have installed and setting up dual boot is cake.

2) Once Mint is booted you want to update it, and it’s a little broken but it’s what I did and you will get some updates. Click where the start menu is in windows find the search field and lookup update manager. Run it and download what you can.

3) Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob (this is not a .blob file make sure you put that in the name) file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder..
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
nvflash
wheelie
boot.blob (we renamed it in the last step)


4) Next we need to install fastboot, this is straight up Linux voodoo, open terminal and get comfy cause that’s what you’re going to be using. next type
Code:
fastboot
it will prompt you with the command to install fastboot.

These inputs and outputs are from lj50036 post on the TF700T and may very from your outputs. I used the processes and it worked for me.

Lets get started

Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
I am going to show you the output of my process
Code:
sudo ./wheelie --blob blob.bin
lj50036@cmbroms:~ > sudo ./wheelie --blob blob.bin
OUTPUT
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbce2501405
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

It may shutdown after each command, get back into nvflash with the above steps.....
Code:
sudo ./nvflash -r --download 7 unlock-token.img
lj50036@cmbroms:~ > sudo ./nvflash -r --download 7 unlock-token.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
/ 8388608/8388608 bytes sent
unlock-token.img sent successfully

Code:
sudo ./nvflash -r --download 14 factory-config.img
j50036@cmbroms:~ > sudo ./nvflash -r --download 14 factory-config.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
/ 5242880/5242880 bytes sent
factory-config.img sent successfully

Code:
sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
lj50036@cmbroms:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully

Code:
sudo ./nvflash -r --go
lj50036@cmbroms:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]

This is where I ran into problems that didn’t work with the TF700T recovery process. I could not boot into Fastboot with the holding the power and the volume down no matter what I did. this is how we got around it.
download the correct .blob from TWRP rename it twrp.blob then run

Code:
sudo ./nvflash -r --download 5 twrp.blob
I don't have output for this.

At this point I could boot into the OS, but still not into fastboot. My OS had the option to reboot to download. If you don’t have this option you could try this or this. But the best way is via the buttons.

Run these command in fastboot in this order

The next command is to just verify your computer can see your device

Code:
sudo fastboot devices
INPUT
lj50036@cmbroms:~ > sudo fastboot devices
OUTPUT
015d2bbce2501405 fastboot

Code:
sudo fastboot erase system
INPUT
lj50036@cmbroms:~ > sudo fastboot erase system
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s

Code:
sudo fastboot erase recovery
INPUT
lj50036@cmbroms:~ > sudo fastboot erase recovery
OUTPUT
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s

Code:
sudo fastboot -w
INPUT
lj50036@cmbroms:~ > sudo fastboot -w
OUTPUT
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...

At this point it just hangs on erasing 'cache'
I just close terminal and open new one, and run the next command
If your tablet hangs just reboot back into fastboot again

Code:
 sudo fastboot erase boot
INPUT
lj50036@cmbroms:~ > sudo fastboot erase boot
OUTPUT
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s

Code:
sudo fastboot erase misc
INPUT
lj50036@cmbroms:~ > sudo fastboot erase misc
OUTPUT
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s

Code:
sudo fastboot erase cache
INPUT
lj50036@cmbroms:~ > sudo fastboot erase cache
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s

Code:
sudo fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....

INPUT
lj50036@cmbroms:~ > sudo fastboot -i 0x0B05 flash system boot.blob
OUTPUT
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s

Code:
 sudo fastboot -i 0x0B05 reboot
lj50036@cmbroms:~ > sudo fastboot -i 0x0B05 reboot
OUTPUT
rebooting...

finished. total time: 0.020s

You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
Boot fully into rom then you can do whatever you would like!!!!!!!!!!!

Make sure you go thank @lj50036
Last edited by bucket81; 29th January 2014 at 04:53 PM.
The Following 4 Users Say Thank You to bucket81 For This Useful Post: [ View ]
30th December 2013, 04:40 AM   |  #2  
bucket81's Avatar
OP Member
Thanks Meter: 6
 
78 posts
Join Date:Joined: Jan 2011
....
6th January 2014, 03:26 PM   |  #3  
lj50036's Avatar
Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,751
 
2,181 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Angry Great Work
Its nice to see that my work on the 700 will be able to, maybe help the 300 community out also.... Keep up the good work.... Thx as always lj
The Following User Says Thank You to lj50036 For This Useful Post: [ View ]
28th January 2014, 01:54 PM   |  #4  
Junior Member
Thanks Meter: 2
 
18 posts
Join Date:Joined: Nov 2007
Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?
28th January 2014, 02:08 PM   |  #5  
lj50036's Avatar
Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,751
 
2,181 posts
Join Date:Joined: Feb 2013
Donate to Me
More
OS
Quote:
Originally Posted by Erario

Thanks for your docs, only a question please, are necessarily forced to use "Linux Mint 15 (32 bit) PC" or can i use Windows as I did to generate the img and blob?
I don't understand this step, "nvflash" work fine to download this file, it doesn't work during the write from Windows command prompt?

I can confirm this working on mint 15 32 bit, mint 15 64 bit, and mint 16 64 bit.. I would stay away from windows if at all possible....Thx lj
The Following User Says Thank You to lj50036 For This Useful Post: [ View ]
28th January 2014, 02:36 PM   |  #6  
Junior Member
Thanks Meter: 2
 
18 posts
Join Date:Joined: Nov 2007
When for some reason will no longer start my "unbrickable TF300TG" (hehehe) I'll try with Windows and I will tell you.
8th February 2014, 06:24 AM   |  #7  
Senior Member
Thanks Meter: 307
 
343 posts
Join Date:Joined: Nov 2012
I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android
The Following User Says Thank You to ebildude123 For This Useful Post: [ View ]
8th February 2014, 06:33 AM   |  #8  
lj50036's Avatar
Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,751
 
2,181 posts
Join Date:Joined: Feb 2013
Donate to Me
More
feedback
Quote:
Originally Posted by ebildude123

I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:

Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android

Did you come from a brick or did you just use nvflash to flash a recovery??
8th February 2014, 06:38 AM   |  #9  
Senior Member
Thanks Meter: 307
 
343 posts
Join Date:Joined: Nov 2012
Quote:
Originally Posted by lj50036

Did you come from a brick or did you just use nvflash to flash a recovery??

A brick
28th February 2014, 03:05 AM   |  #10  
Junior Member
Thanks Meter: 5
 
19 posts
Join Date:Joined: Feb 2014
Quote:
Originally Posted by ebildude123

I would like to point out for nvflash -r --download 5 twrp.blob my output was the following:

Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Then the device proceeded to reboot into android

My device is TF201.
Here is my long story: (search for my post)
http://forum.xda-developers.com/show...php?p=50690267

In short, i cannot get fastboot but can get to APX (power + up)

Was thinking of trying your steps but I dun understand how to get twrp.blob.

Also, prior to my brick i flashed some cwm recovery. Does that matter?
I have all the output files from the flatline thingy.

Any ideas?

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes