Thank you so much for your reply, it had been so long I thought no-one would get back to me! Yes, I do still have access to the email registered, and the backup and public ones if needed, I can give them my keys that they gave me when I set up 2FA if they need, and I used PAT's once and I don't have access to that token, I don't think I used SSH keys if I am remembering what they are correct, and I don't remember my commit history. I can name atleast one of the repos and share the profile picture of the account if they need it for further verification, I can list all of the email adresses linked to the account and the name on the account. I feel like that is enough information.

Hi @rdmilkshakelab,

That is excellent news! Having access to your registered email and your original 2FA recovery codes is exactly what you need. That is the strongest proof of ownership you can provide.

Here is what you should do next:

1. Try the Recovery Codes directly: If you are just stuck at the SMS verification prompt during standard login, look for an option that says "Use a recovery code" or "Two-factor recovery". Entering one of those 2FA keys there might let you bypass the SMS requirement entirely.

2. Submit your info to Support:If the account is hard-blocked and login fails completely, email support@github.com (or use the Locked-Out Support form) directly from that primary registered email address.

3. What to include in your message:

• State clearly that you do not have a phone number for SMS verification.
• Provide a few of your 2FA recovery codes.
• List the primary, backup, and public email addresses linked to the account.
• Include the account name, the specific repo names you remember, and the profile picture details.

Sending this from your verified email address while providing the 2FA recovery codes should be more than enough for the support team to verify your identity and help you regain access. Good luck!

If this helps you recover your account, please consider marking this response as the answer so others with the same issue can find it easily!