deleted stock. apk's and now I can't update!

TeachDis2

Member
May 27, 2010
21
0
0
Yea... so this kind of embarrassing. Recently i rooted my DX and removed some of the bloatware... Instead of just changing the. Apk files to .bak... I deleted them. So when I tried to update to. 604 or whatever the newest update is, the update failed. I'm assuming this happened because the OTA update tries to update some of the .apk's that aren't there anymore.

If someone could please pull the amazonmp3 and blockbuster apps off their pre. 604 droid x and post them, I would be forever greatful!

Fyi i might need more than those two apps. I just have had a chance to look at what exactly I need.

Thanks in advance!
 
Well this sucks. I found the .apks I needed and moved them back onto the phone and they all work. However, I still can't get my phone to update. Could this possibly be due to rooting the phone? Has anyone else run into this problem?

PLEASE HELP!
 
It's likely due to your phone being rooted.

Would removing the root .apks fix this?

I'm definitely not trying to doubt you here but don't you think a lot more people would be having this problem if that were the case? (or am I just "that guy")

Is there a crash dump or log anywhere that might have any info as to why the update is failing?

thanks
 
Okay i removed the root .apk and associated file however the update is still not working.

I tried using adb logcat to get a hint at what might be going on when the update fail. However this isn't very helpful because the phone has to be up and running and adb has to see the device before it would output logcat.

I'M GOING TO LOSE IT IF I CAN'T FIGURE THIS OUT.

help a nerd out. :)
 
I did try that. I've also read in some of the other threads in this forum that rooting doesn't affect your ability to update. Also people have been able to update without having some of the bloatware apps on their phones. so i don't know what the hell is going on.
 
If you can successfully unroot and you've put all the bloatware back, you could always take it back to Verizon and tell them your phone isn't updating.
 
When you say the update failed, does it just not show up, or is it actually giving you an error when you try to apply the update? If so, what does the error say?
 
what happens is I download the update, hit install and the phone reboots and starts the update screen. from there the update hang and then the phone reboots and then I get a popup that says the update fails.

This last time i tried the update though I double tapped on the update screen and it showed a console or output of what the update was doing (that I was looking for all along).

So now I know it's complaining about CityID. It looks like it's doing a checksum and finding that the values don't match. What's weird is CityId runs fine AND I've read that app isn't required for the update.

so now I'm confused...

I guess I'll try reinstalling CityID from adb and see what that does.
 
I've done a factory reset twice now... the problem lies in the CityID.apk... the checksums don't match up between the update and the CityID.apk currently on my phone. That's why i'm trying to find a known .516 CityID.apk

Anyone still rockin' .516?L
 
OK - I assumed a factory reset put everything back to "stock"
I guess based on what you are saying, a factory reset only clears out user settings/usage?
 
Yea, Factory reset just wipes the user data from the phone, it doesn't touch the .apks

I just need that .516 CityID.apk. I just wish there were someone out there that hadn't updated to .604!