Pin not recognized after reboot

Leo_51

I can't log into my Pixel 6a and I don't know why. Could it be related to the update? After restarting, I was asked for my PIN, but it didn't work. I usually unlock my device with my fingerprint.

The timer is currently at 14500 and has dropped to 2000. After restarting the phone, I was able to enter the PIN without any delay, but it didn't work and the timer jumped back to 14500.

I believe the device received an update; perhaps that's the problem. What options do I have to investigate this further? Can I revert to an older version?

Novalissoide

Leo_51 Do a couple of restarts, just to help finishing any update procedure if these aren't completed yet.

Pocketstar

Leo_51 It could be your SIMcard pin instead?
But that should not trigger the timer I guess, merely a PUK-code request...

Perhaps turn off the phone, then remove the SIMcard, reboot and try again to see if that resolved the issue? (Or type the SIM-pin and after that your unlock pin)

I had a similar issue in the past myself until I realized it was my SIM pin, but nowadays I don't use SIMcards anymore for different reasons.

hemingway

Leo_51

Based on another thread I saw here recently, can you try the first four digits of your pin?

de0u

Leo_51 I can't log into my Pixel 6a and I don't know why. Could it be related to the update? After restarting, I was asked for my PIN, but it didn't work. I usually unlock my device with my fingerprint.

Fingerprint unlock is a secondary unlock method. After any restart, the primary credential (PIN or passphrase) must be entered.

Leo_51 I believe the device received an update; perhaps that's the problem. What options do I have to investigate this further? Can I revert to an older version?

For safety reasons it is not possible to roll back the installed version of the operating system, except by unlocking the bootloader, which, for safety reasons, will delete all user data on the device.

Based on the description so far, it seems that either you or the device has forgotten the PIN. It might be productive for you to write the PIN down on a piece of paper and have somebody else enter it. If the device has forgotten the PIN, which is genuinely very unlikely but not mathematically impossible, it will be necessary to "factory reset" it, which deletes all user data and enters the post-installation setup wizard.

Leo_51

Hopefully it will recover on its own; however, there are a few other options: clearing the cache in Fastboot mode or even reinstalling the image without deleting data.

Leo_51

Unlocking the SIM card is no problem, but unlocking the graphene is. The correct PIN is not accepted. According to AI, the possible explanation is that the secondary profile has not been updated and its old encryption keys are locking the entire system. Since it cannot read the keys of the secondary profile, it locks the system.

userofgos

Leo_51 According to AI, the possible explanation is that the secondary profile has not been updated and its old encryption keys are locking the entire system. Since it cannot read the keys of the secondary profile, it locks the system.

Please don't take AI seriously on these matters. They are inaccurate more often than they are correct and the hallucinate just like this response. There's no way it has any relation to secondary user profiles since as you mentioned in the OP you've restarted your phone numerous times.

GrouchyGrape

Leo_51 since the profile wasn't updated

This isn't how updates work. The entire system is updated, affecting all profiles. It's an all or nothing deal.

Leo_51 the connection was made via a mobile network, which is inherently insecure.

While it's true that there is potential for compromise through mobile networks to occur, this is extremely unlikely. Any exploits that do anything more than leak small amounts of data are reserved for very valuable targets (e.g. high level government officials).

Leo_51 According to AI

As others have said... just no. Please don't consult any AI on topics like this. They will sound very sensible, but I promise you they have no idea what they're talking about.

Upstate1618

Several possibilities
Your forgot your correct PIN
Someone else changed it(they must know your previous PIN
A bug in software or hardware causes this(very rare
Your using of adb or roor causes this(depends on what you did, I don't know if you ever used these tools to modify your system

hemingway

userofgos hallucinate

It isn't hallucinations - ime Google's AI will straight up lie to you if it can't provide an answer. They're trained to leave you with the impression that your question has been answered - as opposed to answered accurately.

Leo_51

I agree that AI is unreliable and am still looking for a solution. Another possibility would be a hacking attack or a security vulnerability, since the profile wasn't updated and the connection was made via a mobile network, which is inherently insecure.

Novalissoide

Leo_51 hacking attack or a security vulnerability

Before further speculative thoughts, you need to give us answers to some of our previous questions, and a few more, we're not going anywhere until you do just that.
Have you enabled developer options? Have Adb, root or Shitzuku been used, at any time for any reason? Is the bootloader relocked?

Leo_51

Novalissoide No, developer option is not enabled, I have not used adb or anything else, just regular use. After looking in the recovery log I have not seen any error with gatekeeper or keystore, however the timer delay now is 130000 secunds or 35 hours. This is not real time any more. This could be a bug introduced with latest release bluejay-install-2025112100. I have installed now through adb sideload beta release, 2025120400. I don't know if this is going to help.

Leo_51

de0u It's possible that I might enter the PIN incorrectly a few times, since I type it automatically, but it can't be wrong every time.

Leo_51

GrouchyGrape It is good to know that the update updates all profiles.

Leo_51

The problem started when my son tried to unlock the phone too often. When I tried to unlock it myself, my PIN wasn't accepted and the timer showed 30 seconds. Strangely, the waiting time doubled with each subsequent attempt. It's currently at 135,000 seconds, or 36 hours. Normally, you can enter the PIN ten times before the waiting time doubles.
When I restart the phone, I have the option to enter the PIN without waiting. However, the PIN is not accepted and the timer reverts to 135,000 seconds.

de0u

v-0-dka I have the exact same issue.

The original poster's issue was that a child repeatedly tried to unlock the device (Leo_51), then the correct PIN may have been entered incorrectly a few times (Leo_51). If the situation with your device is different, it would probably be best to start a new thread providing as many details as possible about the situation.

Leo_51

I don't understand why the phone allows PIN entry after a restart, even though the timer delay is currently 35 hours.

Novalissoide

Leo_51 try remove Sim, to rule out a conflicting code situation.

GrouchyGrape

Leo_51 this is a known bug. While it may appear like it's allowing you to attempt to enter your pin after a reboot, these are not genuine attempts and will be rejected, even if there correct pin is entered.

I strongly suggest writing down your pin, removing the sim, then leave your phone alone and wait until the timer runs down. Good luck.

Leo_51

Novalissoide I will do that, the timer is now at 27 hours.

Novalissoide

Leo_51 wish you all luck. That situation is depressing.