Database Info

[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!

TF101 Settings stopped working

I already had a try on this on another forum:
hxxp://www(dot)transformerforums.com/forum/asus-transformer-help/25176-settings-stopped-working-tf101.html
(can't post links yet)
I have a TF101G ( sn:C20KAS035896) from a friend, everytime he went in to the settings it says: "settings stopped working"
I tried a factory reset, (from stock recovery menu), got it to reset, but now i cant get through the "first-time-setup-wizard":
at step 3 it asks to connect to a WiFi network, I select one, it asks for a password, but when I enter it and press ok it says "Unfortunately settings stopped working". After a few seconds it starts again at step one of the wizard..
I figured out it is a WW version.
So, what do I best try next?
After reading some here, i guess I get a alternative recovery and use that to flash a new stock rom onto the tablet.
But could you point me to the right posts and methods, because I'm not sure which is the right one.

http://forum.xda-developers.com/showthread.php?t=1552303
Then this you were looking for ? It is with recovery 3.2.0.1 us or ww stock rooted full rom edition
good luck

It might be. It seems to be a link to a zip file. The contents looks like the contents of a standard firmware file. Only the blob part is much smaller, and there is a system folder which isnt in the standard firmware update.
But I don't know what to do with it..
I was thinking maybe wolfs method 3 could help me out?
hxxp://forum(dot)xda-developers.com/showthread.php?t=1622628
(can't post links yet)
But i'm still strugling with adb though..
When i run "adb devices" I think it should list my TF101 but it doesn't

After some more reading and trying, I've come to the conclusion I can't get adb to connect to the device.
I also have an android phone: a HTC desire, which I can get to connect with adb. But the asus is stuck at the "first-time-setup-wizard" (as I explained above)..
Though I can see the device in windows explorer (win 7 64bit), and the 2 mounted drives "Internal storage" and "SD Card"
I can get it into apx mode, but nvflash doesn't work for my version of the device its a TF101G sn:C20KAS035896
What could i try next?
I want to flash the stock rom, as mine seems to be broken, and I cant use adb
EDIT:
Just found out about wheelie, should that tool be able to do what I want?
androidroot(dot)mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
My device isnt explicitly listed, and EasyFlasher a tool based on wheelie says it doesnt work for my device.. So should it work or not?
Do I need linux for this? I cygwin ok?
EDIT2:
As I understand it, I probably have a Secure Boot Key that isn't version 1 or 2?
There is a sbk detection tool, but afaik it only works on mac, and I don't have a mac available..
I have tried the windows beta version of wheelie, and the output i get is the following:
reflash_sbkv2.bat
Code:
J:\TF101\wheelie>reflash_sbkv2.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --o
dm 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: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
And for the sbkv1 version the same:
Code:
J:\TF101\wheelie>reflash_sbkv1.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --o
dm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
Am I overlooking something here?
Should I get adb working with my tablet in its current state?
Or do I have to return the tablet to ASUS?

Same problem here
Hello frydac, I'm having the same problem as you.
Did you find a way to fix it yet?

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] Don´t boot data was deleted

Someone deleted the files from the tablet when I restart glue on boot, tried to recover with nvflash but is giving error
Using SBK type 2.
Using bootloader: '.\images\bootloader.bin'.
Using BCT: '.\images\transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299648565018420119
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
connection failed NvError 0x30011
Nvflash started
[resume mode]
connection failed NvError 0x30011
i need help please

acacioxda said:
Someone deleted the files from the tablet when I restart glue on boot, tried to recover with nvflash but is giving error
Using SBK type 2.
Using bootloader: '.\images\bootloader.bin'.
Using BCT: '.\images\transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299648565018420119
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
connection failed NvError 0x30011
Nvflash started
[resume mode]
connection failed NvError 0x30011
i need help please
Click to expand...
Click to collapse
sbk2 devices need to use wheelie, its a modified version of nvflash

JoinTheRealms said:
sbk2 devices need to use wheelie, its a modified version of nvflash
Click to expand...
Click to collapse
wheelie is close when i open

[Q] TF300T NVflash hellppp

Hi, I have a problem with my TF300T i have nvflash files when i try to back to live for the first time the device went like this:
wheelie - blob blob.bin - ok and showed the boot .
nvflash - resume - rawdevicewrite 0 2944 bricksafe.img - no problem
nvflash - resume - download 14 factory - config.img - , the tablet is rebooted since then only darkness
can enter the APX but how's command
C: \ 2 > wheelie - blob blob.bin
Wheelie 0.1 - Preflight for nvflash .
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode ...
[= ] Chip UID: 0x15d2d4221182412
[= ] RCM Version : 0x30001
[= ] CPU Model: Tegra 3
[+ ] Sending bootloader ...
[- ] Error 3 sending command
and sneezes as forests again
C: \ 2 > wheelie - blob blob.bin
Wheelie 0.1 - Preflight for nvflash .
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode ...
[= ] Chip UID: 0x100000001
[- ] Unknown error or incorrect RCM protocol version . nverror : 0x2 .
and the device turns off
maybe someone has an idea how to put the device to live

sw354 said:
Hi, I have a problem with my TF300T i have nvflash files when i try to back to live for the first time the device went like this:
wheelie - blob blob.bin - ok and showed the boot .
nvflash - resume - rawdevicewrite 0 2944 bricksafe.img - no problem
nvflash - resume - download 14 factory - config.img - , the tablet is rebooted since then only darkness
can enter the APX but how's command
C: \ 2 > wheelie - blob blob.bin
Wheelie 0.1 - Preflight for nvflash .
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode ...
[= ] Chip UID: 0x15d2d4221182412
[= ] RCM Version : 0x30001
[= ] CPU Model: Tegra 3
[+ ] Sending bootloader ...
[- ] Error 3 sending command
and sneezes as forests again
C: \ 2 > wheelie - blob blob.bin
Wheelie 0.1 - Preflight for nvflash .
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode ...
[= ] Chip UID: 0x100000001
[- ] Unknown error or incorrect RCM protocol version . nverror : 0x2 .
and the device turns off
maybe someone has an idea how to put the device to live
Click to expand...
Click to collapse
I've seen this before. what worked for some people was:
1.) reinstalling universal naked drivers
2.) using different USB port/cabe
3.) using Linux mint
4.) using ubuntu

cmendonc2 said:
I've seen this before. what worked for some people was:
1.) reinstalling universal naked drivers -no effect
2.) using different USB port/cabe -no effect
3.) using Linux mint -no effect
4.) using ubuntu
Click to expand...
Click to collapse
-no effect

sw354 said:
-no effect
Click to expand...
Click to collapse
If you tablet isn't completely bricked you could try this:
http://forum.xda-developers.com/showpost.php?p=47778415&postcount=8

no effect, always wheelie Error 3 sending command
wheelie -r -blob blob.bin nothing happens stuck sending btc

sw354 said:
no effect, always wheelie Error 3 sending command
wheelie -r -blob blob.bin nothing happens stuck sending btc
Click to expand...
Click to collapse
Forgot to rewrite bootloader:
http://forum.xda-developers.com/showpost.php?p=55638990&postcount=71