Android 17 QPR2 Beta 4 Fixes 16 Bugs, but Its OTA Downloads Are 404ing

Google released Android 17 QPR2 Beta 4 on August 31, closing out more than 16 bugs that have dogged eligible Pixel phones, including thermal throttling, unresponsive gesture navigation, and Face Unlock failures in low light. But hours after it went out, the official OTA download links needed for manual installation started returning 404 errors, leaving some testers unable to sideload the build or recover a device stuck mid-update.

What Beta 4 actually fixes

This build is smaller in scope than the previous one, but the bug list is long. Google says it resolves gesture navigation that stopped responding, battery charging that failed to complete, audio routing glitches, and Face Unlock misfiring in dim rooms. Thermal management also gets a pass, which should help phones that were running hotter than expected under QPR2 Beta 3.

On the feature side, the Privacy Dashboard now logs Private Compute Core activity, and a new Agents dashboard groups the permissions granted to Gemini and other on-device AI agents in one place. There is also a Voice broadcast Quick Settings tile, a consolidated Notification Intelligence menu that folds AI summaries, notification organizing, and cooldown controls into a single screen, plus new wallpaper and style badges and extra status bar customization options.

Pixel 11 support is coming, just not in this build

Google has prepared a QPR2 build for the Pixel 11 line, tagged CP41.260814.003.C2, but it has not shipped to those phones yet — Google says it is coming soon. Every other eligible device gets Beta 4 today: Pixel 6a, 7, 7 Pro, 7a, Tablet, Fold, 8, 8 Pro, 8a, 9, 9 Pro, 9 Pro XL, 9 Pro Fold, 9a, 10, 10 Pro, 10 Pro XL, 10 Pro Fold, and 10a. The Pixel 6 and 6 Pro are not on the QPR2 beta at all.

Manual OTA installs are broken right now

If your phone is enrolled in the Android Beta program, it should pick up Beta 4 automatically over the air. The trouble is with the manual route: Google's developer download pages for the full OTA image are returning 404 Not Found errors, which blocks the sideload method testers normally use to install a build without waiting for the staged rollout, or to recover a phone that failed to update.

At least one tester reported their device got stuck in a reboot loop after the recovery OTA file it needed came back as a 404. Google has not said publicly whether the missing files are a temporary hosting problem or a deliberate pull, and has not given a timeline for restoring them.

What to do if you're affected

• If your phone updates automatically through the Beta program, you likely don't need the OTA page at all — let the staged rollout reach your device.
• If you specifically need the manual OTA or factory image right now, expect the download links to fail until Google restores them.
• If a device is stuck mid-update because the recovery file 404s, avoid repeated reboot attempts, which can compound the loop; wait for Google to fix the links rather than trying alternate unofficial sources.
• Pixel 11 owners should hold off checking for QPR2 today — the build for that line has not gone out yet.

Android 17 QPR2 is aimed at further stabilizing the OS ahead of its next quarterly platform release, and Google has been shipping roughly monthly beta builds to get there. The Motion Assist carsickness feature that landed in an earlier Android 17 build is a good example of the kind of smaller addition these interim betas carry alongside bug fixes.