Only for the takju Galaxy Nexus phones running JOP40D

Feb 12, 2013 09:32 GMT  ·  By

Not long ago, Google started to push out the Android 4.2.2 Jelly Bean platform upgrade to its Nexus devices, and the OS is available for the owners of GSM Galaxy Nexus smartphones as a manual download as well.

The necessary file has been found on Google’s servers, weighing 46.4 MB and set to deliver the new JDQ39 build to all takju Galaxy Nexus phones running JOP40D.

Google should deliver the new update to all compatible devices within the next several days, but those who would like to download and install the software before that can already do so.

The new platform release can be found via this link on Google’s servers, and can be installed as usual on the device, as long as there’s a custom recovery available.

For those with stock recovery, however, the process is a bit more complicated, as Android Police notes in a recent article.

In this case, users will need to download the available zip on their computers, then restart the smartphone and enter the fastboot menu by holding the Volume Up and Volume Down buttons while booting up.

Here, they will need to navigate to Recovery by using the Volume up key, then hit the power button to select it. As soon as the Android with a red exclamation mark icon appears, hit Volume Up and the Power button together, and navigate to “apply update from adb” in the new menu that appears.

On the PC, users should make sure that they have a recent version of adb with sideload support (it can be found in the latest Android SDK).

Then, connect the phone to the PC using a USB cable, open a command prompt and type the following command: adb sideload 472aafeb9fe3.signed-takju-JDQ39-from-JOP40D.472aafeb.zip.

The device will install the new update automatically and you’ll be running Android 4.2.2 on it as soon as the GSM Galaxy Nexus has rebooted.

Users without experience in this sort of actions should wait for the official update to arrive. All those who try the manual installation process will do so at their own risk, and they will be the only ones held responsible should anything go wrong during the update.