Last Updated: November 13th, 2012

If you want to update your Nexus 7 to official Android 4.1.2 that started rolling out earlier today but your turn hasn't come yet, you have two options: wait (possibly for a while) or flash it manually. The latter is absolutely safe and lets you bypass the line without any risk whatsoever. Even better - you don't even need to be rooted or running a custom recovery - updating with Jelly Bean and full stock recovery is easier than ever before.

Let's get to it.

Prerequisite: Your Nexus 7 should be running Android 4.1.1 build JRO03D.

Step 1.

Download the JZO54K Android 4.1.2 update zip from Google's servers (32,862,193 bytes, MD5: 1a68f499129ae2ee373806a9cad13174).

If you have a custom recovery, you can just copy it to the device, reboot to recovery, and flash directly as you would any other zip. You're done.

If you have the stock recovery, carry on.

Step 2.

Reboot your Nexus 7 and hold the VolDn button while it's booting up. Once you see the fastboot menu and the word Start, press VolUp a few times until you see Recovery and then press the Power button to enter recovery.

You will see an Android with a red exclamation point. Now press VolUp+Power together, and you should see the menu below.

Select the 2nd option called apply update from adb.


Step 3.

Connect the Nexus 7 to your computer with a USB cable.

Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).

Keep the file you just downloaded on your computer and open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the zip file.

Type in:

adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip

You should see the progress bar go up to 100%, like so:

sending: 'sideload'  100%

At this point, the device should have started installing the update. See the screenshots below:

wm_IMG_20121009_124956 wm_IMG_20121009_125353 

Step 4.

Reboot - you're done! Enjoy the new landscape support in the launcher.

wm_Screenshot_2012-10-09-13-11-23 wm_Screenshot_2012-10-09-13-11-11



P.S. adb sideload kicks ass, doesn't it?

