More Reading

Post navigation

133 Comments

  • So I got the ota in the morning (KRT16s). I’ve read on other forums that this update is pushed after the users are already on Android 4.4. But I went from 4.3 to this update. Forgive me for sounding like an idiot but is this normal?

  • so i downloaded this ne version and i can’t believe what they di the keyboard changed I can’t sign on wht the heck happened/

  • I just got the KRT16S via OTA without getting KRT16O. Is that it? Should I still need the older version? I’m from the Philippines btw.

  • In Chicago and I literally JUST got the OTA for my Nexus 7 outta no where!!!! It’s been weeks and I’m been waiting and waiting and guys it IS HERE!!!! 4:35pm in Chicago IL…totally stock Nexus 7 2013 got the 4.4 OTA now.

  • That’s just weird. Today, my patience finally broke down and I sideloaded 4.4 on my 2012 Nexus 7, and the very moment I booted, I had this bugfix update waiting for me. Something is definitely screwy about the 4.4 OTA–maybe Google pulled the original and plans to push this one out to everyone now.

  • Great job Google, lets get to the next build ready before you ever update my Nexus 7 to the first one. It’s a really sad day when the moto x is getting updates before a nexus does.

  • For any Nexus 7 (2013) owners I will report that if you are rooted on KitKat 4.4 KRT16O and take this OTA update KRT16S then you will likely lose root in the process as I did this morning. Using Wug’s Nexus Root Toolkit which has been updated allowed me to re-root without an issue. No other issues to report and root is up and running fully functional on KRT16S now.

        • I have tried to sideload but 1) getting that key combo to be able to select ADB and then 2) having the device not found when I tried the sideload command.

  • I know the ones that haven’t got it yet are the most vocal, but I have sifted through tons of comments related to this update and have not yet seen one person say they have got KitKat on either gen Nexus 7. Has ANYONE that reads this site got it for theirs at all yet?

      • I checked every comment in this thread and went to two other sites that ran the story. Not even one person has posted about having got 4.4 OTA on either gen Nexus 7 yet except side loading it. I assume the original update was pulled so they could do these fixes. Hopefully a more mass roll out will ensue now.

  • I side loaded the 4.4 update two days ago on my N7 (2013), and had this update waiting to download OTA this morning. Seems to have fixed a lag bug I was experiencing in HangOuts! So far so good! If you a complaining about not having the OTA yet, just sideload it. It really is VERY easy to do. My N7 is stock not rooted.

  • I’m waiting for the 4.4 updates as well for my N7 2012, and N 7 2013 … Been checking everyday. If I don’t get it in the next few days I will be side loading the OTA

  • I sideloaded the update on my 2012 Nexus 7 last week but in the early hours of this morning (12:40am) here in the UK, I got the notification telling me there is a 1.4MB update to install. So I’d imagine that the KRT16O update was silently pulled and the KRT16S build we’re seeing now is what was intended to go out last week before bugs were found.

  • I picked up my n7 2013 late last night and found this little update waiting for me. On reboot, it asked me to pick a backup account. Not sure what that was about

  • I actually received the bug fix update this morning on my Nexus 7 (2012). I live in Germany. However, I did sideload the 4.4 update before.

  • I have a Nexus 7 (2012) and still have not got 4.4, so what is the point of a bug fix OTA update?

  • From what I can tell, very few, if any, have actually received the ota of 4.4 on their n7 2013’s and now there’s a bug fix for it? Does the bug fix fix not getting it?

  • Will I get prompted to install KRT16S if I did not get KRT16O since I am still on stock 4.3.1 JSS15Q ? It seems the only people who are getting prompted to get KRT16S are the ones who annually installed KRT16O via the OTA link or the factory images.

  • Does this mean that when get eventually get 4.4 we will get this version and not have to update again?

  • Instead of letting users know about having issues with the KRT16O and having to pull the update the leave us wondering like a dear in the headlights and forcing some people to install KRT16O manually which would still introduce the bugs from the factory images they silently pull the OTA update and now are releasing KRT16S. I wonder if this also affects the version that the Moto X got ? or is that based on an entirely different build ?

  • I’d rather have a smooth update than a rushed rollout provided the update still comes within a reasonable time frame (no longer than a month). Personally I usually wait a few days after the OTA rolls out before I update to see if there are issues anyway so I can wait.

  • I got the “new” kit kat update. I manually pushed the initial 4.4 kit-kat, and about an hour ago or so I got this small update.

  • I have a Nexus 2013 16 gig and did the sideload for 4.4 and had some issues doing it. The driver wouldn’t recognize so I had to use PDAtalk to force the drivers to work. I installed the Google Experience adk and such afterwords and that worked fine. I just got the KRT16S update and that seems fine as well. So, no complaints here.

  • The latest update it complete CRAP! It updated the Location settings.
    Basically, unless you agree to have Google collect “anonymous location
    data” even when apps aren’t requesting your location data…you are
    FORCED to ONLY use GPS location now. You cannot use Wi-Fi location
    finding if you DISAGREE to allowing Google Location Data! WOW.
    Complete crap.

    • How do you think using WiFi for location has always worked? It has always checked in with Google for the coordinates of the WiFi around you.

  • I had side loaded the original 4.4 update on my 2013 n7 and I got the new build as an OTA a couple hours ago

  • Still no first version of 4.4 on a 2013 N7. Hell, I never got Hangouts 2.0 on my Galaxy Nexus until I side loaded it. This staged rollout BS is the pits.

  • I sideloaded 4.4 onto my 7 (2013), but tonight (11/19) at around 8:30pm I got the official OTA update notice.

  • my nexus 4 is rooted with stock android 4.4 krt16o. i want to know if i can update with my phone still rooted. if i lose the root will i be able to root it again?

  • I had sideloaded 4.4 on my N7 last week and just installed the latest small update. Now my auto rotate doesn’t seem to be functioning. Anyone else have this issue?

        • Strangely enough, booting in safe mode, and seeing auto rotate work, and then rebooting fixed it. It’s what fixed it the first time too.

  • I sideloaded the original 4.4 build on my Nexus 7 2012 and I received the newest build through OTA upon checking for software update right now. 1.4MB in size.

  • Its hard to follow some of the comments when they say “I got it” on this article. To be clear, has anyone received a full 4.4 OTA update on either nexus 7? I’ve got both and haven’t received any updates on either one.

  • I’ve a N7(2012), updated to 4.4 manually using a captured OTA image. I just got prompted for updates, rebooted and checked = I’m on KRT16S. Fun.

  • OK, so I just did this on my 2012 N7. I had installed 4.4 manually last week. I had installed the new launcher from the N5 .apk last week. This update removed the home options in the settings and it looks like it won’t offer me the option to use the new launcher.

    EDIT: It did let me reinstall the new launcher and it’s working again.

  • Just checked for updates on my 2013 N7 and got the OTA immediately.

    note: I had flashed the 4.4 image when it became available.

  • Just got the OTA notification on my N7 2012 after manually updating to 4.4 last week. Haven’t accepted yet, going to backup everything first.

      • I’ve had multiple devices rendered non-functional by ‘routine’ OTAs so forgive me for taking basic precautions. In my experience “It wasn’t supposed to do that” doesn’t quite make it all better after it actually does ‘do that’.

    • Same here. Flashed the 4.4 factory image last week and received the newest update via OTA tonight. I didn’t do a backup, but there’s never any harm in doing so. Ask any iPhone users who updated to iOS7 and lost all their contacts!

    • This may have nothing to do with the N5. If we see them drop a new N5 image we should expect to see an OTA soon for it.

  • I got it on my 2013 N7, only thing I’ve noticed is that it prompted me to set a backup account.

  • This probably explains the painfully slow roll out. They must have silently pulled the update a few days ago to make the fixes.

  • Anyone else have a N7(2012) and not have 4.4 yet? I thought it was out. Maybe I’m completely wrong though.

    • Count me times 2, mine & my mom’s. It’s nice to see I’m not the only one. Well, not nice, I wish we all had it, obviously.

    • i never got it officially. thankfully droid loife had a guide on how to sideload it! very easy!

      • Nothing for my N7 2012 model yet, usually i get the update with in 1-3 days after they release it.

        • If we don’t even have 4.4 for our 2012’s N7 how are we going to get the bug patch? This is the longest OS rollout after release I have ever seen on a device I have owned.

        • That’s weird. I got 4.4 update a week ago and then was pleasantly surprised when I woke up my device last night and had another update.

      • I updated to 4.4 first by doing adb sideload. I also used this toolkit: http://forum.xda-developers.com/showthread.php?t=1766475 just incase things went wrong. In the first place, I was rooted, so I clicked unroot and you can select any of the stock updates from google such as 4.4 and earlier. After I used this ‘unroot’ tool back to stock (you can also use unroot again to flash a different stock rom), I just flashed the first Kitkat update, which is google’s default image, and then the next day, I saw Google’s latest bug fix update (KRT16s) become available in the system update bit in settings. This way I explained is probably the best way to skip waiting for the notification to popup saying 4.4 is available for download. This tool works with all nexus devices by the way 🙂

      • I don’t want to root my Nexus 7. I don’t plan on ever doing so. I rooted my Galaxy Nexus because it was needed to avoid Verizon’s tyrannical wrath, and I have fun poking around with my phones, but my N7 is a consumption device and I don’t really need more than a bunch of games, Netflix + HBO Go, and Google Play books and music.

        I’m pretty furious about still not getting Kit Kat in principle as I did buy a Nexus and the update was supposed to happen a week ago, but honestly I’m liking Kit Kat less and less every day. There’s almost nothing appealing about the update, especially on an N7 which won’t get the google launcher.

        • Well Wugfresh’s Nexus Root Toolkit should just be named Nexus Toolkit.. no need to root to sideload.. unlocked bootloader yes but thats the first thing you do with a nexus..

        • You don’t need to root to sideload the OTA or flash factory images. Don’t be mad as the update did happen a week ago. You have decided to wait for it to be installed for you instead of just getting it yourself. Google said updates would be available for Nexus devices first which is what happened.

          The N7 will get the GE Launcher at some point through the playstore.

        • My n7 2012 is stock unrooted and I just used adb to get kitkat. And GEL actually works great on it. All I did was install the apk after installing kk and it is good. The launcher is really just part of Google search, I think the apk just unlocks it somehow.

          • Not a fair comment anymore. Nexus devices used to be meant for the developer community, and back then I’d agree loading a factory image for yourself was perfectly reasonable. Personally I loaded the image on my three Nexus devices as soon as it came out.

            That isn’t the case anymore. These days it’s obvious that Google has decided to target these to the average consumer by distributing them through carriers and big box stores, so it should be on Google to release the OTA updates to all devices at the same time. A user shouldn’t have to wait forever to get an OTA update if that is their desired way of getting it. And for the record, unless you unlocked the bootloader right when you got the device, it does do a data wipe so it may not be an option for the user.

          • Waaaa…what’s the rush then if you are just “a regular user”? What KILLER featuere MUST you have NOW.

            Its not a factory image, it doesn’t wipe – it is an update file POSTED HERE days ago, mister casual can’t be bothered with a 5 minute adb. Device doesn’t need to be unlocked either. Try again lazy. The iPad is always there for you if you aren’t being properly coddled.

          • Did I say I was a regular user? No, you assumed it, and you made a wrong assumption. I also didn’t say the factory image wipes the device. Removing the -w from the fastboot command ensure it doesn’t.

            What I did say is that unlocking the bootloader DOES wipe it, so if you didn’t do that on day one, which most average users wouldn’t have, the potential for data loss exists.

            What I also said was that with Google changing their target audience for Nexus devices from developers (and enthusiasts by extension) to the average consumer, then they also need to change the way (and timeliness) of how they deliver updates. It doesn’t matter how easy or how much time it takes to do-it-yourself.

            If you’re such a hardcore enthusiast, maybe you should strip out the GUI and go old school command line. After all it’s pretty simple, or maybe you can go buy an iPad yourself.

          • If you take two extra seconds to look at the CONTEXT of my post, you’ll see I’m replying directly to a guy who suggested Nexus 7 owners root their devices. I’m perfectly aware of adb, ever since I used it to root my OG Droid 4 years ago.

            If you read my own post, you’ll see I’m mostly upset about the lack of an update on principle. I don’t really want Kit Kat.

    • Glad to hear(well not glad but you know what I mean) that its not just me. I hope Google does a mass roll-out soon. It’s crazy that the Moto X on Verizon has KitKat before a Nexus does!!!

      Edit: And I saw the tool kit. Personally, I would rather wait for the OTA. But that’s an awesome option for those who want it!

      • don’t hold your breath on it i still do not have the kit kat update. This roll out has really open my eyes on how goggle really sucks and how apple really like their users by pushing their updates to all devices day one

        • Just imagine if something unexpected was caught after a “huge” rollout. Android would have lots of unhappy users. Instead, they will have users salivating with anticipation and will get a good-to-go update at the guinea pig-expense of a few 😀

        • Yeah all the iPhone users LOVED that last year when their maps were horrible. Misery loves company I guess…

          Google published the update so if you were IMPATIENT you could simply side load… they totally suck!!!

      • I have two Nexus7 2013 one being my uncles and one being mine. Neither have been able to receive the OTA update.

    • I have both 2012 and 2013 and nothing. I just posted something on google nexus 7 owners community…

    • Two Nexus7 2013 one being my uncles and one being mine. Neither have been able to receive the OTA update.

    • The factory image is up. I just downloaded it and used adb sideload. That is for my stock unrooted 2012 n7.

    • I flashed it manually on the 2012, no issues. And this morning received this new bug fix update OTA.

  • So, is this why the 4.4 OTA has been held up? I know 8 people with a N7 2013 and none have received OTA, I also haven’t seen anyone online who have received OTA, just flashed it.

Comments are closed.

Related Posts

back to top