Yesterday, Google announced the kickoff of the KitKat OTAs for the Nexus 7 and 10, though we haven't seen the update for the 2012 N7 actually pop up until a few minutes ago. (If you have a 2013 Nexus 7, head over here.)

2012 Nexus 7 Wi-Fi (not 3G yet) owners, listen up. You can now flash the 185MB KRT16O Android 4.4 build without waiting any longer, no matter what your rooting/bootloader situation is. Of course, if you've modified the system partition in such a way that the OTA won't apply cleanly anymore, you have to either revert those changes or wait for the factory image.

Screenshot_2013-11-13-13-13-20 Screenshot_2013-11-13-13-13-06

Boring stock launcher

As before, the latest Nova Launcher beta enables transparency and works like a charm. In fact, Here's How To Try The Google Experience Launcher With Translucent Bars And Google Now Once You Get Your KitKat Update [APK Download].

Screenshot_2013-11-13-13-20-27 Screenshot_2013-11-13-13-17-34

Nova Launcher beta

Disclaimer: Android Police isn't responsible for any harm to your device - proceed at your own risk.


In order to complete the steps below, you need to have the Android SDK installed. The SDK contains the latest version of adb and fastboot, which you will need for flashing. You will also need a MicroUSB cable to execute adb sideload, fastboot flash, and other commands. You don't need a USB cable if you're just planning to download the OTA zip directly to your device and flash it from recovery.

You must be running Android 4.3 JWR66Y for this OTA to work.


Download KRT16O-from-JWR66Y:


Note: This method, just like the native OTA update procedure, does not wipe your data.

Note: If you're using SuperSU v1.69 with OTA Survival enabled, you need to disable it first, otherwise the update may not flash.

adb sideload the zip you downloaded above by following my earlier guide here. If something fails, try to fix it by restoring the system files you've changed or wait for the factory image.

Here's what you should expect to see if you're using the stock recovery:

20131113_130353 20131113_130615

adb sideload using stock recovery

And now that you've flashed yourself some KitKat, go read up on what's new and enjoy!

Update: The Android Runtime switcher seems to be missing here, so no ART for us 2012 N7 users. Curiously, it's there on the 2013 N7.


Rooting a Nexus 7 is very easy but requires an unlocked bootloader and a custom recovery. I recommend using TWRP.

  1. Flash TWRP from here (fastboot flash recovery FILENAME.img).
  2. Reboot into recovery (adb reboot recovery or hold Power+VolDn, then select Recovery).
  3. Flash the latest version of SuperSU.
  4. You should be rooted.

Screenshot_2013-11-13-13-31-03 Screenshot_2013-11-13-13-30-53

