With the Android 4.2.2 update finally rolling out for most Nexus devices (minus Sprint / VZW GNex), Google has posted factory images of each on the Nexus Factory Image page. These images are useful for flashing your Nexus device back to stock, whether to get an OTA update, or fix that brick you just caused.


These images are for the Nexus 4, Nexus 7 (Wi-Fi and 3G), Nexus 10, and Galaxy Nexus (Yakju / Takju variants). If you want to see what's new in Android 4.2.2, check out our post detailing some of the changes. For a deeper dive, take a look at the developer changelog.

Factory Images For Nexus Devices

David Ruddock
David's phone is whatever is currently sitting on his desk. He is an avid writer, and enjoys playing devil's advocate in editorials, and reviewing the latest phones and gadgets. He also doesn't usually write such boring sentences.

  • brkshr

    Seriously?! I JUST loaded the 4.2.1 images. I literally, 2 minutes ago, finished loading it & was about to load the 4.2.2 update. Now I think I'll just load the new 4.2.2 images :-/

    • http://www.facebook.com/profile.php?id=100000003999549 Mike Harris

      I'm not trying to be sarcastic, but why does it matter which way you update?

      • brkshr

        I'm sure it doesn't. It's mostly for peace of mind. Just in case, some off the wall chance, that the update doesn't apply right or something.

      • mechapathy

        For me it's habit from PC. Better to do a clean install than to upgrade in place. In the case of flashing ROMs, I'll only dirty flash once or twice before doing a clean flash.

  • moelsen8

    so why does google allow some devices to have multiple factory images for the last few versions, while for others it has one version that it just replaces? yes, i know they probably want everyone to forget about LTE on the N4, but it's like this for other devices too. just a curiosity.

    • http://www.androidpolice.com/ David Ruddock

      Wait, 4.2.2 disables LTE?

    • http://codytoombs.wordpress.com/ Cody Toombs

      It's based on API level, with a couple of intentional exclusions. Remember, the Nexus devices are "intended for developers" (I know, this is practically a joke now). The original point of Nexus devices are that developers can freely flash back and forth between Android versions to do app testing. Ideally, developers will want to test their applications on the latest and least buggy version that runs a particular API level. In other words, why test an app against 4.2.1 when 4.2.2 fixes some glitch.

      If you compare the API levels with corresponding versions:
      With the version numbers for the Nexus Factor Images:

      You can see that the versions of each factory image corresponds to the highest version that ran on a particular API level. For example, the Galaxy Nexus (GSM) has 4.0.4 (API 15), 4.1.2 (API 16), and 4.2.2 (API 17), but none of the versions in between. I think they should have labeled the versions with their corresponding API level, but they didn't... I also think it's a bit negligent to remove in-between versions, as some OEMs do end up releasing those and it would be nice to be able to test them if a bug turns up, but that's not how Google sees it.

      There are 2 exceptions I found, and both make sense. The API chart doesn't include 2.3.5 - 2.3.7 (versions that ran on the Nexus S) because they were purely service updates to add support for multi-core processors and fix some system apps, but there were zero changes or bug fixes to the API or libraries that developers would notice. There is also no factory image for 4.0-4.0.2 (API level 14) because the Galaxy Nexus is the only device that ran those versions and it was so quickly updated to 4.0.3 (API level 15) that there's no practical reason to write apps targeting that API.

      Sorry, kinda long, but I thought it might be worth explaining fully.

      • moelsen8

        Wow thanks for the in-depth explanation!! There is a method to the madness after all!

  • http://www.facebook.com/profile.php?id=100000003999549 Mike Harris

    I restored a Nandroid backup of the stock Rom on my N10 last night just to try and get the update, but the checker still said I was up-to-date as of (around) 2 am. Should I be concerned that I haven't gotten the OTA yet? I'm almost positive the kernel is stock, so I don't see any reason it wouldn't work. I'd much rather update OTA so I don't have to restore everything after manually updating.

    On a side note, with just two Nandroid backups (one for stock; one for AOKP), I'm left with very little space on my 32GB N10. Obviously, I'm happy I didn't settle for the 16GB version, but I still think that it's ridiculous that Google didn't include an MicroSD slot.

  • blahmoomoo

    So... they've posted the factory updates, but they still haven't made the 4.2.2 update available to the system updater built in to my just-purchased unlocked Nexus 4. I don't get why it's available manually now, but not automatically yet.

    • Razormike

      It is available manually, it just takes a while for the update to reach you.

    • NameHere

      Because Google updates in waves, that's why.

      • Blah

        It could be today or even sometime next week. If you want it immediately, just manually update.

    • http://www.facebook.com/archercc Ryan Stewart

      Are you a noob? They have always staged the updates, everyone always have. Its probably to limit demand on the server and if there was an issue with the update process it might only affect a slim few.

      So few people are going to manually update that it doesn't matter.

      • blahmoomoo

        Highlight: "just-purchased"

        Yes, I'm new to this. Thank you for alienating me.

        • NexusKoolaid

          IIRC (correct me if I have this wrong, anyone) it's rolled out in an IMEI based order. The oldest units should get the update sooner than newer phones. Just hang tight - it will get to you.

        • Matthew Fry

          Don't worry 'bout it. We don't bite... hard.
          - Someone who is chronically misunderstood

        • http://www.facebook.com/archercc Ryan Stewart

          Is your skin that thin?

          The reason I said it that way its its simply logic, nothing special about Android.

    • http://www.facebook.com/profile.php?id=1312291338 Tim Miller

      It's definitely available. I updated yesterday. Clear the cache on your Google Services Framework and check again - may do the trick. Or just flash it manually - that takes all of 30 seconds.

  • Steve Green

    Screw you Verizon. I hate you with the fury of ten thousand suns.

    • Scott

      The verizon variant of the phone is just bad all around. As a device and with Verizon.

      • dshim83

        The Verizon Nexus 4 is by far one of the worst Android devices, in large part due to its lack of existance.

  • Mike Loomis

    I, too, am still waiting for the OTA update for my Nexus 4. I am surprised it is taking this long.

  • Nir

    Got the OTA update here in Israel for the Nexus 4. Not installing it yet though, waiting to hear about the LTE disabling issue. I currently have the 4.2.1 i got in the last OTA update - is there any way of making an image factory out of that? or anyone knows where i can find that image online? (not available anymore, was replaced with the new 4.2.2 on site)