Authy App Crashed and I Can't Access 2FA Codes - How Do I Recover My Exchange Account?

27 September 2026

If the Authy app on your phone has crashed, been wiped, or become otherwise unreadable, you are not necessarily locked out of your exchange account forever. The immediate answer is that you have options, but which ones work depends entirely on how you set up your two-factor authentication (2FA) backup methods before the crash. Recovery typically proceeds in this order: restore from an Authy backup or multi-device sync, use a saved backup code, use a recovery code from the exchange, or open a manual support ticket with proof of identity. The process is rarely instant, so be prepared for a wait.

First, check if authy itself has a backup

Before you panic or contact support, find out whether you enabled Authy's encrypted backups. Authy offers this by default when you register your phone number, but the backup only restores if you know your backup password (sometimes called a master password). If you never set one, the backup exists but is not encrypted with a password you chose - which means it may still restore on a fresh install.

To try restoring Authy on a new or repaired device:

1. Reinstall the Authy app.
2. Enter your country code and phone number.
3. Authy will send an SMS or automated phone call with a verification code.
4. Enter that code. If you have an encrypted backup, you will be prompted for your backup password.
5. If the restore succeeds, your 2FA tokens should reappear.

If you had multi-device sync enabled and your old phone is still functional, you may also be able to view codes there. If neither works, move to the next step.

Use any backup codes you saved

Most reputable exchanges force you to generate backup codes when you first enable 2FA. These are usually single-use strings of letters and numbers, often 8 to 16 characters long. If you stored them in a password manager, printed them, or saved them to a file, now is the time to use one.

How to log in with a backup code:

1. Go to the exchange's login page and enter your email and password.
2. When prompted for the 2FA code, look for a link that says "Use backup code," "Recovery code," or "Lost your 2FA device?"
3. Enter one of your unused backup codes.
4. The exchange will log you in. Immediately go to security settings and disable 2FA, then re-enable it with a fresh authenticator app.

Note that backup codes are single-use. After you use one, it is dead. If you have multiple, save the rest in a secure place. If you do not have any backup codes, proceed to the exchange's recovery process.

Exchange-Specific recovery: manual identity verification

If you have no Authy backup and no backup codes, you are left with the exchange's manual recovery process. This is deliberately slow and intrusive because the exchange is trying to prevent an attacker from doing exactly what you are attempting - accessing an account without full 2FA.

Every exchange has its own procedure, but the general pattern is consistent:

1. Find the recovery or account access page. Look for "Lost 2FA," "Account recovery," or "Trouble logging in?" on the login screen.
2. Submit a support ticket. You will typically need to provide:
3. Your registered email address.
4. A government-issued photo ID (passport, driver's license).
5. A selfie holding the ID (sometimes with a handwritten note and the date).
6. Proof of address (utility bill, bank statement).
7. Details of recent transactions, account balances, or the date you opened the account.
8. The approximate amount and type of crypto held.
9. Wait. Exchanges often take days to weeks to process these requests. They may reply with follow-up questions. Do not expect a quick resolution.

Some exchanges have a "cooling-off" period after a 2FA reset request - often 24 to 72 hours - before they actually remove the old 2FA. This is to prevent account takeover. If you initiated the request, you must wait out this period.

What if you never set up backup options?

If you enabled 2FA but skipped backup codes, never set an Authy backup password, and have no other device, the situation is grim but not always hopeless. Some exchanges will still help if you can prove your identity and show account activity. Others will not, because the security model is designed to treat you as an attacker.

Be honest with yourself: if you cannot prove you are the account owner through transaction history, IP addresses used, or other personal data, the exchange likely will not help you. That is a feature, not a bug.

Prevent this from happening again

Once you regain access - and if you cannot, learn from the loss - set up a more robust 2FA strategy. The single best practice is to store your 2FA seeds (the QR code data) in a password manager or on a hardware wallet that you back up offline. Authy is convenient, but it ties your codes to a phone number and a company's cloud service. A hardware security key (like a YubiKey) or a password manager with TOTP support gives you more control.

Also, always save backup codes. Print them, put them in a safe, or store them in an encrypted file. They exist specifically for this moment.

When manual recovery fails

If the exchange refuses your request, you have few remaining options. You could:

• Check if you have any old emails from the exchange containing partial backup codes or recovery links.
• Look through your password manager's history for any notes about your 2FA setup.
• Accept the loss and focus on securing any other accounts that use the same email and password combination.

There is no magic backdoor. Exchanges do not keep plaintext copies of your 2FA secrets, and they cannot generate codes for you. They can only reset the 2FA after verifying your identity through other means.

The Bottom Line

A crashed Authy app is a serious problem, but it is not automatically the end of your exchange account. Your recovery path depends entirely on the backups you made earlier. If you have none, you are at the mercy of the exchange's support process - which is slow, tedious, and sometimes unsuccessful. The fix is not technical; it is procedural. Make backups, save codes, and treat 2FA as the fragile convenience it is.

Back to account recovery