Database Users

Recovery zip signature verification failing

I recently exchanged my Nexus One for another guy's N-1 which works on ATT 3G. I had done a nandroid backup of my phone, and used that same image to recover the "new" phone to exactly how it was before the switch. It failed first, but after I moved my BCDS folder to the new HTPXXX folder, it went through.
However, now when I try to flash a zip from recovery (Amon-RA 2.2.1), I always get the "Signature verification failed" error. I tried flashing newer radio, after verifying the MD5SUM. I tried flashing the 0.35.017 HBoot. Both of them failed. I am wondering if it's because of the mismatched nandroid recovery I did.
Any help would be greatly appreciated -- thanks!
Edit: Needless to say, after disabling signature verification, everything flashes correctly.

Oops I just realised I should not be posting questions here -- sorry! Can someone please lock this thread?

How to update the Nexus Android 2.2 to Android 2.3.4? Need to unlock the bootloader?
How to update the Nexus Android 2.2 Android 2.3? Need to unlock the bootloader?
I tried but could not update or pro 2.2.1. It says update error and aborted.
I ask for help.

[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.

upgrading to 4.2.2 phonesky.apk error

can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod

bump?
noday42 said:
can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod
Click to expand...
Click to collapse

Have you already tried flashing the 4.2.2 stock rom with fastboot? Also, what's your bootloader version and do you have a device with or without 3g (grouper or tilapia).

The OTA works by *patching* existing files.
That can not possibly succeed under any circumstance if a file it expects to patch has been altered or removed. So, the OTA patch process checks all files it intends to patch first to make sure they are identical to the stock version. If even a single file is out of whack, nothing is changed and the install halts immediately with an error message.
The error message is telling you about the first file encountered with this problem, namely
/system/app/phonesky.apk
So, put the original file back. Get it out of your backups. You do make backups, right? (Note that because of the halt-on-first-fail behavior, there may be more problem files awaiting you.)
Either that, or pretend you are installing a new ROM and proceed accordingly.
OTAs are not meant for upgrading arbitrarily-modified stock ROMs.

thanks guys. I had previously tried replacing the modded app, but it didn't seem to fix anything. Ended up unrooting and restoring to factory 4.2.1, upgrading to 4.2.2 over the air, and re-rooting/restoring apps with TiBu. Thanks for your advice!

noday42 said:
can't seem to find the answer to this anywhere, so hopefully someone can help.
I'm running rooted 4.2.1 stock ROM with CMW recovery. Trying to update to 4.2.2 with absolutely no luck. Whether I try to update OTA or from zip, I consistently get a failed install with this error:
assert failed: apply_patch_check ("/system/app/phonesky.apk"
I've tried everything I can think of. Wiping cache/dalvik, factory reset within CMW, overwriting the phonesky.apk with the stock version. Nothing seems to solve the problem. The 4.2.2 zip file I have is the one downloaded from here.
Any advice on where to go next? I'm completely at a loss.
EDIT: I should also note I had previously cracked the Google Play store with the ChelpUS mod
Click to expand...
Click to collapse
I'm encountering the same with 4.3 update.... I unrooted my device.... CAN YOU PLS POST THE PHONESKY. APK FROM STOCK 4.2.2 urgently

4.3 Update failing

Hi everyone, I have a rooted with stock rom nexus7 with TWRP recovery, every time I want to update to 4.3, it fails, at first it comes to install and after saying 'Verifying Package', it goes to recovery first menu, Any suggestions??
by the way, I don't want to loose any of my data.

Gosh, there are so many threads on this. Did you search or read anything? The specific error is important, but you didn't say what it was. Depending on which error you have determines how to fix it. Was it an 'Error executing updater binary in zip...' or did you get a verification failure on a file such as 'debuggerd' or a system app that you may have replaced or frozen? I was able to fix my problems for a stock rom and kernel, rooted with TWRP after reading the threads in this forum. And your data won't be 'loose' nor will you lose data with this update, but you will lose root, which can be regained easily.

Error when trying to upgrade to 5.0 using TWRP

I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)

dude the error is written in plain English: the process expects one type of thing in your system, but it finds another, doesn't like that so quits. trying to find the exact source of the error would be futile. I received an error too, not sure if it was the same since I didn't bother reading it. I just downloaded the stock 4.4.4 firmware from Google and extracted system.img and flashed it with fastboot. I'd suggest you go that route. you can try flashing from twrp again after that, personally I went the adb sideload route: http://forum.xda-developers.com/nexus-7/general/lollipop-ota-update-via-adb-data-t2941175

arimaidana said:
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
Click to expand...
Click to collapse
You are using OmniROM. Pretty obvious you can't upgrade a custom ROM with a stock OTA.

This has nothing to do with omnirom at all, it all has to do with twrp using a custom .prop with wrong preset values. It wasn't an issue until Google decided that the 5.0 update checks more things, hence this stupid error. Btw that's exactly the 1st thing the upgrade script checks!
twrp must change its way of providing props because it's so obviously a major bug and will prevent using it to install any future updates.
What I did is use the factory image to do a custom non-wiping upgrade (there's a topic about how to do that), got incredibly slow performance and then do a wipe to get performance back and start with a clean slate with Lollipop, like I did with Kitkat.
So I think if your Kitkat was starting to be slow, better start anew and anyway Lollipop lets you choose exactly what to reinstall.