Google Releases April Android Security Fixes to Pixel & Nexus – OTA & Factory Images Live
Google is now releasing Android April security patch after releasing the second beta of Android 7.1.2 beta and Android O first developer preview last month. This is the first release from the Android maker for the month of April and brings security patches and minor bug fixes to Google’s Pixel and Nexus lineup.
Download Android April security patch factory images and OTAs
Google has released Android 7.1.1 NOF27D for Google Pixel and Pixel XL. Nexus 6P and Nexus 5X have received Android 7.1.1 N4F26U; Nexus 6 is getting N6F26Y Android 7.1.1 with NBD92F and NBD92G 7.0.0 also receiving security patches, and finally Nexus 9 LTE and WiFi are receiving N4F26X.
We will be sharing the complete changelog of April Android security patch when it goes live, as Google hasn’t yet updated the security bulletin for this month. At the moment, we can’t say if this month’s release fixes any critical security vulnerabilities.
In the meanwhile, you can manually update your devices using factory images and OTA links. Here are the links:
- Pixel XL: Android 7.1.1 NOF27D – Factory Image and OTA
- Pixel: Android 7.1.1 NOF27D – Factory Image and OTA
- Nexus 6P: Android 7.1.1 N4F26U – Factory Image and OTA
- Nexus 5X: Android 7.1.1 N4F26U – Factory Image and OTA
- Nexus 6: NBD92F (7.0.0), NBD92G (7.0.0), N6F26Y (7.1.1) – Factory Image (2) (3) and OTA (2) (3)
- Nexus 9 (LTE): Android 7.1.1 N4F26X – Factory Image and OTA
- Nexus 9 (Wi-Fi): Android 7.1.1 N4F26X – Factory Image and OTA
Not sure how to use factory images or OTA files to bring your devices up to the latest security patch? Follow the steps in these guides, but make sure to use the zip files from the links shared above:
- Update Google Pixel and Pixel XL to April Security Patch Using Factory Images
- How to Update Google Pixel or Nexus Using Factory Images and OTA files
Android April security bulletin
April’s security release fixes several issues, including a Critical security vulnerability that could enable remote code execution on an affected device through multiple methods such as email, web browsing, and MMS when processing media files. Google promises that there are no reports of active exploitation of any of these reported issues. More details on this can be found here.