Database Info

[Q] nvflash

Last nigh I left my transformer at 25% battery power in flight mode.
This morning was not able to switch my Transformer on.
After trying all possibilities to enter recover mode without success, I decided to use NVflash and reflash prime_v1.4.
However NVflash exits with the following error. What can go wrong?
Any idea how to fix this?
Regards,
Nikola
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA xA532EEB 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags:
0

same error :s

Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Click to expand...
Click to collapse
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)

Kasimodo said:
Have you copy/paste your NVFlash command in this thread or do you write it yourself?
Because it seems to be an error in your command:
the right command is:
The difference between this one and yours is the "0" before "xA532EEB6". You muste have "0xA532EEB6"
if it dosen't work try with another version of Prime... (1.5 or 1.8)
Click to expand...
Click to collapse
This is the content of download.bat
cd %~dp0
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
I tried with different versions of Prime but the same error happens.
Is there any other way to get some more logging/debug info from the bootloader or to check if the emmc memory is not broken or locked.
Regards,
Nikola

I think there is a problem with your internal SD. Because the next command after creating partitions is to format partitions.
But have you tried to download another nvflash.exe?
Otherwise I don't see anything else

battery is too low

Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...

tnp0511 said:
Command is correct (it's in dowload.bat file) and battery is 100% (all night charging) but always the same error...
When I execute batch file, after a few seconds, screen turn on and display :
Code:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: xxxxxxxxxxxxxxxxxxxxx
And batch file close...
Click to expand...
Click to collapse
Exactly the same behavior here.
I will try to charge it tomorrow with another charger.

Make sure to run in a cmd window so that you can see why it's exiting

Run from cmd window
AustinMartin said:
Make sure to run in a cmd window so that you can see why it's exiting
Click to expand...
Click to collapse
The run has also been done from a cmd window:
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --go
It is always exiting with:
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x42008 (0x19042008) flags: 0
Also interesting to notice that when I run without --create and without --go but with --sync
"nvflash.exe" --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB 0xECFE1D98 --sync
The output is
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208340403317
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
but I never get the prompt back.

Is your TF101 rooted?

Kasimodo said:
Is your TF101 rooted?
Click to expand...
Click to collapse
Yes, it was rooted. 1 mount ago i flushed prime1.4 using the same procedure (nvflash + prime1.4). everything worked OK until sunday morning when the TF101 would not switch on.
Regards,
Nikola

Argh. I'm afraid that there is a physical problem.
If it was mine I will try to unroot it to see. Anf after the best is to contact Asus for return.

any other idea ?
otherwise return to Asus on Saturday

im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"

uman01 said:
im sorry for bumping old thread, just curious about the result, since now i have exatly the same problem, i can go into apx mode, but when i started the download.bat, the problem is the same, nvflash just exit after that, tf screen turned on, and when i tried to start the download.bat again, the cmd only show "nvflash is starting"
Click to expand...
Click to collapse
+1
what can we do?

DTrainMusicVein said:
+1
what can we do?
Click to expand...
Click to collapse
You probably have an SBKv2 tablet which you can't use NVFlash right now

baseballfanz said:
You probably have an SBKv2 tablet which you can't use NVFlash right now
Click to expand...
Click to collapse
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance

DTrainMusicVein said:
I checked the original package and it says B50, where exactly would I find if its SBKv1 or 2? Correct me if I'm wrong, but I thought B50s were SBKv1?
Thanks in advance
Click to expand...
Click to collapse
Yes you're B50 should be SBKv1.
You do have all the needed files in the nv flash folder?

I believe so, I have downloaded the rooted and unrooted US versions of the ICS NVFlash and I am going to try the WW next? Any other tips? Its still failing on me...

[solved] Help with NVflash? Reflash failing

Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x37c708542bff297
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!

nvflash on ASUS Transformer Prime TF201

Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

I am getting the same error on mine too.

Same error for me
It took a lot of effort to find a copy of nvflash for ics, but now I find that it does not work and returns the above error.
Russ

tinnymarlin said:
Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
I got the same thing. maybe the nvflash problem. It just display "bad command".

[Q] NVFLASH after restore seems tablet is bricked

While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?

orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin

rigidsh said:
I have same problem, and here http://forum.xda-developers.com/showthread.php?t=1774352&page=47 I read a solution of this problem:
try
Code:
wheelie -r --blob blob.bin
Click to expand...
Click to collapse
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.

Looking for some help on this...
Hi!
So you got the TF300T into APX mode and ran these commands?:
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
...Did you have the files on your PC or on the tablet themselves? Also, how do you get the twrp-ICS.img? I've got the openrecovery-twrp-2.2.2.0-tf300t-ICS.blob file. Do I change it to twrp-ICS.img somehow?
Sorry if this seems like a dumb question. I want to get back to ICS bootloader from JB but finding instructions has been kind of tough. Your post is the first I've found that helps!
Thanks!
-Rob
orion42 said:
WOW! thanks for that! That -r switch has got my tablet back, well eventually.
Just some info for anyone else who might encounter the same problem.
Code:
wheelie -r --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --go
After running the above commands I was still getting a blank screen trying to boot into recovery. Nothing to lose I tried running the above commands missing out the recovery command. After all, I must have flashed the recovery a dozen times. With little hope of success, volume down after the --go command. Bingo, I was into recovery, I could hardly believe it. Successfully restored an ICS backup.
So it's true, if you have the NVFLASH files, you can get back to ICS from JellyBean.
EDIT: I guess the bricksafe and recovery commands should be reverse of what I did.
Click to expand...
Click to collapse

First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.

THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
orion42 said:
First of all, I have to say that I am no expert on NVFLASH and I sort of muddled my way back to ICS rather than knew the correct method. On the other hand, as you point out, there doesn't seem to be any clear instructions anywhere in this forum.
I have the following files on my PC:-
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factory-config.img
recovery.bct
unlock-token.img
These files are specific to the machine on which they were created. If you didn't create them while you were in ICS then, as far as I know, there is no way back to ICS, at least for now.
By the way, I have no idea what all the above files are for but I only needed two of them to get back to ICS.
You will need either an ICS backup to restore or an ASUS ROM to install once in recovery.
The commands have to be run from a command prompt on a PC or laptop with the APX drivers installed.
Connect to the PC then power off tablet. ---- volume up plus power --- and you should get a blank screen.
Apparently my post was a bit unclear about the sequence of commands. This is the correct sequence:-
wheelie --blob blob.bin ( -r switch is probably not needed on the first attempt )
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named)
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --go
--- volume down to boot into recovery ---
DISCLAIMER: These commands worked for me but I can't guarantee they will work for anyone else. If they don't work for you then I don't have any more answers. The process is a bit hairy and if you're unsure, I wouldn't do it.
Click to expand...
Click to collapse