Thanks for the link, rusty++!

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • JLishere

    Thanks AP for posting the step-by-step! If you're using Apex or Nova Launcher however, 4.1.2 is probably not something you desperately need to go after. Personally I'm going to wait for the OTA. Bug fixes are always welcome though. Hope there's more significant features in store with 4.2 (or whatever the next major version is).

    • http://www.androidpolice.com/ Artem Russakovskii

      That depends - it does fix other bugs, like this one http://code.google.com/p/android/issues/detail?id=34212

      • fixxmyhead

        i deleted 2 system apps. do u know if it will still work? or do i have to insert them back

        • Paul_Werner

          You may have to. I deleted some on mine but have the backup from Titanium. I tried without restoring those apps and got (Status 7) Installation aborted

          • fixxmyhead

            damn it ok thanks. do u know if the system apps have to be from a JRO03D rom or can it be from the newest one the JRO03S or whatever the newest one is (prior to this one of course)

          • Paul_Werner

            I'm not sure yet. I'm trying to restore them (I removed 8 of them) and it's hanging right now when trying to restore Google Earth. I think I may just kill the restore on that and install that from the Market (not sure if it'll need that one but it's one I removed right away)

          • fixxmyhead

            yea same here i removed calendar,books,music,magazine,calculator, earth,etc all the junky ones i never use. gonna have to re insert them when i get home

          • catire

            I'm getting the same assert failed on the videos.apk, can anyone pull theirs and post it on dropbox or something? Downloaded from the market and I get the same error.....I really really don't want to do a fresh install

          • fixxmyhead

            I gave up trying to put them back in since I deleted so many stock junky apps. There's already a stock rooted ROM of the update on xda. Download, backup ur apps and data and flash. Shouldn't take no more than 10 mins. Easy peasy everything back to normal on latest version

          • Paul_Werner

            Mine keeps failing on the Google Earth check even when it's installed again from the Play Store and my backup from Titanium is not restoring it. Anyone have this backed up that can send it to me?

        • http://www.androidpolice.com/ Artem Russakovskii

          You may need to, if they were touched by the patch.

  • http://twitter.com/Michael97F Michael Fordham

    The search bar looks ugly, but landscape mode is well overdue.

  • Kenny O

    We Android fans are such an impatient bunch....lol, I know I've been mashing the check for updates button since the first post about 4.1.2......I'll probably do this when I get home from work.

  • Ian Douglas

    I miss the old Nexus "install update.zip from storage" (or whatever it used to say), so you could just download the .zip, renamed it to update.zip, move it to the root of /sdcard/, boot into this recovery, and apply it.

  • Tyson Kemp

    What else can we use sideload for ... you should do a quick write up on it and some features and uses! I think others would find your input interesting?!

  • Stephen Long

    Thanks for the links and step-by-step. I just flashed the update w/ TWRP since I got tired of mashing 'check now.' It appears to be working fine so far!

    Now I'm curious to see how long the next Galaxy Nexus update will take on Sprint (sigh).

  • munim

    I have O3C instead of O3D. Its still 4.1.1. Can I use this image to upgrade?

    • Steini Jónsson

      I have O3S on mine... and it won't let me update... I get this assert error.
      Did you find a solution?

  • Brian Dortch

    are you sure users on stock will be able to enter recovery manually like that? I remember when i was stock that was an issue going into recovery the manual way

    • Bogdan Sladaru

      I have stock, rooted and locked back. I didn't manage to enter the recovery mode using the steps described, but with the device connected while in "normal mode" I just did an 'adb reboot recovery' and it rebooted in recovery mode.

    • jamaall

      when i click recovery, it just goes into the "Google" boot up screen, and I have to force power off. So, your right. Just gonna have to wait for the update now :(

      • Long

        i got stuck at the same screen. then found out that you have to plug the asus usb cable in while booting in recovery mode. After going through series of trouble installing drivers for my nexus to run adb, i finally did it. Now my nexus officially's running 4.1.2 JZO54K

        • jamaall

          I'm not sure if that's worth it for me. The only big thing that I want on the update is landscape, that way I can stop using other launchers. But when 4.2 or 5 comes out, I will do anything to get it asap! haha

      • http://about.me/jason.johnson JJ

        While your device is running, connect it to the computer and issue the command 'adb reboot recovery' - that got me to recovery (I had the Google logo issue too)

    • http://www.androidpolice.com/ Artem Russakovskii

      Well, I just did it and took those pics so, yeah.

  • Mark

    Whoah the official zip file from Google's servers can be flashed with custom recoveries (CWM)? Didn't know that. Kind of thought CWM uses it's own format and all versions of CWM support it but didn't know Google's own zip files work with it.

  • scuttlefield

    Apparently, this breaks root?

  • Guest

    Hmmm...my install fails in TWRP. Using stock rooted ROM. Re-downloading now

    • guest

      Got an md5 by chance???

      • guest

        Looks like it may be my removal of bloatware... Why google?

      • http://www.androidpolice.com/ Artem Russakovskii

        Here's the MD5: 1a68f499129ae2ee373806a9cad13174

  • jamaall

    when i go into fastboot, i scroll up to Recovery Mode, then select it using the power button. The Android with the exclamation never pops up, but it just sits in the Google boot up screen until I decide to force power it off. Anyone know why?

    • Chris

      Got the same problem. Oh well, I'll just wait for the official update

      • http://twitter.com/mikedotdunham mike dunham

        Connect tab to pc and run adb reboot recovery

    • Quinope

      open up command prompt and use adb to boot into recovery that will fix your issue. command is adb reboot recovery

    • http://twitter.com/mikedotdunham mike dunham

      I did too so i connect to pc and from cmd prompt did adb reboot recovery. It came right up and I continued with a successful upgrade

    • OxKing

      You have to connect it via USB to yout PC.

  • ddevito

    Stock, unlocked, rooted with CWM and it fails to install - recvovery.log looks pretty ugly, failure everywhere.

    I think I'll wait for the OTA, however, I'm nervous the OTA won't work now. Anyone else having issues installing with CWM?

  • STiK

    Flashed, rooted, and recovery... works great.. Thanks :)

    • tfso

      If the nrxus is rooted and you just flashed from recovery you lost your data or apps??

  • qbking77

    How to manually install video:


    • Jared Quackenbush

      Hey Qbking! Im rooted with CWM. Installation aborted EVERY TIME! Any Idea?

  • wicked_beav

    Not working for me, installation aborted. Not sure why.

  • crankyd00d

    My adb doesn't recognize the sideload part. I get the help message you get when you enter only adb.exe

    • crankyd00d

      No matter, was finally able to update. I tried to do it with just the adb+fastboot package I had used before and that's why it wasn't working, Just install the SDK and follow the instructions and you'll be good to go :)

  • Bob Houg

    so why does the sideload command not work, it just gives me the help screen for adb

  • NightShift

    Worked fine for me, I just put the upate on sdcard booted into cwm touch recovery and it all went well, at the end there was some message saying something about the bootloader being replaced or something, I didnt read carefully so i think it deleted my root, I just used the root toolkit to re-root and everything is back to normal. Honestly though, I think the battery life on this update isnt as good but its too early to tell.

  • StudMuffin

    For anyone having problems with the "sideload" command, update the android sdk and it should work.

  • http://twitter.com/duncanmak Duncan Mak

    I sideloaded 4.1.2 and now my Nexus 7 feels more sluggish than before.

    Am I the only one?

  • http://btwnworlds.tumblr.com/ Lou G

    I'm nervous to sideload and yet..I've been waiting since yesterday to get this update. Oh well, it'll get here.

  • alex

    What is that purple Icon on the launcher?

  • http://www.dsaif.tk/ Saif

    ADB is in Androidandroid-sdkplatform-tools right?

  • http://www.dsaif.tk/ Saif

    I'm stuck on "Google" logo

    • Jesse Walker

      try spamming your power button

      • http://www.dsaif.tk/ Saif

        Had to plug in USB before going into that. Done.

  • David Spalding

    Your instructions in Step 3 above are incorrect, "Connect the Nexus 7 to your computer with a USB cable." You can't reboot into Recovery unless you are already connected to a system via USB cable in Step 2 BEFORE clicking "Start Recovery...". OR, as mentioned, use "adb reboot recovery" from computer directly.

    • Jesse Walker

      Hold down power and volume down to force the unit to reboot. when you see the "google" screen let go of the power button.

      When you see the screen with Start in the top right corner use the volume button to change it to recovery. Then use the power button to select it. If you find yourself hanging at the google screen spam the power button. It seemed to help me.

      Then when at the recovery screen hold power and volume up to get the menu.

      • David Spalding

        I don't get "spam the power button." Repeatedly press it? Hold it down? Mash it like a crazed monkey? Pfft.

        I like my solution, found on other references, better. Author needs to update this page.

  • Lone McCord

    Downloaded directly to tablet from this page. Installed with Rom Manager Premium v5.0.2.1 using "Install Rom from SD card" - CWM gave me a dialogue allowing it to save the recovery and unlocked root before I rebooted (I choose yes to the two options). Was running rooted stock 4.1.1. I am using the premium Rom Manager - and CWM (in-app purchase from Rom Manager.) Root Held, Tablet updated. Very easy if you use the premium tools. Took longer to write this comment than to update the tablet.

    • Liam Sansam

      I did the same, was thrown an error at first about the file not being mountable, but then tried again from within ClockworkMod Touch and it worked, was given the option to restore root, and that worked perfectly too, took about 3 minutes in total actually to update from 4.1.1 to 4.1.2, stock rooted 4.1.2 with tablet ui looks pretty damn amazing i must add (Density of 160 is perfect)

      • Ruslan

        How you update this tablet to 4.1.2 i change build.prop to and now i can't update

  • Jesse Walker

    I just updated my stock nexus 7. My issue was with getting first getting into recovery mode. Its like it would hang at the google screen. seems like if you spam the power button it lets you in.

    Second, windows 7 didnt like the driver for the nexus that would work while in debugger mode, so I had to force install the driver for it to work.

    Once I got those working it was smooth sailing. Nice update.

  • Chad

    I was having trouble with the adb sideload command. The download link provided has an adb version of 1.0.26. I updated the android-sdk and ran the adb in the platform-tools directory and it worked. The version found in the platform-tools directory is 1.0.29.

  • Kevin Chancey

    I can get halfway through step three and then I get stuck. I am in recovery mode and I launch the command prompt to enter the adb command and I get this message everytime. "'adb' is not recognized as an internal or external command operable program or batch file.". I can see that the device is recognized by Nexus 7 toolkit as an adb device, but it seems that the command is not recognized. Anyone had a similar problem?

    • Jesse Walker

      do you have the android dev kit installed?
      do you have your prompt window open to directory where adb.exe is located?

      • Kevin Chancey

        Yeah, got the Android SDK Tools installed and updated as best as I can tell. I open it and it says SDK Tools rev. 20.0.3. I thought I was in the right directory for the adb.exe, but looking at it now I am unsure. I have an adb.exe in C:Wugs_GnexRootToolkit.v1.4data and another listed as "adb-toolkit" in C:Google Nexus 7 ToolKit.

        Edit. I was not in the platform-tools directory. Thanks for the assistance!

    • http://about.me/jason.johnson JJ

      I have similar - my Nexus 7 is recognized in Windows while it's running, and I see it listed in ADB devices. I can issue the adb reboot recovery command fine, but in recovery, when I select to 'apply update from adb' the device disappears and is no longer listed in adb devices. I can't manually install the latest driver at that point in Windows, and my Android SDK is up to date. Odd.

      • Jesse Walker

        Same thing happend to me. I noticed in device manger in windows is I had the warning flag with nexus 7 again. I had to pick update driver option, then pick browse for driver, then Let me pick from a list and install the adb driver again. Worked after that.

        • http://about.me/jason.johnson JJ

          Perfect, this this did, thanks!!

  • CBers

    Doesn't seem to work on a rooted Nexus 7 wirh TWRP installed.

    Getting assert failed: apply_patch_check("systembuild.prop" error message.

    • Micka

      Be sure your build.prop is in the original state. If it was changed you'll get this message.

    • GazaIan

      Doesn't work in the current version of TWRP, sorry :(

      • evsdog

        BOoo.any other way to update?

        • http://codytoombs.wordpress.com/ Cody Toombs

          I haven't been watching for this, but I would expect that there will be a compatible repackaging of the update posted on XDA fairly soon.

    • Baldyl0cks

      I had an LCD density changed so I just changed it back to 213 using rom toolbox and im set! (Rom toolbox also allows you to reboot to recovery if you're rooted!

  • brutalpanther

    OK what am I doing wrong here.I can get to the recovery screen,and scroll up to recovery mode.but when I hit power button it goes to a screen with nothing but Google on it.never shows me a droid with a exclamation mark or screen to scroll to adb download.help

  • brutalpanther

    you need to revise your instructions on manually updating to 4.1.2.step 2 does not work.I have tried several times and when i press power button on recovery screen all i get is a screen that says google.stays on that no matter what.I followed instructions carefully,but without being able to get past google screen what good are they.Never comes up with little android robot with esclamation or the screen to pick option to apply update from adb.

  • scum

    dosnt work for me, after i type in adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip i get a list of adb commands :/

    • Doug

      Unplug and re-plug your usb cable.

      • Mike

        For me unplug an replug does not work, but the device iss been recognized....

        • jack

          same problem any ideas

    • Escaladeur

      Same problem for me

    • darc87

      USB Debugging turned on?

    • enob

      Getting the same thing

    • David Sharpe

      The linked version of ADB is old and doesn't have the sideload command. Get a newer version.

      • enob

        Wish I refreshed the page sooner.

    • enob

      I fixed it! Download the new ADB from Google. ADB is in sdkplatform tools. Worked fine

  • sutt2m

    Just install cm10 it's a lot easier!

  • Jon Langevin

    Same process, but for OSX users, and includes details such as enabling USB Debugging for ADB to work: https://plus.google.com/106254289171462426958/posts/7JMLE6An1VU

  • Jens Holst Schumacher
  • ptashe

    worked fine for me. I was root so I used clockwork recovery and clear system cache and dalvik cache before updating system. Everything worked perfectly.

  • TidBit

    Thanks. It worked for me. I had to download the sdk and use that adb.exe file, but it worked flawlessly. Thank You Very Much!

  • CD

    If ADB cant see your nexus when in recovery->sideload then its probably not recognised the device to load the correct driver this chap has found a fix http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode

  • http://twitter.com/spackmanstephen BIG UK

    I have yet to receive the update on my Nexus 7. Is there an issue with my device, or are other people not getting the update?

  • Stephane Moser

    I have a Nexus 7 running Android 4.1.1 build JRO03S, its a problem or i can do the update?

  • David H.

    Was just in the midst of doing this manual upgrade (with zip downloaded and ready etc.) and was just about to reboot the N7 and lo and behold... an update from Google! New update found! Thanks Google! :)

  • http://www.facebook.com/people/Scott-Hutton/100001333254808 Scott Hutton

    I'm able to boot into recovery via the usb cable connection and tell it to sideload the file, yet when I type in the adb sideload command, it tells me "error: device not found". Yet it just booted into recovery mode without any problems via the usb cable!?!?!?!?!


    • markbratanov

      Same problem. Any help here guys? I get "error. device not found" on Windows...

    • cellon

      you need to upade the usb driver inf in the android extras path to the actual hardware id...

  • http://www.facebook.com/rajesh.amaravathi Rajesh Amaravathi
  • Pali

    It does work on JRoO3S . . . ?

  • OKinfo

    ERROR signature..patch..not using USB cable.file is on tablet

  • JG

    All this is unnecessary, you can force an update in under a minute simply by doing the following: go to settings>apps>all apps>google services framework, clear data only, dont force stop,then go to settings>about tablet>system update... you should see last checked 12/31/1969, click check now and it should update for you

  • spunkae

    I tried updating my Nexus 7 from Android 4.1.1 to 4.1.2 and I had a lot of problems but I survived and completed the update. I already had unlocked and rooted by tablet so that I could install Browser and Flash. I used WugFresh Nexus Root Toolkit to unlock and root.

    Before the update I saved my root privileges with Voodoo OTA RootKeeper. When I tried to let my tablet update itself with the new version (OTA) I got the Android symbol with a red triangle. Eventually, I found the sideload method above. Unfortunately, the Android SDK mentioned above would not recognize my usb device so I used the command window in my WugFresh NRT and I was able to launch the sideload command.
    The update checked for /system/app/BrowserProviderProxy.apk. Well, as part of the installation for Browser (so I could use Flash), I had to rename this file to another name. Once I discovered this, I restored the original names of /system/app/BrowserProviderProxy.apk and /system/app/BrowserProviderProxy.odex using ES File Manager and then I was able to sucessfully install.

  • chris125

    Mine says cannot read 'sideload" any help to what I need to do?

    • rdrizzle

      Type .zip at the end of the file name

  • Imran Khan

    Hi.. I bought a samsung galaxy nexus from my friend. he purchased it from UK for me and it has Android 4.1. since i m using it from last 2 months now i got a Android Update on 4.2. when i tried to update it an error exists and there is a Bios screen appear which has more than 5 options. the first one is Reboot again. Please suggest what to do. i want to update it to 4.2 and i got also its official notification for update. please help me out what i need to do it. Should i update from a 3rd party Source. my contact no. is 08557997758 please help me out.

    ( There is Signature Error in Bios when i tried to update )

  • ian repsch

    Hi all my nexus 7 is stuck on 4.1.1 and refuses to update to 4.1.2. It fails the OTA and enters recovery mode when rebooted it is still at 4.1.1, I have tried a factory reset, clearing the google services framework re-running OTA (many times) and eventually used adb sideload, which during verifying current system returns

    assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by_name/LNX:xxxxxxxxxx")
    Installation aborted.

    where xxxxx is a big hex number.

    Its just over a week old stock & not rooted and is build JR003S (and I have used the JZ054K from JR003S update). When I first switched it on it found the 4.1.2 update but failed so it cannot be anything I have done or installed I am beginning to think it is either faulty or somehow the factory image is not compatible with the updates and the only way now is to re-flash the whole image. Anyone seeing this or has any ideas, Thanks.

  • Clara

    so what happens when you get "cannot read sideload"?

    • Clara

      and how do you know if you have stock or custom recovery? and I have 03S

  • Vaibhav

    do i have to root my device to do this?

  • http://www.facebook.com/ko.ye.1401 Ko Ye


  • RinVindor

    For the writer of this article perhaps you might want to clarify (crazy idea I know) that you need to hold down the Pwr + VolUp and then ONLY release the VolUp button when at the Recovery Mode. Took me about 30 minutes of searching thinking something was wrong only to find out you hadn't specified that kinda vital step.