I foolishly allowed the OTA Kitkat update on my unlocked Wifi N7 which was unlocked with the Nexus 7 Root Toolkit. When the update was complete the N7 rebooted to a "dead android" screen with the caption "no command". I did some searching and following this link:
http://www.androidauthority.com/man...kitkat-nexus-7-20122013-wifi-nexus-10-317138/
I tried manually installing Kitkat, but I got this error:
"/system/app/BasicDreams.apk" has unexpected contents
So, I searched on that error, and following the instructions of post #26 at http://forum.xda-developers.com/showthread.php?p=47477551 I now get:
E:failed to verify whole-file signature
Help!
Thanks,
Hackhound
hackhound said:
I foolishly allowed the OTA Kitkat update on my unlocked Wifi N7 which was unlocked with the Nexus 7 Root Toolkit. When the update was complete the N7 rebooted to a "dead android" screen with the caption "no command". I did some searching and following this link:
http://www.androidauthority.com/man...kitkat-nexus-7-20122013-wifi-nexus-10-317138/
I tried manually installing Kitkat, but I got this error:
"/system/app/BasicDreams.apk" has unexpected contents
So, I searched on that error, and following the instructions of post #26 at http://forum.xda-developers.com/showthread.php?p=47477551 I now get:
E:failed to verify whole-file signature
Help!
Thanks,
Hackhound
Click to expand...
Click to collapse
Turn off signature verification and get a copy of a fixed basic dreams.apk that isn't modified, change permissions of the apk to rw RR using root explorer app and then place the apk in system/app
I don't have access to the file but you can wait for a copy of it from someone else on this forum.
Sent from my Nexus 7 using XDA Premium HD app
I eventually resolved the problem by choosing the "return to stock and unroot" option in the Root Toolkit. I selected "Kit kat" for the stock version to go to and the toolkit downloaded and installed it without a problem. I then rooted and installed the custom recovery so everything is good now. Thanks.
Related
Hello guys
I recently unrooted my nexus 7 device because I really want to upgrade to 4.2.1. I tried every possible way. My deice is unrooted, so I tried to update my it from settings, but it goes into custom recovery and saya...
"ClockworkMod Recovery v5.8.4.3
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted"
So I said ok, it doesn't work, so I found the most recent update for the nexus 7 and downloaded it, went to custom recovery, found teh file and tried to update it manually.... This is what is said..
"-- Installing: /sdcard/Download/659e6288b87d.signed-n
akasi-JOP4OD-from-JO40C. 659e6288.zip
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted"
I guess my question is.. what can I do from here? I really want to update it soon
Just download the firmware direct from Google and flash it using fastboot. Easiest and most reliable method, though you do need an unlocked bootloader.
Sent from my GT-I9300 using Tapatalk 2
dr.m0x said:
Just download the firmware direct from Google and flash it using fastboot. Easiest and most reliable method, though you do need an unlocked bootloader.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Can you please explain in detail?
From Google meaning their website? or from settings on the Nexus 7? and what do you meant by a bootloader? which bootloader should I use?
I'm not sure but i think if you want to take ota it might need stock recovery to install and to update manually from custom recovery I think you need the BIG update from 4.1.2 JO??? to 4.2 JO40C as the update from JO40C to 4.2.1 JOP40D is incremental if I'm not mistaken....also you may need to update clockwork mod
Sent from my Nexus 7 using Tapatalk 2
Download the update to your device(it's hosted on these boards) reboot your machine into recovery, and install from zip. It's the way many of us update our devices. There was no need to unroot your device. Your OTA failed to install because of the custom recovery you're using.
I'm using 4.2.1
How do u get the screen to not turn off
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I've got the same issue.
CWMRecovery says the same thing when I want to update by OTA.
I tried to install manually the ZIP file (/cache) by copying it in my /sdcard with CWMR but I had the same script.
I'm rooted, in 4.2 (logic) with CWMR 6.0.1.9 no touch.
Do I have to restore stock recovery or a sideload flash (or fastboot) would work ?
Visa Declined said:
Download the update to your device(it's hosted on these boards) reboot your machine into recovery, and install from zip. It's the way many of us update our devices. There was no need to unroot your device. Your OTA failed to install because of the custom recovery you're using.
Click to expand...
Click to collapse
I am using clockwork recovery. How can I change the recovery?
Easiest way to upgrade stock firmware
http://forum.xda-developers.com/showthread.php?t=1907796
Follow the above link. It walks you through downloading a factory image from google and using fastboot to install it, regardless of what you may have done to your device. Also, if you are doing this, you can go ahead and use the latest image if you want, which puts you at 4.2.
enjoy. :good:
mondokat said:
http://forum.xda-developers.com/showthread.php?t=1907796
Follow the above link. It walks you through downloading a factory image from google and using fastboot to install it, regardless of what you may have done to your device. Also, if you are doing this, you can go ahead and use the latest image if you want, which puts you at 4.2.
enjoy. :good:
Click to expand...
Click to collapse
Cheers. I couldn't really be bothered spoon feeding when I posted earlier and thanks to your link I don't have to.
Sent from my Nexus 7 using Tapatalk 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).
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.
so I was so elated to finally have KitKat. I downloaded the update from one of the sites linked in the General Forum for the Nexus 7, and attempted to adb sideload it. This is what I got:
Verifying current system…
“/system/etc/audio_effects.conf” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What do I do?
Thank you for your help
Should I try to download again? It seems as though I have some sort of audio that messed it up.
Sent from my Nexus 7 using Tapatalk
Here is my audio.conf it talked about:
https://db.tt/TwT6k3ez
Sent from my Nexus 7 using Tapatalk
i had the same problem
i downloaded the lastest 4.3 image from google (https://developers.google.com/android/nexus/images#nakasijwr66y)
you must have a clean and fresh install of it.
trying to flash this via CWM or TWRP recovery failed.
so i extractet the image and used the "flash-all.bat/flash-all.sh"
all user data were gone (i dont care about at my tablet ) but so a could flash the rom.
after that i could flash the update to 4.4
oder esyer now. flash the stock 4.4 image
https://developers.google.com/android/nexus/images#nakasikrt16o
(links are for wifi model)
jma9454 said:
so I was so elated to finally have KitKat. I downloaded the update from one of the sites linked in the General Forum for the Nexus 7, and attempted to adb sideload it. This is what I got:
Verifying current system…
“/system/etc/audio_effects.conf” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What do I do?
Thank you for your help
Click to expand...
Click to collapse
I've attached the original file I extracted from the 4.3 stock image (nakasi-jwr66y-factory-1e503532.tgz).
You can try copying it to /system/etc/ (ensuring permissions are correct) and then retry the installation.
I suspect that if you've been playing around with audio tweaks then it's going to fail on other files too.
If it does, then you can use fastboot to _just_ flash the system.img and you won't lose any of your data.
Same thing happened to me. But it's worse, it's stuck on bootloader and Windows won't recognize the device (unkown device on device manager) so I can't even use adb to flash factory image. I'm really desperate here, anyone here with a tip?
fabulosospucas said:
Same thing happened to me. But it's worse, it's stuck on bootloader and Windows won't recognize the device (unkown device on device manager) so I can't even use adb to flash factory image. I'm really desperate here, anyone here with a tip?
Click to expand...
Click to collapse
Use Wug toolkit to install drivers (it has a couple of possibilities) until it works, then install factory image.
I got it to work on windows 8.1, so it's possible.
I'm having a similar problem. I tried to adb sideload 4.4 that I downloaded from the google website and got an error. Now my nexus 7 is bootlooping at the google logo and returning to twrp shortly after. I can't seem to use fastboot and I've wiped everything. I'm also on a Mac. Any help would be greatly appreciated. I can't seem to figure out a solution.
I received the error message "E: Error executing updater binary in zip '/data/media/0/sideload.zip' "
brian_199 said:
I received the error message "E: Error executing updater binary in zip '/data/media/0/sideload.zip' "
Click to expand...
Click to collapse
You need to post the whole error message, not just that one line.
fozzie said:
You need to post the whole error message, not just that one line.
Click to expand...
Click to collapse
Updating partition deltails...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/0/sideload.zip'
brian_199 said:
Updating partition deltails...
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/0/sideload.zip'
Click to expand...
Click to collapse
There's your problem. You have no /system/build.prop file.
Did you delete it? Have you a backup? You need to get it back on the device.
Edit: I've attached the build.prop from the N7 2012 (nakasi/grouper) JWR66Y ROM.
fozzie said:
There's your problem. You have no /system/build.prop file.
Did you delete it? Have you a backup? You need to get it back on the device.
Edit: I've attached the build.prop from the N7 2012 (nakasi/grouper) JWR66Y ROM.
Click to expand...
Click to collapse
Thank you, I really appreciate it. How can I reinstall the build.prop.zip?
You wouldnt happen to have a stock build.prop for KRT16O would!d you? My dumbass forgot to back mine up before I edited mine to add mods. :banghead:
Sent from my Nexus 7 using xda app-developers app
y0brando said:
You wouldnt happen to have a stock build.prop for KRT16O would!d you? My dumbass forgot to back mine up before I edited mine to add mods. :banghead:
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Just unzip the file
brian_199 said:
Thank you, I really appreciate it. How can I reinstall the build.prop.zip?
Click to expand...
Click to collapse
Just use something like Root Explorer to copy it from your SD card to /system/ (and check permissions are 644 or rw-r--r--).
GMPOWER said:
Just unzip the file
Click to expand...
Click to collapse
thanks, worked like a champ :victory: :victory::good:
I have the same problem.
Verifying current system…
“/system/xbin/dexdump” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
please help me.
very thank you for your help.
supernuta said:
I have the same problem.
Verifying current system…
“/system/xbin/dexdump” has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
please help me.
very thank you for your help.
Click to expand...
Click to collapse
If you can say what device and ROM you're coming from, I can probably post the right version of the file.
I'm from nexus4 jb4.3 JWR66Y occam
thank you very much.
supernuta said:
I'm from nexus4 jb4.3 JWR66Y occam
thank you very much.
Click to expand...
Click to collapse
Here you go.
Hi,my nexus 4 just received 4.4, when it was installing, an error message displayed said there is a signature problem, in stallion aborted. Then when it restarted, it is in the loop in the booting. What should I do now? My nexus 4 is rooted, is it what caused the problem?
ttttkk said:
Hi,my nexus 4 just received 4.4, when it was installing, an error message displayed said there is a signature problem, in stallion aborted. Then when it restarted, it is in the loop in the booting. What should I do now? My nexus 4 is rooted, is it what caused the problem?
Click to expand...
Click to collapse
It probably was a bad download. If you download the OTA file, you should be able to update with ADB sideload
lopezk38 said:
It probably was a bad download. If you download the OTA file, you should be able to update with ADB sideload
Click to expand...
Click to collapse
Hi,
I have the same problem and I tried that. Unfortunately, I got this error:
"set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)"
I guess I can flash a clean image from bootloader, but before that I would like to recover all my data :S
Could I backup my data somehow before that?
(I have root, but I have not custom recovery)