11
Dec
image

No sooner than we got 4.4.1 with camera fixes galore, 4.4.2 started hitting Nexus devices. While most should have already received the update, factory images are now available for download directly from Google. They're not alone in this rollout, as the binaries are also available if you need that sort of thing.

image

Hit the links below to grab the downloads.

Factory Images for Nexus Devices, Binaries for Nexus Devices

Cameron Summerson
Cameron is a self-made geek, Android enthusiast, horror movie fanatic, musician, and cyclist. When he's not pounding keys here at AP, you can find him spending time with his wife and kids, plucking away on the 6-string, spinning on the streets, or watching The Texas Chainsaw Massacre on repeat.

  • naysayer

    Why the jab against us GNex users? *angry* ;-)

    • Sam

      Because TI, the people who made your OMAP processor, exited the business and isn't providing any support for the OMAP. No support, so no new binary. And besides, it's been like 2 and a half years since release of the GNex.

      • naysayer

        That's actually wrong. TI did post new binaries and Google still uses the chip. You do not simply exit a business "just like that". TI still has obligations. http://forum.xda-developers.com/showthread.php?p=47151583#post47151583

        • Franco Rossel

          1. The binaries were posted after 4.4 release.
          2. What Google device still uses TI?

          • naysayer

            Oh, nothing. Just Google Glass. http://en.wikipedia.org/wiki/Google_Glass

          • Franco Rossel

            Like I said, Google Glass is running Android 4.0 Ice Cream Sandwich, so it won't help you to fight for an update.

          • naysayer

            1) TI still updates the drivers.

            2) TI still sells the chip.
            Need I say more?

          • Franco Rossel

            They updated they drivers too late

          • naysayer

            What are you talking about? If Google would have wanted to update the GNex, they would have easily been able to do so. You seem to assume that TI and Google work in a vacuum.

          • Franco Rossel

            Well, Google won't update the Gnex anyways, so custom roms will do.

          • ass

            Please go choke on Google's cock somewhere else, your arguments are pathetic.

            CM and the other ROMs had 4.4 out for GNex almost immediately after the Nexus 5 came out. TI drivers, my ass.

          • Franco Rossel

            Please, go to be a dumbass somewhere else. Launch ROMs for the Gnex had several graphical glitches and errors, until the drivers were released.

      • Simon Belmont

        Well, not exactly 2.5 years. The G'Nex was released just over two years ago.

        The rest of what you say is accurate, though. Cheers.

      • fuy

        Right, expecting a multi-billion dollar corporation to do the same thing, that a bunch of handful of devs do in their basement is insane. Incredible just how much Google dick some of you fanboys suck.

        Everytime someone mentions TI with regards to the GNex, he sounds like a fucking idiot.

  • redsmith

    404, anyone? Maybe they're still uploading them...

    • angrysock

      Looks like they're still downloadable, you just have to add the first 8 characters of the SHA1 hash right before ".tgz"

      For example, Nexus 5 4.2.2: https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz

      • redsmith

        I see... they are still using the SHA1 from KRT16S. Strange. Thanks a lot dude!!!!

        • angrysock

          Time to lay off the shrooms maybe :p It looks like they're all different hashes though but maybe I missed something?

        • angrysock

          Oops! I see what you meant! Sorry, had to get out of the mindset not everyone is part of the N5 master race :p

      • Belén Cebrián

        They have spelt wrong some links. For example for the Nexus 4 and 4.4.2 the right link is this:

        https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz

        Yes, what you said: the link until "factory" and the those 8 characters, but for the 4.4.2 version they have put the wrong characters, those of 4.4 SHA1 instead of the 4.4.2 SHA1.

        • angrysock

          Good catch! One would think they have this process automated at this point but there seems to be some very human-ish errors here.

          • a random downloader

            Yes, noticed this myself. I don't expect that it'll be long before they're put right, somehow…

        • http://www.LOVEanon.org/ Michael Oghia (Ogie)

          It failed for me. To hell with it, I'll just wait for OTA (I've had issues with it not updating). I'll just irrationally take it as a sign.

    • David Crawford
  • Marc

    Links are broken.

  • angel_spain

    That "all relevant nexus devices" stinks. :(

  • ITGuy11

    404. That’s an error.

    That’s all we know.

  • weirdstuff

    Yup, still busted... :-(

  • Cheeseball

    If only Texas Instruments would release the source code for those said binaries so that other developers would improve them and get a proper working 4.4.x out. They're not obliged to though, and doing so may violate their agreement with ARM and Imagination Technologies.

    • naysayer

      There are already ROMs for the GNex that work pretty much perfect.

      • PhoenixPath

        Bingo. Latest CM11 builds are dang near perfect.

        • Floris

          I'm running them on my Maguro and they almost feel like they're entirely stable. The stock browser became less usuable though, but I'm now using the latest Chrome Beta which somehow manages to run very smoothly.

          • PhoenixPath

            Yep. Threw the latest build available this weekend on my Son's (formerly mine) VZW GalNex and it's running smooth as butta.

            Probably the best that device ever ran. By the time I gave up on it I was ready to chuck it. Good to see it's been given a second chance at life.

      • Cheeseball

        Yeah, I know there are ROMs that work well enough on the Galaxy Nexus, but what I really mean is for other devices that use TI OMAP 44xx. The GPU binaries are not directly swappable unlike the Mali-400MPs (although there are still problems.

    • ass

      Another idiot complaining about Ti drivers, when so many ROMs run flawlessly on GNex.

      • Cheeseball

        How about the Huawei Ascend P1? Or the Galaxy S2 (GT-I9100G)? There ARE other devices using the TI OMAP 4460 aside from Samsung's GNex, moron.

  • Karan O

    i'm getting 404 error on every nexus device EXCEPT nakasiG one so i think they're still uploading them OR they are taking them down because of new build (LOW POSSIBILITY) !
    i just wanted to download them today and i assumed they are there for couple of days and then encounter 404 error and this headline ! so tomorrow maybe!

  • hariprasanth

    404 Error while trying to download the Binaries :(

  • Harris Hakim

    If the link 404's you need to add 8 first characters of the SHA-1 to the end of the link.

    Like so:

    hammerhead-kot49h-factory-.tgz to hammerhead-kot49h-factory-02006b99.tgz

    • angrysock

      Beat ya by a minute ;)

      • Harris Hakim

        Actually I just copy pasted the instruction from a Redditor. (Could be you LOL)

        • angrysock

          Haha, nope. I just noticed it was weird to have "-.tgz" file ending and then I noticed the first 8 chars of the hash in the previous images so I put two and two together

          • Harris Hakim

            Good eyes!

  • Артём Лаптев

    https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz
    Factory Images "occam" for Nexus 4 4.4.2 (KOT49H)

    • Ezio

      Thanks!

  • hakan

    Are there any updated bootloader or radio images compared to 4.4.1?

    • Peter

      not from 4.4.1 to 4.4.2

Quantcast