robcomet1 said:
THANK YOU SO MUCH! I will try it out and report back here later with my results. I do have all the necessary files you mentioned so I should be ok! Here's hoping! :fingers-crossed:
Click to expand...
Click to collapse
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817

Will do! Still haven't had a chance to do it yet. Will let you know.
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse

Finally got a chance to do this to my pad and it worked great! Thanks again for the help my friend! I'm back on CM10 as we speak! :victory:
orion42 said:
nvflash --resume --download 5 twrp-ICS.img ( or openrecovery-twrp-2.2.2.0-tf300t-ICS.blob or whatever the file is named )
With regard to this command, If you only have a blob file I'm not sure if it will work.
It's probably safer to download and flash an img file:
http://forum.xda-developers.com/attachment.php?attachmentid=1351051&d=1348498817
Click to expand...
Click to collapse

orion42
As you said information about restore with NVFlash is sparse. Could you create a thread with the proper information that others can follow to recover their units? I don't have NVFlash but have seen numerous threads where people needed help as you provide.
Thanks!

orion42 said:
While still on ICS I created all the necessary files for NVFLASH. I then installed stock jellybean and later installed CLEANROM 2.5.
I was quite happy with this ROM but I just had to know if I could get back to ICS using NVFLASH. Big mistake perhaps.
I am no expert but I did my best to follow all the instructions I could find. I went into APX mode and ran the following commands:-
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 5 twrp-ICS.img
All commands seemed to work and reported success. I'm not sure but at this point I perhaps should have run "nvflash --resume --go" but I didn't. Instead, for some reason, I powered off the machine with the power button and then tried to reboot into twrp recovery. Nothing just a blank screen.
I then tried to power on while pressing the volume up button to try to get back into APX mode with the following result:-
E:\X\ADB\TF300T>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2109a6540a08
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error -1 sending command
So it seems that perhaps the chip id is recognised so maybe there is some hope or am I clutching at straws?
Can anybody help?
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.

rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
I can't believe you posted that! Have you by chance seen how many bricks there have been on nvflash due to lack of info?
Your guide is good for creating files but no mention of how to use them. Everyone doesn't have your knowledge and insight.
Maybe it is time to reveal the secrets of nvflash. It could be a good thing but as it stands it is a brick maker due to lack of knowledge and help.

rayman said:
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM

uumeshh said:
can you please tell us how to get blob.EBT, blob.APP and blob.LNX files from ICS ROM
Click to expand...
Click to collapse
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
http://forum.xda-developers.com/showthread.php?t=2012033

