[NvFlash] [Recovery] With [Generated Blobs][TF-700-T]

lj50036 · Nov 22, 2013

This is a general users guide to unbricking your tf700t...

This is only what I did, It was successfull for me.
I did this on linux mint 32 bit, so thats what I can help with. Im sure it can be done on windows but who would want to!!!!!!LOL
I will help anyone that needs it of course... No matter the os... Just let me know!!!!

What you need
Your device specific nvflash backup files generated while enabling nvflash.
!!!!!!!!If you dont have them there is no help for you!!!!!!

blob.bin
bootloader.ebt
unlock-token.img
factory-config.img
bricksafe.img

Also needed
A tf700t (Its bad now, but all will be ok)
Fully charged tf700t (Just plug it in, it will charge no matter what...If not you dont need my help!!!!)
Asus data cable
Linux Mint 32bit PC
Super user permission
Stock firmware blob (from asus's web site, make sure you get the right one)
nvflash and wheelie
And fastboot for your PC

Downloads

nvflash/wheelie-Linux
click me

nvflash/wheelie-Windows
click me

Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR 700
click me

INSTRUCTIONS
Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder...

In your home folder you should have

blob.bin
unlock-token.img
factory-config.img
bricksafe.img
bootloader.ebt
nvflash
wheelie
boot.blob (we renamed it in the last step)

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 outputs of my process ....
If you are running windows drop the 'sudo ./' and make sure your CMD window is opened as admin

Code:

sudo ./wheelie --blob blob.bin

lj50036@area51:~ > 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@area51:~ > 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

lj50036@area51:~ > 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@area51:~ > 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@area51:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]

At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot...You will now have fastboot.
We are not done yet!!! Getting close now!!!!!!

Run these command in fastboot in this order

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

Code:

 fastboot devices

INPUT
lj50036@area51:~ > fastboot devices
OUTPUT
015d2bbce2501405 fastboot

Code:

 fastboot erase system

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

Code:

 fastboot erase recovery

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

Code:

 fastboot -w

INPUT
lj50036@area51:~ > 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:

 fastboot erase boot

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

Code:

 fastboot erase misc

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

Code:

 fastboot erase cache

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

Code:

 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@area51:~ > 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:

 fastboot -i 0x0B05 reboot

lj50036@area51:~ > 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 than you can do whatever you would like!!!!!!!!!!!

lj50036 · Nov 22, 2013

Feedback

I am here to help just ask..... We will get you on the right path!!!!!

lj50036 · Nov 22, 2013

nickelfritz9 · Nov 23, 2013

thanks

will be bookmarking this page! i hope to never have to do this but will have step by step instruction if something would ever go terribly wrong. i hope this helps people out before they totaly give up on there device just remember the TF700T is 99.5% unbreakable

Chazzfazzle · Nov 27, 2013

First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash. Everything works like a charm up until the user data wipe. This is what I get:

