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.

  • dustyData@lemmy.world
    link
    fedilink
    English
    arrow-up
    39
    ·
    21 hours ago

    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
      link
      fedilink
      English
      arrow-up
      6
      ·
      11 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.