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
View Poll Results: Was this forum helpful
YES 13 92.86%
NO 1 7.14%
Voters: 14. You may not vote on this poll

Post Reply

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

OP lj50036

22nd November 2013, 02:03 PM   |  #1  
lj50036's Avatar
OP Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,647
 
2,071 posts
Join Date:Joined: Feb 2013
Donate to Me
More
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 outpus of my process

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!!!!!!!!!!!
Last edited by lj50036; 4th September 2014 at 08:02 PM.
The Following 18 Users Say Thank You to lj50036 For This Useful Post: [ View ]
22nd November 2013, 02:03 PM   |  #2  
lj50036's Avatar
OP Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,647
 
2,071 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Smile Feedback
I am here to help just ask..... We will get you on the right path!!!!!
Last edited by lj50036; 27th November 2013 at 07:32 AM.
The Following User Says Thank You to lj50036 For This Useful Post: [ View ]
22nd November 2013, 02:04 PM   |  #3  
lj50036's Avatar
OP Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,647
 
2,071 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Mine
Last edited by lj50036; 3rd August 2014 at 05:46 AM.
The Following 3 Users Say Thank You to lj50036 For This Useful Post: [ View ]
23rd November 2013, 08:04 AM   |  #4  
Junior Member
Thanks Meter: 1
 
9 posts
Join Date:Joined: Oct 2013
Angry 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
27th November 2013, 11:06 PM   |  #5  
Junior Member
Thanks Meter: 5
 
7 posts
Join Date:Joined: Mar 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?
27th November 2013, 11:38 PM   |  #6  
Recognized Contributor
Thanks Meter: 2,503
 
3,530 posts
Join Date:Joined: Oct 2012
More
Quote:
Originally Posted by Chazzfazzle

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?


Quote:
Originally Posted by Chazzfazzle

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.
The Following 2 Users Say Thank You to _that For This Useful Post: [ View ]
28th November 2013, 12:30 AM   |  #7  
lj50036's Avatar
OP Recognized Contributor
Flag Muti-Verse
Thanks Meter: 1,647
 
2,071 posts
Join Date:Joined: Feb 2013
Donate to Me
More
Fastboot
Quote:
Originally Posted by Chazzfazzle

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
Last edited by lj50036; 28th November 2013 at 08:53 AM.
The Following 2 Users Say Thank You to lj50036 For This Useful Post: [ View ]
30th November 2013, 05:06 AM   |  #8  
Junior Member
Thanks Meter: 5
 
7 posts
Join Date:Joined: Mar 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.
The Following User Says Thank You to Chazzfazzle For This Useful Post: [ View ]
1st December 2013, 09:45 AM   |  #9  
Junior Member
Thanks Meter: 5
 
7 posts
Join Date:Joined: Mar 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?
1st December 2013, 10:22 AM   |  #10  
Recognized Contributor
Thanks Meter: 2,503
 
3,530 posts
Join Date:Joined: Oct 2012
More
Quote:
Originally Posted by Chazzfazzle

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".

The Following 2 Users Say Thank You to _that For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
nvflash, tf700t, unbrick
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes