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.
Related
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
I have an unlocked AT&T Atrix running on another carrier (GCI of Alaska) that I rooted with WeaselyBreak (yes, that is a Harry Potter joke, I actually used GingerBreak). I have been trying to do an OTA upgrade to GB with no luck. I have not done anything with my bootloader. I have cleared the Superuser App data before the attempts as well as stopping it before one attempt. I went into Titanium Backup and unfroze all of my bloatware as well. Still no luck. I have downloaded the update four times now and everytime it gets ~25% through the unpacking screen before it changes to "Danger Will Robinson!!" android screen. And I have to reboot to a "Update Failed!" message.
Any ideas?
Banger_AK said:
I have an unlocked AT&T Atrix running on another carrier (GCI of Alaska) that I rooted with WeaselyBreak (yes, that is a Harry Potter joke, I actually used GingerBreak). I have been trying to do an OTA upgrade to GB with no luck. I have not done anything with my bootloader. I have cleared the Superuser App data before the attempts as well as stopping it before one attempt. I went into Titanium Backup and unfroze all of my bloatware as well. Still no luck. I have downloaded the update four times now and everytime it gets ~25% through the unpacking screen before it changes to "Danger Will Robinson!!" android screen. And I have to reboot to a "Update Failed!" message.
Any ideas?
Click to expand...
Click to collapse
Flash 1.8.3. SBF and try again?
If the update is failing that early it's probably where the update is checking to see if all of the 'system' files match up. You have something non-stock on your phone's 'system' files. It does not have to be bootloader related to throw that warning icon. Do you have swype beta installed? hdmi mirroring? webtop mod? If so you'll get the Android warning icon if you try to apply the update.
I haven't flashed before and was going to avoid starting (I hear it's hard to stop).
I finally gave up on the OTA route and wired my phone to my PC so that the Motorola website could have manglefication access to my phone. It did some stuff, my PC made a lot of noises (some of which my phone seemed to respond to), and
a few awkwardly erotic minutes later my phone looks vaguely the same as it did before. I say vaguely because it appears the update actually worked and it does look a bit different.
If it hadn't, I would have had to learn how to flash, which I understand may involve heavy drinking and a trench coat. I appreciate your response, but I have learned to stick to the adage my IT geek friends have taught me "Doing what is easy is not always right, but it is always easy."
Thanks!
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Dash_Skeezy said:
Earlier today i flashed a stock rom, locked my bootloader, and flashed the stock AT&T recovery in an attempt to recieve the 4.2.2 update. As i was checking for the update, a 13.8 mb update was downloaded, however when it tried to install, a red exclamation point came up. So i restarted and tried it again and no luck. So then i decided to run the RUU and start fresh and try again. However this time, the update is not being recieved. Any ideas or hints that you guys have?
Click to expand...
Click to collapse
Try to uncheck the automatic time in settings and put the tine 24 hour ahead. And try to get the update. Some claim it works this way.
Sent from my HTC One X+ using Tapatalk
Same for me
Having exactly the same problem. Made an account because i could not find an answer anywhere else. Just tried the time strategy and it did not work.
I do have the downloaded update file. Is there a way to install it through ADB and pushing, as can be done with nexus devices?
Thanks
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
matt135353 said:
Hello all, and thanks in advance for your help. I don't know if all of this is relevant to what happened, but I'm including it in case there's some small clue.
My phone was an S-OFF running HBOOT 2.09. I have been running Deck's CM builds for a while now with no issues. Last week, I decided to update to the new firmware which included the new partition layout.
HTC's RUU executable did not work, so I used the two zip method in this post. I first renamed rom_01 to PJ75IMG.zip, placed it on the SD card, rebooted and installed, then did the same with rom_02. Loaded everything up, seemed great with the stock image. After verifying everything was working fine, I flashed a new recovery (2.7.0.0b, via PJ75IMG.zip as well), and installed the latest OmniROM (3/31) via recovery. I had some issues with the PA 0-Day GAPPs that were recommended (force close errors with Google Keyboard) so after reflashing Omni switched back to the 12/09 GAPPs in Deck's thread. Everything seemed great.
A few days later, after having the phone in my pocket, my screen turned into a rainbow of pixels. Here is what it looks like: http://imgur.com/9ef6F8z It still seemed to work, just the screen was always that rainbow.
Thinking it was an issue with the firmware, I tried to RUU back to a somewhat earlier stock by using ViperRUU 3.16.651.3. However, after going through the RUU process, it had gone about 30-40 minutes with no updates, so I thought it had crashed. I checked to see if that was normal, and saw that it was not and they recommended restarting the process. I restarted both the ViperRUU (couldn't find phone anymore) and the phone, and now I think my phone might be totally bricked.
When I turn it on, there is nothing on the screen. It vibrates once, like it's trying to start, but nothing happens and the phone is otherwise unresponsive. I can try to boot into the bootloader (volume down + power) and that SEEMS to work, but the screen doesn't turn on then either. Occasionally, it will display the same rainbow pixels after "selecting" an option on the bootloader menu (I'm assuming). I've also pulled the SD card to insure it's not trying to read any PJ75IMG.zip.
I can't seem to get it to go into fastboot mode (single power button click after thinking I'm in the bootloader) and adb only shows the device as OFFLINE when I can get it to detect. It's hard to know what's going on without the screen.
Has anyone heard of this before? I probably ****ed something up but other than ending the ViperRUU early, not sure what. Thanks in advance, I very much appreciate it.
Click to expand...
Click to collapse
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Evolution_Freak said:
This is a known hardware issue. Look here:
http://forum.xda-developers.com/showthread.php?t=2470296
It happened to me as well. I called Sprint and they replaced my phone for no charge.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmm...I bought mine secondhand and am going to be running it on Ting, you think they would do that for me if it happens? :laugh:
matt135353 said:
Ah, thanks for the link. I don't have TEP and it's out of warranty but I'll give Sprint repair a shot. Thanks!
Click to expand...
Click to collapse
I have TEP but that never even came up. I never filed a claim. They originally wanted me to go to a Sprint store to have a tech look at it but I complained that the nearest store is an hour away. So they took my word, after explaining what was happening, and sent me a new (refurbished) EVO and then I sent them the old one in the package they provided with the new one. This was back in November of 2013 and I never heard anything else about it.
Sent from my Nexus 5 using XDA Premium 4 mobile app