Share this Story

Download: Android 4.2 Update for Nexus 7 and GSM Galaxy Nexus

If you own the “takju” GSM Galaxy Nexus or a Nexus 7, it’s time to update to Android 4.2. The files are already available from Google (even pushing out to some devices), so depending on the state of your device, your instructions for updating may be different. Let’s get to it!

Download:  JOP40C (Nexus 7) | JOP40C (“takju” Galaxy Nexus)

*In order to use these files, you have to currently be on JZO54K.

Instructions (rooted w/ custom recovery):

1.  Download the file to your internal storage.
2.  Reboot into your custom recovery.
3.  Choose “install zip from sd card” and select the update file you downloaded above.
4.  Tell it to flash it, watch it happen, and then enjoy 4.2.

Instructions (non-rooted):

*Involves some simple adb.

1.  Watch this video –


*You could also try going into Settings>Apps>All> and then finding Google Services Framework. If you Force Stop and then Clear Data on that, sometimes that will trigger the update into being pushed to your device.

Via:  XDA [2]

  • AB

    it keeps aborted any help pls?

  • the force stop worked for me hello 4.2

  • spectremANDROID

    Thanks for the caption below the photo. Neither the video or any other method I’ve seen since the update became available was working for me. I didn’t even have to reboot for this to work. I appreciate it. Droid Life FOR LIFE!!! LOL! Seriously… I appreciate it.

  • dzztg
  • Was trying to do this manually for the last hour or so. This worked perfectly…thanks!

  • am i the only one who doesnt have a camera app for nexus 7 with this update??

  • Ankh-su-Namun

    I have a GNex GSM version. i keep getting a Status 7 Error then installation aborts. any help on this guys?

  • Matty

    You can force your nexus 7 to get the update. Go to settings> apps>all> find Google services framework then force close and clear cache. After that go to about phone in settings and check for update. It should say something like last checked for update November 1970. Can take a few tries before it says 4.2 is available. I did it just then. Photo sphere not supported on nexus 7’s yet 🙁

  • The trick below the video didn’t work for me until I did it, then powered the unit off for a few minutes. When I turned it back on, it updated automatically.

  • My wife just tried this and it forced the update she is Puerto Rico on work as I type this. Settings>Apps>All>Google Services Framework>Force Stop>Clear Data than Check for Update, repeat 2 more times without rebooting. After third time if nothing than Restart and repeat 3 times again. Let me know if this works.

    • igot4.2woohoo

      Strange. Had to do 3 times, reboot, do 3 more times like you said before it offered 4.2.

  • Gnex Dude

    Guys, anyone notice post 4.2 update, that the font on the GNex stock text app looks different?

  • Gnex Dude

    My GNex is now on 4.2. If anyone else out there got the update, I’m wondering if you can shed some light on the following. When I do the 2 finger swipe to access the notification power controls (wifi/airplane/brightness/settings/etc) it does not act as a true “toggle”. That is if I press the bluetooth button, it takes me to the bluetooth settings vs. simply turning on my BT. Same for Wifi. Is anyone else experiencing this same thing?

    • Same thing on my Nexus 7. Only thing thats a true toggle is Airplane mode

  • Gnex Dude

    Fellow DLs, I think I figured out a way to force update on the GSM GNex and N7 using

    “the Settings>Apps>All> and then finding Google Services Framework. If you Force Stop and then Clear Data” instructions above. I noticed that while I was on wifi, when I cleared data and forced stopped Google Service Framework, almost instantly it would go from 0Kb to 148Kb. As such, I wanted to make sure no information was sent to my phone. I put the phone into Airplane Mode, did the clear data/force stop under Google Services Framework. Then I took the phone out of airplane mode and viola, the update to 4.2 started. I then tried the same thing on my N7 and sure enough, no update took until I put the device in Airplane Mode, cleared data/forced stop and then put it back into wifi. Maybe I was lucky, but I figured I’d share.

    • iajoeior

      it didnt work 🙁

    • Michael Wilson

      Dude, that worked spot on for my N7. I’ve been doing the standard force all day by keeping it in wifi to no avail. This worked on the first try. Thanks a bunch!!

    • Worked perfectly. I just started airplane mode. Then force stop Google Services Framework.” Then clear data. Headed over to System Update page. Held power button for a split second to toggle airplane mode back off. Hit check for update. The 4.2 prompt popped up instantly.

    • This worked like magic – thanks!

  • Updated but forgot to keep root. Anyone have a link or something showing how to root 4.2?

  • michael wilson

    How can I install this on my nexus 7 running cm10…it’s the same build number, but keep getting and error when flashing.. Any ideas why..

  • RampageDeluxe

    I’m having a weird issue with this. It has the owner info as my mom. I have no idea how or why it is that way, but when I go to settings to change it, it FC’s.

  • Daniel Maginnis

    can anyone help me out? for starters, i installed the SDK and even wugs nexus root kit when the last update dropped. i had it rooted and unlocked for a bit then went back to completely stock system with 4.1.2. anyhow, i’m following the video above and get stuck at the flash from adb step. i can get it in to recovery, select update from adb, but as soon as i do that i get a “bad beep” from my pc that makes me think the device did not detect properly. type adb devices at command and it does not find. it does find it when i first plug the device in, while it is running.

    • Daniel Maginnis

      i’m running sdk update manager right now. installing any updates as well as 4.2

    • Daniel Maginnis

      i got it figured out and its installing now. i guess wugs didnt install the adb drivers, nor did the sdk. i just assumed i had them. installed another toolkit form here and i’m good to go.

  • I keep getting an error message of “error: device not found” when attempting to load through adb. I made sure to have the Google USB drivers installed through the SDK tools, and I’ve tried this on every USB port on my laptop, too. Entering “adb devices” doesn’t show my Nexus 7 as having been connected. Any suggestions?

    • rmcray08

      I’m having the same issue. I’m on Windows 8, have installed the android SDK + Google device drivers. ADB will recognize the device and allow me to reboot to recovery using “adb reboot recovery”, but then it won’t find the N7 using “adb devices” after the reboot. Any help would be awesome!

  • Storm36x

    Loaded this on my Nexus 7 and photosphere closes saying the nexus 7 isnt compatible. Any thought on this?

    • fredclown

      Same here. Ugh!

  • has anyone else tried multi-users? I thought it would automatically share apps. Was hoping that was the case so I could hand the 7 to my kids and not give them my email acct as well (all my apps are on my email).

    It looks like I have to sign my gmail acct into the 2nd user to see the apps. I don’t want my kids to then be able to open gmail and accidentally mess with stuff.

    • Daniel Rosseau

      Why not create gmail accounts for them? That way they can each basically have their own tablet with their own games and levels and stuff.

      • Eventually…too young now, plus I already have a bunch of paid games

  • Can we please talk about how we are going backwards in build numbers? JO* comes before JZ*, but it a newer build. How did that happen?

  • Keith0606

    If anyone has updated their N7 can you look and see if there the miracast stuff is available under settings?

    • Cant find them

      • Keith0606

        well that just (insert your own expletive(s)). That was the feature I was hoping for the most. Maybe in a future update then, hopefully it’s not a hardware limitation.

  • Mike

    Non root, rebooted Nexus 7 with adb, went to do the sideload and it now cannot find the device. It obviously found it first to reboot it, now stuck on sideload screen and adb cannot find device.

    • derek connolly

      if you hold down the power button for like 10 seconds it will reboot. I had the same issue. Did you do *adb reboot bootloader* or *adb reboot recovery*. When I booted to bootloader first then to recovery my computer didn’t see my tablet in adb. However when I rebooted straight to recovery it worked fine. For me anyways.

      • Mike

        I noticed that when it rebooted into recovery (which is what I booted in) that when I went to device manager, it did not install the driver for the nexus 7(it was fine under when fully booted up), Window 7 64bit, btw. So I updated driver and browsed, then chose device. Chose Android Phone, the ADB Interface. Then I was able to see the device and push update.

  • Booyah

    Is the 4.2 Gmail running well on anyone’s N7? For some reason not working on mine…

    • RampageDeluxe

      It’s working fine for me.

      • Booyah

        I must be missing something then. Did you flash 4.2 Gapps or anything? Gmail won’t let me zoom.

        • RampageDeluxe

          I thought you meant that the app isn’t working, but I went and tried to zoom and its not working here either. I’m going to try and install the apk I have and see if that works.

          • Booyah

            Yeah, sorry I wasn’t clear. That was the main reason I wanted 4.2 was to have the zoom for gmail so I’m hoping it’ll work somehow. I’ll probably just end up flashing AOKP when they come out with their latest build next week.

          • RampageDeluxe

            I reinstalled the leaked Gmail 4.2 apk and it works like a charm. I don’t blame ya, I might do that myself.

          • Booyah

            Tried what you suggested and was unsuccessful, any luck?

          • RampageDeluxe

            I didn’t see this other reply. Did you uninstall the gmail app that came with the update? I uninstalled, rebooted and then installed the leaked apk.

          • Booyah

            Yeah I actually just did that. It works fine now. Funny thing was that the swipe to archive/delete worked fine, but didn’t zoom. The leaked Gmail2.apk works great. Thanks for getting back to me though.

  • Booyah

    Kind of a double edged sword. Flashing on N7 breaks root and you have to root again. Does anyone have a way around that?

    • Raven

      Voodoo OTA Rootkeeper

    • barrmy

      it would have taken less time to re-root than to type that msg

  • Has anyone received the update running stock JRO03S on the Nexus 7?

    • Michael Wilson

      Yup, but I forced it. Put the N7 into airplane mode. Go to settings>apps>all>google services framework. Clear data and then force stop. Turn wifi back on, check for update and you should be golden.

  • Diego Diaz

    I keep getting Status 7 error, Installation Aborted… hmmmmm

    I am using CWM 6

    • cjlee89

      Do you have a custom kernal? Francos to be exact?

      • Diego Diaz

        No, I am running stock

        • cjlee89

          Any custom system apps?

          • Diego Diaz

            The only other thing that is not stock is when i flashed some of the 4.2 goodies like photospehere, keyboard, clock…would i need to do a factory reset since i deodexed necssary apps?

          • cjlee89

            You would need to reflash the 4.1.x system apps back before this will flash successfully.

          • Diego Diaz

            thanks for all your help!

          • cjlee89

            No sweat!

          • XF1ber

            Anybody have a link to the 4.1.x Keyboard/apps so I can revert back.

          • cjlee89

            You can try dirty flashing your current 4.1.x ROM back on.

  • Force Stop > Clear Data > Force Stop worked!

    • Eleminohp

      this was the method that worked for me, while nothing else did…thank you sir!

  • Def waiting for BB on this, already have most of the 4.2 stuff installed on it and it is so nice.

  • cjlee89

    C’mon Mr. Alfonso 🙂

    • William_Morris

      I wouldn’t be amazed if Pete has a new one out within the next 48 hours. BB FTW!

      • Pete always waits for AOSP, so perhaps 48 hours after AOSP hits.

    • cjlee89

      AOSP is a GO!!

  • Christopher Riner

    Definitely wanting to try this out, but it shouldn’t kill root where its not an ota or fastboot, right?

    • JoshGroff

      I’ll find out in a few mins, downloading and flashing now.

      • derek connolly

        my root is gone.

        • JoshGroff

          Well, now we know.

        • RampageDeluxe

          CWR asked me if I wanted to keep custom recovery and to keep root.

  • MikeSaver

    When do you think Verizon Gnex will get this? And I’m rooted so by that I mean, when do you think a custom rom will come out with 4.2 for Verizon GNex?

    • KleenDroid

      I would bet by the end of the day and tomorrow at the latest.

      • RW-1

        Well, that will depend on when the source is released to AOSP, I wouldn’t go for a crossover ROM onto the VZ GNex myself …

  • bakdroid

    Xoom WiFi will get this before the Verizon GNex. LOL!

  • F you Verizon! I would not be at all surprised if the Verizon Gnex never got 4.2.

    • KleenDroid

      ? What are you talking about? I bet we will have it by the end of the day.

      You are not stock are you?

      • I’m not. I’m running BB and I expect/hope Peter will get us 4.2 when it hits AOSP. But I’m talking about all those people running stock, you know, your average person, not us nerds. Verizon doesn’t give a crap about us and it’s those people that get screwed. I’ll be fine if 4.2 is a bit late, but I wouldn’t be surprised if Verizon has just given up on the Gnex completely.

        • EC8CH

          Which is exactly why carriers should have no control over software. If the phone’s manufacture is willing to support their products why should the carriers stand in the way of manufacture’s supporting their customers.

          My rooted VZW Gnex will be running a 4.2 ROM shortly thank you very much Verizon.

  • andrew piegnet

    my N7 is totally stock with root and custom recovery….failed. this happened last time with the 4.1.2 update.

    • Steve Benson

      Have you changed any of the system apps? Install the new gmail or keyboard? If so, you have to return it to stock before this will flash.

      • EC8CH

        Thanks for the heads up. I’ve flashed the 4.2 keyboard, so I guess I’ll restore my stock backup before flashing the update.

  • Any idea yet if the 4.2 update for the N7 includes the wireless display functionality?

    • derek connolly

      I don’t think so, I’m not seeing it in any of the settings so far.

      • This is potentially the saddest news I have ever received. Was planning on getting a N7 but I need a form of video output (I review mobile games on youtube)

  • fauxshizzl

    I know this is very far fetched. But considering the Verizon Razr M is already getting JB, anyone think they finally realized how terribly flawed their update system is and might make a small attempt to speed things up for all their future phones? It’s probaby just the optimist in me coming out again.

    • bqluong

      hahahahaha, sorry that made me choke on my coffee a bit

    • AnotherAndroidKid

      no. they want you to buy new hardware from them, not upgrade and keep using your old hardware.

      • fauxshizzl

        Yeah I know, just the one phone they actually updated quickly gave me a small glimmer of hope. Far fetched as it may be to see continue in the future.

  • Mr ilheis

    Don’t forget that if you modified any system files you will get a Status 7 error and installation will abort.

    • Taylor Bonnesen

      How do you fix that problem?

      • Mr ilheis

        I usually mod my system files and make a .bak or use J Rummy’s toolbox and it will make a backup for you. Otherwise hope you make a nandroid before you modified the file so you can extract it or scour the webs for one.

  • Does root still work after flashing?

    • r0lct

      Stock OTAa kill root. However you can easily re-root the same way you did the first time.

      • I was thinking more along the lines of the first option, flashing the update directly and not waiting on the OTA.

      • Raven

        Or use Voodoo OTA Rootkeeper.

  • ShameOnYou

    Nothing for my N7 yet.

  • scottn7

    I just downloaded for non-root. If I don’t see an update by the weekend, I will give it a go myself.

  • r0lct

    I think I’ll just let my N7 pull it down whenever it comes. As for my Gnex I’ll be much more impatient and download the first thing that boots on a Verizon GNex.

    • Daniel Clifford

      Just bought a used Gnex for super cheap. Hoping that coming from a Bionic that my patience for Verizon to push this out is not too thin!

      • JoshGroff

        The dev community really made the VZW G-Nex worth it, but at least last update they were only a few weeks behind.

      • r0lct

        What Josh says. Keep in mind it’s the only phone on Verizon not trying to block you from unlocking/root/rom so the whole experience is much easier.

    • 1MPR0BUS

      I give it until the days end until we have something bootable for the VZW GNEX. Thank god for developer support.

      • r0lct

        Yeah, I figure I’ll be running some hacked together backup before I leave work and BB 4.2 by the end of the week.

    • saint_stephen

      Same here. N7 OTA and then Bugless Beast 4.2 as soon as it’s available for Toro GNEX.