Android 16 QPR2 Beta 3.1 Patch Released for Pixel Devices Facing Boot Issues
Google has released Android 16 QPR2 Beta 3.1, a patch specifically addressing a boot issue affecting Pixel devices that had “Enable desktop experience features” activated prior to installing the previous beta update.
The update, rolling out today, is available as two separate builds: BP41.250916.010 for Pixel 6, 6 Pro, and 6a, and BP41.250916.010.A1 for all other Pixel devices. The release follows a temporary pause of the over-the-air (OTA) update last week after reports of the bootloop issue surfaced; the new version is a relatively small download, measuring 2.64 MB on some devices. This issue highlights the risks inherent in beta software, where unexpected bugs can occur.
Google provides several recovery options for impacted users, including allowing the system to automatically revert to Beta 2 after multiple failed boot attempts. For those with USB debugging enabled via the Android Debug Bridge (ADB), sideloading the new OTA package is recommended. Users already in the Android Recovery page can perform a factory reset, with detailed instructions available on the Android developer website. Further assistance and troubleshooting can be found at the Google Pixel support pages.
While Beta 3 resolved numerous other problems, a separate bug causing the disappearance of certain lockscreen clocks remains. Google is expected to release a more comprehensive bug fix update in the coming weeks.
Google has not yet provided a timeline for a full resolution, but encourages users experiencing issues to follow the provided recovery steps.
Following last week’s release, Android 16 QPR2 Beta 3.1 is rolling out as a patch for Pixel devices that failed to boot if “Enable desktop experience features” was enabled before installing.
- BP41.250916.010: Pixel 6, 6 Pro, and 6a
- BP41.250916.010.A1: All devices
On our Pixel 9a already running Beta 3 and had no issues, this is just a 2.64 MB update. Google last week pulled the OTA. Today’s release notes do not have an updated entry for Beta 3.1.
Google lists several options for devices that “took the Beta 3 update, had… Settings > System > Developer options > “Enable desktop experience features” turned on, and are unable to boot.”
- Ideally, let the system recover itself back to Beta 2 after the system fails to boot a few times.
- If you have (ADB) USB debugging enabled in developer options before the bootloop
- Sideload the new OTA package update
- If you are on the Android Recovery page after the bootloop: Factory reset
- Factory wipe/reset from Recovery/Rescue mode
The full instructions are available here.
Beta 3 fixed a lot of problems, but there’s a bug with the loss of other lockscreen clocks. Google presumably has a bigger bug fixer update in the coming weeks.
FTC: We use income earning auto affiliate links. More.
