Androidpolicy.jar - Nexus 5 Q&A, Help & Troubleshooting

I've been trying to update my rooted Nexus 5 for a while now with the actual over the air updates and I just noticed they're not actually applying. So I started to update manually but it wouldn't let me because of changes made in the system after installing mods. So I uninstalled all the mods I used and the update proceeds further but it still fails and now tells me that there's an error with androidpolicy.jar. Can anyone provide a flash able zip for this so I can finally update to 4.4.2?
Please and thank you.

joviansky said:
I've been trying to update my rooted Nexus 5 for a while now with the actual over the air updates and I just noticed they're not actually applying. So I started to update manually but it wouldn't let me because of changes made in the system after installing mods. So I uninstalled all the mods I used and the update proceeds further but it still fails and now tells me that there's an error with androidpolicy.jar. Can anyone provide a flash able zip for this so I can finally update to 4.4.2?
Please and thank you.
Click to expand...
Click to collapse
You can fastboot flash the system and boot image to return your phone to stock, then take the ota
http://forum.xda-developers.com/showthread.php?p=47369234

Related

Rooted users: Results After Installing Maintenance Update?

As reported here and on SU, the maintenance update from Sprint/HTC is being rolled out over the air. Can people with Root and/or a custom ROM tell us what happens if you update? I doubt you'll loose root but I'm just curious and I'm sure other are too.
This is only for rooted users. No need to post if the update isn't available to you yet. IF it works for you and you're rooted/rom'ed, post.
Root: Yes or No
ROM: Tell us which
Reuslts: Still rooted, working fine?
As for me, the update isn't available yet but I want to know what I'm getting in to before I allow it.
EDIT: So far it looks like the update won't even install for rooted users - Recovery image gets in the way...
EDIT2: freshlyill has provided a direct download of the update pkg file in post #7
EDIT3: This update definitely cannot be made on rooted Heros but doesn't hurt the phone if you try. No risk.
EDIT4: UPDATE: SUCCESS! thecodemonk has confirmed that root is still available on page 4. Process: Use stock RUU to bring it back to stock, download and apply update, re-root like normal!
EDIT5: Satinkzo has also confirmed that the above works. Now, somebody ROM this sucker up
Im rooted on Fresh ROM. Dl the update now, at about 20%...
I cannot get it to install on rooted phone. Looks like the recovery image or something gets in the way.
freshlyill (from fresh rom) got the update and also said it seemed to error out because of the recovery image. But he rebooted again and it appeared to work. He still has root but has no signs that the update applied. Still getting wake lock on stock messaging app.
No firmware update available for my phone yet.
Decided to take the plunge since I nandroided recently...whee! (going about 1%/second ^_^)
same here. Rooted with no custom rom. Won't take the update.
here's the update..
http://rapidshare.com/files/308943608/update.pkg
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Same here, but using Fresh ROM
@Fresh: how did you get the update to take?
Same as ElAguila
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Verification failed here as well.
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
I'm in that process right now just to test. You might beat me though
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Satinkzo said:
I'm in that process right now just to test. You might beat me though
Click to expand...
Click to collapse
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
I downloaded and opened the update.pkg and it is just a zipped file. I wonder if it would be possible to push it with adb?
Negrito said:
Same here.
@Fresh: how did you get the update to take?
Click to expand...
Click to collapse
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
kylez64 said:
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Click to expand...
Click to collapse
It's actually not as dangerous as it sounds since I can always RUU back to the vulnerable version and nandroid restore.
EDIT: Status...RUU complete, applying update now.
chicojd said:
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
Click to expand...
Click to collapse
If that is the case then you don't want this MR if you want to stay rooted then. I was kind of hoping that wasn't the case with this MR.
freshlyill said:
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
Click to expand...
Click to collapse
My mistake, i misread 'flipz' post.

[Q] Anyone know what I am doing wrong by looking at this picture

I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
jmcdonald58 said:
I am trying to install ota 1.84 from 1.53 stock backup I made when I 1st rooted-after I flashed the stock rom to my device I was prompted for the ota update which I downloaded I fastboot flash stock recovery used ota rootkeeper to protect root when I went to install the update it went about 25% then this message appeared,epic fail I rechecked my rom to make sure there wasn't any rooted apps on it just plain stock I know it something I have missed along the way but I stuck atm -went ahead and reflashed cwm and restored backup -Can anyone help point me in the right direction on this one??I apoligized in advance if its been posted somewhere on here I have failed to locate and answer
Click to expand...
Click to collapse
hopefully better image
Geeze best image i have
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
x1tyme said:
I never apply ota update but hope this help you out.
http://www.jbhale.com/2012/06/09/dev-how-to-apply-ota-htc-tested-on-one-s/
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Thanks will give it a look
frdd said:
It says Error in file, have you tried redownloading it? Did you manually download the OTA file or did you get it the usual way (search for updates in phone).
Click to expand...
Click to collapse
I downloaded it directly from device
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
touch of jobo said:
It says:
Code:
Verifying current system...
assert failed: blablabla
To me, this means:
It checks the system on your device to see if it can take this OTA, but the hash of your build.prop file does not match what it expects.
Maybe this OTA is not for your device or you're not on truly stock 1.53.
-Jobo
Click to expand...
Click to collapse
Yeah going take a look at it later that's kinda what I was thinking anyhow I appreciate the help

