The Android 4.4.3 rollout is in full swing, with the 2013 Wi-Fi Nexus 7 getting its OTA early this morning and a bunch of flavors of GPE devices and various Motos receiving theirs just a few hours ago. Nexus 5 owners with locked bootloaders even started feeling a bit snubbed waiting for their OTA to arrive, but they can now breathe with ease - not only has the OTA indeed begun, but we have the download link and manual flashing instructions right here.

Update: In case you're wondering, Sprint says the Nexus 5 4.4.3 OTA is rolling out in batches until 6/9/14, meaning it should be under a week until it's out for everyone via natural means.

Note: You have to be on Android 4.4.2 (KOT49H) for this OTA to succeed.

Download: signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip

File size: 92.2MB

MD5: 934dfe0f2660fa3208067c122cf7626c

If you're not familiar with the manual installation process, proceed to this guide for an earlier update, and you'll be set up with Android 4.4.3 in no time. Happy flashing!

What's new: To get a better idea of what's new in Android 4.4.3, hit up this post and check out the updated Dialer.


Thanks, Steve Secor, Caner Kamburoğlu, David Juarez, lulzer, and everyone else!

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.

  • lulzer

    Unfair, I posted the link :S, here and on xda

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

      Gave you a shout too.

      • lulzer

        fair, thanks!

    • Simon Belmont

      Thanks. I actually used your link about an hour ago.

      You helped me, man. Yay.

    • http://www.facebook.com/lucyparanormal Daniel Tiberius

      Thank you lulzer!

  • darkdude1

    About time :).

  • Roberto Giunta


    • Guest

      Because DISQUS didn't let me post a GIF but said it was attached...

      • Simon Belmont
      • Brenda Robert


        ❦❦❦ �❦❦❦ ❦❦❦ ❦❦❦ ❦❦❦ �❦❦❦

  • rale

    Wait. Does this mean that the 4.4.3 OTA for the Nexus 5 started rolling out ?

    • Steve Secor


  • Sam Del Valle


  • Camiel Hirschberg

    Wraaaah! Finally !!!

  • ClarkDV


    • bozzykid

      If you are a Nexus 5 Sprint owner, then it is more than an incremental update.

      • lljktechnogeek

        Why is that? As far as I'm aware, the only difference between the Sprint Nexus 5, the T-Mobile Nexus 5, and the Google Play Nexus 5 is what carrier (if any) it's locked to.

        • Andrew

          I believe 4.4.3 enables support for tri-band LTE on Sprint (aka Sprint Spark)

  • Crispin Swickard

    March build date? Wow. they were dogfooding that thing for a while. Side loading will commence soon as I get home...

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

      Indeed. KTU84M is Android 4.4/KitKat, dated at approximately March 25, 2014.


      • darkdude1

        I wonder what the few months delay was for then...:s

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

          QAing, testing and re-testing, and dogfooding.

        • Ibrahim Yusuf

          waiting to drop it on the same day as WWDC, maybe?

      • Sascha Prüter

        That's misleading. KTU84 was cut on March 25th but it gives no indication on when the subsequent B/C/D/E ... L/M builds got cut. These subsequent builds are usually called on-demand and only contain handpicked changes so you cannot assign a date with a calculator to it :)

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

          I suppose you're right.

          Finally, the last letter identifies individual versions related to the same date code, sequentially starting with A; A is actually implicit and usually omitted for brevity.

          The date code is not guaranteed to be the exact date at which a build was made, and it is common that minor variations added to an existing build re-use the same date code as that existing build.

          So if a small component was giving them trouble, they could have kept the same base build and fixing some .so or whatever the problem was, though I didn't think it could take months for such a freeze without advancing to the next build calculated from the actual date.

          • Sascha Prüter

            You can e.g. see that KTU84L was cut on May 1st:

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

            Well, that's when it was committed. Who knows when it was actually bundled and finalized.

          • Sascha Prüter

            This is actually the timestamp from the buildserver when the build (with the hand-selected changes) got kicked off. So while the individual changes might have gotten submitted into the dev branch earlier, this is the timestamp they got picked & "bundled" into a build (KTU84L in this case).

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

            Thanks for the extra info, Sascha. If someone knows about this, it's you ( https://www.linkedin.com/pub/sascha-pr%C3%BCter/1/115/904 ) . Stop by more often :-]

          • Crispin Swickard

            Mystery solved. Teamwork!. :)

  • Dean Politis

    Is there anyway to force the update? The way I used to force the refresh, by going into Settsings->Apps->All and clear the cache of the Google Services Framework, is discourage by Google because it could mess you up (it did do that to me once).

    • Sir_Brizz

      There is no way to force the OTA.

      • Dean Politis

        Not even checkin through the phone dialer?

        • Mateusz Cichon

          In short: no - Google is caching your deviceId until next rollout stage and you can't force it to give you that file in any way other then creating new deviceId (small TODO: study Google's checkin methods and create simple program which will register new Android device to your account and then check for OTA)

          In long - yes - You can study Google's communications mechanisms by Reverse Enginnereing them and then you can create fake DNS server which will tell your Android that domain android.clients.google.com is on your server. From that, you can send any file you want - device will save it and reboot to recovery which will check it and eventually use patches to upgrade your device. So as you can see, you've to first have access to OTA file from Google. Filename of that file can be spotted by someone or cracked up, although it'll take some time to do it. Filename syntax is: [EDIT: can't post syntax here because it's getting messed up so here's link to pastebin: https://pastebin.com/ES4N7hri

    • Simon Belmont

      Yes. Download the OTA linked above, install the Android SDK, and then go into recovery mode on your N5, and do an "adb sideload from a command prompt on your computer.

      Sorry, if that sounds smartassed, but I just did it and it was easy. Give it a shot and you'll feel powerful.

    • remister

      I think the only way to "force" an update is through time and patience. All others are placebos :P

    • lulzer

      It does work whatever they say (Always used it on my N7). After the trick is done, just delete and re-add your google acocunt (thats the only thing that gets broken temporally) and done.

    • Rod

      I sideloaded using ADB.

      My first time doing this, but it's quite simple.

      Just download the "Minimal ADB and Fastboot" program from XDA, no need to get the whole Android SDK.

  • Mizzo


  • Peter

    New updated casting icon when using Miracast.

    • Simon Belmont

      Did they add the fabled casting of your screen (mirroring) to Chromecast? That would be sweet.

      I haven't had time to test anything yet. I will soon.

      • Peter

        Unfortunately not.

        • Simon Belmont

          Yeah. Confirmed.

          I just did a quick check and nothing. Hopefully in Android 4.5 / 5.0 later this month.

          • Peter

            I think it would most likely be an update required on the Chromecast itself rather than Android. Android already supports screen mirroring. I use a Netgear PTV3000 for Miracast, but it's a bit hit and miss.

            On a related note, my Chromecast just updated firmware yesterday to 17250.

          • Simon Belmont

            Yeah, Android does already support screen mirroring using Miracast. Has since Android 4.2.

            But that's using a different transport protocol than what would happen with Chromecast. Chromecast would probably use WebRTC or something to mirror your screen. But, I agree, it probably needs an update on both ends. No argument there, and I'm sure Google Play Services already has the update in place to make that happen on Android's end.

    • Kurt Schultz

      All the options are there in Settings -> Display -> Cast screen, but when I hit the button to cast to my living room, it says "Casting screen to Living Room has failed.

  • Matthew Toomey

    Disable or uninstall Xposed installer and mods?

    • xnadax

      Uninstall the Xposed framework from the Installer (but no need to uninstall the Installer itself or any modules).

      • Matthew Toomey

        Thanks. I'm pretty sure ^ this is the right (most stable) answer.

    • Chris

      About to install it over xposed. I'll let you know how it goes. More then likely, Xposed will be written over.

      • asda

        good luck with that

      • yankeesusa

        Just make sure that you uninstall within the app.

    • ltredbeard

      I'm pretty sure it wouldn't install over Xposed even if you tried

      • yankeesusa

        I did the 4.4.3 zip ota and all i did was uninstall xposed from WITHIN the app. Left everything in tact. It worked flawlessly. After update I reinstalled xposed and all my modules still worked like before.

        • ltredbeard

          I did the same. Turns out there was a problem with my boot partition (maybe I didn't update it last time???). Updated without a problem once I reflashed the 4.4.2 boot img.

  • Simon Belmont

    Just sideloaded via ADB about 45 minutes ago. Feels good, man.

    I'm gonna let it settle down and then check it out later. Anyone else notice that the multitasking animation (shrinking/expanding) feels like it has a slight hesitation now?

    • Peter

      I haven't noticed it on my N5.

      • Simon Belmont

        I checked again and it seems like it's better now. Might have just been because I'd just rebooted and stuff was loading.

        Also, my phone was really hot (105 F), after doing all the installation and because it's really hot in my house at the moment. I think the CPU/GPU was downclocked perhaps due to thermal throttling, but it's cooling off now.

        • yankeesusa

          Yea, it will get hot because after the update the apps have to update also and the screen stays on with the highest brightness for some reason.

  • Churchill

    fk you Google

    • polesmoker99

      fk you Yahoo

      • Sean Thomas

        fk you AltaVista

        • Simon Belmont

          Fk you HotBot. Fk you Dogpile.

          Fk you Metacrawler. Fk you (insert old-timey search engine).

  • Hillal Lozi

    i have a custom recovery on my n5, if i flash the zip will i lose root or my data?

    • xnadax

      You won't lose your data. You might lose root, but just flash the SuperSU zip right after the OTA, and all will be fine.

    • yankeesusa

      You won't loose data and you won't lose root if you have supersu installed and use the ota keeper update within the app. I did it last night and root was intact after update.

  • DarxideGarrison

    the update was aborted. not sure if its because its rooted or xposed framework has anything to do with. it is running the stock rom.

    • bunnybash

      it's xposed that is tripping you up

    • yankeesusa

      Make sure xposed is uninstalled within the app itself or flash the xposed disabler. I think its exactly like bunnybash said.

      • DarxideGarrison

        I ended up doing a factory reset and then flashed with Nexus Root toolkit!

  • Rod

    Just sideloaded. Works like a charm.

  • Josh Jacobi

    when I type in cmd prompt "adb sideload file name" it says cant read file name? I downloaded the zip file and adb is working, I dont know what I'm missing. I didnt have this problem with 4.4.1 or 4.4.2. Please help

    • anon


      adb sideload d173d546ab2347ead90cb0978657f11046300511.signed-hammerhead-KTU84M-from-KOT49H.d173d546.zip

      • Josh Jacobi

        haha yup thanks. Forgot the .zip

      • Tom Harman

        not working for me, not sure what the heck.

    • Rod

      Or rename to the file to A.zip and you're set.

  • https://play.google.com/store/apps/developer?id=iWizard Bikram Agarwal

    Sharing my update experience for the benefit of anyone else going through the same.

    * I downloaded the OTA zip to my device. Uninstalled xposed frameowrk and booted into recovery.
    * Made a nandroid backup. Then tried to flash the zip.
    * It gave an error that GenieWidget.apk has unexpected content. I rebooted and restored "News and Weather" app via TiBu.
    * Next flash attempt complained about GenieWidget.odex. I had to download 4.4.2 factory image and extract the GenieWidget apk and odex from it using the ext4 unpacker tool and adb push them to /system/app.
    * The flash attempt kept complaining about one or the other file and I kept extracting those files from the 4.4.2 factory image and adb push them to my device, until..
    * it complained about "EMMC: /dev/block/platform"... something. Didn't find this in the factory image.

    At this point, I gave up hope of flashing the ota and followed instructions from here - http://www.reddit.com/r/Nexus5/comments/2771cq/install_443_ota_for_rooted_users/chyf1no

    I'm now rocking the 4.4.3

    Hope this helps someone in need.

    • Calipsort

      Thanks, I too faced issues with OTA installation with Xposed uninstalled. Gonna install the factory image.

      • https://play.google.com/store/apps/developer?id=iWizard Bikram Agarwal

        Don't forget to delete the -w flag from the bat file; otherwise it will wipe your device clean.

    • Had Enough With the BS

      the notification screen states specifically that it recommended to download the update via WiFi. Worked for me and worked fast. Also left Xposed intact; no uninstall necessary.

  • Hammad Nadeem

    Does it work with nexus 4 ...?? Because I have the same build number..!! Please help me out..

    • Kurt Schultz

      No, this is for the nexus 5

  • Boba F

    Still getting the goddamn data drops when on WiFi and LTE.

    • yankeesusa

      Who is your service provider?

      • Simon Belmont

        If it's T-Mobile, then that's the key. I got my first data drop out this morning post Android 4.4.3 update (I updated last night).

        I do notice better reception overall, though. Maybe it was a fluke.

        • yankeesusa

          Exactly, except I was going to say to get a new sim card. I did and redid my mobile network selection with data not enabled then re enabled it and no longer have data drops.

          • Simon Belmont

            Weird. My SIM card is less than a year old, so it would be odd if that was the problem.

            I'll try redoing the network selection, though, like you did. My data drops seem to be very random. I could go for weeks without a single drop out, but then have a day where it drops 3-4 times in the span of twenty minutes (also, apparently, T-Mobile is working on the LTE towers around here adding 20+20, so that could be the culprit, too). I assume by redo, you mean just select the network in the mobile network settings in Settings?

          • yankeesusa

            Sim card swap is the first thing I recommend. Most T-Mobile stores will swap them for free and even though it's less then a year sim cards can go bad, it's rare but they can. And yes, mobile networks within settings.

          • yankeesusa

            I just had a data drop yesterday. So it looks like the issue came back for me. Oh well.

        • Boba F

          Yes Im on T-mobile but it has something to do with the WiFi I think. When on LTE alone I never lose connection.

          • Simon Belmont

            I lose connection on LTE alone. So, that's not the problem (for me at least).

            On Wi-Fi I've never lost connection. Sounds like we're opposites.

  • Idan Yael

    The downloaded file has a different md5 and when uploaded to the device it can't verify the signature. Installation aborted. Tried re-downloading 3 times, same thing.

    • David K.

      Same problem for me: When I try to install using TWRP I get the error message "Zip signature verification failed."

      When I uncheck the Zip file signature verification Verifying current system aborts with "/system/bin/surfaceflinger" has unexpected contents.

      As far as I can remember my N5 runs a stock KOT49H that came with the Nexus Root Toolkit. No frameworks installed or changes applied. Any ideas on the unexpected contents? Thanks in advance.

      • coolscrotie

        Ever tried Franco kernel? This fucked up my system when 4.4.2 was released. Had to delete 2 files...

        • David K.

          Thanks for the hint. However, I've never tried Franco kernel. I'm not sure (and can't prove anymore), but my problem might be caused by remnants of Chainfire's [root] CF.lumen I played around once.

          I've flashed the 4.4.3 factory image, applied a backup and everything's just fine.

          • ReyMaxwin

            I disabled cf lumen and xposed but now it complains about my buildprop being different... Figures. No idea how to restore.

    • yankeesusa

      This means you have some file that has affected some system file, like xposed. It all needs to be disabled and all files returned to stock. The only issue is figuring out exactly what files are doing this.

  • Guest

    And still no sign of the OTA Zip for Nexus 4... :/

  • Raphaëll

    One question. Do I have to be rooted for this?

    • Tom Harman

      No sir, I'm not, but I had to use wug fresh nexus root toolkit to get the sideload to work, for some reason it would not for me with just using cmd prompt, kept getting a can't read error from adb, but finally got it done without root or having to have the bootloader unlocked.

      • Google_Is_The_Higgs_Boson

        What happens if you are rooted... Will the OTA work?...

        • Simon Belmont

          Yes. It will likely require you to reinstall SuperSU or whatever root permission app you use, though, afterwards.

          If you're using XPOSED, then you'd probably want to uninstall modules first. They'd be wiped out otherwise, I think.

          • Google_Is_The_Higgs_Boson

            Thank you...

        • yankeesusa

          You can just disable/uninstall frameworks from within the xposed app. After disabling within the app you can even leave xposed installed and ota will work. I used supersu "survival mode" to keep root after update. Then I reinstalled frameworks within the xposed app and all my modules were still in tact

  • Tom Harman

    found a new feature this morning to the 4.4.3 update, texting going to wrong person, wow that was a not so good thing to discover. i sent a message to my wife, and someone else responded back in a completely different text convo! WTF Google.

    • Dan

      Holy shit.

    • Simon Belmont

      Wow. That sounds like an issue that Google fixed in Android YEARS ago.

      I believe it was in FroYo or Gingerbread. People would get sent messages from the wrong thread.

      • Tom Harman

        yeah i remember that back then as well.

  • http://artigosparaprogramacao.blogspot.com Mateus Marquezini

    Hey people! Does it work in the Nexus 4 ???????

    • Tom Harman

      This zip does not!

  • Google_Is_The_Higgs_Boson

    I'll wait for it to hit my Nexus 5 officially...

    • Simon Belmont

      It really is easy to do it via ADB. Literally as simple as one command line while connected to your Nexus 5 awaiting an ADB upload.

      It took me 10 minutes from beginning to end. But, I understand if you're more comfortable waiting for it to automatically download.

      • Google_Is_The_Higgs_Boson

        I've done this before with my old GS2 Epic... Updating it to ICS and then JB... I had no problems with it... But I just want to wait... Make it a ceremony...lol

        • Simon Belmont

          Yeah. More often than not, I usually wait, too.

          I was just excited about a bunch of fixes for my N5 that I'd been looking forward to this time, so I took the plunge. I'm glad you're familiar with the manual process, though. That's a step a head of a lot of folks. Haha.

          • Google_Is_The_Higgs_Boson

            With my GS2 I was already waiting months... So I jumped in as soon as I could... Lol with my N5 i'm savoring it... I have my candles and Android shrine all ready for the OTA...lol

          • Simon Belmont

            Hahaha. I bet you'll be in full swing at your shrine come later this month when Android 4.5 / 5.0 drops.

            I might have to build a shrine for that occasion, too. Cheers.

          • Google_Is_The_Higgs_Boson


          • Google_Is_The_Higgs_Boson

            I'm just wondering why they took so long to roll out 4.4.3... Being close to I/O I'm surprised they did it at all with 4.5 or 5.0 coming...

      • Blake Guy

        i keep getting a cant read sideload error....

  • Simon Belmont

    Just got my first data drop out post Android 4.4.3 update (updated last night). It was on T-Mobile LTE (not sure if that matters).

    I have, however, notice better signal strength with the updated radio contained in Android 4.4.3. It's definitely a stronger signal and throughput seems very good. I'm still letting this update settle in before making any snap judgments. Battery life seems a tad LOWER than Android 4.4.2, but that could just be post-update shenanigans. We'll see. My two cents.

    • Tom

      I'm still getting data drops when on Wifi and LTE. This is ridiculous. BTW, do you happen to have one of the 1st-produced models that begin with serial number 310K? That's what I have. I checked with a friend who has a newer revision (311K) and he's never had this problem.

      • Simon Belmont

        Yeah. I bought my N5 within 30 seconds of it becoming available, so it's likely a first-run model.

        I wonder if it might have something to do with the SIM card tray. The original models protruded from the side of the N5 a bit (though mine actually doesn't suffer from this), and maybe it's getting jostled around.

        • Tom

          Hmm, my sim card tray is flush with the side but I have received random 'no sim' errors in the past...and I had to reboot for it to get service back. Maybe this is something specific to our 1st-run models? Do you think we can just exchange it for a newer model?

          • Simon Belmont

            Yeah. I never got "no SIM" errors either, which is what makes me believe it's probably not my SIM card (or the tray), that someone suggested below. I'm beginning to think it's just T-Mobile. I NEVER used to have data drop outs the first few months of ownership of my N5, and then it just started happening happening about 3-4 months ago (T-Mobile has been working on the LTE towers in my area lately, so that could be a cause).

            As for exchanging it, you probably could. I always worry about exchanging a device and then getting a new one that has worse problems or doesn't fix the problem I originally exchanged it for. I've seen that happen to a bunch of people. They end up exchanging multiple times and just getting more and more frustrated.

          • Tom

            Yeah I'm already frustrated that I waited since December for them to fix this and they still haven't. I'm considering either selling it for what I can get or doing an RMA exchange.

      • jjrudey

        I checked mine and I have 311K but still experience data drops on Straight Talk. It seems to happen more often when I don't have a strong signal.

    • yankeesusa

      yep, I got my first data drop yesterday too on the way home. I picked up my phone and voila, no signal at all, then after a minute it came back. That really sucks. I'm on tmobile also

  • beermksa
  • SpiderDice

    I can't get into fastboot mode. I can enter the recovery mode with the little android and the exclamation point, but when I click on Power + Vol Up, nothing happens. Help!

    • Simon Belmont

      Yeah. Hold power, then press Vol Up.

      Don't do it all at once. You literally have to be holding power first, then hit Vol Up.

      • SpiderDice

        Perfect! That worked. You really have to hit the combination the same as you did to get into Recovery Mode.

  • Serge Cebrian

    ha.. placebo effect ... i thought i updated optimized apps at restart,, but my version is still on 4.4.2

    i updated via twrp .. so i dont know if it failed or succeeded or (failed while said succeeded)


    • Serge Cebrian

      reflashed recovery sideloaded update... now restarting optimizing again.. :)
      i should be on 4.4.3.now

      lets see if root survival made root survive

  • JordanMcRae
  • Paito Anderson
  • Laurențiu Selei

    Just got the update. I prefer the black dialer, it looks better

  • TechLust

    Is it strange to get 4.4.3 update notification while running CM 11 (M6)? I just got that on my N5.

  • Neel Neeraj

    i tried installing the zip using CWM but it always gives me a error saying status 7 error installation aborted. i have already uninstalled Xposed.

    • yankeesusa

      Did you disable xposed frameworks within the app itself before uninstalling? You have to go into xposed then into frameworks section and uninstall. After uninstalling you can even leave the app in there and still do the update and it will work just fine. What you can do now is install xposed again, disable it and remove it if you want or just leave it. I left mine and after update I reinstalled frameworks within the app and all my modules were still good and active. Good luck

  • tex blues

    Nexus 4 OTA received today - Now getting Exchange services stopped working anytime I reply or send an email using my ActiveSync account on the phone. Have shut down and restarted several times but still have the same issue.

  • ineptone

    Tried to flash this via TWRP several times and continually get a failure. It simply states there's no MD5 detected and zip can't be verified. There's no other info provided as far as what might be creating the issue. Any advice? I'm running stock kernel with a few Xposed modules, the N5 sound booster mod, and that's it.

  • Fellwalker

    It has wrecked my battery life. If you read around, that is a common complaint and Google blame incompatible apps! Had to recharge at lunchtime, after it nearly burned a hole in my leg whatever it was doing (screen off, no apps running that I know of). It has also broken my rSAP bluetooth connection to my inbuilt car hands free. Every update I've had from Google has broken something.