Last Updated: November 17th, 2013

Following closely behind the 2012 and 2013 Nexus 7 KitKat OTA updates, it's finally the Nexus 10's turn to receive the same treatment. You can now flash the 219MB KRT16O Android 4.4 build without having to wait for your tablet to alert you, 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.

Unfortunately, I don't have a Nexus 10 (it's the only modern Nexus device I didn't buy), so I won't be able to post my own screenshots. Once one of you or someone on our team flashes successfully, I will update the post with some images.

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 signed-mantaray-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.

preprerecovery prerecovery recovery_DSC4213

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

Screenshot_2013-11-17-12-52-37 Screenshot_2013-11-17-12-52-57

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


Rooting a Nexus 10 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.

Thanks, Kyle Riedemann and Paul Robertson!

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.

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

    Try Nova Launcher with translucent bars and confirm please.

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

      Someone will have to. I don't have a Nexus 10.

    • Edward Germanotta

      Some users report on reddit that nexus 10 doesnt have this because of the processor

    • David

      It's the first time I'm trying Nova just to inform you all, but unless I'm doing something wrong, it only works for me if I hide the notification bar (i.e., it only works when you automatically hide the bar, if it's static, then it's black. Hopefully I'm explaining correctly).

  • andrew zavala

    sweet! can't wait to put this on my nexus 10 when i get home :D Thanks!

  • imperticus

    *comment about N4 and KitKat*

    • annalisedyy264

      мʏ вυɖɖʏ'ѕ ɛх-աιғɛ мαĸɛѕ $66/нʀ օɴ тнɛ ιɴтɛʀɴɛт. ѕнɛ нαѕ вɛɛɴ աιтнօυт աօʀĸ ғօʀ 6 мօɴтнѕ вυт ʟαѕт мօɴтн нɛʀ քαʏƈнɛƈĸ աαѕ $2048з ʝυѕт աօʀĸιɴɢ օɴ тнɛ ιɴтɛʀɴɛт ғօʀ α ғɛա нօυʀѕ. աнʏ ɴօт ƈнɛƈĸ нɛʀɛ fox200&#46com

  • ITGuy11

    Got it!

    • Yash Raj Chhabra

      how is it on the nexus 10 ?? any performance improvements ?

    • David

      Hate that. Waste of space. They should have kept the two pane Settings layout.

      • pfmiller

        Really, what were they thinking?? All that free space yet I still need to back out to switch between settings?

      • bob


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

        No ART.

        • Jdban

          Baw. Thanks!

        • Matthew Fry

          *sigh* Google, what's the deal? Nexus 10 gets the boringest version. But it'll be nice to be able to copy text again.

      • Simon Belmont

        I think it better serves Google's purposes to test ART on their two newest devices. That would be the N5 and N7 2013.

        I'm sure we'll see ART enabled on the older N7 and N10 eventually. It would benefit both performance wise, considering they are older hardware.

        • aSquard

          ART is on the 2013 N7 ^_^

          • Simon Belmont

            Yeah, it is. That's what I meant above.

            Google is testing out ART on its newest hardware. It'll probably trickle down to the older hardware once it's more stable and has more performance benefits.

        • Matthew Fry

          There is a problem with that logic. Currently, the Nexus 10 is supposed to be *the* 10" reference device. It's much more likely that they've only built and tested on Snapdragons.

          • Simon Belmont

            It's possible. AOSP builds of Android 4.4 with ART support are working on anything, though.

            Either way, I'm sure we'll see it eventually from Google. My Nexus 7 (2012) is ready.

  • http://katzmatt.com/ Matt Katzenberger

    Gah. Installed from TWRP. Now I'm stuck on the boot animation.

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

      Wipe cache?

      • Bluewall

        21 times :p

      • http://katzmatt.com/ Matt Katzenberger

        Yeah. Not supposed to?

      • http://katzmatt.com/ Matt Katzenberger

        No big loss. Nothing like a fresh install to really make Android fly.

    • ReturnOfTheMack

      Stick to the latest CWM or stock recovery. TWRP does not work with Android 4.4.

      • bob

        Twrp works fine with 4.4

    • scuttlefield

      I keep getting the same issue...when I can manage to install it, I get stuck at the boot animation.

    • techniq

      I had the same issue when trying to flash with CyanogenMod Recovery (flash would fail and then get stuck when attempting to boot).

      Ended up restoring the recovery partition back to factory from the 4.3 factory image (`fastboot flash recovery recovery.img`) and then adb sideloaded the update.

      • Jaska

        Thank you techniq! Your instructions saved me from factory reset and other harm. Though I should have read some of these comments already before trying to upgrade to 4.4 using TWRP.

    • Sycobob

      Ditto. Fails from TWRP. I did exactly what techniq did, used fastboot to flash stock recovery from JWR66Y and sideloaded it from there instead. The stupid Android with a ! through me off for a while though. I thought recovery was broken, but you have to tap Power and Vol-Up at that screen to actually see the recovery options.

  • Whyzor

    Wouldn't it be easier to save the OTA .zip file as update.zip onto /sdcard path, then reboot into recovery mode and flash directly there, skipping the 'adb' step which gets a lot of people in trouble because of the USB drivers & needing a PC...etc.

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

      With a custom recovery, sure. Stock recovery can't do that.

      • Whyzor

        Ah I thought I did this on an older device with stock recovery, just had to name it 'update.zip', maybe not...

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

          I think that was changed several updates ago. Adb sideload is the preferred and supported method.

  • Michael Romano

    Cool but I'll wait for my OTA update. Don't want to risk things.

    • http://twitter.com/anishbhalerao Anish Bhalerao

      "Hey, why are you sitting in the dark? There is a light bulb switch right here! It's safe and effective, turn it on!"
      "Cool, but I'll wait for the Sun to rise tomorrow."

      • KilpiBan

        Well said dog!

      • Mayoo

        While I agree, for some user it's more like : "Hey my car broke and I could fix it myself. But I prefer to wait for a trained mechanic to do it for me."

        • http://twitter.com/anishbhalerao Anish Bhalerao

          Light bulb and the Sun.

    • Stonethrower

      I got my update OTA and now the pad is stuck in an endless loop had to contact Google they have promised me a replacement.

  • Itaré

    My S2 with CM11 has ART.

    • Kieron Quinn

      Well it would do, it's built from AOSP

  • Rey Perez

    I updated my N10. Visually pretty much looks exactly the same as 4.3 with the exception of the status bar. I do get the expanded screen when in Books but other than that there's really nothing to be excited about since all the cool front facing features from the N5 have been left out. Scrolling in Chrome might be better, or it could be placebo.

    • PhoenixPath

      I noticed right away my Netflix "fullscreen" icon is gone now as well...and black bars remain top and bottom.

      Hopefully it's something that will get fixed relatively quickly. No need for the bars in 4.4.

      Would also love transparent notification bar/navigation.

  • Markus Ressel

    I get the error:
    set_metadata_recursive: some changes failed
    E: Error executing updater binary in zip "filename"

    I tried Dalvik/Cache wipe and reflashed the System.img from 4.3 factory image (JWR66Y) but it didn't help :( I don't want to wipe it completely :S

    • BrianLipp

      just went through this myself. Tried a bunch of stuff, even factory reset back to latest 4.3. Youre using TWRP, and they havent released a new version that works for 4.4, so you have to switch to CWM and flash the zip, and it will work

      • Markus Ressel

        I tried it with the stock recovery now (via adb sideload) and it worked. Thx :)

    • scuttlefield

      I got this same error, then got caught in a bootloop (with the KitKat boot animation). I reflashed back to stock 4.3 but got caught in a bootloop again. :-/

    • Dave

      Are you rooted and running SuperSU 1.69? was having the same error, so I uninstalled SuperSU updates, then the 4.4 update was successful.

  • BrianLipp

    What the hell, why did they get rid of the Fragment UI in the system settings? Googles gone crazy with 4.4

    • bob

      Looks loads better to me. Way too cluttered before

      • BrianLipp

        its a bunch of wasted space and animations and loads. theres enough screen real estate to show the option and its settings. now 90% of the screen is empty for no reason.

      • pfmiller

        I don't care if it was cluttered before. Maybe the use of negative space in the new version is as beautiful and meditative as a Buddhist woodcut, but as a settings app it is less usable.

  • http://gplus.to/mbirth Markus Birth

    I can't seem to be able to root mine using SuperSU-1.69.zip. TWRP reboots during "Restoring files". CWMR completes, but after booting the N10, it is still unrooted. What's the trick?

  • Leo Kanellopoulos

    already flashed :D

  • TylerChappell

    It's amazing that the 2013 Nexus 10 seems to be the best kept secret this year.
    Where is it? I wanna drool over its potential specs...
    Same resolution display, probably a Snapdragon 800, between 2-3GB of RAM.
    I mean, there WILL be a 2013 Nexus 10, right? I hope they aren't waiting until 2014.

  • Markus Ressel

    Why did they move the up/down indicators from the wifi icon to the quicktoggle icon? Doesn't make any sense to me. Besides really good low level and "under the hood" improvements 4.4 isn't a very good update imo :S

  • Moeen Ahmed

    my pc wont recognise my device in recovery mode. finds it as mass storage but when flashing the image it cannot find it. have all the latest drivers from android sdk. not sure why it wont recognise it...

    • Mike Cline

      I have the exact same problem... searching and searching for a solution. Windows Device Manager shows "Nexus 10" with an exclamation mark. When I try to update the drivers while in Recovery Mode, I point it to the driver directory and it says it can't find the drivers. However, outside of Recover Mode, Nexus 10 shows up as working with fully up-to-date drivers. It's appearing like it's an entirely different machine when in Recover Mode. Likewise, I can see the device with "adb devices" when running normally, but not when in Recover Mode. "adb sideload" command fails with "error: device not found". Help please!

      • Mike Cline

        FYI -- found a way to get past this. Seems that the device reports a different "Hardware ID" to windows when in recovery mode, making the drivers not recognize it.

        This thread here was helpful: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/

        I went in to device manager, clicked on Nexus 10 and went to details, found the device ID:

        Then added a line to my android_winusb.inf file:
        %CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_D001&REV_0226

        Then reinstalled the driver and it worked!

        • Moeen Ahmed

          thanks will try this

  • Guest

    Had the set metadata error. I was rooted with SuperSU 1.69. Had to uninstall updates to SU, then the update worked.

  • CERN

    No love for tilapia? Argh! Bankai!

  • ero1112

    thanks for bricking our tablets ... just flashed the zip file and already waiting 8 minutes at the boot logo.

    • David Sousa

      You don't know what brick means. Nexus devices are almost unbrickable (messing with the bootloader being the only probable reason for doing so).

  • cinval

    I followed (`fastboot flash recovery recovery.img`) and adb sideloaded the update ref techniq's post. this worked ok BUT the notifivation bar only works if I drag the left hand side. no right hand drag to get at settings.. anyone else have that?

  • Michael Pahl

    Can we please get an AP mirror for 2013 nexus 7?

  • Guest

    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 =(

  • John-Smith

    I feel like I've wasted so much time waiting for the updates, reading articles, searching etc...

    I think I will just wait for everything to come over the air for all my devices instead of wasting more time.

  • Andres Schmois

    What the hell has Google done on the N10.... All the blue is gone. First keyboard blue gone, now Android UI blue gone? I don't think Google remembers what Android 2.0 looked like. It seems as if they're going backwards.

  • icyrock1

    For those who updated; how's adobe flash player working (are there any problems)?

    • bob

      Same as always... In other words, badly. Flash needs to die and get replaced quickly