Think I may have bricked my prime? - Asus Eee Pad Transformer Prime

I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?

geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.

McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)

geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer

Related

[Q] Need Help...Soft Brick

Yesterday I tried to flash AndroWook Hairy Bean 1.4 using TWRP v2.2.2.0. The flash said it was successful, but upon booting up the device hangs at the Asus splash screen (the one with Eee Pad on it).
No errors are encountered on this screen. It just says, 'The device is unlocked'. I am able to access TWRP still and have tried flashing another ROM, Energy's latest JB ROM. However, I receive the same results with that one also.
I was a moron and neglected to do a backup. I did wipe the cache, dalvik cache and factory reset prior to flashing, but I also selected to wipe the system and I think that is were I f'd up.
How do I recover? I am very dependent upon this device and any help would be appreciated.
BialyMurzyn said:
Yesterday I tried to flash AndroWook Hairy Bean 1.4 using TWRP v2.2.2.0. The flash said it was successful, but upon booting up the device hangs at the Asus splash screen (the one with Eee Pad on it).
No errors are encountered on this screen. It just says, 'The device is unlocked'. I am able to access TWRP still and have tried flashing another ROM, Energy's latest JB ROM. However, I receive the same results with that one also.
I was a moron and neglected to do a backup. I did wipe the cache, dalvik cache and factory reset prior to flashing, but I also selected to wipe the system and I think that is were I f'd up.
How do I recover? I am very dependent upon this device and any help would be appreciated.
Click to expand...
Click to collapse
what recovery are you using? I had this problem this morning for a couple of hours. What ended up fixing it was pushing this http://forum.xda-developers.com/showpost.php?p=34359560&postcount=5497 via fastboot and using the new twrp to flash the rom. my twrp was not getting the job done. I wiped data also with the new twrp. No problems after that.

[Q] Keeps booting into Clockwork Recovery instead of CM

So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Try this
SarahAnne said:
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
Click to expand...
Click to collapse
Try this : http://www.mediafire.com/?4s77jvehqvsuruu
1)Download it
2)put the files ( flashing.boot Mlo etc...) on your sdcard,
3)completely turn off your nook ,
4)put your sd card on nook and turn it on.
5) press the ''N'' button when you see ''cyaogenboot'' (it also saids press ''n'' button for BOOT MENU)
6) in Boot Menu just choose option #1 (Internal Boot) it should boot into cm10
I had the same issue, but after a time (after making some supid things) i bricked my tablet, I figured this out with some help, It worked for me so it should work for you too.
So I was able to randomly boot into the bootloader and boot into CM but now it keeps rebooting into clockwork.
I have also attempted installing CM10 using the following link including using the flashable_fix_bootloop.zip that I cannot sadly can't link to due to being a new user
and the only difference is that now CWM went from blue accents to orange.
The function of flashable_fix_bootloop.zip is to reset BootCnt counter and BCB flag (see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1) in the event they do not get reset properly in some installation/recovery process. It seems that your "recovery boot-loop problem" might have a different underlying root-cause, hence re-setting these counter+flag by itself will not cure the problem.
Which particular build version of CM10 and AOKP ROM did you try?
Also, did you do "wipe data & factory reset" & "wipe cache" as part of the ROM installation?
Have you tried reflashing the ROM once you're in CWM? (As I underestand you may have, but just making sure!)
Maybe download it again (or try another one) and the flash it again (after the usual wipes) with your new recovery.
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
SarahAnne said:
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
Click to expand...
Click to collapse
When you boot from the SD card have you tried holding down 'n' to get to the menu then selecting SDC boot? It should boot cm10.1. Try selecting SDC recovery also and see what it does. You might be doing something wrong during the process.
You can also try renaming your boot file for cm10.1 to altboot. Then try it.
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
SarahAnne said:
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
Click to expand...
Click to collapse
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
DavDoc said:
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
Click to expand...
Click to collapse
6.0.3.1
SarahAnne said:
6.0.3.1
Click to expand...
Click to collapse
Still may be a shot in the dark, but try downgrading CWM to an earlier version, but not so early as to be unable to flash CM10. Maybe 6.0.2.5 to 6.0.2.9
Not ensuring this will work but it may be worth a shot. At least it won't put you in any worse condition than what you are in now.
Good Luck
Another thought, did you make a backup of your last ROM before flashing CM10? If you did I would assume you tried flashing your backup already, but have to ask.
It looks like you may have used two different builds of CWM based on one of your earlier posts - change of font color.
You also try the repart image if you don't have a stock backup. Find it on raywaldo site. It will re write your internal storage with stock ROM. Then flash cm afterward.
Woot I got the factory rom reinstalled, time to install cynogenmod again
I had the same problem
This worked:
digixmax said:
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Click to expand...
Click to collapse
However I was still unable to install any 4.2.2 ROMs + gapps.
I was on cwm 6.0.2.8 (or whatever the exact numbers are)
updated to cwm 6.0.3.7
wipe data
install rom
install gapps
wipe cache
wipe dalvik
everything works now.