c:\peri>fastboot -w
erasing 'userdata'...
OKAY [ 22.643s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
erasing 'cache'...
OKAY [ 1.277s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
finished. total time: 23.925s

After restoring nvflash the device shows up in fastboot but labeled as ?. The system recognizes it and interacts with it though. Everything else goes well until flashing the boot.blob (9.4.5.30). The file uploads like it is supposed to but when it goes to install I get the red text on the screen saying "signature mismatch" or "failed to process command flash: system error(0x170003)." Tried with all tf700 us updates with the same result. I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?

_that · Nov 27, 2013

Chazzfazzle said:
First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash.

?? A bad ROM flash is usually easily recoverable using the recovery, as it does not touch your bootloader. How did you manage to break fastboot and your recovery with a bad ROM flash?

Chazzfazzle said:
I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?

Try it under Linux - there were several reports about problems with nvflash under Windows.

lj50036 · Nov 27, 2013

Fastboot

Chazzfazzle said:
First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash. Everything works like a charm up until the user data wipe. This is what I get:

After restoring nvflash the device shows up in fastboot but labeled as ?. The system recognizes it and interacts with it though. Everything else goes well until flashing the boot.blob (9.4.5.30). The file uploads like it is supposed to but when it goes to install I get the red text on the screen saying "signature mismatch" or "failed to process command flash: system error(0x170003)." Tried with all tf700 us updates with the same result. I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?

Make sure that you open your CMD window as administrator... There is a hole about 2 cm below the sd card slot. I have heard some people needing to push this... Here is what they are doing seems some have to do this and some dont... Dont know if it will help any worth a shot...

Reset your device with a paperclip/needle (about 2 cm down from your sdcard slot) and hold vol-down to enter fastboot

If thats not it than... Im going to have to go with _that... Linux is what you need for your next step!!!!!! Let me know and as always thx lj

Chazzfazzle · Nov 30, 2013

Sorry for the delay. I am having to learn how to dual boot linux and windows and learning how the system works. I will say this is wicked fast compared to windows 7. If this is successful I may consider converting. But I digress. I will give it a shot and let you know how it worked out. I will also try the reset switch. And once again thanks for all the info. You guys are awesome.

Chazzfazzle · Dec 1, 2013

So I got Ubuntu up and running and I have the adb and fastboot drivers installed. I also dl'ed the linux wheelie and nvflash files. The computer can see my device when I run fastboot devices command but it won't run wheelie from the directory I created for it. Where do I put my files so the terminal can run them?

_that · Dec 1, 2013

Chazzfazzle said:
So I got Ubuntu up and running and I have the adb and fastboot drivers installed. I also dl'ed the linux wheelie and nvflash files. The computer can see my device when I run fastboot devices command but it won't run wheelie from the directory I created for it. Where do I put my files so the terminal can run them?

Linux does not run programs in your current directory by default, for security reasons. To run wheelie from your current directory, type "./wheelie".

Chazzfazzle · Dec 4, 2013

I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.

Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.

lj50036 · Dec 6, 2013

Great!!

Chazzfazzle said:
I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.

Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.

Hey thats great news, would you email me those links and I will integrate them into the process!!! Thx lj

samheg · Dec 7, 2013

Chazzfazzle said:
I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.

Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.

Hi Chazzfazzle,

I have exactly the same problem you've had.
I'm stuck at "Failed to process command flash:system error(0x170003)"

Could you please explain me what you did to fix it?
Thank you

---------- Post added at 04:29 PM ---------- Previous post was at 04:16 PM ----------

@lj50036

Like Chazzfazzle, at the "sudo ./fastboot -w" step, i got :

Code:

$ sudo ./fastboot -w
erasing 'userdata'...
OKAY [ 10.358s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type  not supported.
OKAY [  0.000s]
erasing 'cache'...
OKAY [  2.089s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type  not supported.
OKAY [  0.000s]
finished. total time: 12.448s

And a "sudo ./fastboot devices" gives me :

Code:

$ sudo ./fastboot devices
????????????	fastboot

Did I miss something?

lj50036 · Dec 7, 2013

Fastboot Install

How are you installing fastboot??

What Linux are you running??

samheg · Dec 7, 2013

I've downloaded the sdk from the Android website
dl.google.com/android/adt/adt-bundle-linux-x86_64-20131030.zip

I've tried with the fastboot package in the saucy universe repository too : android-tools-fastboot

samheg · Dec 9, 2013

samheg said:
I've downloaded the sdk from the Android website
dl.google.com/android/adt/adt-bundle-linux-x86_64-20131030.zip

I've tried with the fastboot package in the saucy universe repository too : android-tools-fastboot

I'm running Ubuntu gnome 13.10

samheg · Dec 10, 2013

An additional question :
I've generated the blobs and the bricksafe.img when the tablet was still on ICS.
After that, I've updated it to JB and so to a version 10.6.1.14.x of the bootloader.
Could it be the cause of my problems with nvflash/fastboot ?

Sent from my Nexus 4 using xda app-developers app

lj50036 · Dec 10, 2013

Feedback/Fastboot

samheg said:
An additional question :
I've generated the blobs and the bricksafe.img when the tablet was still on ICS.
After that, I've updated it to JB and so to a version 10.6.1.14.x of the bootloader.
Could it be the cause of my problems with nvflash/fastboot ?

Sent from my Nexus 4 using xda app-developers app

No, that should not affect fastboot... I am digging for more info about your issue, I have some solid leads, just need a little more time, have not forgot about you... as always thx lj

Chazzfazzle · Dec 16, 2013

My problem ended up being the nvflash distro from androidroot.mobi. I don't know if it is broken or just incompatible with my system. I ended up finding a working (worked for me anyway) version from nvidia directly. It's part of the Linux Developer Kit.

Get it here: https://developer.nvidia.com/linux-tegra

Make sure you only, and I can't stress this enough, make doubly sure you only get the Cardhu Driver Pack. NvFlash is located in the bootloader folder of the archive. I replaced androidroot.mobi's version with this and the rest is history. Hope this helps.

Also I did this on Ubuntu 12.04.3. I see you are on the latest release. I seriuosly doubt that makes any difference but, the more you know...

samheg · Dec 21, 2013

Unfortunately that didn't solve my problem.

I'm still stuck with fastboot not recognizing my tf700t.

Code:

$ sudo ./fastboot devices
????????????	fastboot

I'm open to any suggestion.

[NvFlash] [Recovery] With [Generated Blobs][TF-700-T]

Was this forum helpful

YES

NO

Senior Member

Senior Member

Senior Member

Member

Member

Recognized Developer / Inactive RC

Senior Member

Member

Member

Recognized Developer / Inactive RC

Member

Senior Member

Member

Senior Member

Member

Member

Member

Senior Member

Member

Member

Similar threads

Top Liked Posts