[GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201

Search This thread

jo_r

New member
Nov 8, 2017
1
0
Hi guys,

Sorry, I can't help as I'm a newbie and I followed this guide and my tablet is now bricked.
Maybe someone could help me as I'm facing the same issue some of you had but I've been unable to resolve the way you did.

The problem came when I made this :
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
I confirmed flashing.
The tablet restarted, the blue bar appeared but only a few seconds and then rebooted.
Since, I've got the nvidia logo (on top left is written it is unlocked) and that's it.
I downloaded file "WW_epaduser_10_4_2_18UpdateLauncher.zip" from Asus website (it is the correct one as it's written at boot "ww_epad-10.4.2.15-20120917 A03"). I've TWRP v2.6.3.0 installed.
I tried to flash this rom but I got immediately "Failed" message.
When trying to flash "KatKiss-7.1_TF201_026.zip" from my external sd card, the progress bar showed during a few minutes until it displayed "Failed".
For information, APX works and I can enter TWRP.

Thanks a lot.

Jo
 

M!W

Member
Apr 17, 2010
9
1
Does anyone have the latest Linux binaries? The download links for Linux are broken.
 

nguberinic

Member
Dec 24, 2015
5
1
Cant really understand

Please can someone clarify the procedure !

I can get to APX mode with my asus tf 201 transformer..

I have backup of files:
recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log, bricksafe.img, factory-config.img and unlock-token.img.

But I have no idea why in the hole process of restoring tablet I use none of the files.
My Asus is stucked in bootloop, and it boots back after roughly 10 sec beaing stuck in teamwin recovery window and then bootloops again and so on.
When I press power and volume up button and I
call wheelie in help it uploads 'wheelie.exe --blob blob.bin',
as soon as I enter next command 'nvflash.exe -r --download 4 blob.EBT' it uploads the file and it goes to loop again.

I have followed guide for installing Android 7.1 Nougat 'https://forum.xda-developers.com/transformer-prime/help/guide-tutorial-asus-transformer-prime-t3486237'
and there it says •Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot) bootloader V 10.4.2.18.

Here am reading that it's not good if it's v10.4.2.18... Am getting really confused.

Once again, if someone could clarify in simple English, what am I doing wrong, or what should I do to do it the right way...
Thank you all for patience !
 
Please can someone clarify the procedure !

I can get to APX mode with my asus tf 201 transformer..

I have backup of files:
recovery.bct, create.bct, bootloader.ebt, blob.log, blob.bin, pt_restore.log and pt_patch.log, bricksafe.img, factory-config.img and unlock-token.img.

But I have no idea why in the hole process of restoring tablet I use none of the files.
My Asus is stucked in bootloop, and it boots back after roughly 10 sec beaing stuck in teamwin recovery window and then bootloops again and so on.
When I press power and volume up button and I
call wheelie in help it uploads 'wheelie.exe --blob blob.bin',
as soon as I enter next command 'nvflash.exe -r --download 4 blob.EBT' it uploads the file and it goes to loop again.

I have followed guide for installing Android 7.1 Nougat 'https://forum.xda-developers.com/transformer-prime/help/guide-tutorial-asus-transformer-prime-t3486237'
and there it says •Android 4.1.1 (JellyBean; Nvidia logo bottom right on boot) bootloader V 10.4.2.18.

Here am reading that it's not good if it's v10.4.2.18... Am getting really confused.

Once again, if someone could clarify in simple English, what am I doing wrong, or what should I do to do it the right way...
Thank you all for patience !

Look like you're on the wrong bootloader, a stock TF201t need to be updated to the HairyBean Bootloader in order to work, I'm on bootloader version 10.6.1.27.1 which needs to updated to run TWRP and 7.1. - NP

https://forum.xda-developers.com/showthread.php?t=2407248
 
Last edited:
@nguberinic

Got your PM, but it wont let me paste picture, the bootloader version is only visible when you boot up the tablet, if you boot in the fastboot screen it will stay on the screen and look like this. - NP
 

Attachments

  • TF201t_fastboot_screen.jpg
    TF201t_fastboot_screen.jpg
    33.1 KB · Views: 79

sturm314

New member
Sep 21, 2018
1
0
Hello,

It looks like something when wrong while following the procedure to upgrade my tf201 to Nougat ( like in the step-by-step tutorial from djibe ).

Fortunately, I had created all the img and wheelie blobs before I bricked my tab. The problem now is that I can only get the tablet into APX mode (otherwise it won't boot at all). Thus, I'm trying to recover it to factory settings and normal status with nvflash.

However, I couldn't find anywhere how to use the blobs and img files to recover the tab with nvflash, since the names of the files don't match with the nvflash tutorial (and I really don't understand much what I'm doing). Besides this, I've tried to download the zip files (TF201-JB-10.4.2.15-Unblobed.zip or TF201-ICS-9.4.2.28-Unblobed.zip), but none of both links seem to work. Could you please help me on this?

Many thanks in advance,
Sturm
 

georgecoat

Senior Member
Dec 27, 2014
50
14
Hi guys,
My tf201 keeps shutting down.
I was using it when suddenly if just shut down and went black dead.
I started it, in several seconds it goes off again.
When started to recovery or to system, or even get into nvflash recovery mode it just goes off in several seconds.
The same for adb or fastboot, i cannot do anything, it just shut off in a second as soon as I get into any mode.
I have got all the files and backups ready, but my problem is that tf201 keeps shutting down and I cannot push any files to it.
I wonder if any of the experts here have seen something like this I would really appreciate any suggestions.
 

EpicLPer

Senior Member
Aug 29, 2012
694
385
28
Scheibbs
epiclper.com
Hi guys,
My tf201 keeps shutting down.
I was using it when suddenly if just shut down and went black dead.
I started it, in several seconds it goes off again.
When started to recovery or to system, or even get into nvflash recovery mode it just goes off in several seconds.
The same for adb or fastboot, i cannot do anything, it just shut off in a second as soon as I get into any mode.
I have got all the files and backups ready, but my problem is that tf201 keeps shutting down and I cannot push any files to it.
I wonder if any of the experts here have seen something like this I would really appreciate any suggestions.

There's a little hole on the left side which is a reset switch. Press it for a few seconds and see if it fixes stuff. For me it fixed the weird audio and lag issues I had a few years back, even after disconnecting the battery which was weird...
 
  • Like
Reactions: georgecoat

andrewjt19

Senior Member
AIM: This is a general users guide to unbrick, recover, downgrade or upgrade using nvFlash for the Transformer Prime TF201. I will try my best to help anyone out so please feel free to PM me if you have any questions.

REQUIREMENTS:
1. Transformer Prime TF201 (duh!!!)
2. Enabled nvFlash access (Tegra 3 nvFlash by AndroidRoot)
3. Window or Linux computer [Linux recommended]
4. Ability to use a command prompt or terminal shell
5. nVidia APX drivers [Windows Only] (Universal Naked Drivers)
6. Wheelie & nvFlash binaries/executables
7. You device specific nvFlash backup files generated while enabling nvFlash

THIS GUIDE COVERS:
1. Manual steps for basic unbrick, recovery, downgrade or upgrade. [Windows & Linux] This is your first option to recover your device.
2. Automated complete factory reset & recovery [Linux Only] Use this only if you cannot recover using the manual steps or if you want to completely wipe and recover your device.

IMPORTANT INFORMATION:
At the moment, nvFlash can only be enabled on a device with the 9.4.2.28 ICS bootloader. If you have upgraded to the official Jelly Bean ROM before enabling nvFlash, you would have the new 10.4.2.15 bootloader and you will no longer be able to enable nvFlash. When following this guide, read the information provided carefully to prevent any permanent damages. Be patient as each step may take a while to complete. Make sure your device is charged (recommended more that 75% battery) before attempting anything detailed here. Do not forcefully power off your device at the wrong time. Keep you device connected to your computer during the whole process. If you encounter bootloops or are stuck at the Asus spinning wheel after this process, a data wipe should fix this (Power + Vol Down, then select Wipe Data)

WHY ENABLE NVFLASH:
nvFlash would allow you to recover your device from almost any brick and would allow you to upgrade or downgrade your device.

SETUP:
1. Download the nvFlash binary/executable for your operating system [ Windows / Linux ]
2. Download the wheelie binary/executable for your operating system [ Windows / Linux ]
3. Install the APX drivers [ Windows Only ]

FOR LINUX USERS:
Make sure you always run nvflash and wheelie as root or sudo. If your user does not have root privileges or is not a sudoer, you will quite likely not be able to do this. If you are a root user, do not use the sudo prefix in the commands below.

INSTRUCTIONS [MANUAL STEPS]:
1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie

5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:

7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:

8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:

9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:

10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)


SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY:
This process completely wipes all partitions (except external SD/mSD cards) and reflashes everything, essentially returning your device to a near factory state. You will not lose you unlock status or nvFlash access. You will lose all data from your internal storage (/storage/sdcard0 or /data/media).
Unfortunately, due to technical reason, this process is possible only using Linux, since the nvflash executable for Windows is very old and cannot handle this process. I will be creating a detailed step-by-step guide for those not comfortable with Linux. But for now, this is available for all those who know how to use Linux.
To use this, you need to download one of the unblob'd stock ROMs below (or create your own) along with the semi-automated complete recovery zip below.
You will also need the device specific nvFlash backup generated when you enabled nvFlash.
Complete instruction are in the "README" file in the semi-automated complete recovery zip.

DISCLAIMER: nvFlash can save your device, but if used incorrectly, it could permanently brick your device. If you follow the instructions carefully, you should not have any problems. However, in the event that you do have a problem, neither I (craigacgomez), nor the AndroidRoot team can be held responsible. Use this guide at your own discretion. If you need help or do not understand something, PM me and I will try to help you as much as I can.

DOWNLOADS:

UN-BLOB'D STOCK ICS 9.4.2.28 ROM
- Un-blob'd stock ICS 9.4.2.28 ROM
- Completely unmodified

UN-BLOB'D STOCK JB 10.4.2.15 ROM
- Un-blob'd stock JB 10.4.2.15 ROM
- Completely unmodified

SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY [Read Info Above Before Using This!!]

CREDITS:
AndroidRoot - Everything you see here has been made possible because of the AndroidRoot team.
nVidia

SUPPORT THE PROJECT
Donate to AndroidRoot - They are the amazing people behind nvFlash for the Prime
Donate to me (craigacgomez)

Does anyone have the original un-blobbed ICS and JB ROM's they could share? They links in the OP are dead. Thanks
 
Last edited:
  • Like
Reactions: georgecoat

georgecoat

Senior Member
Dec 27, 2014
50
14
There's a little hole on the left side which is a reset switch. Press it for a few seconds and see if it fixes stuff. For me it fixed the weird audio and lag issues I had a few years back, even after disconnecting the battery which was weird...

Thank you very much.
I tried, unfortunately it didn't help :(
Thanks again for suggestion.
 

georgecoat

Senior Member
Dec 27, 2014
50
14
There's a little hole on the left side which is a reset switch. Press it for a few seconds and see if it fixes stuff. For me it fixed the weird audio and lag issues I had a few years back, even after disconnecting the battery which was weird...

Hi guys,
My tf201 keeps shutting down.
I was using it when suddenly if just shut down and went black dead.
I started it, in several seconds it goes off again.
When started to recovery or to system, or even get into nvflash recovery mode it just goes off in several seconds.
The same for adb or fastboot, i cannot do anything, it just shut off in a second as soon as I get into any mode.
I have got all the files and backups ready, but my problem is that tf201 keeps shutting down and I cannot push any files to it.
I wonder if any of the experts here have seen something like this I would really appreciate any suggestions.

I think this might be a hardware issue? Maybe the battery fried?
:(
 

georgecoat

Senior Member
Dec 27, 2014
50
14
I think this might be a hardware issue? Maybe the battery fried?
:(

I got it back to life!
It was the battery issue!
Just to recapitulate:
It started by shutting down the tablet one day while showing 100% battery.
Would not boot into anything (system, recovery, adb, fastbook even nvflash mode) because it would shut off after several seconds.
I tried to reinstall everything, but I could not finish any process, tablet would shut down in the middle.
I left it connected on the dock hoping it will recharge.
After 2-3 days I tried to start it, it would show red battery screen and shut down immediately. That was something new I have not seen before.
I looked around and have find out that battery is or completely fried or need to get reset.
There is two methods to try.
1. open the tablet and unplug the battery cable, then after a while plug it back and charge.
2. reset by applying paper clip in the little hole on the left side of the tablet below the Micro SD card slot and charge at the same time.

I decided to start with the second method first, since I didn't want to open the tablet.
I plugged the paper clip into the hole and taped it on the body of the tablet with the tape in a way that would apply constant pressure on the clip. I plugged it through the USB into the computer and let charging for about 5-7 hours.
Then I tried to start it into recovery.
Miraculously it worked and battery was showing 35%.
After that point everything wen smooth, I formatted and reinstalled new N 7.1.2] [ KatKiss - Nougatella #036 ] by timduru and it works like new again.
Battery is charging normally and instead of constant 100% is now showing real number that goes down when I use the tablet and up when I charge it.
Looks like the battery needed to be reset by complete discharging and then starting it up by disabling all the controls using the paper clip trick while charging on computer. That started the battery again into a new life.
Hopefully this post will help someone in similar troubles.
Thanks for support guys!
Sincerely
georgecoat

---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------

Does anyone have the original un-blobbed ICS and JB ROM's they could share? They links in the OP are dead. Thanks


You can unblob it yourself.
Get the stock firmware here.
Get the blob tools here.
unpack blobtools and blob from downloaded zipped stock firmware in the same folder. Then start the cmd window in that folder and run


you will get

blob.LNX - boot.img
blob.SOS - recovery.img
blob.EBT - bootloader.bin
blob.APP - system.img
blob.PT- partition info
 

jehe1966

New member
Dec 29, 2013
1
0
nvFlash binary/executable for linux

Hello,

Apparently the androidroot.mobi website is offline, where can I find the nvFlash binary / executable for linux (ubuntu).

Thank you in advance
 

FlyingTaco

Member
Sep 1, 2010
12
1
Tallahassee
nvFlash binary/executable for linux

Hello,

Apparently the androidroot.mobi website is offline, where can I find the nvFlash binary / executable for linux (ubuntu).

Thank you in advance
Sorry for necro bumping but I found them on github:

wheelie in the linux tarball gave me errors but the one I compiled from source worked:

nvflash may complain about file creation, AndroidRoot generated by the CWM recovery is owned by root.

Just leaving these notes here in case someone else stubs their toe on an old tf201 they had laying around and was today years old when they found out you could get nvflash even after the JB bootloader.
 

EpicLPer

Senior Member
Aug 29, 2012
694
385
28
Scheibbs
epiclper.com
Just leaving these notes here in case someone else stubs their toe on an old tf201 they had laying around and was today years old when they found out you could get nvflash even after the JB bootloader.
I don't even know if this is of any use these days? Does modern Ubuntu run on it still?
Even the optimized and ported Android versions with that Merkat or whatever it was isn't running smoothly at all anymore sadly since that hardware is just too old these days. Is it even worth trying?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 52
    AIM: This is a general users guide to unbrick, recover, downgrade or upgrade using nvFlash for the Transformer Prime TF201. I will try my best to help anyone out so please feel free to PM me if you have any questions.

    REQUIREMENTS:
    1. Transformer Prime TF201 (duh!!!)
    2. Enabled nvFlash access (Tegra 3 nvFlash by AndroidRoot)
    3. Window or Linux computer [Linux recommended]
    4. Ability to use a command prompt or terminal shell
    5. nVidia APX drivers [Windows Only] (Universal Naked Drivers)
    6. Wheelie & nvFlash binaries/executables
    7. You device specific nvFlash backup files generated while enabling nvFlash

    THIS GUIDE COVERS:
    1. Manual steps for basic unbrick, recovery, downgrade or upgrade. [Windows & Linux] This is your first option to recover your device.
    2. Automated complete factory reset & recovery [Linux Only] Use this only if you cannot recover using the manual steps or if you want to completely wipe and recover your device.

    IMPORTANT INFORMATION:
    At the moment, nvFlash can only be enabled on a device with the 9.4.2.28 ICS bootloader. If you have upgraded to the official Jelly Bean ROM before enabling nvFlash, you would have the new 10.4.2.15 bootloader and you will no longer be able to enable nvFlash. When following this guide, read the information provided carefully to prevent any permanent damages. Be patient as each step may take a while to complete. Make sure your device is charged (recommended more that 75% battery) before attempting anything detailed here. Do not forcefully power off your device at the wrong time. Keep you device connected to your computer during the whole process. If you encounter bootloops or are stuck at the Asus spinning wheel after this process, a data wipe should fix this (Power + Vol Down, then select Wipe Data)

    WHY ENABLE NVFLASH:
    nvFlash would allow you to recover your device from almost any brick and would allow you to upgrade or downgrade your device.

    SETUP:
    1. Download the nvFlash binary/executable for your operating system [ Windows / Linux ]
    2. Download the wheelie binary/executable for your operating system [ Windows / Linux ]
    3. Install the APX drivers [ Windows Only ]

    FOR LINUX USERS:
    Make sure you always run nvflash and wheelie as root or sudo. If your user does not have root privileges or is not a sudoer, you will quite likely not be able to do this. If you are a root user, do not use the sudo prefix in the commands below.

    INSTRUCTIONS [MANUAL STEPS]:
    1. Download an un-blob'd ROM (links below). [Advanced users can use BlobTools (blobunpack) and unblob a ROM. Make sure you have compatible unblob'd images of the bootloader, recovery, kernel & system]
    2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)
    3. Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode.
    4. Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie
    Windows:
    Code:
    wheelie.exe --blob blob.bin
    Linux:
    Code:
    sudo ./wheelie --blob blob.bin
    5. After wheelie does it's job, your device will be ready in nvFlash mode. You can now begin the process.
    6. We start with the bootloader. In the case of the un-blob'd ROMs below, this is the blob.EBT file. To flash the bootloader, use this command:
    Windows:
    Code:
    nvflash.exe -r --download 4 blob.EBT
    Linux:
    Code:
    sudo ./nvflash -r --download 4 blob.EBT
    7. Next we move to the recovery image. In the case of the un-blob'd ROMs below, this is the blob.SOS file. To flash the recovery image, use this command:
    Windows:
    Code:
    nvflash.exe -r --download 5 blob.SOS
    Linux:
    Code:
    sudo ./nvflash -r --download 5 blob.SOS
    8. Next we move to the boot image. In the case of the un-blob'd ROMs below, this is the blob.LNX file. To flash the boot image, use this command:
    Windows:
    Code:
    nvflash.exe -r --download 6 blob.LNX
    Linux:
    Code:
    sudo ./nvflash -r --download 6 blob.LNX
    9. Next we move to the system image. In the case of the un-blob'd ROMs below, this is the blob.APP file. To flash the system image, use this command:
    Windows:
    Code:
    nvflash.exe -r --download 10 blob.APP
    Linux:
    Code:
    sudo ./nvflash -r --download 10 blob.APP
    10. Finally, we reboot the device. After you run the following command, you will see the text "AndroidRoot 9.4.2.28" and your device should reboot in a few seconds. If you device does not reboot after you see the text, force a reboot (long press the Power button)
    Windows:
    Code:
    nvflash.exe -r --go
    Linux:
    Code:
    sudo ./nvflash -r --go

    SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY:
    This process completely wipes all partitions (except external SD/mSD cards) and reflashes everything, essentially returning your device to a near factory state. You will not lose you unlock status or nvFlash access. You will lose all data from your internal storage (/storage/sdcard0 or /data/media).
    Unfortunately, due to technical reason, this process is possible only using Linux, since the nvflash executable for Windows is very old and cannot handle this process. I will be creating a detailed step-by-step guide for those not comfortable with Linux. But for now, this is available for all those who know how to use Linux.
    To use this, you need to download one of the unblob'd stock ROMs below (or create your own) along with the semi-automated complete recovery zip below.
    You will also need the device specific nvFlash backup generated when you enabled nvFlash.
    Complete instruction are in the "README" file in the semi-automated complete recovery zip.

    DISCLAIMER: nvFlash can save your device, but if used incorrectly, it could permanently brick your device. If you follow the instructions carefully, you should not have any problems. However, in the event that you do have a problem, neither I (craigacgomez), nor the AndroidRoot team can be held responsible. Use this guide at your own discretion. If you need help or do not understand something, PM me and I will try to help you as much as I can.

    DOWNLOADS:

    UN-BLOB'D STOCK ICS 9.4.2.28 ROM
    - Un-blob'd stock ICS 9.4.2.28 ROM
    - Completely unmodified

    UN-BLOB'D STOCK JB 10.4.2.15 ROM
    - Un-blob'd stock JB 10.4.2.15 ROM
    - Completely unmodified

    SEMI-AUTOMATED COMPLETE RECOVERY - LINUX ONLY [Read Info Above Before Using This!!]

    CREDITS:
    AndroidRoot - Everything you see here has been made possible because of the AndroidRoot team.
    nVidia

    SUPPORT THE PROJECT
    Donate to AndroidRoot - They are the amazing people behind nvFlash for the Prime
    Donate to me (craigacgomez)
    16
    What is APX mode?
    APX mode is basically a programming mode or download mode for nVidia based devices. On a development device or an unrestricted device, when you get into APX mode, you can program your device using nvflash commands. Most production devices lock down APX mode and disable nvflash access. This is where wheelie comes into the picture for our devices. If you cannot access APX mode, you have probably permanently bricked your device.

    What is wheelie?
    Wheelie is an nvflash pre-loader that boots the tablet into an nvflash ready mode that lets you use regular nvflash commands (with -r prepended!). Wheelie was created by the amazing folks at AndroidRoot. Wheelie uses the "device specific" blob.bin file to bootstrap the device in APX mode and allow nvflash access. The blob.bin file has information like the Chip UID which is different for each devices and cannot be used interchangeably. If you get you device repaired or RMA'd and the motherboard is replaced, you would need to regenerate the blob.bin file.

    What is nvflash?
    nvflash is a low-level flash utility for nVidia based devices which gives you low level access to the system to flash, format, recover, repartition and do many more functions. It is a very powerful tool and should be used with caution. Read and follow all instruction carefully when using nvflash.

    What is "-r" in the nvflash command?
    The whole purpose of -r or --resume is to tell nvflash that the device is already running the nv3pserver (nvflash recovery mode), without -r or --resume it will try to do the preflight that wheelie does for us.

    What is "--download X" in the nvflash command?
    This parameter in the nvflash command is used to download/flash the specified file to partition X in the device. So the command "nvflash -r --download 4 blob.EBT" with download/flash the file blob.EBT to partition 4. These partitions are defined in the device partition table. The flash.cfg file in your nvflash backup is the partition table description if you want to know more details.

    What is "--go" in the nvflash command?
    This parameter in the nvflash command is used to boot bootloader after nvflash completes instead of looping in nv3pserver in resume mode. Basically it should exit resume mode and reboot your device.

    What is BlobTools?
    Once again, this is the genius brainchild and result of the amazing folks at AndroidRoot. The Asus Transformer series uses "blobs" to flash stuff. A blob can have multiple partitions (system, boot, recovery, bootloader). Blobs are moved to the staging partition (/dev/block/mmcblk0p4) and are automatically flashed upon reboot. The blob header defines where the different files in a blob get flashed to (boot gets flash to the boot partition, system to the system partition, etc.). BlobTools in a utility to create and extract these staging blobs. All blobs need to be extracted before being using with nvflash.

    I have already upgraded to Jelly Bean. Can I still use nvFlash?
    At the moment, nvFlash can only be enabled if the device is using the 9.4.2.28 ICS bootloader. If you have not yet enabled nvFlash and you have upgraded to the stock Jelly Bean ROM, you will have the 10.4.2.15 bootloader and you will no longer be able to enable nvFlash.
    If you have already enabled nvFlash before upgrading to the stock Jelly Bean ROM, you will continue to have nvFlash access even though your bootloader was upgraded.
    5
    Thanks for info. I used this procedure few weeks ago. Got the bootloader back but stuck in APX mode. Couldn't boot. I needed to flash other files back. Then repartitioned and format all partitions fresh.

    There's actually an automated process for it. Does every partition and sector back from backup files. It reverts device completely back to previous state. Its posted by kmdm. Only works in Linux though. Link below.

    http://forum.xda-developers.com/showpost.php?p=32365961&postcount=489

    Wejgomi

    Yes, I have made automated scripts for both these un-blob'd ROMs for Windows & Linux... I just need to test them before releasing them (most probably tonight PDT)... the manual steps will work till then...
    3
    Hi! (I know that this is an old post, but as newbies gonna search for these answers, I will provide them.)

    In the mean time, I have a few questions now that I'm at this point, and I'm not sure if this is the appropriate thread or not, but here goes:

    1) Now that I'm at this point, is it safe to update to ota jb without losing nvflash access to recover my tablet? or will it overwrite the bootloader making it possible to brick again?


    • NVFlash is a part of the nVidia Tegra SoC (System on Chip) and it is not stored in the flash part of your device.
    • It is (as someone explained) a substantial part of the hardware. It cannot be removed, disabled, changed or modified in any known way (well, you could try to solder the chip and do stuff...).
    • Every(?) Tegra device has a unique encryption key which is part of that code and therefor cannot be altered, too.
    There is (again, as I have been explained) nothing you can do with adb, fastboot and APX/wheelie/nvflash that will alter that features. It is unbrickable, as long as there is no hardware error/defect (e.g. USB port malfunction).

    Therefor, flashing any recovery/bootloader/ROM will not remove nvflash abilities.

    But beware: nvflash has to be used the first time to create the backup files before you go to any ASUS Stock ROM with Android 4.1/4.2 (as my device is a TF300T/TF300TG I cannot advice you on the right version numbers as they differ from model to model). You must keep the files safe. They are unique to each device because of the above mentioned encryption key. You cannot "borrow" the blob.bin files etc from any other device as they are device specific encrypted.

    (Often the terminus used is "to install nvflash" which is technically quite wrong as you do not permanently install anything to your device. What you do is to download/copy the encrypted bootloader and other partitions. Therefor: keep the files safe.)

    Why only working below 4.1? Because after you upgraded to JellyBean you will not be able to install a custom bootloader. But this is needed to create the nvflash backup files. Asus made us a real PITA! After being on any JellyBean bootloader only Asus can install bootloaders. Because only they have the encryption key "to be let in". Or you can use nvflash, because the backed up files are already encrypted for your device.

    2) TWRP will not backup my tablet, it keeps giving me an error every time I try, so I installed AndroidRoot's patched CWM according to their instructions. Will I be able to reinstall that if I do update to ota jb?

    Again, my device TF300TG/TF300T is very similar in nvflash matters, but the prinicples are the same.

    CWM and TWRP are custom recoveries. From the moment you "unlock your bootloader" with ASUS' unlock tool you are entitled to install any recovery compatible with your hardware. The recovery has to be specific to the bootloader (on TF300T(G)), so after installing 4.1 or 4.2 you need a different TWRP or CWM (read their homepage and/or device specific threads!).

    Even if Asus removed the possibility to flash a custom recovery e.g. with the next JB update, you would be able to go back to the nvflash backup which enabled the old bootloader (e.g. 4.0) and let you install the desired recovery/custom ROMs/Stock ROMs.

    Again, Asus cannot steal that nvflash option from you. You can always revert. (Again, I did not invent/research all of this by myself, I only spent days(!) reading the forum on these topics.)

    3) Can I install CM10 safely and be able to revert back to stock if I don't care for it, or if it's not stable enough for my everyday use?

    Yes.

    (But just be aware that you should make nandroid/Titanium Backup/app data backups as changing the ROM requires often to do a full wipe.)

    If there are (substantial?) errors in this text, please PM or reply so that I can fix this. I really want to help, especially the new people. It is a pain if there are errors, especially when they are not corrected or only corrected 500+ posts later. ;)
    3
    Here you go.

    DOWNLOADS:

    UN-BLOB'D STOCK ICS 4.0.3 (9.4.2.28) ROM

    - MD5 - a74e05be2d3aba2af5c970e30d3a3720
    - Un-blob'd stock ICS 4.0.3 (9.4.2.28) ROM
    - Completely unmodified

    UN-BLOB'D STOCK JB 4.1 (10.4.2.18) ROM

    - MD5 - 47603552984c10b7e7180fb6cb23901e
    - Un-blob'd stock JB 4.1 (10.4.2.18) ROM
    - Completely unmodified