Yealink Forums

Full Version: T21P Stuck on "Initializing" - Recovery Mode Fails`
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
A few T21P E2 handsets have decided to brick themselves after reboots. There was no firmware upgrade happening at the time.

(The provisioning file has no firmware URL listed in it, so I'm not sure why or how they got stuck on "Initializing" when they are rebooted.)

To restore the phones to working order, I asked my vendor for recovery files (.bin, .rfs and .rom) and I started a TFTP server.

When I put the handsets into recovery mode (by holding down the speaker button) and enter the correct IPs for the gateway and TFTP server, the TFTP server displays a "File too large" error when the handsets attempt to download the .rom file.

The .bin (which is larger than the .rom) and .rfs files download just fine though.

The phone displays show "Start Upgrading" and they just sit on that screen for hours.

Any ideas? Are these phones just duds?
(08-21-2021 10:36 PM)YCMJamie Wrote: [ -> ]A few T21P E2 handsets have decided to brick themselves after reboots. There was no firmware upgrade happening at the time.

(The provisioning file has no firmware URL listed in it, so I'm not sure why or how they got stuck on "Initializing" when they are rebooted.)

To restore the phones to working order, I asked my vendor for recovery files (.bin, .rfs and .rom) and I started a TFTP server.

When I put the handsets into recovery mode (by holding down the speaker button) and enter the correct IPs for the gateway and TFTP server, the TFTP server displays a "File too large" error when the handsets attempt to download the .rom file.

The .bin (which is larger than the .rom) and .rfs files download just fine though.

The phone displays show "Start Upgrading" and they just sit on that screen for hours.

Any ideas? Are these phones just duds?

Hi,

Please give this one a try, but the use is at your own risk.
"https://www.go-ccs.nl/downloads/Yealink T21-E2.zip"
(08-22-2021 03:08 AM)complex1 Wrote: [ -> ]Hi,

Please give this one a try, but the use is at your own risk.
"https://www.go-ccs.nl/downloads/Yealink T21-E2.zip"

I was told by someone else that I should retry it a few times if it fails to upload, but I've retried it over 50 times without success. I didn't imagine that the recovery mode for Yealinks was so unpredictable/unreliable.

I've also tried 2 different TFTP servers (PumpKIN and TFTPD64) - no difference, the same "file too big" error.

I'll give your files a go and update this thread with the results.

(If it permabricks my handset however, I'll probably be quite upset at Yealink!)
Ok, that didn't work and I repeated the process about 30 times.

I'm beginning to feel like I'm being mugged off by Yealink. Is there a training course I need to pay for to find out the real way to transfer recovery mode firmware to a Yealink phone or something?

This way is obviously super unreliable and "just keep retrying" feels like something Lucy would say to Charlie Brown just after she pulled the football away yet again.

[Image: LhMWItU.png]
(08-24-2021 04:19 AM)YCMJamie Wrote: [ -> ]Ok, that didn't work and I repeated the process about 30 times.

I'm beginning to feel like I'm being mugged off by Yealink. Is there a training course I need to pay for to find out the real way to transfer recovery mode firmware to a Yealink phone or something?

This way is obviously super unreliable and "just keep retrying" feels like something Lucy would say to Charlie Brown just after she pulled the football away yet again.

Hi,

Sorry if it didn't work.
It may be best to submit a support ticket directly to the Yealink helpdesk.
https://ticket.yealink.com/
(08-24-2021 06:18 PM)complex1 Wrote: [ -> ]Hi,

Sorry if it didn't work.
It may be best to submit a support ticket directly to the Yealink helpdesk.
https://ticket.yealink.com/

You are probably right.

(I wasn't meaning to take anything out on you specifically, I was just frustrated with the process and Yealink. Apologies if you thought otherwise.)
Reference URL's