Cannot update Deco x50 v1 firmware from version 1.2.2

Cannot update Deco x50 v1 firmware from version 1.2.2

Cannot update Deco x50 v1 firmware from version 1.2.2
Cannot update Deco x50 v1 firmware from version 1.2.2
2024-10-23 02:00:21 - last edited 2 weeks ago
Model: Deco X50  
Hardware Version: V1
Firmware Version: 1.2.2

Hi,

 

I followed the guide here for my X50 v1 to get it back to an older version so I can then upgrade to a newer firmware:

 

https://www.tp-link.com/ca/support/faq/2958/

 

I've managed to get back to v1.2.2 firmware however whenever trying to install any of the most recent firmware versions via the TP-Link website it won't work.

 

If I do it via app I get I already have the latest firmware version (1.2.2 is not the latest by far for the 1.0 version of the X50) and if I do it via the web interface I get an "Upgrade failed. Please select the latest version of firmware to upgrade".  

 

The original firmware reset process worked fine but being it's the X50 apparently it won't support me using that method to upgrade to a firmware any newer than 1.2.2 due to file size I believe?  

 

Is there anyway of knowing what check is being carried out that it's failing on when thinking my newer firmware is somehow older than the one I'm uploading? It just doesn't really make sense at this stage.  

  1      
  1      
#1
Options
1 Accepted Solution
Re:Cannot update Deco x50 v1 firmware from version 1.2.2-Solution
2024-10-23 07:36:32 - last edited 2 weeks ago

  @MeNaCeNZ 

Hi, Nice to see you again.

May I know how long you have had the Deco X50?

Usually, It is not supposed to recover from the 2.0.3 20240112 Rel. 36417(ISP version) to the general 1.2.2 firmware version.

Are the Deco units still working well on the 1.2.2 version?

 

I think even though the firmware recovery works, the general firmware versions don't cover the region code"NZVDF" and through the standard firmware upgrade interface, the hardware can't find the matched region code from the uploaded bin file.

Thank you very much and best regards.

Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:Cannot update Deco x50 v1 firmware from version 1.2.2-Solution
2024-10-23 07:36:32 - last edited 2 weeks ago

  @MeNaCeNZ 

Hi, Nice to see you again.

May I know how long you have had the Deco X50?

Usually, It is not supposed to recover from the 2.0.3 20240112 Rel. 36417(ISP version) to the general 1.2.2 firmware version.

Are the Deco units still working well on the 1.2.2 version?

 

I think even though the firmware recovery works, the general firmware versions don't cover the region code"NZVDF" and through the standard firmware upgrade interface, the hardware can't find the matched region code from the uploaded bin file.

Thank you very much and best regards.

Recommended Solution
  0  
  0  
#2
Options
Re:Cannot update Deco x50 v1 firmware from version 1.2.2
2024-10-23 08:17:31

  @David-TP  

 

I've had it a couple of nearly 18 months now , I was able to push through the 1.2.2 because of the recovery guide when setting the IP to 192.168.0.1 and doing the reset trick.  

It is working fine enough under 1.2.2 which still seems more advanced than the firmware the isp had put on the device.

 

Unfortunately it's the only Firmware under the size limit for the x50/55 that another tp-link member had mentioned in another post.

 

Is there really no way to just push a newer firmware to the device the same as what I did with the 192.168.0.1 web frontend? It seems crazy to ahve a file limit size and then basically say there is no way to forcibly put a firmware on a device because of rather poor checking procedure of checking region codes that end up just being hard coded by ISPs.

 

It is worth noting that many people on sell their ex. ISP deco's and then end up in the same boat of having an ISP Deco they can't neccessarily upgrade anymore (especially if not with the same ISP).  I think there needs to be a means to force firmware onto devices (at our own risk) as was done with the recovery otherwise ... people are getting trapped buying devices they didn't know were ISP locked devices and being stuck without being able to udpate for seurity etc.  

  0  
  0  
#3
Options