sodcalculator

10 Tech How-To

Install Android 16 Developer Preview on Pixel

Guide 10-55265 · Updated · Step by step

This guide walks you through installing the Android 16 Developer Preview on a compatible Google Pixel device. It’s aimed at developers and early adopters who want to test the latest features and APIs before the public beta. You’ll need a Pixel phone, a computer, and a willingness to wipe your device — the preview is not a stable daily driver.

What You’ll Need

  • A compatible Google Pixel device (Pixel 6 and newer, including Pixel Fold and Pixel Tablet). Check the official Android developer site for the exact list for this preview.
  • A USB cable that supports data transfer (not just charging).
  • A computer (Windows, macOS, or Linux) with Android SDK Platform Tools installed (adb and fastboot).
  • Your Pixel must be unlocked (bootloader unlocked) — this wipes all data, so back up anything important.
  • Battery at least 50% charged.
  • Patience — flashing can take a few minutes.

Step-by-Step

  1. Back up your data. Unlocking the bootloader and flashing the preview wipes everything. Use Google One backup or manually copy photos and files to your computer.
  2. Enable Developer Options. On your Pixel, go to Settings > About phone and tap Build number seven times. You’ll see a toast saying “You are now a developer.”
  3. Enable USB debugging. Go to Settings > System > Developer options and toggle on USB debugging.
  4. Install Platform Tools on your computer. Download the official Android SDK Platform Tools zip for your OS, extract it to a folder (e.g., C:\platform-tools on Windows, ~/platform-tools on Linux/macOS).
  5. Connect your Pixel to the computer. Use a good USB cable. On the phone, accept the “Allow USB debugging?” prompt and check “Always allow from this computer.”
  6. Verify adb connection. Open a terminal/command prompt in the platform-tools folder and run adb devices. You should see your device listed as “device” (not “unauthorized”).
  7. Unlock the bootloader. Run adb reboot bootloader. The phone will restart into fastboot mode. Then run fastboot flashing unlock. On the phone, use the volume keys to highlight “Unlock the bootloader” and press power to confirm. This wipes your data and reboots.
  8. Re-enable USB debugging. After the reboot, go through Settings again to turn on USB debugging (it resets after the wipe).
  9. Download the Android 16 Developer Preview factory image. Go to the Android Developer website, find the preview for your device, and download the factory image (not the OTA, unless you’re already on a previous preview).
  10. Extract the factory image. Unzip the downloaded file. Inside, you’ll find a folder with the device codename (e.g., “panther” for Pixel 7) and a flash-all.sh (Mac/Linux) or flash-all.bat (Windows) script.
  11. Flash the image. With your phone in fastboot mode (reboot via adb reboot bootloader if needed), run the flash script from the extracted folder. On Windows, double-click flash-all.bat; on Mac/Linux, run ./flash-all.sh in the terminal. The script will wipe your device and install the preview.
  12. Wait for the process to finish. The script will flash the bootloader, radio, and system partitions, then reboot. It may take 5-10 minutes. Don’t unplug the cable.
  13. Set up your device. Once it boots, you’ll see the Android setup wizard. Go through it as usual. You’re now running Android 16 Developer Preview.

Common Mistakes

  • Using the wrong factory image. Each Pixel model has a different image. Downloading the wrong one will fail or brick the device. Double-check the codename in the filename.
  • Not unlocking the bootloader first. The flash script will fail if the bootloader is locked. You must unlock it before flashing.
  • USB debugging not enabled after the bootloader unlock. The unlock wipes data, so you must re-enable it before flashing.
  • Interrupting the flash. Don’t unplug the cable or close the terminal mid-flash. This can leave the device in a bootloop or with a corrupted system.
  • Running the script from the wrong directory. The flash script needs to be in the same folder as the image files. If you run it from elsewhere, it won’t find the files.

Tips

  • Keep the platform-tools folder in a short, simple path (e.g., C:\platform-tools) to avoid path-length issues on Windows.
  • Use a USB port directly on your computer, not a hub, to avoid connection drops.
  • Before flashing, read the release notes for the preview — some features may be broken or incomplete.
  • If you want to go back to stable Android, download the latest stable factory image for your device and flash it the same way. It will wipe your data again.
  • Consider joining the Android Beta Program later if you want over-the-air updates instead of manual flashing — but that’s for the beta, not the developer preview.

Troubleshooting

  • Device not showing in adb devices: Reinstall the USB driver (Windows) or check the cable. Try a different port. On the phone, revoke USB debugging authorizations and re-accept the prompt.
  • Fastboot says “waiting for any device”: Install the proper fastboot driver (Windows) or run fastboot devices to check. On Linux, you may need udev rules for Android devices.
  • Flash fails with “out of memory” or “not enough space”: This is rare but can happen if the image is corrupted. Re-download the factory image and try again.
  • Device stuck in bootloop after flashing: Hold the power button for 30 seconds to force restart. If it still loops, re-flash the image — sometimes a second attempt works. If not, try flashing the stable image to recover.
  • Bootloader unlock option not appearing: Some carriers lock the bootloader. You may need to contact your carrier or use a SIM-unlocked device.

Frequently Asked Questions

Will installing the developer preview void my warranty?

Unlocking the bootloader and flashing a developer preview can void your warranty with Google or your carrier, though Google often allows re-locking the bootloader to restore warranty status. Check your device’s warranty terms.

Can I install the preview without a computer?

No, the developer preview requires a computer to flash the factory image. The public beta later can be installed over the air via the Android Beta Program.

Will my apps work on the developer preview?

Most apps should work, but some may crash or have visual glitches because they haven’t been updated for the new APIs. That’s expected in a developer preview.

How do I get updates for the preview?

You’ll need to manually flash each new preview build. The developer preview does not receive over-the-air updates like the beta.

Can I downgrade back to Android 15?

Yes, you can flash the stable Android 15 factory image using the same method. It will wipe your data, so back up first.

Is the developer preview stable enough for daily use?

No, it’s meant for development and testing. Expect bugs, poor battery life, and missing features. Use a spare device if possible.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →