[Asus  Eee Pad Transformer Prime] aamcc:
I'm relatively new to the process of rooting and flashing so please be gentle senpai. Overall, my question is, how do I get either restored to my back-up, or to a better cleaner ROM. What motivated my tampering was that bluetooth wasn't working in Cyanogenmod 10.1

I received a TF201 tablet from my brother who is fairly experienced with the process of flashing roms and working in the world of rooted devices. He lives a while away so to have him look at it with me is a challenge but I've discussed the status of the tablet with him and he's hopeful that there's a solution.

When I received the tablet it was running the following:

Cyanogenmod 10.1 (according to the settings)

twrp 2.5

JB bootloader (at least this is the best I can conclude since the nvidia insignia is in the bottom right at the splash screen.)

As a side note, when I'd power on while pressing the down volume, in order to get to fast boot I had to select the USB signal option. This changed later. (unsure when.)

The status of the tablet now seems to be (emphasis on seems since I've tried many things while attempting to get a working rom) the following:

Successfully ran restore back-up to Cyanogenmod 10.1 (success being that it ran the data and seemed satisfied when completed with no error codes or issues.)

Running Hairybean 2.31 and twrp 2.5 ( I think, not sure how hairybean fits into the functionality of the recovery but the whole UI is hairy still.)

JB Bootloader (again because the bottom right nvidia)

Fastboot is default and only 3 selections available in recovery mode. While on this screen at the top left it says "Key driver not found . . Booting OS.

When trying to boot to the restored back-up I get a regular ASUS logo with nvidia symbol at bottom right, and "the device is unlocked" at top left. This screen sits for a moment, then goes black (as if it's trying to do the right thing) and then the screen returns and the tablet stays there indefinitely.

In recovery mode, when I select "mount" I'm able to see that "system" has a red switch (so it's not mounted.) I can turn it on, and it stays on persistently while in the recovery mode, but when I've attempted to reboot the tablet either to the ROM or directly back to recovery, the "system" is unmounted again.

This is a summary of what I've done to the tablet, at first I was just trying to get the katkiss ROM according to the thread referenced below. After a few steps I realized I was in trouble and started trying to fix the tablet with anything that would work.

http://xdaforums.com/transformer-tf300t/development/rom-t2817919

Here is the log I made of what I did to the tablet. Maybe something here will explain the issues I'm having.

It's not completely comprehensive since I realized too late that I should have documented everything I did.

Backed up in TWRP

Flashed Hairybean http://xdaforums.com/showthread.php?t=2407248

Updated TWRP to 2.6.3 as suggested #543 http://xdaforums.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951

Tried to flash katkiss http://xdaforums.com/transformer-tf300t/development/rom-t2817919

When katkiss failed, tried grimlock kernal according to #543 http://xdaforums.com/transformer-tf300t/development/rom-t2817919/post56681951#post56681951

That seemed successful.

Rebooted to twrp recovery (password required)

Searched about password, clicked cancel, attempted to format data but failed.

Attempted to clear data through fastboot according to: http://android.stackexchange.com/questions/89182/bricked-my-tf300t-how-to-re-partition-internal-storage-to-get-it-back

Couldn't get any ROM to work

Decided to try from square 1 to get virtuous prime to work according to http://sitr.us/2012/05/12/installing-a-custom-rom-on-the-transformer-prime.html

Cleared data through fastboot in system, recovery, userdata, boot, misc, and cache.

Flashed clockworkmod

Flashed virtuous prime with fastboot -i 0x0b05 flash system

fastboot -i 0x0b05 reboot

Would not boot to OS, or recovery,

"key driver not found . . booting OS" at top left

After this, I again cleared data through fastboot system, recover, userdata, boot, misc, and cache.

I flashed the default ASUS TF201 kernel from https://github.com/namidairo/android_kernel_asus_tf201

Installed a twrp.blob that I got from a page flumpster recommended it (I can't find it now.)

Able to get to recovery, but received "unable to mount" errors whenever I did any formatting in the recovery mode.​

Thank you for your help. I'm open to trying whatever you think will work. I know this is a sensitive product and apparently prone to bricking but I'm really REALLY hoping that I didn't brick my new toy. I don't know if there are other diagnostic tools I'm not aware of that would give me a better read on what the status of my tablet actually is to try to pinpoint the issue or if the only way to do that is to clear everything on it and start over to be sure of what's running.

You guys are phenomenal. Thank you in advance.

aamcc