Google Addresses Pixel 6 Factory Reset Error - Here's What You Need to Know

Google Addresses Pixel 6 Factory Reset Error - Here's What You Need to Know

Relief may be coming soon for Google Pixel users suffering from the Pixel 6 brick, as Google has released an official response on what users can do to avoid their phones from becoming bricked while the company works on a fix.

The first glitch occurred when users tried to restore their Google Pixel 6, Google Pixel 6a, and Google Pixel 6 Pro to factory settings; they received an error message saying Android could not be loaded. 'Data may be corrupted. If you continue to receive this message, you may need to perform a factory data reset and erase all user data stored on this device," the message continued.

Google then issued some advice on how to work around the issue, adding that it is considering a permanent solution to the problem; Google recommends leaving the device powered on and idle for 15 minutes after a reboot after a system update Google recommends leaving the device powered on and idle for 15 minutes after a reboot following a system update. After that time, a factory reset of the phone can be performed. Alternatively, Google recommends resetting the phone to factory conditions before downloading a recent system update.

Unfortunately, this does not help much for users whose phones have already been bricked after attempting the update. Google is asking users to bookmark this thread for an eventual fix. Currently, there is no mention of whether this glitch qualifies as a warranty issue, but some users mentioned that Google Support mentioned this option in the original support thread.

While the cause of this glitch is not well understood, it is important that users do not attempt to reset their device to factory conditions again when the glitch occurs. If they do, they will receive a message that an important file cannot be found. It is annoying to have to wait, especially since the most common reason for performing a factory reset is to sell the phone, but it is better than breaking the device.

It is good that Google is trying to resolve this issue, and the relatively quick response is encouraging. However, a full resolution is likely to take some time yet.

Categories