Solved Bricked Yealink T54W's with 96.86.0.20 firmware

[tenroc2o0o]

I just finished bricking 5x Yealink SIP-T54W's by installing the 96.86.0.20 update from either 96.85.0.5 or 96.86.0.5. 4x of them bricked after pushing the firmware via 3CX, and then one of them after using the phone's admin UI directly with the ROM downloaded from 3CX. I had 6x others that successfully updated. That's a 45% failure rate, in case anyone was counting.

The phones hang on "Welcome, Initializing.. Please wait". When I attempt to enter recovery mode by holding down the speakerphone button while power is applied, I'm unexpectedly greeted with a new menu that says "Whether to enter the recovery mode and run the backup system? 1) Yes 2) No". Pressing [1] just results in a hung black screen or a hung "Welcome" screen, whereas [2] doesn't do anything and locks the phone up afterwards.

This is different than previous firmware releases, where holding down the speakerphone button would prompt with two options, "1) TFTP 2) USB". Either option would allow you to load the recovery files (bin/rom/rfs). I'm unable to get to this point on these phones now after this failed firmware update.

I have a case open with Yealink and am waiting on their response.

Just thought I'd share, and maybe 3CX should consider retracting the firmware for T54W's.

As a side note, the same firmware image is also used on T53W's. I've had two phones fail to update - they get stuck in a firmware update loop where they hang at 93% while "downloading", and after rebooting the phone each time, 3CX re-triggers the same firmware update which then keeps hanging at 93%. However, I was able to enter recovery mode and restore those without any issue.

 

[dmat1175]

Copy both files and rename them to match the phone model. I also copied over the .rfs file from one of the links above but I'm not sure if that is needed or not:
[Link Removed]

So on the USB you should have 3 files:
T54W.bin
T54W.rfs
T54W.rom

Just switch the files name to match your phone model T53W, T54W, etc. I would imagine this also works for TFTP but did not try it.

 

[EulePS]

So i download the .BIN and .ROM files from the first link.
Then i download the .RFS file from the folder T54S.

Then i rename the files to:
T54W.bin
T54W.rfs
T54W.rom

and copy these to the USB.
The USB is formatted FAT32.

Then i put the USB in the phone, put in the Network Cable for power and hold redial button.
Pull number 2 and it comes Network Failed...

 

[dmat1175]

Try the .rfs file from this link for the T54W, the T54s might be different:
[Link Removed]

If that still doesn't work you may have to try and TFTP the firmware over to the phone. I did not try TFTP for any of the 7 or so phones I had fail so I can't confirm if it works or not.

 

[EulePS]

Thank you but i don't help...

If USB ist format to NTFS -> Update failed -1
if USB is format to FAT32 -> Network failed

....

 

[tenroc2o0o]

Thank you !

Which file should i copy to the USB? Rename the file?
We get Network Failure or Updated Failed...

We're still trying to figure that out.

Yealink sent me a new ROM and BIN with version 96.86.0.21 for testing and said to NOT use an RFS file, but my TFTP log is still showing "too large" on the ROM and is still attempting to download an RFS file.

If i use the older BIN and RFS and 96.86.0.5 ROM, i still get same errors - rom is too large

"Peer returns ERROR <File too large> -> aborting transfer "

 

[EulePS]

Same Problem Here with TFTP …

 

[bloomy32]

hey guys. new update. new set of firmware from yealink now with the 3 files needed (last one they released only had 2, whcih is why the file size too big error). works with both USB and TFTP
[Link Removed]
boot into recovery with redial, and reload using the files.

 

[complex1]

For users whose Yealink T5xW phone is not bricked but unable to update to version 96.86.0.23...?
Download version .23 from the PBX Yealink folder and manually install in your TxW.
This did the trick for me.

 

[NickD_3CX]

Hi everyone,

We just had a meeting today with Yealink regarding this matter.

As our contact from Yealink mentioned here, if any of your devices have been rendered unusable by the upgrade to 96.86.0.20, then please contact Yealink Support as mentioned in the aforementioned post.

Traditionally the files we get from Yealink are "General Release" material, but most of the times we get them before they hit the Yealink website.

Version 96.86.0.20 was meant to be the release version, but due to this issue, we worked with Yealink and within ~24 hours we had replaced it with 96.86.0.23.

Where we are right now:

• You have upgraded the T5xW device to 96.86.0.23 and it is working fine
  In this case, there is nothing to do.
  
  
• You have done nothing and you are still on 96.86.0.5
  In this case in the MC, you should now see a new firmware available (96.86.0.23) to which they can upgrade safely.
  
  
• You attempted to upgrade to 96.86.0.20 and the phone is unusable
  You need to contact Yealink Support for instructions on how to restore their phone to normal operation at https://ticket.yealink.com/ as explained by Yealink here.
  
  
• Customer upgraded their phone to 96.86.0.20 and the phone is working normally
  There are no actions required, if the upgrade was successful all is good.
  However, in the MC they will now still see a newer firmware available, 96.86.0.23.
  Unfortunately you will not be able to upgrade to this firmware via the MC, because in essence, 96.86.0.20 and 96.86.0.23 are the same apart from a small change in the ROM.
  This will be resolved when Yealink releases a newer firmware again, e.g. 96.86.0.30, in which case phone on both 96.86.0.20 and 96.86.0.23 will be able to upgrade normally to it.
  If this really annoys you, you should either contact Yealink for help, or, try installing 96.86.0.23 manually from the phone's web UI from here.

