Database Users

[Q] trying to upgrade to 4.1.2 - failed to verify whole-file signature

Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?

Foxman2k said:
Running 4.1.1 at the moment and rooted / unlocked using a toolkit.
Trying to update to 4.2.2 ota but when the nexus reboots I get that error.
What do I do?
Click to expand...
Click to collapse
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel

flyi said:
I think I have the same problem, mine says "Verifying current system..." then says "assert failed: apply_patch_check ..."
I'm currently running 4.1.1 stock rom rooted and custom kernel.
Also, I think you mean 'trying to update to 4.1.2 ota'.
Click to expand...
Click to collapse
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.

Install a custom recovery and use it to run the update. If you already have a custom recovery, then that's why you can't run the ota via google possibly.

flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
But I don't have a custom kernel. Just rooted and unlocked.

mustbepbs said:
Flash the stock kernel. You can do it a number of ways. You can find a cwm zip file with it, use the toolkit to do it, or get the IMG yourself and flash it via fast boot. I had this error earlier.
Click to expand...
Click to collapse
Any guides on this? Pretty new to android.

Anyone have any thoughts on what I should do?

Did you touch any of your system apps?
Seems more likely your update didn't download fully and it failed and md5 checksum. Just try again next time.

I don't think I touched any of the system apps. I did download Adblock and six axis tool. Anything else to look for?

I've downloaded the update probably 4 different times now and same thing each time.

Anything else I can try?

Foxman2k said:
Anything else I can try?
Click to expand...
Click to collapse
Any other options besides resetting? has no one else who only rooted and unlocked run into this problem???
I didn't change any system apps, and for rooting purposes the only apps I downloaded where Titanium Backup, Sixaxis and Stickmount. Should I remove those?
and OT Rootkeeper. Do I remove root first?

flyi said:
See thread:
http://forum.xda-developers.com/showthread.php?t=1764794
seems to be due to custom kernel
Click to expand...
Click to collapse
I was getting exactly the same as you Foxman2k, about the unverified whole-file signature when trying the OTA way. I've just followed the advice of the above linked thread and it worked fine. I had to install Quick Boot (Reboot) to get in to Recovery, then update from SD Card, then ensure signature verification is disabled, then select the downloaded .zip file. I did have RootKeeper active, but I don't really understand what that does so not sure if it made any difference.
HTH

I finally managed to get mine to go through, am rooted but running stock and was getting the error with build.prop.
Then it hit me, I am in tablet mode with my screen at 160, so I set it back to 213 and boom it went through.
HTH

Please help me! apply_patch_check failure when updating to 4.1.2

I have kepy my Nexus 7 fairly stock - it's just been unlocked and rooted with Clockwork recovery.
However, when I try to apply the 4.1.2 update, I get the following:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/app/Wallet.apk" ,"(numbers)", "(more numbers)")
Because I am in the UK, I did play with a modified version of Google wallet for a while.
I got this message during both OTA update process or by manually trying to install the update apk.
I deleted the modified wallet.apk from system/app and then used Market enabler to install the "official" google wallet app.
Still no luck.
I then tried clearing dalvik and cache, and an entire factory reset.
Still get the above error message.
So does anyone know how a file that doesn't even exist anymore in /system/app is causing the error?
Any clever ideas on what to do next?

You put this in the wrong section. This should be in Q/A. Are you tring to update through OTA, or a manual update through CWM?

AFAinHD said:
You put this in the wrong section. This should be in Q/A. Are you tring to update through OTA, or a manual update through CWM?
Click to expand...
Click to collapse
Tried both ways, same result both times.
OTA update rebooted me straight into CWM recovery, and with the manual update method, I booted into CWM recovery and tried to apply the downloaded apk.

The wallet.apk needs to be in system/app.
Not data/app as it is when installed from the play store.
Sent from my Nexus 7 using xda premium

thisisgil said:
Tried both ways, same result both times.
OTA update rebooted me straight into CWM recovery, and with the manual update method, I booted into CWM recovery and tried to apply the downloaded apk.
Click to expand...
Click to collapse
Have you tried reflashing stock recovery then applying the update ota?

AFAinHD said:
Have you tried reflashing stock recovery then applying the update ota?
Click to expand...
Click to collapse
That was more or less my next option. Although in that case, I'd be more inclined to just directly flash 4.1.2 stock.

Hi!
Did you have any luck installing the update???
I'm getting the same error but for youtube.apk!!!
H

Hope this helps: http://forum.xda-developers.com/showthread.php?t=1945938

Did you?
alonsodhv said:
Hi!
Did you have any luck installing the update???
I'm getting the same error but for youtube.apk!!!
H
Click to expand...
Click to collapse
I also have the exact same problem!! Were you able to find a solution?

[Q] System Update after CWM/Root

So did anybody get a system update msg after rooting and flashing CWM?
I didn't even know this was possible to get OTA updates after putting CWM on..?

people may get the messages they will also be able to download it but when it comes to installing, it will fail with custom recovery and it will remove root if you have stock recovery but root.

