EDIT: You know, after some time to cool off, Google Authenticator 2FA can still be enabled and isn’t being phased out like the less secure SMS 2FA, so it’s really not the end of the world here. The chance of permanent lockout is avoided, even if the whole Google Prompt system is still wack.

  • Chozo@kbin.social
    link
    fedilink
    arrow-up
    3
    arrow-down
    2
    ·
    1 year ago

    Right. I think you can see where I'm going with this. The fact that you're being dodgy with the question is making me question your motives with this post.

    So, what device? You don't have to tell me the name, but describe it to me. Is it the device that you flashed a new OS onto?

    • doctorcrimson@lemmy.todayOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      It's not constructive to answer your question instead of explain the situation to you for the 8th time. There is only one device and it was wiped and can never be recovered, not even by restoring the OS, but the Google Prompt is still the default option forever now. I found this mildly infuriating.

      The best solution is to use something like Google Auth since only the SMS is being phased out. Do you understand now or de we need to repeat this again and again?

      • Chozo@kbin.social
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        1 year ago

        So, when you said "The device has never existed", you realize how that was a bit misleading, right? The way you've been presenting this situation would suggest that Google enabled 2FA in an impossible manner.

        The device existed. You ignored the warnings and wiped the device before transferring your authentication elsewhere. There's plenty of things to be critical of Google over, but flagrant user error like this isn't one of them.