rayman said:
Your issue is the fact that you mindlessly thought it was a good idea to restore bricksafe.img. That's not how it works.
If you just flash that without knowing what you're doing, you're more likely to cause issues than fix anything..
The downgrade could have been handled by just doing (having previous blobunpack'ed a stock ICS rom):
Code:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
There's no reason to do anything more. There was a reason we held back how to do full brick recovery - when used wrong, it just makes recovery a lot harder, and in general, people use it wrong.
Click to expand...
Click to collapse
Yes, of course, how mindless of me not to know those commands but now I can run them. But wait, I just remembered, I already successfully downgraded to ICS 2 months ago using the mindless method. Incidentally, I never said it was a good idea but rather it was the only idea someone as mindless as me could come up with. How could it possibly have worked? I just got lucky I guess.

tobdaryl said:
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/showthread.php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/showthread.php?t=1068548
UI for blobtools - http://forum.xda-developers.com/showthread.php?t=2012033
Click to expand...
Click to collapse
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?

uumeshh said:
well after booting into nvflash i used follwing commands
nvflash --resume --read 4 blob.EBT
nvflash --resume --read 10 blob.APP
nvflash --resume --read 6 blob.LNX
nvflash --resume --read 5 twrp.img
can these files be used later to downgrade to this paticular ROM from which the files are generated?
Click to expand...
Click to collapse
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.

tobdaryl said:
Yes that is the purpose according to rayman's above post. At least that is the way I see it.
Rayman is the DEV who posted the origional Nvflash thread.
Click to expand...
Click to collapse
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !

hunterr986 said:
When ever i use the above commands i get these error messages ... can you help me unbrick from APX mode .
Nvflash started
[resume mode]
failed executing command 18 NvError 0x30012
command failure: read failed
For all the commands .. i extracted them from blob file using BlobUnPack.exe tool !
Click to expand...
Click to collapse
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.

tobdaryl said:
Can I assume you have previously installed nvflash and have your files created at that time? If so I'll try to help otherwise apx is useless.
What asus firmware blob did you use with blobunpack? If it was a JB blob do not flash the ICS twrp recovery!
wheelie -r --blob blob.bin -created with Nvflash install
nvflash -r --download 4 blob.EBT -created with blobunpack
nvflash -r --download 10 blob.APP – created with blobunpack
nvflash -r --download 6 blob.LNX – created with blobunpack
nvflash -r --download 5 recovery.img-ICS twrp recovery image name when using blobunpacked ICS blob
nvflash --resume --go
Notice I have added a command to the beginning of the info posted in this thread. In this thread we took what rayman posted as literal but it appears we need the first line to boot into nvflash before giving the remainder of commands.
Also if you look at my signature you will find a thread relating to nvflash which may contain some info not presented in this thread.
If you get the same error tell me which command you typed to get that error.
Click to expand...
Click to collapse
Thank you for your reply.
I have a TF300T !
Unfortunately i do not have the blob.bin . I did not create it while unlocking my device.
So after unlocking my device my friend tried to flash a rom buring which he wiped out everything, flashed and rebooted. After which it got stuck in an infinite bootloop at Asus Logo.
I can get into APX mode so i did a lot of research and realized that i dont have the blob.bin !
so i am trying every possible tutorial before declaring it as bricked.
Is there a way i can unbrick it ? The main problem is that it doesnt have fastboot or adb access.
PS: I came across a petition on the internet asking asus for giving access n all ... I am assuming its for letting people like me without blob.bin to unbrick theor devices ! Am i right ?

[Q] Acer A200 Brick

Unlocked Bootloader // Rooted // Twrp Recovery
Was flashing new rom clicked DEV/ Cash Clean.. tablet got stuck.... next thing i know its Bricked.... Only Led on power and black screen.....No Factory rest, Recovery, Fastboot, reset button..... only APX mode.
** Did all the study about A200 which way less than A500.
1st day on Windows: blackthund3r_A500_APX_Flash_Tool_v0.4.1; SBclaculator,
Found my UID by Twrp recovery ... to make use used
USBDEVIEW... same Uid: 0a70704341014157 { yeap there is a letter in the uid}
Used SBCal got SBK : 0x42A16F00 0x476FC701 0xFB032103 0x01022103
Used next tool: V8-UNL-ICS-HC-bootloader-MULTI-cwm..... no luck permission denied...
2nd day; Linux didn't need any extra driver automatic Nvida on Usb list
Used apx.c code to make sure the uid. which was same : 0a70704341014157
so Next nvFlash
./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x42A16F00 0x476FC701 0xFB032103 0x01022103 --sync
:::::::::::::::::::::::::::::::::same result Access Denied................!!!!!!!!!
I am pretty sure A500 SBK is Different than A200 because it has a letter......
Also (--odmdata #) has to different than A500......
So question is HoW to find --odmdata for A200?
And SBK is it different from A500? How can i get my SBK??