I lost my phone with my access codes and GitHub Mobile account. I don't have my passkeys. Is there a way to contact GitHub support by email? I'm a student, so I can't lose that account because I would lose my access

[BOTXD764]

Discussion Type

Product Feedback

Discussion Content

No response

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[hoangperry]

Losing the phone that held both your authenticator/recovery codes and a signed-in GitHub Mobile session is the hard case, but there are still routes — try them in this order:

1. Recovery codes stored anywhere other than the phone. When you enabled 2FA, GitHub gave you a list of one-time recovery codes — check a password manager, a printout, a saved file, a backup email to yourself. One code entered at "Use a recovery code" on the sign-in screen gets you straight in. This is the fastest path if any copy exists.
2. Another device still authenticated. If you're signed into github.com in a desktop browser anywhere, or GitHub Mobile on a tablet/old phone, you're already past 2FA there — go to Settings → Password and authentication and add a new factor (TOTP + a passkey) immediately, and generate fresh recovery codes.
3. Authenticator cloud backup. If your TOTP app was Google Authenticator (with account sync), Authy, or 1Password, your 2FA seeds may have synced to your account — install it on a new phone, sign into that app's account, and your GitHub TOTP may reappear. Same for passkeys synced via iCloud Keychain / Google Password Manager on a replacement device.
4. SMS fallback, if you had a phone number on the account and can get a replacement SIM with the same number.
5. If none of the above: the account-recovery process at https://github.com/support (the "Can't access your account?" link on the 2FA prompt) is the last resort — an identity-verification flow. It's slow and not guaranteed, but it's the only route when every factor is gone.

Once you regain access: set up at least two independent factors (a TOTP app and a passkey), and store the new recovery codes somewhere off-device (password manager + a printout). The single-device failure you just hit is exactly what a second factor + off-device recovery codes prevent.

[BOTXD764]

Hello, I want to do an identity verification flow for the account FabricioArroyo please

…

On Sun, Aug 23, 2026, 5:21 AM Hoang N. Truong ***@***.***> wrote: Losing the phone that held both your authenticator/recovery codes *and* a signed-in GitHub Mobile session is the hard case, but there are still routes — try them in this order: 1. *Recovery codes stored anywhere other than the phone.* When you enabled 2FA, GitHub gave you a list of one-time recovery codes — check a password manager, a printout, a saved file, a backup email to yourself. One code entered at "Use a recovery code" on the sign-in screen gets you straight in. This is the fastest path if any copy exists. 2. *Another device still authenticated.* If you're signed into github.com in a desktop browser anywhere, or GitHub Mobile on a tablet/old phone, you're already past 2FA there — go to Settings → Password and authentication and add a new factor (TOTP + a passkey) immediately, and generate fresh recovery codes. 3. *Authenticator cloud backup.* If your TOTP app was Google Authenticator (with account sync), Authy, or 1Password, your 2FA seeds may have synced to your account — install it on a new phone, sign into that app's account, and your GitHub TOTP may reappear. Same for passkeys synced via iCloud Keychain / Google Password Manager on a replacement device. 4. *SMS fallback*, if you had a phone number on the account and can get a replacement SIM with the same number. 5. *If none of the above:* the account-recovery process at https://github.com/support (the "Can't access your account?" link on the 2FA prompt) is the last resort — an identity-verification flow. It's slow and not guaranteed, but it's the only route when every factor is gone. Once you regain access: set up *at least two independent factors* (a TOTP app *and* a passkey), and store the new recovery codes somewhere off-device (password manager + a printout). The single-device failure you just hit is exactly what a second factor + off-device recovery codes prevent. — Reply to this email directly, view it on GitHub <#205468?email_source=notifications&email_token=AWYZBYH4D22BS6RYBYOCQ6D5LLHUZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGIZTINZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18123472>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWYZBYBY4D4ZOFXMSZ4JQML5LLHUZAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBWGU2TGMZQUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AWYZBYB5ZC6SU44DEZETUHT5LLHUZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGIZTINZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/AWYZBYHQX33OD44F5KDQOV35LLHUZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGIZTINZSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[v-coder247]

Hi @BOTXD764,

For account related issues, GitHub Support requires that you contact them from the email address verified on that account. If you haven't already, please submit a request using this form: https://support.github.com/contact/cannot_sign_in

When completing this step, you won't be required to sign in, but you will need to verify your email address. If you're currently signed into a different account, please sign out first before following the link.

As no other Community Discussions team members will be able to provide additional help with account related questions I am going to close this discussion. We appreciate your understanding and patience while Support works through your request!