The latest Android 17 QPR2 beta for Pixel devices appeared to be rolling out smoothly late last week, but the experience for users who prefer to manually install the update has been anything but smooth. Google's official OTA download links are now returning 404 errors, leaving Pixel testers unable to sideload the build and, in some cases, unable to recover devices that have fallen into reboot loops.

Android 17 QPR2 Beta 4 was made available to Pixel testers over the past few days, promising fixes for several long-standing issues. According to the release notes, the beta addresses overheating problems, unexpected reboots, broken app drawer search, Bluetooth call audio issues, notification shade failures, and Face Unlock problems. For many users, the update is a welcome step toward a more stable Android 17 experience. But for those who rely on manual downloads, the rollout has become an unexpected obstacle.

What is Android 17 QPR2 Beta 4?

Google uses quarterly platform releases, or QPRs, to deliver feature drops and stability fixes in between major Android releases. These betas are part of the Android Beta Program and are intended for developers and early adopters who want to test new features and ensure their apps work with upcoming software. QPR2 Beta 4 is the fourth beta in the second quarterly release cycle for Android 17. It is not a full public release, but it is an important checkpoint before the final QPR2 build is pushed to all supported Pixel devices.

The update is particularly notable because it includes fixes for a number of annoying bugs that have affected Pixel owners throughout the Android 17 cycle. Reports from beta users have included excessive heat during normal use, random restarts, and problems with essential system interfaces. Fixing these issues before the stable rollout is a key reason why Google runs a beta program in the first place.

Manual OTA downloads returning 404

Manual sideloading is a common method for testers who do not want to wait for the over-the-air update to reach their device. Instead of relying on the automatic rollout, users can download the full OTA image from Google's developer portal and apply it using Android's recovery tools. This is especially useful for users who have already enrolled in the beta program but have not yet received the update, or for those who need to restore a device that will not boot normally.

That process has now hit a wall. When testers attempt to download the Android 17 QPR2 Beta 4 OTA package from Google's official manual download page, they are greeted with a 404 error. The message indicates that the requested file is not available on the server. The issue has persisted for days, according to affected users, and has not been resolved with simple browser refreshes or alternate network connections.

One Reddit user described a particularly difficult situation: their Pixel was stuck in a reboot loop, and they were unable to access the OTA file needed to recover it. Manual sideloading is often a recovery path for devices that are not functioning properly, so the broken links leave these users with few options. Instead of a straightforward fix, they may have to wait for Google to restore the files or resort to factory resetting their device.

Is this an isolated problem?

No. The 404 issue appears to be widespread. Reports have surfaced from multiple Pixel owners across different models and regions. An independent check of Google's manual download page returned the same 404 errors for Android 17 QPR2 Beta 4 OTA images. That makes it unlikely that the problem is caused by regional server issues or individual account problems. It also means that the files may have been removed or invalidated server-side.

The timing is especially unfortunate because OTA downloads for beta builds are occasionally pulled when a critical bug is discovered. Google has not provided any explanation yet, so it is impossible to say with certainty whether the missing files are related to a problem with Beta 4 itself or simply a technical issue with Google's download infrastructure.

Pixel device support

The Android 17 QPR2 Beta 4 rollout is not available for every Pixel device. According to the original update notes, the Pixel 6 and Pixel 6 Pro remain unsupported, which means users on those devices cannot participate in the QPR2 beta. Meanwhile, Pixel 11 devices have not yet received QPR2 support, so owners of the latest Pixel hardware are also left out of this particular beta cycle. The supported list includes a range of Pixel models between those generations, though Google has not always made the exact list easy to find on the manual download page.

Device support can vary from one beta release to another, and Google sometimes adds or removes devices as the beta program evolves. Pixel users who are unsure whether their device is eligible should check the official Android Beta Program page or wait for the automatic update to arrive. However, with the manual download links broken, even users with supported devices cannot currently obtain the OTA package through the official channel.

What could be causing the problem?

There are several possible explanations for the 404 errors. Google may have accidentally invalidated the URLs when updating the download portal. The OTA files may have been pulled because of an issue discovered after the initial rollout, even if Google has not announced it. Or the company could be in the middle of updating the files to a slightly newer build, with the old links temporarily disabled in the meantime.

It is also possible that the beta files are still available through other channels, but testers are strongly encouraged to use official downloads whenever possible. Installing an OTA package from an unofficial source carries additional risk, as the files may not be signed by Google and could lead to security or stability problems. Given that the entire purpose of the beta is to test software in a safe way, sideloading unverified builds is not a good idea.

Google has not publicly acknowledged the outage on forums or social media. The company's developer support channels have not issued a statement, and there is no estimate for when the manual downloads might return. We have reached out to Google for more information about the broken OTA download links and will update this article if the company provides an explanation.

Source: Android Authority News