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

[Q] unable to update my n7 3g to android 4.2.2

when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.

Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"

bftb0 said:
Hmmm, I notice you said "unroot"
stock recovery or custom?
That assert is there to insure that it is only flashed to a tilapia/nakasig (3g) N7
The getprop values in question are being read from the *recovery*, not the installed ROM... so, the most reasonable conclusion is that you have a custom recovery or stock recovery from a grouper device installed on your (tilapia) 3g N7.
Flash the stock tilapia recovery there and try again.
This would be an unreasonable hypothesis for a never-rooted tab, but you did say "unrooted"
Click to expand...
Click to collapse
Hi!
im having the same problem, Nexus 7 3G is rooted with custom recovery...
is there a way to install the 4.2.2 update with custom recovery or do i have to return to stock?
thank you!

R: [Q] unable to update my n7 3g to android 4.2.2
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk

Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?

mouse100 said:
You are maybe using a recovery for grouper. Just flash the right tilapia recovery and all should works.
Nexus 7 3G - Tapatalk
Click to expand...
Click to collapse
thank you , ill flash it as soon as i get home and check if it works!

azfarmiera said:
when i try to upgrade my n7 3g using OTA or manual update i will give me a message
'assert failed: getprop("ro.product.device") == "tilapia" ll getprop("ro.build.product") == "tilapia" E : Error in /sdcard/0/357318e165a8.signed-nakasig-JDQ39-from JPO40D.357318e1.zip (status 7) Installation aborted.
i used 4.2.1 stock rom
locked bootloader
unroot.
Click to expand...
Click to collapse
hey there.i get the solution.i just flash stock recovery and wait until OTA update notification on phone and it will update 4.2.2.thank for your help

bisco said:
thank you , ill flash it as soon as i get home and check if it works!
Click to expand...
Click to collapse
just flashed openrecovery-twrp-2.4.1.0-tilapia.img recvery file but update still does not work

bftb0 said:
Flash the stock tilapia recovery there and try again.
Click to expand...
Click to collapse
Is just the stock recovery posted somewhere? I can't seem to find it.
Sent from my SGH-I777 using xda app-developers app

rthisp said:
Hum... I had this kind of problem, I guess.
I searched many threads when I rooted and unlocked my Nexus 7 3g, to avoid this "status 7" problem.
I chose Wug´s nexus toolkit, unlocked and rooted my device. After that, I installed, via toolkit, the TWRP recovery.
When I received the system update notification, my device asked me to reboot, then a screen of TWRP appeared to me. I just rebooted the system and now, without update, I don´t even get the message again.
I assume that the Wug´s toolkit flashed a grouper version of TWRP. What I have to do now ? I would like to do the things manually. Maybe flash a factory image from here with this method.
I´m very noob with this kind of thing, because I still have a old milestone 2 with a locked bootloader. The method to flash ROM in milestone 2 is quite different...
Anybody can help me ?
Click to expand...
Click to collapse
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.

theBeachBoy said:
Found how? Same here with cwm... Chose reboot and now still on 4.2.1 and no more ota update available... Even when I check for updates.
Click to expand...
Click to collapse
finally I found it. took so long I almost abandonned
I had to use stock recovery and adb sideload the zip file, it would not work with CWM eveb if I manually edit the script to skip that assert line, it would crash later in the modem part of the update.
Also, if you have a 3G version you need to use nakasig instead of nakasi, I have used the link from there to get the zip file: http://forum.xda-developers.com/showthread.php?t=1745781

Error updating to 4.2.2

The 4.2.2 update for my Nexus 7 came OTA today, but did not complete due to an unspecified error. Now my N7 says there are no updates available when I have it check, but according to my "About Tablet" screen, I'm still at 4.2.1. I tried manually installing the update, but to no avail.
I'm using ClockworkMod 6.0.2.3 as my recovery tool, and the name of the file I used to attempt to manually update is 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip. I also attempted a factory reset to start over, but this has been unfruitful as well. Same with installing the 4.2.2 ROM through ROM Manager v5.5.2.1 and downgrading to 4.1.
Results from manual updating through ClockWorkMod Recovery:
Sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>"...
Restarting adb...
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/framework/core.odex", "4d5d9dd8ba5fc765ccd859b160230c9609d41123", "1dd96f5702237c4b06a2e338aa7c9cc606f8d69")
E:Error in /tmp/update.zip
(Status 7)
Installation aborted

Wow... this hasn't been covered ad nauseum already. You didn't even have to search... there are already multiple current threads in which it is clearly and concisely laid out.
Its because you modified the system. The update is a patch- if any of the files that it must verify before patching are not 100% stock, it will fail. Flash the stock image.
Sent from my Nexus 7 using Tapatalk HD

najaboy said:
Wow... this hasn't been covered ad nauseum already. You didn't even have to search... there are already multiple current threads in which it is clearly and concisely laid out.
Its because you modified the system. The update is a patch- if any of the files that it must verify before patching are not 100% stock, it will fail. Flash the stock image.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
What is the filename of the stock image?

What is your N7 model ??
GB ...
Wifi only or 3G ??

paolocorpo said:
What is your N7 model ??
GB ...
Wifi only or 3G ??
Click to expand...
Click to collapse
I have the nakasi (wifi only N7).

[Q] Nexus 4 won't upgrade to 4.2.2 in any way

[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!

domi_niku said:
[Q] OTA failed and displayed dead Android saying Error! Tried to sideload the zip file using Toolkit 1.6.8 and it didn't go through. Tried to load it using TWRP and this is what I get:
Code:
Verifying current system...
assert failed: apply_patch_check("/system/build.prop". "5a778d005448ec19
E:Error in /sdcard/de8b8...zip
(Status 7)
Error flashing zip '/sdcard/de8b8...zip
I'm running rooted stock ROM, never tried anything else so I don't know how I could have messed up something.
Thanks for any ideas!
Click to expand...
Click to collapse
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot. Also read this thread well http://forum.xda-developers.com/showthread.php?t=2145848.

gee2012 said:
Flash a stock rom and install the OTA through adb sideload with adb and not by a toolkit, worked for me. After that reroot.
Click to expand...
Click to collapse
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?

domi_niku said:
I'm gonna try the stock 4.2.2 ROM, thanks.
It still doesn't the answer the following question: what's wrong?
Click to expand...
Click to collapse
Did you try a different kernel in the past? ie Franco's kernel?

harpo1 said:
Did you try a different kernel in the past? ie Franco's kernel?
Click to expand...
Click to collapse
No, never. I just wiped the phone and installed stock 4.2.2 using the Toolkit and now it won't boot.
EDIT: I guess that's because the Toolkit doesn't support 4.2.2. Oh well just flashed it using ADB. Hope I can get all my app data back...

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