Problem installing OTA 4.4.2 with custom recovery (TWRP) and encrypted phone

Hi everyone,
Las week the OTA update appeared in my phone. I tried to use the google-automatic procedure, but as I have my Nexus 5 rooted, the install was aborted as soon as the device was restarted.
I read the helpdesk thread, trying to update the device manually, but I can't be able to.
I have the 4.4 to 4.4.2 .zip file inside the downloads folder, I restart the device to recovery mode (I've installed TWRP), and after writing the decrypt password and mount the volume, When I try to apply the zip file
"/system/app/EmailGoogle.apk" has unexpected co
E: Error executing update binary in zip '/sdcar
Error flashing zip '/sdcard/Download/b3d1f30762
Updating partition details..
Note that the senteces is cut due to the lenght of the screen.
Before flashing, I go to mount option, and mount all the folder (system, firmware, sdcard)
Any ideas?
Now I'm thinking that when I rooted the device, I used ES File Explorer to delete some apps directly from /sys/apps, maybe is that the error, that some GApps has been removed from the device.
Thank you!
Yes Google has nicely written in app checks. If these apps are not present on check the update is aborted
Sent from my Nexus 5 using Tapatalk
So I have to reinstall the GApps package, and try to apply de update?
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Ben36 said:
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Link not valid, but thank you, I will install GApps
Zepius said:
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Click to expand...
Click to collapse
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Deiwor said:
Link not valid, but thank you, I will install GApps
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Click to expand...
Click to collapse
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
jd1639 said:
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
Click to expand...
Click to collapse
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Deiwor said:
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Click to expand...
Click to collapse
Flashing the system and boot images isn't starting from scratch... you can keep your userdata as long as you aren't using a custom ROM. Flashing those just gives you back a clean stock OS without any of your mods. No need to start from scratch. Should only take a couple minutes.
Also, your mods are the reason it failed in the first place, not because you were rooted. Rooting itself does not prevent OTA updates.

[q] OTA 5.0.1 on rooted shield

I am rooted on locked bootloader. My tablet just downloaded the 5.0.1 update. Has anyone flashed this yet and kept root? Not sure where the download is stored on the file system in case of sideloading or flashing from CWM. Thanks.
Hi. Inside the update ZIP there are some hash checks of the system partition, so what is needed is rebuilding ota update ZIP, which I can't do atm.
didn't work for me
Im 5.0 rooted with unlocked bootloader, using CWM.
After downloading, it restarted to cwm and installation failed. Didn't take a picture or write down the details; making a second attempt now, will report back. Did not lose root during install attempt.
Mine is failing because CWM seems to be telling it I'm still on Android 4.4.2.
same here
johndough247 said:
Im 5.0 rooted with unlocked bootloader, using CWM.
After downloading, it restarted to cwm and installation failed. Didn't take a picture or write down the details; making a second attempt now, will report back. Did not lose root during install attempt.
Click to expand...
Click to collapse
The same happend to me did you manage to fix it?!
wibimaster said:
The same happend to me did you manage to fix it?!
Click to expand...
Click to collapse
Until someone rebuilds the update to remove the checks you will keep getting an error.
Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.
bigcletus said:
Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.
Click to expand...
Click to collapse
Oh, this is interesting! so this way you keep both the root and CWM?
which shield you have got?
bigcletus said:
Ok. Here is what I did on my locked bootloader shield:
1. Download the full 5.0.1 US LTE zip and SuperSU 2.40.
2. Entered CWM, flashed 5.0.1, then SuperSU, wipe cache partition, and reboot. Done.
Nothing to it. Only thing now, how do I remove the OTA notice I keep getting to update? It seems that the incremental update had downloaded and now it keeps prompting me to flash even though I manually updated with the full version. Anyone know how to get around this? Thanks.
EDIT: I used the command 'pm disable com.nvidia.ota' and so far seems to have fixed it.
Click to expand...
Click to collapse
Do you have the wifi 16 us or the 32 LTE us?

[Q] Unable to install OTA update (5.1) with TWRP installed

One huge problem here is that every time I fail to install, I get prompted to download the update again. It makes it VERY SLOW to do trial and error. Every time I accept the update it then boots into TWRP and I don't know what to do to install the update.
Please advise.
You can sideload the 5.1 update, more info here on sideloading http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
You need to be totally stock to be able to update via OTA if I am not mistaken, meaning no root, no custom ROM, not custom recovery, your best bet now is to flash the OTA zip for 5.1
RichardBronosky said:
One huge problem here is that every time I fail to install, I get prompted to download the update again. It makes it VERY SLOW to do trial and error. Every time I accept the update it then boots into TWRP and I don't know what to do to install the update.
Please advise.
Click to expand...
Click to collapse
Like people said, gotta go back to stock everything then enjoy your update.
Or just flash one of the zips available on here. Job done
http://forum.xda-developers.com/showthread.php?p=59618859
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Yup I flashed a zip. Way quicker

Categories

Resources