I have the appropriate recovery files label T41.rom, T41.bin and T41.rfs in the TFTP private root directory. i set the TFTP settings on the T41, but get an update failed (-1) message. Any idea what that represents?
thanks
(07-19-2019 07:35 PM)jwhopkins Wrote: [ -> ]I have the appropriate recovery files label T41.rom, T41.bin and T41.rfs in the TFTP private root directory. i set the TFTP settings on the T41, but get an update failed (-1) message. Any idea what that represents?
thanks
Dear Customer,
This is Baron from Yealink, I will work with you on this case.
T41S.rom,T41S.bin and T41S.rfs are the correct file name used for recovery mode, I will send the files(T41S.bin&T41S.rfs) for you.
You can download the files from the following link:
https://drive.google.com/open?id=1M_YuCG...ozmfvAd7me
Best regards
Baron
Thanks Baron. It now starts updating (which it didn't before) but complains that I have bad .rom file. The .rom I am using is the latest from the Yelling support site (66.84.0.15) which I then renamed to T41S.rom. Any thoughts? It uploads a couple of items (progress percentage is dynamic). I have included a copy of the screen shot
Thanks in advance for your assistance.
- Jon
(07-24-2019 08:15 PM)jwhopkins Wrote: [ -> ]Thanks Baron. It now starts updating (which it didn't before) but complains that I have bad .rom file. The .rom I am using is the latest from the Yelling support site (66.84.0.15) which I then renamed to T41S.rom. Any thoughts? It uploads a couple of items (progress percentage is dynamic). I have included a copy of the screen shot
Thanks in advance for your assistance.
- Jon
Hi Jon，
For the bad rom issue, there are three kind of possibilities:
(1) The network disconnect when you do upgrade;
(2) The rom file is error;
(3) The server is down when you do upgrade;
Suggestions:
(1) You can monitor the network to see if any packets lost;
(2) Re-download this firmware again, then test again.
If none of above helps, please reproduce it again, and offer us the syslog of phone and the log of TFTP server, then we can see what is happening here. Below is the FAQ about how to capture phone syslog.
http://support.yealink.com/faq/faqInfo?id=712
Any question, freely to let me know.
Best Regards,
Baron