Thanks, Andrei Voica and TheManii!

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.

  • firesoul453

    I cant wait for cyanogenmod to get 4.4!

    • PhoenixPath

      Unofficial CM11 nightlies exist for quite a few models already.

      • firesoul453

        unfortunately the sprint galaxy s4 doesn't appear to be one of them :(

        • PhoenixPath

          You're more than welcome then, to join me in my grumbling.

          It's not productive or all that much fun, but it does pass the time...sort of.


      • Jadephyre

        Doesn't count, still uses 4.3 binaries, so it's a half-measure right now.

        • PhoenixPath

          OK...I've seen this type of comment enough times now, that I have to put a stop to it. This is not 100% directed at you personally, so keep that in mind:

          No. Sorry, but just...no. That's dumb.

          "Binaries" are Drivers.

          Are you using Windows 8? I bet many of your drivers were written for Windows 7. Some of them were even probably written for Windows Vista. Does that mean you're OS "doesn't count" as Windows 8? Bull-hockey.

          CyanogenMod exists and is popular in a large measure by the fact that it allows many devices who's manufacturers have dropped support run the "latest and greatest" version of Android.

          The manufacturers dropped support...no more drivers.

          Example: The latest official stock ROM released for the Galaxy S1 was Gingerbread (2.3). The latest official release of CM for that device is 10.1.x (4.2).

          Do you believe the drivers for that device were written for 4.2? Do you believe that the official CM isn't, in fact, official?

          Hint for anyone confused by binaries: While it is definitely easier for devs to port CM to devices that have existing binaries for that version of Android, it is most definitely *NOT* a requirement.

          /rant off

          Again, sorry to fire that off at you personally, but I've seen this so many times lately it's gotten on my nerves a bit. Sorry...

          • Jadephyre

            Have it your way, i'd rather have a ROM compiled with drivers made for that specific branch of OS release than something that had to be hacked into shape in order to work. And no, I do NOT use the trainwreck called Windows 8. The only worse versions of Windows were ME and ME 2 (aka Vista).

          • PhoenixPath

            Not my way. CM's way, apparently.

            Name your OS. I *guarantee* some of the drivers you are using were written for the previous version.

            " i'd rather have a ROM compiled with drivers made for that specific branch of OS release"

            That is entirely your option, and one I don't disagree with at all. But saying the OS "doesn't count" because it meets the standards of the OS authors...but not yours? I don't want to say it's self-righteous or elitist, but it's gotta be darn close.

            Again, I'm not really trying to insult you here. If Im at all snarky, it's because I've seen this too many times and my Nexus 10 hasn't gotten the OTA yet (bad day). I just want to help people who may think as you do understand that CM is still CM, so long as CM says so....even if it isn't using up-to-release drivers.

            (My first Android device would never have seen ICS if it hadn't been for CM and folks like jt1134...and it worked *better* on CM/ICS than it *ever* did "stock".)

            ...just sayin'. I'll drop it now. Peace. :-)

  • Danny Holyoake

    *comment about the Nexus 4 not having KitKat yet*

    • Nwanu

      It's always worse when it's actually close.

      • Jacob Serna

        That's what she said. What wut ?

    • Mathias Kenting

      *Comment about no Google Experience Launcher on any other Nexus than N5*

      • SorinDobrin

        You ain't losing much...that was the first thing that I got rid off once I got my nexus 5

        • annalisedyy264

          мʏ ғʀιɛɴɖ'ѕ ѕιѕтɛʀ-ιɴ-ʟαա мαĸɛѕ $60 αɴ нօυʀ օɴ тнɛ ιɴтɛʀɴɛт. ѕнɛ нαѕ вɛɛɴ աιтнօυт α ʝօв ғօʀ тɛɴ мօɴтнѕ вυт ʟαѕт мօɴтн нɛʀ ιɴƈօмɛ աαѕ $12з47 ʝυѕт աօʀĸιɴɢ օɴ тнɛ ιɴтɛʀɴɛт ғօʀ α ғɛա нօυʀѕ. нօք օʋɛʀ тօ тнιѕ աɛв-ѕιтɛ fox200&#46com

        • someone755

          On the other hand though, I adore it! ^^

      • Kris Pucci

        i agree...I do not understand why they would not offer the GEL on all Nexus devices. I just does not make sense when they are trying to "defragment" the experience.

      • bL4Ck

        Man i read so many people whine because the GEL is exclusive to the N5, some even mentioned stuff like "Google is branching Android in two and keeping the good stuff for the new phone only" rofl

        Anyway, as usual thanks AP for the links, just sideloaded the OTA on my N72012 and everything is working fine.

      • Jim S
      • Octo

        rocking the galaxy nexus with not only a ported 4.4, but GEL as well. and they said the GNex wouldnt get any updates. you were saying?

  • omarsalmin

    I find it easier to boot (not flash) cwm and install the ota as any other update.zip

    Alternatively, you could just flash cwm to make rooting easier down the road!

    But that's just me

    • Brandon Schneider

      Looking for this. I can just factory reset in TWRP to wipe my current CM ROM, and then just flash this like any other ROM, right?

      • omarsalmin

        You'd have to come from stock to use the method above.

        You could just restore a factory image and then do what I said above

  • ron

    HTC one gpe next please!

    • Jadephyre

      You get yours on friday, as for us Nexus 4 Users... only the stars would know, and they ain't tellin'

  • hasan

    Nexus 4 next hopefully.

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

      Nexus 10 is next.

      • hasan

        Thanks. Ah, thought N10 rollout already started.

        • Kyle Riedemann

          Here's a link to the 10 OTA via XDA


  • Matthew Fry

    But.. where.. Nexus... my.. 10...

  • scuttlefield

    Still no APK for the Nexus 10? I thought I heard some people were actually getting it yesterday. No?

  • PhoenixPath


    Still waiting for my Nexus 10 OTA.

    (Heck, still waiting for anything more reliable than claims of botched installs and "Hey, it worked for me!" to prove it's actually in the wild at all)

  • Robert Alex Kibler

    has anybody done this yet? I'm in the process of downloading the adt bundle because I didn't have it on my work machine before. Any issues?

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

      I have - this is how the screenshots and photos in this post were taken. No issues.

      • SimonC

        Doesn't look like ART is in the developer options?

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

          You're right. It was there in the 2013 N7, but not in 2012.

          • Bariman43

            Confirmed it's not in the 2012 N7. Disappointed, but there must be a reason for it.

          • Imparus

            The reason could have something to do with it being an experimental feature, and they haven't gotten it enough stable for us to test it on the 2012 nexus, nevertheless I'm also a bit disappointed, was looking forward to play with it :p

          • Simon Belmont

            That's my guess. It's probably more worth Google's while to test it on the two newest devices in their line-up for now (the N5 and N7).

            I'm sure we'll see ART enabled in a future update for the 2012 N7 because it will likely help performance on an older tablet. Just my two cents.

      • tymalo

        I received an error when trying to update. It said:

        "E:Error in /tmp/update.zip
        (Status 7)
        Installation aborted"

        I hit reboot now and now my N7 boots up to a dead bugdroid and says No Command. I can't get out of recovery. Do you have any idea why it failed?

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

          You must have modified something on the system partition, or your zip is corrupt. Try pressing Power and VolUp together and wiping cache and rebooting. If you really soft-bricked somehow, you can just flash the 4.3 factory image and try this OTA process again. That should work for sure, since it'll restore your device to stock 4.3.

          You won't even lose any data if you take out the -w flag from the factory image installer.

          • tymalo

            I tried to wipe cache but it still goes to the error screen. I just downloaded the 4.3 factory image. Does AP have a guide on how to install a factory image?

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

            Son of a bitch. The mirror got corrupted somehow. I'm uploading a new mirror now. I'm guessing you downloaded it from there and not from Google's server?

            Edit: Correct mirror now up.

          • Jay W.

            I have the same error... I downloaded it from the mirror.

          • mike dunham

            I just tried the mirror, and it was unable to verify the signature. Sideloading Google's link now

          • tymalo

            I actually got it from Google's. I'm going to have to figure this out.

          • jazzruby

            SuperSU 'Survival' mode may be causing issues with the update as can be seen in 'Erroneus' post/error log. It sets an immutable bit on the su binaries; may want to add this to the install/flashing method.

  • MrMathboi Reborn

    Like I'm waiting it to appear automatically on my nexus 7 do you know if it will appear today

  • Flydroid

    Is it possible to flash it over PA?

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


  • Ben Baranovsky

    I can't wait for my HTC One Google Play Edition to get the OTA! HTC has just two more days to deliver on their promise of an update within 15 days, and inside sources say it's almost finished!

  • Kingu Prima

    and... #Nexus4 ?

  • Kyle Riedemann

    Some one just found the link the the N10 on XDA!


  • Sergio Cunha

    Can't go trought the "Android with a red exclamation point", I do what is meant to be done, but the Nexus reboot. I've the stock recovery.
    Can some one help?

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

      Hold the power button and quickly press volume up. Let go of the power button though, before it shuts down the device.

  • Václav Smažený

    No ART for N7 :(

    • sssgadget

      4.4 is not significantly different than 4.3 for N7. Fragmentation everywhere.

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

        It's an experimental feature, let's not complain about the absence of something that breaks apps and might as well have not been there yet. They have enough test samples now with the N5 and N7 2013 that they can disable it on other devices for now.

      • Smithers_Jones

        It's not fragmentation. Do you even know what the word means?

        apps don't care if you have it or not, they will work regardless. It's feature disparity across devices, something Apple and Microsoft have been doing for years.

        • sssgadget

          "It's not fragmentation."

          "It's feature disparity across devices"

          Can you read it again?

      • pobautista

        Nope, 4.4 is a major Android upgrade. See http://developer.android.com/about/versions/kitkat.html . What the N7 doesn't get is just ART and SMS-Hangouts integration.

        I'm excited about the reduced memory footprint, but sad because though barely 16 months old it won't get to play in the ART experiment.

    • fattire

      It's in cm-11 for nexus 7 2012

      • jjsan

        doesn not work

  • Jadephyre

    So, can this be flashed by wiping the system partition in CWM (plus cache and dalvik) or do I need to have 4.3 first and then sideload it?

    Because flashing back to stock 4.3 is too much of a hassle right now.

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

      This is an OTA, not a full image. It can only apply on top of stock 4.3.

  • http://www.innews.dk/ Erroneus

    Didn't go well with my Nexus 7. Flashed from TWRP, got error:

    "chown of /system/bin/.ext/.su to 0 failed: Operation not permitted
    ApplyParsedPerms: chgrp of /system/bin/.ext/.su to 0 failed: Operation not permitted
    ApplyParsedPerms: chmod of /system/bin/.ext/.su to 420 failed: Operation not permitted
    ApplyParsedPerms: lsetfilecon of /system/bin/.ext/.su to ubject_r:system_file:s0 failed: Operation not permitted
    ApplyParsedPerms: removexattr of /system/bin/.ext/.su to 0 failed: Operation not permitted
    script aborted: set_metadata_recursive: some changes failed
    set_metadata_recursive: some changes failed
    E:Error executing updater binary in zip '/sdcard/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip'
    Error flashing zip '/sdcard/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip'
    Updating partition details..."

    Not booting system anymore.

    • Jay W.

      did you download from the mirror? the zip file was corrupted :(

      • http://www.innews.dk/ Erroneus

        Nope from google, and verified the file was oki with MD5. Looks like there is some problem, because I'm not alone with this it looks like.

        • jazzruby

          Heads-up the first string of numbers in the filename is the sha1 of the archive.

          Did you have OTA 'Survival' mode set in SuperSU as that would have used chattr to set an immutable bit on the su binaries (hence, your resolution/fix)

          • http://www.innews.dk/ Erroneus

            Yeah I know, I got the MD5 from XDA :)

            I don't remember having enabled Survival mode, but it's on both my Nexus 7 and Nexus 4 running SuperSU v1.69. So it's defiantly possible, thanks for the info.

    • http://www.innews.dk/ Erroneus

      Heads up for anyone else having this problem.

      I managed to fix it, by deleting /system/xbin/daemonsu and /system/bin/.ext/.su , so maybe the OTA update has an issue with SuperSU v1.6?

      Went into recovery, mounted system, connected my Nexus 7 to my PC and from commandline:

      adb shell
      cd /system/xbin/
      chattr -i daemonsu
      rm daemonsu
      cd /system/bin/.ext/
      chattr -i .su
      rm .su

      • Jay W.

        Thank you sir.

      • Rodrigo Gonzalez

        Hey, I'm having a problem with the "adb shell", gives me "error: closed" all the time. I rebooted the N7 and my pc but didn't work, any solution?

        • Rodrigo Gonzalez

          Now I just wipe system by mistake......
          yeap, i think i just kill my tablet. I can't sideload, push, install anything....shit

          • http://www.innews.dk/ Erroneus

            Sorry to hear that mate. Not sure why you are getting the error: closed problem.

            My guess is that your system didn't recognized your tablet. Next time run adb devices command if make sure they sees each other.

          • Rodrigo Gonzalez

            Thanks man, but I've already used "adb devices" and no problem. I've used every solution I've found on the internet (adb devices, kill-server, start-server, restart,etc) for that error, but those solutions are for when your system don't recognize the device. The shell is not working properly, I get that error with adb shell, adb push, adb usb...
            For now is imposible to flash a factory img, I can't push anything, the usb-otg doesn't work, sideload neither....
            Next time I will wait for the OTA

          • Charlie Pearce
          • Raj Bhatt

            Do you still need help with this? It can be done via fastboot. Let me know and I'll walk you through it.

          • Rodrigo Gonzalez

            No, I solved it yesterday :D
            At the end I used the instructions to flash a factory image (never had done before), once I had back an OS (JB 4.3) I flashed the update to KitKat and everything is working fine now.
            Thanks to all of you who respond to my cry of lament xD

          • Raj Bhatt

            Awesome, good to hear! It feels so good to bring back a device from the dead :)

          • Stalemate

            Try the Nexus Root Toolkit, as Charlie Pearce recommended, and if ADB still doesn't allow for a connection try to use fastboot commands instead (manually, through the Android Development Kit if you prefer).


      • Matchstick

        How did you get into adb shell ?

        After the failed install my N7 wont boot and ADB Shell isn't available in stock bootloader or recovery mode

        • http://www.innews.dk/ Erroneus

          adb shell and other adb commands worked here without problems, when I was in TWRP recovery.

          • Matchstick

            Aha, got in via TWRP, but sadly looks like the failed update wiped the /system directory so I had to do a no-wipe restore from 4.3 factory image then sideload the 4.4 update over that.

            Ah well it's working now.

      • josh911usa

        Thank you! This saved me from having to wipe!

      • notzippy

        Know it has been a while, but wanted to say thanks for the hint. I went through 3 recoveries without success until I found this. Although it did not fix my issue it led me to the correct path. I flashed system that I was on then the OTA update worked, so there must have been some other files in there as well causing issues.....

    • Baisil

      i'm getting something slightly different

      someone help me out..i'm using cwm..getting this error...sorry if i'm being a noob

      ApplyParsedPerms: chown of /system/etc/install - recovery.sh to 0 failed: Operation not permitted
      ApplyParsedPerms: chgrp of /system/etc/install - recovery.sh to 0 failed: Operation not permitted
      ApplyParsedPerms: chmod of /system/etc/install - recovery.sh to 420 failed: Operation not permitted
      ApplyParsedPerms: lsetfilecon of /system/etc/install - recovery.sh to u : object_r:system_file:s0 failed: Operation not permitted
      ApplyParsedPerms: removexattr of /system/bin/etc/install - recovery.sh to 0 failed: Operation not permitted
      script aborted: set_metadata_recursive: some changes failed
      set_metadata_recursive: some changes failed
      E:Error in /data/media/0/download/update.zip (Status 7)
      Installation aborted

      • Baisil

        pls someone reply..i am not able to boot

      • http://www.innews.dk/ Erroneus

        Sorry, no idea what causes that problem.

      • Baisil

        Guys I found my solution...got tgz file from Google devs...extracted it in platform tools and ran the .bat file....after some 10 mins....I'm on kitkatphew..that was long day

        • Jay T

          what did you do sir?

      • Jay T

        i have the same problem

  • Robert Alex Kibler

    Just installed it. Everything went without a hitch (except my tablet keeps uninstalling my custom recovery so I have to reinstall the recovery through fastboot every single time I want to use it, but whatever). I installed the GoogleHome apk that was posted here earlier, and while it works, there are some really annoying bugs that made me uninstall it. For one, every time I return home from another app, the keyboard automatically opens. And two, i can't swipe left to get to Google Now. It's just not there. I only have one dot at the bottom for my main screen. If I swipe left, I get the overscroll animation.

    • Dissidence

      Use the Google Experience Launcher, long-press the homescreen, select Settings and enable Google Now. Everything SHOULD work properly then.

      • Robert Alex Kibler

        That fixed it! Thanks! Any idea how to stop the keyboard from opening every time I return home?

        • PhoenixPath

          Hate that. Despise that. Want to throw the darned thing out the window because of that.

          Someone please find a fix for this!

    • jazzruby

      Check for a file - /system/recovery-from-boot - and if found rename by adding a .bak extension.

  • S0l

    Hmmm... Stock 4.3 with Root + TWRP
    getting error with the downloaded zip file using the sideload method. keep getting "failed" at the very end

    re-downloaded the zip 3 times! each time it throws the error when trying to install.
    eventually stuck in bootloop! had to re-flash 4.3

    think i'll wait for the OTA to arrive on my device :(

    • Maemayz

      Supersu 1.69?

    • plastikman

      I'm using cwmr and had to update to the latest version. Mine was complaining about changing the permissions on some system files.

  • Mathieu Poirier

    Can someone check and see if the bootloader version has changed from 4.23? I am having bootloop issues from the supposed 2 different versions of that bootloader floating around, and it won't let me flash an older version, so I'm hoping a newer version can remedy the bootloop. And before anyone suggests anything, I have tried flashing every possible factory image with no success, and I only have access to fastboot, no adb.

    • Mathieu Poirier


  • matt

    think any rom devs will be able to include ART? it isnt necessary but im just curious to play with it, hence the reason i usually flash heavily modded/experimental roms

  • SwankMonsta

    The mirror file doesn't work at all. Did you reupload?!

  • Ian Santopietro

    Just a quick note: if anyone has problems getting the image to verify "Red Triangle in recovery", just download the JWR66Y factory image and flash the system image inside it to system from fastboot. This should restore your system to full stock.

  • Smithers_Jones

    Anyone having problems with SuperSU on N7 2012? All my other Kitkat devices work, but not that one, su just hangs. Tried 1.65 and 1.69

    • Dudley Dowrong

      Yes, I have the same problem. Tried both versions like you did and no dice. Any program requesting root leads to a crash. Hope a new SuperSU comes out soon that fixes this...

  • BlackAce15

    Stuck on the cmd part did "adb sideload KitKat.zip" and it says cannot read "KitKat.zip" any help?

  • http://www.tutrago.com Tutrago.com

    If you follow the Guide, you don't have to download the hoooole SDK, you can just have adb and fastboot installed. Here is the installer http://forum.xda-developers.com/showthread.php?p=42407269 only 2Mb and copy the files in the installation folder....

  • ercl

    Does N7 2012 get any smoother?
    My sis is complaining about the lagginess. Maybe I'll flash stock KK for her, if it's smoother.

  • mgamerz


  • Paul_Werner

    For anyone that prefers Koush's Superuser here's the download:


  • Pengwn

    Yay!! I have transparency with the newest Action Launcher Beta!!

  • Julio

    i have this error.

    no md5 file found..
    verifying current system..
    "/system/app/Currents.apk" has unexpected contents.
    E: Error executing updater binary in zip...

    I tried twrp and adb sideload..


    • Thein Lin Aung

      How did you solve it?

    • DragonMaster

      I had the same problem until i figured it out. In my case i uninstalled all the unnecessary google apps via titanium backup and so the new update file will not find the system apk's necessary to update, and so it will give you an error. Also if you modified any system app or flashed any zip files via recovery from xda or any other source then you will get the same error depending on the apps modified.

      The solution to this is - 1) if you freezed any google apps in titanium then just unfreeze them, don't try to install them from the play store, it won't work (eg google currents in your case, coz when you install the file from play store it gets installed as com.currents.android.apk or some name like that, but instead you need the file with name currents.apk in the system folder Just replacing the file name wont work either coz the logs dont match).

      2) Unflash any zips files if you did so (if you have xposed framework then disable it by flashing disablexposed.zip found on xda. then reboot)

      3) if all the above fails then the only option is to do a clean install of android 4.4 by downloading it from google's developer website.

      You need to make a backup of everything on your device. Backup of all your apps and app data using titanium backup of helium. Backup photos and videos and messages.

      Using TWRP, wipe cache, data, system and rom (basically everything to be wiped)

      Then use abd sideload to install. For one step adb sideload click on the file flash-all.bat in the platform tool folder on your computer and it will do everything automatically including sending system rom on your device.

      Warning: Doing the above way will even wipe custom recovery like TWRP or CWM recovery. Just google it how to install it later.
      But the above solution worked for me.

  • Lpp

    I just flashed supersu but it doesn't show up on the drawer, how can I solve this?

  • JonJJon

    Ah ok so the Nexus 7 2012 Kitkat easter egg screen is a spin-able letter "K" which when held on reveals a Kitkat branding style Android logo with Android 4.4 below it. Not the same as the Nexus 5 one then. I might have missed this said somewhere else though.

    • eeee

      It's the same. Keep pressing the Android/KitKat logo.

      • JonJJon

        Ah gotcha, dumb moment there haha, too late here obviously but just had to sideload the thing :)

  • jazzruby

    Well damn... WTF I got a soft-brick:
    ApplyParsedPerms: removexattr of /system/app/CloudPrint2.apk to 0 failed: Operation not supported on transport endpoint

    script aborted: set_metadata_recursive: some changes failed

    E:Error executing updater binary in zip '/sdcard/Download/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip'

    The update removed files and applied all the patches and boot image and then failed on 'Symlinks and perms' with the above.

    The odd thing is CloudPrint.apk isn't/wasn't a system app.
    I had to fastboot flash the boot and system imgs to get back to a working ROM

    • plastikman

      Update your cwmr. Had the same issue and this fixed it. Flash the new version using fastboot in Tue bootloader.

      • jazzruby

        Thanks, using TWRP I'll flash CWR and give it another go

    • jaara

      You have to use recovery with SElinux support, like CWMR

  • DSiDewd

    Can I go straight to this without wiping if I'm still on 4.2?

  • Mahdi Khan

    I'm pretty new to all this. Do I just click on the download link from N7 2012 and just install or do I have to do anything before hand? My N7 hasn't been modified or rooted in anyway previously.

    • pobautista

      There's a guide linked in the "Install" subheading of the article. Don't forget to back up your data before doing anything....

  • Avri Roth

    What about the Nexus 7 grouper? its also wifi only...

  • Ian

    Thanks, worked great!

  • Thomas Wong

    Since my SIM plan no longer applies, I figure I will just flash my Nexus 7 3G 2012 to Wifi and apply the OTA...

    • http://ridukkokun.wordpress.com/ Dukkokun

      great idea if you want to use your n7 as a paper holder

      • Thomas Wong

        Don't worry... I don't need 3G now. So it's fine for me to have a wifi-only Nexus 7 3G 2012 with Android 4.4 KitKat! :) And I got it working hours ago...

  • Martin Nilsson

    ooo, it has a new boot animation =) I guess it's the same as on Nexus 5 then - pulsing blobs instead of the X?

  • olav

    Won't this work on JSS15R?

  • chingfu

    obviously nobody realized the permission manager is gone... :( apart from practically non-existent changes in kitkat (oh yeah they changed their highlight colour to... white/grey *facepalm*) this is a major setback.

  • Androphoner

    Please i can belive that you root the Nexus7 2013 at the moment now... i'ts not possible with this method.

  • Andy Deeks

    I thought 4.4 was supposed to remove the colour, make things more neutral, but there is still Holo blue on a lot of dialogue boxes! like the power down messages etc?

  • aritra

    what will happen if i just copy it to the device, reboot to recovery, and flash directly with stock recovery?

  • Danyal Butt

    Well I have upgraded to 4.4 via adb and was rooted already..
    Nexus 7 2012 Wifi

    Startup animation is changed but and version number too but other than that I can't see much difference in theme and new feature are missing too, feedback from someone else?

  • Danyal Butt

    Well I have upgraded to 4.4 via adb and was rooted already..

    Nexus 7 2012 Wifi ?

    Startup animation is changed but and version number too but other than that I can't see much difference in theme and new feature are missing too, feedback from someone else?

  • Martin Nilsson

    Worked like a charm - but kind of feel like I should have waited. Everything runs great, looks great and is awesome in general. BUT, I print from my tablet and if the app doesn't support the new print - sorry! I thought I would still be able to use the Cloud Print app, but that's a part of the system now and can't be accessed via intents (share to cloud print).

    I can print from Quick Office, but since no apps support the new storage thingy it can't open any files. Well, I did clear the defaults for docs and PDFs so now it works that way. But still. That's 2 new and pretty major features that aren't, as far as I can tell, backwards compatible and simply just break everything =(

    *added on the Nexus 10 first, now in the right article*

  • loibi

    with adb sideload filename i get the error: device not found. What should i do ?

    • Maxr1998

      You need to install the drivers, also you have to execute cmd as admin... ;-)

  • Jahed Abdul

    hi guys i cant seem to install the kit kat zip im using twrp

  • bolski

    Okay, I have the WiFi version of 2012 Nexus 7. It's running the latest 4.3. When I attempt to flash this update via TWRP, I get the following error message:
    This package is for "grouper" devices: this is a "tilapia".
    Well, from what I understand, "tilapia" is the 3g device. Mine is NOT a 3g device. Mine is the wifi device.
    I have disabled SuperSU as well as the keep root option. It still will not flash.
    Any ideas?

    • Robert L.

      I have the same problem. How did you reimaged your Nexus? Just flashed the Factory Image?

  • Sebatian

    Can someone please tell me if after updating the nexus 7 wifi 2012 the bootloader version is still the same as on 4.3? Cause I flashed the complete 4.4 Google image and I still have the same bootloader version. Thanks in advance.

  • Kisko

    This didn't work for me. I have tried using both TWRP and CWM and both do the exact same thing:

    Unpacking new files
    Unpacking new recovery
    Symlinks and permissions
    set_metadata_recursive: some changes failed
    E:Error in /sdcard/0/Download/*ota zip file name*
    (Status 7)
    Installation aborted.

    It does not boot anymore, just displays the Google logo and then reboots into recovery. I am able to access the files using ADB. Does anybody have any ideas? I don't want to do a factory reset.

    • Daniel Herd

      I had to update my bootloader to 4.23 then go back to stock 4.3 then upgrade. I did part of the work through WugFresh's kit and part through Fastboot.

  • YouJay

    Is anyone else having this problen on KitKat? Touchscreen locks/hangs in Immersive Mode on Secondary User.
    Bug report: https://code.google.com/p/android/issues/detail?id=62366

    • Pete Tandon

      yes. its on all nexus tabs.

  • aritra

    why the original image is 345 mb and the one in this post is only 185 mb?

  • Deven Bender

    Cannot read kitkat.zip file...any ideas???

  • mpmat

    Once I'm in Recovery mode "adb devices" doesn't list my Nexus 7. so the Sideload Command fails with a "no device found". Anyone else running into this?

    • Bo Kee

      In recovery there are no adb, just fastboot commands.

      • mpmat

        Actually I was able to get this to work. The issue was that the Nexus 7 reports a DIFFERENT hardware ID when in ADB Recovery mode. So the Window's driver wasn't being recognized. I had to alter the driver .inf file to include the "new" hardware IDs, and then I could install the driver.

  • Bo Kee

    I have an error status 7 while upgrading via adb sideload. Stock, no root, stock recovery, locked and getting /system/media/bootanimtion.zip has unexpected contents.
    I have recived two ota updates for 4.3 and all went well. Does anyone have a clue what to do. I don't wanna loose data. Thanks in advance.

  • Kostas G

    updated OTA when my n7(2012) asked me to do so and now is slow in everything!!!