How to Install Android 11 DP1: A Step-by-Step Guide

Android 11 Developer Preview 1 (DP1) is the first early build of the next major Android version, aimed at developers and enthusiasts who want to test new APIs and system changes before the public beta. Installing it requires an unlocked bootloader and a compatible Pixel device, and it will wipe all data on the phone. This guide walks you through the entire process, from backing up your data to flashing the factory image, so you can get DP1 running safely.

What You’ll Need

A compatible Google Pixel device: Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a, Pixel 3a XL, Pixel 4, or Pixel 4 XL (DP1 supports these models).
A USB cable that supports data transfer (not just charging).
A computer running Windows, macOS, or Linux.
Android SDK Platform Tools (includes ADB and Fastboot) installed on your computer. Download the official package from the Android developer site.
Your phone’s bootloader must be unlocked. If it’s not, you’ll need to unlock it first (this wipes data).
At least 50% battery charge on your phone to avoid interruption.
Backup of all important data—flashing will erase everything.

Step-by-Step

Back up your data. Use Google’s built-in backup (Settings > System > Backup) or copy photos, files, and anything important to your computer. Since flashing wipes the device, this step is critical.
Enable Developer Options and USB debugging. On your phone, go to Settings > About phone and tap “Build number” seven times. Then go to Settings > System > Developer options and turn on “USB debugging” and “OEM unlocking” (if available).
Download the Android 11 DP1 factory image. Visit the Android Developer Preview site (developer.android.com/preview) and download the factory image for your specific Pixel model. Make sure you pick the correct variant (e.g., “flame” for Pixel 4, “sargo” for Pixel 3a).
Extract the downloaded zip file. Use a file archiver like 7-Zip (Windows), The Unarchiver (macOS), or unzip (Linux). Inside you’ll find another zip file named like image-flame-pp1a.190520.004.zip and a script file (flash-all.sh for Mac/Linux, flash-all.bat for Windows).
Install Platform Tools. If you haven’t already, download the SDK Platform Tools zip from the Android developer site and extract it to a folder on your computer. Note the path to this folder (e.g., C:\platform-tools).
Connect your phone to the computer. Use the USB cable and plug it into your computer. On your phone, a dialog may appear asking to allow USB debugging—check “Always allow from this computer” and tap OK.
Verify ADB connection. Open a command prompt or terminal in the platform-tools folder (Shift+right-click > “Open command window here” on Windows, or use cd on Mac/Linux). Type adb devices and press Enter. You should see your device listed as “device” (not “unauthorized”). If not, check the USB debugging prompt on your phone.
Reboot to bootloader. Type adb reboot bootloader and press Enter. Your phone will restart into the bootloader (fastboot) mode, showing a green Android robot.
Verify fastboot connection. In the same terminal, type fastboot devices. Your device should appear with a serial number. If it says “no permissions” or nothing, you may need to install USB drivers (Windows) or set up udev rules (Linux).
Run the flash script. Navigate to the extracted factory image folder (where flash-all.bat or flash-all.sh is located). On Windows, double-click the .bat file, or type flash-all.bat in the terminal. On Mac/Linux, run chmod +x flash-all.sh then ./flash-all.sh. The script will flash the bootloader, radio, and system images, then automatically reboot the phone. It may take several minutes—do not unplug the cable.
Wait for the phone to boot. The first boot after flashing can take up to 10 minutes. You’ll see the Android boot animation. Once it finishes, you’ll be greeted with the setup wizard. Set up your device as new or restore from your backup.

Common Mistakes

Wrong factory image: Downloading the image for a different Pixel model (e.g., using Pixel 3 image on Pixel 3a) will cause the flash to fail or brick the device. Double-check the model number in Settings > About phone.
USB debugging not enabled: Without it, ADB won’t recognize your device, and you can’t proceed. Ensure it’s on before connecting.
Insufficient battery: Flashing requires power; if the phone dies mid-flash, it can become unstable. Charge to at least 50%.
Unlocked bootloader required: If your bootloader is locked, the flash script will fail with an error. You must unlock it first, which wipes data.
Using a non-data USB cable: Some cables only charge. Use the original cable or one known to support data transfer.
Interrupting the flash: Pulling the cable or closing the terminal during flashing can corrupt the device. Let it finish.

Tips

Keep the platform-tools folder handy: You’ll need ADB and fastboot for future updates and troubleshooting.
Use a stable USB port: Prefer a direct port on your computer rather than a hub to avoid connection drops.
Read the release notes: The DP1 has known issues; check the Android developer site for bugs that might affect you.
Downgrade is possible: If DP1 is too buggy, you can flash the latest stable Android 10 factory image using the same method—just download the appropriate image and run the script.
Do a clean install: Since this is a developer preview, a clean install (without restoring app data) reduces the chance of weird issues.

Troubleshooting

ADB doesn’t detect the device: Make sure USB debugging is on and you’ve accepted the RSA key prompt. Try a different USB port or cable. On Windows, install the Google USB driver via SDK Manager.

Fastboot says “device not found”: Ensure you’re in bootloader mode (check the screen). On Linux, add udev rules for Android devices. On Windows, install the correct driver.

Flash fails with “not enough space” or “partition not found”: This usually means you have the wrong factory image. Re-download the correct one for your model.

Phone stuck in boot loop after flashing: Try a factory reset from recovery mode (hold Power + Volume Down to enter bootloader, then use volume keys to select Recovery). If that doesn’t work, re-flash the factory image with the flash-all script again.

Bootloader unlock option is grayed out: If “OEM unlocking” is disabled in Developer options, you may need to insert a SIM card and connect to the internet for a few minutes, then re-enable it. Some carriers block bootloader unlocking—check with your carrier.

Script fails on Windows due to missing drivers: Install the latest Google USB driver from the SDK Manager, then restart the computer and try again.

Frequently Asked Questions

Q: Will installing DP1 void my warranty?
A: Unlocking the bootloader and flashing a developer preview may void your warranty, depending on the manufacturer and region. Google’s Pixel devices are generally tolerant, but it’s not guaranteed.

Q: Can I go back to Android 10 after installing DP1?
A: Yes, you can flash the Android 10 factory image using the same fastboot method. It will wipe your data again, so back up first.

Q: Do I need to unlock the bootloader to install DP1?
A: Yes, the bootloader must be unlocked to flash a factory image. Unlocking wipes all data, so back up before doing it.

Q: Will I get OTA updates for DP1?
A: No, developer previews are not delivered via OTA. You’ll need to manually flash future previews or the final beta using the same method.

Q: Is DP1 stable enough for daily use?
A: No, it’s an early developer build with many bugs and missing features. It’s meant for testing, not as a daily driver.

Q: What if my Pixel model isn’t listed?
A: DP1 only supports the devices listed in the “What You’ll Need” section. If yours isn’t there, you’ll have to wait for the public beta or stable release.

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 →