[Asus  Eee Pad Transformer Prime] flueterflam:
I have come across several posts the are identical or very similar to my issue. However, I am having an additional issue which seems to be the cause of my not being able to unbrick. I'll try to provide enough details, but let me know if I missed something important.

My prime appears to be completely bricked, because I tried to fix another problem. When I tried to upgrade a stock ICS prime to JellyBean, I had many problems because the recovery kept error out with the droid guy with the red triangle and ! symbol. Somehow, I ended up actually do it and ended up with the US_epad-user-10.4.2.15.zip rom (US_epad-10.4.2.15-20120917). Because I am overseas, I had problems installing some things in the market and was considering root or a custom rom. At some point, I unlocked the device, which still displays clearly every time I boot. While look through several things that appeared very straight-forward, I ultimately ended up with a brick. The device is stuck on the splash screen. I have access to fastboot. However, adb doesn't recognize the device.

When trying to RCK (or wipe data) from the bootloader, I get:

Booting Recovery kernel image
Booting failed
[COLOR="Red"]Unrecoverable bootloader error (0x00000000).[/COLOR]

This post:

[Q] Transformer Prime possibly bricked. Help?

appeared identical to my current problem. The suggested use of universal drivers has not helped, however.

This post:

[SOLVED] Can access fastboot but can't get past splash screen

also appears identical...

These two also appears to provide hope:

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

[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)

...but ultimately, continue to evade my tablet.

Why? you may ask...

Well, it seems that I can boot into fastboot. When I manually run any command, it seems to work fine. But the prime becomes unresponsive to all subsequent commands. It requires that I force reboot and re-enter fastboot. When I try to run Urkel's Fresh Start, the wiping all runs smoothly, and the staging command

fastboot -i 0x0b05 flash staging system.blob

run smoothly. From that point, it becomes unresponsive again. It appears that although the flashing completes without errors, it doesn't take...or perhaps is inaccessible because the bootloader is jacked. Here's the output from Urkel's Fresh Start, for example:

Press any key to continue . . .
.: Now cleaning the TF201 partitions :.
erasing 'cache'...
OKAY [ 2.160s]
finished. total time: 2.160s
******************************
erasing 'userdata'...
OKAY [ 39.644s]
finished. total time: 39.645s
******************************
erasing 'recovery'...
OKAY [ 1.953s]
finished. total time: 1.954s
******************************
erasing 'staging'...
OKAY [ 0.948s]
finished. total time: 0.948s
******************************
erasing 'system'...
OKAY [ 2.208s]
finished. total time: 2.209s
******************************

.: Partitions now clean, continuing to reboot back into bootloader. Do not miss
selecting FASTBOOT with VOL+D and then VOL+U on the USB Icon. If you miss it no
big deal reboot back into FASTBOOT before continuing :.
Press any key to continue . . .
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s

.: Confirm you are in FASTBOOT before continuing to flash a fresh image/blob. Th
is will take 3-5 minutes because of the size of the image :.
Press any key to continue . . .
sending 'staging' (537604 KB)...
OKAY [ 94.723s]
writing 'staging'...
OKAY [ 1.329s]
finished. total time: 96.054s
rebooting...

finished. total time: 0.548s

.: No need to set up the tablet but let the tablet fully boot to welcome screen
then hold down the power to shut if off. When off turn it back on and enter FAST
BOOT. Once at FASTBOOT then continue :.
Press any key to continue . . .

It appears fine...however, it doesn't reboot, even thought the command said it was successful. So, I try manually rebooting and get stuck at the welcome screen again. It's a vicious cycle...:mad: Anyhow, this type of situation is the same for all of the other workarounds that I have found to this problem.

It seems that fastboot is semi-responsive, but no actions that I take are recognized upon reboot. I would love to try and figure out why fastboot is having these issues... and unbrick my tablet. So, please let me know if I have missed any threads that have exactly this solution (ie. fastboot works...but not really).

Thanks in advance, and let me know if I missed details that are necessary.