Android 14 Storage Bug Has Users Locked Out of Their Devices

An anonymous reader quotes a report from OPP.Today: Android 14, the latest operating system from Google, is facing a major storage bug that is causing users to be locked out of their devices. This issue is particularly affecting users who utilize the "multiple profiles" feature. Reports suggest that the bug is comparable to being hit with "ransomware," as users are unable to access their device storage. Initially, it was believed that this bug was limited to the Pixel 6, but it has since been discovered that it impacts a wider range of devices upgrading to Android 14. This includes the Pixel 6, 6a, 7, 7a, Pixel Fold, and Pixel Tablet. The Google issue tracker for this bug has garnered over 350 replies, but there has been no response from Google so far. The bug has been assigned the medium priority level of "P2" and remains unassigned, indicating that no one is actively investigating it.

Users who have encountered this storage bug have shared log files containing concerning messages such as "Failed to open directory /data/media/0: Structure needs cleaning." This issue leads to various problematic situations, with some users experiencing boot loops, others stuck on a "Pixel is starting..." message, and some unable to take screenshots or access their camera app due to the lack of storage. Users are also unable to view files on their devices from a PC over USB, and the System UI and Settings repeatedly crash. Essentially, without storage, the device becomes practically unusable.

Android's user-profile system, designed to accommodate multiple users and separate work and personal profiles, appears to be the cause of this rarely encountered bug. Users have reported that the primary profile, which is typically the most important one, becomes locked out.

No links to the actual issue!?

[NFN_NLN]

> The Google issue tracker for this bug has garnered over 350 replies, but there has been no response from Google so far.

https://issuetracker.google.co... [google.com]

Re:

[AleRunner]

So, like, it's linked right there in TFS. Failed reading comprehension at school?

You have to admit that "randsomware" is not the most obvious link title for the issue tracker, in fact it's exactly the link I would instinctively ignore given the word chosen and since it's a single word link it's less obvious than it could be. I hate to be forgiving of NFN_NLN, since I'm not 100% sure we're politically aligned and it's outdated to be polite to people who don't agree with you on every single little thing, especially sunny side up or down, but the comment is fine.

Re:

[NoWayNoShapeNoForm]

> The Google issue tracker for this bug has garnered over 350 replies, but there has been no response from Google so far.

https://issuetracker.google.co... [google.com]

It's NOT A BUG. It is a new security feature.

Re:

[AleRunner]

It's NOT A BUG. It is a new security feature.

I really can't tell if you are joking or not any more. Are they trying to force everyone to use secondary profiles?

It seems you should be able to get into developer mode and use one of the android backup tools on GitHub to copy the contents off, test restore to another device, then reset the original device and get your data back. This seems to be a problem for people who don't have a backup of their phone they can recover from.

Re:No links to the actual issue!?

[itsme1234]

people who don't have a backup of their phone they can recover from

That is nowadays basically all Android users [reddit.com].

Re: No links to the actual issue!?

[anonymouscoward52236]

Google's official response will be: you know what? Our project graveyard is looking a bit lonely and could use a new friend like, the entire Android project.

Re:

[velinion]

The bug is assigned to someone, and it's rated P0 (highest) in priority, and S0 (highest) in terms of severity. That's a pretty strong response. They could have downplayed it by reducing the severity or priority, but they're owning it.
Any textual statement doubtless needs to be vetted by PR, and go through Legal, and a bunch of other BS, but those assignments didn't.

Really wish I could read the post-mortem on this one though. Whatever bug triggered this must have slipped though so many unit tests and phas

Quit complaining

[93 Escort Wagon]

Google is simply taking security to the next level!

Oh no!

[EvilSS]

That is terrible. Well I guess you will just need to buy a new device. Sorry!

-Google

Structure Needs Cleaning

[bill_mcgonigle]

Maybe adb boot a LineageOS recovery image and run fsck on rhe mmc?

Is it f2fs?

Re:

[itsme1234]

You can't boot anything else (as in you don't have the keys to sign it) without wiping the storage, because you know ... "for your security"...
Even if you boot the storage is encrypted with keys you don't have ... "for your security".

mdcrypt, on-disk keys, adb/fastboot, twrp, oh my.

[gavron]

Maybe adb boot a LineageOS recovery image and run fsck on rhe mmc?

Is it f2fs?

Maybe except you probably mean "fastboot boot" and even so that's for a recovery image (like TWRP) not a full OS. There's a reason you can't boot an OS image using fastboot boot and really I'd love to get downvoted by spending a page describing it... but let's go with "it's complicated, whereas the recovery image is all self-contained."

The problem here is corruption of the mdcrypt key. The whole point of how md does encryption is unless you have a working key you can't add a secondary key. So if you're s

It's Google

[freitasm]

It's not surprising. Google support is non-existent. Many times I've asked for support and even on a Google Workspace paid account I was told to "ask the community".

Re:

[should_be_linear]

they are disrupting the core idea of "support",which old-fart companies used to provide.

Google Lockout -- Surprise

[BoRegardless]

Now are people going to run to iPhone's?

Re:

[JThundley]

iPhone's what?