My phone is rooted using the process described here: http://forum.xda-developers.com/showthread.php?t=996616 . I was prompted for OTA v. 1.70.605.0 over the weekend. I initially rejected it but when I saw no one had complained here, figured it was ok to install.
When I accepted the install, the phone rebooted and I saw the screen with the android and the progress bar. After about 20-30 seconds the progress bar was replaced by the yellow exclamation point. I left it for a while but then figured it had failed. I pulled the batter and booted. the phone booted fine. However, after running for about a minute it rebooted to again try the ota install, which again failed. How do I fix this?
nevermind, looks like someone already asked about this: http://forum.xda-developers.com/showthread.php?t=1170688
I don't think your supposed to do ota updates if your rooted are you?
Sent from my ADR6400L using XDA App
yeah, that was my mistake... oops. Should have just installed a custom rom, oh well. Do you know how to undo what I've done now? I didn't find the magic zip file on the sd card your supposed to delete. Do I need to do a factory reset or something and start from scratch? there must be a way to just tell it to stop trying to install the ota.
Boot into clock work and wipe cache only.
Sent from my HTC Thunderbolt
Related
Looking for some help. Trying to install new update, but keeps failing with the android logo and a triangle with exclamation mark after attempting to install. Not sure what I hit but when taking battery out got the following screen. I was on 1.57 with gladroot. Had to sbf flash during the original update process some time ago as didnt get run scripts correctly first time through
Flash back to 26, then 57, then 83. Clean and fresh update is what you need.
Sent from WinBorg 4G using XDA Premium App
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
When the triangle and exclamation appears you don't have to take out the battery. Only touch the right low corner of the screen and the reboot display appears. I had the same problem at first but the information appeared indicated me what was the problem. Once corrected the update ran well.
logichoops said:
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
Click to expand...
Click to collapse
I've done it so many times myself now, but I like tinkering. The day I got beta I flashed back to 4.1.26 three times while at work before I ended up being successful with everything because I kept making "operator errors"! I planned for this and took my wall charger to work so I could boot into recovery. Took me over an hour each time to get fully updated! lol
Yeah, you have to flash to a clean version. Most likely you have a mod installed on your phone, and you can update with a mod on your phone.
Are either enabling sideloading or adding the tethering apn that gladroot does for you considered a mod? Just curious what I'm in for when I try to go from rooted 1.57 to 1.83 OTA
So, im trying to install an update that i received a notification for...i believe its the one that helps with 3g connectivity and what-not. But while trying to install it, I rebooted to a black screen with a ! inside a triangle and the little android standing next to it...what does that mean?
I let it sit for a GOOD long while, yet nothing happened. Does this mean i can never update?
***This has been solved. My last post in the thread says what i did.***
If you are rooted and you tried to do the OTA then you'll brick your phone.
i was rooted with stock. the OTA came up while i was texting and normally i hit reject, but i accidently hit ok while texting and now every time i start up, it says "Powering Down..."
Any OTA flashed over a rooted device will brick it, I believe.
Edit: Well I found this. May help.
http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Superthrust said:
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Click to expand...
Click to collapse
Glad to hear you're good to go!
Don't flash OTAs when you're rooted next time!
^_^_^
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.
MY TBOLT MUST DID THE OTA OR ATLEAST TRIED TO WHILE I WAS SLEEP NOW IT KEEPS POWERING OFF THOUGHT I HAD ROM MANNAGER TO RESTORE A BACK UP OFF MY SD BUT IT MUST DIDNT INSTALL AFTER LAST UPDATE I ONLY HAVE JUST THE PREMIUM LICENSE. I THOUGHT IT WOULD STAY POWERED LONG ENOUGH TO GO DL ROM MANAGER IN THE MARKET BUT IT WONT. I TRIED DL THE NEW OTA SO I CANN PUT IT ON MY SD AND FLASH HBOOT BUT IT KEEPS NAMING WITH THE .ZIP.ZIP EXT NO MATTER HOW MANY TIMES I RENAME IT WHAT CAN I DO I LOOKED HERE http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html BUT I NEED ROM MGR DO I NEED TO DL A STOCK AND UNROOT IT WHAT CAN I DO.... HELP PLEASE SAD PART I WORK FOR VZW AND I KNOW HOW THEY DO WITH EQUIP CHARGEBACKS
First, locate your caps lock and TURN IT OFF. Next locate your period key and put them on the end of your sentences. Making sense of your post is giving me a headache.
Now, on your computer you need to disable the "hide file extensions for known file types" option to fix the zip.zip problem. Can't give you exact directions since you didn't say which os you're using.
Sent from my ADR6400L using Tapatalk
Windows7 currently
I have the same problem and I tried to get in through the clorkworkMod adb shell, but the device is not recognized by adb...? When the device boots up it is recognized. with my DINC I could use the shell while in clorkworkmod.
Is it showing as device offline or not showing the device at all. If its offline, through cmd, close adb server, then start it back up, half the time that fixed that problem for me. If its not showing at all, try setting it to HTC Sync i believe was the one i had to do at one point for it to register. I've rooted 4 times using ADB method and each time its been a little different, so i can't narrow down what i'm doing wrong to help you more with the adb, sorry.
Similar Issue
Hi All and thanks to all the cats on here that willfully give their knowledge! I have a Tbolt - Rooted with Revolutionary, stock rom (removed VZ Bloat via Titanium ), but this latest OTA update is not leaving me alone. I try to reject it and magically a few days later I get out of nowhere reboot and then the android exclamation point with a triangle. I use the Clockwork Mod Recovery to wipe data cache and reboot which makes the update manager get upset saying it failed. The error I see in Clockwork is this:
CWM Recovery V5.0.2.1
E: Failed to verify whole file signature
E: Signature Verification Failed
Install Aborted
So how can I get this update (I am assuming it is to fix the HTC fail for new exploit out there) which I think would be a good thing. I am not ready to flash a custom ROM yet so please don't reply saying "Just flash with my favorite ROM"
Thanks ahead of time!
It pushes the update, and if you don't reject within 3 mins, viola, you have a nice new update. If you can still get into recovery, which it sounds you can, install a stock rooted either full or debloated. Thats the updated equivalent to what you have now. Make sure you grab the rooted though. Here is the full rooted (not debloated) http://www.multiupload.com/H06XI7W380
from this thread
http://forum.xda-developers.com/showthread.php?t=1312193
I'd probably wipe cache and dalvik cache, but you can probably leave data since you're staying stock.
Thanks for the direction nbdysreal!
So I might be the only person on Verizon who has this problem (I've researched all over the place). I have an issue that is driving me mad with this update. Yesterday, while at work, I was able to update to that preliminary update (the 14mb one) without issue. Immediately after the phone rebooted, I was prompted to download the 500+ mb Sense 5 update. Everything seemed to go well. The update downloaded, the phone rebooted, and started installing the update. Then, about a quarter through the update, the Red Triangle of the Stock Recovery appears, cutting off the update. Out of curiosity, I held up the volume-up and power buttons, and the Recovery Menu came up. On the bottom, where it describes the various processes going on, it says:
Verifying Update Package...
Installing Update...
Verifying Current System...
assert failed: apply_patch_check("/system/framework/apache-xml.odex", "ad2209bdf836715d79558f2fe9c0d474e655afb6", "671aa4acd71a88a36aa5774b9d5334e1a9373162")
Installation aborted.
I have tried everything. I wiped Cache, Did a Factory Reset in three different ways (from the actual OS, from the bootloader menu, and from the Recovery, and every time, the same thing seems to happen. I am effectively stuck on that preliminary update, with nowhere to go. Does anybody have any advice? The phone was never rooted, no S-Off, and the bootloader has always been locked. I'd rather not have to send this one in to VZW, as it was a replacement for a phone that had the SIM card error. This one has been fine for months, so I'm hesitant to get it replaced.
Same here
I am having the same issue. The only issue that I am having is with a book.apk file. Hopefully someone will have a solution.
We're either of you rooted to begin with? If so I believe the OTA update will fail.
Make sure you have several gigs of free space on the phone.
Apply update with full battery or mostly full with charger hooked up.
Or backup, root the phone and download one of the stock update images here on xda.
Good luck.
Sent from my HTC6435LVW using xda app-developers app
Stupid spell check correction
Sent from my HTC6435LVW using xda app-developers app
lsmaverick31 said:
So I might be the only person on Verizon who has this problem (I've researched all over the place). I have an issue that is driving me mad with this update. Yesterday, while at work, I was able to update to that preliminary update (the 14mb one) without issue. Immediately after the phone rebooted, I was prompted to download the 500+ mb Sense 5 update. Everything seemed to go well. The update downloaded, the phone rebooted, and started installing the update. Then, about a quarter through the update, the Red Triangle of the Stock Recovery appears, cutting off the update. Out of curiosity, I held up the volume-up and power buttons, and the Recovery Menu came up. On the bottom, where it describes the various processes going on, it says:
Verifying Update Package...
Installing Update...
Verifying Current System...
assert failed: apply_patch_check("/system/framework/apache-xml.odex", "ad2209bdf836715d79558f2fe9c0d474e655afb6", "671aa4acd71a88a36aa5774b9d5334e1a9373162")
Installation aborted.
I have tried everything. I wiped Cache, Did a Factory Reset in three different ways (from the actual OS, from the bootloader menu, and from the Recovery, and every time, the same thing seems to happen. I am effectively stuck on that preliminary update, with nowhere to go. Does anybody have any advice? The phone was never rooted, no S-Off, and the bootloader has always been locked. I'd rather not have to send this one in to VZW, as it was a replacement for a phone that had the SIM card error. This one has been fine for months, so I'm hesitant to get it replaced.
Click to expand...
Click to collapse
Try Running the 3.06 RUU here: http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
I rooted the phone before the updates. My phone's Software is 2.08.605.1 Android 4.1.1 and Sense 4+. Where can I download the new Android and Sense version for my phone without doing the OTA update?
Just look in the XDA DNA development forum, scroll down a little ways and you will see posts for the download. There are odex, deodexed, and superstock versions. I am running the superstock with no problems.
djautoclinic said:
Just look in the XDA DNA development forum, scroll down a little ways and you will see posts for the download. There are odex, deodexed, and superstock versions. I am running the superstock with no problems.
Click to expand...
Click to collapse
Thanks for the reply. I used "DNA-Super-Stock-Sense 5-3.06.605.4-v1.0" through Rom Manager and it worked like a charm. As far as I can see it will update OTA if Verizon actually sends out kitkat.
Thanks again.