[Eee Pad Transformer Q&A, Help & Troubleshooting] mateorod:
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.

./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync

it formated a bunch of partitions and ended with this error

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:

mateor@mateor-HP-Pavilion-dv6700-Notebook-PC:~/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

mateor@mateor-HP-Pavilion-dv6700-Notebook-PC:~/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.

mateor@mateor-HP-Pavilion-dv6700-Notebook-PC:~/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
mateor@mateor-HP-Pavilion-dv6700-Notebook-PC:~/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...:p

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

$ ./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!