Yesterday T-Mobile announced new over-the-air updates for the Nexus 4, 5, 6, 7, and 9. They contained security and bug-related fixes that, for the most part, aren't all that exciting. The patches amounted to under 20MB for all but the Nexus 6, which was under 30. But Google didn't promise us fun when it promised monthly Nexus updates. Read More
Google announced the Stagefright vulnerability fix would start rolling out as an OTA today, but it has also added new factory images to the Nexus developer pages. That means bootloader unlocked Nexus phones and tablets can flash the new build immediately, even if your device is running some wacky ROM. Read More
Android 5.0 was a big visual change for Android, but the upcoming M release will make its mark on Android as well. Google is likely going to announce hard cut-offs for Nexus device update support. There will be no more guessing about which devices will get updates and for how long, but that means several older devices are going to stay on Lollipop. Read More
After an early tease with the Nexus Player, it looks like Android 5.1.1 is legitimately rolling out to the Nexus family. An OTA for the Nexus 10 was spotted just a few hours ago, and now factory images and binaries have been posted for that tablet and both generations of the Nexus 7 (Wi-Fi only, for now). There haven't been any OTA reports for the two smaller tablets, but they will probably start rolling out shortly.
There are still no signs of OTAs or factory images for the seemingly ignored Nexus 9, nor any phone or tablet with a cellular radio. Read More
The Nexus 10 appears to be receiving its Android 5.1.1 update over-the-air. This is mainly a bugfix release, but any update is welcome news, especially on a device that's considered by some to be past its prime.
The update weighs in at a somewhat paltry 13.9 MB and is most likely build LMY47V. We don't have a link to the OTA update ZIP file yet, but once we do, we'll update this post. This is likely a good sign that we'll start seeing a wider rollout to more Nexus devices in the very near future, possibly even to the so-far-neglected Nexus 9. Read More
Google has made Android 5.1 official and that means Nexus updates. Factory images are starting to pop up on the developer page, so you can easily get your device back to stock no matter what unspeakable things you've done to it. All the images we have so far are linked below.
Of our many jobs here at Android Police, one is to make our readers' lives easier when we can. With that in mind, here's a roundup of every known Nexus Lollipop OTA. As new ones become available, this post will be updated accordingly.
Lollipop will be released to Nexus 4, 5, 7 (2012 and 2013), and 10, plus bugfix OTAs to Nexus 6 and 9. As I'm sure you've guessed, there will be plenty of files to be had.
Nexus 9 Issues
Update: For those of you who had issues with applying the LRX21L > LRX21Q update, that was a screw up on Google's part. Read More
Time to break out that old Nexus 7 or Nexus 10—Google has just posted system images based on Android 5.0.2 for both of these devices (razor and mantaray). The most recent version on these tablets before today was 5.0.1, so it's not like they've been waiting on Lollipop this whole time like some devices (cough razorg cough).
It's not unusual to see slightly customized builds of Android rolling out to Nexus devices shortly after the release of a new version. It certainly happened a few times with KitKat, and it looks like Lollipop is on track to do the same. As the rush of factory images and OTAs roll out, AOSP is also receiving commits for the new device-specific builds; and Al Sutton was quick to put out changelogs for each version. These begin with the version currently residing on the Nexus Player, 5.0.0_r2 (LRX21M), and run through LRX21Q, which just appeared on the Nexus 9.
Since each build only appears on select devices, they're organized below to show where they've been distributed. Read More
If you're trying to flash your Nexus 5, 7, or 10 to Android 5.0 now that the factory images are out, there's nothing more infuriating than running into an error in the process. The most common error we're seeing today as part of the flashing process is the dreaded "missing system.img" dialog, which aborts the update process on the target device.
The reason this happens is because the flash-all script that comes in the image package, which most of you are undoubtedly trying to use, is attempting to flash the .img files in the update using the 'fastboot update' method, which appears to be failing for some reason for some users. Read More