So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
Related
First time I'm posting so hey.
I just bought a HTC Hero today and decided to load a custom ROM onto it.
I flashed it fine, and installed modaco earlier (file name: 2.8-update-hero-modacocustomrom-core-signed).
So when I powered it back on, it looked like it worked fine, but I must of went wrong somewhere.
The phone will boot up, stay on for like 5 seconds, and then restart. When it comes on, I can't do anything cause it freezes on the lock screen then just restarts.
I'm pretty sure I messed up by putting that ROM on a t-mobile UK Hero(which I unlocked). I aint sure as I'm only new to this.
Any advice on how to fix this?
did you do a phone wipe before installing the custom rom?
I formatted the SD card.... I think before I flashed it.
Then just put the ROM on the root of the SD card.
See it looked like it done everything fine with the ROM.
I held in the home/power buttons, loaded the boot menu.
I did a "Ndroid back up" (did I spell that right) - so I could restore in case something like this happened (which I did, since I need my phone lol), then picked "SD Choose", picked the modaco ROM and it seemed to install fine. Took a few minutes. Install complete. I rebooted the phone.
Then it loaded the normal boot screen, and would literally last only 1 second and freeze on the lock screen saying no signal, then it would reboot. And loop this pattern.
Neo-Dragon said:
I formatted the SD card.... I think before I flashed it.
Click to expand...
Click to collapse
A wipe has nothing to do with the SD card. It is essentially resetting your phones internal memory back to "factory" defaults. I take it you have a custom recovery image, as you mentioned making a Nandroid backup - you will find an option to wipe there.
Regards,
Dave
So if I wipe the phone before hand and then upgrade it should be fine?
If I do a nandroid back up, will I still be able to roll my phone back if it fails?
A wipe now may fix your problems with you needing to upgrade again.
My suggestion would be trying this first - if it doesn't help, restore your nandroid backup, wipe, and apply the new ROM again.
Regards,
Dave
Cheers mate.
After the wipe, I re-installed the ROM and it works perfect.
Thanks again.
I used the 1 click toot method and thought I may return my fascinate. I decided against it and tried to root again with no luck. The root always has a bunch of FC's and eventually gets stuck. The generic ringer also starts with no way to stop it. Only a battery pull will restart the phone afterward. I have also already really installed the Samsung drivers for the phone. Anybody have any thoughts?
Did you go back to stock via odin...if not do so...and push root manually...instead of an app.
I did through Odin. Tried to push root manually last night. The phone froze right after the push and never recovered. Had to battery pull. I had all of the files pushed and got to the chmod and wait stage when it froze.
Hmm, maybe re push to stock in odin...make sure you are doing the correct files...though it sounds like you did...a second time around sometimes seems to hit the spot...droid used to give me the same issues with sbf.
Do a factory data reset after you redo the odin recovery. Make sure you are using the verizon file when pushing each flash and doing it in the proper order. Then manually root, dont use one click or an app.
Also remember to push the files one at a time and let the phone restart between each one booting back into download mode.
Sent from my SCH-I500 using XDA App
I've been working all weekend so I havent had too much time to deal with it. I wiped data and cache in the recovery menu initially and then the phone wouldn't allow me to sign back into my Google account. It kept telling me that I didn't have a data connection on 3g OR wifi. I finally did a factory reset through the privacy menu (not in recovery) and all seems to finally be working and completely stock. Now off to root and flash voodoo...
hey i had the same problem i made a post on how to fix it though.. go to the 0.00 internal storage issue mine was doing what u said plus more but i fixed it just follow the steps i set
http://forum.xda-developers.com/showthread.php?t=804457
Got it. Just for the record: Rooted, Flashed all three files with Odin to get "back to stock". Re-OTA'd. Somehow Busybox and Su were still there so I manually removed. Then changed my mind about returning the phone and attempted to root again with no luck. Re-flashed through Odin ok, then attempted root but errors prevented finish. Cleared data and wiped cache through recovery. Then my google account wouldn't resync b/c of network connection error, even though I had a working data connection the entire time. Tried booting into recovery and clear and wipe data again. No luck. Finally decided to use factory data reset from within settings. Now all clear, rooted again, re-synced my google account and all good. You guys rock. Thanks for the help.
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
PieceKeepr said:
I tried to run a kernel tweaking script and ended up screwing the phone up. I have wiped and re-flashed several times but I keep getting Android layer restart loops and I have to pull the battery. Is there any way to actually wipe the phone and get a truly "clean" install?
I read some stuff posted by bftb0 but I'm not sure if any of it applies to my situation. Can I use the ErisMTDNuke zip if I have never used Clockwork?
I have RA Recovery and the S-Off bootloader (1.49.2000). I can get into recovery with no problem it's just that flashing the ROM again is not fixing the problem for whatever reason.
Click to expand...
Click to collapse
Try Wiping Everything, then Boot up your phone Without the Sdcard!
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
PMGRANDS said:
Try Wiping Everything, then Boot up your phone Without the Sdcard!
Click to expand...
Click to collapse
I have wiped everything that Recovery will allow me to wipe. I have not pulled the SD card though.
MongooseHelix said:
How far does the phone get before it loops back? Are you able to use adb to get a logcat of what's going on?
Some things to think about trying if you haven't already:
* Flashable Stock ROM - March 2011 OTA - keeps custom recovery
* Flashback21 v2 - March 2011 OTA - reverts to stock recovery
* Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP - April 2010 - rename to PB00IMG.zip, flash with bootloader
Click to expand...
Click to collapse
It varies actually. Sometimes it will boot all the way but when I do a function or two, say bring up the keyboard, it will reboot. Other times it will boot to the lockscreen, but then reboot and go into a loop. And sometimes it will never make it past the boot animation before looping.
I did try flashing another ROM I had on the SD card, xtrROM, then wiped cache and data before flashing GSB again, but no joy because it still happens. I'll try these and see what happens.
PieceKeepr,
It sounds to me like you might be overclocked too high...we have seen some phones in the past that used to run okay at higher speeds but no longer do...
If you can get to the overclocking / setCPU settings, try backing your clock-speed down from where ever the phone is booting-up or running at.
You could also test this by flashing the stock ROM that I see a link that MongooseHelix posted above since that should run at 528MHz (i.e., the one that retains custom recovery).
Worth a shot anyway (make a Nandroid backup, then wipe and flash the stock ROM and see how that behaves for a little bit...might shed some light on if overclocking is the issue).
Cheers!
It definitely was not an overclocking problem.
Tentatively I think I have it fixed. I flashed the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP then rooted again. Wiped dalvik and data and flashed xtrROM to see if it booted OK and it did. Wiped dalvik, wiped data and deleted the android.secure folder and flashed GSB. Everything seems to be working great.
The only downside is I lost my S-Off bootloader but I can fix that later. The upside is that my phone has not been this responsive and snappy in quite a while. I don't know if the IMG file is responsible for that or if it's the fact that when xtrROM loads it says it formats boot, system and cache.
I noticed the performance increase briefly the first time I flashed xtrROM then GSB but it crashed and started looping when I tried to install and set up an app from the SD card. After the process outlined above I again installed the app (Swiftkey) but when I tried to configure it the setup started looping. This was a problem encountered by many a while back and was determined to be a corrupt file. So I uninstalled the app and installed the newest version from the market even though I don't like it as much as the older version.
I'm gonna leave this open until I'm comfortable that it's fixed. Thank you all for the input and a huge THANK YOU to MongooseHelix!
As a side note I followed these instructions to get the S-Off bootloader... http://forum.xda-developers.com/showthread.php?t=725047 ... and I'm wondering if I actually have to do the whole thing again. Can I flash the PB00IMG.zip and get the S-Off bootloader again or should I do the whole thing?
Two days and not a single problem, so I thinks it's safe to say it's fixed. Thanks again for the help.
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
how did you solve your problem? i'm in the same situation
irafcummings said:
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
Click to expand...
Click to collapse
what information did you recover?the info might mismatch because the roms differ.Also try flashing a new recovery like cwm or AmonRa
Also if you restored the system directory when you did a restore, its like building two houses on top of each other, its 2 full houses, so both will crash because of the pressure. It probably just installed the system restore on top of the update, did you do a data wipe? Furthermore, if you look in the folder with your backup data, your should only restore the data portion rather than doing a full phone restore! so in the future, do a full wipe before reporting, and also, store the backup in a remote area, but put your data folder back in the original location and install it!
Sent from my PG86100 using XDA App
I ended up flashing CWR via an SBF file. It seemed like CWR just got corrupted somehow. From that point, I was able to restore from the nandroid that I created prior to updating. Hope that helps.
I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse