Lost the Phone With Your Authenticator App? Get Back In

The fastest way back in depends on what you still have, not on which app you used. First, lock or erase the lost phone while you still can. Then, if your authenticator app was signed in to an account or backed up, set it up again on a new phone: Google Authenticator (signed in to a Google Account) and Microsoft Authenticator (cloud backup on) both document restoring codes this way. If it was never signed in or backed up, the codes left with the phone. Use another second step you still have (another signed-in phone, a passkey, a security key, a phone number), then saved backup codes, and only then the account's own recovery, which Google and Apple say can take days. Work down the table below; each row names the vendor page it comes from.

What should you do first?

Secure the lost phone. Google's Authenticator help says to "immediately ensure that any codes stored on the device cannot be accessed by others" and points to remote erase. On Android, use Find Hub's "Mark as lost" first, which "Locks your device with your PIN, pattern, or password"; Find Hub needs the phone to still be signed in to your Google Account, so do this before you sign the phone out anywhere. On an iPhone, use Apple's Find My.

What do you still have?

Two things decide which row you are in. The Google Authenticator split cannot be changed after the phone is gone: either the app was signed in before the loss, or its codes left with the phone. And signing in to your Google Account or Microsoft backup account on the new phone can itself ask for a second step. If the lost phone was that second step, use the "another second step" or backup-code rows for that account first.

Backup codes come after the other second steps because each code works once. For sites other than Google, Microsoft and Apple, use that site's own two-factor recovery; backup codes on other sites can differ in length and flow.

Can you get Google Authenticator codes back on a new phone?

Yes, if the app was signed in to a Google Account before you lost the phone. Google: "When you sign in to your Google Account within Google Authenticator on a new device, your codes are automatically synced to this device." Sync needs version 6.0 or later of the app on Android, or 4.0 or later on iOS.

If you had chosen "Use without an account", the codes never left that phone. Google says this "will remove codes from all of your Google Accounts and store them on your device. Codes will not be available on your other devices." The only other transfer Google documents needs the old phone: it shows a QR code under Transfer codes, Export codes, and the new phone scans it. Without the old phone, Google's instruction is that "you need to visit every site that you have Google Authenticator set up on to remove the codes, and then relink your new device." You need to get into each site first, with another second step, backup codes or that site's recovery.

Can you get Microsoft Authenticator codes back on a new phone?

Yes, if backup was on before the loss, and only onto the same kind of phone: Microsoft says "accounts backed up using an iOS device cannot be restored on an Android device." On Android, Microsoft's restore steps say to "select Restore from backup. Sign in to your recovery account using the personal Microsoft account you used during the backup process." On an iPhone, the backup lives in iCloud; follow Microsoft's iOS steps on the restore page, signed in to the same Apple Account.

What comes back depends on the account. Microsoft's backup page says the codes restore for personal Microsoft accounts that use a one-time password code and for third-party accounts such as Amazon, Facebook or Gmail. For work or school accounts, and personal accounts set up for passwordless sign-in, only the account name is backed up, so you sign in to those again (for work or school, through your organization).

Microsoft's backup page also dates a change: "Starting January 2027, you will no longer use your Microsoft personal account to enable backup. You will need to enable 'Microsoft Authenticator' from Google One backup." That applies to Android.

Does Apple's Passwords app bring your codes to a new device?

It can, through iCloud Keychain, if Keychain was on before the loss. Apple's iPhone guide keeps verification codes for two-factor sites in the Passwords app. Apple's Keychain page says Keychain keeps "your website and app passwords and passkeys, credit card information, Wi-Fi network information, and other account information up to date across all your approved devices", and that it syncs "to provide convenience and redundancy in case you lose a single device." Apple does not name verification codes in that list, so after the new device syncs, open each account in Passwords and check that its code is there. Menu names here follow the iOS 27 guide, current on September 28, 2026.

If you still have another Apple device, approve the new one from it. If every device with Keychain is gone, Apple's escrow route is to "authenticate with your Apple Account on a new device, then respond to an SMS sent to a trusted phone number." Apple then asks for the passcode of a device that used Keychain and allows only 10 attempts; after several failed attempts, "the record is locked" and you must contact Apple Support. Do not guess. If the trusted number was on the lost phone, have your carrier move the number to a new SIM first.

What if another second step still works?

