• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root OTA update failure

thornev

Android Enthusiast
I am unlocked, rooted and have CleanROM 1.0 installed. I downloaded the OTA update, I got prompted to install it and I replied OK. Phone powered off, came back up so that update was being applied, and then about 1/4 of the way through I get this error:

Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed: apply_patch_check("/system/app/AccountSyncManager.apk". some gobbledee-gook numbers)
E:Error in /cache/fumo/OTAPkg.zip
(Status 7)
Installation aborted.

Is this because I have a de-bloated ROM? Even after I did a factory wipe, in Settings > About Phone > Software information, the Software number is still CleanROM 1.0. How do I get rid of that ?

UPDATE... Well, I bricked my phone - stuck on white HTC screen - so did a factory wipe. Oh well. Trying to apply OTA update again now. OH NO !!! Still won't go !!! Same error. HELP !! Also, ain't got no WiFi, says "Error" for Wifi settings. Oy.
 
You should still be able to get into recovery. My suggestion would be to grab CleanROM 1.6 which includes the OTA. You can drop it on your SD card in recovery(use the USB-ms mounting option)
 
Thanks, MrSmith. I tried that 2 days ago and it didn't seem that the radio update is included as I still was getting only 4 bars for the VZW network signal. I read that a 5-bar icon is an indication that the radio is updated. Is that incorrect?
 
Thanks, MrSmith. I tried that 2 days ago and it didn't seem that the radio update is included as I still was getting only 4 bars for the VZW network signal. I read that a 5-bar icon is an indication that the radio is updated. Is that incorrect?

To be honest I'm not sure. I took no interest in the OTA so I'm not sure other than the version change what would be different. If you're still stuck I would say try relock the phone, apply the RUU, then re-root/ROM.
 
I'm trying to get the phone back to stock. "fastboot oem lock" doesn't work, says "oem" is an invalid option. So then I tried anyway to run the RUU utility from Scott's web site, but it failed with an "unknown error". Boy am I up the creek with only 1 paddle trying to get the OTA update.
 
I'm trying to get the phone back to stock. "fastboot oem lock" doesn't work, says "oem" is an invalid option. So then I tried anyway to run the RUU utility from Scott's web site, but it failed with an "unknown error". Boy am I up the creek with only 1 paddle trying to get the OTA update.

Someone else encountered this and believe it or not solved it by using an upper case "F" on "Fastboot" . Don't ask me what difference that makes...

Check your path to make sure you don't have another version of fastboot hiding somewhere. I'd specifically call fastboot like "c:\android\fastboot.exe oem lock" or if you're on a mac/linux "/android/fastboot oem lock"

In any case the phone HAS to be locked before running the RUU
 
Thanks again, MrSmith. I bit the bullet and followed your original advice to install CleanRom 1.6 just so I can get my life back. =:-) I wish the radio were updated, but maybe another day I'll attempt all of this again. Or maybe Scott will include the radio update in CleanROM 1.7.
 
Thanks again, MrSmith. I bit the bullet and followed your original advice to install CleanRom 1.6 just so I can get my life back. =:-) I wish the radio were updated, but maybe another day I'll attempt all of this again. Or maybe Scott will include the radio update in CleanROM 1.7.

He can't. Because we don't have S-OFF. Currently the only way to update the radios is via the RUU/OTA.
 
He can't. Because we don't have S-OFF. Currently the only way to update the radios is via the RUU/OTA.
Ah. Well I wish he'd put a note about that in his post that the update doesn't include the new radio. My head's a little flat right now on one side. =:-)
 
Back
Top Bottom