this post was submitted on 04 May 2025
222 points (95.1% liked)

Mildly Infuriating

39411 readers
906 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.

Rules:

1. Be Respectful

Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...

2. No Illegal Content

Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...

3. No Spam

Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...

4. No Porn/ExplicitContent

-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...

5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts

-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...

6. NSFW should be behind NSFW tags.

-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

7. Content should match the theme of this community.

-Content should be Mildly infuriating.

-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.

...

8. Reposting of Reddit content is permitted, try to credit the OC.

-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...

Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense

Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 2 years ago
MODERATORS
STRIKINGdebate2@lemmy.world
LillianVS@lemmy.world
Tenthrow@lemmy.world
222
Google requires me to find a "verification code" from my android device in order to log in; the device in question has already been wiped (factory reset). (sh.itjust.works)
submitted 23 hours ago* (last edited 23 hours ago) by throwawayacc0430@sh.itjust.works to c/mildlyinfuriating@lemmy.world
32 comments fedilink hide all child comments
 

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.

top 32 comments
sorted by: hot top controversial new old
[–] dustyData@lemmy.world 37 points 16 hours ago (1 children)

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.

[–] MicrowavedTea@infosec.pub 6 points 6 hours ago

You should enable MFA yes. But it's definitely not reasonable to expect a forced half-assed version of MFA that keeps changing when you DON'T enable MFA. OP should have migrated the account before wiping the phone but this behavior was not caused by them.

[–] yessikg@lemmy.blahaj.zone 22 points 18 hours ago

If you have more than one MFA method turned on, an option will show up to Try Another Way

[–] superfes@lemmy.world 56 points 23 hours ago (1 children)

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.

[–] throwawayacc0430@sh.itjust.works 26 points 22 hours ago (4 children)

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.

[–] y0din@lemmy.world 3 points 8 hours ago

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!

[–] MrQuallzin@lemmy.world 46 points 22 hours ago (2 children)

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.

[–] CmdrShepard42@lemm.ee 0 points 12 hours ago (1 children)

Wouldn't "Desktop mode" work the same on a mobile browser?

[–] janonymous@lemmy.world 10 points 21 hours ago

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.

[–] Witchfire@lemmy.world 5 points 22 hours ago (1 children)

Have you tried reaching out to support?

[–] sunzu2@thebrainbin.org 15 points 21 hours ago

Lol... This is Google we are talking about

[–] MicrowavedTea@infosec.pub 42 points 22 hours ago (5 children)

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.

[–] njordomir@lemmy.world 21 points 22 hours ago

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.

[–] Ibaudia@lemmy.world 6 points 20 hours ago

They're just called "backup codes" now. But yeah.

[–] LodeMike@lemmy.today 3 points 18 hours ago

Also, Google will outright not allow you to log in even with all authentication methods if it doesn't like your IP or browser.

[–] JasonDJ@lemmy.zip 3 points 22 hours ago (2 children)

Airplane codes? Was that an autocorrect for API?

[–] unmagical@lemmy.ml 9 points 21 hours ago

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.

[–] MicrowavedTea@infosec.pub 6 points 20 hours ago

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.

[–] LodeMike@lemmy.today 1 points 19 hours ago

You can't enable MFA without a phone number or a mobile device.

[–] spaghettiwestern@sh.itjust.works 15 points 21 hours ago* (last edited 19 hours ago) (2 children)

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.

[–] Rivalarrival@lemmy.today 2 points 11 hours ago

I found that I can't convince google assistant (via bluetooth headset) to find my phone unless my phone is unlocked. The only workaround I've found is to set a 1-second timer.

[–] throwawayacc0430@sh.itjust.works 5 points 20 hours ago

Reminds me of the joke: "I cant see clearly enough to find my glasses" 💀

[–] CosmicTurtle0@lemmy.dbzer0.com 5 points 19 hours ago

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.

[–] LodeMike@lemmy.today 3 points 19 hours ago

I also lost an account like this. Absolutely idiotic.

[–] kikutwo@lemmy.world 4 points 22 hours ago

I got the same directions to verify just yesterday. The directions aren't correct, and there's no way to do this as described.

[–] array@lemm.ee -2 points 21 hours ago (1 children)

That's why they ask you to back up the recovery codes. Learn how to use your devices

[–] red@sopuli.xyz 4 points 19 hours ago (1 children)

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.

[–] LodeMike@lemmy.today 2 points 18 hours ago

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.