I managed to install it with CWM, it linked me right into CWM and asked me if I want to keep root etc.. I think CWM may have updated a few things.. Because it was fully possible.

So what update is this??
Sent from my Nexus 4 using xda premium

UKROB86 said:
I managed to install it with CWM, it linked me right into CWM and asked me if I want to keep root etc.. I think CWM may have updated a few things.. Because it was fully possible.
Click to expand...
Click to collapse
After reading this I went ahead and attempted the system update on my stock/rooted ROM with CWM.. And you're totally right. Flashed. Fixed recovery so it didn't replace stock, and fixed root so it stayed. Totally awesome. Never heard of this before.
Sent from my Nexus 4 using xda app-developers app

BraydenJames said:
After reading this I went ahead and attempted the system update on my stock/rooted ROM with CWM.. And you're totally right. Flashed. Fixed recovery so it didn't replace stock, and fixed root so it stayed. Totally awesome. Never heard of this before.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
How is this possible? Did u use the OTA update?
Sent from my cm_tenderloin using Tapatalk

BraydenJames said:
After reading this I went ahead and attempted the system update on my stock/rooted ROM with CWM.. And you're totally right. Flashed. Fixed recovery so it didn't replace stock, and fixed root so it stayed. Totally awesome. Never heard of this before.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
what you meant fixed recovery and fixed root.
You fix it manually after OTA, or the CWM recovery is still there after the update?

OTA updates have been flashable with custom recoveries on a nexus for a long time. I only say long because I cant remember for sure back in the n1 days. But this nothing new.
FYI. Ota will flash just fine with root. With a custom recovery. With a unlocked bootloader. They will not relock your bootloader.

Emama said:
what you meant fixed recovery and fixed root.
You fix it manually after OTA, or the CWM recovery is still there after the update?
Click to expand...
Click to collapse
Like CWM asked me if I wanted it to fix it... Haha.
Sent from my Nexus 4
---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------
jimmyz said:
How is this possible? Did u use the OTA update?
Sent from my cm_tenderloin using Tapatalk
Click to expand...
Click to collapse
Yep. It popped up, and I updated. Voila.
Sent from my Nexus 4

albundy2010 said:
OTA updates have been flashable with custom recoveries on a nexus for a long time. I only say long because I cant remember for sure back in the n1 days. But this nothing new.
FYI. Ota will flash just fine with root. With a custom recovery. With a unlocked bootloader. They will not relock your bootloader.
Click to expand...
Click to collapse
Thanks. I have been going back the stock recovery before I flashed ota on my gn- guess I didn't need to do this!
Sent from my cm_tenderloin using Tapatalk

I just came here to ask this. It errors out with TWRP. Looks like I'm going back to CWM.

hey guys, when I try to boot into recovery there is an android laying down with red exclamation mark... what do? I'm trying to update to 4.2.1.. Should I just wait until it arrives on my device?

jaestreetss said:
So what update is this??
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
4.2.1 and yes it's confirmed that CWM can perform regular OTA system updates, while keeping ROOT etc.

UKROB86 said:
4.2.1 and yes it's confirmed that CWM can perform regular OTA system updates, while keeping ROOT etc.
Click to expand...
Click to collapse
Yup, worked for me.

Ajfink said:
Yup, worked for me.
Click to expand...
Click to collapse
Not here...
These errors popped up in CWM Touch 6.0.1.9:
E: failed to verify whole-file signature
E: signature verification failed
It asked if I want to install the untrusted package. After selecting yes, I get Status 7 Installation aborted.

To help anyone else, I flashed root/cwm on my device right out of the box, and couldn't install the OTA update from Google. Message just says "Waiting to reboot..." and logcat shows this error:
Code:
I/CheckinTask( 986): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
D/SystemUpdateActivity( 986): status=4 mobile=true batteryState=0 roaming=false lastCheckinTime=1354311432182 mSetupWizard=false
I/SystemUpdateService( 986): download in progress: [id: 103 compl: true succ: true bytes: 39806693 reason: 0 fn: /cache/609c838b9a40.signed-occam-JOP40C-from-JVP15Q.609c838b.zip]
I/SystemUpdateService( 986): file has been verified
E/SystemUpdateService( 986): OTA package doesn't exist!
V/SystemUpdateService( 986): called install()
E/SystemUpdateService( 986): OTA package doesn't exist!
Not sure why I'm getting that error message. Anyway I ended up downloading the package directly from Google here:
http://android.clients.google.com/p....signed-occam-JOP40C-from-JVP15Q.609c838b.zip
Then booting into CWM and installing it from sdcard.
When you reboot CWM will ask you if you want to keep CWM and also root, hit 'yes' on both. Seems to have worked great and I now have Photo Sphere!

Thanks for ur posts mates, was worried of loosing root and cwm right after I got it
But CWM updated perfectly!

