Locked out after OTA update on Pixel 10 Pro XL - correct password rejected (BFU)

DeletedUser996

wizoatk Context clues!

schweizer

pp2026 I don't have the expertise to audit the AOSP keyguard source code myself,

So do I. But with todays modern AI such as Claude it should at least point you whether in your relevant update there were modifications in the relevant code area. That would be step 1. Step two would be to find suspects for the error. I mean, the parsing of the string (your password) is probably just one line. Let AI tell you which characters are stripped and id one of them is part of your password. If you can file a substantial bug report I am quite convinced the GOS team would fix it quickly.

GrapheneOS

DeletedUser1034 There are frequent OS updates and it doesn't necessarily have anything to do with OS updates just because people noticed they couldn't log in after an OS update. Most of the people reporting a similar issue said they had just recently changed their PIN or password right before it occurring. We don't think most of it has been a bug. A small subset may be caused by a bug, particularly this one where they used special characters and it's possible Android changed how that's handled such as changing the Unicode encoding of what they entered, although we have no indication of that actually being the case. There's currently no confirmed issue.

grayway2

It's not a bug. The password is rejected only because it's not the right password.

Don't blame grapheneOS.

Your only option is to factory reset the device. No one can retrieve it.

My advice is to download something like KeePassDX and write the new password in the database. Use a strong password you know for years to protect the database and don't try to make that password harder, use what your brain can't forget.

pp2026

GrapheneOS
Thank you for the detailed response — that's helpful context.

de0u

DeletedUser1034 I'm a new user and a bit of a newbie in sec.

I'm also not great at backing everything up and know myself enough that I'll probably fail at some point.

This bug makes me a bit worried.

Many other things can go wrong, such as leaving a phone on a bus, being robbed, dropping the phone into a river, or the flash storage failing. Each one of them is probably more likely than a password going bad. Backups protect against all of them.

JeanLama

I had a very similar problem yesterday on a brand new Pixel 10 Pro. I flashed Graphene OS straight from the box,the Pixel crashed immediately after the grapheneos setup finished (I mean, the os setup, the flashing process seems flawless). Upon rebooting, it wouldn't accept my password, even though it was correct. I formatted the device, and I didn't have any problems since.

Stock os was still android 16.

« Previous Page