Google's Android 17 QPR2 Beta 4 Links Fail With 404 Errors for Pixel Testers

Q: Are the unannounced XR glasses features in Android 17 secretly causing the mysterious Beta 4 download failures?

No. There is no evidence that Android 17’s XR glasses features are causing the Beta 4 download failures. What is confirmed is much narrower: Google’s official manual OTA links for Android 17 QPR2 Beta 4 are returning 404 errors on the download page, blocking sideloads and recovery installs. Multiple users and outlets reproduced the problem, and Google had not explained the cause as of Aug. 31. A 404 generally points to a hosting, publishing, or page-linking problem, or to files being pulled, not to a software feature inside the build itself. The XR-related material in Beta 4 is real, but it points in a different direction. Release notes and coverage show Beta 4 includes fixes for screen mirroring to USB-C XR glasses and for blank-screen behavior in smart-glasses 3D mode. That suggests Google is stabilizing XR support in the software, not that those features somehow broke the web delivery system for OTA packages. There is a plausible alternative explanation: Google may have temporarily removed or unpublished the files while checking for a separate issue. That would fit the 404 behavior, but it remains unconfirmed. It is also notable that automatic over-the-air delivery to enrolled beta users appears unaffected; the problem is specific to manual download links. So the mystery remains unsolved, but the available facts support a distribution or file-availability issue on Google’s side, not a hidden XR feature causing the failures.

1 articles · Updated · Android Authority · Aug 31

Google’s official OTA files for Android 17 QPR2 Beta 4 are returning 404 errors, blocking Pixel users who need to manually sideload the update.
Android Authority reproduced the failures on Google’s manual download page, and Reddit users said the broken links have persisted for several days rather than hitting only a few devices.
Manual installers are the hardest hit: one Pixel owner said a reboot loop left them unable to recover because the full OTA package could not be downloaded.
Google has not explained whether it pulled the files intentionally or whether the outage points to a problem with Beta 4 itself, which otherwise shipped fixes for overheating, reboots, Bluetooth call audio and Face Unlock.