bitpushr said:
To help anyone else, I flashed root/cwm on my device right out of the box, and couldn't install the OTA update from Google. Message just says "Waiting to reboot..." and logcat shows this error:
Code:
I/CheckinTask( 986): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
D/SystemUpdateActivity( 986): status=4 mobile=true batteryState=0 roaming=false lastCheckinTime=1354311432182 mSetupWizard=false
I/SystemUpdateService( 986): download in progress: [id: 103 compl: true succ: true bytes: 39806693 reason: 0 fn: /cache/609c838b9a40.signed-occam-JOP40C-from-JVP15Q.609c838b.zip]
I/SystemUpdateService( 986): file has been verified
E/SystemUpdateService( 986): OTA package doesn't exist!
V/SystemUpdateService( 986): called install()
E/SystemUpdateService( 986): OTA package doesn't exist!
Not sure why I'm getting that error message. Anyway I ended up downloading the package directly from Google here:
http://android.clients.google.com/p....signed-occam-JOP40C-from-JVP15Q.609c838b.zip
Then booting into CWM and installing it from sdcard.
When you reboot CWM will ask you if you want to keep CWM and also root, hit 'yes' on both. Seems to have worked great and I now have Photo Sphere!
Click to expand...
Click to collapse
I have the same problem you had, the phone wasn't rebooting in recovery. I've tried another way! since I bought my phone today, the first thing I did was rooting it and installing cwm recovery. my phone cames with jb 4.2 and was trying to updating to 4.2.2 but failing to reboot, so I performed a wipe and then he re-downloaded the whole package. the first time the ota updater said he couldn't verify the package, it continued repeating it a few times and then I received the notification to update. this time he managed to reboot the phone and cwm rec started, but it said it couldn't verify the package signature and labeled it as untrusted package... scared, I didn't installed it.
back to the ota screen, it was convinced I updated the phone so it was continuing to say it was updated. I deleted the data of google services framework and i had again the invitation to update to 4.2.2. the package was downloaded and verified at the first try and I tapped install.
then again, cwm said the package was untrusted... is that normal?

[SOLVED] Stuck in TWRP Recovery after failed Update to Kitkat

So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom

tom1807 said:
So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom
Click to expand...
Click to collapse
i am in the same boat

Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there

tom1807 said:
Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there
Click to expand...
Click to collapse
TWRP is fine. Myself and others have installed the OTA via TWRP without issue. Did you download the OTA with Goomanager? I can't think of another reason the OTA zip would be in there, but let me know otherwise.
If that is the case, download the ota http://android.clients.google.com/packages/ota/google_nakasi/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip from Google's servers, push it to /sdcard/Download/ via adb and try again.

Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk

tom1807 said:
Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you modified any system apps, build.prop, kernel, etc?

No, not at all. Only root and twrp
Edit:
Exact error message: set_metadata_recursive: some changes failed

Problem solved:
Followed this guide (except the bootloader-grouper-4.23.img and KitKat is booting

Nexus 7 2012 automatically boots into recovery
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.

nolan111 said:
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.
Click to expand...
Click to collapse
He flashed the 4.3 JWR66Y factory image and then installed the OTA.

comminus said:
He flashed the 4.3 JWR66Y factory image and then installed the OTA.
Click to expand...
Click to collapse
Yup that is what I had to do. I flashed the factory image with WugFresh's NRT. I accidentally deleted the OS as well from my tab. Thankfully I had saved a copy of TB on my PC. TB saves the day yet again. However, I was still not able to sideload the OTA for KitKat. I keep getting Error: Device not found error message on command prompt? I guess I'll wait for the factory image to be uploaded by Google and then flash the files.

Nexus 7 grouper, manual update fails

I have a Nexus 7 (2012, grouper) which so far I have kept on 4.1.2 (JZO54K) using FOTAkill, but now I want to update to 4.2.2. I also have the latest CWM recovery (6.0.4.3).
I plan on applying successively:
094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
then
659e6288b87d.signed-nakasi-JOP40D-from-JOP40C.659e6288.zip
then
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Using ADB I tried to apply the first update, but it fails. I also tried applying it from /sdcard, but the same thing happens. The error message happens after "verifying current system..." and it consists of:
assert failed: apply_patch_check("/system/app/Browser/ProviderProxy.odex", "21a896ab...
E: Error in /data/media/094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
(status 7)
I tried downloading the zip update again, but it still fails. I downloaded it from http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip

Does the fact that by bootloader is locked have anything to do with this error?

...and the answer is no. Even with bootloader unlocked, the update still fails with the same error.

FWIW I haven"t solved this. Can anyone help me, please?

jh1521 said:
FWIW I haven"t solved this. Can anyone help me, please?
Click to expand...
Click to collapse
Flash the latest factory image, much faster and simple

GtrCraft said:
Flash the latest factory image, much faster and simple
Click to expand...
Click to collapse
I don't want android 4.3, 4.4 or 5 on it, I want 4.2.2. I cannot find any factory images for 4.2.2.
(edit) I was looking in the wrong place, I did find a nakasi image for 4.2.2. I will try that.