[Asus  Eee Pad Transformer Prime] fenixjn:
Hello, well this batch file saved my tablet from an 'Option 3' brick (cannot boot ROM but still have access to recovery and fastboot). Unfortunately, I could not find any help other than "go to the the IRC channel to see IF it can be fixed"... so since I had tried a similar approach on my first android device, the EVO and all that mess that was needed to root it, I decided to experiment with this batch file. I came from Baked ROM ICS, I don't recall the version but I am sure it was ICS.

The first thing to do was to download and unpack the blob file... yes, on that other thread it says 'do not flash the blob file because it will hard brick'... I kinda read that too late. I had already tried this batch file with the official blob.

Now onto the experience: the first thing I attempted to do was to run the batch file with admin priv on my W7 machine, it worked fine until I started to flash the blob file itself... it would eventually say writing... FAILED: (), and then reboot... and back to the cannot boot ROM.

I decided to open the batch file and found these two lines:

fastboot -i 0x0b05 flash staging system.blob
fastboot -i 0x0b05 reboot

Now, I decided to run the command manually from my command prompt... it took longer than it did while running in the batch file... I got my OK [xxx.x s] and then writing SUCCESS. But here is where it gets weird... how come running the command from CLI manually took longer as expected (since I was expecting a transmitting period and then a writing period) while running the same command from the batch file it failed? I have no idea... but basically... check your screen on the tablet. If it says something along the lines that it could not write to the device with red letters, CTRL+C the batch file and run the command itself manually, it might help (it did to me after running the batch file twice and running into the same wall)

Another thing I noticed on the batch file is this:

fastboot -i 0x0b05 erase cache
echo ******************************
fastboot -i 0x0b05 erase userdata
echo ******************************
[b]fastboot -i 0x0b05 erase recovery[/b]
echo ******************************
[color=green]fastboot -i 0x0b05 erase staging[/color]
echo ******************************
fastboot -i 0x0b05 erase system
echo ******************************
...
[b]fastboot -i 0x0b05 flash staging system.blob[/b]
fastboot -i 0x0b05 reboot
...
[color=red][b]fastboot -i 0x0b05 erase staging[/color][/b]
[color=blue]fastboot -i 0x0b05 flash staging recovery.blob[/color]

From what I understand here: the green command erases the OS, then the black command flashes the new OS, but the red command seems to erase the OS we just put in and then the blue command just flashes the recovery where the OS was supposed to exist! I am not really sure if the 'staging' area is some kind of temporary memory but I did notice that after running the batch file I could no longer boot into RCK (because it was erased before... but it was supposed to be written to by the blue command... it does not happen). The command can be corrected as:

fastboot -i 0x0b05 flash recovery recovery.blob

This allowed my tablet to be able to access the recovery once again (at this point the previous fix for the OS had also worked, so I had JB on my tablet but no recovery).

I am not claiming to know more than OP in regards of how fastboot commands work (I have no idea with the -i 0x0b05 has to be there, but the fact that the command syntax allowed the erase commands to work means that it must be there), I am just posting my findings in how this batch file, combined with the blob file allowed me to get my tablet back to life from an option 3 brick.

To the OP: you have my thanks for the batch file, without it I would not have been able to get my tablet back.

(For those wondering what I mean by 'option 3' brick: I am using the convention posted here. Option 3 is considered 'you need one on one help to fix it')