Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Alright, after bricking my phone yesterday and spending hours finally unbricking it, I've decided that I'm just not quite ready to play around with ROMs on the Transformer Prime. At least, not until they get a little more stable.
However, I'm finding myself unable to get my Prime back to stock ICS...
What I'm currently running is a Cyanogenmod 9 nightly build from 3/4/12. Through Rom Manager I was able to install the latest CWM (5.8.2.0) BEFORE the whole bricking incident. Now I can't even get my WiFi turned on...so I suppose any further changes via Rom Manager are halted.
Anyway, I used Vipermod's tool and was able to unroot successfully. I then went into settings and attempted to perform a factory reset. However, my tablet booted up with the same, Cyanogenmod boot screen and brought me back without any changes.
So then I tried using ADB....plugging my Prime in and typing "adb reboot recovery". But I get the message "adb server is out of date. killing..." then on the next line * daemon started successfully *. My device resets...but same thing...cyanogenmod...no CWM...no changes.
I thought maybe ADB wasn't working because I had unrooted. So I re-rooted, again using Vipermod. I see superuser again now...but ADB reboot recovery is still not working.
So now I'm stuck... I seemingly can't perform a factory reset with my build of cyanogenmod, and I can't find any way of getting back to recovery (I've tried selecting recovery reboot after pushing the power button, tried selecting recovery from within Rom Manager and tried with ADB...all failed). Again, all I want to do is factory reset, and get my stock ICS back. Can anyone please help me out?
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Diamondback said:
You won't get back a total stock ICS easily
You can't use Factory reset after unlocking the Prime and installing CWM
adb reboot recovery does not work
The only way to reboot to recovery is via holding down Vol_Down on boot and then pressing Vol_Up
non working wifi is because you have a wrong kernel
you can't boot to recovery because it's most likely wiped
Try installing CWM from Rom Manager again, if that does not work follow the guide in the dev section to flash another CWM version manually.
Then reboot to recovery and flash another ROM.
Make sure the ROM contains a new kernel, so your Wifi is working again.
Click to expand...
Click to collapse
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
scaryslocuda said:
Thanks again Diamondback!
To clarify, I don't really need stock ICS. What I need is a working ROM with Android Market (Google Play, WTF?), WiFi, a web browser...all that. I've heard that Virtuous is good, so I'll probably go that direction.
But more importantly, I need a way to install it, and the only way I know how to do that is a) using Rom Manager (which apparently doesn't work with the Prime at the moment), or b) doing it through CWM (which isn't working for me at the moment either).
As far as your suggestions go, I can't use Rom Manager to install CWM again, because my WiFi isn't working. However, I have found instructions online for flashing CWM manually, but it involves installing fastboot, and doing something with a "blob". I don't know what a blob is, but in your unbricking post, you specifically state:
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
I'm not sure if that applies in this case, but the last thing I want to do is brick my device again.
This is the post I'm referring to:
http://www.theandroidsoul.com/install-cwm-5-8-2-0-on-transformer-prime/
Can you advise whether this method is safe, or point me in the direction of a safer method for flashing CWM manually?
Thanks!
Click to expand...
Click to collapse
My warning only applies to STOCK blobs (like the ones in the official asus updates from their website).
The guide you posted seems to be fine.
Great! I'll give it a shot tonight.
One last thing... If I find that Virtuous isn't the best fit for me, would you advise AGAINST installing the stock firmware posted over at Android Soul? Is this what you would consider a "stock blob" or is this something different? Here is the link:
http://www.theandroidsoul.com/trans...h-cwm-recovery-on-unlocked-bootloader-primes/
That's a zip, not a blob, you can flash that
Diamondback said:
That's a zip, not a blob, you can flash that
Click to expand...
Click to collapse
Worked perfectly! Thanks so much for your help Diamondback...again!
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
are you referring the the stock rom offered by mycomputerdoctor? If so, the flashing does fail, but your phone will still work. From what I understand the only problem is the error in TWRP and you wont have root anymore.
My phone does indeed still work, but I wiped /system before trying to flash so I don't have a ROM installed currently and therefore cannot boot past the splash screen.
http://forum.xda-developers.com/showthread.php?t=1999962
docnok63 said:
http://forum.xda-developers.com/showthread.php?t=1999962
Click to expand...
Click to collapse
Unfortunately, that is an RUU, which does not work for me. Thanks, though.
install the rom, even if it says fails, it should still boot. you could also just adb push the updated rom on to your sd card.
Thrillhouse847 said:
Alright, so I wiped my phone in TWRP in preparation to flash something and I neglected to make a backup (I know, rookie mistake). The ROM I tried flashing will not go through and now I am stuck. I can boot into recovery fine but I really need a ROM to flash so I have something to boot into. I can't use an RUU (I have tried), probably because I used the bootloader unlock/root work-around. I'd gladly take any advice but I think what I need is just a flashable .zip of the stock ROM or maybe a backup I can restore in TWRP. If some kind soul could help me out, I'd be forever grateful.
Click to expand...
Click to collapse
Im in the same boat :/ stuck in recovery and have no rom to flash. going to try to adb the latest version and see how that goes.
I was afraid of something like this. We shouldn't be messing with our phones without a back to factory state.
I'm actually all set now. I flashed the updated stock, debloated ROM and made a back up so I'm good to go.
Sent from my HTC6435LVW using Tapatalk 2
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
xFoCaLx said:
I have a 4.1.1 Transformer Prime that I was finally able to unlock last night. After unlocking I followed this blog post to get nvflash setup and download all of my backups. Up to this point everything went smoothly.
After such I loaded CM 10.2 and Google apps on a flash drive to load the rom but even after many reboots Flatline would not see my microSD card. It would still boot to the stock rom at this point so I booted up and put the rom and apps on the internal storage and got back into Flatline. At which point I kept getting errors for mounting the internal storage. I loaded TWRP recovery hoping for different results but found that it asked for a password right away when going into TWRP. This helped me figure out that for some reason my internal storage was encrypted. After reformatting the internal storage I was able to load TWRP without it asking for a password. Since TWRP was already loaded I tried using it to isntall CM 10.2 and gapps. Install went clean but it would never boot the rom, just bootloop. At this point I had trouble getting back into recovery, it would just bootloop and ignore my Vol down press. Eventually using nvflash as an exit to the boot loop I was able to get back into recovery. I then tried to flash CM10.1 with similar results, no bootloop, just hang at the Asus screen.
At this point I decided to change gears a little and thought I would try Androwook after seeing all the posts about it. So I loaded up the files onto my microSD and and double read the post and loaded the Upgrade Hairybean 2.31 (4.2.1) Bootloader & TWRP (2.5).zip. After the blue bar filled and it rebooted I was presented with a signature failure error, bootloader 0x000..8. Very discouraging. Booted into nvflash again, but I was presented with a problem, which is very similar to the state I am currently in.
My bootloader is hosed, I cannot get to recovery, and I am unsure as to how/which file to use for recovery from the backups I made earlier. After some searching I found a post with the ICS bootloader linked. I downloaded it and loaded it through nvflash and now I am back to having access to fastboot and recovery again. However, the bootloader version is an old version, AndroidRoot 9.4.2.28. I searched some more and found a post that claimed the bootloader was AndroidRoot 10.4.2.15. I snagged it, loaded it up through nvflash but it wont let me into recovery or fastboot. I loaded a JB recovery through nvflash hoping it might help, but it didnt. So now I'm trying to get back to something I can use. Even a stock Prime is better than one that cannot boot roms. I tried loading Flatline recovery hoping to use it to load the JB bootloader again, but it doesnt seem to ever load in the ICS bootloader.
So currently I have nvflash working, the AndroidRoot 9.4.2.28 bootloader, with TWRP ICS 2.6.3.0 as the recovery. I am hoping someone can help me get this thing to a point where I can load a rom that works or back to a stock rom.
Click to expand...
Click to collapse
Fair play, at least you tried and you probably learnt a lot in the process.
You have nvflash backups so don't panic. It is fixable.
I am going to send you my google talk address now over PM. Add me by going to gmail on your PC in your browser and adding me in the bottom left hand corner to chat. I will try and talk you thru it.
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
puntxo said:
If you finally get to boot your transformer prime, would you mind posting here what caused all that mess and the steps you followed to solve it?
PD: Flumpster, I've been reading this forum for a week since tomorrow arrives my transformer prime, which i recently purchased on another forum, and I hope to unlock it, then run nvflash to backup the whole thing and finally install hairybean without any trouble. I would like to thank you for all the work you have done this far helping people to solve their bricks. I really appreciate the way you explain everything, it helps me understanding all this stuff. Great Job
Click to expand...
Click to collapse
This was a new one on me and I have no idea how he got himself into it but we managed to fix it anyhow.
He was the first person I have helped tho that needed to restore unlock-token.img, factory-config.img and bricksafe.img as he had some error saying failed to inject certificate, unrecoverable bootloader.
As long as you have all your nvflash backups you will be fine amigo.
Total newbie to all this. First time I've unlocked or rooted android.
I unlocked using the Asus unlocker. Rooted with motochopper. Then I installed fastboot and nvflash and flatline. Messed up here as I was planning to install CM11 and when I tried to install the ROM it failed. Should have read the small details. Soft bricked my tf201 and could only use apx.
Used nvflash to recover to stock jb. Re-rooted and tried to install CWM. Didn't work recovery would freeze in the loading recovery image. But I could still just boot normal into my device. Tried TWRP and had the same problem.
How do I get the recovery to work. Do I need to go back to the stock image and try all over again?
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
JoanneDisFan said:
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
Click to expand...
Click to collapse
Can you put SOLVED in the title of the thread..
Thx Josh