[TOOL]TF201 NVFLash [Updated 21. July]

Search This thread

djkinetic

Senior Member
Feb 26, 2011
3,641
1,387
Chicago
It doesn't matter. Lsusb should show an NVIDIA device in APX mode (Vid: 0x955) even without udev rules.
However, connect the device to USB before powering into APX. There are intermitten issues with usb not quite initializing correctly if you connect cable afterwards.

I tried that that lusb still doesnt show anything connected to USB...so I'm almost certain it needs to be RMAed, another user had a similar situation with the tab not recognizing, guy ended up having to send it into Asus the repair was around 270...if I can find one for 300 total I'll probably just grab a new one instead...either way its unrecognizeable in Linux, and in Windows I can't get any drivers installed for it...been at it 3 straight days now without any luck.
 

rayman

Senior Recognized Developer
May 1, 2008
278
1,399
Guess I am going to remain unrooted :(

Just to clarify (Do feel free to remain unlocked, but just making sure the facts are on the table).

This is a method to unbrick, yes, BUT, you will only be able to unbrick if you've done this procedure *prior* to bricking.

You basically get a failsafe from the device through this procedure - but you loose warranty (though, jury is still out on whether or not they refuse warranty on hardware)

When it comes to software, once you've done this procedure and have those files, there's NOTHING that can brick you software-wise.
 
  • Like
Reactions: morgan39

joe ferreira

Senior Member
May 21, 2007
582
296
Mountlake Terrace, WA
nvflash binary package for tegra 3 ICS for win32-x86/x64

attached is a working tested nvflash binary package for tegra 3 ICS win32.
included is also fastboot and adb executables.

extract this zip and all wheelie win32 executables in the same directory and follow the directions on http://androidroot.mobi/?p=452 as rayman has stated.

a couple things to note:
MAKE BACKUPS OF YOUR BLOBS

entering apx mode was not very clear.
hold power + vol up until you feel the tablet vibrate
release power and volume up and immediately press volume up for about 3 seconds
then release volume up.

the screen will remain blank but will be in nvidia apx mode.
you will then need to install the apx driver from the universal driver package here on xda.


edit: fyi I have nothing to do with androidroot.mobi team.
I have a prime and spent the last two days trying to find the nvflash binaries on the hacked nvidia site and thought I would share.
 

Attachments

  • nvflashwin32_adb_fastboot.zip
    697.8 KB · Views: 2,913
Last edited:

joe ferreira

Senior Member
May 21, 2007
582
296
Mountlake Terrace, WA
fastboot/blobs after the nvflash fix

flashing a recovery like twrp:
say you get a copy of twrp from http://teamw.in/project/twrp2/93

it comes for the tf201 in a .blob format (openrecovery-twrp-2.2.0-tf201.blob)

at a commandline type
blobunpack openrecovery-twrp-2.2.0-tf201.blob

this will give you a file called openrecovery-twrp-2.2.0-tf201.blob.sos
this is the recovery.img file

in nvflash
nvflash -r --download 5 openrecovery-twrp-2.2.0-tf201.blob.sos

in fastboot
fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.2.0-tf201.blob.SOS
 
Last edited:

cyiam40

Senior Member
Aug 28, 2010
79
11
Joe you rock! I have been teaching myself linux until u posted this.

Sent from my Transformer Prime TF201 using XDA Premium HD app
 

rift999

Senior Member
Jan 3, 2012
224
21
In regards to the windows version. I got past the wheelie line and when I type in a nvflash command it does not recognize nvflash as a command. I think I need windows 64bit binaries for nvflash?
 

YoMarK

Senior Member
Sep 15, 2007
440
88
Tnx Joe, Windows binary worked fine.

Just followed the guide from Windows without problems, have working nvflash now. :good:

Edit: bought you guys some coffe/beer.
 
Last edited:

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
A couple of questions:

- How does nvflash behave when facing bad blocks? Is --obliterate the option to handle them? Or is it --format_all?
- How big is the nand? Is it really 32GB? If so, we would have a lot of space to, say, install another operating system on it, would that be feasible?
- Can we get a partition list with --getpartitiontable? It requires the --bl <bootloader> option to also be passed on the command, would that be ebtblob.bin?

TIA
 

Attachments

  • 6343570-620-410.jpg
    6343570-620-410.jpg
    147.6 KB · Views: 196

joe ferreira

Senior Member
May 21, 2007
582
296
Mountlake Terrace, WA
In regards to the windows version. I got past the wheelie line and when I type in a nvflash command it does not recognize nvflash as a command. I think I need windows 64bit binaries for nvflash?

no i did this on windows 32 bit.
wheelie.exe and nvflash need to be extracted in the same folder...

---------- Post added at 02:27 PM ---------- Previous post was at 02:26 PM ----------

Tnx Joe, Windows binary worked fine.

Just followed the guide from Windows without problems, have working nvflash now. :good:

Edit: bought you guys some coffe/beer.

thanks for donating to androidroot.mobi
I also donated to them last night.
I wanted to buy them few beers for there hard work.
 

Striatum_bdr

Senior Member
May 29, 2011
4,650
2,176
Marseille
A couple of questions:

- How does nvflash behave when facing bad blocks? Is --obliterate the option to handle them? Or is it --format_all?
- How big is the nand? Is it really 32GB? If so, we would have a lot of space to, say, install another operating system on it, would that be feasible?
- Can we get a partition list with --getpartitiontable? It requires the --bl <bootloader> option to also be passed on the command, would that be ebtblob.bin?

TIA

You've got a partition list in the cfg file in the original zip file from in OP links I guess.
Don't know about the command options didn't dig in yet.
 
  • Like
Reactions: beekay201

rift999

Senior Member
Jan 3, 2012
224
21
A couple of questions:

- How does nvflash behave when facing bad blocks? Is --obliterate the option to handle them? Or is it --format_all?
- How big is the nand? Is it really 32GB? If so, we would have a lot of space to, say, install another operating system on it, would that be feasible?
- Can we get a partition list with --getpartitiontable? It requires the --bl <bootloader> option to also be passed on the command, would that be ebtblob.bin?

TIA

I think it would be possible to dual boot with another OS if someone could figure out the bootloader to do it. I think some people were installing another form of Linux overwriting android before.

no i did this on windows 32 bit.
wheelie.exe and nvflash need to be extracted in the same folder...

They are in the same folder. I have one folder with adb, fastboot, wheelie, nvflash, and so on it. I then just shift right click to open a command window in that folder. I don't have a 32 bit windows though That is why I think I might need different binaries.
 

shreddintyres

Senior Member
Aug 25, 2010
1,527
559
Richardson, Tx
Say i wanted to do something incredibly stupid to see if it would work. say flashing a N7 kernel just to see if it works. I SHOULD be able to correct any idiocy on my part provided ive set up NVFlash properly?

No i havent done this yet i want to make sure before i even try.
 

Subsonic44

Senior Member
Jan 21, 2012
1,179
574
Virginia
Theye are in the same folder. I have one folder with adb, fastboot, wheelie, nvflash, and so on it. I then just shift right click to open a command window in that folder. I don't have a 32 bit windows though That is why I think I might need different binaries.

The nvflash that you can download in post #125 works fine on my windows 7x64 machine.
 
  • Like
Reactions: lortay78

brakeb

Senior Member
Nov 20, 2010
63
4
I'm looking for the 'blobunpack' command, so that I can unpack TWRP to put on my TFP, but I can't seem to find it anywhere...

I want to nvflash some kind of recovery... right now, I'm afraid to power this off with !!!!device update success!!!!!! on the screen.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 108
    After much hard work and scary semi-bricks, we are proud to finally provide nvflash to the masses!

    This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.

    Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!

    NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES

    More details at http://androidroot.mobi/?p=452

    Important note: We kind of forgot to clarify what the license for wheelie was so here goes. Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.

    Update log:
    1. 18. July: Added windows version!
    2. 21. July: Clarify License

    Enjoy
    - AndroidRoot.Mobi Team

    NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.
    37
    nvflash binary package for tegra 3 ICS for win32-x86/x64

    attached is a working tested nvflash binary package for tegra 3 ICS win32.
    included is also fastboot and adb executables.

    extract this zip and all wheelie win32 executables in the same directory and follow the directions on http://androidroot.mobi/?p=452 as rayman has stated.

    a couple things to note:
    MAKE BACKUPS OF YOUR BLOBS

    entering apx mode was not very clear.
    hold power + vol up until you feel the tablet vibrate
    release power and volume up and immediately press volume up for about 3 seconds
    then release volume up.

    the screen will remain blank but will be in nvidia apx mode.
    you will then need to install the apx driver from the universal driver package here on xda.


    edit: fyi I have nothing to do with androidroot.mobi team.
    I have a prime and spent the last two days trying to find the nvflash binaries on the hacked nvidia site and thought I would share.
    35
    Here's your Windows How To

    Ok, took me a while to find everything I needed and make sure everything was setup just right for this to work, but finally got all my backups made. So, I figured I'd make a how to a save a few people some time.

    **Note** This is for windows, windows 7 (x64) spicifically, but may also work on (x86).


    1) Plug in you tablet to your PC.

    2) Download the most recent version of Universal Naked Drivers here:
    http://xdaforums.com/showthread.php?t=1426502

    3) Go to Device Manager (Control Panel -> Device Manager), select any instance of Asus or TF201, and uninstall the current driver, and also choose "delete the driver software for this device." If you were already using a older version of Naked Drivers, then you places to delete drivers are under Android Device -> Asus Transformer Prime ADB Interface, and Portable Devices -> Transformer Prime TF201.

    4) Unplug your tablet, and turn off internet, just so windows doesn't go and try to download anything when you plug it back in. Plug you tablet back in and if you see it trying to install a driver, hit the X on the notification in the system tray.

    5) Go back to Device Manager, select your device (should have a ? or ! by it now, since it doesn't have drivers). Right click on it & choose Update Driver Software. Browse Computer for Driver Software, Navigate to the folder where you unzipped the driver package you downloaded earlier (make sure that the include all sub-folders is checked), select Next. A Warning may come up about security, choose to install anyway.

    6) Download the attached .zip, which includes blob & wheelie files provided by androidroot.mobi and the NV Flash files provided by joe ferreira. Make sure to thank both. Deleted upon developer request... Use the OP to find the proper tools. :)

    7) Unzip the attached file, and open a command prompt in the folder (Shift+Right Click). Follow the instructions here: http://androidroot.mobi/t3_nvflash/
    You do not need to issue the "$" in front of the commands.

    8) After you reboot & before moving on to the "Accessing nvflash" part of the guide linked above, grab the files that were made @ /sdcard/AndroidRoot and copy them to the same folder on your PC as all the other NVFlash files... Continue with the linked guide.

    9) Once you put your device in APX mode for the first time and connect it to your PC, go to Device manager and you should see a APX device with a ! symbol. Just like before, right click on it and choose update driver, navigate to your drivers folder you downloaded earlier, and update the driver. You should now be able to successfully issue the "wheelie --blob blob.bin" command and be able to move onto the next step. If your device is still showing up as Unknown device, you didn't install the drivers right, and you need to uninstall them again, and re-install them as stated.

    10) I issued the NVFlash Commands in this order:
    - wheelie --blob blob.bin
    - nvflash --resume --rawdeviceread 0 2944 bricksafe.img
    - nvflash --resume --read 14 factory-config.img
    - nvflash --resume --read 7 unlock-token.img
    - nvflash --resume --go <---- This reboots your device, so issue it last.

    11) You should be all set to go, with all your files in one folder.... go get your brick on!!! :laugh:
    11
    fastboot/blobs after the nvflash fix

    flashing a recovery like twrp:
    say you get a copy of twrp from http://teamw.in/project/twrp2/93

    it comes for the tf201 in a .blob format (openrecovery-twrp-2.2.0-tf201.blob)

    at a commandline type
    blobunpack openrecovery-twrp-2.2.0-tf201.blob

    this will give you a file called openrecovery-twrp-2.2.0-tf201.blob.sos
    this is the recovery.img file

    in nvflash
    nvflash -r --download 5 openrecovery-twrp-2.2.0-tf201.blob.sos

    in fastboot
    fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.2.0-tf201.blob.SOS
    10
    So, now that I have created all of the backup files, is there a guide somewhere which explains how to restore my device if it does get bricked? Windows 7 X64......

    No, no guide yet.

    We purposedly left out the procedure for doing a full restore until it is explicitly required.
    Our experience is that if we give the instructions for this, people will do it for every little brick that could easily be fixed in other ways and it's just not a good idea ;)

    For 99% of cases, you can restore by simply flashing the partitions that have been broken, e.g.
    1. Bootloader having issues => nvflash -r --download 4 bootloader.bin
    2. Broken or stock recovery => nvflash -r --download 5 recovery.img
    3. Broken or stock boot partition => nvflash -r --download 6 boot.img
    4. Broken system partition => nvflash -r --download 10 system.img

    stock system.img, boot.img etc can be retrieving by using the blobunpack tool on the blob file (different blob :() inside official ASUS images (downloaded from support.asus.com). When unpacked, blob.APP => system, blob.LNX => boot.img, blob.SOS => blob.LNX.

    There are very few cases where you will brick further than this and when/if that happens, we'll be happy to help people through it, assuming they have ALL the backups we mention on androidroot.mobi! In everyday usage, you won't need those backups, but when/if something really bad happens, they could mean the difference between a brick and a recoverable tablet.