Lost Google Authenticator for a Crypto Exchange: How to Restore 2FA

What was lost: a 2FA code or wallet access?

Google Authenticator generates one-time codes for sign-in and action confirmation. It does not hold your exchange balance or control it instead of the exchange. An empty app does not itself prove that assets are lost: restore the second factor or complete account-ownership verification.

A separate wallet’s seed phrase cannot replace an exchange code. If losing the phone also removed access to a self-custody wallet, use the guide for a lost phone. Do not enter a seed phrase into an exchange account-recovery form.

First steps without deleting retained data

1. Record whether the old phone is accessible and an exchange session is still active.
2. Check the Google Account selected in Authenticator and whether the relevant entry is present.
3. If a displayed code is rejected, check the service, code expiry and the phone’s system time.
4. If the old device is available, follow the official transfer procedure; do not publish the export QR code.
5. If no codes remain, open the exchange’s official recovery channel.
6. Save the request number and the list of evidence requested.

Google describes synchronization after signing in to the same account and manual transfer from the old device. If synchronization was not previously enabled, installing the app on a new phone does not itself recreate the entries. Deleting a synchronized entry affects other synchronized devices; do not use deletion to troubleshoot an empty screen.

If the device was stolen, separately secure your email and exchange account using official session-management tools. Do not treat an unknown active session as evidence of security and continue using it.

How an official reset works: the Bybit example

Bybit’s instructions start with “Having problems with verification” during sign-in. Select the Google Authenticator reset and complete the additional verification offered, such as available contact channels or facial verification. The guidance warns that self-service is unavailable for suspended or restricted accounts; an official support request is then needed.

Requirements depend on the verification methods available and the service’s regional version. Do not transfer a document list or timeframe from another exchange’s instructions. If both phone and email are inaccessible, state both problems immediately so the reply is not limited to sending a code to an inaccessible channel.

To prepare, list the UID, accessible contact methods, date the device was lost, last successful account visit and previous request numbers. Submit personal documents only through the requested secure form. The exchange verification article explains how to check that a response is complete.

Educational request example and checks after recovery

Example situation: the old phone is broken, codes cannot be transferred, email is accessible and synchronization was not previously used. This is a reason to request an official reset, not to look for a way to calculate a one-time code.

• Account: [UID or permitted identifier].
• Problem: access to Authenticator lost since [date].
• Retained: [email / number / active session].
• Unavailable: [old device / backup key].
• Already done: [checks and official form result].
• Request: identify an available ownership-verification method and the next reset step.

After recovery, check sign-in with the new second factor, contact details, devices and the withdrawal address book. Store backup information without exposing it to others. According to Bybit’s current guidance, resetting or disabling Authenticator triggers a protective withdrawal restriction; follow your account notification and do not treat a successful sign-in as a promise of immediate withdrawal.

If the reset is rejected, the next reply should address the stated gap: an inaccessible channel, ownership mismatch or insufficient evidence. For an initial assessment, a specialist needs the rejection text and a description of retained access, not current codes.