Bootloop on Pixel devices since March: Google apparently has a solution

Since Google released a major update to Android 16 QPR3 in March as a “Pixel Drop”, many users have been unable to use their Pixel smartphones. This is because since then, at least hundreds of Pixel devices – from the Pixel 6 series to the latest Pixel 10 series – have apparently been stuck in a reboot loop (bootloop). Google has been working on fixing the bug since then, but with modest success. Those affected are frustrated by their devices being useless for months; now, the first users have apparently received a solution tool from Google. According to reports, it doesn't work for everyone.

Long delay

The public issue tracker entry for the bootloop bug is now nearly 800 entries long. Users have been sharing their experiences with Google and other affected parties there since March. They write about their attempts to find a solution and the sometimes frustrating communication with Google, which offered some bootloop victims Google Store credit and a replacement device, but without recovering the data stored on their defective devices.

Google announced at the end of April that it was working on a solution that could save the devices without data loss. Google has apparently been distributing this solution to the first users since the beginning of June. It is a web tool for which affected users must connect their Pixel device to a computer with at least 7 GB of free space.

According to the dedicated website, the tool works on Pixel 3 or newer devices with Android version 10 and higher. It also does not support Android tablets or ChromeOS devices. According to the posts of the first testers, the Pixel device must be put into Fastboot mode and then into Rescue Mode. According to one post, the tool guides users through the process, and they only need to follow the instructions.

Google also states that the software is still a beta version. It is therefore quite possible that the company will soon share new, stable software. According to the post, testers do not need to worry about their data. It says: “Don't worry—this specific recovery process is designed to fix the bootloop without wiping your personal data. You can back up your files normally once the phone is working again.”

Some affected users report that their device was not recognized, so a rescue was not possible. As a solution, one person flashed an Android 17 beta, which made the Pixel smartphone work again. Another user reports on Reddit and in the issue tracker about a successful solution: He was able to start his device in safe mode. Then he activated location services, deactivated Wi-Fi, and removed all saved networks. Thereafter, according to his report, the device restarted normally.

However, the numerous posts from the officially over 400 affected users, according to the issue tracker, show that Google has not yet fully mastered the problem and cannot provide a universal solution. For those affected, this is a bitter experience with Google's hardware support. Google was unable to provide us with an official statement on the matter when requested at the beginning of last week.

It should be noted that the number of affected devices appears to be relatively manageable, but the company should fix devices with such serious errors more quickly and communicate more transparently.

(afl)