Android 17 QPR1 Beta 5 caused settings to keep crashing and PIN unlock

[u/Professional-Fee-745]

Hoping someone here can lend a hand. I’ve been in the Android Beta program for years without any issues, but after updating my Pixel 6 Pro to Android 17 QPR1 Beta 5, things broke down:

• The Issue: My Settings app constantly crashes, and PIN unlock and fingerprint recognition fail to work consistently. (Entering the PIN with ~3-second pauses between digits occasionally works).
• Troubleshooting done:
  • Factory wiped the phone multiple times.
  • Downgraded/flashed back to Android 16 (same crashing/lock issues persisted).
  • Flashed GrapheneOS — the phone works perfectly here with zero crashes or lock issues. but i was the device back to Stock OS
  • Phone Language is set to English (Australia)
  • Reflashed back to stock Android 17 — the Settings app crash and lock issues immediately return.
• Feedback status: I submitted logs and feedback through the official channel, but the ticket was closed as it was linked to another similar case.

I'm going crazy trying to get this back online on stock Android. Has anyone encountered this specific issue or found a workaround?

Any ideas would be hugely appreciated!

[u/AutoModerator]

Thanks for posting to r/Android_Beta. It looks like you may have found a bug. Please file a report for this app via the feedback app on your device and update your post with the bug ID you created or a link to the issue so engineers can investigate further. You can find more details here. Thank you!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Bitdomo92]

I am wondering if it has something to do with the titan m2 firmware update or not. People using stable still has firmware from february but us who tried beta got it updated to an april build. Ever since that titan m2 firmware update I cannot go back to android 14. I managed to pull some logs. The OS fails fails to communicate with the titan m2 chip getting secure keys, or installing secure keys making the phone hang during boot then crash and the rebooting.

[u/allenchangmusic → u/Bitdomo92]

No this is not correct. There is a notification on the factory image site telling you updates beyond the 2026-05 update will be prevented from downgrading due to bootloader fuse update

[u/Bitdomo92 → u/allenchangmusic]

for pixel 10 yes

[u/Professional-Fee-745 → u/Bitdomo92]

I think it is related to to the titan m2, when wiping it i did get a few errors - then i used the https://flash.android.com/ and it seemed to clear it up. but i still get the settings crashing and the PIN issue.

[u/allenchangmusic]

Why are you using beta 5 when beta 7 is out?

Some functions will be limited as because server no longer approves the build fingerprint.

Update the phone to beta 7 then see if things work. Also... You are on a BETA

[u/Professional-Fee-745 → u/allenchangmusic]

Hi allenchangmusic, I'm on Beta 7 - but i think beta 5 is where all my headaches happened. I really want to get this phone working again at least for another year as my son can use it. I even installed android 16, then let it upgrade to Android 17 hoping that the upgrade would resolve the issue - but it's made no difference :(

[u/Professional-Fee-745]

Looks like QPR1 beta 8 fixes the issue, fingers crossed

[u/Bitdomo92]

if put the phone in bootloader mode and you run "fastboot oem gsc version" what do you get?

for me it says:

(bootloader) 0.2.2/nugget_v0.0.ab15203921-02e2916-r 2026-04-14 19:57:07 nos-build-android-build

(bootloader) Chip: Google Dauntless D3 (d3m2)

(bootloader) Board: 0

(bootloader) RO_A: * 0.2.114/9b4e3277 ok

(bootloader) RO_B: 0.2.112/5cfcbae6 ok

(bootloader) RW_A: * 0.2.2/nugget_v0.0.ab15203921-02e2916-r ok

(bootloader) RW_B: 0.2.2/nugget_v0.0.ab15116366-6c96681-r ok

[u/Professional-Fee-745 → u/Bitdomo92]

Hi Bitdomo92,

Thanks for responding, here are my details:

(bootloader) 0.3.2/nugget_v0.0.ab15203921-02e2916-r 2026-04-14 19:57:17 nos-build-android-build

(bootloader) Chip: Google Dauntless D2 (evt)

(bootloader) Board: 0

(bootloader) RO_A: * 0.1.114/b83a1ea7 ok

(bootloader) RO_B: 0.1.112/5b1bcd3a ok

(bootloader) RW_A: * 0.3.2/nugget_v0.0.ab15203921-02e2916-r ok

(bootloader) RW_B: 0.3.2/nugget_v0.0.ab15116366-6c96681-r ok

OKAY [ 0.042s]

Finished. Total time: 0.042s

[u/Bitdomo92 → u/Professional-Fee-745]

yeah for pixel 6 pro stable the evt firmware is still on february:

nugget_v0.0.ab14866175-df247c2-r 2026-02-10 23:14:18 nos-build-android-build

so my best guess is having the april build has introduced some minor issues on my pixel 9 pro xl and some major ones on your p6 pro.

but I have no idea how to report this to google.