Google guarantees a rescue patch for Android 14’s “ransomware” bug

So Android 14 has this gorgeous horrible storage bug for upgrading customers. When you’ve got a number of consumer accounts in your system, upgrading to Android 14 can really lock you out of the system’s native storage, which creates an unimaginable variety of issues which might be all fairly much like getting hit with device-encrypting “ransomware” malware. Bugs are all the time going to occur, however the huge downside with that is that Google has seemingly been ignoring it, and on Friday we wrote about how customers have been piling up tons of of reviews for 10 days with out an acknowledgement or repair promised by Google.

Apparently another spherical of reports reviews was sufficient to get the gears transferring at Google. Over the weekend the Problem tracker bug has been kicked up from a mid-level “P2” precedence to “P0,” the very best precedence on the difficulty tracker. The bug has been assigned to somebody now, and Googlers have jumped into the thread to make official statements that Google is wanting into the matter. Here is the massive submit from Google on the bug tracker:

We’re conscious of a problem occurring on some Pixel gadgets (Pixel 6 and later fashions) which have each obtained the Android 14 replace and have a number of customers (apart from the first consumer) arrange. A number of customers embody customers, visitors, restricted profiles, and little one customers. Nevertheless, it doesn’t embody having a couple of Google account throughout the main consumer or work profiles.

Relying on the system, this problem may end up in the first consumer being unable to entry media storage. Alternatively, the difficulty can reboot the system with a “Manufacturing facility information reset” message. If this message is accepted, information that’s not backed up could be misplaced, and whether it is declined, the system repeatedly reboots with the “Pixel is beginning” message.

We’re persevering with to work on fixes for impacted gadgets, and have already pushed out a Google Play system replace that can assist forestall this problem from being triggered on extra gadgets. To examine if a Google Play system replace is obtainable on your system, comply with the directions on this Assist Middle article.

For those who’re experiencing this problem: In case your impacted system is unable to entry media storage, we anticipate a system replace will restore the difficulty and restore entry to media information with out requiring a manufacturing facility reset. In case your system is caught in a “Pixel is beginning” boot loop on account of this problem, we’re investigating strategies that might be able to get well some information. We’ll present extra info as quickly as it’s out there.

For customers who aren’t experiencing this problem, or have already manufacturing facility reset their system, we advocate avoiding creating or logging right into a secondary consumer on the system till the OTA replace is obtainable.

We’re sorry for the inconvenience this has precipitated, and we admire your endurance.

The highlights listed below are that Google says the bug impacts gadgets with a number of Android customers, not a number of Google accounts or (one thing we thought initially) customers with work profiles. Establishing a number of customers means going to the system settings, then “A number of customers,” then “Enable a number of customers,” and you’ll add a consumer apart from the default one. For those who do that, you will have a consumer switcher on the backside of the short settings. A number of customers all have separate information, separate apps, and separate Google accounts. Little one customers are in all probability the preferred cause to make use of this characteristic since you may lock youngsters out of issues, like buying apps.

Delivery a Google Play system replace as a fast Band-Assist is an fascinating answer, however as Google’s submit suggests, this doesn’t suggest the issue is fastened. Play system updates (these are alternatively known as Venture Mainline or APEX modules) enable Google to replace core system elements by way of the Play Retailer, however they’re actually not meant for essential fixes. The massive downside is that the Play system updates do not aggressively apply themselves and even let you recognize they’ve been downloaded. They simply passively, silently look forward to a reboot to occur to allow them to apply. For Pixel customers, it feels just like the horse has already left the barn anyway—like most Pixel telephones have mechanically utilized the practically 13-day-old replace by now.

Customers can pressure Play system updates to occur themselves by going to the system settings, then “Safety & Privateness,” then “System & updates,” then “Google Play system replace.” When you’ve got an replace, you will be prompted to reboot the cellphone. Additionally be aware that this differs from the standard OS replace checker location, which is in system settings, then “System,” then “System replace.” The system replace display will fortunately inform you “Your system is updated” even when you have a pending Google Play system replace. It could be nice to have a single location for OS updates, Google Play System/Mainline updates, and app updates, however they’re scattered all over the place and provides conflicting “updated” messages.

Lastly, it is excellent news that Google has an answer within the works for individuals who have already been locked out of their gadgets. A manufacturing facility reset has all the time been an answer that fixes the issue, however that may even erase all of your information, and a few individuals understandably do not wish to do this. For individuals caught in a “Pixel is beginning” boot loop, Google sounds a bit sketchier, with Google planning a repair that can get well “some” information.

We’ll let you recognize when any of those fixes come out. Google had higher get to work shortly, as some Android companions are already rolling out Android 14 to a a lot wider viewers. Samsung is rolling out Android 14 to the S23 in some areas immediately, and we actually do not know if this impacts Samsung telephones or not. Getting began on all of this 10 days in the past in all probability would have helped.