[Q] Issues after switching to cwm from twrp

Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?

[Q] Boot Loot -- Help!

Here's my situation--I had been running MeanBean for a while and decided to try Kush's KK build (http://forum.xda-developers.com/showthread.php?t=2518211&highlight=loop). I flashed the recovery he linked to, then installed the rom and gapps he linked to. TWRP said everything went successfully. But, when I reboot, the phone just hung at the HTC splash screen. I tried flashing again, downloading fresh and flashing again, wiping the cache, etc. Nothing worked.
So, I decided to go back to my last nandroid of MeanBean. But, after TWRP "successfully" recovered to the latest nandroid, I got stuck in a boot loop. The phone gets through the first part of the boot animation, then freezes and reboots. I tried installing a fresh version of MeanBean, flashing back to TWRP 2.6.3, but nothing has eliminated the boot loop.
I'm s-off and I've never gotten stuck like this before. Anyone have any thoughts?
Reboot to the bootloader and run the command "fastboot erase cache" from a command prompt, then try a fresh install. Are you sure you're S-off?
Sent from my HTC EVO 4G LTE
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
tbhtjd said:
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot image from the rom? You shouldn't need to if you're s-off but couldn't hurt if you're still getting boot loops.
Sent from my EVO LTE
Thanks, Fin. I tried fastboot flashing to boot.img separately (which shouldn't be necessary with s-off) after a fresh install, and I'm still in the boot loop. Any other ideas?
Go to recovery, do a full system wipe (data, system, Dalvik & cache) and re-flash the ROM after a fresh download. Really, though, you shouldn't have to wipe cache, since it's under /data.
Sent from my HTC EVO 4G LTE
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
tbhtjd said:
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
Click to expand...
Click to collapse
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Trying to flash MeanBean, which is what I've been using previously. I flashed the regular 2.6.3 Jewel TWRP.
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
fredgar75 said:
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
Click to expand...
Click to collapse
Hmm, don't think that's it. I've been able to mount internal storage and wipe the cache, etc. just fine.
I'm at a loss at this point as to what the problem might be. If you shoot me a PM I have one last option for you.
Sent from my HTC EVO 4G LTE

[Q] Brick with access to fastboot

So, I got annoyed with the speed of my 4.4 ROM and tried to install a new ROM. In the process of wiping davlik and cache, my TF201 hung and didn't do anything. After an hour, I hard rebooted it. Internal memory was totally wiped (including the ROM and Gapps, naturally) and I had to do a whole dance of trying to get the new ROM onto the SD card. After I did that, and installed a new ROM, it wouldn't install Gapps with an error saying it couldn't access the /data folder.
Even though the ROM install seemed to be successful, the tablet hangs on the splash screen ("unlocked" screen). I can access TWRP still, and I get a full fastboot menu.
Am I boned here?
markaments said:
So, I got annoyed with the speed of my 4.4 ROM and tried to install a new ROM. In the process of wiping davlik and cache, my TF201 hung and didn't do anything. After an hour, I hard rebooted it. Internal memory was totally wiped (including the ROM and Gapps, naturally) and I had to do a whole dance of trying to get the new ROM onto the SD card. After I did that, and installed a new ROM, it wouldn't install Gapps with an error saying it couldn't access the /data folder.
Even though the ROM install seemed to be successful, the tablet hangs on the splash screen ("unlocked" screen). I can access TWRP still, and I get a full fastboot menu.
Am I boned here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2409602
Where it says to get the TF300 official firmware get the official TF201 Jellybean instead.
Follow all the instructions and you should be back to stock with no recovery. Then install the official TWRP for the TF201 and go from there.

Categories

Resources