Google's page for a lost or stolen phone lists what still counts: "Another phone signed in to your Google Account", a backup phone number, "A backup code you previously saved", a hardware security key, or "A passkey created on another device." It adds a trusted computer: "If you previously signed in from a device and checked the box next to 'Don't ask again on this computer,' you might be able to sign in from that device without a second verification step." For a number that lived on the lost phone: "If you lose your phone, you can ask your carrier to transfer your phone number to a new phone or SIM card."

What if you saved Google backup codes?

Sign in, click "Try another way", then "Enter one of your 8-digit backup codes." Each works once: "after you use a backup code to sign in, that code becomes inactive." Once you are back in, make a new set; Google says "when you create a new set of codes, the old set automatically becomes inactive."

Nothing works: how long does account recovery take?

• Google. The lost-phone section sends you to Google's account recovery. Google gives a time only in its lost-security-key section, for anyone with no other second step: "it can take 3-5 business days for Google to make sure it's you."
• Microsoft. Microsoft's recovery form "will review your answers and respond within 24 hours", but it sets a hard limit: "if you have turned on two-step verification and cannot access any of the alternate methods to get a verification, we cannot help you, sorry."
• Apple. Apple says recovery can take several days or more, and "Contacting Apple Support can't help you shorten this time." It also says to "Turn off all other devices that are currently signed in with your Apple Account until account recovery is complete", because "If your Apple Account is in use during your request, your account recovery will be cancelled automatically." If you started recovery in Settings, System Settings or the Apple Support app, you can keep using that device; if you started it on the web, Apple says to turn that device off too if possible.

Once you're back in, what should you clean up?

The lost phone stays a live credential until you remove it.

• Google. Change your Google Account password, as Google's lost-phone steps say. Then in Google Account, Security, Your devices, Manage devices, select the lost phone and choose Sign out under "Account Access", which removes "access to your Google Account and connected apps on your device." Lock it with Find Hub before this step, not after.
• Microsoft Authenticator. Tell Microsoft to forget the old phone: for a personal account, go to the two-step verification section of your Account Security page and "choose to turn off verification for your old device"; for work or school, use My Apps or your organization's company portal. Microsoft's FAQ says "you must both delete the app from your old device AND tell Microsoft or your organization to forget and unregister the old device"; with the phone gone, the unregister step is the one you can do.
• The new phone. Turn on sync or backup in its authenticator app, so a future loss is the first row of the table, not the last.
• Google backup codes. Make a fresh set; the old set stops working.

Setting this up before a loss rather than after one? What to set up before you switch to an authenticator app has the checklist.

Where does MagicLess fit?

MagicLess does not read authenticator apps, so nothing above runs through it. When a recovery step sends a code or a sign-in link by email to a Gmail inbox you connected, MagicLess can offer it on the page while you sign in from Chrome on a computer; it never submits the form for you.

FAQ

Can I recover Google Authenticator without my old phone?

Only if it was signed in to a Google Account before you lost it. Otherwise, get into each site with another second step, backup codes or that site's recovery, then remove the old authenticator and link the new phone.

Does Microsoft Authenticator back up automatically?

No. Backup is a setting you turn on in the app before the loss (Cloud Backup on Android, iCloud backup on iPhone); otherwise there is nothing to restore.

My new phone shows a code but the site rejects it. Is that a recovery problem?

Usually not. One common cause is the phone's clock: check it with the authenticator clock check. Also check that you are using the code for the right account.

What happens with a work or school account?

Microsoft backs up only the account name for these accounts, so you sign in again and re-register through your organization.

Claim ledger

Sources

• Google Account Help: Get verification codes with Google Authenticator
• Microsoft Support: Back up and recover account credentials in the Authenticator app
• Microsoft Support: Restore account credentials from Microsoft Authenticator
• Microsoft Support: Microsoft Authenticator FAQs
• Apple Support: iCloud Keychain on iPhone
• Apple Support: Automatically fill in verification codes on iPhone
• Google Account Help: Sign in with backup codes
• Google Account Help: Fix common issues with 2-Step Verification
• Microsoft Support: Help with the Microsoft account recovery form
• Apple Support: How to use account recovery when you can't reset your Apple Account password
• Google Account Help: Lock or erase your lost phone or computer
• Android Help: Find, secure, or erase a lost Android device