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 have more than one MFA method turned on, an option will show up to Try Another Way
I also lost an account like this. Absolutely idiotic.
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.
The most annoying part is you may get this for a previous phone even if you have registered a new phone. If you really want to avoid Google’s forced MFA the best way is to actually enable MFA and generate some airplane codes. Those can generally be used regardless of what Google asks at the time and you can store them offline or even memorize a couple. Probably not as secure but at least you won’t get locked out.
Also, Google will outright not allow you to log in even with all authentication methods if it doesn’t like your IP or browser.
This is a good reminder. I recommend everyone grab their takeout data every now and then, but also, print out the 6 codes and put them in a safe deposit box, safe, bury them in a ziplock bag inside of a coffee can in your yard, etc. Hopefully it will be a waste of your time, but if you need them, they’ll be there.
You can’t enable MFA without a phone number or a mobile device.
They’re just called “backup codes” now. But yeah.
Airplane codes? Was that an autocorrect for API?
Apparently they’re called backup codes now. I could swear they used to be called airplane codes (because they’re offline ig). It’s just some randomly generated 8-digit codes.
No. When you enable 2FA Google gives you about 10 backup codes that will always work regardless of if you have access to your authenticator app.
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.
on a computer
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
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 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.
It’s well known that Google does not tell you that it’s forcefully adding second factor to your account if you log into that account on an Android/iOS device/app.
