There are no other options. This is even more stupid than the phone number verification thing. Attemping to logging to Google Play Store on that wiped device (which previously was logged in to the account) doesn’t work either.
Luckily, this is a throwaway account, not much data of value was lost. FRP on the wiped device was also off.
But like, what is the point of this. Suppose, my phone got stolen. How am I supposed to log in to Google to initiate a remote wipe, if it ask for a verification code which is on the phone that the thief has?
Zero logic at all. 🤦♂️
Edit: And MFA was never enabled. Just to clarify.
If you’re logged in on a computer you can deregister the device in your security settings and it will use the other available authentication types.
I’ve always been able to select another way to verify my login.
I’m just gonna copy paste what I said to another user on another thread regarding this topic:
Okay, so I attempted to access it again. Its currently in a weird state of partial access.
I can “log in” but as soon as I try to access anything, say, Gmail, I get that screen again.
This is what the settings page looks like:
So its not totally locked out, but its not functional either, I’m not even on a VPN.
Notice, 2FA is off.
Then I click Gmail and get this:
I tap “more ways to verify” and get this:
I tap the only option, and it circles back to the previous screen.
They said to try again on a computer. All your screen shots are from a phone. You might get the same result, but we won’t know until you attempt it.
Wouldn’t “Desktop mode” work the same on a mobile browser?
I had the same issue just a week ago after resetting my phone. As was said here I had to deregister my device in Google, because they didn’t know that I had reset that device. For Google it was a complete new device in my hand, despite it still being the same phone after reset. That’s why Google tried to make me F2A on what it thought was my old device.
Only after removing the old device in Google on my computer was I able to login on it again.
I know this doesn’t directly solve your issue, and it might not help much now, but I wanted to share my experience just in case it’s useful.
When I had a similar problem after switching phones, what ended up helping was that I had 2FA enabled beforehand. In that case, after selecting the option to recover my account suddenly allowed me to receive a verification code via SMS—something that didn’t appear on the usual login screen, it was greyed out before selecting this option.
It probably won’t work if 2FA is disabled, but maybe it’s still worth checking if any recovery options that shows up helps. There might be a choice there that helps you resolve your problem as well.
In any case, good luck—I hope you’re able to get it sorted soon!
Have you tried reaching out to support?
Just to be very clear. This is happening because you didn’t have MFA active. I know it hurts to hear, but this is why you always migrate first, wipe the device second. MFA would’ve allowed you several methods for proof of ID. If your phone gets stolen, then thieves can’t even use the phone for anything. You can remote wipe and block the device, and it turns into paperweight. The device nukes your data then locks the bootloader.
The company used to have it set up so in order to trigger an audio alert using “Find My Device” so you could actually, you know, find your device, you had to have that device in your hand and respond to a security prompt.
It is my firm belief that Google employees never use their own products.
Reminds me of the joke: “I cant see clearly enough to find my glasses” 💀
I had this happen after I changed my unlock code and then locked myself out.
I imagine part of this is a conflict between their logic for reinstalling your settings and the fact that your credentials have been changed and you need to unlock them. The account restore workflow doesn’t have a path for people who recently changed their passcode but need to log in.
I ended up abandoning the process and starting over. But gave me the opportunity to try a new launcher.
I got the same directions to verify just yesterday. The directions aren’t correct, and there’s no way to do this as described.
That’s why they ask you to back up the recovery codes. Learn how to use your devices
This thread is full of insane people with insane workarounds to an issue they are alerted upon when activating 2FA.
Keep the recovery codes in a safe place - not on the same device.
