Android 17 is now stable and has been released to Pixel devices in recent days. By now, Beta testers are supposed to have had the opportunity to opt out and move to the stable release without performing a data wipe.
But the software has encountered numerous issues ever since the release, including widgets vanishing, search bar glitches, Wi-Fi issues, battery drain, and more. Now, the June Google Play System Update has another problem.
Android 17 broke this user's phone
A Reddit user in the r/GooglePixel community reported that the latest 105MB June Google Play System update sent their Pixel 9 into a bootloop, greeted by a “corrupted system” error that only a factory reset could fix.
Before that, they had been running Android 17 QPR0 Beta 4.1 and waiting for the stable Android 17 over-the-air (OTA) version.
A bootloop keeps devices stuck in an endless restart cycle. It powers on, tries to boot, fails, and restarts automatically over and over. The user has no control over it and cannot use the phone at all while it is happening.
This Play System update sent my Pixel 9 into a bootloop.
I got a ‘corrupted system' error and had to do a factory reset to get it working again. Has anyone else experienced this?
I was on Android 17 QPR0 Beta 4.1, waiting for the Stable 17 OTA that wouldn't wipe my data (oh, the irony!).
rodrigoswz, Reddit.
The only way out was a full factory reset, which erased everything the user had been trying to preserve by staying on beta. Other users described the same issue. One Pixel 9 Pro owner even said they tried many recovery attempts before accepting that a factory reset was the only fix.
A Pixel 6 Pro user on the same Beta 4.1 build confirmed the identical outcome, while one Pixel 10 Pro Fold owner got lucky when their device booted normally on the first reset attempt rather than requiring multiple tries.
Some people got even luckier avoiding a data wipe by sideloading the Android 17 QPR1 Beta 5 update. But it required some technical work. Those who couldn't find an OTA package for beta versions to sideload alternatively unlocked their bootloader to manually flash stable the software.
Sideloading may work for some users
If you are on Beta 4.1 and have not yet updated to the June Play System version, sideloading Beta 5 may be your best solution. However, the procedure requires a PC, a USB cable, Android Debug Bridge (ADB), and the OTA package file.
If your bootloader is locked, sideloading may not work at all, and you would need to unlock it first to flash the update manually, which itself triggers a wipe.
The update installs automatically, so you may not get a chance to act before it lands on your device. But sometimes, updates for the system may land without auto-installing.
The new version may appear in Settings > Password & Security > System Security > Google Play System update. Avoid it for now. Also, the Play Store auto-update toggle for apps will not block it since the update is pushed directly through Play Services, not the Play Store.
