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.
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!
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?
Nope.
You mean a web browser? Those exist on mobile devices too.
A web browser is not a computer. A phone is not a desktop computer. Google (and most other large companies) keep many features restricted to their full websites, not mobile apps and mobile versions of their sites. For those who are used to/grew up with smartphones, tablets, and chromebooks, these tactics help to make it harder to leave their ecosystems as they aren’t used to navigating desktop environments.
(Chromebooks do give desktop versions of websites by default, but they have helped reduce technological literacy in exchange for convenience)
On a computer or device that the device and browser is already signed into.
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.
Have you tried reaching out to support?
Lol… This is Google we are talking about