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

Help OTA Update to 2.3.340 not working

R

Raryn

Well-Known Member
My phone is ~2 weeks old, and is currently running 2.3.151. Got a notice of an OTA update this morning for 2.3.340, downloaded it, and when it rebooted it would only get about 1/5 of the way through installing before the ! would come up and then it would restart and tell me that the update failed. Tried this 3-4 times.

I found the update.zip for this update and tried installing it manually through the recovery console. The error below popped up.

Installing Update... assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/shadow_vzw/cdma_shadow/shadow:2.2/VZW/23.15:user/ota-rel-keys.release-keys" || file_getprop("/system/build.prop". ro.build.fingerprint") == "verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys.release-keys"
E:Error in /sdcard/update.zip
(status 7)
Click to expand...

I'm rooted, but have not messed with build.prop at all. Running a few standard rooted apps (setcpu, titanium backup, adfree) but am on the stock theme and ROM.

Any way to install the update?
 
honestly idk much about the error I just know people were having problems with the ota after deleting system apps
 
FFS.

Trying it OTA again and its telling me I reinstalled the wrong version of CityID. Friggen bloat!

Edit: The error is

assert failed: apply_patch_check ("/system/app/CityID.apk". "555aadfa5e340007ca49b658467302ad89d5bd76", "3dd143663a7da3a0b9f62f38afd52dd9c8107ad3"')
E:Error in /cache/Blur_Version_2.3.151.MB810.Verizon.en.US.zip
(Status 7)

though I probably made a mistake copying down the hash codes.

Anyone know where I can find the "correct" version of CityID?
 
I tried different "CityID" apks from a couple sources and nothing helped.

In the end I just sbf'd, restored all my settings with titanium backup, made sure to back up all the bloat this time, and upgraded (successfully) OTA. That should NOT have been necessary, but oh well. Lesson learned for next time.
 
Got my Droid X 2 weeks ago, and rooted it almost immediately to get rid of the bloatware because I hated having all that Verizon crap on there. Thought the Titanium Backup would help me, but I didn't know it doesn't actually back up the programs. Lesson learned!

Anyhow, I couldn't install this latest update, so I've been trying to put all the old apps back on, and I've succeeded mostly. However, I can't for the life of me get CarDock back on there. And CarDock is where the update says it is finding an error. I've done everything correctly (at least in the same way that brought back all the old ones), and it's nowhere to be found except in the system files. Any ideas? I'm stumped.

Also, when I originally started removing apps, I couldn't get rid of the Blockbuster one, no matter how hard I tried. Any ideas there either? It was the only one I couldn't get rid of.

So all that being said, in the future, are there any better ideas on how to get rid of bloatware that won't be a pain in the butt next time there's an update? I heard freezing them in Titanium Backup works well, is this true?

And one last noob question...how beneficial is it to install all the ROMs and whatnot that people are going around with? I would love to have my phone pimped out, but I'm not a system file techie so much. I love me some sleekness. Thanks for all your help!

My error message from the installation:

assert failed: apply_patch_check ("/system/app/CarDock.apk", "c9cc1be95af5d4152775a3df6848c35f8d1396c7",
"c3351e5dcea8dd312218d5a137f31406d7980c03")
E:Error in /cache/Blur_Version.2.3.151.MB810.Verizon.en.US.zip
(Status 7)
Installation aborted.
 
CarDock, CityID and everything is here: http://www.chadhaney.com/droidXDefault/


Are you following the directions exactly? Permissions make a big difference, and I have a feeling this is what's hurting you. Here's what you do:

1. Download Root Explorer, and use that to go to the /system/apps directory
2. Press the Mount R/W button on the top right and put all the apk/odex files that you are missing.
3. Every file you put there must have All the "READS" checked, and the User "WRITE" checked. You must also install any solo APK's (the ones with ODEX files will not install - but both need the permissions fixed) To access this permission dialog, long press on the file and select Permissions.
4. Mount it back to R/O on the top right

Are you doing that? The first error you gave in your original post is odd and I've never heard of that one....
 
Yeah, I've been giving everything permissions...and everything else installed, but CarDock is the only one that won't after I've done the same things to it. Do I need to put both the .apk and the .odex files in there? None of the others made me do that. :confused:
 
I know it doesn't help much now, but in the future instead of deleting the bloat just rename the extension to .bak or something like that. "Removes" it from the phone but is easy to get back for update time. SBF is probably the easiest way to fix it
 
Hrm. I actually had the same problem and somehow fixed it. I tried reproducing what I did and now I'm stuck in a bootloop as well haha. I'll let you know what I figure out.

Edit: Got it. There's probably an easier version but meh. Flash the leaked 2.3.320 SBF, factory reset, then flash the 2.3.340 system only sbf.

2.3.320 leak DL
2.3.340 system only sbf
 
Raryn said:
I tried different "CityID" apks from a couple sources and nothing helped.

In the end I just sbf'd, restored all my settings with titanium backup, made sure to back up all the bloat this time, and upgraded (successfully) OTA. That should NOT have been necessary, but oh well. Lesson learned for next time.
Click to expand...

I also tried a few CityID apks with no luck...is anyone running 2.3.151 that might be able to share their apks?

If not, can anyone point me to a guide to do the sbf thats being referenced?
 
I had an issue where I rooted my phones removed the bloatware and couldn't update to 2.3.340. I had to flash my phone using RDS Lite 4.8 and use the current SBF. Tthen after I was able to use Z4Root
 
You must log in or register to reply here.
Back
Top Bottom