Following Verizon rolling out Android 8.0 for Pixel and Pixel XL, Google has now released Android Oreo OTA update links for the compatible devices. The Android maker had posted the factory images for Pixel and Nexus devices last week, however, they were limited to developers (not that it stopped any of us from flashing them - check our review here). Android 8.0 Oreo factory images have too now been uploaded on the public site.
If you haven't received an official update to install Android 8.0 Oreo on your device, don't want to wait any longer, and are okay with the general process, here are the Android Oreo OTA links and factory images for Google Pixel, Pixel XL, and Nexus devices.
Download Android Oreo OTA files and factory images
- Google Pixel: OPR6.170623.011 (Bell, Telus, Telstra, TMO, Sprint, USCC, Rogers/Fido), OPR6.170623.012 (other carriers) - Factory Image (2) & OTA (2)
- Google Pixel XL: OPR6.170623.011 (Bell, Telus, Telstra, TMO, Sprint, USCC, Rogers/Fido), OPR6.170623.012 (other carriers) - Factory Image (2) & OTA (2)
- Pixel C: OPR6.170623.010 - Factory Image & OTA
- Nexus 6P: OPR6.170623.013 (Not for TMO/USCC/Fi) - Factory Image & OTA
- Nexus 5X: OPR6.170623.013 - Factory Image & OTA
These factory images were previously available via the Android Developers page, however, Android Oreo OTA files have showed up for the first time. Users find installing OTA files easier than flashing factory images as the latter requires an unlocked bootloader. We have already shared with you steps to install Android Oreo on Pixel or Nexus devices using factory images. For OTA files, you can follow the official instructions here.
What's with the long build names...
You may have noticed the usual 6-digit build name is now gone with a longer string replacing it. Google is changing the format of Android build numbers with the release of Android 8.0 Oreo. The current and any new updates will be in the format of "
In this new format, the P stands for the first letter of the code name ("O" for Oreo), V is for the vertical, which will remain "primary" for the user builds, and BB is the code branch used in a build (R6 in current release). The next 6 digits are for the date the Android build was synced with the development branch and finally the last 3 digits represent multiple individual versions with the same date code, starting with 001.
This may sound a little confusing but the original build ID scheme, while shorter on the front, was even worse. Interested for more? You can check out the details of this new and the old scheme over at Google.