sAndroid 4.4

Updated with links to the OTA zip files for the Nexus 4 and Nexus 7 (2012/13) mobile data models. You can find them at the bottom of the article.

After hearing that Android 4.4  KitKat would be rolling out to the Nexus 10 and WiFi variants of the Nexus 7 (2012/2013), many of us jumped to check to see if we’d receive the update. Unfortunately, Google tends to take its time updating devices and we could be in for a rather lengthy wait.

As Android enthusiasts, you know we couldn’t simply wait to try all of that KitKat, and luckily there’s a method to install Android 4.4 KitKat onto your device manually using ADB sideload. Here’s a step by step guide (with images!), to help you manually download and install Android 4.4 KitKat onto your Nexus tablet. (Wifi variants only).

Android Authority takes no responsibility for what may happen to your device. While this is a reasonably safe procedure, you continue at your own risk. This procedure is recommended to intermediate and advanced Android users.

  • A WiFi variant Nexus 7 (2012 or 2013) or Nexus 10 with drivers installed.
  • A microUSB cable
  • Windows PC/Linux/Mac
  • Running the latest variant of Android 4.3 with the build number “JSS15R” for the Nexus 7 (2013), “JWR66Y” for the Nexus 7 (2012) and Nexus 10. (must be running the stock ROM, not a custom one)
  • The latest version of the Android SDK (which can be found here).
  • Zip file containing the Android 4.4 file for your tablet. Click here for the file for the Nexus 7 (2012). Click here for the link for the Nexus 7 (2013). Click here for the Nexus 10 file. (All files are from Google servers and are completely safe)
  • Make sure that if you’re using a laptop it is connected to a power point or at the very least fully charged. Ensure your tablet is also fully charged.
  • Optional: Create a backup of your data before you begin.

This method will not clear data, and you shouldn’t lose any of your app data or settings.

1. Make sure you have a microUSB cable at hand, as well as a PC or Mac, and are running the latest Android 4.3 version. Also make sure that you’ve already downloaded the Android SDK, as well as the Android 4.4 update zip file for your respective device and have all of your drivers installed.


2. Go to Settings>About Phone>Click on build number seven times until the message “You are now a developer” appears. Exit from “About phone” and scroll down and find the “Developer Options” setting. Click on this and then enable USB debugging.


2 (b). Connect your tablet to your computer and a warning should pop up with the computers unique RSA number asking if you want to connect to the computer. Click “Always connect to computer” and accept. Then disconnect the USB cable from the computer. Now turn off your device.

3. Return to your computer and unzip the Android SDK that you should have already installed (if not return to the “what you need” section and make sure you’ve completed all of the steps before returning).

4. Find the zip file containing the Android 4.4 update and rename it to something easy like “Kitkat”. Then move the file to the Android SDK in the folder titled “Platform tools”. (This will make things easier when using the command prompt).

5. Return to your tablet and power it back on by holding Power and Volume down buttons at the same time (for the Nexus 10, hold down the Power and volume up and down buttons simultaneously). You will now be faced with the fastboot mode.


Fastboot Mode.

6. Click the volume up button until you see the words “Recovery mode”. Press the power button to accept. It will show the Google logo and then you’ll be greeted by an Android with an exclamation mark and the words “no command written”. Use the micro USB to connect to your computer.


Recovery mode

7. Hold the home power button down first, then quickly hold the volume up button while still holding down the power button (this is a little difficult and you’ll need to work on your timing before getting it right). You will then see this:


8. Use the volume down button to go down to “apply update from ADB” and hit the power button to accept. You will then see this:


9. (Almost done!) Now return to your computer for the final steps. Open the folder containing the Android SDK and open the “platform-tools” folder. If you’re using Windows Vista/7/8, hold shift and then right click on any empty space. You’ll see the option “Open command window here”. If you’re using Linux or OSX or Windows XP open a command prompt and then navigate to “platform-tools”.


Windows 8 command prompt window.

10. In the command window type the following command “adb sideload Android KitKat”, without the quotation marks and substituting Android KitKat for whatever you named the zip file containing Android 4.4 for your device. Edit: Remember to add the extension “.zip” to the end of the file name for the zip file.

11. If you’ve done everything correctly, you can now sit back and watch your device install the update itself, if not head to the troubleshoot section to see some of the problems you could be facing.


12. One the update has been installed, you’ll see the counter hit 100% and you can now boot up your device. Voila! KitKat chocolaty goodness for your Nexus tablet!

Android 4.4 KitKat logo - aa

Remember that you will lose root by using this method. Also remember that the update does not bring the new Google launcher with “Ok Google” and swipe left for Google Now functionality.

  •  If your device isn’t being read try another USB port or perhaps another USB cable.
  • If it still isn’t being read, try uninstalling and reinstalling the drivers for your tablet.
  • If that doesn’t work try manually installing the drivers by following this link to download the universal drivers for your tablet. Unzip the downloaded folder, then simply open your device manager and manually install the update by right clicking on your device and click “update device” then in the pop up window “browse folders” and find the folder that you just unzipped and install the drivers.
  • If that doesn’t work, my final method is to use PdaNet. The program is normally used to tether your smartphone to your computer, however it also works very well helping you install the drivers for your device. Follow this link to install the program on your computer. You can always uninstall the program once you are done using it.
  • If you are stuck in a boot loop you may need to go back into recovery and clear cache and if that doesn’t work you’ll have to factory reset (loss of all data, so remember to back up folks!). Luckily these measures are very rarely necessary.

UPDATE: Here are the links for the rest of the Nexus devices eligible to get the Android 4.4 update.

Nexus 4:

Android 4.4 KRT16S from Android 4.3 JWR66Y 
Android 4.4 KRT16S from Android 4.4 KRT16O

Nexus 7 (2012) 3G:

Android 4.4 KRT16S from Android 4.3 JWR66Y

Android 4.4 KRT16S from Android 4.4 KRT16O

Nexus 7 (2013) 4G:

Android 4.4 KRT16S from Android 4.3 JLS36I

Just choose the correct zip file for your respective device and download it, and then continue with the instructions already provided. Just like the other links, this method won’t make you lose any data. Also, for those of you who were asking, this method differs from the factory images method as it doesn’t require you to have your bootloader unlocked, and it won’t lose any data. It’s also a little easier than the factory images method for the same reasons.

Have you used ADB sideload to push the Android 4.4 KitKat update to your Nexus tablet or are you waiting for the official OTA? What do you think of Android 4.4 KitKat?

