I've been trying to update to 4.2.2 all day, but every time I try, Clockworkmod (most current one) gives me several errors error:
the first being: "E: Invaling Command Argument"
Then: "E: Failed to verify whole-life signature
and: "E: signature verification failed"
After which I have to accept to install this "untrusted zip" -- I select 'yes', obviously.
After that, this last error occurs and the installation gets aborted: "assert failed: apply_patch_check( "/system/app/SystemUI.apk" blablabla...*load of text* blablabla... "(Status 7)"
I honestly don't know what's going wrong, or whether this is just some stupid question...I already thought it might be a problem of Clockwordmod or the fact that I'm rooted, but I'm not sure, and I don't want to waste my time unrooting, updating and rerooting again if it turns out to not make a difference.
If I have to uninstall Clockwordmod, could you please tell me how? Or should I just keep on trying?
Manually updating isn't really an option for me...I tried it... once...and, well, I ended up stressing all day because I was afraid I completely ruined my phone xD
Thanks in advance
And sorry for any grammatical or spelling errors!
(not completely sure whether this is important information, but well:
I'm running stock Android 4.2.1 yakju on my GSM Samsung Galaxy Nexus; rooted and unlocked; installed Clockworkmod 220.127.116.11 through ROM Manager; flashed yakju over my original yakjuxw; and updated through that forced-update-trick where you clear all data of Google Services Framework; and have been messing around with apps like Ful! Screen and LMT lately (uninstalled both))
I got excited with the update my nexus 7 pulled today, but I got an 'error' message (with a broken droid on it's back) at the very start of installation. After restart it went back to 4.2.1 and no sign of an update to download.
Running stock 4.2.1 on rooted 16g N7
My Nexus 4 also gave the "Error" message when trying to install the update. It has an unlocked bootloader and was rooted, but otherwise completely stock. I had to do a factory reset for the update to install successfully.
My wife has a Galaxy Nexus, and hers also has an unlocked bootloader and is rooted. The update installed just fine, and the phone didn't even lose root.
I'm getting what appears to be exactly the same error as MrFlipnote.
First, some details of my system:
Hardware: Nexus 7 wi-fi only
Current Android version: 4.2.1
Current kernel version: 3.1.10-g22b4fcd #1 Fri Nov 2 10:55:26 PDT 2012
Current build number: JOP40D
Rooted prior to this update.
ClockworkMod Recovery v.18.104.22.168.
I first attempted to install the update after receiving the official notification that the update had been downloaded and was ready for installation: I clicked on the notification message, followed the prompts, and received the same error messages whose details I will give below.
Since then I have downloaded the update separately from -
- then attempted to invoke an update as follows:
On the (Ubuntu) PC, in a terminal:
1. [cd to the location of the downloaded zip.]
2. adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /sdcard/
3. adb reboot recovery
That reboots the Nexus 7 to CWM Recovery mode. Then, on the Nexus 7:
1. Select menu option: Install zip from sdcard > Choose zip from sdcard.
2. Select folder "0", then scroll down to the pushed zip file and click it.
3. Click "Yes - Install 6ece[...].zip
Whereupon I get the errors listed below.
Things I've tried (followed by a repeat of the process above):
* In CWM, selecting option: Wipe cache parition.
* In CWM, selecting option: Advanced > Wipe dalvik cache.
* In CWM, selecting option: Fix permissions.
* In CWM, selecting option: Install zip from sdcard > Toggle signature verification.
None of those worked.
The error messages as reported on-screen on the tablet are as follows, when I attempt the update with signature verification switched off (with verification turned on, I also get the "signature verification failed" error reported by MrFlipnote):
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
UPADTE: that DID NOT work. haha. the update still gave me the same error. and I just got stuck on the boot animation screen. (waited 15 minutes, then did a battery pull ) I am doing a restore now, and will patiently wait for a better solution.
I'm having the same issue. After I create a backup I am going to try flashing a stock system img and then try the update again per this link:
Will update everyone with the results as soon as i'm done. ::fingers crossed:: wish me luck!
Last edited by its_lucky; 02-17-2013 at 04:00 PM.
Reason: UPDATE on situation
I've fixed the problem largely thanks to the following page, which explains that it is caused by the SHA-1 hash code (used as a kind of file version identifier) of one or more files on the system not matching the hash expected by the updater - because some program has unexpectedly modified the file:
In my case the problematic file was /system/build.prop, so I needed to find a clean copy of that file from my (as was) *current* version of Android, namely 4.2.1. That is no longer available from Google but it is available from this site:
I was a little dubious about downloading images from a third-party site, but it seems above-board and I've had no problems.
I wanted the 4.2.1 JOP40D image file listed on that page, nakasi-jop40d-factory-6ac58a1a.tgz. Inside the .tgz file was a .zip file, and inside that was the system.img file that contained the file that I was after - but it wasn't easy to get to: I needed to mount the .img file first.
I used this page -
- which explains how to use two programs called simg2img and make_ext4fs to mount .img files and make new .img files (I only needed the first). You can do this in any folder (I did it from my Downloads folder):
Then go into the newly created sys folder and find the file that you want.
I took a copy of build.prop from there and used adb to push it to the /sdcard folder on my Nexus 7. On the Nexus 7, I then used ES File Explorer (as root) to rename the existing build.prop file to something else and paste the new build.prop in its place.
Only at this point did I notice that there were already three backups of build.prop in the /system folder. It might have sufficed to take the most recent of those, and use that as my new build.prop. But since I'd already found this clean instance and had no idea about the state of those backups, I didn't try that approach.
I then repeated the update process as described in my initial message (from "adb reboot recovery" onwards). This time, the update proceeded without any further hitches. I now have Jelly Bean 4.2.2! What I don't have is the Sunday afternoon that I wasted working out all of the above.
I hear ya! I also spent Sunday afternoon trying to figure it out, only to fail. heh.
well, congrats on finding the solution! and thanks for the links and walkthrough!
now I'm debating if I want to spend more time on what seems to be such minor update. if you don't mind my asking, in your opinion, was all that work worth it?
I followed AndroidPolice's adb walkthrough, very easy, lemme go hunt a link brb Ok, here it is; http://www.androidpolice.com/2013/02/13/the-nexus-4-finally-gets-android-4-2-2-jdq39-as-well-here-are-instructions-for-installing-it-manually/
hello there thanks for the guide...but will the future updates require the same steps to update?or will it update automatically (settings>about phone>software update)?
and plz try to include a video ,thanks in advance