Brick!
Hey guys,
I'm running into a CWM loop brick as well.
I'm not a stranger to flashing ROMs or Kernels in the past, as I've done it frequently on my SGS1.
But, after following directions on how to install AOKP for TF201, I ran into a CWM bootloop. Rooted the device, unlocked the bootloader, installed CWM, then installed the ROM. Tried to boot and was stuck in a loop.
I could not restore my back up that was created prior to the installation and cannot install another ROM.
I've tried going through most of the unbrick methods with no avail.
I can get into fastboot, Windows recognizes the device and tries to install a driver, mind you I'm using the naked drivers. But, in ADB the device is unknown when I do an adb get-state.
I have a sinking feeling that I'm doomed, but I'm just curious if anyone else has been here.
I just find it odd that Windows can still recognize the device, but ADB doesn't. When I go into CWM, Windows does not recognize the device at all and I have the same unknown state in ADB.
I've tried the WSG Unbricker and since the adb state is unknown, it can't push the files over.
I'm hoping for a reason to hope haha, but I think I'm done for. Just looking for confirmation.
Thank you.
Update: I'm able to push the recovery image from WSG to my tablet, but I can't get back into it now. If I try to push any other files I get an error:
sending boot...
writing 'boot'
FAILED (remote: (BadParameter))
finished. total time: 0.873s
On my TFP it says: Failed to process command flash:boot error(0x4)
Anyone know why I would get this?
**************************************
Anyone receiving this error, please read the next post #268 (Swiftks) (this resolved my issue).