Google Pixel: March update causes bootloops on some devices
Some Pixel users are reporting bootloops after the March update. Google has classified the issue as critical, but a solution is still pending.
(Image: Yasin Hasan / shutterstock.com)
The March update for Google's Pixel smartphones apparently contained more than just a bug: In addition to a freezing lock screen, some users' devices are stuck in a reboot loop (bootloop) after installing the Pixel drop (Android 16 QPR3) from early March. Google has now confirmed the error.
Factory reset doesn't help either
For weeks, some users have been struggling with the error, which apparently occurs on various models – from the Pixel 6 to the Pixel 8, and the Pixel 9 Pro and 10 Pro XL. This is evident from an entry with numerous complaints in Google's Issue Tracker. The number of affected users does not seem to be large and could be related to a nearly full device memory before the update was installed. This is at least suggested by the entries – but it is not confirmed.
So far, the manufacturer has advised resetting the affected devices to factory settings (Factory Reset). However, this involves the loss of all data not backed up on the device. Furthermore, user reports are circulating that the problem persists even after a factory reset. Google had released another small update with bug fixes in early April, but the update cannot be installed on devices with bootloops because they cannot be started – it is also unclear whether it fixes the error.
Videos by heise
Data recovery in safe mode
As Android Authority reports, some users have apparently managed to start their Pixel smartphones in safe mode while connected to the charging cable. This allowed them to create a backup of their data before the device fell back into the bootloop.
Small comfort: According to the issue tracker, Google's developers have addressed the issue and classified it with P0 priority. According to Google, this means it is a “problem that needs to be fixed immediately with as many resources as necessary.” However, it is uncertain how long it will take to resolve the issue.
Affected users may have to expect to visit a repair shop or send in their device due to the boot loop. We have asked Google for a statement on how to proceed. It has not yet been received at the time of this report.
(afl)
