This article was written by John Lieske of johnlieske.com and submitted to us. All we’ve done is pretty it up a little bit and posted it for all you Nexus lovers out there looking to manually update to Android 4.2.2. Enjoy!
The latest Android Jelly Bean build, Android 4.2.2, is currently rolling out to Nexus devices and is receiving positive reviews. Some of you may be having some trouble getting the OTA update, and for some Nexus 10 users you may be finding that the OTA is failing to install. This brief walk-through will take fellow rooted Nexus owners along the steps to getting Android 4.2.2 safely installed without resetting your device.
The main thing preventing many rooted users from updating over the air (OTA) is the custom recovery. In the past, the OTA update would check the recovery on the device, and re-flash the stock Android recovery in its place during the reboot. These are easily protected by the popular custom recoveries these days, so getting the update started is the only real challenge. I’ll describe different methods you can use to start the Android 4.2.2 update, beginning with the least difficult and concluding with sideloading via the Android Debugger (adb).
Note: everything below is working from the assumption that you’re running stock Android and not a custom ROM. If you have a custom ROM installed, you’ll have to find an updated version of that ROM to get Android 4.2.2 on your device. Otherwise you’re going to have to download your stock image from Google and install the factory image fresh (which will erase everything).
The first thing that rooted users should try is going to Settings >> Apps >> All and scrolling to find Google Services Framework. Tap the “Clear Data” button and confirm by tapping “OK”. From there, use the back button to get to the main Settings screen. Scroll all the way down and tap About Phone (or About Tablet on the Nexus 7 and Nexus 10), then tap System Updates. You’ll see the “Check Now” button to have the device check for updates, and you should notice that the last time the device will be reporting it checked was back in 1969 (which I like to pretend is an artifact of time travel). Tapping “Check Now” should result in beginning the download of Android 4.2.2 and update process for many. It will ask you to confirm that you want to install the update.
Most root users already know that updating the device will remove your root. There are a few ways around this. Clockwork Mod recovery can not only protect itself from being over-written, it can also attempt to retain your root for you. For my own devices, I prefer to use OTA Rootkeeper by Project Voodoo. As long as the update doesn’t format or overwrite the /system partition, OTA RootKeeper helps to maintain a working root (including backing up your su binary).
If you can’t get the update over the air, your next best bet is to flash the update from your recovery. This involves downloading the update, moving the update to your device, then booting your device to recovery and initiating the install.
The first step is finding the Android 4.2.2 update. You can download the Nexus 7 update here, the Nexus 4 update here, and the Nexus 10 update here. Download these to your computer, transfer them to your device in whatever manner suits you best, and reboot into recovery. For those who aren’t used to it, booting to recovery is pretty simple on a Nexus: you power down the device, and then power it up while pressing (and holding) the volume up and down buttons.
You boot to a screen with a big (green) colored arrow pointing to where your power button is, and Andy the Android in the background. From here, you can use the volume up and volume down to choose different boot options. Boot to recovery by pressing volume up or down until the arrow is red and says “Recovery mode”, then pressing the power button.
Once in recovery, you’re going to want to find the option to install from a zip. This should require you to specify a zip, which is the file you saved to your device. Install the Android 4.2.2 update from that zip file, then reboot your device. The update will run its final steps before you boot to the lock screen and can enjoy the Andriod 4.2.2 goodness.
This method assumes you have adb installed. This also assumes you’re updating from 4.2.1 and not an earlier build. If you’re not sure or you have adb installed, you can probably find a good set of instructions here. As always, use at your own risk. This method has also been covered before.
Plug the USB data cable from your computer to your device. Be sure you have the Android 4.2.2 update file for your device– again, grab the Nexus 7 update here, the Nexus 4 update here, and the Nexus 10 update here. Once the file is downloaded, move it to the same folder where ADB is located. Using the steps described above in the previous method, boot into recovery. Within the recovery mode menu you should find the option to “sideload” or “apply update from adb”.
At this point, you must open a command-line window on your computer to run the adb commands. You may need to change directory to your ADB folder. These are the commands that you will run for your device:
adb sideload de8b8d101614.signed-occam-JDQ39-from-JOP40D.de8b8d10.zip
adb sideload 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
adb sideload eaef14432ff5.signed-mantaray-JDQ39-from-JOP40D.eaef1443.zip
After you run these commands, you’ll see a progress bar as the update loads onto the device. The progress will reach 100% and then you’ll see the device installing the update. The update will finish, at which point you can reboot the device from the recovery menu. As Android completes booting up it will run the final install processes, and then you should be at your lock screen.
Once the update completes, enjoy Android 4.2.2!
There are some Nexus 10 devices that will hit an error during the Android 4.2.2 update process. This is because there’s corruption on the system partition of the device that’s causing the update to fail. The symptom for this is a ‘Status 7’ error during the install process. For me it was when the ‘set_perms’ process was showing during the update.
To fix the problem you need to run the e2fsck command on the device, but you must do it through adb on your computer. The way you do this is by following all of the directions I gave above to prepare for sideloading the update, but instead of running the sideload command, you must run the following:
adb shell “e2fsck -y /dev/block/platform/dw_mmc.0/by-name/system”
(Include the quotes above, since they contain the command being run on the device)
The command above will only work on the Nexus 10. If you’re experiencing this symptom on other devices do not run the command as shown above. Improperly using e2fsck can ruin your partition table on your device, bricking it. For help walking through fixing corrupted partitions on other devices, I strongly recommend finding someone who is familiar with the command line and have them help you find your partition layout. It’s not difficult, but it’s also not very forgiving. I came across this specific issue with the Nexus 10 because there was a corrupted update that some people received, which corrupted the file system.
After running the file check above, go back and try to update the Nexus 10 to Android 4.2.2. Try Method 1 first, since the main problem for the update will have been fixed.