• Posted byby Kellen

Download: Nexus 7 “nakasi” Android 4.2.2 JDQ39 Update

Android 4.2.2 Nexus 7

As expected, the rest of the Android 4.2.2 (JDQ39) files for Nexus devices are starting to become available. Here is the link for the Nexus 7 “nakasi,” which is the WiFi-only version.

In order to update using this file, you’ll need to come from JOP40D. 

Download Link

Instructions (Custom Recovery):

1.  Download the file from above to your internal storage.
2.  Temporarily flash a custom recovery if you haven’t already.

Windows | Mac

3.  Reboot into recovery.
4.  “Install zip from sd card.”
5.  Choose the new JDQ39 update file and install.
6.  Enjoy.

Instructions (Without Custom Recovery or Root):

*If you want the full detailed instructions, hit up this guide.

1.  Download and install the Android SDK.
2.  Make sure adb is working correctly by typing in “adb devices” into a command prompt.

*You should get a serial number in return if your device is detected.

3.  In the same command prompt, type in “adb reboot bootloader” to reboot to fastboot.
4.  From the bootloader screen, scroll down to “Recovery” and select it.
5.  If you see an Android with an exclamation mark, press Volume Up and Power to move past to recovery.
6.  From the stock recovery, choose “apply update from adb.”
7.  In adb type “adb sideload 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip”

*You could also rename the .zip file to something easier to type like “JDQ39.zip” as well.

8.  If it works correctly, you should be taken through some online instructions.
9.  Select “reboot” and enjoy.

Cheers G.O.D.!

Written by

Kellen

It’s not often that you get to merge personal passions into a professional life, but that’s what Kellen did when he launched Droid Life in 2009. After working years of unsatisfying jobs in the medical and property management fields, he took a risk to try and create an online community while playing with the coolest gadgets on the planet each day, a risk that has turned out to be incredibly rewarding. Outside of Droid Life, Kellen is your typical Portlander who drinks way too much good beer, complains often about the Trail Blazers, and can be found out on the streets for a run, rain or shine.

Post navigation

64 Comments

  • Did this update introduce gesture typing? Or did I just not notice it in previous versions? It’s pretty cool.

  • i need some help
    i have clock work mod recovery touch and when i try to flash this zip the nexus 7 says e: eror in sdcard/0/longname for update.zip (status 7) cna some one help meeeee pleeeease

  • Is anyone else seeing repeated crashes of “com.android.phone” after the upgrade (even in safe mode)? My device was running stock JOP40D, unrooted. I’m about to do a factory reset on it, but wanted to see if anyone else had run into this.

    • I’m having that exact same issue. Have you been able to fix it? I haven’t factory reset it yet and would rather not but if that’s the only solution then I will. Thanks.

      • I finally just gave up and did a factory reset, but that turned out to be not enough for me. What I ended up doing was flashing a stock recovery image of JOP40D, then reapplying the upgrade to that. Since then, everything has been fine – no idea what caused the issue in the first place.

        • Thank you for the response Mark. I will try to factory reset it first to see if it works. If it doesn’t then I will flash a stock recovery image as well but I’m not sure how to do it. Did you find a tutorial or did you already know? Could you help a fellow Nexus 7 owner out? Thanks! 🙂

          • Hi Diane,

            I had done it before, but that was after reading the excellent tutorial at http://forum.xda-developers.com/showthread.php?t=1907796.

            The hardest part for me was getting the drivers set up so my computer would recognize the Nexus 7… this could be challenging, since, if you haven’t turned on “developer mode” for your device, it will be difficult to get to this screen with com.android.phone constantly crashing.

            Good luck!

            Mark

          • Hello Mark,

            I’ll check out the tutorial, definitely looks like I need to sit down for this as I’m not very familiar with such a procedure. And as you said, it definitely will be challenging to turn on “developer mode.” Thanks for your all your help! 🙂

  • lost root – and now adb always shows my device “offline” no matter what I do. Haven’t had a problem connecting with adb before now… Tried to boot into recovery but got the red exclamation point. Sigh.

    • Your post helped me, thanks. I replaced adb.exe and other files (fastboot and the two .dll’s) in C:Program Files (x86)WugFresh Developmentdata with the latest version of adb.exe. After that, the Nexus Root Toolkit worked properly and I just re-applied Root. It seems to have worked!

  • 1. Error 7 cannot flash, then fake-bricked by bootlooping. 2. Grouper is the device name, even says it in the fastboot, not Nakasi, that’s why when you download a ROM, you make sure it says “grouper”

  • Nexus 7 32GB 4.2.1 ROOT and CMW 6.0.0.19

    CMW error 7 applying the update, maybe work with stock recovery..

  • Hey DL, If I follow the custom recovery steps I’ll lose root, right? I read that the latest CWM might actually keep root. But if we lose it, I can flash superuser in recovery right? Or use Wug’s toolkit to restore root?

    *might be worth including this info in the main post… just sayin.

    • Before flashing, open SuperSU and go to the Settings tab. Check the Survival Mode checkbox. Reboot to recovery and flash the zip. After rebooting, go back to SuperSU settings, uncheck enable Superuser, and recheck it again. You MAY need to re-install Busybox. I did, but not sure if it was needed. I needed to re-enable Seeder, but all other root apps just worked.

    • If you have the latest CWM it will ask you if you want to restore root and disable stock recovery. If you want you can do as Alan says or download VooDoo OTA Root Keeper.

  • Take note that if you are running a custom kernel the update will fail, you need to make sure you restore the stock kernel image. You did make a backup…right?

  • After downloading an app it gives you an eta of how long the download will take.
    I’m pretty sure it didn’t do that before, someone correct me if I’m wrong.

      • Damn, I was hoping it would be better. After 4.2.1 it has been slow as well. I used the app forever Gone, and that has helped speed it up, but not the greatest as 4.1. Thanks for reporting!

    • I think the changes are mostly Bluetooth oriented. No real performance enhancements under the hood in this one. I’d bet they’re saving the good stuff for Key Lime Pie.

      • Too early to make a definitive conclusion (and maybe things still need to settle down a bit) but right now it seems to be unchanged from 4.2.1 or at best maybe a tad less laggy when swiping the lockscreen open and switching users (if you have multi-user enabled on your N7).

        Definitely still more sluggish than 4.1 was.

        The only thing I have noticed definitely fixed is the bug where you had to often hit the power button multiple times to get the screen to come on. I just wiped my N7 about a week or two ago and it was still exhibiting this behavior in totally stock JOP40D. It seems to be totally resolved now.

        • Finally, That power button lag was crazy annoying. Hopfully the launcher is less laggy than 4.2.1. Going through my apps was extremly choppy, especially when I got to the wigget section. Also If they fix the battery drain and brightness bug ill be fine. I had a Stock Droid X for 2.5 years, so I can deal with a little lag lol.

Comments are closed.

back to top