Database Users

[Q] Error While Attempting to Apply Update.zip

Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7).
Full Error:
Code:
-- install from sdcard...
finding update package...
opening update package...
installing update...
assert failed: file_getprop (" /system/build.prop", "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2/vzw/23.15:user/ota-rel-keys,release-keys" || file_getprop(" /system/build.prop" , "ro.build.fingerprint") == "verizion/shadow_vzw/cdma_shadow/shadow:2.2.1/vzw/23.340:user/ota-rel-keys,release-keys"
E:Error in /sdcard/update.zip
(Status7)
Installation aborted.

doronster195 said:
I was rooted with z4, had apps frozen with titanium backup, have bootstrap, used dx overclocker (to undervoltage and to do a quick-boot with "android" logo rather than Droid Eye). I unrooted, unfroze, stock voltage/speed and turned off apply at boot, FORGOT to undo the quick-boot (but I thought it wouldnt matter since i'm unrooted).
Booted into recovery, tried doing the update.zip got Installation Aborted error (status 7), pressed reboot phone and got the M, followed by the "android" logo that WILL NOT GO AWAY.
Phone won't load, what should I do? Need phone to work soon!
Click to expand...
Click to collapse
Ok it sounds like you are stuck in a bootloop.....you can restart your phone by doing a batt pull then when you go to turn it on hold the power button and home at the same time until you see the exclamation mark and droid guy ..this means you are in recovery mode ...then press the search button and a menu will appear ....use volume rockers to scroll and the camera or menu button to select ....go to data wipe/factory reset and select it ...then reboot and if it works your x will be back to how it came out of box if it doesn't then you will have to sbf ...find the sbf file for whatever system version you are on and flash it and that should work

Well, I did a restore, which worked. However, I'd still like to receive the OTA update. I downloaded the update.zip and want to install it myself. Why was i given this installation aborted error? Was it truly because of what I said above--quick boot option?
Edit: Tried booting into normal recovery (not bootstrap), while not rooted, and no rooting tasks have been done since the restore. Trying to "apply sdcard:update.zip" gives me an Error in /sdcard/update.zip (status 7) Installation Aborted
Edit2: Original Post updated with issue

I'm in the same boat...
I unfroze the bloat and unrooted my phone, it was stock with all bloat froze so nothing out of the ordinary to be concerned about.
Ran update.zip and got the same error as you. I'm not savvy enough to understand or figure out what's going wrong with any certainty. My best guess is that something in the build prop doesn't jive with the build prop the update.zip file checks against. I doubt rooting would have caused any change in my build prop and I never did anything to my phone other than root and freeze bloat so my build prop should be fine.

Problem Solved
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.

Can you share the sbf I am having the same issue and it is ticking me off. Thanks in advance

i posted the link for the sbf in the above post, i cannot post actual links, so you'll have to add to figure out the url for yourself. Just go to androidchat*org and go to their file database, its in there.

doronster195 said:
Fixed the issue thanks to the help from the guys at: (#androidchat on freenode)
specifically tabe and krayzee.
I am 2.3.15 originally, with a bootloader 30.04 (not 30.03).
I used the sbf (that I got from androidchat), and just sbfed. Before activating my phone again, I did the update.zip and it worked just fine.
Guide I used for SBF: droidxforums /forum/hacking-help/12015-complete-droid-x-sbf-flashing-guide.html
(it says you should be careful if you are on 30.04, but i did it on 30.04 so you will be fine)
Hope this helps.
Click to expand...
Click to collapse
Which sbf did you use? Do you have a link to that? PM if necessary...

4.2 Update Recovery Error - Unique Issue

I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?

JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319

Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.

I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?

[Q] 4.2.2 Update Error Help

So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)
Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image

That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.

bftb0 said:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.
The error that occurred is given in the recovery log file - /cache/recovery/recovery.log
Please report what the error was. If you actually have root in the ROM you should be able to view this file.
No need to relock your boot loader - that is unrelated and relocking it only complicates things.
One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
Click to expand...
Click to collapse
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Thanks!

MatthiasSchuetze said:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?
Click to expand...
Click to collapse
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?
What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.
As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.
And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.
The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)
The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:
- run the OTA, look at the error in /recovery/log/recovery.log
- hand patch the file involved
- re-run the OTA.
Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.
The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).
A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.
If you don't like the result, restore your Nandroid backup. That's what backups are for.**
good luck
** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.

First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.

MatthiasSchuetze said:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.
So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!
Why is the picture that I attached not showing?
This is the error message:
ClockworkMod Recovery v6.0.1.9
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation update...
Verifying current system...
assert failed: apply_patch_check("/system/build.
prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")
E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3
9-from-JOP40D.07501b11.zip
(Status 7)
Installation aborted.
I rechecked it for the Nexus 7. The message is slightly different:
assert failed: apply_patch_check ("/system/lib/libSR_A
udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")
E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr
om-JOP40D. 6ece895e.zip
(Status 7)
Installation aborted.
Now, it does show (the picture). Nice.
Click to expand...
Click to collapse
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.

signature verification failed problem

Hi people. i have got nexus 4 for about one month. so one day it got ubdate file and when i pressed install, it reboot and on recovery page it says signature verification failed. ubdate is not instaling.
phone is rooted
it runs stock 4.3 version of android OS
can anyone help me on this problem?

Flash a custom recovery to fix that issue.

[Q] How to install new small security patch on JB 4.3

I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.

I will appreciate any help.

I have this too
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret

rookie8155 said:
I have rooted my Nexus 4 with Tool Kit and flashed it with stock 4.3 image. Few days later came new small security patch for 4.3. Now every few days I get the notification on my phone but when I try to let it install, it does not get installed.
Here is phone info:
Android version: 4.3
Build number: JWR66V
Kernel: 3.4.0-perf-gf43c3d9
I will appreciate your help. Is this update available as a zip file on the forum? if it is, then I can side load it on my rooted phone.
Click to expand...
Click to collapse
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page

bcw1000 said:
If it helps, I have to problem too.
I have rooted my phone and installed ClockworkMod Recover v6.0.2.3 but have not installed any custom ROM or other changes (that I know of).
I periodically get a messge an update has been downloaded, but when I attempt to install it, ClockworkMod informs me:
Code:
E: failed to verify whole-file signature
E: signature verification failed
Since I don't know what it is, I abort the install, but I can't tell what is happening. I would also appreciate any help.
Regards,
Bret
Click to expand...
Click to collapse
Yes, I have also installed ClockworkMod Recover v6.0.2.3 and running stock ROM as well. . If this update is available as a zip file then we can install it. It should not be just two of us having this issue. Everyone who rooted phone should have same issue.

HeyyMyNameIs said:
Im not good with these type of thing but here http://forum.xda-developers.com/showthread.php?t=2145848 alot of guys here can help you, and i think the OP already has a solution on the 1st page
Click to expand...
Click to collapse
Thanks for pointing towards the right direction. I tried to side load the zip but it failed. I will post the question in the other thread.