Google‘s relentless pace of software updates continues! Hot on the heels of this week’s Pixel Feature Drop, the company has already launched Android 14 QPR3 Beta 2 for eligible Pixel devices (Pixel 5a and newer). 

The newest beta should squash several bugs from last month’s release, but early reports suggest it comes with a major caveat.

Android 14 QPR 3 Beta 2 Update

Android 14 QPR3 Beta 2 addresses some frustrating hiccups from the initial QPR3 beta. This includes device crashes during specific events like app updates or switching users, displays failing to wake after a reboot, always-on display malfunctions, and the disappearance of battery status information. Additionally, backup and restore processes should now function as intended.

These are the bug fixes in the Android 14 QPR3 Beta 2 update:

– Fixed an issue that sometimes caused a device to crash or restart unexpectedly.
– Fixed an issue that sometimes caused a device to crash or restart unexpectedly while updating apps after the device was flashed.
– Fixed issues that caused a device to display a blank, black screen after booting from flash.
– Fixed an issue that caused a device to crash and display a blank, black screen after switching to a secondary user.
– Fixed issues when always-on display mode was enabled that interfered with the “Double tap to wake” gesture and prevented the device from unlocking if the user tried to use their fingerprint to unlock the device.
– Fixed an issue that sometimes caused battery information to not display correctly in the system settings, status bar, and on the lock screen.
– Fixed issues that prevented device-to-device transfers and backup and restore from working.

Android 14 QPR 3 Beta 2 is bricking Pixel phones

Unfortunately, it looks like these fixes come with a serious risk. Multiple sources, including 9to5Google, have reported that sideloading Android 14 QPR3 Beta 2 can soft-brick Pixel devices, meaning they cannot fully boot. 

Even Google’s upcoming flagship, the Pixel 8 Pro, and the foldable Pixel Fold aren’t immune to this issue.

While the temptation to get those bug fixes immediately might be strong, it’s better to hold off on sideloading for now. 

The OTA (over-the-air) update appears to work without encountering the bricking issue. If you absolutely must sideload, AndroidPolice’s report suggests that users should make sure the ‘OEM Unlock’ option is enabled in the device’s developer settings as a precaution.

But for now, it seems best to avoid sideloading, particularly if you rely on your Pixel phone as your primary device.

Related:

RELATED ARTICLESMORE FROM AUTHOR