– Google Pixel 6 to 10 users face a boot loop/restart error since March.
– The May update did not fix the issue for all affected devices.
– Some phones cannot even boot into recovery mode to install updates.
– Google is investigating but has no blanket fix; support must be contacted for case-specific steps.
– Avoid installing Android 17 beta, as it may worsen the problem.
It has been over two months since we first reported it, and since the March update was released, a growing number of Google Pixel 6 through to the Pixel 10 users have been complaining about an error causing the smartphone to restart repeatedly. These affected Google Pixels either only display the Google logo or the boot screen, or crash right after the pin code has been entered, which is a real pain for most people.
May update was supposed to help
The May update was intended to provide a fix, but unfortunately this did not work for everyone. An additional issue is that some affected smartphones can’t even boot into recovery mode, so there is no way to install the update in the first place. Over 800 comments from affected customers have now been published in the Google Issue Tracker, showing the scale of the problem.
Google’s email response
Google has now informed customers via email that the error has been under investigation since March. The company says they have compiled a guide showing the steps which can be taken to fix the problem under certain circumstances. Instead of publishing these instructions on a website, affected customers should contact Google support to recieve information on the solution, which seems like a weird choice.
- The next steps depend on how exactly the error manifest itself on your smartphone
- There is still no blanket solution for all affected devices
- Anyone with this problem apparently has no option but to contact support
Warning about Android 17 beta
It is important not to install the beta version of Android 17, as according to several user reports this can lead to further problems and make things even worse. The whole situation remains frustrating for many users, who have been waiting for a proper fix for months.