Troubleshooting
2FA Codes Are Going to Your Old Phone
Codes keep landing on a phone you no longer carry, and logging in feels stuck.
Is this your situation?
You changed phones, and your two-factor authentication codes still go to the old device. You have not yet updated the phone number or authenticator app tied to your account.
The short answer
Your account is still set to send codes to the old phone. If you still have the old phone's SIM, a text message code can be sent to that mobile phone. If you have no phone, no app and no other session, look for the option that says I don't have my phone.
What you see, and why
| Symptom | Cause |
|---|---|
| Text message codes arrive on a SIM you no longer have. | Facebook uses a newly added mobile phone number to help you log into Facebook. |
| You cannot use your old phone number to reset your password. | You cannot use the same mobile phone number used for two-factor authentication to reset your password. |
| You are stuck with no code and no working app. | If you don't have your phone at all, look for an option that says I don't have my phone on the authentication screen. |
Check these first
- Check whether the old SIM still receives texts. A six digit text message code can still be sent to a mobile phone.Verify: Check if the old SIM is active and can receive messages.
- Check for saved recovery codes. Recovery codes are one-time backup codes generated from Facebook Security and Login Settings.Verify: Check any printed or saved copy of your recovery codes.
- Check for another logged-in device. You can approve a login attempt from another device already logged in to Facebook.Verify: Check your other devices for a Facebook session still signed in.
How Facebook handles this
- A mobile phone number added for two-factor authentication helps keep the account safe.
- You cannot use the number tied to two-factor authentication to reset your password.
- A saved recovery code can be entered in place of the two-factor authentication code to log in.
- Each recovery code can only be used once.
Which path applies to you?
- Do you still have the old phone and its SIM? A text message code can still be sent to that mobile phone.
- Do you still have the authenticator app installed anywhere? A third-party authentication app can be used to generate login codes.
- Are you still logged in on another device or browser? You can approve the login attempt from that other logged-in device.
- Do you have no phone, no app and no other session? Look for the option that says I don't have my phone on the authentication screen.
Step by step: finding the cause
- Try the old phone first A six digit text message code can be sent to your mobile phone.Where: Facebook login screen → Password sectionConfirm: Check the old phone for a new text message.
- Check a recognized device You can approve a login attempt from a device Facebook already recognizes.Where: Login → Recognized deviceConfirm: Check that device for a login approval prompt.
- Use a recovery code A recovery code can be used in place of an authenticator code when logging in.Where: Facebook login screen → Password sectionConfirm: Check any saved list for an unused code.If this fails: Each recovery code can only be used once.
- Look for the no-phone option If you do not have your phone at all, look for an option that says I don't have my phone on the authentication screen.Where: Authentication screen → I don't have my phoneConfirm: Check the screen for this option.
- Ask Facebook to confirm identity You can ask Facebook to confirm your identity to regain access if other tips do not work.Where: Help Center → Login help flowConfirm: Check for a prompt to confirm your identity.If this fails: Confirming identity may involve security questions about the account.
- Update your security method once in After logging back in, add a new mobile phone number for two-factor codes.Where: Accounts Center → Password and securityConfirm: Check the new number appears under your method.
Common mistakes
- Trying to reset the password with the old number The number tied to two-factor authentication cannot be used to reset the password.Why it happens: For security reasons, that same number is blocked from the reset flow.
- Discarding the old SIM too early The SIM can still receive the six digit text message code.Why it happens: The account still points two-factor codes to that number.
- Losing printed recovery codes Recovery codes are one-time backup codes generated from Security and Login Settings.Why it happens: Each code only works once, so a lost set leaves none to use.
- Assuming no path exists without the phone An option exists reading I don't have my phone on the authentication screen.Why it happens: The option is simple to overlook among the other prompts.
Quick reference
| Situation | What applies |
|---|---|
| Still have old SIM | A six digit text message code can be sent to that phone. |
| Still have authenticator app | The app can generate login codes. |
| Logged in elsewhere | You can approve the login from a recognized device. |
| Have saved recovery codes | A recovery code can be entered in place of the authenticator code. |
| Recovery codes used up | Each recovery code can only be used once. |
| No phone, app or session at all | Look for I don't have my phone on the authentication screen. |
| Old number tied to two-factor authentication | It cannot be used to reset the password. |
| Back in after recovery | You can add a new phone number for two-factor codes. |
Keeping track of who has access
Delvia keeps a clear record of your access methods, so the setup you diagnosed doesn't recur unnoticed.
Was this helpful?