Ok, so my phone is stuck trying to install the damn OTA update even though I rejected it. It apparently self downloaded a few days later. I'm running an XDABolt ROM, can't remember which, but it's basically stock Sense just debloated. When I power the phone on, it boots up, but then power cycles a few seconds later and tries to install the update. It freezes a few seconds into the cycle. Is there anything I can do besides wiping the phone? And will wiping it even work? I neglected to do a backup in the last few weeks, and I'd rather not lose any of my changes since my last backup.
Thanks for any help.
Nevermind, I bit the bullet and just factory reset, seems to be OK now.
Thanks anyways.
Related
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.
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
downwardzspiral said:
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Maybe give flashtool a go, just flash one of the stock firmwares.
Already tried that. As stated before, it gets to the first screen which prompts me to chose a language, and then immediately reboots
I want to make sure I have the proper partitioning and such for the newer ROMs since I had not done the OTA, I just flashed the JB rom when it first came out.
So I just spent the last hour using LGNPST a few times.
Here is what happened. This was my first time using LGNPST.
Putting the phone in download mode was simple. I selected the .dll and then the 20j.bin
It got to 67% and the phone restarted. Then it gave the message at 85%.
I look at the phone and nothing seems to have changes, my wallpaper is the same and it looks like everything is there. I figured this would clear everything and I would be starting fresh.
So I tried it a couple more times with the same result. I even restated my PC and made sure nothing else was running.
I thought I might as well go back to 10o then. I selected it, again at 67% the phone restarts, but now it's got the old splash screen and hangs at the end of it. I let it sit and sit, restart it a few times all the same, it hangs after the splash.
So I do it one more time back to the 20j. 67% and it restarts. Now it boots there is a screen that said updating apps. Now it seems I am back to the stock JB I had before w/ my custom wallpaper and apps all there.
How do I check and see if it worked and I have the proper partitioning to try out the 4.2.2 ROMS?
Well looks like it must have worked.
All the AT&T apps I had frozen with TiBu are back, and when i open TiBu it can not find root.
I still thought that using LGNPST would wipe it clean. Guess I was mistaken.
Re=rooted w/ the new universal root and running FreeGee now.
I rooted my GS4 a few monthes ago and when i try to do a system update it restarts the phone, goes into recovery and begins installing the update. About a quarter of the way though it says "error" and aborts. This happens every time i try to update. Last night i attempted to unroot in SuperSU, restarted the phone and tried to update again. Still giving me the error. Also this morning the phone is generally laggy especially while typing (odd because not is much running) and texts take 10-15 minutes to send. Can someone help me i forgot a lot about rooting since i did it a few monthes ago and would appreciate some assistance. thanks!
willystylee1 said:
I rooted my GS4 a few monthes ago and when i try to do a system update it restarts the phone, goes into recovery and begins installing the update. About a quarter of the way though it says "error" and aborts. This happens every time i try to update. Last night i attempted to unroot in SuperSU, restarted the phone and tried to update again. Still giving me the error. Also this morning the phone is generally laggy especially while typing (odd because not is much running) and texts take 10-15 minutes to send. Can someone help me i forgot a lot about rooting since i did it a few monthes ago and would appreciate some assistance. thanks!
Click to expand...
Click to collapse
Umm... 4.4 doesn't exist for the phone. Otherwise, check any one of the MANY thread about the 4.THREE update that are around. Try to just use the no-wipe Odin image. Root is never guaranteed.
willystylee1 said:
I rooted my GS4 a few monthes ago and when i try to do a system update it restarts the phone, goes into recovery and begins installing the update. About a quarter of the way though it says "error" and aborts. This happens every time i try to update. Last night i attempted to unroot in SuperSU, restarted the phone and tried to update again. Still giving me the error. Also this morning the phone is generally laggy especially while typing (odd because not is much running) and texts take 10-15 minutes to send. Can someone help me i forgot a lot about rooting since i did it a few monthes ago and would appreciate some assistance. thanks!
Click to expand...
Click to collapse
There are no data wipes orginal odin images over in android dev. Usually trying to update while rooted will fail. There is a guide as well in android dev for updating to mj7 and keeping root.
Hope this helps.
Sent from my SCH-I545 using xda app-developers app
So it has been a VERY, VERY, long time since I attempted to root a device. I admit, that I completely forgot most of what I knew from back in the day rooting like the Motorola OG Droid. Here's the deal. I tried rooting a USC XT1526 and I had no idea what I was doing. I followed the steps through and managed to install TWRP and SU. So I assume I got full root. Well The issue started after I got an UPDATE AVAILABLE message and tried to go through with the OTA Update. When it got to the point of installing the OTA Update, my device turned off like normal but instead of updating, it booted into TWRP recovery. It didn't update at all and when I booted my phone normally, it kept trying to update so my phone turn off (loop) every time it tried to install the update. I did a factory reset and it stopped rebooting. I later tried to flash back to fully stock but I believe I might have downloaded the wrong file because I now have a device with no WiFi. Can someone please help me.