Serious issue with 25.30.0.20 - Multiples Bricked W52P

[dbrandphoto]

There is a serious bug in relation to Yealink's W52P base firmware version 25.30.0.20. We've now bricked 4 units and have users down.
The original issue that arose was caused by inputting a remote phone book into the W52P with firmware v25.30.0.20. When the phone book was put in the place, the handsets lost communication with the base, and the Register Status on the Account tab, went from Registered to Unknown. I had the user reboot the handset which did not function. Then I had the user reboot the base station. After rebooting the base station, the base would not come back up and is now bricked. There were 7 units onsite total that were receiving the remote phone book. The first 1 was the process I listed above. Immediately after this occurred, I grabbed a spare W52P unit in the office to test. It was running 25.40.0.15. The remote phone book took and functioned fine, no "searching for base" message, or any issues whatsoever. I then tried with the latest firmware (25.50.0.20). This also functioned correctly. As soon as I tried to downgrade the unit to 25.30.0.20, the unit bricked. It was stuck on the firmware updating page for about 20 minutes before I pulled the power on the unit. Upon rebooting, the power light was lit solid but there was no other activity from any of the other lights. The unit is no longer able to be pinged, it is not accessible anywhere on the network, and the handset is not connected nor will it connect after attempting to de-register and re-register again. Plain and simple, the unit is dead.
Something to not, while trying multiple things to get the base to reset, I noticed if you hold the page key WHILE powering on the base, the power light goes lit, then the network, then the handset however the handset is still unable to connect and it is not accessible on the network. I think this started to put it into a recovery mode possibly? but there is no literature online referencing this so I was not able to fix the base.
At this point, it looks narrowed down to the firmware so rather than rebooting 1 of the other units at the customers site, I started the firmware upgrade process. Same result, bricked phone. Had the user reboot, and nothing, same as what I'm seeing here. So that's 3 bricked phones. The 4th one bricked when I plugged in a brand new, unprogrammed W52P, running 25.40.0.15. I just tried to downgrade the firmware to 25.30.0.20, That bricked the unit as well.
The remaining 5 or so functioning units at the customers site appear to be functioning AFTER removing the remote phone book string. I removed the string and the Register Status changed from Unknown to Registered again, with no other changes being made.

First and foremost, I need to know if there is a process that we can go through to "un-brick" the base stations, maybe some sort of a recovery mode? That would be ideal as the 2 units at the customers location are located in the UK (we're in California), so there is significant cost involved in shipping replacements AS WELL AS significant downtime to be experienced by the users if they have phones down.

Plain and simple, I need a fix, ASAP.

[njkmoore]

Not sure if this helps but if your handset is not registering try de-registering it using a different handset - this was not obvious to me and is not possible through the web interface. Go through the de-register menu on a diff handset and de-reg the one in question, and you may then find it will re-register.

I had this issue after updating the firmware on the handsets. Very, very odd that you can't de-reg using the web interface but can using other handsets.

[dbrandphoto]

(04-08-2014 04:54 PM)njkmoore Wrote:  Not sure if this helps but if your handset is not registering try de-registering it using a different handset - this was not obvious to me and is not possible through the web interface. Go through the de-register menu on a diff handset and de-reg the one in question, and you may then find it will re-register.

I had this issue after updating the firmware on the handsets. Very, very odd that you can't de-reg using the web interface but can using other handsets.

No handsets were able to register to the base. The base was bricked, completely bricked. I would get a solid power light and that's it, nothing more. I have been in communication with Yealink since the origional post and they provided the files and process for recovering the base. I'm emailing Yealink to get a public instruction set so I can post it in the forums for other users to access if they run into this issue as well.

[dbrandphoto]

(04-09-2014 10:05 AM)Yealink Support Wrote:  Hi dbrandphoto,
Please test below rcovery mode for W52P and kindly feedback to me.
Recovery mode for Yealink Dect Phones.pdf

That's what I needed. I actually already received this exact PDF and tested the process before my last post, the reference to a public version was because the copy I received, had a download link with login credentials for the FTP specific to the reseller we purchase our phones through. Thank you for posting the updated PDF. I'm going to create a new post on this so it's available for other users that run into this. Can you also please add this PDF to the resource documents page for the W52P.

Thank you.

[rickcpoole]

Could you please let me know if you manage to fix this issue in regards to the base stations bricking without reason.

Second unit has just bricked out of the blue.

Thanks!

[James_Yealink]

Hi Rick,

Sorry for your inconvience.
What's the w52p firmware you are using? The latest fimeware should not have the problem.
Can you try a hard reset to login in the web interface.

Step to do a hard reset:
1. Disconnect the power adapter.
2. Long press the paging key and reconnect the power adapter.
When base station reset finishes, the power indicator LED, network status LED and registration LED illuminate in sequence. System PIN and all individual settings are reset to factory defaults. Handset registrations will also be cleared after base station reset.

Regards,
James