Hat tip to James for the tip regarding going into fastboot mode on the Nexus 10!

  • Jefficko

    I have a problem, it’s saying varification failed.. Aborted. Why? I have stock 4.3.1. No root, no custom whatever..? :(

    • Yanksrock1000

      Yep me too…anybody know a way around this?

      • Cody

        I think the links are broken they files are not signed I downloaded it from a separate source and it worked

        • Adam Koueider

          Links are definitely not broken. Did it with these links and it worked. Not sure what’s happening. Which device are you using?

    • Adam Koueider

      Android 4.3.1? The WiFi versions of the Nexus 7 (2012/2013) both only have updates up to Android 4.3. The only device to receive an Android 4.3.1 update was the LTE variant of the Nexus 7. Unfortunately, this guide won’t work on the LTE Nexus 7 (2013) or the 3G Nexus 7 (2012).

  • Thisisme

    Can’t I just download the update and manually flash it on recovery (not using adb sideload) ?

    • Lee Pinkston

      Yes that’s what I did last night

  • Mystery Man

    Why haven’t you upgraded to Windows 8.1?

    • Matthew Ponce de Leon

      My laptop is incompatible with Windows 8.1. It has VGA issues.

    • Adam Koueider

      It’s not my PC (I use a Chromebook) I borrowed it off a friend and I have no idea why he hasn’t upgraded to 8.1.

  • Ben Gareffa

    adb command not found?

    • NotTheDroidYoureLookingFor

      you’re in a directory that does not contain the adb. if you’re in the platform-tools folders try ./adb sideload

      • dylan

        -bash: ./adb: No such file or directory

        • Formulake

          no Dylan there’s no such directory if you haven’t downloaded the platform-tools after installing the SDK. The ADT bundle has platform-tools and you’ll find adb.exe in there.

          • Landon Tetreault

            also make sure you cd into the correct folder

    • Jeff Edsell

      This fixed “adb not found” for me:

      Unfortunately verification fails on the file when I send it over.

      • Adam Koueider

        Which device are you using?

        • Jeff Edsell

          Nexus 7 2012, but I noticed my build JWR66V rather than JWR66Y. I don’t know how to deal with that.

          • Adam Koueider

            That’s probably the reason. You should’ve received that (JWR66Y) update a long time ago. Out of ideas, sorry. Best to wait for OTA for this.

    • drewb

      I had the same prob found out you need to type, ./adb sideload

    • Kenny J. Kang

      Find and run “SDK Manager.exe” in android-sdk-windows folder you unzipped. Unselect everything except “Android SK Platform-tools.

      Now you have Platform-tools folder. Follow the instructions from above from now starting from Step 9.

  • Albus

    the padnet works quite well!!! google usb driver sucks!

  • Daniel

    7. home button?

    • vitor francisco

      I also don´t understand this point. Should be volume button down first?????

      • Adam Koueider

        Power button, not home button. Sorry for the brain fade. Updated!

    • Adam Koueider

      Major D’oh moment on my part! Brain fade I guess. As other commentors have said it’s the power button. Sorry for the error will update!

      • Daniel

        No problem! :) got it running, thanks Adam!

  • Daniel

    When typed into cmd, nothing happens to the tablet.

  • RNB

    How do i install the driver?

    • Adam Koueider

      Which driver?

  • Guest

    it didnt do anything for me

  • Mattattackk101

    you guys should make a simple video on how to do this

  • Viktor

    I tried everything for the error: device not found problem and the pdanet method worked.. Excellent!

    • PerezGomez

      Where is tha pdanet method???

      • james grigg Follow the instructions given and it should install the correct drivers :)

  • Pedro Montes

    im stuck at the home button part….. btw home button??
    ….. help i guess….

    • Jason

      Yeah, I am with you. What home button?!

      • Adam Koueider

        See above^^

    • Jason

      It is power and volume up. Just press them both together. Don’t hold anything down.

      • Pedro Montes

        thanks u so much

    • Adam Koueider

      Major D’oh moment on my part! Brain fade I guess. As other commentors have said it’s the power button. Sorry for the error will update!

  • Omar

    home is actually the power button. Then you have to watch if you have windows 8. it does not want to use the adb driver. You have to after you plug in the tablet when in recovery goto your devices and update driver…. select manually then select one that is already installed. Android should be on top of that list then say yes windows I know what I am doing. Next continue with the adb sideload.

    Good Luck

    • Adam Koueider

      Windows 8 is super annoying with the ADB driver. Took me ages to figure that one out. That method you listed didn’t work for me, so I just used PDAnet and it worked. I recommend that method when all other methods have been exhausted.

      • Ben Kema

        Thanks for all your help Adam…can u please explain how to do this using pdanet??

  • Ram

    I’m getting all the steps down but when i finally get to the command prompt part, and type it in , it says “Android Debug Bridge version 1.0.31” and then a lot of stuff comes up and suddenly stops coming up and nothing has happened. No reaction from the nexus 7. Please help. Im lost here.

    • RNB

      Me to

    • Chris

      same here, did everything correctly and even updated drivers with the google ones and it still does not push via adb. just a bunch of cmd jargon and no response from tablet….this update sucks!

      • Adam Koueider

        See my response to original commentor’s comment.

        • vitor francisco

          sorry to bother again, but I also get a bunch of cmd jargon. When i put adb devices it recognizes the device, but then adb sideload only gives what is in the pic. what should I do now? thanks!

      • Formulake

        1. Did you place the in the same folder as adb.exe (platform-tools) 2. Have you checked the Device Manager to see if you have Android ADB Interface under Android Phone 3. (After confirming the previous 2 points) Run adb kill-server, then run adb start-server, the run adb devices. You should see your attached device. If not, try another USB cable and another USB port. Things should proceed smoothly from here.

        UPDATE: Also, if you only downloaded the SDK installer, you still need to install the platform-tools once the SDK tool opens. Your best bet is to download the complete ADT bundle and uncompress it before going ahead with the update. I don’t know how familiar you are with these terms and tools but if you’re a newbie then don’t fret too much. This stuff boggled me the first time too. It’s actually quite simple if you just follow the instructions that many other like Adam have put out there, to help people like us get by in a very coded world. All the best.

    • Andy

      I was getting the same thing, here’s what worked…. In the instructions under step 10 where it says “In the command window type the following command “adb sideload Android KitKat”, without the quotation marks and substituting Android KitKat for whatever you named the zip file containing Android 4.4 for your device” you need to add the .zip extension to the filename. Running Win7 Pro, worked for me.

    • Adam Koueider

      As Andy said remember to add the .zip extension. What I’d like you to do is open a new command prompt (ensure your device is in recovery mode) and then type in the following command “adb devices”. If a serial number comes up it means the computer is reading your device if it leaves it blank then it means your computer isn’t reading your device in recovery mode (usually happens in Windows 8).

      For this I recommend you to go to the troubleshooting section of the article and follow one of the three methods I left to ensuring that both your Nexus 7 and ADB drivers are installed correctly. Hope this helps!

    • Adam Koueider

      As Andy said remember to add the .zip extension. What I’d like you to do is open a new command prompt (ensure your device is in recovery mode) and then type in the following command “adb devices”. If a serial number comes up it means the computer is reading your device if it leaves it blank then it means your computer isn’t reading your device in recovery mode (usually happens in Windows 8).

      For this I recommend you to go to the troubleshooting section of the article and follow one of the three methods I left to ensuring that both your Nexus 7 and ADB drivers are installed correctly. Hope this helps!

  • Jackrabbit916

    I just got done doing the update. I had some problems getting the drive for my device installed, but the suggestion to use PdaNet did the trick for me. I now have all the goodness of Kit Kat. Now I am going to try and install the launch and see how it goes. Will update to let you guys know how it went for me.

  • Iacobus

    I actually skipped Fastboot mode in step 5 and went straight to Recovery mode by holding power + volume up.

    Also, users (like here) are reporting they cannot get beyond using “ADB sideload” when using their Nexi in Recovery mode with ADB in Windows. (Something about hardware IDs switching or something while the Nexus goes into Recovery mode; I’m not a huge propellerhead on this matter.)

    This is rectified by modifying the “android_winusb.inf” file to reflect the hardware driver ID. An example of this is posted at:

    Make sure you modify the right block. ([Google.NTx86] if your’e on a 32-bit system; [Google.NTamd64] if you’re on a 64-bit system.) Save it and then try to install the driver again when Windows asks you to.

    • zeb

      Thanks! Got it working with my Nexus 4. ADB sideload wasn’t recognized at first, but with that hack it worked. Great.
      Well.. now on to the next problem. E: signature verification failed.

      • zeb

        Got it working using the scripts that was bundled with the zip-file. Just executed flash-all.bat, with the phone in recovery mode.

  • Formulake

    Thanks Adam. Just managed to flash my device using adb and by following your guide meticulously. I’ve now got 4.4 running on my nexus 7 (2013). Just an update though, the whole transparent notification bar thing doesn’t happen by default. Don’t know if it needs to be enabled somewhere so it pretty much looks like 4.3 but I’m looking forward to all the other optimised sweetness that 4.4 is supposed to bring with it. Appreciation goes out to you once again for the great instruction set.

    • Adam Koueider

      Currently the transparent notification bar is a Nexus 5 only feature :( however, you can install Nova launcher beta and then get a transparent home/notification bar.

      • Formulake

        Thanks for the tip, Adam. I think I’m going to stay loyal to the plain vanilla Android experience though. I’m a sucker for simplicity and there’s nothing simpler. On my non-Google devices, though I’ve got Nova Launcher Prime running but that’s only because none of them perform like a Nexus device and I don’t mind mucking around with them. My Nexus 5 arrives in 2 weeks and it’s unlikely that I’ll be using Nova on that either.

        • Adam Koueider

          Yep, found that to be the truth as well. I don’t quite know why, but the GEL seems to enable the feature. It’s as if the feature is there, but Google was too lazy to enable it. Wierd. Only problem with the GEL is that the search bar will overlap with the first row of icons in horizontal mode on the home screen. Other than that, works like a charm!

          • Formulake

            Oh! How right you are! That’s really strange. I hardly ever use the homescreen in landscape mode so this major detail skipped my attention entirely. Fortunately, I use the DashClock widget for the homescreen so it only overlays on the top end of the time widget. Still…it’s bloody ugly isn’t it?

          • Adam Koueider

            Well technically it isn’t made for the Nexus 7 yet, so I can sort of understand. However, Google did resolve a few issues (voice search force close, keyboard popping up for tablets) in the latest Search update. Hoping the next one resolves all of the problems.

          • Formulake

            Here’s my million dollar question and I suppose the best answer would be to wait and watch but….now that I’ve updated to 4.4, when Google officially releases the update for the Nexus 7 will I be able to use the OTA update or do you suppose it will show me that I’m already “Up to Date”? Don’t bother to answer if my question is too much of a shot in the dark.

          • Adam Koueider

            Wait, do you want to receive the same update you just manually installed? Or do you wish to continue receiving updates in the future (for e.g. Android 4.4.1)? If the former, the answer is no, if it’s the latter the answer is yes. You can still update OTA.

          • Formulake

            Well, no, receiving the same update would just be silly wouldn’t it :) I was kinda hoping that Google would push the OTA once they’ve looked into these little problems with the update but so long as it happens somewhere down the line (which it will, I’m sure) that’s all I need.

          • Adam Koueider

            Are you referring to the issues with the Google Experience Launcher? That would come as an update to the regular Google Search application via Play Store or an APK. This is because the Google Launcher is actually a part of the Search app. Unless you were referring to issues with the actual update (P.S. If you’re having issues with Android 4.4 could you expand upon them)?

          • Formulake

            No, you’re absolutely right. I’m referring to the GEL issues. So far 4.4 makes project butter look like project quicksand. It runs like a dream. The battery optimisations are pretty mind-blowing and I know that most people look for gimicky add-ons but the OS itself leaves very little wanting. I’m especially in love with the RAM optimisation at this point. Looks like they’ve managed to cut back on as much as 18-20% of the original requirement based on my 4.3 – 4.4 transition.

  • Brent

    Overall good instructions. For step #7 (at least on the 2013 Nexus 7), you hold down the power button and then PRESS the volume up button (but don’t hold it down). When I did step #10, the command prompt window came up with an error message something like “no device found” and I finally ran installed the PdaNet program as suggested in the Troubleshoot section above, and then it all worked.


  • Randall Combs

    Step by step this is NOT working. I get to the point to sideload the file the command promt say “cannot read AndroidKitkat” what am I doing wrong. Drivers check, SDK check and extracted, 4.4 placed within the correct file. I literally followed the direction verbatim. Help.

    • Adam Koueider

      Okay, remember to add the file extension “.zip” to the end of the file name in command prompt. Tell me what happens after that. Hope this helps!

      • Randall Combs

        My mistake. I named the file “” thus when in the command prompt it did recognize the file. I renamed it “AndroidKitkat” then in command prompt it typedtyped “adb sideload “” it appears to be working now… But slowly.

  • Ar

    e:signature verification failed

    • Adam Koueider

      Which device are you installing it on?

      • zeb

        got the same error, on Nexus 4.

        • Adam Koueider

          This update method only works for the Nexus 7 WiFi and the Nexus 10. Sorry!

          • zeb

            Got it working using the scripts that was bundled with the zip-file.
            Just executed flash-all.bat, with the phone in recovery mode.

            Now running Kitkat on N4. :)

          • Adam Koueider

            Really? Which Zip did you download? Notice anything wrong?

          • zeb

            Downloaded the zip for Nexus 4 from Unzipped it in the same folder as the adb.exe and fastboot.exe. Executed the flash-all.bat. Phone in recovery mode. Easy.

          • Adam Koueider

            Ah ok. Thought you were using the Nexus 7 zip. I’m guessing you already had an unlocked bootloader?

          • zeb

            Yes. Already unlocked.

          • HQ

            I use the adb sideload method and using the flashall.bat, but both of them not working.
            Using the flashall.bat, it say bootloader version not same.
            Using adb sideload, it say signature verification failed.
            Can anyone help?

          • Ar

            I tried with flashall.bat and got 4.4 But I hope there are no bugs.. Last I did it for 4.3 my battery began draining like heck and I had to do antoher factory install (I gave it to the LG guys who did it for me) to correct the problem.

      • re

        nexus 4

        • Adam Koueider

          Read the rest of the comments in this thread. This guide is for the Nexus 7, Nexus 10 WiFi variants.

          However, if you’ve got a Nexus 4, and an unlocked bootloader (and you’re up to the part where you need to use adb sideload), you can simply download the factory images from Google and while in Recovery mode, execute “flash.all.bat” (for Windows) in the Command Prompt. That should work!

          • Vaibhav Sawant

            Not Working showing this error message

  • Phuc Duy

    Does I lost my apps and data when install this factory image?

    • Adam Koueider

      Using this method and the links provided you should not lose any data.

    • Formulake

      I can confirm that I did not lose any of my settings, data or apps while updating to 4.4. Proceed without fear.


    Holy crap I finally did it. Those USB drivers had me stuck.

  • Jonathan Fletcher

    adb not recognized

    • Adam Koueider

      What device are you using? Try the troubleshooting methods listed above.

      • Jonathan Fletcher

        Nexus 7 2013 wifi

        • Adam Koueider

          Did you try the troubleshooting methods?

          What I’d like you to do is open a new command prompt (ensure your device is in recovery mode) and then type in the following command “adb devices”. If a serial number comes up it means the computer is reading your device if it leaves it blank then it means your computer isn’t reading your device in recovery mode (usually happens in Windows 8).

          For this I recommend you to go to the troubleshooting section of the article and follow one of the three methods I left to ensure that both your Nexus 7 and ADB drivers are installed correctly. Hope this helps!

          • Jonathan Fletcher

            I think it could be a driver problem, I’m using Vista ultimate and it just won’t recognise the drivers i’ve downloaded

          • Adam Koueider

            Yup, in this case, I’ve found the PDAnet method the best way to go.

          • Jonathan Fletcher

            installed pdnanet and tried the adb devices command, it recognised the device in recovery mode but not when you “apply update”

    • Adam Koueider

      Okay, I think I know your problem. Rename the “” as just “Kitkat” then type in “adb sideload”. You forgot the zip extension. Let me know how that helps.

      • Tom

        Thanks man. the “.zip” in the file name was the problem

  • Dave Christian

    Great article, thanks! The troubleshooting section was particularly handy; my Nexus 7 (2012, Wifi) would connect to ADB while operating normally but when in recovery mode Windows (7, x64) couldn’t see the device. I installed the PdaNet driver and it all worked. Going to have a play with my freshly KitKat-ed N7 now…

  • Varun Kumar

    Got “Device Not Found” problem while executing this code :
    adb sideload Android

    but fixed it using daNet

    also i tell u don’t rename the zip file as “Android”….instead use a single word name like “”

    • Rudraksh D. Majumdar

      how did you fix the “device not found” problem? Please share.

      • Varun Kumar

        i have a Nexus 7 2013

        install this software on your pc []

        check once if this connects your device with pc via this software…if it is a success…

        continue with the given steps…

  • dano

    do you know if this will work with other android tablets?

    • Adam Koueider

      Nope, only Nexus tablets I’m afraid.

  • Harshit Khanna

    Thank you AA, I now have the 4.4 KitKat Update :D

  • Thank you — very useful. You’d do well to change the instructions so people aren’t renaming the file to a name with a space in it though.

  • EU

    I know that I`m off topic but still I wonder how much money did Google received from Nestle(Kit Kat) for associating this version of android with Kit Kat.

    • Adam Koueider

      None. no money changed hands for this deal.

  • Arsene Teo

    my N7(2012) doesn’t have ART mode…WHY!!!….

  • Harsh Patel

    if i am installing it ,
    the data on my internal memory is wiped out or the data has to be backed up

  • Juan Carlos Cañón Mercado

    “Make sure that if you’re using a laptop it is connected to a POWERPOINT or at the very least fully charged. Ensure your tablet is also fully charged” :) :) :) Until now I don’t even know POWERPOINT was necessary to flash android!

  • JTH

    Painless update, clear instructions, everything went as planned. Nexus 7 2013. Thanks, Jeff

  • Nate

    I’m stuck at “Android is Upgrading… Finishing boot.”

  • alex

    error: device not found I have the adb driver installed, also all the sdk tools

  • Fred

    I have done everything, however the KitKat boot animation is stuck, and has been playing over and over again for around half an hour. Anyone have any suggestions? Help appreciated.

    • Adam Koueider

      Look at the troubleshooting section.

  • Zach Poucher

    I keep getting this and where it says the adb sideload Android is what i put in. The file is in the platform-tools folder and i have connected my device after using PdaNet. Still is not working, please help me! Oh and sorry for it being so long… =


    6_64-20131030sdkplatform-tools>adb sideload Android

    Android Debug Bridge version 1.0.31

    -a – directs adb to listen on all interfaces for a c


    -d – directs command to the only connected USB devic


    returns an error if more than one USB device is


    -e – directs command to the only running emulator.

    returns an error if more than one emulator is r


    -s – directs command to the device or emulator with

    the given

    serial number or qualifier. Overrides ANDROID_S


    environment variable.

    -p – simple product name like ‘sooner’, or

    a relative/absolute path to a product

    out directory like ‘out/target/product/sooner’.

    If -p is not specified, the ANDROID_PRODUCT_OUT

    environment variable is used, which must

    be an absolute path.

    -H – Name of adb server host (default: localhost)

    -P – Port of adb server (default: 5037)

    devices [-l] – list all connected devices

    (‘-l’ will also list device qualifiers)

    connect [:] – connect to a device via TCP/IP

    Port 5555 is used by default if no port number

    is specified.

    disconnect [[:]] – disconnect from a TCP/IP device.

    Port 5555 is used by default if no port number

    is specified.

    Using this command with no additional arguments

    will disconnect from all connected TCP/IP devic


    device commands:

    adb push – copy file/dir to device

    adb pull [] – copy file/dir from device

    adb sync [ ] – copy host->device only if changed

    (-l means list but don’t copy)

    (see ‘adb help all’)

    adb shell – run remote shell interactively

    adb shell – run remote shell command

    adb emu – run emulator console command

    adb logcat [ ] – View device log

    adb forward –list – list all forward socket connections.

    the format is a list of lines with the followin

    g format:

    ” ” ” ” “n”

    adb forward – forward socket connections

    forward specs are one of:






    jdwp: (remote only)

    adb forward –no-rebind

    – same as ‘adb forward ‘ but fail


    if is already forwarded

    adb forward –remove – remove a specific forward socket connection

    adb forward –remove-all – remove all forward socket connections

    adb jdwp – list PIDs of processes hosting a JDWP transport

    adb install [-l] [-r] [-s] [–algo –key —

    iv ]

    – push this package file to the device and instal

    l it

    (‘-l’ means forward-lock the app)

    (‘-r’ means reinstall the app, keeping its data


    (‘-s’ means install on SD card instead of inter

    nal storage)

    (‘–algo’, ‘–key’, and ‘–iv’ mean the file is

    encrypted already)

    adb uninstall [-k] – remove this app package from the device

    (‘-k’ means keep the data and cache directories


    adb bugreport – return all information from the device

    that should be included in a bug report.

    adb backup [-f ] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]

    [-system|-nosystem] []

    – write an archive of the device’s data to


    If no -f option is supplied then the data is wr


    to “backup.ab” in the current directory.

    (-apk|-noapk enable/disable backup of the .apks


    in the archive; the default is noapk.)

    (-obb|-noobb enable/disable backup of any insta

    lled apk expansion

    (aka .obb) files associated with each applic

    ation; the default

    is noobb.)

    (-shared|-noshared enable/disable backup of the


    shared storage / SD card contents; the defau

    lt is noshared.)

    (-all means to back up all installed applicatio


    (-system|-nosystem toggles whether -all automat

    ically includes

    system applications; the default is to inclu

    de system apps)

    ( is the list of applications to b

    e backed up. If

    the -all or -shared flags are passed, then t

    he package

    list is optional. Applications explicitly g

    iven on the

    command line will be included even if -nosys

    tem would

    ordinarily cause them to be omitted.)

    adb restore – restore device contents from the backup


    adb help – show this help message

    adb version – show version num


    adb wait-for-device – block until device is online

    adb start-server – ensure that there is a server running

    adb kill-server – kill the server if it is running

    adb get-state – prints: offline | bootloader | device

    adb get-serialno – prints:

    adb get-devpath – prints:

    adb status-window – continuously print device status for a specifie

    d device

    adb remount – remounts the /system partition on the device re


    adb reboot [bootloader|recovery] – reboots the device, optionally into the boo

    tloader or recovery program

    adb reboot-bootloader – reboots the device into the bootloader

    adb root – restarts the adbd daemon with root permissions

    adb usb – restarts the adbd daemon listening on USB

    adb tcpip – restarts the adbd daemon listening on TCP on th

    e specified port


    adb ppp [parameters] – Run PPP over USB.

    Note: you should not automatically start a PPP connection.

    refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1

    [parameters] – Eg. defaultroute debug dump local notty usepeerdns

    adb sync notes: adb sync [ ]

    can be interpreted in several ways:

    – If is not specified, both /system and /data partitions will be u


    – If it is “system” or “data”, only the corresponding partition

    is updated.

    environmental variables:

    ADB_TRACE – Print debug information. A comma separated list

    of the following values

    1 or all, adb, sockets, packets, rwx, usb, sync

    , sysdeps, transport, jdwp

    ANDROID_SERIAL – The serial number to connect to. -s takes prior

    ity over this if given.

    ANDROID_LOG_TAGS – When used with the logcat option, only these de

    bug tags are printed.



    • Adam Koueider

      I got this error once. Best method of attack was to uninstall and reinstall drivers and if that’s not the case then you’ve typed it in wrong. Can you tell me the command that you typed in?

      • Zach Poucher

        I put in: “adb sideload Android” If I try it without the .zip which would then just be the name of the file that i extracted and changed the name it does the same thing. Any ideas what I’m doing wrong?

        • Adam Koueider

          What did you name the original folder? Rename it simply “Kitkat” (NO ZIP EXTENSION NAME) and then when you type in the command add the zip extension at the end so that would be “”

          • Zach Poucher

            I named it “Android KitKat” and when I put it in I added the .zip

          • Adam Koueider

            Try it the way I previously said if it sill is not working here’s anotheranother troubleshoot method. In the command prompt type in adb devices (while ur device is plugged into your computer and in recovery mode). If it shows up some sort of serial number then it’s connected, if not try uninstalling and reinstalling the drivers. Remember to try the method I said before trying this one.

          • Zach Poucher

            Should I still put it into the thing to update from adb?

          • Zach Poucher

            Now it says it cannot read I checked and it picks up my device but it wont install. Now what?

          • Adam Koueider

            Glad I could help.

  • Cody Rush

    Every time I get to sending the .zip with side load it would just repeat the adb commands… But when i put the command adb devices it shows up… Makes no sense…I tried on both my Mac and my windows… I’m going crazy, any advice

  • anmolm97

    The link you provided gives a 185MB file to download for my Nexus 7 2012, however this official link gibes a 385MB download(…which one should I download?

    PS: Im new to all this flashing/fastboot/adb stuff

    • Adam Koueider

      Page not found error.

      • anmolm97

        sorry, here’s the correct one

        • Adam Koueider

          Your analyzation is correct. The link you gave is a factory image, which most people use to install a fresh boot after messing around with custom ROMs, that means it requires more files and is larger as people might not necessarily be running stock Android already.

          I linked the OTA update, meaning people are already running stock Android and it can be smaller.

          The second question is a little difficult to answer. Nexus devices don’t have locked bootloaders like in the original sense like carrier devices. My recommendation is that unlocking bootloader and rooting doesn’t void warranty, unless you go brick it while flashing a custom ROM or something. And my recommendation is that if you ever need to send it back just return to stock and relock your bootloader just in case. But generally, neither rooting or unlocking bootloader void warranty related to hardware faults on Nexus devices.

          • anmolm97

            Where do i get the drivers after booting in recovery mode?

          • Adam Koueider

            In my experience, the PDAnet method (in troubleshoot section) worked best.

          • anmolm97

            I also have one last question. In what steps are the following supposed to be done? Rooting,Unlocking the Bootloader, Flashing another recovery eg TWRP Recovery?

          • Adam Koueider

            Ok, so first things first make a backup of your device and the data. Then unlock bootloader, then root, then you can flash whatever custom ROM you’d like. My recommendation for Nexus devices is to use the WugFresh Toolkit. Works really well. Also if you’re installing CyanogenMod, there’s the new Cyanogen Installer which helps beginners install Cyanogenmod.

          • anmolm97

            What application would you recommend to backup? And which ROM do you find the best? Also I’m inclined towards the AOKP ROM. Thanks once again.

          • anmolm97

            Which backup application would you recommend? and which is the best ROM according to you? I like AOKP atleast in the videos i have seen.

          • anmolm97

            Done man!! Thanks a ton!! :D and great guide by the way..

  • tesst24

    I dont have that – “Recovery mode”. Press the power button to accept. It will show the Google logo and then you’ll be greeted by an Android with an exclamation mark ” My nexus 7 shows up teamwin menu, this tutorial is shit, not enough explained everything..

    • randomdudexxx

      This is for stock recovery users. You have custom twrp recovery. There probably is an adb sideload option in twrp, you just have to use your brain and find it.

  • tesst24

    google is SHIT, why they don’t allow to update to new kitkat update ? it was releases in 2 weeks ago …

  • Victor Neves

    Finally successfully installed! Tip 1: be sure the drives are ok when connect and after activate USB debugging (different driver). Tip 2: install the correct java (32 or 64 bits) before running Android SDK.

  • Richard Giordano

    how do u fix the error device not found? btw using a nexus 7 2012 with the latest version of android 4.3

    • rhymiZ

      For those that have that receive device not found with ADB trying to sideload the update, I’ve found a fix for that. (Windows 8, I don’t know if this works on Windows 7, but try it and let me know.)

      Steps: Install the drivers that come with your SDK or download them here:

      Get your device ready to receive update from ADB, then right click on “Computer”, Select Properties then device manager.

      You should see your Nexus show up with a triangle, indicating that drivers have not been installed. Right click on Nexus 7 or which ever Nexus you have, click properties, select update driver, browse my computer for driver software, then click on let me pick from a list…, a Window will pop up with where you can select your device type, select ADB Interface, then click next, you’ll be taken to a screen where you can select a Model, click on ADB Interface (or ADB Testing Interface), click next, you’ll get a warning message from Windows, click yes anyway and your driver will be installed.

      Test it by opening a shell and typing “adb get-serialno”, you should see your Nexus’ serial number.

      Then proceed to sideload your update, enjoy!

      Lemuel Boyce
      Twitter: @rhymiz

      • pauliex

        Thank you! This worked perfectly.

        • anonymoushand

          adb interface not an option for me?

          • rhymiZ

            If you installed the drivers before you turned your tablet/phone off and tested if you could see your device with/in ADB running the “adb-get-serialno” command, you should get that option when you try to update the drivers manually, if you follow the above steps.

      • JB

        Thanks This worked for me too!

      • G

        splendid mate… been breaking my head since morning for a slution… this one did it on my Win XP. am at sending my at 75%:)


  • Jesus

    I keep getting a *cannot read ‘’ any ideas?

    • Mike

      anyone have ideas on this one? I am getting “cannot read” no matter what I rename it and after many downloads from different sources (but it’s the same file).

  • Chuck

    When I type in the command prompt “adb sideload KitKat”, I get the response *cannot read ‘KitKat’*

    • Mike

      yes, same here… I’ve tried downloading the file many times now and have renamed the file and still get “cannot read.” help?

  • Ralu Lulu

    help!!! the error message displays “cannot read KitKat” .. why????

  • Ralu Lulu

    help! the error message i have displayed is “cannot read Kitkat”..why??

  • Edwin

    says Cannot read **
    any help?

    • Smatthew

      make sure you’re not using winRAR .. if that’s the case the filename will be .tgz. Right click the android update’s compressed file, go to properties and check under”Type of File” what the .xxx filename is. hope this heps.

  • Codfather

    Just a quick note for Linux desktop users, if you get the following error while running the adb command , you need to run it as a Root user.

    error: insufficient permissions for device

    Once you see this message you need to kill the adb server daemon that is now running, using the ‘kill’ command – you can find the process with ‘ps -ef | grep adb’

    Run the command again as root, and all will be well, and you will get kitkat on your nexus 7.

    Thanks for the write up, apart from this one point

    • SB

      How do I “kill” this daemon?

      • SB

        Never mind got it.

  • ronmate

    how to solve “device not found”?

  • SB

    Finally succeeded after multiple fail to verify errors. Skip the rename to “Kitkat” step and go with the real file name. That worked first time. Just copy/pate into terminal.

  • BJaq

    I used this method instead:

    The methods listed here just didn’t work for me but this recovery/factory thing did wonders. After having “bricked” my phone, I recovered it last night. Got to thinking that maybe I can recover my phone to KitKat today :3

    Try it out. It will save you time and frustration :)

    Mac users, use Keka 7zip.

  • mjrfitz

    To confusing

  • john

    will I still receive OTA updates in future if I do this?

    • Adam Koueider


  • rudy

    Is adb necessary? Can you update it without this? In previous os versions, I just download to my phone/tablet, go to recovery mode then flash it.

  • jala

    Followed the steps carefully and slided Kitkat. But it booted up with some error. Then I did a reboot and now it stacked at booting up. I reslided, same thing. Basically it is bricked.
    Is there any way to fix it?


    • jala

      I did a factory restore and wiped out data. Luckily, Kitkat started and seems everything is working now, except I lost everything, which is ok for me as I only use this to read news.

  • Rudraksh D. Majumdar

    error: device not found

    I have already updated the drivers before trying this. Tried two different USB cables. What could be the problem?

  • Anupam

    Will this void the remaining warranty of the tab?

  • Angelo Antonio Costa

    Does anyone know when KitKat will be fully made available through the conventional system update? I’ve been having trouble with this manual installation.

  • Anupam

    is there any update file for nexus 7 2013 mobile version?

    • Adam Koueider

      Just added the links! Enjoy!

  • Adrian Siwy

    Will I be able to use this method on my nexus 4 with the n4 stock image.

    • Adam Koueider

      Just added the link, enjoy!

  • jag

    I am getting error message saying..unable to read KitKat..any help

  • Bex Foster

    It’s a shame that you’re not near the top of the search results for this. This would have saved me several hours of headacheness :|. I just got the newsletter in my email, trust me, no other site is as comprehensive as you guys! Great work!

  • Alexander

    Can you still receive OTA updates in the future after doing this?

    • Brian


  • Sejjady

    I got “* cannot read *”

    • johnnycizzle

      i also recieved this

    • That guy

      Got same thing. OS already recognizes .zip extension. Use “”

    • Brian

      the factory image downloaded was not a zip file! its a .TGZ so you need to use this extension…

  • Syed Ahsan

    i’ve got nexus 7 2012 running on build no. JWR66Y, its rooted and CWM recovery installed, i selected “install zip from sideload” in CWM and then sent the update file from command prompt using “adb sideload kitkat.tgz” (as the file i downloaded was in tgz format instead of zip), the problem is that the command prompt is sending the file to my tablet but the tablet doesn’t read it or whatever, it gets stuck at “send the package u want to apply to the device with adb sideload “, what should i do ?

  • Azee Essack

    can it work on Nexus 4

    • Adam Koueider

      Just added the links for the Nexus 4. Enjoy!

  • chuckr01

    Your instructions were the best I found on several posts, very clear step-by-step. Thanks.
    A couple of notes, I am running 8.1 and extracting the SDK download took an unbelievable amount of time. I finally got it done more than once and sometimes the pop-up to get into command mode worked, others didn’t. When it did I got the device not found error. I finally copied the platform-tools folder to my desktop and extracted it from there. That took no time at all. I still got device not found and then went to the PdaNet cure and success!
    Thanks for the clear step-by-step, my extra steps were probably due to inexperience, this is the first time I’ve tried something like this.

  • tom west

    I could never get this “Connect your tablet to your computer and a warning should pop up with the computers unique RSA number asking if you want to connect to the computer. Click “Always connect to computer” and accept. ”

    to work …..

  • Dean

    Does this void the warrenty?

  • Deven Bender

    cannot read…anybody know why?

    • Brian

      its not really a zip file…. when in CMD just start typing OCCAM then press tab to complete the file name. its a .TGZ extension.

  • Micky Rastogi

    i am having a problem with USB drivers….1) my windows cant find drivers online 2) i tried installing manually but still it says could not find….even i am specifying the path of the driver…but still it says couldn’t find! What to do ??????

  • Android User

    Would I be able to use this if I no longer have a previos version of an Android OS on my N7 (2012)…as of right now it only boots to the Google screen and I can get it to the CWM Recovery (version screen.

  • jonnyqwest30

    is the Nexus 4 ADB file for update out yet?

    • Adam Koueider

      Just added it!

  • Cojo

    What do you mean by “Remember that you will lose root by using this method. Also remember
    that the update does not bring the new Google launcher with “Ok Google”
    and swipe left for Google Now functionality.” This features does not come with this method or aren´t supported by device? If they should come how can I gain them ?

    • Adam Koueider

      Google is keeping the Nexus 5’s new launcher strictly to the Nexus 5 at least for now. However, you can always grab the pulled APKs and install them. It works pretty well, only one issue with landscape mode. Here’s the link: Remember to install the new search update, if you haven’t recieved it yet (different to the one in the article as it has since been updated)

  • Brian

    Why there is no OTA update came? Had to manually update it.. Is this a legit Kitkat update?

    • Brian

      yes its legit because you download the factory image from google!

  • Ryan

    To those with the CANNOT READ ‘xxxxx.ZIP’ issue –

    I was able to successfully install by typing the full path after the adb sideload command (Note this is for Mac OSX Terminal):

    /Users/ryan/Desktop/ADT/sdk/platform-tools/adb sideload /Users/ryan/Desktop/ADT/sdk/platform-tools/

    (all in one line / command)

    Hope this helps anyone else having the same trouble…

  • Milton

    do you lose root?

    • mackjao

      yep, it’s mentioned in article


    kana punda hw to instal in xperia ZR……???????

    • senthil.s

      +91 9944205021

  • rmblog

    thanks guys for the tutorial KK 4.4 is the biz

  • Scott in MA

    Everything is fine until Step 7. I have tried holding the down power up, the power down and up and the down power and up. Nothing is getting me to the screen in 7. Any ideas?

  • Daniel Bobke

    Worked flawlessly! One oddity – after I did the reboot after the load was done, it went through the standard apps check and contact database update. When the OS loaded and the interface came up, it said that the OTA update was available to install and had been downloaded! I checked the “About Tablet” section and it did say 4.4, but I did not check the build. I applied the OTA update just to be thorough. Is anyone else seeing this? Did Google push and update to their update?

    • Adam Koueider

      Yup, this was another update for the bug fixes. It went from KRT160 to KRT16S. Just minor bug fixes.

  • Lorand

    I got all steps done but when I do the adb sideloat, on the command command prompt and press enter, a bunch of text fills down the page but it doesn’t install anything to my nexus 7 2013 wifi. So then I tried unplugging it and plugging it back in, but whenever I plug it back in and is powered off, in recovery mode, or the No Command screen, my device doesn’t connect to my computer. How do i fix this?

  • Bob

    Was having so much trouble with this for hours thanks to God damn Windows drivers. Tried plugging it into my macbook, ran ./adb and pressto, 2 minutes.

    I strongly urge if you have any OS X machine, do the smart thing and try it on that. Windows proving once again it’s a pile of crap to me.

  • Ben Davenport

    thanks AA went smooth really easy it only took about 15mins and after installation i got a system update with the new bug fixes awesome!

  • Volker Neumann

    In What You Need,
    “JWR66Y” for the Nexus 7 (2013)
    should be
    “JWR66Y” for the Nexus 7 (2012)

    • Adam Koueider

      Yup, sorry about that. Fixed!

  • Winston

    I’m having trouble doing this with my mac. Each time I try to do it it bashes me and just tells me it’s a directory and nothing happens.

  • Gabe

    Won’t work. On a mac. This is what I get.

    -bash: /Users/(got rid of my name)/Documents/adt-bundle-mac-x86_64-20131030/sdk/platform-tools: is a directory

  • Jay T

    set_metadata_recursive: some changes failed
    E: error in /tmp/
    (status 7)
    Installation aborted


    • I”ve got the same error. I think when you translate it, it means “You have to factory reset, neener neener neener.”

      And then PRAY that the factory reset unbricks the damn phone. It doesn’t always, from my research.

  • Roy

    Where can I get the 4.4 file for nexus 4?

    • Adam Koueider

      Just added the Nexus 4 and mobile data Nexus 7 links. Enjoy!

  • jeff

    Will wait for the official update!

  • Eli Shirk

    after typing the command prompt (adb sideload i get this:
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device not found

    Is this a driver issue? How do I uninstall and reinstall all necessary drivers for my Nexus 7 (2012 WIFI)?

  • Emilio Villegas

    This was a fucking pain in the ass but I made it. it turns out that I’m not a complete tool :P

  • Emilio Villegas

    is there anything like this for the nexus 4?

    • Adam Koueider

      Just added the Nexus 4 and 3G/4G Nexus 7 model links too!

      • Emilio Villegas

        Done that too thanks!

  • Eli Shirk

    I’m getting an ERROR. Here is what is shown on my phone:

    Now send the package you want to apply
    To the devise with “adb sideload ”…
    Finding update package…
    Opening update package…
    Verifying update package…
    Installing update…
    Verifying 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/
    (Status 7)
    Installation aborted.

    • Matthias von Wachter

      I’ve got exactly the same issue with my Nexus 4 after a failed OTA update to KitKat and later trying to fix it via this post.

      • Eli Shirk

        I used this guide to factory reset. The best part is that the toolkit already has the KitKat update so when you’re done you’ll have a fresh and clean install of KitKat. Skip to the “Restoring to Factory Stock with Toolkit” section. Kind of wish I would have just done this anyway because I had some other issues that I thought a factory reset might resolve and it did, and it didn’t take that long to set up my home screens and apps again.

        • Matthias von Wachter

          Thanks for the advice.
          I have tried to use fastboot to flash the nexus 4, but could not get into proper fastboot mode, so it didn’t work. Since the toolkit requires fastboot as well, I cannot imagine any different result.

    • Md. Atiar Rahman Chowdhury

      did you solve your problem ?

  • westy

    Great advice guys but still a real pain. Finally got it to load across to my Nexus 7 and then the verification failed. Enough is enough, I’ll sit on my hands for a while!!

  • admiralsaltybob

    I manually updated to KRT16O from JWR66Y using the above… as soon as I did, I received the over the air update from Google to KRT16S (only 1.5mb).

    • Adam Koueider

      Yup, it’s a minor bug fixes update. Nothing major difference that I’ve noticed.

  • Ben

    I’m getting a release key error (E:Error in /tmp/

    Before you ask my N7 (2012 wifi) is not rooted and i have not modified the zip in any way. For some reason it has the 4.3 release keys (but i am definitely running 4.3!).

    Is there any other option than trying a factory reset, re-update and then go again?

    • Ben

      Ok did the factory reset and updates. Still same problem.

  • mayu11.91

    in this manual update all data and apps are delete or keep as it is?

  • Rodrigo Alves de Brito

    Amazing! Just did it here and everything worked. The only issue was the USB drivers; I installed them and the PC recognised them with the phone on, but when I turned it off (with debug activated) and started bootloader, the PC simply did not recognise it anymore. Then I installed PdaNet and the drivers issue was solved. The update ran smooth and solid and everything is working just fine so far. THANKS!!!

  • Ben

    I found that works for people with the cannot read file error.

  • Nagakiran

    Just updated my Nexus 7 (2012) with the instructions above.. Had to use PDAnet to fix device not found error.Other than that,the instructions were very clear. Thanks for sharing !

  • Hanif Sipai

    E: Signature Verification Failed Error stucked Please help.

  • Abdulla Jassar

    Can you plz tell me how to navigate in windows XP

    cuz I have this path :

    C:Documents and SettingsMSFuserDesktopadt-bundle-windows-x86-20131030sdkplatform-tools


  • Samm

    Does this root and/or unlock the bootloader on the device??

  • merino

    how to navigate in command prompt? i put my sdk , kitkat files under C:Users }my name directory…but it said adb is not recognized as an internal or external command, operable program or batch file.

  • bizo

    plzz help guys … version 4.3 is so bad
    i have a lot of issues … battery gets exhausted fast , screen gets hotter, notification par dis responded, the side bar should be shown and hidden by the back arrow and doesn’t respond any, finally the WiFi having a problem connecting any wireless.
    plz any other update or bring back my old OS.

  • Md. Atiar Rahman Chowdhury

    I am a nexus 7 (2012 wifi) user. I flashed my device with custom rom several time. can download the ota update 4.4 but then i am getting error installing it. also i am facing problem with adb sideload. what is the solution ?

  • Shahriar Ahamed

    Help full post. 100 like for this post.
    Please visit for free android apps

  • SB

    Folks, any idea how to update to Kitkat on a non-Nexus Tablet ( I have a local made tab which is having 4.0.4 android firmware)

  • ferreol

    How to root this kit Kat update?
    Any solutions ?

  • Adam Johnson

    I need some help on MacOSX, i’m stuck on the sideload section so how do i move the file to my phone

  • Vaibhav Ravichandran

    updated to 4.4.1 on my nexus 5 using this method :) thank you

  • mohammed

    my nexus 4 still have android 4.2.. how to go about updating it to 4.4?

  • Ana

    Hi, I was wondering if these steps will work on another phone if im using the correct OTA files for my phone? Thanks!

  • DarxideGarrison

    Yall dont have to rename the file. just highlight the folder name right click and “cut”. when you open the command prompt, type adb (space) sideload (space) and rightclick the top of cmd box and paste and add “.zip” so it looks like this:

    adb sideload

    and just hit enter provided you have sdk tools, tablet, & everything else set up correctly. It worked for me!

  • Paul

    I got Nexus 5 and constantly checking the update from settings asap I came to know 4.4.3 is available but it is still showing 4.4.2 as a updated version and not yet downloaded the new update. As a Jesus user isn’t it suppose to update automatically as soon they are released. I guess I can do it manually but to hasseles waiting for auto update. Is there anything I am missing or is the update not yet available for UK?

  • I have build number JWR66V, not Y. Does this matter?

  • Stefhani Santos Vilvar

    I have my nexus 7 2013
    My tab is 4.4.2
    My problem is,, it always requesting update to 4.4,3 but if I started to install it will become error,,

    Do i need to use laptop to update it??
    but before when I install it will updated automatically without computer

    • Stefhani Santos Vilvar

      Plz reply

  • Observer

    I have an Android TV box, with Rockchip Nexus 10 Android 4.4.2 Kernel 3.0.36 root@ubuntuweaver 15
    RK3188 4.4.2 KOT 49H Vendor Nepumuk V1.00 firmware.

    it is prompting me for a storage decryption password at start up.
    If I re set, I am prompted with the android logo and a question mark, and unable to go further.
    After a few minutes, it reverts back to password prmpt.

    Anyone has an idea how to proceed please ?

  • Michael Scott

    My Nexus 7 (2012) seems to be stuck half-way between “regular” boot mode and Fastboot mode. That is, when I hit the power button, the Google logo comes up in the middle of the screen and the (unlocked) lock appears at the bottom of the screen…….but I also have the Fastboot menu “tabs” visible at the top right (either Start, Recovery, Restart bootloader, etc).
    But, that’s as far as I can get. I can roll/scroll through the Fastboot options using the volume up/down keys, but Restart bootloader and Power off are the only two commands that do anything. (

    Power off DOES in fact power down the unit……and Restart bootloader brings up Android man lying on his back……with the Fastboot Mode list of Product Name, Variant etc, etc down in the lower left quadrant of the screen…..but from there, I can’t go anywhere. I can’t get into the recovery menu with all IT’S commands. When I click on Recovery mode, using the Power button for example, I get a tiny white “Booting failed” message in the top left corner of the screen.

    I’m suspicious that while in the process of desperately attempting a downgrade, I may have inadvertently yanked a USB cord when I was halfway through doing a “flash-all.bat” command while trying to get KitKat 4.4 loaded, which is my ultimate goal. (I foolishly let 5.1 OTA and have been trying to “get back” ever since.

    Any suggestions as to what I should try now? Please and thank you, anyone!

  • Kal Clark

    Better instructions in how to enter recovery mode:
    If your tablet is on, turn it off.
    Press and hold the Volume Down button, then press and hold the Power button at the same time until the tablet turns on. You’ll see the word “Start” with an arrow around it.
    Press the Volume Down button twice to highlight “Recovery.”
    Press the Power button to start Recovery mode. You’ll see an image of an Android robot with a red exclamation mark and the words “No command.”
    While holding down the Power button, press and release the Volume Up button once.