Android 16 is not suitable with Google’s newest beta launch

Key Takeaways

• Putting in Android 16 DP1 over Android 15 QPR2 requires an information wipe on account of incompatibility.
• Guide set up through Fastboot or Android Flash Device wipes knowledge by default, as does unlocking the bootloader, so this solely impacts customers who have been trying to bypass these steps.
• This situation could be non permanent and could possibly be resolved in future Android 16 builds.

Google’s first construct of Android 16 has formally arrived, and although the DP1 in its identify signifies it is meant to be a preview for builders, many die-hard Android followers will likely be flashing it at the moment to get a style of the long run. Those self same early adopters have possible already put in Google’s newest beta,

Android 15 QPR2
, which can debut in just a few months because the March Pixel Function Drop. Besides there’s an issue: The 2 updates are usually not suitable.

In Google’s announcement put up for Android 16 DP1, the corporate casually outlined what could possibly be a serious downside for folk trying to set up this replace at the moment:

In the event you’ve already put in Beta 1 from the Android 15 QPR2 Beta program, you won’t be able to maneuver to the Android 16 Developer Preview program with out wiping your gadget. Think about avoiding putting in future betas to transition to the subsequent developer preview construct with no knowledge wipe.

In different phrases, early adopters who eagerly put in Google’s newest public beta might want to wipe knowledge when flashing the DP1 pictures. Technically, wiping after flashing would work too, it is simply that you just’d be caught in a bootloop till you probably did (Observe: If this does occur to you, press and maintain the quantity down key in your Pixel whereas it is bootlooping to get into Fastboot mode, then boot into restoration mode to wipe knowledge).

Let’s face it, you have been in all probability going to need to wipe knowledge anyway

Like all developer previews from Google, Android 16 DP1 shouldn’t be accessible as a conventional OTA, since these are reserved for the secure and beta channels, and this construct is a pre-beta launch. In the end, this implies it’s important to manually set up the OTA file or flash the manufacturing unit pictures.

Google’s manufacturing unit pictures packages include a flash-all.bat file which you could run in a command window in your desktop to execute all of the related fastboot instructions one-by-one. The step the place it flashes the principle chunk of information sends this command:

fastboot -w replace filename.zip

The “-w” half sends a command to totally wipe the gadget, so you would completely run the flash-all script as-is and be able to go. Traditionally, most individuals who use it modify the script to delete that “-w” although, so that they could not do this right here.

For individuals who use Android Flash Device to put in updates like these, the software additionally wipes knowledge by default. So you may simply must keep away from altering the settings and let Google’s utility handle the remainder — however in fact, that does imply your knowledge will likely be gone as soon as the replace is full.

Do not uncheck Wipe Machine if you happen to set up this construct on high of Android 15 QPR2

Do not forget about bootloader unlocking, which additionally wipes knowledge

One other factor to contemplate right here is that it’s best to positively unlock your bootloader earlier than making an attempt Android 16 DP1. We had just a few individuals who flashed the primary DP of Android 15 on high of Android 14 with out unlocking their bootloader first, they usually ended up with bootlooping telephones that could not be used till a lot later (because you want to have the ability to boot into Android, allow Developer choices, and activate OEM unlocking earlier than placing your telephone into bootloader mode and sending the Fastboot command to unlock the bootloader).

The method of unlocking a telephone’s bootloader triggers an automated manufacturing unit reset, so people who find themselves simply beginning out (and doing issues the appropriate means) will not want to fret about this, even when they have been on Android 15 QPR2.

Will this all the time be an issue with Android 16?

Most definitely, the truth that Google is requiring a manufacturing unit reset is proof that Android 16 DP1 is constructed from an older supply than Android 15 QPR2. This could possibly be a byproduct of Google’s accelerated timeline for Android 16, however it might simply be mounted in Android 16 DP2, and would possible be a non-issue by the point a public beta was launched.

All advised, it is a comparatively minor inconvenience, so long as you are conscious up entrance that you will lose knowledge with this replace — in spite of everything, it is simply one other small step in an already-tricky course of, and for lots of people, no further steps are wanted.