Google on June 23, 2026, surprised the Android community by restoring Pixel 6 and Pixel 6 Pro eligibility in the Android 17 QPR1 Beta 5 rollout, after the devices were conspicuously absent from the previous beta. The new build, CP31.260608.007, is available for all enrolled devices starting from the Pixel 6 onward, but it carries a critical warning: a no-wipe downgrade to the stable channel is not guaranteed. This means anyone jumping into this beta should be prepared to lose their data if they later change their mind.
Build Details and Availability
The Android 17 QPR1 Beta 5, build number CP31.260608.007, includes the latest platform patches and is available over-the-air (OTA) to all devices enrolled in the Android Beta Program. Supported models now encompass:
- Pixel 6 and Pixel 6 Pro
- Pixel 6a
- Pixel 7, 7 Pro, and 7a
- Pixel 8, 8 Pro, and 8a
- Pixel 9, 9 Pro, 9 Pro XL, and 9a
- Pixel Tablet
- Pixel Fold
Factory images and full OTA .zip files are also available for manual flashing on the official Android Developers website. The update weighs around 400–500 MB for most devices, though the size may vary by model and previous build. Users on Beta 4 will receive an incremental OTA, while those coming from stable Android 17 will see a larger package.
The Pixel 6 and Pixel 6 Pro Return
The disappearance of the Pixel 6 series from Beta 4 last month sparked widespread speculation. Some developers feared that Google had cut support early due to the devices’ age, while others pointed to potential hardware or driver issues. Google never publicly explained the omission, but the Pixel 6’s return in Beta 5 suggests that whatever technical hurdle existed has now been cleared.
For Pixel 6 owners, this revival extends the usable life of a phone that originally launched with Android 12. It also indicates that Google’s QPR1 testing cycle will include the Tensor G1 chipset, ensuring that any framework or kernel-level improvements are validated on that generation. Users who sideload the OTA manually do not need an unlocked bootloader, but bootloader-locked devices must still be enrolled in the beta program to receive future updates.
The No-Wipe Warning: Why It Matters
The most important detail accompanying Beta 5 is the explicit caution that a downgrade to the stable public release may require a full factory reset. This is not unusual for late-stage QPR betas—when platform-level changes like partition resizing, updated bootloader rollback indexes, or new security keymapping are introduced, the device’s keystore and filesystem may become incompatible with earlier builds.
Specifically, if a user installs CP31.260608.007 and later opts out of the beta program, the next stable OTA could fail to install unless the data partition is wiped. The same risk applies when flashing a factory image without a wipe. Google advises that anyone who is not prepared to potentially erase all data should avoid installing this beta. For professional developers, this is an acceptable trade-off. For casual testers, it’s a stark warning.
Real-world reports from the Android Beta subreddit already confirm that several users attempting to leave the beta after Beta 4 encountered forced resets. With Beta 5, the rollback protection appears to be even stricter. Back up your files, photos, and two-factor authentication tokens before proceeding.
What’s Expected in QPR1 Beta 5?
Quarterly Platform Releases (QPRs) are not feature showcases; they are the vehicle that delivers the next set of bug fixes and polish to Pixel phones after the major Android OS launch. Android 17 having reached its platform stability, QPR1 Beta 5 focuses on resolving issues that emerged during earlier betas and on finalizing the code ahead of the stable QPR1 release expected later this year.
While Google has not published a detailed changelog as of this writing, beta testers can anticipate:
- Fixes for Bluetooth connectivity drops reported on Pixel 7 and 8 series
- Improved memory management that addresses launcher redraws
- Camera stability enhancements, especially for night mode processing
- Kernel-level tweaks that reduce jank and improve touch responsiveness
- Updates to system APIs that third-party apps rely on for background tasks
The build also likely contains the latest security patches, bringing the platform up to the June 2026 security bulletins. These monthly fixes address both high-severity vulnerabilities in the Android framework and closed-source vendor components.
Implications for Windows Enthusiasts
For the Windows-focused reader, Android 17 QPR1 Beta 5 matters more than one might think. Microsoft’s cross-device ecosystem—Phone Link, Nearby Share (now Quick Share), Intel Unison, and Windows Subsystem for Android (though deprecated)—relies on the stability and feature set of the Android platform on the phone side.
Testing beta builds ensures that integrations like:
- Notification mirroring in Phone Link
- Instant hotspot activation from Windows
- App streaming through Phone Link
- Clipboard sync and drag-and-drop file transfers
…remain fluid and do not break when the stable QPR1 release arrives. Historically, Google’s QPR betas have introduced Bluetooth stack modifications that temporarily disrupted Phone Link pairing. Enthusiasts who depend on these workflows are well-served to test Beta 5 on a secondary device or report any regressions through the Android Beta Feedback app.
Furthermore, developers building dual-screen experiences for Windows and Android (e.g., companion apps for creative suites or productivity tools) can use QPR1 Beta 5 to validate foreground service limitations and new permission models before the stable rollout.
How to Enroll and Install
Enrolling a device in the Android Beta Program is straightforward:
- Visit the Android Beta Program website.
- Sign in with the Google account associated with the Pixel device.
- Locate the eligible device in the list and tap “Opt in.”
- On the phone, navigate to Settings > System > Software update and check for updates. The Beta 5 OTA should appear.
The download will proceed automatically once the phone is on Wi-Fi and has sufficient battery. Manual flashers can find factory images on the Android Developer site.
What’s Next for Android 17?
QPR1 Beta 5 is one of the final stepping stones before the public release of the December Pixel Feature Drop. Google typically ships one or two more beta builds before the stable QPR1 arrives, each with progressively tighter release criteria. After QPR1, attention will shift to QPR2, which will enter beta by early 2027 and arrive as the March feature drop.
For the broader Android ecosystem, partners like Samsung, OnePlus, and Xiaomi will begin incorporating the QPR1 code into their own One UI and OxygenOS betas. Windows users running beta builds of other Android skins may see similar cross-device improvements down the line.
In the immediate future, testers should keep an eye on the Android Beta subreddit and Google’s issue tracker for any late-breaking bugs introduced in CP31.260608.007. The no-wipe warning is not to be taken lightly—a single ill-timed downgrade can result in hours of phone reconfiguration. But for those committed to previewing what’s next, Beta 5 represents the most polished taste of Android 17’s first quarterly milestone.