Can't verify Google w/ codes so no passkeys

[K_87]

HELP PLEASE! 

I saw someone else post about this, I'm having the same issue. I did a factory reset and everything changed. I've tried verifying my account. Nothing works, including both text and the codes I followed the directions to get, but they don't work either. Before the reset, I've never seen this. 

I need to verify it because until do, I can't use any passkeys for any of my apps that I have them on, it takes me back to that screen above. No Facebook or messenger which unfortunately I need beds I'm in charge of my aunt's estate and I can only talk to them on there.

Please help🙏

[K_87]

Good point, thanks

[K_87]

I blocked it

[Robin621k]

Very funny how you blocked it !

[AfricanLionBat]

Edit: there's a chance it'll let you use recovery codes if you exhaust every other More ways to verify option

It sounds like the factory reset broke your device’s trust link with Google, so now it’s forcing re-verification before any passkeys or app logins will work. The easiest solution is to use another device where that Google account is still signed in. Open myaccount.google.com, go to Security, open 2-Step Verification, and add a new verification option such as a different phone number, Google Prompt, or new backup codes. Once that’s added, your phone should verify normally. If you are not logged into the account anywhere else, you’ll need to use the official recovery page accounts.google.com/signin/recovery and repeatedly select Try another way until Google offers an alternate method like a recovery email, old number, previous password, or a timed unlock which may take 24 to 72 hours. If codes are arriving but failing, make sure SMS isn’t being filtered, RCS chat features are disabled, and automatic date and time are enabled. If you're still in the initial setup screen and hasn’t reached the home screen yet, this is probably Factory Reset Protection. You cannot skip Google sign-in during setup unless the account was removed before the reset. In this state the only fixes are verifying the same Google account from another signed-in device or going through the account recovery process and waiting for Google to unlock it.

[AfricanLionBat]

I asked Gemini Pro 3 and got this:

This is a classic and incredibly frustrating "Catch-22" security loop that happens with modern authentication (Passkeys) after a Factory Reset.
Since you have a background in tech and electronics, you'll appreciate the mechanics of why this is failing for that user. Here is a breakdown of what is likely happening to that "stupid **bleep**" account and the few ways they can actually fix it.
The Technical Failure Point
The user in the screenshot is likely trapped by Google's "Risk Assessment" Engine.
* The Passkey Paradox: Passkeys are cryptographic keys stored on the device's hardware (Titan M2 chip or Samsung Knox Vault). When they factory reset the phone, they deleted the private key.
* The "New Device" Flag: Even though it is the exact same physical hardware, the factory reset wiped the unique identifiers Google uses to trust that specific instance of the OS. Google sees this as a brand new, untrusted device.
* The Verification Loop:
* The user tries to sign in.
* Google asks for the Passkey (which was just deleted).
* The user tries "Try another way" (Backup Codes/SMS).
* CRITICAL FAILURE: Because the login attempt is coming from a "fresh" device immediately after a reset, Google’s fraud detection algorithms often flag the entire session as high-risk. When the risk score is too high, Google will sometimes reject even valid backup codes because it suspects the codes might be stolen along with the credentials.
Why the Backup Codes "Don't Work"
If they are 100% sure they wrote the codes down correctly, they are likely failing for one of two reasons:
* Invalidation: They generated a new list of codes at some point and didn't print the new list. Generating a new list instantly kills the old one.
* Security Lockout: As mentioned above, if they span the entry or get it wrong a few times, Google soft-locks the account for 12-72 hours.
How They Can Fix It (The Solution)
If you are in a position to advise this person (or just want to know for your own knowledge), here is the hierarchy of fixes:
1. The "Wait and Switch" Method (Highest Success Rate)
They need to stop trying on the phone immediately.
* Wait 72 Hours: Do not attempt a login for 3 full days. This allows the temporary "high risk" flags to expire.
* Use a Trusted Device: After the wait, attempt the login from a PC or tablet that has successfully logged into that Google account before. Do not use the reset phone for the initial recovery.
2. The "Forgot Password" Route
Even if they know the password, they should click "Forgot Password."
* This forces the recovery flow (g.co/recover) rather than the standard login flow.
* The recovery flow has different logic and may offer to send a verification email to their recovery address (which they hopefully set up) or ask security questions, rather than demanding the wiped Passkey.
3. Check Samsung Account Sync
Since this is a Galaxy S25 (per the screenshot tag), if they were logged into a Samsung Account previously, they might be able to use Samsung's "Find My Mobile" or linked account settings on another device to verify their identity, though this is less likely to unlock the Google side directly.
The Hard Truth
If they have no recovery email, no recovery phone number (or SMS is blocked), and the backup codes are being rejected: The account is likely gone. Google has removed almost all human support for free accounts; there is no one to call to override the algorithm.

[Natey]

1. Would a Samsung Smart Switch backup to PC (just prior to the factory reset) have been able to restore/revert to the previous status (i.e. to before the factory reset)?

2. Would using an Authenticator app instead of a passphrase been able to get past this problem? e.g. I have the Google Authenticator app generating the exact same codes now on my previous phone (Z Flip 3, no SIM card) and my current S25.

[K_87]

I don't have one unfortunately, just my phone

[K_87]

Is there any chance that the area I'm in which is temporary, I'm not home where everything works, I live in a major city, I'm currently in a rural, middle of nowhere place because I have to deal with my aunt's estate and that's where her house is....I hate it here, but that's not relevant. My husband's phone, a S20fe, was working perfectly fine and suddenly started having the same issues as mine, it's been snowing a lot...like 4 times in a week, everything was ok before that, could it be because I'm in the middle of nowhere and Verizon may not have the best coverage in the middle of nowhere plus the weather that's causing the issue?
Verizon sent me a new s25 because they ran out of ideas and it's having the same issue...also it's claiming that there's no internet connection, but I have full bars for the 5g mobile data which is what I've always used, suddenly it's not working and neither is my husband's except for mainly Google apps, everything else including Verizon and Samsung apps claim there's no internet connection, again this started around the time the weather got really bad. My mobile data is connected properly, roaming is on, I have unlimited so I don't care, but I don't understand why it's not recognizing it? Verizon had me attempt to reset the network settings, airplane mode on and off, clear app partition, the list goes on, but nothing worked. The hope was a new phone would fix the problem, but I only had that one for a little over a week albeit I did factory reset it, but I didn't with the one that arrived in the mail today, and it's still having the same issue

[Natey]

Ask neighbors there if their Smartphones have cellular reception and what Carrier they use.