Android 4.2.2 (JDQ39) for takju Galaxy Nexus now available to download and manually install


Last night, Google started pushing Android 4.2.2 (JDQ39) to the GSM Galaxy Nexus, Nexus 7, and Nexus 10. Unfortunately a lot of people are still waiting for the update to hit their devices, but if you have the takju Galaxy Nexus (The one bought from the Play Store), then you can download the Zip file and update it yourself. Again, we don’t have the changelog, but we are pretty sure that this update will at least fix the known Bluetooth streaming bug, among other things.

In order to do the update your device needs to be running build JOP40D. If you already have a custom recovery, you can just download the Zip file {linked below), copy it to your device, and flash. If you’re running the stock recovery, then download the Zip file (linked below), but leave it on your computer and follow these instructions:

You will need the latest version of adb in order to proceed. Just download the latest Android SDK to make sure you’re up to date.

  1. Power off your takju Galaxy Nexus, and power back on by holding the Volume Up and Volume Down buttons while it boots.
  2. The fastboot menu should appear and you should see “Start” in the top right. Press Volume Up till it changes to “Recovery.” Press the Power button to select it.
  3. You will see an Android with a red exclamation point icon, press Volume Up and the Power button at the same time.
  4. You will get a new menu and you can navigate to “apply update from adb.”
  5. Now it’s time to connect your takju Galaxy Nexus to your computer via a USB cable
  6. Open the command prompt in Windows (cmd in Windows, regular shell in Linux and Mac) and navigate to the directory that the Zip file is located in.
  7. Type: adb sideload
  8. The update will install and reach 100%.
  9. Reboot and enjoy Android 4.2.2


Download takju build JDQ39 from Google’s servers. **This is ONLY for the takju version of the GSM Galaxy Nexus!!

source: AndroidPolice



About the Author: Robert Nazarian

Robert lives in upstate New York where he was born and raised. Technology was always his passion. His first computer was a Radio Shack TRS80 Color that used a cassette tape to save programs, and his first laptop was a Toshiba T1200FB that sported a CGA greyscale screen and two 720kb floppy drives (no hardrive). From the early 90’s through late 2011, he only owned Motorola phones starting with the MircroTAC all the way through to the Droid X. He broke that streak when he bought the Galaxy Nexus. Now he's sporting a Galaxy Note 4, and absolutely loves it. He has a wonderful wife and a 6 year old son. In his free time he enjoys sports, movies, TV, working out, and trying to keep up with the rapid fast world of technology.

  • Charles Rodowski

    Bad news, looks like 4.2.2 bluetooth still broken when it comes to connecting address books to BMW idrive systems(’06 e90), back to 4.1.2 I go!

    • Digilus

      I was all excited to get it my Nexus working with my Audi again – but no luck. It connects via bluetooth then a second later – disconnects. 4.1.2 is looking attractive :(

  • Tsmi

    Hi, i have recently used a guide to manualy update my phone from 4.0 to update my phone to 4.2.1 (Android 4.2 for yakjuxw). I tryed to sideload the 4.2.2 today (i have takju) after the official update failed and was surprised to see that the sideupdate did not apply also! Any suggestions on how to fix this or why the update did not apply?
    I have Andoid System Info-App which states that my ID is JOP40D, Produkt: takju aund Device: maguro

  • NK

    My G Nexus Build Number is JOP40D.

    Android Version: 4.2.1

    I installed the Android SDK on my Windows System and tried the steps given above.

    in Command Promt:

    1. “adb devices ” .. does not list my device
    2. “adb sideload ” did not run. Gives me some error kind of help options.

    Can somebody tell me if I am doing something wrong in my process of updating?


    • Charles Rodowski

      First, do you have adb debugging enabled in the developer options? If not then simply open settings->about phone, then tap the build number field about 7 times to enable developer settings. Then enable adb debugging under developer options. If you don’t see your phone under adb devices then check your usb drivers. Finally, you’ll need adb version 1.0.29 or higher to use the sideload command, check with “adb version” command.

      • NK

        Hey Chrales,

        Thanks for your input.

        Well, I was literally frustrated with adb and the functionality, out of that I went ahead to do my G Nex to Factory Reset.

        And Bammmh… after reset, 1st thing that started was Android 4.2.2 update available! :)

        Only thr’ Wi-Fi!

        Love Google and Nexus!

        That could be one way of getting that update ha!

  • vlad7777

    Hi, I have 4.2.1 rooted and TWRP installed. The OTA update was sent to my Nexus 7 but after it runs – it reboots into TWRP and then when I reboot into system – I am still with 4.2.1.
    I tried sideload – ant this also runs, but in the end I am back to 4.2.1.
    I think there was some file that I changed the extension of some file to “bak” to prevent stock rom from overeriting TWRP and unrooting the device, but I do not remember which file it was.
    I think that this blocks the update process.
    If anyone can help – I would appreciate
    Best regards