Any firmware we upload to our download server is hand-given to us by the IP Phone manufacturer and checked briefly by us as well that the upgrade is successful. Unfortunately all our testing T5xW devices upgrade to 96.86.0.20 without issue, hence why we did not detect this.

Yealink has informed us that they will be taking measures to avoid this from happening again.

 

[Firstbyte19]

Same issue here! Bricked 6 T57W's. Submitted a ticket with Yealink because I was getting error (-3) file size too large. They emailed me the 96.86.0.21 bin file, now getting an update failed(-1). This is a new install across several Ford dealerships, it's hard to explain to a customer what in the world happened or assure them this won't happen again. It's more frustrating to know, so many people are in the same boat. Does anyone have the correct file for a T57W?

 

[tropicsoftde]

I have a T57W here that was in a firmware update loop after an update to 96.86.0.23. This means that after the update to 96.86.0.23 the Fon booted and after the complete start it went back into the loop for the firmware update. The only way I could do this was to quickly trigger the factory reset a few seconds after the start and before the new firmware update with the push of a button and I am back to 97.84.0.125 on the T57. Now of course I don't dare to update the T57 with the x.x.x.23.

 

[eagle37]

Maybe this will help someone... Fortunately we were starting with T54W phones that were still running .20, they just would not update to .23. The .23 firmware being distributed by 3CX is incomplete. Yealink provided the complete .23 firmware, but after a successful update, the phones would reverted back to the prior firmware version. The solution was to push the bad .23 firmware from 3cx, let each phone fail the update, then manually update to .23 with the ROM provided by Yealink, and now all our phones are successfully upgraded to .23.

 

[Lyman_Yealink]

Hi all，
Yealink has released version 23 of the firmware on its official website. You can follow the upgrade guide to upgrade your device to the latest version 23. You can click this link to get the firmware:https://support.yealink.com/en/portal/docDetail?documentCode=bd47f0dca2c4f84c

If you have any other questions, you can contact Yealink's Support team（https://ticket.yealink.com/）, and your request will be responded to quickly.


Note：
Please notice the following requirements:
1. For devices in firmware version 84 (for example, xx.84.0.125 or 96.84.0.95), you need to upgrade the device firmware to version 96.86.0.18, then to version 96.86.0.23.
2. For devices in firmware version 86 (for example, 96.86.0.5 or 96.86.0.10), you need to upgrade the device firmware to version 96.86.0.18, then to version 96.86.0.23.
3. For devices in firmware version 85 (for example, 96.85.0.5), you can directly upgrade the device firmware to version 96.86.0.23.
4. For devices in firmware version 96.96.0.20, you are not required to upgrade as the features provided by 96.96.0.20 and 96.86.0.23 are identical. You can upgrade the device if Yealink releases a new version in the future.

 

[techguyjason]

Thank you !

Which file should i copy to the USB? Rename the file?
We get Network Failure or Updated Failed...

I am getting the same errors. I sometimes get Update failed -4 or -1 or network Failure.

I have tried several different USB drives of different sizes all formatted to fat32. Tried the firmware named as it comes, also just T54W and T54W with firmware version.

Can someone that has fixed this please give steps and details of what they did?

Thanks,

 

[NickD_3CX]

I am getting the same errors. I sometimes get Update failed -4 or -1 or network Failure.

I have tried several different USB drives of different sizes all formatted to fat32. Tried the firmware named as it comes, also just T54W and T54W with firmware version.

Can someone that has fixed this please give steps and details of what they did?

Thanks,

I think you should follow the advice of Yealink mentioned here and contact https://ticket.yealink.com/ :
https://www.3cx.com/community/threa...ws-with-96-86-0-20-firmware.82455/post-383085

 

[bryanc1]

Happened to myself, here. Getting a failure with a 3 second countdown after firmware attempted to load.

 

[William Jones]

Thank you !

Which file should i copy to the USB? Rename the file?
We get Network Failure or Updated Failed...

You will need to rename the files T54W.rom T54W.bin or to match the model phone you have. I have been able to restore 5/6 phones so far. The USB recovery is giving me a network error on the last phone.

 

[William Jones]

After contacting Yealink support they were able to provide me with a set of files that worked the last phone that was being stubborn. I hope this helps everyone else still fighting this issue.

[Link Removed]

 

[tenroc2o0o]

After contacting Yealink support they were able to provide me with a set of files that worked the last phone that was being stubborn. I hope this helps everyone else still fighting this issue.

[Link Removed]

Same here. They sent me ROM 96.86.0.21 with new bin and rfs files. The one they sent you appears to be ROM 96.86.0.23.

I just noticed 3CX now marked 96.86.0.20 and .21 as not supported, and they've put a new firmware zip out that has an upgrade guide with TWO roms in it -- .18 and .23. Apparently, you MUST upgrade to .18 BEFORE upgrading to .23. I guess no one warned us?

 

[William Jones]

Same here. They sent me ROM 96.86.0.21 with new bin and rfs files. The one they sent you appears to be ROM 96.86.0.23.

I just noticed 3CX now marked 96.86.0.20 and .21 as not supported, and they've put a new firmware zip out that has an upgrade guide with TWO roms in it -- .18 and .23. Apparently, you MUST upgrade to .18 BEFORE upgrading to .23. I guess no one warned us?

All the phones but one worked with the .21 firmware but the last one just wouldn't take that is when they sent me the .23 firmware. I am just glad this only affected my smallest client and not all of them.