Factory Images for Nexus and Pixel Devices  |  Google Play services  |  Google for Developers
Skip to main content
Google
Play services
API Guides
New Releases
Reference
Samples
Support
Downloads
Beta
/
English
Deutsch
Español
Español – América Latina
Français
Indonesia
Italiano
Polski
Português – Brasil
Tiếng Việt
Türkçe
Русский
עברית
العربيّة
فارسی
हिंदी
বাংলা
ภาษาไทย
中文 – 简体
中文 – 繁體
日本語
한국어
Sign in
Google
Play services
API Guides
New Releases
Reference
Samples
Support
Downloads
Beta
Factory Images for Nexus and Pixel Devices
Factory Images for Google Pixel Watch Devices
Full OTA Images for Nexus and Pixel Devices
Full OTA Images for Google Pixel Watch Devices
Driver Binaries
Home
Products
Google Play services
Downloads
Factory Images for Nexus and Pixel Devices
Stay organized with collections
Save and categorize content based on your preferences.
Page Summary
outlined_flag
Binary image files are for restoring Nexus or Pixel devices to their original factory firmware.
It is typically easier and safer to sideload the full OTA image instead of using factory images.
Relock your bootloader after using a factory image for security.
Installing a factory image will erase all data from your device.
There are special instructions for updating certain Pixel devices to the May 2025 monthly release due to a bootloader update.
This page contains binary image files that allow you to restore your Nexus
or Pixel device's original factory firmware. You will find these files useful
if you have flashed custom builds on your device, and want to return your
device to its factory state.
Note that it's typically easier and safer to sideload the
full OTA image instead.
If you do use a factory image, make sure that you relock your
bootloader when the process is complete.
These files are for use only on your personal Nexus or Pixel devices and may
not be disassembled, decompiled, reverse engineered, modified or redistributed
by you or used in any way except as specifically set forth in the license
terms that came with your device.
Note: For convenience, we listed the release date along with each build.
Sometimes, the release date may be different from the security
patch level (SPL) date. The SPL dates for each build can be found
on the Codenames, tags, and build numbers page.
Factory images for Google Pixel Watch
devices are also available.
Special instructions for updating Pixel devices to the May 2026 monthly release
Warning: The May 2026 update for Pixel 10, 10 Pro, 10 Pro XL and 10 Pro Fold
devices contains a bootloader update that increments the anti-roll back version
for the bootloader. This prevents the device from rolling back to previous
vulnerable versions of the bootloader. After flashing the May 2026 update on
these devices you won't be able to flash and boot older Android 16 builds.
After taking an May 2026 update and successfully booting the device post update,
an Android 16 build resides in the inactive slot
(seamless updates for more
information on slots) of the device. The inactive slot contains an older
bootloader whose anti-rollback version has not been incremented. If the active
slot is then flashed with a build that fails to boot, the fallback mechanism of
seamless updates kicks in and the device tries to boot from the inactive slot.
Since the inactive slot contains the older bootloader, the device enters an
unbootable state.
To avoid hitting this state, if you are flashing an impacted Pixel device with
the May 2026 update or newer for the first time, flash the bootloader partition
to the inactive slot after successfully updating and booting into Android 16
May 2026 at least once. This can be done by following these steps:
After a successful boot into Android 16 May 2026 for the first time, sideload
the full OTA image corresponding
to that build and reboot the device to ensure that both slots have a bootable
image.
Special instructions for updating Pixel devices to the May 2025 monthly release
Warning: The May 2025 update for Pixel 6 (6, 6 Pro, 6a) and Pixel 8 (8, 8 Pro,
8a) devices contains a bootloader update that increments the anti-roll back
version for the bootloader. This prevents the device from rolling back to
previous vulnerable versions of the bootloader. After flashing the May 2025
update on these devices you won't be able to flash and boot older Android 15
builds.
After taking an May 2025 update and successfully booting the device post update,
an Android 15 build resides in the inactive slot
(seamless updates for more
information on slots) of the device. The inactive slot contains an older
bootloader whose anti-rollback version has not been incremented. If the active
slot is then flashed with a build that fails to boot, the fallback mechanism of
seamless updates kicks in and the device tries to boot from the inactive slot.
Since the inactive slot contains the older bootloader, the device enters an
unbootable state.
To avoid hitting this state, if you are flashing an impacted Pixel device with
the May 2025 update or newer for the first time, flash the bootloader partition
to the inactive slot after successfully updating and booting into Android 15
May 2025 at least once. This can be done by following these steps:
After a successful boot into Android 15 May 2025 for the first time, sideload
the full OTA image corresponding
to that build and reboot the device to ensure that both slots have a bootable
image.
Terms and conditions
Warning: Installing a factory image will erase all data from the device, and
unlocking the bootloader will make your device less secure. In most cases it
should be possible to sideload the
full OTA image instead. This
does not require a data wipe, and does not require the bootloader to be
unlocked.
While it may be possible to restore certain data backed up to your Google
Account, apps and their associated data will be uninstalled. Before proceeding,
ensure that data you would like to retain is
backed up to your Google Account.
Downloading of the system image and use of the device software is subject to the
Google Terms of Service. By
continuing, you agree to the
Google Terms of Service and
Privacy Policy. Your
downloading of the system image and use of the device software may also be
subject to certain third-party terms of service, which can be found in
Settings > About phone > Legal information, or as otherwise provided.
Acknowledge
I have read and agree with the terms and conditions.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-07-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-07-07 UTC."],[],["Factory images restore Nexus/Pixel devices to their original firmware, useful after flashing custom builds.  Updating Pixel 6/6 Pro/6a to Android 13 requires flashing the bootloader to the inactive slot to prevent an unbootable state. This can be done by sideloading the full OTA image or by manually flashing the bootloader via `fastboot` commands after the first successful Android 13 boot. Flashing a factory image will erase all device data.\n"]]
Connect
Android Developers Blog
Get News and Tips by Email
More Resources
Android Developers Website
Google Design
Tools
Android Studio
Google Play Console
Android
Chrome
Firebase
Google Cloud Platform
Google AI
All products
Terms
Privacy
Manage cookies
English
Deutsch
Español
Español – América Latina
Français
Indonesia
Italiano
Polski
Português – Brasil
Tiếng Việt
Türkçe
Русский
עברית
العربيّة
فارسی
हिंदी
বাংলা
ภาษาไทย
中文 – 简体
中文 – 繁體
日本語
한국어