sodcalculator

10 Tech How-To

How to Install Android 15 Developer Preview

Guide 10-48743 · Updated · Step by step

This guide walks you through installing the Android 15 Developer Preview on a compatible Google Pixel device. You’ll get early access to new features and APIs before the public release, but you’ll need to unlock your bootloader and flash a system image manually. The process takes about 30–60 minutes and requires a computer and a bit of command-line comfort.

What You’ll Need

  • A supported Pixel device (Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, Pixel Fold, or Pixel Tablet — check the official list before starting).
  • A USB cable that supports data transfer (not just charging).
  • A computer running Windows, macOS, or Linux.
  • Android SDK Platform Tools (contains adb and fastboot).
  • Google USB driver (Windows only).
  • Android 15 Developer Preview system image (download from the official Android developer site).
  • Backup of your phone’s data — flashing wipes everything.

Step-by-Step

  1. Back up your device. Use Google One backup or a local backup to a computer. Flashing the preview erases all user data, so this step is non-negotiable.
  2. Install Platform Tools. Download the SDK Platform Tools zip for your OS, extract it to a folder you can remember (e.g., C:\platform-tools on Windows, ~/platform-tools on Mac/Linux).
  3. Enable Developer Options. On your phone, go to Settings → About phone and tap Build number seven times. You’ll see a toast saying “You are now a developer.”
  4. Enable USB debugging and OEM unlocking. Go to Settings → System → Developer options and turn on both USB debugging and OEM unlocking. The latter is required to unlock the bootloader.
  5. Connect your phone to the computer. Plug in the USB cable. On your 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”. If it says “unauthorized”, check the phone screen and accept the prompt.
  7. Unlock the bootloader. Run adb reboot bootloader. The phone will reboot into fastboot mode. Then run fastboot flashing unlock. On the phone, use the volume keys to select “Unlock the bootloader” and confirm with the power button. This wipes your data and reboots.
  8. Re-enable USB debugging. After the reboot, go through Developer Options again and turn on USB debugging (OEM unlocking will already be on).
  9. Download the Android 15 Developer Preview image. Visit the Android developer website, find the “Developer Preview” section, and download the factory image for your specific Pixel model. Make sure you pick the correct device codename (e.g., “bluejay” for Pixel 6a).
  10. Extract the image. Unzip the downloaded file. Inside you’ll find a folder with several files including flash-all.bat (Windows) or flash-all.sh (Mac/Linux).
  11. Boot into fastboot again. Run adb reboot bootloader from the platform-tools folder.
  12. Run the flash script. On Windows, double-click or run flash-all.bat in a command prompt. On Mac/Linux, run ./flash-all.sh in a terminal. The script will flash the bootloader, radio (if any), and system partitions, then reboot automatically.
  13. Wait for the first boot. The first boot after flashing can take 5–10 minutes. Don’t interrupt it. You’ll eventually see the Android setup screen.
  14. Set up your device. Go through the setup wizard, restore your backup if you want, and verify that Android 15 is active by going to Settings → About phone and checking the Android version.

Common Mistakes

  • Using the wrong image. Flashing a Pixel 7 image on a Pixel 6 will fail or brick the device. Double-check the model and codename.
  • Forgetting to unlock the bootloader. If you skip step 7, the flash script will fail with an error like “FAILED (remote: not allowed)”.
  • Not accepting the USB debugging prompt. The phone must be in “device” state, not “unauthorized”, before you can proceed.
  • Interrupting the flash. Unplugging the cable or closing the terminal mid-flash can leave your phone in a bootloop or with a corrupted system.
  • Using a USB hub or poor cable. A flaky connection can cause random failures. Use a direct port and a known-good cable.

Tips

  • Keep the platform-tools folder handy; you’ll need it again to flash future preview updates or to revert to stable Android.
  • If you’re on Windows, install the Google USB driver from the Android developer site before connecting your phone, or fastboot may not recognize it.
  • Make sure your phone has at least 60% battery before starting. Flashing can take a while and a dead battery mid-flash is bad news.
  • Join the Android Beta for Developers program if you want over-the-air (OTA) updates instead of manual flashing. It’s easier but not available for the first Developer Preview.
  • Take a screenshot of your current Android version and build number before flashing, so you can verify the install later.

Troubleshooting

  • “fastboot: command not found” — You’re not in the platform-tools directory, or the tools aren’t in your PATH. Navigate to the folder where you extracted them and try again.
  • Device shows as “unauthorized” in adb devices — Unplug and replug the USB cable, then check the phone screen for the debugging prompt. If it doesn’t appear, revoke USB debugging authorizations in Developer Options and try again.
  • Flash fails with “remote: (not allowed)” — The bootloader is still locked. Reboot to fastboot and run fastboot flashing unlock again.
  • Phone stuck in a bootloop after flashing — This usually means the image didn’t match the device. Boot back into fastboot (hold power + volume down) and reflash the correct image. If that fails, flash the latest stable factory image to restore the phone.
  • Script runs but phone doesn’t reboot — The script may finish with the phone still in fastboot. Manually run fastboot reboot to restart.
  • No data after setup — That’s expected. You wiped the device. Restore from your backup during setup.

Frequently Asked Questions

Will I lose all my data?

Yes, unlocking the bootloader and flashing the preview wipes your phone completely. Back up everything important before starting.

Can I go back to stable Android after installing the preview?

Yes. Download the latest stable factory image for your device and run the flash-all script the same way. This will wipe your data again, so back up first.

Is the Developer Preview stable enough for daily use?

No. It’s meant for developers to test apps and APIs. Expect bugs, poor battery life, and missing features. Don’t install it on your primary device unless you’re prepared for that.

Will I get updates automatically?

No. Developer Preview builds are manual flashes. Later, the Android Beta program will offer OTA updates, but the first preview does not.

My device isn’t a Pixel. Can I install it?

No. The Developer Preview is only available for supported Pixel devices. Other manufacturers release their own previews later.

What if I don’t want to unlock the bootloader?

Then you can’t install the Developer Preview. Unlocking is required. If that’s a dealbreaker, wait for the public beta, which doesn’t require an unlocked bootloader.

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 →