Skip to main content

How to manually update your Nexus tablet to KitKat [updated]

With the right tools and a little knowledge, there's no need to wait for your OTA

Update: Nexus 7 (2012) link has been added. Get to flashing!

Update 2: And the Nexus 10 is now good to go.

The Android 4.4 update has started rolling out to the Nexus 7 and Nexus 10 tablets around the world. But if your tablet has yet to receive the update, then don't despair — we've got a quick walkthrough that'll get you updated in a few minutes, assuming you've got a little experience with a command line.

Note that this is for stock Nexus tablets, and for people who want to update without really doing any real hackery, but don't mind a little command line work. Nothing we do here is permanent, other than the update itself. If you've already flashed a custom recovery, you should be able to update manually using that, instead of our method. And with that...

Caution: This guide is intended for technically proficient users only. Proceed at your own risk. Dragons ahead, etc.

The prerequisites

  • A completely stock Nexus tablet running the latest build of Android 4.3
  • The latest version of the Android SDK installed
  • The OTA packages (those here are for Android 4.4): Nexus 7 (2012); Nexus 7 (2013); Nexus 10

Check past the break to see the full manual update process.

The process

  1. Place the update .zip package from Google in the Android SDK/platform-tools folder on your computer, but do not unzip it.
  2. On your Nexus, go to Settings > Development options and switch the toggle on. Then enable USB debugging under the "Debugging" menu group.
  3. Power down your tablet
  4. Start up the bootloader by holding down volume up, volume down and power on your tablet.
  5. When the menu loads, plug your Nexus into your computer.
  6. Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
  7. When the Android with the red exclamation point appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. 
  8. Use the volume up/down keys to select "apply update from ADB," then press power to select it.
  9. On your computer, open up a command prompt or terminal window.
  10. Using the command line, navigate to the Android SDK/platform-tools folder 
  11. On Windows, type:
    adb.exe sideload <the complete name of the OTA zip file you want to flash>
    ... or on Mac, type:
    ./adb-mac sideload <the complete name of the OTA zip file you want to flash>
    ... or on Linux, type: 
    ./adb sideload <the complete name of the OTA zip file you want to flash>
  12. The update should begin installing. When it's done, select "reboot system now."
  13. Enjoy some delicious KitKat
Jerry Hildenbrand
Senior Editor — Google Ecosystem

Jerry is an amateur woodworker and struggling shade tree mechanic. There's nothing he can't take apart, but many things he can't reassemble. You'll find him writing and speaking his loud opinion on Android Central and occasionally on Twitter.

242 Comments
  • Mages, I hear its to best to bring your wand and cape, archers and knights fumble when exploring the dungeons. - Android Central App. Remember courage is contagious.
  • On it. XT1060 via Android Central App
  • Wouldn't it be easier to put the downloaded .zip file onto the device's /sdcard path, then boot into recovery & select flash zip. Skips the whole 'adb' part, which can be frustrating for a lot of people to get the finicky USB drivers working.
  • True, but this guide is specifically for people who haven't flashed a custom recovery.
  • You can use WugFresh's Nexus Toolkit to revert back to stock recovery if you have a custom recovery flashed. Very easy to use.
  • You can use WugFresh's Nexus Toolkit to revert back to stock recovery if you have a custom recovery flashed. Very easy to use.
  • How do you get the option to select flash zip? I only have the option to apply update from ADB.
  • The option to select the zip to flash is only for those who have a custom recovery installed. If you do not, just follow the above instructions and you will be fine.
  • I did the same and bricked my Nexus 7.
  • I don't see an sdcard pathlisted on the internal storage.? Any advice?
  • So when is the Update for Nexus 4 coming ???
  • When it comes... When it comes... Posted via Android Central App
  • Haha...Want it now,lol :-)
  • Does this have GEL?Its being reported on Google plus that after the update completes a sweep menu appears asking if you want the GEL launcher and after you open google now,downloads it
  • Can you put a link?
  • I hope this is true. I heard rumors of it not having the Google Experience launcher on the tablets.
  • It does not, but you can easily install the APK.
  • Hay guys just wondering does this wipe all data??
  • If installing by ADB sideload method, no, it will not wipe your data.
  • It shouldn't, it will run the same scripts as an OTA Posted via Android Central App
  • If you don't know how to wipe the data on your Android device, then best you not attempt to manually update it. Posted via Android Central App
  • Side loading 4.3 on the Nexus 4 and 10 caused play store issues. Anyone try this method and ran into issues? Posted via Android Central App
  • No problems here with 4.4 works as it should and no I didnt wipe and everything is the way it was before the update, no need to wipe an official sideload update folks as long as you are stock and not rooted it is the same as if you had accepted OTA.
  • You sure those issues weren't because of the "clear framework trick" people were doing to try to get the OTA faster?
  • I've done everything said step by step, but when I go to side load the file on the command prompt, I get the message "'adb.exe' is not recognized as an internal or external command, operable program or batch file." I've tried just adb sideload but that doesn't seem to work either. I had downloaded the latest SDK just then and installed the packegs with SDK manager.
  • You may of skipped step 10. Or did it wrong.
  • You may of skipped step 10. Or did it wrong.
  • Have you navigated to the platform-tools folder in cmd? Posted via Android Central App
  • You have to define adb first. Go to my computer-properties-advanced-define environment variables. Set the name as adb and location as C:/android/platform-tools or where ever platform tools you have installed. Sent from my White Nexus 4.
  • Or just simply put platform-tools in your path so it will always be there when opening a terminal...
    http://m.windowsitpro.com/systems-management/how-can-i-add-new-folder-my... Posted via Android Central App
  • Will sideloading a non rooted N7 2013 format my device?
  • It shouldn't but its always good to have a backup ;) Sent from my White Nexus 4.
  • It will not wipe it. Worked perfectly on my Nexus 7. Posted via Android Central App
  • It's so funny about updates. I'm like you guys and dying to get the latest greatest software all the time. All of my friends though get mad when they have an update. Some will never install it unless it finally makes them. Posted via Nexus 5
  • It doesn't help that Windows 8 completely forgets the ADB process every time and you have to start from scratch with new drivers every time you've used more than one nexus on the same PC.
  • Looks like the only update that is actually pushing out is the Nexus 7 2013 WiFi. Anyone gotten the update for either the Nexus 10 or the 2012 Nexus 7? Kind of suspect it's going to take close to a week for everyone to get Kit Kat on these devices and the Nexus 4 won't see it until after that sometime. The "several weeks" comment that Google made about Kit Kat rolling out to other devices was clearly aimed at the Nexus 4, wouldn't surprise me if the Nexus 4 doesn't get it until December.
  • Well I have the 2013 N7 and haven't gotten it yet... It's weird, Google should allow those who actually care about the update just be able to hit the update button and update. Those who don't care as much or don't know about it should get it last.
  • Thanks for this. Easy, tho I had to reacquaint myself with DOS my commands. It had been awhile.
  • i cant seem to get into the bootloader? does it need to be unlocked before i can gain access? i am new to this so i am unsure
  • Jerry mistakenly said the Up Volume AND Down Volume buttons. For the Nexus 2013, it's just the Down Volume button and press the power button for 2 sec or so.
  • Lame. Can't do this on Server 2012 R2. Computer wont install a driver for the nexus 7 in sideload mode. Can we just rename it to update.zip and install it that way? Or I guess I could just wait >.<
  • I'm having the same problem with Windows 7.
  • I wonder if it's a 64bit driver problem. Anyone completed this on 64bit Windows 7/8?
  • I just did the update from my win7-64 machine with no problems
  • Turns out the inf file didn't have the correct device ID for the new nexus. So after adding the correct ID, and rebuilding the .cat file, creating a temp cert, and disabling driver signing, it worked. Lot of trouble for not a lot of change. Dayframe is prettier though :-P
  • Worked like a charm, thanks guys Posted via Android Central App #HOLOYOLO
  • Can someone please elaborate on how to perform Step 10? Everything else seems straightforward. Posted via Android Central App
  • Be sure you have the Android SDK installed on your computer. Go to the platform-tools folder. You can start a command window here by holding shift and right clicking the folder - then click "open command window here". Now you can start with your adb commands. I always start with the command - adb devices - to make sure everything is working correctly Posted via Android Central App #HOLOYOLO
  • Right, and when it's not--device list empty--you can waste a whole lot of time trying to fix. My PC has no idea what to make of my Nexus 4 or 7 (2012). Haven't found a solution. Maybe I should just completely uninstall the SDK and start over in case the version I brought out of mothballs and updated today is the culprit. Though if I can't find drivers to recognize the devices at baseline, can I blame the SDK? Posted via Android Central App on Nexus 4
  • this may help http://www.theandroidsoul.com/nexus-7-2013-drivers-installation-guide/
  • that was the best mot clear advice ever
    thank you
  • Anyone else having trouble getting this to load? I'm rooted and unlocked on a WiFi '13 N7 and I'm trying to install it through recovery. I've tried CWM and TWRP and downloaded the package 3 times. It keeps failing. Posted via Android Central App
  • Same. Tried CWM and TWRP. CWM error is:
    "EMMC: /dev/block/platform/msm_sdcc.1/by-name/boot ...." has unexpected contents.
    E: Error in /tmp/update.zip
    (Status 7)
    Installation aborted
  • I've tried renaming the file to "update.zip". I've tried installing from SD card.
    What the hell?
  • Same problem here. Any solution yet?
  • Same status 7 error here on 7 2013. I tried a bunch of tricks I found online to no avail, including sig verification toggle, editing a script file, renaming the file and a couple more. Still, status 7. Would suck to have to revert back to factory stock and getting OTA that way. But finding no other options. I tried beeing rooted and unrooted. I am unlocked. OTA downloaded fine. Started in stall, rebooted into recovery awaiting a prompt from me. Found the file and continued install until I got status 7 error.
  • me too. And I just found out that they purposely changed the files in 4.4 so you cannot sideload it when rooted because of the partitions. I had to unroot.
  • Do you know if it's possible to unroot so the ota flash can go successfully? I have stock rooted 4.3_JWR66Y and I dont want to wipe and apply the 4.4 Kitkat ota.
  • I can't get this to work, period. As soon as I enter Recovery Mode, I lose driver support in Windows 7 (and, thus, connection through ADB).
  • Did you confirm ADB was working correctly before entering recovery? Try the command - adb devices - before you go into recovery to make sure it list your nexus 7 Posted via Android Central App #HOLOYOLO
  • I did, but thanks for the tip. It works when booted into the OS. It works when in the bootloader. It does NOT work when booted into Recovery mode.
  • Same happened with me. Updated/reinstalled the driver, worked. But now facing a problem after the command for sideloading part, installation aborted status 7 unexpected content
  • Same issue here. Win 7 driver is good up until I enter Recovery. If anyone has suggestions I'd love to hear it.
  • http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-... It's a bit of extra effort but it did the trick.
  • i'll give it a shot. Thx!!
  • Worked for me too. Appreciate the assist!
  • This fixed the driver issue. Not sure why they would have left out the proper device ID?
  • This let me connect to my Nexus 4 in recovery! Thanks so much for the link!
  • Well, I've had it with this driver BS. I've fought with this for an hour. I used those instructions and now it will recognize the device in pre-recovery boot menu, when I go into recovery, it stops recognizing the N7. I've uninstalled, reinstalled, updated software of drivers....what a piece of junk system this is. I have the Nexus 7 (2012). I've read countless articles about how to get it to recognize and nothing has worked. Thanks fer nuttin' google. By far the worst experience I've had with an Android device and I'm not a novice at this.
  • Same here. I am on Win7 64bit and I get the same problem. Please let me know if you find a fix and I will do the same.
  • I had the exact same problem and then I found this article. http://helpdesk.rsupport.com/entries/21710102-Installing-the-Generic-Goo.... Get your device to the install from ADB screen and then follow Step 3 to install the drivers for "Android Composite ADB Interface".
  • What I'm getting is that when I go to recovery, I get "no command" underneath the triangle. I am normally pretty alright with this kind of thing. But unable to get any further. Help would be appreciated
  • Absolute awesomesauce, cheers man. Hopefully the guys here will update the post with that.
  • If you're using the latest mac SDK, there's no adb-mac (at least not in the one I downloaded today).
  • What do you mean, theres no adb-mac? I have the latest sdk.
    name here-iMac:platform-tools my name sideload
    -bash: syntax error near unexpected token `newline'
  • dont type "adb-mac" just type adb
  • i did that, installed sdk (I'm assuming I have after clicking on the Eclipse.app file), navigated to the directory, and typed in "./adb sideload still getting -bash: syntax error near unexpected token 'newline'. Am I missing a step?
  • oop nevermind. i got it. haha. it's already posted down below, but JIC, make sure that you're device isn't in the recovery mode for too long before you start sending over the update through terminal. and also the file name doesn't need to be in between the < & >. JIC people made the same mistake as i did.
  • Jerry, for the Nexus 2013 you only hold Vol-Down, holding both up and down will not work. Just figured you'd like to correct this for the first timers :)
  • Should have reloaded my page to see this before I posted the same thing right below hahaha oh well
  • Didn't take the time to scroll through and see if it was already there, but to get into Bootloader, all you need it VOLUME DOWN + POWER, not both volume keys. Thank goodness for Cyanogen Mod's website being awesome and telling me that :) UPDATING NOW!!!
  • Was going to post the same thing that the instructions in the post were wrong. Thought my Nexus was messed up since holding both volume up and down with the power button freezes it. The only way out is to hold the power button for 15 seconds.
  • Im on a mac and I cant adb sideload "
  • If you did not create an environment variable for adb, you need to navigate to the folder and use ./adb instead of just adb.
  • I'll be trying this tonight. Thanks guys.
  • After sideloading the Nexus 7 (2013) zip file I got an error: Now send the package you want to apply
    to the device with "adb sideload "...
    Finding update package...
    Opening update package...
    Verifying update package...
    E:failed to verify whole-file signature
    E:signature verification failed
    Installation aborted.
  • I think this error might be due to me having a Nexus 7 (2013) LTE.
  • NEXUS 2012 --> W/ 3G Everything works until it tries to install and then I get the same error: Now send the package you want to apply
    to the device with "adb sideload "...
    Finding update package...
    Opening update package...
    Verifying update package...
    E:failed to verify whole-file signature
    E:signature verification failed
    Installation aborted.
  • Did you ever figure this out? Getting the same error.
  • anyone?same problem here...
    please help
  • Worked great heat. Booting into KK as I type this.
  • nvm what i said, on mac u have to do ./adb devices then ./adb sideload KRT16O.zip.
  • Does the bootloader need to be unlocked for this to work? My Nexus 7 (2013) won't even boot into the bootloader. The screen just goes black until I restart the tablet as normal. EDIT: Follow the above tips on just using power and volume down to get to bootloader.
  • I found first that I could not get into the bootloader with the power/volUp/volDown, so I looked online and found that If you have the Android ADT tools installed that you can do the command line option of "./adb reboot bootloader" command (mac and linux), or "adb.exe reboot bootloader" (win). This will dump you into "Step 5." But as soon as I ran that command, while in Win7, and USB Debugging on, I had to authorize my computer on the N7's screen. So I did this, and then found that once in the bootloader and selected the recovery mode, that unlike what it says in "Step 7", I had to repeatedly press power and volUp to get the recovery options. Once "update from ADB" was selected, pressed power, I realized that Win7 no longer wanted to comm with the N7. So I gave up and booted my PC into Ubuntu to try my luck there. So I then made the first mistake of leaving the N7 in the state where it was waiting for ADB (in the recovery mode), and then tried to type in "./adb sideload LONGFILENAME.zip" at the linux shell (in the appropriate directory as layed out for us here). I got a permission error. Typing in "./adb devices" showed a bunch of "???????", and there was my permission error. Remembering that when the N7 was booted, and I tried to do the adb bootloader command from Win7 I got an accept this computer dialog on the N7, I booted the N7 back up, and tried the "adb reboot bootloader" again from linux and got that same dialog again and finally authorized the Ubuntu install I'm using. When I got back to the recovery mode, I typed in the shell "./adb devices" and it showed a device name in hex (I guess), meaning that I was able to see the N7 finally. Then I just typed in the "./adb sideload VERYLONGFILENAME.zip" command again, and it finally took. Hope this helps some of you even though I know most of you probably don't have a linux machine/install going. But there is definitely a problem with Win7, even if you have drivers installed properly. NOTE: 4.4 Booted up while I wrote this, no Google Experience Launcher that I can see. Oh well. At least it booted up!
  • when (on linux machines) adb get you permission error, the quick/dirty way to do it is just run it as root. >> sudo bash
    >> ./adb kill-server
    >> ./adb devices => and it shows there the device number
  • Thats what I needed. I kept getting the permission error, tried this and now kit kat is going on my 2012 Nexus7
  • Did everything and it says abd is connected. when i type in my file adb.exe sideload and i type my file KitKat.zip it says error: closed
  • Were you able to find the source of this error? b/c im getting the same one..
  • Please post a resolution for this problem if you have one.
  • Here is an excellent guide on how to use adb sideload in windows for any of you having issues. This goes into more detail. http://www.droid-life.com/2013/02/12/guide-how-to-use-adb-sideload-to-up... Cheers for the links Jerry. Posted via Android Central App
  • Nexus 7 (2012)... GIVE ME THE FILE!!!! :(
  • Agreed need zip file for my precious Posted via Android Central App
  • I don't think the upgrade for the 2012 has actually been released despite Google's tweet last night. Haven't found anybody that has received the update for a 2012 Nexus 7, there are no binaries available, and the images are not there. Strike 1, 2, and 3... It's probably won't be released for several days or weeks... Nexus 4 hopefully by Christmas, but wouldn't bet on it. Google seems to be having "issues" for whatever reasons with getting the Nexus updates out in a timely manner this go around.
  • http://android.clients.google.com/packages/ota/google_nakasi/13088e35942...
    Nexus 7 2012 (Wi-Fi) Saw it in XDA ;)
  • ok so i did adb kill -server than adb start-server it connects . when i type in adb devices it shows emulator- 5554 device i than try the sideload and it says error device not found
  • How come this update does not look like kitkat on Nexus5? still see the widgets in the apps menu and long press does not bring me the new menu, icons are sized the same than before.
  • The Google Experience was not included.... an APK is floating around to add it though.
  • Thanks Ashram, after doing some searching looks like the Google Experience is only included in the Nexus 5 so far which is a bit sad considering that a bunch of GUI twinks are part of it and does not come out of the box with KitKat 4.4
  • successfully sideloaded the update and now have 4.4 what major improvements are there on the Nexus 7 (2013) over 4.3??! I don't see too much.
  • Just saw this in XDA: http://android.clients.google.com/packages/ota/google_nakasi/13088e35942...
    Nexus 7 2012 Wi-Fi
  • Got me by 3 minutes LOL
  • Holy mother of God...That was a b!tch to deal with. After realizing I have to add some code to the driver file to recognize the device, it finally worked!
  • What's the code you're referring to cos I keep getting the "device not found" error?
  • I attempted to add hardware IDs my PC is seeing when the Nexus 7 is in recovery mode to the inf file, but I don't really know what I'm doing...and it didn't help. Posted via Android Central App on Nexus 4
  • Man............I had the same problem! Windows XP would see my Nexus 7 (2012) through the command "adb devices", but once I got into recovery it wouldn't show it as a connected device. AND whenever I got into recovery device manager kept coming up trying to install drivers and couldn't find the right ones. I had to edit the hardware ID in the "android_winusb.inf" file. This link was what helped me. ARGH!!! That took me a couple hours of searching around. Glad to be rolling with KitKat on my N7 though! :-)
  • Fu*king brackets!!! Why didn't you write that I shouldn't input them too!? Spend an hour to get that. I know this is my fault, but anyway you may now quit reading my post-Post forum signature :)
  • Fu*king brackets!!! Why didn't you write that I shouldn't input them too!? Spend an hour to get that. I know this is my fault, but anyway you may now quit reading my post-Post forum signature :)
  • Cool,
    Thanks for the help Jerry. It's always feeling being a genious when you have help... lol...
    Followed your procedure listening the White album.
    Saw the first boot listening to Back in U.S.S.R.... Quite a good feeling...
    Got it root, and seem to work very well will ChainFire latest and TWRP (latest)...
    Thanks again... I'm a huge (!!!) fan...
  • Strange... When I noted the version number of the software I got that notice: This post has been automatically been marked as spam. Please revise your comment to either remove links and/or references to money. If you are still having problem, please e-mail site support and include a copy of the comment
  • Thanks. Worked fine for me. No transparent launcher but like the new lock/touch sounds. Have to get used to the new statusbar colors.
    Keep up the good work. Posted via Android Central App
  • Does it have the GEL launcher? if you swipe left you get the google now screen?
  • Nope. I sideloaded that to. Posted via Android Central App
  • Use gravity box for the transparent nav and staus bar
  • Link for the Nexus 10 (from xda-developers, haven't confirmed myself yet): android.clients.google.com/packages/ota/google_mantaray/279e5e2396480cbffd97943a5db5bbc743ef7e77.signed-mantaray-KRT16O-from-JWR66Y.279e5e23.zip
  • I cannot get the hidden menu in stock recovery to show up after hitting volume down > then quickly hitting volume up. Anyone else?
  • I have done it without any trouble. First hold power button down, while still holding the power down, tap once the volume up button. Then the menu comes out to select update from adb among other choices.
  • Just saw this on XDA - Nexus 10 OTA link I just pulled from logcat: android.clients.google.com/packages/ota/google_mantaray/279e5e2396480cbffd97943a5db5bbc743ef7e77.signed-mantaray-KRT16O-from-JWR66Y.279e5e23.zip
  • Not to be mean but, I don't think 2102 has happened yet. Posted via Android Central App
  • Just used this process to update my N7 2012, Thanks Jerry.
  • I think I can wait a day or so. There aren't any earth shattering changes so whenever I get it is fine with me.
  • Actually as a KitKat user on the Nexus 5, I have to say that 4.4 is a huge step forward from 4.3. 4.3 was/is great, but 4.4 seems to be so solid when compared. Regardless whether you wait it out or manually update, you WILL see and notice a difference.
  • Sadly it seems the 2012 did not get the whole 4.4 advantages.
    I can't use "ok google" on the home screen, I don't have the new launcher. I don't get full screen even in the google apps etc'
    I did however notice faster response times.
  • Damn that sucks. I haven't completed the update, ran in to a status 7 error so had to wipe cache and start over. Should be done shortly and will check it out. Wish we got the full 4.4 but as long as it at least brings on better performance, that's better than nothing I guess. :-)
  • Send me a pm and I can send you the links for getting all the 4.4 advantages. They are coming ;)
  • Will an OTA update de-root a rooted device? Will I have to setup everything again? Ta. Posted via Android Central App
  • Yes and no. For me, TWRP and CWM have always offered to retain root access after installing the update. I just installed the update.zip in CWM (couldn't wait for the OTA) and reinstalled the SuperSU .zip *before rebooting*. When I booted up, I was running KitKat with my SuperSU root access still intact.
  • Tried this method with TWRP, but it fails. What am I doing wrong?
  • Same, does not work with TWRP.
  • Where would I get the SuperSU.zip file?
  • No provlem. Found it at Chainfires home site. Just being lazy...
  • YES! Thanks for the updated links Jerry! Updating my N7 2012 as we speak. :-)
  • I assume this does not apply to the lte version?
  • Worked so much easier than I expected! Dropped the update.zip into my Downloads folder, installed it via CWM, reinstalled the SuperSU .zip to retain root access, and voila, my beloved Nexus 7 runs on KitKat. A little miffed though that not only did google skip the Experience Launcher for the Nexus 7, but also updating the app drawer icon/page scroller as well as leaving out the setting to manage installed launchers. Nova Beta it is for me!
  • Nexus 7 2102?? Whoa, man. Can't believe that's only just now getting KitKat. :P
  • Don't know if it is placebo or not, but my Nexus 10 feels faster Posted via Android Central App
  • How do you get the N10 t accept an update via ADB in recovery? Holding power and up just reboots for me, holding power and down puts it in download mode and ADB can't see it. EDIT: Got it. Right combo just held it too long. Doesn't help that I can't ever tell which button is up and which one is down in the bootloader/recovery!
  • I was able to sideload the zip, but then I get this before it updates Warning: No file_contextsVerifying current system Then it say patching....
    Upacking.... Then
    E:Error in /tmp/update.zip
    (Status 7)
    Installation aborted Anybody else get this? How did you fix it?
  • I got that too but i dont know what to do
  • I just updated my fine. But I had to restore to stock first. Then the install went perfectly. So far seems a lot smoother. All the normal Play Store app install fine, root OK, but tweaks from expose is not working Posted via Android Central App
  • I going to put the whole log here
    Restarting adbd...
    Finding update package...
    Opening update package...
    Installing update...
    Warning: No file_contextsVerifying current system...
    Removing uneeded files...
    Patching system files...
    Patching boot image...
    Unpacking new files...
    Unpacking new recovery...
    Symlinks and permissions...
    set_metadate_recursive: some changes failed
    E:Error in /tmp/update.zip
    (Status 7)
    Installation aborted. Any advice on what I should do from here? Thanks
  • See my comment a few posts down Posted via Android Central App
  • Great . Thanks worked great for Nexus 7 2012 Posted via Android Central App
  • When I type in the command it says "the syntax of the command is incorrect" can anyone help me out?
  • Are you typing the command after navigating the the platform-tools folder?
  • worked like a charm on my new nexus 7 2013 and on my friend's nexus 7 2012 without any fuss
  • Anyone have any ideas about why I might be getting error:device not found on step 11? I can reboot the bootloader just fine from the command prompt.
  • I had the same error, and needed to manually install ADB drivers. Worked like a charm after installing. Google Koush Universal ADB (Android Debug Bridge) Driver for Windows
  • THANK YOU!!!! Win 8 was being a tool and would not let me install any other drivers this was the only thing to fix mine but up and running enjoying that kit kat goodness !
  • If drivers dont fix it, make sure you turn off the option where it mounts the device as a media device.
  • Just noticed I have JSS15J on my 2013 N7. Anyone have any idea why I never got the 15R OTA? I'm guessing that's why 4.4 won't install...
  • You modify anything? If not, just manually update to the latest 4.3 and go from there. Posted via Android Central App
  • Followed the directions and it worked perfectly.
    Well, perfectly after I manually installed the android adb driver.
  • Followed Jerrys tutorial to the letter and was not able to do it as I'm sure there were lots of steps left out. Where's the idiots guide to doing this?
  • Worked perfectly. Thanks for the tip!
  • apparently, adb sideload is not on whatever version of the android SDK I have. I'm now extracting the 1.1 GB file onto my hard drive, at 640k/second. I'll probably get the notification before this thing finishes extracting.
  • Anyone beside me notice there is no option to switch to art in the development settings after updating to 4.4???
  • Piece of shit... Save yourself a couple of hours! What I had to do coming from Vanir Rom (Nexus 2012).... Update Wugs Toolkit
    Check USB debugging in developers options
    Change storage from MTP to PTP (under storage -> settings)
    Revert back to 4.3 JWR66V
    Update to 4.3 JWR66Y
    Check USB debugging