728 x 90

Google pauses Android Q beta rollout following ‘bootloop’ borkage

Google pauses Android Q beta rollout following ‘bootloop’ borkage

Android Q beta 4 is sending some Pixels to Borksville GOOGLE HAS BEEN FORCED to halt the rollout of its latest Android Q beta after some users suffered bootloop borkage. Early-installers have flocked to Reddit to complain that the fourth Android Q beta, released on Wednesday, is causing problems. Users – primarily those using Pixel 2 XL and Pixel

Google pauses Android Q beta rollout following 'bootloop' borkage

Android Q beta 4 is sending some Pixels to Borksville

GOOGLE HAS BEEN FORCED to halt the rollout of its latest Android Q beta after some users suffered bootloop borkage.

Early-installers have flocked to Reddit to complain that the fourth Android Q beta, released on Wednesday, is causing problems. Users – primarily those using Pixel 2 XL and Pixel 3 devices – have moaned that the update fails to install and instead throws their Pixel into a state of constant reboot. 

“Help! My Pixel 3 is stuck in a bootloop after trying to install the Q Beta 4. All I get is the Google logo with the progress bar underneath, been like that for 20 minutes now,” one user whined.

Another sobbed: “Same issue here. A good 30+ minutes to the first Factory Reset screen, and now I’m about 15 minutes into the second ‘G’ and progress bar that I expect to fail.”

Following these complaints, Google has taken, somewhat oddly, to Reddit to announce its temporarily pausing the update while it attempts to resolve the issue. 

“We’re aware of an issue with Android Q Beta 4 related to installing updates,” Google said. “We’ve temporarily paused Beta 4 OTA updates to all Pixel devices as we investigate the issue. We apologize for any inconvenience, and will provide an update once the issue is resolved.”

If you’ve already installed the update and your device is showing signs of borkage, Android Central has some tips for recovering your phone, though it might involve carrying out a full factory reset. 

Its first piece of advice is to “wait it out”, with some users reporting that the issue appears to resolve it out. If you’re not that lucky, try rebooting your device and, if you still have no joy, force your phone into recovery mode. 

If you’re unlucky enough that that doesn’t sort it out, you might be looking at a factory reset to get things back up and running. µ

Further reading

[ad_2]

Source link

Susan E. Lopez
ADMINISTRATOR
PROFILE

Posts Carousel

Leave a Comment

Your email address will not be published. Required fields are marked with *

Latest Posts

Top Authors

Most Commented

Featured Videos