Yealink Forums
Dead W52H - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: Dect Phone Series (/forumdisplay.php?fid=6)
+--- Forum: W52P (Wireless) (/forumdisplay.php?fid=23)
+--- Thread: Dead W52H (/showthread.php?tid=862)



Dead W52H - bsnipes - 10-01-2013 12:27 AM

I decided to update the firmware on a W52H that I just received after updating the base station. The USB utility got to 10% and then said it had completed. Handset appears to be totally dead. Is there a recovery procedure for them available?


RE: Dead W52H - Yealink Support - 10-10-2013 02:53 PM

Hi Bsnipes,
Did you follow our upgrade guide to upgrade it?
http://www.yealink.com/Upload/W52P/V40/How%20to%20Upgrade%20W52x%20Handset%20Firmware%20Using%20the%20USB%20Update%20To​ol.zip
Could you try again?
Thanks.


RE: Dead W52H - mkeuter - 10-10-2013 09:06 PM

I had the same issue today when I tried to upgrade the handset from 26.30.0.40 to the new 26.30.0.50.
The handset looked dead, but was still detected via USB. I had luck and could reflash it with FW 26.30.0.40.


RE: Dead W52H - bsnipes - 10-10-2013 10:59 PM

(10-10-2013 09:06 PM)mkeuter Wrote:  I had the same issue today when I tried to upgrade the handset from 26.30.0.40 to the new 26.30.0.50.
The handset looked dead, but was still detected via USB. I had luck and could reflash it with FW 26.30.0.40.

That worked for me. Thanks.


RE: Dead W52H - mkeuter - 10-14-2013 09:21 PM

@Yealink:

Are there known problems when updating to the new 26.30.0.50 handset firmware?
Had anyone success with that FW?


RE: Dead W52H - Yealink Support - 10-17-2013 09:06 AM

Hi,
I have tried it, and I succeed.
I upgrade from 26.30.0.40 to the new 26.30.0.50
These are my steps:
1.Open Update Tool,
2.Browse to load firmware,
3.Connect one side of USB cable to computer,
4.Press OK button of handset to activate it,
5.Connect other side of USB cable to handset,
6.Click upgrade.

I attached my updating picture.

Could you try again?

Thanks


RE: Dead W52H - mkeuter - 10-17-2013 05:58 PM

After re-downloading it, it now worked as you described, thanks.