Related
My phone is asking me to update. should I update or not? If not how do I keep it from popping up the message?
Sent from my Eris using XDA Premium App
I forgot to mention I have the July OTA and have a custom Tom on there already.
Sent from my Eris using XDA Premium App
the ota will kill your root!! heres an ota disabler, just load this zip on sd and flash like a rom....hope this helps...
Thanks!
Sent from my Eris using XDA Premium App
yea no problem, definetly post back if you have any issues...
frosteddroid said:
the ota will kill your root!! heres an ota disabler, just load this zip on sd and flash like a rom....hope this helps...
Click to expand...
Click to collapse
Not true for any phone with a custom recovery. If you accept the OTA, the phone will boot into the custom recovery, and the update will immediately fail. With Amon_RA, it will fail due to a signature verification error, and with ClockworkMod it will fail due to an assert() check at the beginning of the script
In both of these cases, the termination of the install occurs before a single thing is changed. Moreover, because the OTA downloader never even checks to see if the OTA install succeeded, the nag popup will disappear after the failure, and will never reappear again (unless you did a wipe data/factory reset procedure on that ROM).
[ Edit ] the exact assertion that occurs is
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/htc_desirec/desirec/desirec:2.1/ERD79/185970:user
/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/htc_desirec/desirec/desirec:2.1/ERD79/335228:user
/release-keys");
So, I guess - in the ClockworkMod case - it depends on whether or not your ROM dev changed the "ro.build.fingerprint" in their ROM file. If it wasn't changed, and your recovery boots to ClockworkMod instead of Amon_RA, then it is possible that the install will run, which would over-write the custom recovery. Not really a disaster, even if that happens, as you still have a rooted ROM from which you can run
Code:
flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
.
If you went into a bootloop after the install, and you had the 1.49.0000 S-ON bootloader, and you did not have USB debugging turned on... well, that would be a possible disaster (soft bricking). (Another reason to use Amon_RA with a current version of ROM Manager, rather than having Clockwork being written into the recovery boot.)
If you have a stock ROM which is rooted, and you DO want the update to happen, gnarlyc put together a flashable .zip which performs the same patching update, but does not overwrite either the recovery boot or the radio. You can find that flashable .zip here.
Obviously, you ought to know which stock ROM your rooted ROM is based upon before flashing either of these.
sweet! thanks for the link to gnarly's zip. i got the install failed on the wife's rooted eris (still stock rom) but was worried i would have to unroot to do it. no way im going to do it on my gsb 1.7 eris.
Hello. I have a Droid RAZR XT912 (Verizon) and am having troubles with the JB update. I have the update file from Dev-host. I have all bloatware apps unfrozen. I went through OTA and backup root, temp unroot, restore root, temp unroot, and restore root. I also cleared dalvik cache (through TiBU) and system cache (through stock recovery) before updating. Also, verified all MD5 checksums.
My screen after attempting to apply update reads as:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/build.prop",(assorted numbers and letters)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I looked around the forums to try to find a similar error, with a fix that worked, but none of them fit.
Other info:
I do not have safestrap installed, just rooted.
I AM on .211.
I would just really love to get this update. Thanks.
I kept getting that same error message. For me, it was because I had Eclipse installed as my ROM, so I couldn't update over it.
To fix, I fastbooted back to stock .211 ICS, then flashed the JB update through stock recovery. Then booted into JB, rooted using the newly found method, and installed a custom recovery. Haven't found another JB custom ROM that I like that works perfectly yet, so still on rooted stock JB for now.
Hopefully that will help you somehow.
Sent from my DROID RAZR Maxx using XDA Premium
Seems to be going well for me, now! I tried just doing a factory reset, and that didn't go. Ended up fastbooting with Droid Razr Utility 1.82, and the update seems to be going through for me! Will go ahead and use the new rooting method once it is complete, and then go through with restoring apps and other backups. Take a thanks.
I've got a rooted Verizon Razr Maxx that has received the OTA 98.72.16 update. It downloads, prompts me to install, gets 1/3rd of the way through then shows the update failed symbol (Android with red warning triangle).
It'll then restart and prompt me to redownload the update.
What is going wrong here? I've been through this cycle 3 times and I just want it to stick.
Been through the same exact thing. I had to back up all my data with TiBu, flash a bonestock ICS, then update, then restore data. I had to have help doing it and i didnt completly understand most of the things i was doing so i cant really help you but you might try installing the update from a external SD to see what error you get
OTA 98.72.16 update
Any advice out there on successfully completing the OTA update package from Motorola/verizon? I keep getting an update unsuccessful. Not sure I want work around it with factory reset and then going back and forth with data. The description of the benefits of the update are vague... not sure I need it that bad. Anyone have any inside scoop, advice or knowledge on this?
Update
CC440 said:
I've got a rooted Verizon Razr Maxx that has received the OTA 98.72.16 update. It downloads, prompts me to install, gets 1/3rd of the way through then shows the update failed symbol (Android with red warning triangle).
It'll then restart and prompt me to redownload the update.
What is going wrong here? I've been through this cycle 3 times and I just want it to stick.
Click to expand...
Click to collapse
So attempt #4...
I wiped the cache, did a factory reset and attempted to install the update from the SD Card in Recovery mode.
I received the following error:
- Verifying system...
assert failed: apply_patch_check("/system/framework/framework-res.apk", "7213ee77f6adfff8543ab0c02094aca55aa2x788", "5da1ccb2003fe1cf47787fdbdd9c5d1c65f7209c")
E:Error in /tmp/sideload/package.zip
(Status)7
Installation aborted.
Fixed!
CC440 said:
So attempt #4...
I wiped the cache, did a factory reset and attempted to install the update from the SD Card in Recovery mode.
I received the following error:
- Verifying system...
assert failed: apply_patch_check("/system/framework/framework-res.apk", "7213ee77f6adfff8543ab0c02094aca55aa2x788", "5da1ccb2003fe1cf47787fdbdd9c5d1c65f7209c")
E:Error in /tmp/sideload/package.zip
(Status)7
Installation aborted.
Click to expand...
Click to collapse
Attempt #5, success!
I used Razr Utility 1.82 to flash the phone back to completely stock .211, wiped the cache, installed from the SD and the update finally completed and stuck.
Did ya unroot or protect ya root from voddo root keeper . If not then try to do that it may help ya
Thx
Hit the thx button if i helped ya in anyways
its still not working for me, actually i cant get the razr utility to do anything... so i cant flash the stock version, any ideas on getting that working?
You must not have any modifications on your phone. No root (but you can protect root with OTA Root Keeper), no changed or deleted system apps, no changed baseband, kernel etc.
Do you have any of that mods?
I rooted using the utility, the main reason was to get rid of the bloatware, so no different roms or anything of that nature, I tried different booting options and running it and no luck, I am trying to unroot by rerooting with a different program, that will rewrite over the utility root that comes with a full unroot option. so far so good, unrooted and waiting while the ota downloads to install, wish me luck
dinc4life said:
I rooted using the utility, the main reason was to get rid of the bloatware, so no different roms or anything of that nature, I tried different booting options and running it and no luck, I am trying to unroot by rerooting with a different program, that will rewrite over the utility root that comes with a full unroot option. so far so good, unrooted and waiting while the ota downloads to install, wish me luck
Click to expand...
Click to collapse
If you got rid of bloatware apps that are put there by Verizon, then that is your problem. All of those bloatware apps need to be there and unfrozen for the update to take.
After fully unrooting i have had no luck i just tried installing from recovery and recieved the same errot message as the previous entry did. Goimgbto try to install one more time and then try reflashing the stock with the utility
I had to reset my RAZR to stock with Matt Groff's droidrazrutility to get the update to install. Be sure to backup your apps and data.
you may have some frozen apps or deleted apps
try to defrost them or reflash the rom
CC440 said:
Attempt #5, success!
I used Razr Utility 1.82 to flash the phone back to completely stock .211, wiped the cache, installed from the SD and the update finally completed and stuck.
Click to expand...
Click to collapse
idk if youll read this but if you do can you point me to where it explains how to wipe the cache and install from eh SD card? cuz i just did the flashboot to .211 and it still fails.
I was having the same problem. I had to uninstall Safestrap for the update to take. I used rootkeeper, unfroze everything, and it finally worked. I was able to keep root as well. I am so relieved. Hope this helps someone.
Sent from my DROID RAZR using xda app-developers app
Downloaded OTA update 2.18.707.5 .
But while installing ...RED EXCLAMATION mark ..and reboots
Tried Thrice..
Flashed Kernel and Stock Recovery and Relocked Bootloder..Still no success
Please anyone upload OTA file ...I will Try installing using TWRP recovery.
Update- I tried installing using TWRP and encountered with an error. (assert check failed- Automative_internet radi0.apk
Suggestion are always welcome
networkofhell said:
Downloaded OTA update 2.18.707.5 .
But while installing ...RED EXCLAMATION mark ..and reboots
Tried Thrice..
Flashed Kernel and Stock Recovery and Relocked Bootloder..Still no success
Please anyone upload OTA file ...I will Try installing using TWRP recovery.
Update- I tried installing using TWRP and encountered with an error. (assert check failed- Automative_internet radi0.apk
Suggestion are always welcome
Click to expand...
Click to collapse
i got an "assert failed: apply_patch_check" error for the calculator widget.
AdX9170 said:
i got an "assert failed: apply_patch_check" error for the calculator widget.
Click to expand...
Click to collapse
This means you have flashed some previous update not intended for your region, like some of us flashed 1.17.401.3 when we weren't supposed to have it, hence we coudnt update ota 4.2.2 as our ots was to patch 1.17.401.1, maybe this will help you, but its not 707, its 401, should still be able to flash though if unlocked through twrp. http://forum.xda-developers.com/showthread.php?t=2419784&page=3. You will need your firmware.zip not mine, different cids. or you could just flash this http://d-h.st/cK4, twrp again. Im sure as long as your unlocked with custom recovery you can flash different cid, except of cause the firmware.zip.
boe323 said:
This means you have flashed some previous update not intended for your region, like some of us flashed 1.17.401.3 when we weren't supposed to have it, hence we coudnt update ota 4.2.2 as our ots was to patch 1.17.401.1, maybe this will help you, but its not 707, its 401, should still be able to flash though if unlocked through twrp. http://forum.xda-developers.com/showthread.php?t=2419784&page=3. You will need your firmware.zip not mine, different cids. or you could just flash this http://d-h.st/cK4, twrp again. Im sure as long as your unlocked with custom recovery you can flash different cid, except of cause the firmware.zip.
Click to expand...
Click to collapse
That's not the case here.. I got an ota update in the device a couple of months back but it wouldn't install on its own so I installed that very downloaded zip file through cwm recovery..
AdX9170 said:
That's not the case here.. I got an ota update in the device a couple of months back but it wouldn't install on its own so I installed that very downloaded zip file through cwm recovery..
Click to expand...
Click to collapse
That will be why then, I bet if you left out that previous update, you would be able to install no problems. Sam problem for me, assert patch failed, but mine was the build.prop, because im UK and the forced ota wasn't for me.
boe323 said:
That will be why then, I bet if you left out that previous update, you would be able to install no problems. Sam problem for me, assert patch failed, but mine was the build.prop, because im UK and the forced ota wasn't for me.
Click to expand...
Click to collapse
No no I think u didn't get me. the ota update was shown on my phone. It gave me a notification that an update is available. I didn't download the update manually from xda. the download happened on my phone thru the ota service itself.
I have solved it and done update completely..
Problem --- STOCK nandroid backup have got problem.. so HTC update fails
Solutions -- Need to Update system folder with proper files for update to be sucessful
Action plan -- Those people who went to STOCk android ( INDIA) using Nandroiod backup will face issue
I will upload proper Nandroid backup ( old backup with files updated) ..
Then download update from HTC and it works and Hboot is upgraded to 1.7 from 1.4
Note -- this is for only CID 038 Which i use in India
https://drive.google.com/folderview?id=0B4wYr_bVgSTBd2ZvaHc1YllZa0U&usp=sharing
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
And now my phone is stuck with a white screen. Menu options are:
Reboot
Reboot to Bootloader
Boot to Download mode
Boot to Recovery Mode
If I select recovery mode, it is unable to launch and takes me back.
Ok, I set it to Download mode and re-ran the RUU .exe, and it seems to have flashed properly now. So I guess I'm good. But I do have questions:
A) Why did the OTA fail multiple times with the System 7 message
B) Why did the RUU .exe wipe everything and give me the 155 failure the first time
C) Is there anything I should do/install/check to prevent problems in the future?
shawndoc said:
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
Click to expand...
Click to collapse
you did something to make status modified
Yes, but what? Every other OTA has installed fine. I haven't tried to root or mess with s-on/off. The only thing I can think of, is last time I reset my phone (due to gmail failing to get push notifications) I uninstalled a bunch of the bundled apps, but I did it using the normal apps management settings.
shawndoc said:
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Click to expand...
Click to collapse
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
schmeggy929 said:
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
Click to expand...
Click to collapse
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
shawndoc said:
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
Click to expand...
Click to collapse
Gotcha, the 2.11.651.180 was the pre-MM update then the MM full OTA. Yes it is weird you were getting those error on a OTA. Even the RUU shouldn't have lead to an error as well. You still having problem or everything ok now?
Yup, all good now. Forcing the phone into download mode and performing the upgrade took. Thanks.