14
Nov
KitKat-Thumb
Last Updated: June 2nd, 2014

Back on Halloween, Google promised that proprietary binaries and factory images for the Nexus 4, Nexus 7, and Nexus 10 would arrive shortly after devices received their OTA updates. Even though some OTAs haven't even rolled out yet, as of a few minutes ago, all modern Nexus devices now have Android 4.4 KRT16O factory images and drivers available for download.

image

This means you can flash stock Android 4.4 onto any supported device, even if an OTA either wasn't available yet or wouldn't work for some reason. The availability of binaries/drivers, on the other hand, is great news for custom ROMs.

Note #1: If your bootloader is locked, your data will be wiped for security reasons - there's no way around that. You will want to back up what you want manually.

Note #2: If your bootloader is already unlocked, you have the option of skipping the data wipe during the factory image flashing procedure. In some situations, not wiping user data may prevent the device from booting, in which case you'd probably need to go ahead with the wipe, but for simple OS upgrades from one version of stock Android to another one higher, wiping data should not be necessary.

Prerequisites

In order to complete the steps below, you need to have the Android SDK installed. The SDK contains the latest version of adb and fastboot, which you will need for flashing files and issuing commands. You will also need a MicroUSB cable to execute adb sideload, fastboot flash, and other commands. You also need to unlock your bootloader - a process that wipes your data.

Enable Developer options by going to the Settings -> About screen and tapping Build number until the OS unlocks the hidden Developer options menu. Now go to Developer options and make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done.

To unlock the bootloader, if you haven't already done so:

  1. Reboot into the bootloader by issuing an adb reboot bootloader command on your computer or using the correct combination of buttons applicable to your device.
  2. Warning: This will wipe your data. Type in fastboot oem unlock on your computer. Agree to the unlock by selecting Yes on your device (VolUp, then Power).
  3. You have now unlocked your bootloader (and the data partition was wiped clean). Verify by rebooting to the bootloader again and looking at Lock State.

Instructions

  1. Download the full factory image corresponding to your exact model (for example, 2013 Nexus 7 Wi-Fi is razor), which includes the full system, bootloader, recovery, kernel (boot.img), and radio (radio not included for Wi-Fi-only variants). It's a clean slate for these components - they'll flash cleanly over anything you have now.
  2. Unpack the tgz (tar/gz) archive into its own directory. I use Total Commander, but you can use any tool that reads gz and tar, like 7-Zip.
  3. Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and:
    a) remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip. The -w option instructs fastboot to wipe data.
    b) remove any mentions of fastboot erase userdata if you see any. Oddly, some factory image scripts, like the one for nakasi, wipe each partition manually first. You don't want to lose userdata.
  4. Reboot into the bootloader and run the appropriate flash-all script.

That's it, you're done.

Note: The above procedure restored the factory recovery, so if you want a custom one, you can flash one now (see below).

For better security, you can relock the bootloader by issuing fastboot oem lock while booted to the bootloader. This will, however, mean that if you ever want to do anything that requires an unlocked bootloader, you will lose your data in the unlock process.

Rooting

