Share this Story

Download: Android 4.4 (KRT16S) Official Update for Nexus 7 (2012) and Nexus 7 (2013)

nexus 7 lte verizon

Nexus 7 owners, it’s time to get your Kit Kat on once again. Last week, Google released the OTA zip files for build KRT16O, but this week, a new build is available, KRT16S. You will need to be sure of which build you are running, before you go diving into files included below. Some of you may have already been updated to KRT16O so you’ll need a different file than those who are still on Android 4.3. 

In the links below, we’ve listed out each file with the build you are going to along with the build you are coming from.


In order to flash, you can use the “adb sideload” command through adb and the Android SDK (instructions). If you are stock with root and recovery, flashing the .zip file through recovery often times works.

Cheers Dan and Jesus!

  • blipton

    When Google attempted kitkat 4.4 updating, it bricked my unlocked/rooted nexus7 wifi 2012 (nakasi or grouper er3 I believe it’s also called), with the dreaded ‘Error!’, ‘No Command.’

    Since I don’t see the ‘custom recovery’ option, what would have I originally needed to do, in order to add it? Is it part of wugfresh’s unlocking process or something in Google’s fastboot settings?

    I ask because installing via usb instead of from a file was a pain.. adb sideload complained that the device wasn’t found.. in order for ‘apply update from ADB’ to work, I had to modify ‘android_winusb.inf’ and reinstall the driver:
    %CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_D001

    BTW, anyone know the difference (or which is used for what) between:
    Android ADB Interface
    Android Bootloader Interface
    Android Composite ADB Interface

    In any case, manually installing the update also fails, but this time with some interesting info:

    Installing update…
    Verifying current system…
    “/system/app/BasicDreams.apk” has unexpected contents.
    E:Error in /tmp/update.zip
    (Status 7)
    Installation aborted.

    So something in this screen saver (which i never used) appears is corrupt. I recall running into a similar issue a while back, when it wouldn’t update to 4.1 because I had modified the camera apk to supported hi resolution pictures, but since then I learned not to mess with changing any system apps. Yet here I am anyways 🙁

    Luckily, following these directions using fastboot (not recovery) did the trick without wiping my data!
    http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 or
    https://developers.google.com/android/nexus/images?hl=vi (adding a .tar extenstion to the file inside the tar file)

    *Alternate Reovery Mode:
    Hold volume down and power
    At the next screen, press up until it says recovery mode
    Press power
    You then get the Android with red exclamation
    Press power, hold it and then press volume up

  • Stooge

    Ver 4.4 completely breaks flash.

  • Brad Stephens

    After updating my camera, snapchat, and instagram apps aren’t working at all… Help please

    • John Grover

      Same issue, but only camera app won’t run.

  • JohnPA2006

    Update is installing on my nexus 7 fhd right now, YAY !!! NorthEast PA

  • Jeff Mowbray

    Question for someone. I was waiting for the OTA KitKat 4.4 update on my 2013 nexus 7 and when I go to update tablet it does appear. However it indicates the 242.5 MB update couldn’t download. There is a “retry download” button at the bottom, but when I press it, it does nothing. Any ideas other than sideloading the update?

    • DeJeanne Taylor

      Same issue…. don’t know how to fix

      • Jeff Mowbray

        I actually got the OTA update and all is well

    • mohsen

      I have a same problem, and i don’t know how to fix it, does any body know how can i fix this problem?

  • cornel

    hey guys i need help , after updateing nexus 7 2012 wifi to 4.4 the official from google the tablet does not boot into the OS … it just shows the 4 cercles movong o infinity.. can not connect it to laptop , does not show the adb menu and the recovery from back up does not work sais it does not find any file. what can i do ?

  • Chuck Davis

    I turned my Nexus 7 (2012) on yesterday and was prompted to upgrade to KK 4.4. After installing, it became unresponsive. I now have to power completely down, then power up to access the Launcher, and even then not all the icons launch their apps, ie YouTube. Of the apps that do launch, the “back” button at the bottom of the tablet will not work, rendering the app practically useless. Any thoughts? Ideas? Suggestions on places to turn for answers?

  • Ted Weller

    Ha! After mucho waiting, I tried the cautioned against ‘force stop Goggle Services Framework’ in settings and ‘Clear Data’. When I went back to System Update check, I got the Android 4.4 System Update dialogue box and as I type it’s downloading now. It started out fast but is gotten kind of glacial. Hopefully, the install will go off without a hitch. Ummmm……..now it sped up again and I got the notice to restart and install. Fingers crossed.

    • alex

      how is it now?

  • khemraj baniya

    Use me this programm m…hhhaaa.

  • sparkplug

    Why did my my status bar change to Greg? Where is the blue how do I get it back to blue

  • Ty

    If you still want to use flash don’t update, won’t work with kit kat

    • JohnPA2006

      I removed flash from mine well before it updated. I hated the way ads loaded on some of the web pages, flash ads are super annoying. I am happier with out. Though some of the “adult video content” streaming sites needed flash. Oh well there are plenty more of those that still do work !! :o)

  • whippy

    Got my update just now on Nexus 7 (2012). KRT16S

  • Nurdo84

    I have tried repeatedly to load this, all I get is FAILED. Its everything from error in update.zip to unknown content. I’m on JSS15R going to KRT16S on a Nexus 7 2013 WiFi. I’m so confused as how to fix this, worse however, I’m not sure anything remains on the device…

  • j

    Got the update on my nexus 7 and…. Spoiler alert…after playing around don’t see what the fuss is about!

  • Bob Wendt

    I am still waiting!!! I though that Google would be more adept at this!

  • Bryan Ott

    I got 4.4 on my N10 this afternoon I guess I’m unimpressed. Or maybe the OS is just that Good that it didn’t need a fancy update?

    • djeaux

      After my Nexus 7 2013 got the OTA, the only visible change seems to be a new camera icon & some minor changes in the camera app interface. No GEL, no other obvious differences. “Immersive?” Play Books & Chrome already did the full screen trick in 4.3. I assume some cool stuff happened under the hood, but it must not have been that major because I didn’t lose root.

      For those of you already on 4.3, I say don’t lose sleep over when you get this upgrade. You probably won’t notice 4.4 when you get it.

  • Md . Atiar Rahman

    Please some one help me. I use a nexus 7 2012 WiFi version. My bootloader is unlocked. Currently I am running 4.3. . I download the 4.4 ota update last night and I download it. But when it was installing , it suddenly shows error. What could be the problem ?

    • ImperialMiMi

      I am getting this error too. I even factory reset my N7 2012 WiFi and tried the update again… still get ERROR. WHYYYYYYYYYYYY

      • Md. Atiar Rahman Chowdhury

        i also have had his problem when i was trying to use the sideloader.

        • Matthias von Wachter

          I’ve had the same problem as well. Could not fix it so far as I could not get the phone into fastboot mode.

          • LightByter

            I got my OTA update last night, and it also crashed on install (N7 2012 wifi.) I was able to get into fastboot mode (with great difficulty) following these instructions: https://support.google.com/nexus/answer/2668187?hl=en&ref_topic=3415522
            Still haven’t got it back up yet.

          • Matthias von Wachter

            After getting mine into Fastboot mode by pressing the power button and both volume keys at once, I could flash a fresh image of Android as provided on the Google developer site. But it did take quite some fiddling with the provided flash_all script for me to get it to work. I’ve now got a fresh kitkat on my phone, but my data was lost. I suspect that one could have flashed it without deleting the user data, (remove the -w flag before the flash command in the script) but my phone was ready for a clean install anyway 🙂
            Still I think it’s really a not OK move by Google to deliver an OTA Update that just kills your phone. Shows no regard for the customer. If you’re not paying(for more than hardware costs) you really are just the product, not the customer.

  • QtDL

    When the 4.4 update finally came through last night it bricked my N7. Took some work but had to go back to bare bone stock, OTA up to 4.3, then sideloaded the KK updates. There are quite a few others that reported the same problem on the Google forums.

    • ssjnimma

      ok I had this same issue last night… where can you direct me to get a fix? thanks

    • jian9007

      Had the same thing happen with the 4.4 OTA on my Nexus 4. Borked it and ended up wiping it then I had to push 4.3 back to get it to boot, then finally was able to install the 4.4 OTA. Nexus 7 just gave me an error too. Was able to boot it back up though, minus the 4.4 update. I now await the notification for the OTA again. Google jacked this update up for sure.

  • engemasa

    Interestingly I’m already running KRT16S.

  • Alex

    Where is The nexus 5 review?! I

  • David Gray

    No need to flash 4.4 yourself people…jsut hit the “Check Now” button because as of last night 11/21 at 4:30PM I offically received 4.4 OTA from Google on my Nexus 7 2013 and I am SO HAPPY!!! FINALLY GOOGLE

    • Simon Belmont

      I tried that twice today, on two separate occasions, and nada. Looks like I’ll have to wait for the 100% roll out batch.

      I have a 2012 N7. Hopefully the 100% batch is out this weekend or early next week.

      • Guest

        I’ve been trying

      • Peter Tirrell

        I’ve been trying the ‘check update’ button twice daily for the past week and still nothing. This is on a 2013 N7. Honestly I wonder why they have that feature in there because between this Nexus 7 and my VZW Galaxy Nexus I’ve *never* successfully tried checking for updates and had it pull anything.

        • Simon Belmont

          My 2012 Nexus 7 and GSM G’Nex both always pulled down their updates before I even checked. I don’t think I ever really tried to force a “check” until KitKat for my Nexus 7, though I’m sure I pressed the button for the hell of it a few times in between.

          It’s really never been an issue until this update. The roll out was slowed down and then STOPPED due to a critical device encryption bug and people kept checking but were doing it in vain. It’ll come when it comes. I ALMOST sideloaded it this weekend, but to be honest, I’ve had KitKat on my Nexus 5 for two weeks, so I can wait.

  • Tom17

    I got the update this morning OTA when I turned on my GEN 1 Nexus 7

    • migz

      Is the hotword “ok Google” working when you say it because mine isn’t?

  • Just_Some_Nobody

    People are so impatient for something they’ll dink around with for an hour and then it’ll fade into the background. Your obsessive desire for instant gratification will never be fully sated. Ever. You’ll always want something more; something better.

    Put the internet down and go outside for a while.

  • Thomas Schmitz

    On my Nexus 7 2012 HSPA+ I’m trying to update with the .zip file via CWM, but I get the error “/system/fonts/MTLmr3m.ttf has unexpected contents” and the installation aborts at that point. What am I doing wrong?

    • ProbablyHittingOnYou

      Same here. I don’t understand what’s going on at all.

      • Ronan Eckelberry

        Update CWM to newest. I believe it is or try via TWRP. If you get “Wugs” toolkit it will download all the images, zips, etc for your device and you can flash or just boot to newest CWM or TWRP. Good luck!

        • ProbablyHittingOnYou

          Thanks. I ended up flashing the OS, and it worked like a charm 😀

  • sski66

    The OTA came this afternoon, & right off I noticed the raw speed of it, it’s just great. I didn’t think I would like the white color change of the icons but I actually do, it;s clean. I also noticed if I’m setting a wallpaper from G+ from a folder in the Photo section you see the wallpaper in that full screen, I mean it really takes up the whole screen, it’s pretty damn cool. Also I like the new icon for settings, can’t wait to see what else I discover. O, by the way I’m so glad I updated my N7 to the new one, & this time I bought the one with data. It comes in so handy like today in the waiting room of the DR. office, I think it’s the perfect size, beautiful screen, & now it’s tasty as hell with Kit Kat,hahaha. I hope you guys get the update soon…

  • i just want 4.4 on my s4 play edition…….

  • Flyinion

    Well I guess now I know why it took so long for my 2013 Nexus 7 to get 4.4. Looks like Google changed the version midway through the update. I came home tonight to finally see the update notification but it turned out to actually be this newest version not the older KRT16O version.

    • James Zhangya

      Yeah, if spend so long time to wait ! I think i will get a MYSAGA C1. http://goo.gl/HxDGSy

  • kennyidaho

    My 2013 Wi-Fi finally got Kitkat today.

  • Shadowstare

    *Checks 2013 Nexus 7*
    “System is up to date”
    *Goes back to Guardian Cross*

  • n11

    So uh, where’s 4.4 update? I keep getting “your system is up to date” on my 2013 N7.

    • droidrazredge

      I guess me and you missed the 1% and 50% party. I guess we’ll have to wait for the 100% roll-out party next week :(.

      • Michelle Sierra

        Do you think Google will really give me the update sooner or later

        • palomosan

          You’ll get it soon, just stop pressing check for update.

          • Michelle Sierra

            alright i will give it a try thank you

          • Michelle Sierra

            sorry never had a nexus 7 so the notification will appear in the corner like everything else thank you

        • droidrazredge

          You still have a chance to get it today or tomorrow, but I tend to think we’ll get it later because I am looking at two tablets and neither of them have the update notification so far so I feel that we’ll most likely get it by Monday or Tuesday. It seems the 50% roll-out has come and gone and is reaching the amount of Nexus devices it was intended to within the time-frame of the roll-out for that phase.

  • valapsp

    The audio problem and persistent remove button is still present.

  • NorCalGuy

    In case there are any vz gnex users who want a kk build with no black boxes they should check out slimkat really fast and smooth no reboots and no black boxes with the new 11/21 build!!

  • Jerry

    I received ota today on my nexus 7 2012. I’m really not seeing anything like advertised
    No full screen, no transparent pull down or no saying OK Google on the home page. Only thing I notice is white battery and white wifi. This isn’t what I was expecting at all! This blows!
    Does anyone know if I have to set anything up to have these functions? If so please help

    • Rich Robinson

      I got the OTA as well and yes it’s not as advertised. This is an extremely minor update because it appears Nova offered more a couple weeks ago! Google Experience is also not there….

      • Jerry

        Still scratching my head on this one.
        I watched you tube videos and this doesn’t look anything like it should

        • Laviver

          Same here, Lets hope this is only a preview release, with full functionality coming soon?

          • JerBear

            Kinda doubt it.
            Really not liking the ice colored Wi-Fi or battery either. Looks like I lost Wi-Fi connection

          • DainLaguna

            Thats probably because all the online vids you have been seeing of kit kat have been on the nexus5, which has a unique launcher. alot of kit kats improvements are under the hood. Its actually kinda crazy that folks like you arent aware of stuff like that given the site that you are on and how many articles there have been on the subject.

            not trying to be a dick or anything, its just that this topic has been so like completely covered by droid life, youd have to TRY to miss it.

          • Tarzanman

            That’s not exactly true. I had been paying pretty close attention (in anticipation of getting a nexus 5 and upgrading both of my nexus 7 tablets), but was still surprised when my original nexus 7 got the update, but did not have the same launcher/UI that my nexus 5 has.
            I think that the differences between the implementations have been understated, or completely missed/ignored by most sites doing the coverage.

          • JerBear

            Sorry Dain I don’t have droid life as my home page. You could have stopped at improvements under the hood. I have heard so much hype about Kit Kat through other media as well. It’s not as though I expected a total redesign, but something visually aside from iced Wi-Fi and battery icons would be nice. Aside from visual, whatever is under the hood in Kit Kat I sure have been getting force close in chrome which I never had!

    • Kupari

      If you flash the AOSP release (which is truly stock Android) as opposed to the Google release, you’ll get these functions. Still, it’s a massive annoyance that Google aren’t providing the new launcher for their older devices.

    • lolmaster

      If you go to settings and then language make it US English so you can say OK Google

  • Scott Capodice

    I finally got the Kitkat OTA…ridiculously long wait!

  • droidrazredge

    For some reason even though that Google Engineer said it was bad to press the check for updates as it will reset me queue, my OCD keeps wanting to press it because I don’t have the update yet on my Nexus 7 2013. I guess it’s like those people who keep pushing the crosswalk button over and over thinking it’ll make the light change faster. #FirstWorldProblems

    • Scottyb112

      I guess I should of read that article, because I press it like 5x a day.. Fck!

      • droidrazredge

        I’ve been pressing it about that many times too. Probably makes sense now as to why I don’t have the update and I’m still in 4.3.1 hahaha. Now I see everyone getting the update but me now within the post.

    • Herbie

      Is that true about the queue?

    • Simon Belmont

      It’s not bad to press it. It’s just not going to do anything to make the update come faster.

      Google rolls out their updates on a percentage basis, so if they’re at 25% roll out, for example, it means you have a 25% chance of getting the update. If you press check for update and you don’t get it, you have to wait for the next chance (probably a day or two later), which is 50% roll out, and so on. So, you can press the button all you want, but it’s really a waste of time after the first try (for that day). I usually check once a day at most (still nothing on my 2012 N7).


    Finally got dat OTA!!!

  • Scottyb112

    I still never got the 1st update on my 2013 Nexus 7??

    • michael arazan

      iterally just got my update, the first one, 2 hours ago. The icon finally showed up.

    • palomosan

      I got mine yesterday, it’s actually the KRT16S, meaning that if you haven’t received the update you’ll the latest one (ktr16s) as a whole.

  • Ted Ellis

    Was just about to try this and guess what shows up. The OTA version.

  • fartbubbler

    being stubborn at this point. I COULD flash this, but still waiting on my KitKat OTA!

  • Nate Bousfield

    Repost, My sister decided to be helpful and updated my phone (nexus 4) after I got an OTA notification… The problem is I’m rooted and haven’t made a backup since 4.3. I get a “no command.” error that loops every 30 seconds. Any ideas?

    • Pedro

      My idea?
      Don’t give your sister your rooted phone.

      • Nate Bousfield

        Thanks for the advice.

        • NorCalGuy

          If you can boot into recovery and reflash athe same ROM and gapps as before it might robot other wise you will have to revert back to your backup or reflash a new ROM all together

          • Nate Bousfield

            I’m working on doing that right now.

  • Nick

    OTA download for this unroots FYI.

    Read somewhere that this wouldn’t unroot; but I also ran this update at ~3am. I might have just misread that unroot part.

  • morgan boyle

    i got this update 2 days ago OTA. actually i got the OTA before i even read there was a new update. a first for everything….

    • morgan boyle

      actually, i got this OTA upgrade soon after i sideloaded the first version of 4.4

  • My impatience finally drove me to sideload the original update on Monday and then within hours of the bug fix build being released I got the notification. It seems they’re pushing out the bug fix build faster than the original update.

    • Aaron

      Me too. Had to sideload the update to KK but got this OTA yesterday morning or the morning before that.

  • Jack

    I just got the update and updated my 2013 Nexus 7 from OTA this late afternoon today! Running 4.4 KRT16S now with No problems! Thank you Google!

    • DanielMena9

      Excellent news, first person that confirms they received the OTA. Can’t wait to get home and check my N7 (2013).

      Now to wonder when my LG G2 will be updated to kit kat from 4.2

    • Mezocy101

      Got the same update as well Nexus 7 (2013)! Love it

    • kerrhome

      Same here. Got it tonight for my 2013 Nexus 7. My Moto X got it yesterday though (when I got it in the mail) 😉

      • Jack

        How do you like your new phone Moto X? I am deciding if I should get Moto X on Verizon or wait for Nexus 5 to work with Verizon…

        • jimt

          Your going to have a long wait for Verizon, like forever.

  • DanielMena9

    All I care about is OTA for my Nexus 7 (2013). Us folks that purchased the tablet “before sale” on Friday, should get priority. Early adopters.

    • Guest

      Us folks who bought it on release should get priority.

    • Pedro

      Early adopters should know how to apply the update without using the ‘Check for updates’ button.
      If they can’t, then wait.

      • Jim Foskett

        That’s all well and good if you can get the adb sideload to actually work. I can’t get it so my Nexus is recognized by my computer when it’s in recovery mode. Spent 3 days trying to get it to work. No luck.

        • Andrew

          Same here, my Nexus 7 2013 isn’t recognized in recovery mode, even after lengthy troubleshooting. I tried installing the SDK, reinstalling the drivers, editing the driver .inf file, the universal driver, everything. It doesn’t even show up in device manager if it’s in recovery mode. Driving me nuts.

          • e_droid

            You guys should download Wugfresh’s tool, get the correct drivers installed and I am pretty sure you can run the adb sideload through the program: http://www.wugfresh.com/

          • Jim Foskett

            Sounds exactly like what I did. The Nexus will show up in the Device Manager in recovery, but it has the yellow exclamation icon on it.

  • DanSan

    please stop putting tablets and phones in the dirt! ughhhhhhhhhhhhhh

    keeps getting worse and worse each time. first dirt, then a rock, then inside a water, ontop of wood chipper blades. i cringe each time

    • Flat_Stanley

      I’m waiting for the pictures of the devices in a sandbox. Even thinking about it makes me shudder. Rocks and dirt I’m ok with, but not sand.

      • michael arazan

        Time to put atop driftwood floating in a lake

    • M3D1T8R

      I like it. Makes for excellent contrast in the photo.

    • Just_Some_Nobody

      Personally, I think they should set it on a pile of bricks because the article is about sideloading an update.

    • Cathy

      Time to put atop driftwood floating in a lake

      I just started 7 weeks ago and I’ve gotten 2 check for a total of $2,000…this is the best decision I made in a long time! “Thank you for giving me this extraordinary opportunity to make extra money from home.go to this site for more details http://xurl.es/8wiii

    • hoodieNation

      I wanna see a big muddy footprint on the back of it. haha

    • 12.21

      calm ur god dam tits dude its cleanable & the glass on this thing is pretty strong so yea stop complaining playa

  • Good_Ole_Pinocchio

    Google really needs to figure out the whole slow roll out thing.

    • I think that a beta update feature would work best, something like they do with chrome.

      When you tap the version number 9-10 times you get developer options. Maybe when you tap the top right of the “No updates available” screen it gives you access to beta updates? I think that that would be a good solution.

    • Pedro

      They should send out the update to everyone at once, then get all the bug reports at once.
      Or, like this one, they should analyze the initial bug reports, stop all OTA updates, fix the build, and then roll out.
      Or just continue the updates if they don’t find a critical fix in the initial rollout.

      I waited until Tuesday to apply the factory images for my N10, and immediately had the ’16S update available.

      After about 5 days after factory images out, I thought there might be an issue.

      tl:dr: Issue with rollout discovered. Rollout stopped. Issue fixed. Google did good.

    • Jason B

      They have already. The people who got the OTA first probably reported issues (or even developers), so Google stopped the rollout to other devices. That way they don’t have a larger mess to clean up if the update breaks something.

      That’s also the reason why it’s pushed in phases. They have the server capacity to roll it completely out, but why do that if everyone ends up with a buggy device that doesn’t work as intended?

      Then you just open the flood gates with complaints rather than useful bug reports.

      • Craig Jacobs

        I’m sure this will start a flame war, but I have both Android and iOS devices, and Apple has this figured out. Why can’t Google?

        • michele

          that’s actually not true. I have an iphone 4s since 2011. look at the history of 5->5.0.1->5.1.0->5.1.1 , 6->6.0.1->6.0.2->6.1->6.1.1->6.1.2->6.1.3->6.1.4, and now also 7->etc etc. they all took place in a few weeks.

          • Craig Jacobs

            do you have OTA enabled? I usually get them same day.

        • John B

          Apple has it figured out? I work in an education environment, and iOS6 and iOS7 updates and then updates to those have created MAJOR headaches. Apps quit working, wireless quit working, Apple changing things, etc. It even got so bad that Apple Configurator used to control the iPads quit working, the iOS guys would not share info with them to help update their software.
          Apple has it figured out? Right….

    • Just_Some_Nobody

      They do have it figured out. That’s why it’s a slow roll out.
      You want it faster, there’s ways. Otherwise, it’s really not that hard to be patient for something you’ll play with for an hour and then never again.