Share this Story

Download: Android 4.1.2 JZO54K Update for Nexus 7

With Android 4.1.2 (JRO54K) going official today and starting its rollout to select Nexus 7 devices, we know that many of you are itching to get a hold of it. Thanks to the wonderful invention known as the internet and Twitter, we have the file, directly from Google. 

Download:  Google Link

If you want to flash this file, you will need to be on build JRO03D, which was released back in July. You can be rooted or non-rooted, but the easiest way to flash the file is going to be in a custom recovery like CWM. For those confused or who aren’t rooted, you’ll need to flash the latest ClockworkMod Recovery through adb or one of those All-in-One tools. You shouldn’t need to root in order to do this.

Once you have a custom recovery, drop the .zip on your internal storage, reboot into recovery, and “install zip from sd card.”

Let us know how it goes!

Cheers @WinDroidGuy!

  • Mike Snyder

    The Status 7 error message preventing me from installing this update rubbed me the wrong way…so I edited the installer script removing ALL of the verification BS. Installed without a hitch. Of course, I am used to editing ‘updater-script’ files every time I want to flash one of my devices…

  • JustinRadice

    got the downlaid to install but it killded my root…….anyne rn into this problem

    • Havoc70

      yes it did, i re-rooted with WugFresh Root Tool and its was good again

  • Here is a youtube video I just used to install Android 4.1.2 JB on my stock, non-rooted Nexus 7! If when you get to the point where you can’t copy and paste the .zip file to the cmd promp, just type the file in yourself. Code: adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip Make sure you type that code just as it is (including the spaces).

    Thanks goes to Android Police on this one! Just sharing more android love!

  • Scott Schrob

    My N7 has had version JRO03S since I got it in Sept, so how would I upgrade? I am stock but unlocked and rooted.

    Would I have to downgrade?

    • Download the .zip file to your Nexus 7 if you have a custom recovery. If not, follow the video I posted a minute ago just below yours.

      • Scott Schrob

        But will it work since I am not on the same build as the article says you should be on?

        • You would have to flash the stock files in before trying this.

  • Works like a charm! Surprisingly enough, my Nexus 7 has gotten faster! The link for the youtube video on how to install it is perfect! Especially for a lite/moderate Romer like me!

  • David Verba

    I’m getting Error 7 – says malformed WE# (which is the first line) anyone have a clue how to fix?

  • Mr ilheis

    I modified my build.prop using J Rummys Toolbox and just did a restore to OG build.prop and it worked.

  • koseyface

    Installed w/ clockword mod, it seems faster than b4, however I had to upgrade a few programs like tItanium backup pro and a few task killers

  • Ezye1313

    Has anybody else besides me not seen the update OTA?

    • Daniel Clifford

      I have yet to see it. Pretty sure its a slow roll out.

  • djjsin

    looks like the status 7 is happening for those’s who’ve made changes to the Nexus 7 system files. i installed the original browser (which required me to rename/remove browserproviderproxy.apk and browserproviderproxy.odex), and when i would read the log file, that is what caused my Status 7 error. I replaced those two files, and update worked perfectly

    • Guest

      you need to restore browserproviderproxy.odex. It helps me

  • So my Nexus 7 is currently unlocked + rooted on 4.1.1 JRO03D, & has CWM

    Placed the .zip of the 4.1.2 file onto the root of my /sdcard, & attempted to flash the file in CWM, but the installation process gets aborted, with “Status 7”. Not exactly sure what’s going on..

    Anyways FWIW here’s a pic of my N7 in CWM, showing the error text:

    • I’m assuming this could mean it’s simply a bad .zip, but I can’t be sure

      • djjsin

        its not simply a bad .zip file. you modified your build.prop file so it is failing cause the verification check cant verify that the build.prop is correct file

        • I have modified my build.prop, but only to add the line “launcher.force_enable_rotation=true” to the bottom, to enable homescreen rotation.

          I’ve since removed this line, saved the build.prop, & rebooted & the line is removed now. Not sure what else is up… Would it be possible to fix this? Would I need to replace my current build.prop with a new, fresh one…?

          Sorry for being unsure on some of this stuff..

          • You can disable “signature verification” if that would solve it …

          • ddevito

            nope – that doesn’t fix it. Only fix seems to be to flash stock images and start again

  • If you have stock JB on the N7, you can go into the stock recovery and side load from ADB with the file above. Was actually a lot easier than I expected (and new experience compared to other stock recoveries where you usually have the .zip on your “SD Card”)

    • Zack Stottlemyer

      so I guess I have to unlock to upgrade? I tried doing recovery mode power + volume down didnt give me the option to boot from my zip file.. all my other devices are rooted just was trying to see if i could force this vs wait

      • No. Just reboot to stock recovery. I wasn’t unlocked or rooted. When
        the guy pops up on his back with the red triangle push the volume up and
        the menu will be there with the option to adb sideload.

        • Zack Stottlemyer

          so power off power + volume up.. boot into recovery mode.. once that is done i should be able to see adb sideload and load the file? right now I did it and its been on the “google” splash screen for a few minutes

  • spursrchamps2007

    Does anyone know if this addresses the touch screen issus

  • So this means 4.1.2 for the Galaxy Nexus right…?

    • Justin Swanson

      I think this is only for the N7

      • Tyler Chappell

        For now, at least.

  • gerry

    everything went smooth and easy just flashed it with cwm touch didn’t even lose root and the landscape is very nice still testing it out to see what else has improved..

  • Nacho

    this file appears to have been pulled from the server since the URL pings out.

  • Does that fix the WPA Enterprise issue?

  • Zack Stottlemyer

    what are the steps for non rooted?

    • Crazy Kettle Toms

      really? Its in the post!

  • Mike Yost

    Flashed back to stock Nexus 7 images, flashed CWM Touch, and installed the patch with no issues. On 4.1.2 now, ASUS added their own keyboard, kind of dumb on a Nexus device.

  • shara9

    install failed for me

  • shara9

    install failed for me

    • ddevito

      same here.

      Just out of curiousity – did you edit your build.prop?

      *update* – error status 7 – prob a bad .zip download. Trying again…

      • shara9

        no i didint , i getting same error status 7 , i download it twice didnt work

        • ddevito

          I’m pretty sure that means the .zip is bad. I’m downloading from my trustworthy server, I’ll see how it goes

          • djjsin

            most likely not a bad zip file. If your getting status 7, you modified some aspect of the system files, which is causing the verificaiton to fail. revert the file back to the original system file and you should be able to update with out issues. The error tells you what file the verification check is failing for.

          • barpan

            know where I can find the original copy of build.prop for Nexus 7? 🙂

        • ddevito

          failed again – damn

          • shara9

            are you using cmw or twrp

          • ddevito


      • andrew galvin

        You may be using the newer touch version of CWM. I have gotten this problem in the past and used an older CWM version and it worked.

        • ddevito

          I downgraded CWM and it still fails.

        • ddevito

          I tried manually sideloading the update and it still fails – WTF!

    • PIL

      Installation failed for me as well using CMW

    • failed for me also

    • Try disabling “signature verification” in CWM recovery … Hope this helps.

  • BrianLipp

    waiting for the BB update, no rush though, not an update that is desperately needed. (not sarcasm)

  • dhirensavalia

    Installed and everything seems to be working fine.

  • dhirensavalia

    installed and everything seems to be working fine

  • ddevito

    my install failed – wtf

    • djjsin

      most like due to a verification failure against a system file you modified.

      • ddevito

        you’d be right (build.prop it seems) but no matter what I do to restore it the install always fails. I turned off signature verification in cwm but still fails.

  • fixxmyhead

    im assuming this will work with twrp right?

    • Steve Benson

      That’s what I used and everything went smoothly. I had to adb clockwork, su and busybox back onto the device. When I booted back up I just used Goo to re-install TWRP. Everything is solid and back to normal with 4.1.2.

  • EvanTheGamer

    Sweet, thanks guys!

  • ddevito


  • KleenDroid


    • NexusMan

      Any noticeable enhancements?