Rooting your Nexus device is very easy. It requires an unlocked bootloader and a custom recovery. I recommend using TWRP.

  1. Flash TWRP from here (Reboot into the bootloader as before and then fastboot flash recovery FILENAME.img).
  2. Reboot into recovery (adb reboot recovery).
  3. Flash SuperSU. To do that, download the zip, then put the recovery into adb sideload mode (in TWRP, it's under Advanced), and then do adb sideload FILENAME.zip.
  4. You should be rooted.
  5. Reboot, head to the Play Store, and update SuperSU.

Nexus Images, Nexus Drivers

Artem Russakovskii
Artem is a die-hard Android fan, passionate tech blogger, obsessive-compulsive editor, bug hunting programmer, and the founder of Android Police.
Most of the time, you will find Artem either hacking away at code or thinking of the next 15 blog posts.

  • Sven Joy

    Getting 404 on nakasi.

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

      Yeah, that one seems broken. nakasig works but not nakasi. I'm sure it'll be fixed in no time.

      • brnpttmn

        Aha! Thanks!

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

          It's fixed.

          • pyroguysf

            It's up but the checksums don't match so I'm a little leery with the multiple problems today... has anyone successfully flashed the factory image yet? I'm getting
            MD5: c9fc3764ab268962424b38e75b26d875
            SHA-1: b27054b89ccbf0a268c7bfb9cfd7cc4570f1d0a8

          • test21843

            I keep getting invalid bootloader image, even doing manual steps. What gives?

          • Richard

            I had the same issue. Confirm you are using the correct factory image. The file you download should start with "occam". I accidentally used the "mantaray" image which is for the Nexus 10.

          • test21843

            Even without running checksums, the size of the download keeps changing.

          • Sandro

            Hello

            I've the same md5sum and sha1sum of yours... either someone hacked the official factory images or google put the wrong files or checksum!

          • http://wugfresh.com/ WugFresh

            I am still getting a mismatch hash for razor but I was finally able to get matching hashes for all the other packs (based on what google posted). Here are mirrors if anyone needs: https://www.androidfilehost.com/?a=show&w=files&flid=9490

          • pyroguysf

            I initially used your NRT (thanks!) cause I'm lazy. Looks like you're still missing nakasi/grouper too though. I'm still getting the same 345 MB file this morning that I can't get a proper flash out of, so I'm just gonna wait. Also, why is the first thing it does unlocking the bootloader? Shouldn't the factory image not require that?

          • Joshua Talley

            Mine is mostly functional, but doesn't want to properly log in to Google service. For example, Google Now is a no-go. Period. Keeps saying there's a "network error" which is incorrect, as everything else connects just fine. Also, I can use Hangouts for SMS, but not for Hangouts. In fact, nothing involving Google sign-in works. Time to go back to 4.3

          • Haneesh

            Can you verify if its working with that image (the one with different md5 than the provided one) please..

    • FaizVisram

      it's (FINALLY) fixed! :D

  • Ryuuie

    Actually, the 10 isn't there for some reason... D: My bad. :(

    • Mort

      No, it's there... there's just no shortcut at the top of the page (seen in the screenshot above). Scroll down to
      Factory Images "mantaray" for Nexus 10

      • Ryuuie

        Ohh. Ok. Cools. :)

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

      Definitely there, just downloaded it.

    • A

      As usual, Google forgets about the N10 because they don't give a shit.

      • michi

        huh? i see it, just have a closer look

  • Gregory O’Neill

    I almost yelped out at my desk at work. Jumping for joy

    • Gargl Popargl

      Be careful. Not that anything breaks or something.

  • http://404err0r.com/ Henry Park

    I reset it so I can get it through the right channels.... fine... I'll wait a little more until they send the OTA...

  • epsiblivion

    so the nexus 4 doesn't have ota yet right?

    • Ryuuie

      No, it's just factory images which you CAN flash over. It'll just wipe your device.

      The OTA will probably be out today though.

      • Jadephyre

        Just leave out the userdata.img (as in delete it from the ZIP inside the download) and you can keep your stuff ;) (Photos, music, basically everything you put on your device yourself. Save your Texts though, those won't get saved by omitting userdata.img)

        • Kieron Quinn

          Why wouldn't your texts get saved? They're stored in the data too

          • Jadephyre

            Really? Okay, i'll take your word for it, but I saved mine regardless, just in case you know ;)
            I always thought that texts would be saved somewhere in the system.

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

          I have the guide up now. You don't need to leave out userdata.img if you want, just take out -w from the script.

          • TEST

            Artem, When do you think the Nexus 4 ota will start rolling out?
            *Please answer if you can*
            *Android police is by far the best android blog, Keep up the great work!*

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

        You don't need to wipe if you're already unlocked.

        • Ryuuie

          Oh, really? Didn't know that. I thought it was the flashing of the factory image itself wiped it. Huh.

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

            No, it's the flashing of userdata.img that wipes. Flashing system, boot, and recovery images just overwrite something you can't write to anyway from within the OS.

          • Jay W.

            Will SuperSU 1.69 have any impact on this? Do I need to unroot, first? I had a hell of a time flashing the OTA on my N7... had to flash the 4.3 image first.

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

            If you use a factory image, it doesn't matter what your existing system partition looks like and if SuperSU's OTA survival mode was on. The factory image will flash a clean stock 4.4 system partition.

  • @bleakneonblack

    Gonna get a post together for the install process? Is it just flashing the image? I don't need to do anything with the drivers right? Flashing equates to a wipe though, I believe...

    • brnpttmn

      I'm interested in this also. I have a Nexus 4 that is rooted with the 33/84 hybrid radio flashed, and I am wondering about the best way to upgrade. OTA or flashing separate.

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

        I already updated the post with the full guide.

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

      Just updated the post with the guide.

      • @bleakneonblack

        Thanks! If I am reading correctly, my locked bootloader means no way to upgrade without a wipe, right?

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

          Well, the OTA won't require a wipe if you're locked. But flashing a factory image does need an unlocked bootloader.

          • @bleakneonblack

            Guess I'm waiting for the OTA! :(

          • Guest

            You can unlock your bootloader in a few seconds...

            download a copy of fastboot, open terminal/cmd in the same folder as fastboot, type in

            fastboot oem unlock (or if you're on a mac, ./fastboot oem unlock)

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

            Except that wipes data.

          • Nathan

            Use scenario 2 from here: http://www.androidpolice.com/2013/07/24/how-to-flash-your-nexus-4-to-android-4-3-jwr66v-and-root-it-right-now/

            Works like a charm.

            You won't lose any data. Not from (system) apps and not from the internal memory either.

  • Huton Gergö

    Google thx for my births-day present

    • http://blog.code-infection.com/ Balazs Nadasdi

      If we get an OTA on friday or saturday... Then that will be my birthday present too :)

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

      How many births did you take today?
      KTHXBYE.

  • Ryan Markwald

    N7 2013 wifi downloaded too quick, and it only has flash-bash.sh, flash-all.sh, and flash-all.bat inside...missing stuff.

    • Sven Joy

      Same for me...

    • http://www.standupforkids.org blackroseMD1

      Same here. They may be in the process of being uploaded.

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

      Yea, that one seems broken too. It's the curse of the Wi-Fi Nexus 7s!

    • Casey

      Ditto

    • Andrew Chandler

      It got pulled because at first it was wrongly linking to the image for the 4G model (deb), not the Wifi model (flo).

    • David Marion

      The link is now fixed.
      The checksums on the page are still wrong, from when the file was under 1MB. These are what I got.
      MD5 - 1bb4ce870b4c79483a0e83735679bea5
      SHA-1 - 91d28ab13d32fe4926fd3cfdfbe2d92efeb62b69

      • http://wugfresh.com/ WugFresh

        I can confirm that is the same hash I am currently getting for razor.

  • Addic7ed

    Hi, if il flashing with thé nexus root toolkit can i still root and install twrp ?
    I've yet done a backup with titanium ;)

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

      You can always install TWRP and root.

      • Addic7ed

        Thx for reply
        I m going to flashing now m'y n4
        Best regards from france

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

          Added the rooting/TWRP section.

          • Addic7ed

            doesnt works with nrt tool^^

  • perhac88

    So if your bootloader isnt already unlocked, you lose all data if you unlock it then?

    • Josh C

      Yep. If you're locked and want to not lose data i think the only option is to wait for OTA.

      • perhac88

        Ahhhhh tough decision then....

        Edit: So when the ota comes out can you sideload it without your bootloader unlocked and not lose data? Or do you need to unlock the bootloader?

        Sorry for all the questions :)

        • Josh C

          You could do a full backup from adb, unlock bootloader, upgrade, then restore the backup. But it won't be exactly the same as a straight forward update w/o wipe. You'll have to redo your homescreen(s) and such, and sometimes not all of my apps restore for whatever reason. If i were in your shoes i'd probably just wait to see if i get the ota in the next few days :p

        • Melissa Peterson

          The OTA is downloaded directly to the device, so it's not necessary to sideload it. You also don't need to have an unlocked bootloader and nor will the OTA wipe any of your data.

  • Kyle Riedemann

    Anyone flashed yet? Is the messages app still there?

    • Hakan

      Yes

  • Recznik

    Rayman Fiesta Run saves are in cloud?

  • Leonardo Benveniste

    The Nexus 4 doesn't have the transparent nav and status bars!!

    • TheLastAngel

      Wow, that sucks! I hate Google for the entire rollout of 4.4 to "legacy" devices. Half assed as can be.

    • realizm1

      You have to have the updated Google search app. Or you can have the Nova kit Kat beta(which is really nice) and enable in settings!

      • Leonardo Benveniste

        I have the latestlatest version of the search app and I got nothing. Also Google Maps isn't showing the new transparent bar either, I get black bars everywhere

        • Ryuuie

          You also need the launcher to go with it.

    • Ryuuie

      They're there, just not accessed by the stock launcher.

      • Leonardo Benveniste

        Google maps isn't doing it either

        • Ryuuie

          Google Maps isn't supposed to. It's only for when you're not in an app OR if an app calls for that specific API. Maps doesn't call for the transparency API.

        • Crispin Swickard

          Currently its only on the home screen, and apps would need to be updated to support the new feature. None do this (so far). Books was updated for the new full screen thing, but that should work on any 4.4 device.

          • Leonardo Benveniste

            Maps on the Nexus 5 does it

          • Crispin Swickard

            Doesn't seem to on mine yet. Not sure if I may have gotten the update for yet though. Unless it was suppose to be the one thats ships on it. If thats the case its not working for me at least.

  • Victor A. Ceja Jr

    Sorry for being uninformed but can you brick your phone by flashing these images? I have always been afraid of rooting because of the possibility of bricking the phone. Thank you.

    • Ivan Feign

      Nope. Only if you do it wrong somehow, but it's pretty hard to do wrong.

      • Victor A. Ceja Jr

        So it is pretty safe to try it myself even though I've never flashed or rooted before?

        • Ivan Feign

          Yes, it is very easy. Just follow the guide. I wouldn't worry when flashing official images, only if you're going to flash a custom rom/kernel, you should be cautious.

          • Victor A. Ceja Jr

            Thank you! I look forward to 4.4 Kitkat!

          • Ivan Feign

            Me too! I just installed it on my Nexus 7. I'm gonna wait for CM11 for my Nexus 4 though, there's certain things in AOSP that annoy me, that CM does better. Now that these binaries are out, CM11 for the N4 can make some good progress.

          • Crispin Swickard

            Also if your a bit timid on things if you google the Nexus Root toolkit it can automate a lot of the process for you. ADB is not my friend...

          • Victor A. Ceja Jr

            Thank you for the suggestion! Will do

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

      1. Just the opposite, in fact, these factory images exist so you can unbrick something you've bricked. They're there so you can always restore back to stock.
      2. You don't need root to do this.

  • manish aditya

    nexus 7 2012 wifi 4.4 download link not working

  • fzammetti

    I wish all these guides everywhere would stop saying "use a custom recovery to flash" because people will do that and then wonder why they can't take an OTA next time. Instead, it should clearly specify to use the custom recovery TEMPORARILY, but but stock back afterwards... unless a person actually WANTS a custom recovery permanently of course, but I've talked to some people that don't realize they even have that choice.

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

      A custom recovery shouldn't prevent an OTA, should it?

      • fzammetti

        In most cases it will... at least on some devices, and I'm actually not sure about the Nexus devices now that I think about it.

        • Chris Hutchinson

          People always say it doesn't work, but I'm sure I've done it when putting Jellybean onto my old n7.

          • fzammetti

            And I recall doing it on some devices in the past as well frankly... so I wouldn't claim it's an all-or-nothing proposition... but, to me, it falls in the "better safe than sorry" category, that's why I made the comment... better people go in with their eyes open either way.

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

          I've always flashed OTAs with custom recoveries, and I don't think I've ever had a problem.

        • PaintDrinkingPete

          Yeah, I've never done it on a Nexus device either, but I know on some of the older devices I've owned that OTAs wouldn't work if a custom recovery was used...errors and fails when flashing. Probably best to check first.

      • Leonardo Benveniste

        Yes it does

      • Martial Clausse

        It does, at least on the Galaxy Nexus and the Nexus 4.
        OTA gets downloaded but it then reboot to recovery to update, and the custom recovery can't use the update package.

  • TheSparks
    • KrispyInTO
    • NoBullet

      holy shit this is the most overused gif. youre killing it

    • souleymane sidibe

      hello
      i have this : ./flash-all.sh: 21: ./flash-all.sh: fastboot: not found

      I dont anderstand the step 4.
      please!

      • Geek

        Your Fastboot is not set as an environment variable ! Rather do one thing, fo to the SDK>Platform-tools>and past your files here and then flash the stuffs

        • souleymane sidibe

          thanks!

        • Tobbbe

          What if you get this error and already have all the files in SDK/Platform-tools? :S

          • McNucklefuts

            I have this problem too - all the files are here and its still giving me this problem!

          • Clive Cleaves

            You could edit the flash-all.sh file with ./fastboot in front of everything.

            Or you could add the path your fastboot file is located by: export PATH=${PATH}:/Users//Desktop/path/to/file in your .bash_profile

      • rbfx4x

        sudo apt-get install android-tools-fastboot

        Assuming you are on Ubuntu :)

  • ViperX

    Is it true, no transparency on Nexus 4?

    • Jay W.

      Not true. Read around a bit for the details.

      • ViperX

        Ok, thank you. I will try it in a few minutes.

    • Stacey Liu

      The lock screen is not transparent. GEL and Google Search are. So...it's half there.

  • asdf
  • michi

    get the nakasi image working, please

  • hasan

    Finally. Just flashed 4.4 on Nexus 4 :D

  • Patrick Marcelino da Silva

    Hi how do I do that with adb ???

  • kodextr

    the link for nexus 7 2012 wifi only version is broken

  • Jay W.

    What is the command to run a batch file from fastboot?

  • RockAndRock

    My device is not detected when I type adb devices on the command :/

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

      Uninstall the USB driver and reinstall it using the one in the Android SDK. I had this problem too and that fixed it.

      • RockAndRock

        It's hard :(

      • Patrick Hills

        oops nvm

        • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

          Ok? What do you need help with?

      • RockAndRock

        can you give me more details please ?

        • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

          Is this your first time using the Android SDK? Are you using Windows or Mac?

          • RockAndRock

            Yes, it's the first time. I'm using Windows

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            You need to run Android SDK Manager, if you still haven't and install Android SDK Tools & Android SDK Platform-tools in order for those commands to be valid. After you have those installed from the Android SDK Manager, in a command prompt make sure to use the "cd" command to change your directory towards the "platform-tools" folder found on your C: drive. If you need more help, search on Google on how to use ADB and fastboot commands or some type of guide.

          • RockAndRock

            thank you, i need help now with the 3rd step

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            When you unzip the folder, there will be a 'flash-all.bat' file. You need to right click on it and open it to modify one line in there. If you need more clarification give me a few minutes to check and answer on here.

          • RockAndRock

            i can't open this file for editing :(

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            Use a word editor to open it. Access the file by right clicking and opening the file with a program that you choose (as long as it can edit text).

          • RockAndRock

            You have skype ? I'm really lost :(

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            I do have Skype. For various reasons, I cannot post any contact info on these comments.

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            If you want, my Google+ account is linked in an article within AndroidPolice (I supplied them with an APK before and thanked me for it). You can find my link at the bottom of this article: http://www.androidpolice.com/2013/10/16/netflix-v3-0-for-android-begins-a-slow-rollout-complete-redesign-with-slide-out-navigation-action-bar-and-no-more-lag-apk-download/

          • RockAndRock

            i sent you a message on hangouts

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            It was a pleasure helping you.

          • MyLeftNut

            Actually, you don't need the whole sdk, just a few files. As long as you have those, you'll be fine for this relatively simple process. If your device still isn't being recognized but you have the appropriate files then download and unzip this file http://downloadandroidrom.com/file/Nexus7/rooting/Nexus7Root.zip. In the USB drivers folder there is file called android_winusb.inf. Plug your device in while in adb mode, open "Devices and Printers" in your start menu. Your device should be under "Unrecognized devices with a yellow triangle. Right click and select properties (and get your device ids while in there) manually update drivers. When it asks, select I have disc or something similar and browse and point it to the .inf file from earlier. It will install and update your drivers and the flag should disappear. The name should also change. You can also download this file from Google directly but the link gives you the adb.exe and fastboot.exe as well.

            If, even with the appropriate drivers, your device still ins't being recognized in cmd. Open the .inf file and make sure the device ids under your device match the one you pull earlier. If your id isn't in there add it in the appropriate section 32/64bit, save and install the driver.

          • MyLeftNut

            Sorry I mean you can download the driver from Asus directly or from whomever is the manufacturer of you device. Diego laid it out a bit more succinctly. I need to learn to edit :)

          • BrahManty

            I'm having the same problem, but my nexus 10 doesn't even show up in unrecognized devices when its in recovery so I can't get a Device ID to fix the drivers. Its like its not even connected, but I can hear windows recognizing that its plugged in. So confused.

    • Sean

      I've had similar issues, even with the correct USB driver... This post fixed my issue: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/

    • Nimer55

      http://developer.android.com/sdk/win-usb.html

      download that on desktop. Then go to device manager (on windows), you should see something that either says Android or Nexus with a a yellow triangle on it. Select update driver, then pick local file, and use that file you downloaded on desktop... It worked for me.

  • Marlab

    N7 13 image still retarded. Well no problem for me because I'll have to send my nexus for third repair anyway so I wouldn't enjoy kitkat for long anyway...

  • Jefficko

    VARIFICATION FAILED... :( help?

  • Lastb0isct

    What if i'm already rooted with my Nexus 7 2013? How would i go about putting this on it?

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

      Doesn't matter if you're rooted or not.

      • Lastb0isct

        But i shouldn't need to use the Android SDK, correct? Can't i just put the image on my tablet and flash from there?

        • Jadephyre

          No.

  • Andrew Chandler

    Umm... 2013 Nexus 7 Wifi links to the image for the 4G version. Didn't notice until I tried to flash and it failed. What the hell, Google??

  • Chapi

    LOL yesterday ive loaded AOKP on my Nexus4 and today...surprise :D

    One question: it doesn't matter that i have custom rom and root right? Just need to install 4.4 img via ADB?

  • Johnny

    My phone won't get past the boot logo :/

    Help?

    • Patrick Hills

      Chiming in on this: I'm having the same issue.

    • PaintDrinkingPete

      It's not likely I'll be monitoring this thread to respond (you may get better help taking this to a forum), but it would help to know (1) what device you have and (2) any other info about your install...did you wipe data? did you check file hash after downloading? etc...

      • Johnny

        I have a nexus 4 - I used the flash-all script and my device just doesn't get past the boot logo. I didn't wipe data because the post said it would install cleanly over everything

  • Patrick Hills

    I'm stuck at the boot screen after using flash-all... any ideas?

    • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

      Instead of using the flash-all, try doing one by one...

      • Patrick Hills

        Hmm.. just competed that using a new cable in a new usb port. Phone completely wiped. Using a mac... any other ideas?

        • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

          I'm assuming it didn't work?

          • Patrick Hills

            OOps, yes, it didn't.

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            What was your device running prior to the installation? It might help me assess what's wrong.

          • Patrick Hills

            4.3 Stock, CWM, Rooted, Unlocked bootloader.

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            I had a custom 4.4 Kit Kat AOSP ROM that was rooted with and unlocked bootloader and the TWRP recovery; my phone booted up (though it failed like a bajillion times and crashed so I wiped everything since I have a backup).

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            You might try wiping everything and doing one more time. If not, I have no suggestions for you. Are you sure you flashed everything correctly.

          • Patrick Hills

            Okay. Finally got it. Used an updated Fastboot / ADB, flashed the system image twice. Don't know what exactly fixed it, but thank you for your help and suggestions,

          • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

            No problem. 😃

          • AkhilSood

            Yea the updated Fastboot needs to be used on mac. The older one borks up when flashing system.img. I had to spend quite some time figuring this one out.

        • Justin

          Also using a Mac. I ended up having to enter each command, preceded by "./" and that seemed to work for me.

  • Ransom

    Okay, so i flashed everything as supposed to and it worked wonderfully. I decided to enable ART instead of dalvik though, but that made my N4 go into bootloop. Flashing 4.4 via adb doesn't help get it back to normal, i suppose i should reflash custom recovery and get a backup from before flashing 4.4?
    Also, is that google's fault or just my device?

    • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

      It might be incompatibilities with your installed applications... ART is still very experimental.

      • Ransom

        oh well, i thought incompatible apps simply wouldn't launch

        • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

          Well, that's true, but some apps might be causing a problem. It's only a possibility...

          • Ryuuie

            It shouldn't be causing a bootloop. It sounds like something didn't flash right.

  • Patrick Marcelino da Silva

    Guys, how do I install de rom, using the adb sideload?

    • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

      You can't with the factory image.

      • Patrick Marcelino da Silva

        Thanks man!

  • http://riteshtripathy.wordpress.com/ Ritesh

    Someone please tell me the Occam tar is okay and not missing shit?

    • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

      It's not missing anything. You can flash everything and it works. I can confirm.

      • http://riteshtripathy.wordpress.com/ Ritesh

        Cheers!

  • donjamal

    is anyone else having issues with the home button not taking you back to the homepage? :O nexus 4 - flashed without wiping data

    • donjamal

      also clicking on links doesn't work - it just opens chrome but does not navigate to the site

    • Jadephyre

      Yeah, as long as I didn't have any one launcher set as default it sort of worked by displaying the list of launchers, but Apex currently doesn't take me back.
      I'm going to do a full flash to stock 4.4 and root again.
      Means i'll have to copy everything to the phone again, but what the hell, better safe than sorry ;)

    • Stacey Liu

      Yeah you have to wipe data. This happened to me the first time.

  • Crispin Swickard

    Alright N10 your time has come to join the N5... Was planning on doing the forced OTA thing with TWRP tonight anyway. Now I have an alternative if that doesn't work out. :)

  • Bruno Marangoni

    Hello guys!

    I read the instructions but I gotta ask:

    - Is it needed to install drivers if you have a locked bootloader and stock rom installed on Nexus 4? Or it's just a matter of "sideload it and be happy"?
    - Will my data be wiped if I have all conditions above checked?

    • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

      You cannot side load it. It is the factory image, not OTA Update .zip file for one to use ADB Sideload. If you unlock your bootloader all your phone's date will be wiped. An unlocked bootloader is needed to apply this update with the factory images. You can try backing it up (there are methods online you can use).

      • Bruno Marangoni

        But my only problem will be if I have to install all the drivers. Will I need it?

        • http://twitter.com/diegojdiaz Diego Josué Díaz Reyes

          I'm confused by your question. Are you referring to the drivers for you computer? If so, yes, you'll need to install the drivers to be able to hook up your phone and it be able to be registered by you computer. If you're referring to the Nexus 4's drivers, no, you'd only have to install the bootloader, then the radio, and finally the image... Or you could use your flash-all script (though I recommend against it).

          • Bruno Marangoni

            Sorry, I meant the Nexus 4's drivers. Thanks for the info. Gonna try here and see if works.

          • Bruno Marangoni

            Worked like a charm! I used the flash-all script (erasing the -w command) and everything's fine here. Many many thanks!

  • i2cube

    Umm I don't see the factory images for Nexus10 in either googles page or the image that you posted here.

    • Crispin Swickard

      Its not in the first section with the links currently, but if you scroll done to the actual device listing it is there.

      • i2cube

        Awesome. I should have scrolled down before leaving that comment....

        • Crispin Swickard

          You would think it would be there, but impatience tends to strike us Nexus folk who tend to "need" the current OS version right now. I am chomping at the bit to get home, and flash mine now. lol

  • Syafeeq Shaharani

    nakasi (nexus 7 2012) worked now. :D

    • Franco Rossel

      Use the one from 4.3

  • Guest

    I've been trying to upgrade my N10 since early this morning and for the first time in my Android flashing history, I fell like an absolute noob. Nothing I've tried has worked all day and I'm completely stumped as to why I'm sitting here with an almost useless tablet.

    I started by downloading the build linked to in this article. What I hadn't realized was that I shouldn't have tried flashing while using TWRP (since it doesn't support 4.4, according to a bunch of comments I've been recently seeing). Doing so resulted in my N10 not being able to boot into anything but the recovery... except that the recovery was then the stock one. Since I couldn't get it to boot, I re-flashed TWRP and tried installing a couple of the stock builds, but they all failed. I even tried wiping all the data and have even done it a few times since, but that has never helped.

    So then I tried flashing a stock recovery that I extracted from the stock Jelly Bean build's archive (mantaray-jwr66y-factory-3d8252dd.tgz). That doesn't work. CWM either. In fact, the only recovery that I can get to work now is TWRP. The others just get stuck in a weird bootloop where the screen just flashes like it's trying to boot up.

    I thought the factory image here might solve my problem, but the installation just fails every time.

    Oh, and I've also tried re-locking and unlocking the bootloader, but that didn't do anything.

    Please tell me somebody here can help me figure out some way to fix this. I would happily go back to JB at this point and just wait for the OTA if that's what I had to do to get this thing to boot again.

  • Mike Harris

    Ugh... I've been trying to upgrade my N10 since early this morning and for the first time in my Android flashing history, I fell like an absolute noob. Nothing I've tried has worked all day and I'm completely stumped as to why I'm sitting here with an almost useless tablet.

    I started by downloading the build linked to in this article. What I hadn't realized was that I shouldn't have tried flashing while using TWRP (since it doesn't support 4.4, according to a bunch of comments I've been recently seeing). Doing so resulted in my N10 not being able to boot into anything but the recovery... except that the recovery was then the stock one. Since I couldn't get it to boot, I re-flashed TWRP and tried installing a couple of the stock builds, but they all failed. I even tried wiping all the data and have even done it a few times since, but that has never helped.

    So then I tried flashing a stock recovery that I extracted from the stock Jelly Bean build's archive (mantaray-jwr66y-factory-3d8252dd.tgz). That doesn't work. CWM either. In fact, the only recovery that I can get to work now is TWRP. The others just get stuck in a weird bootloop where the screen just flashes like it's trying to boot up.

    I thought the factory image here might solve my problem, but the installation just fails every time.

    Oh, and I've also tried re-locking and unlocking the bootloader, but that didn't do anything.

    I really hope somebody here can help me figure out some way to fix this. I would happily go back to JB at this point and just wait for the OTA if that's what I had to do to get this thing to boot again.

    • Mike Harris

      I extracted the recovery from the stock KitKat build's archive and flashed that. That, at least, let me boot into the recovery safely... but it's still in a boot loop that keeps going to only the recovery. And when I try to install the factory image, it again fails. I also tried wiping all the data again.

  • Filipe Dâmaso Saraiva

    Thank you so much for these instructions, it was my first factory image flash and it was exactly the help I was looking for. Everything went smoothly! Cheers :D

  • MerdescuRazvan

    Check your device storage on the Nexus 4. I had this issue where out of my 16 Gig i only got like 5 usable. Looked it up on the internet and it seems like something didn't erase right. Re-flasing manually took me some time :(.

    Careful !

  • Burt the Brave

    Can anyone explain this? Unlocked Nexus 4 with 4.3 (JWR66Y)...

    Device version-bootloader is 'MAKOZ20i'.
    Update requires 'MAKOZ30d'.

    • Juliano

      Easy. Google published an image that does not contain the required bootloader version that you must apply before flashing the image.

      That's what happens when you fire JBQ.

      • Franco Rossel

        JBQ wasn't fired, he quit.

        • Juliano

          yeah yeah, i know...

          and btw, good thing it was just a naming issue.

          • rainaby

            I cant update my phone as the bootloader version differs ! What to do ?

      • Stacey Liu

        They didn't change the file name. The bootloader in the image actually is Z30d, but the image file is named Z20i.

        DAE THINK JBQ WAS THE ONLY COMPETENT GOOGLE EMPLOYEE?!

        • Juliano

          lol there, there, let me put the emoticon for ya:

          "That's what happens when you fire JBQ :-P"

        • JeyPs

          Can I just rename the file then?

          • Stacey Liu

            You don't have to do anything. The file name is irrelevant. the only reason it's there is so you can point fastboot to the new bootloader. The phone only looks at what's inside the file, not the name.

    • Kevin Jones

      Have the same issue, any answers?

    • Aalok Kamble

      you'll need to unlock the device.
      use 'fastboot oem unlock'
      then try again.

  • Nathan

    4.4 OTA over here on my Nexus 4!!

    • Jefficko

      what are you saying?

      • Mike Harris

        4.4 OTA over there on his Nexus 4!!

        • Nathan

          I will provide you guys with the file as soon as I can.

          • jm9843

            Yes, please and thank you.

          • TeamNexus

            Where will this be available?

          • Nathan

            Right here at Android Police.

          • TeamNexus

            Thank you!

  • Saymonps

    I have 4 Nexus bootloader unlocked, rooted and stock recovery. Making full process willlose root?

    • David Marion

      Yes, you will lose root. It's easy enough to re-root, though.

      • Saymonps

        In fact it is a simple process. Thank you!

  • Squiddles

    Removing the '-w' will keep data on the SD storage partition? For 4.3 I manually flashed everything but the 'userdata.img' in the zip.

  • Wayne Randall

    Suckered again by the .png of links..

    bastards.

  • disqus_D5EpY60qw2

    The nexus 7 2013 Wifi tgz file only has the flash scripts and nothing to actually flash ಠ_ಠ

    • Jefficko

      sherlock

  • Mike S.

    You don't need to flash a custom recovery in order to root. I rooted and kept the stock recovery.

    • David Marion

      You can, but I see no benefit to it.

  • Ryuuie

    Hmm.. wondering if there's an issue with the camera on this. I'm getting a black screen when I open it.

    • Squiddles

      Mine seems to work.

      Side Note: Not sure if it was possible before, but following the changes in 4.4 I can swipe down in the camera and see the notification area [as seen in the attached screenshot]

      • Ryuuie

        Did a reboot and it works now. :)

        That's a 4.4 change, yes. It allows you to get notifications if the bar's hidden without having to leave the app.

  • Nitinart Nunthong

    already installed it.I tried Android Runtime too ,I think it makes a nexus 4 faster. :D

  • Fitzelgard Allan Gerard

    Is anyone else having this problem with G+ that you can't change Notification tone? Mine just won't budge. Its stuck perma with System Default tone set.

  • Ricardo

    hey guys,i need a lilttle help here, two things:
    i have already instaled the adb and fastboot drivers in my pc, becuase i had to install it 3 months ago when my phone got in a bootloop so no problem here

    i already downloaded the factory image and used winrar to extrat the folder.. the question is, i dont know what to do know? just need the steps thats it.thanks in advance.

  • Sashank Narayan

    Nexus 10 images haven't been released yet

    • scuttlefield

      They are actually there, but not showing on the main page. Click on "Factory Images "mantaray" for Nexus 10". It's there.

      • Sashank Narayan

        Yes you're right. Thanks!

  • Andres Reyes

    Hey,

    I think I have done all the ways that can be possible to try to make the fastboot but it still giving me problems... I´ve read all the comments but I don´t know what´s wrong.

    I will post photos showing what cmd says...

    HELP PLEASE!

    • Spasillium

      Don't use the .bat file. Follow the steps here: http://forum.xda-developers.com/showthread.php?t=2010312

      • Andres Reyes

        Im trying to step-by-step and typing all the commands but still no effect at all.. :(

        • http://www.homysnetworks.com/ Mariusz Kraus

          try to copy all factory image files (6 files) to platform-tools folder and than start the file .bat. Of course go first in CMD to path /.../.../platform-tools/

        • http://blog.tonysarju.com/ Tony Sarju

          You need to run the commands from the platform-tools directory. You are running them from your home directory. Also, make sure to extract the files into platform-tools(it looks like you may have done so already) because I see you exploring the TAR file in the bottom left window.

  • Akera

    Might want to change "fastboot update image-razor-jss15j.zip." to reflect the current version zip. Might be confusing for some newcomers !

  • Stacey Liu

    God damn it Google! There's no transparency on the lock screen! That makes GEL look out of place.

    Completely unacceptable. /s.

    • mnajem

      i guess this is only for Nexus 5 firmware.. could be there's another update on this stock firmware?

  • philknall

    Tried flashing on my mako. Getting error "Device version-baseband is 'M9615A-CEFWAZM-2.0.1700.84'. Update requires 'M9615A-CEFWMAZM-2.0.1700.97'."
    Anyone else? How do I fix this?

    • philknall

      Nvm, renaming the baseband image to .97 and flashing it manually before doing the batch seems to have worked.

  • Ankit

    getting a error msg cannot load 'bootloader-tilapia-4.23.img'

    • Ankit

      Help Me Any one what to do now ... ihave nexus 7 2012 32gb 3G+WiFi

      • Bruno Marangoni

        Do you have an unlock bootloader?

  • Allan Michaels

    Installed on nexus 4. I'm not seeing transparent nav and menu bar. That was the most exciting thing about this update :(

    • FritoDorito

      The transparent nav and menu bar need to be called on by an app. The AOSP launcher doesn't support it. Try either the GEL Launcher or the new version of Nova and it will work.

  • mnajem

    finally got a working compass :) been using many variant of AOSP and port of KitKat .. but since the driver haven't been released...

    btw, what is the purpose of "binaries" - the BroadComm, Qualcomm and others? Are those for the XDA ROM ROM developers?

    since I already downloaded them but since I took a look at the flash-all.sh file nothing being mentioned on using these files. perhaps I just need to delete them sinceit's no use for end user like me

  • jackennils

    Am I the only one who can't find any 4.4 for the Nexus 10? o.O

  • Виктор Манчев

    Is this another sign that Google really wants to part ways with Samsung?

  • Kakashi Hatake

    after updating to KK i can't transfer my files from win8 only debugging is working

  • House
  • Ian

    I successfully updated my N4 using this method. I did the exact same thing to my N7 3G and it wiped the device :-(

  • dark0mlks

    i open the flash-all.bat and i reboot my phone into bootloader and a cmd pops up showing error cannot open "...."

    • Bruno Marangoni

      Were you in the Bootloader screen when you tried to flash-all?

  • http://bentheman96.com/ Ben Martin

    Is this factory image for the Nexus 7 (2012) different from the image from your earlier post? If it's the same, then I won't flash the factory, but if its different I may need to.
    There are some issues on the image I currently have.

    Please let me know :) Thanks

  • klyntone

    thank you for th clear instructions.

    i flashed th contents of occam-krt16o-factory-75ccae7a.tgz and everything is working excellently.

    do i also need to flash th binaries;
    (broadcom-mako-krt16o-fd7a4074.tgz, lge-mako-krt16o-388d2913.tgz and qcom-mako-krt16o-ea79ab66.tgz)

    or are they included in th factory image?

    • Bruno Marangoni

      I did it using the "flash-all" script inside the image and everything worked, including the drivers, because they are inside the .tgz file.

  • N

    Any ota.zip files yet?

    • N

      For the n4?

      • Nathan

        No.

  • ginobili

    Oh god.

    If you press in the link for Nexus 4 for Android 4.4 it show it at the first line of the screen and i didn't realize that and i was trying to flash all the time the factory image for Nexus 7...

    Thankfully i'm still at bootloader hahaha

  • hajime

    Please, can I flash these like any other custom ROMS? (currently running CM 10.2 on my Nexus 7 (2012, Wi-Fi)

  • hajime

    Please, can I flash these like any other custom ROM (currently running CM 10.2 on Nexus 7 2012 Wi-Fi). Thanks!

    • David Marion

      If you're talking about flashing it thought recovery mode, no you cannot. You need to follow the instructions in the article.

  • http://friskychatter.com/ _jsw_

    Successfully upgraded my Nexus 4 and 2013 Nexus N7 just now using these instructions (TWRP was already installed, and both were unlocked and rooted previously). The actual upgrade is very fast; optimizing the apps on the first boot takes some time (just mentioning it for those who wonder how long the process takes - moments for the upgrade, and an average a a second or two per app and some more time to upgrade databases).

  • John

    Still can't pull the OTA update on my 2013 WiFi Nexus 7. Aret they still staggering the release?

    • http://friskychatter.com/ _jsw_

      FWIW, my Nexus 4 and 2013 Nexus 7 both did not show the OTA update (prior to my manual update) even upon going into the settings and checking again.

    • Romeil

      Not yet on my Nexus 4

  • Gaja

    Is Nexus 4 getting translucent bars officialy?

    • Nathan

      Not yet, but it does have them if you install the GEL apk.

  • Dimis29

    Sorry to intervene but need help asap!
    How to perform #4 in "Instructions"?
    I have TWRP 2.6.3.1 installed, bootloader unlocked and stock 4.3. I am trying to update to KitKat, but cant. I tried via adb sideload and after installation is completed (100%) I get "failed" message in TWRP. Tried a flashable .zip and again "failed" message appears instantly. I tried to use this guide to revert to stock recovery but I cant perform #4 in "Instructions". Do I really need to revert to a stock recovery or can I use TWRP? Can anyone help me please?

  • noisejr

    HELP!!! fastboot is stopping after writing radio!!!!

    • riccardokennedy

      I had the same problem. I think it was because I was doing using Windows 7. Tried with the wife's laptop running Windows 8 and it worked a treat. It had me worried for a while tho.

  • lanzz

    Followed instructions, removed "-w" option, still got my data wiped. I'm blaming the "fastboot erase userdata" command included in the flash-all.sh script, which is not mentioned in this howto, and which I also missed while checking the contents of the script. Good thing I did a backup before flashing :)

    • lanzz

      Update: The above comment concerns the Nexus 7 (original) flash script. Apparently it is not universal — my Nexus 4 flash script did not contain any "fastboot erase" commands, and just removing the "-w" did the trick to preserve my data. Pay close attention to your flash scripts and look out for "fastboot erase userdata" commands which might be unexpectedly present there.

  • Nanda

    it displays fastboot.exe has stopped working? what to do

  • jaska

    If I need to unroot for warranty reason, is it possible?

  • Fredrol

    Hi, this might be a stupid n00b question, but what should i write to run the flash-all?

    Will this conpletly flash the whole 4.4 update?

    I prefere to do it on mac, but i have windows also avaleble.

    Thanks! :-)

  • Cro0707

    WTF is happening, why Google still didn't push any OTA update?!?

  • legaleagll

    Stuck in a bootloop after installing the factory image for Nexus 10. Tried both with the wipe and without. Everything appears to go fine with the fastboot commands and the system restarts, but gets stuck at the colored balls image. The image still moves, but never passes this step. Any suggestions.

    • Joakim Andersson

      How long is never? You might just be too impatient.

      • legaleagll

        You're right, never could be an overstatement, but it was still stuck after about an hour, so I don't think it was coming out. I reverted back to the 4.3 factory image and had the same issue. I did ultimately resolve the issue however but it required going into recovery mode and manually forcing a wipe of the data and cache to get it to stop boot looping.

  • Noé De Saint-Imphal

    It woked for me... put google just published a fix to 4.4 (KRT16S). How can we install that without wiping out everything again?

  • Mashá Ponce

    Hello, I unlocked and rooted my nexus7 v1 with wugfresh nexus utility and received the system update on the status bar today, yet when I tried applying the update, it failed. What do I have to do in order to install it? Just download the image of my version and flash it?

  • BossC

    Have I missed a step? I removed the -w from the relevant line and my userdata was still wiped!

    When I went back in I saw this line

    >> fastboot erase userdata

    which the article made no mention of...

  • inder

    My android dead after update is complete n show red triangle error.

  • dmyton

    my jwr66v won't update to jwr66y - can I jump to 4.4.2 or do I need to update to jwr66y, then 4.4, then 4.4.2?

  • http://www.augustasoftsol.com/ matthew

    its nice app .. but while instal i'm getting problems.. is there any steps ? or any other problems comes ?

  • Greg Hockenjos

    Just confirming Towelroot is unaffected by this update and worked like a charm!

  • Konstigt2

    Rooting does NOT require custom bootloader. I use Chainfire's SuperSU which I just flash according to instructions with the android sdk toolkit.

Quantcast