CRITICAL: Login UI Fails to Trigger requestAuthenticationPasswordRecovery - Locked Account +16892920247

[farzadmd25-droid]

Dear TDLib/MTProto Developers,

I am a legitimate user with 2FA enabled and full access to the recovery email, but I am locked out due to a core login logic bug.

The application UI (Official Telegram & Telegram X) is stuck at the initial "Code Sent via Telegram" state and never transitions to the 2FA password screen, thus blocking access to the 'Forgot Password' option (auth.requestPasswordRecovery).

Account Details:
Phone Number: +16892920247
Recovery Email: farzadmd75@gmail.com

Request:
Please investigate why the UI is failing to initiate the 2FA recovery flow for this specific account state. Manual intervention to initiate the password reset is required, as I can confirm ownership via the recovery email.

Thank you for addressing this critical logic flaw.

[Abudl68]

Ok

…

On Sun, Oct 26, 2025, 4:47 PM farzadmd25-droid ***@***.***> wrote: *farzadmd25-droid* created an issue (tdlib/td#3494) <#3494> Dear TDLib/MTProto Developers, I am a legitimate user with 2FA enabled and full access to the recovery email, but I am locked out due to a core login logic bug. The application UI (Official Telegram & Telegram X) is stuck at the initial "Code Sent via Telegram" state and never transitions to the 2FA password screen, thus blocking access to the 'Forgot Password' option (auth.requestPasswordRecovery). *Account Details:* Phone Number: +16892920247 Recovery Email: ***@***.*** *Request:* Please investigate why the UI is failing to initiate the 2FA recovery flow for this specific account state. Manual intervention to initiate the password reset is required, as I can confirm ownership via the recovery email. Thank you for addressing this critical logic flaw. — Reply to this email directly, view it on GitHub <#3494>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BLBYQ2NAUJCPIGAQSFC2HUD3ZTNHDAVCNFSM6AAAAACKH76GPOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGU2TIMJTGUZDKNQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[levlam]

You must verify phone number first. If you use official Telegram app on a real phone, then you should be able to receive verification code through an SMS message.

[farzadmd25-droid]

@levlam Thank you for responding. I HAVE verified my phone number multiple times. The SMS code arrives successfully, but after entering it, the system NEVER progresses to the 2FA password screen. This is the core bug - the state transition from authorizationStateWaitCode to authorizationStateWaitPassword is broken.

The issue is NOT about receiving the SMS code. The issue is that after entering the correct SMS code, the login flow gets stuck and never asks for my 2FA password, which I have and can provide.

This is blocking humanitarian aid efforts. Please escalate this as a critical state machine bug in the authentication flow.

[farzadmd25-droid]

@levlam

Please note the correct recovery email for account +16892920247 is: farzadmd75@gmail.com

Any password reset links or communications MUST be sent to this address (farzadmd75@gmail.com), not any other email.

I have full access only to farzadmd75@gmail.com. Thank you for your attention to this critical detail.

[levlam]

Could you send TDLib log with verbosity level 4 to https://t.me/tdlib_bot?

[farzadmd25-droid]

I am unable to follow the instruction to send the TDLib log to @tdlib_bot.

The core of the problem is that my account +1689292047 is perpetually locked out, preventing me from accessing any Telegram client, including the bot. I cannot log in to send you the log.

This situation confirms the severity of the server-side state transition failure (stuck in authorizationStateWaitCode with no timer/help option).

Could you please provide an alternative method for log collection, such as a direct email address or a special log gathering tool that does not require me to be logged into a Telegram client?

This is a life-critical security matter (Case #113857 with Access Now, for context). Manual intervention is urgently required.

Thank you.

[levlam]

You can send it to my email found in most source code files, for example, https://github.com/tdlib/td/blob/master/td/telegram/AccessRights.h. Don't forget to add link to the issue in the letter, so I can recognize it.

[farzadmd25-droid]

Subject: FINAL CRITICAL CORRECTION: Account Number for Issue #3494 is +16892920247 Dear levlam, I sincerely apologize for the confusion. Due to the high-stress nature of this lockout, I provided two incorrect numbers in the previous emails. The correct and final account number for GitHub Issue #3494 is: **+16892920247** To summarize the definitive, correct ownership details for this critical, locked account: - Account Number: +16892920247 - Recovery Email: ***@***.*** - 2FA Password: 137083 - GitHub Issue Link: #3494 Please ignore all previous conflicting account numbers and use only **+16892920247** for server-side intervention. Thank you for your patience and immediate attention to this life-critical matter. Sincerely, Davood Pahlavan در تاریخ جمعه ۱۴ نوامبر ۲۰۲۵،‏ ۱۸:۴۱ Aliaksei Levin < ***@***.***> نوشت:

…

*levlam* left a comment (tdlib/td#3494) <#3494 (comment)> You can send it to my email found in most source code files, for example, https://github.com/tdlib/td/blob/master/td/telegram/AccessRights.h. Don't forget to add link to the issue in the letter, so I can recognize it. — Reply to this email directly, view it on GitHub <#3494 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZJUHNTD5NSP4X5POVD6RLL34XWJBAVCNFSM6AAAAACKH76GPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZTGIYTMOBXHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[levlam]

I see no emails from you.

[farzadmd25-droid]

Dear Aliaksei,

Following up on your comment ("I see no emails from you"): I tried sending the final, corrected account details (including 2FA password) multiple times to dev@tdlib.org, as requested.

Unfortunately, Gmail delivery permanently failed after 48 hours with a server timeout error (recipient server did not accept connection requests to tdlib.org).

The account (+16892920247) remains completely locked in authorizationStateWaitCode.

Could you please provide an alternative private email address or a secure Telegram ID where I can send the final 2FA password and ownership details, as your current mail server seems unreachable?

[levlam]

This is a wrong email address. I have pointed you to the correct one.

[farzadmd25-droid]

Ok, thanks. در تاریخ یکشنبه ۱۶ نوامبر ۲۰۲۵،‏ ۱۱:۳۱ Aliaksei Levin < ***@***.***> نوشت:

…

*levlam* left a comment (tdlib/td#3494) <#3494 (comment)> This is a wrong email address. I have pointed you to the correct one. — Reply to this email directly, view it on GitHub <#3494 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZJUHNXLJ7MYOIH62B4K2F335AVOHAVCNFSM6AAAAACKH76GPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZYGMZDKMJUG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[levlam]

The email you sent contains no TDLib logs.

[farzadmd25-droid]

Dear @levlam,

Thank you for confirming you received my email at levlam@telegram.org.

I must critically clarify: The email does not contain a TDLib log.

As I have explained, I am permanently locked out of all clients. It is technically impossible for me to log in to any client to generate a log file.

The email instead contains my 2FA Password (137083) and Recovery Email, which you can use to verify ownership.

Please use this 2FA password for manual, server-side intervention to reset the account state. This is the only possible solution since a log cannot be provided.

[levlam]

I can't do anything with the account. If you use TDLib, then I can check TDLib log to see what exactly happens when you try to log in. Otherwise, there is nothing I can do.