כיצד לשדרג את הקושחה של הנתב Cudy?

@Dear Steve,

I mean the terminal that is connected to the P5.

“This is a cudy P5 router version 1.0.”

This is a cudy P5 router version 1.0.

@Dear Steve,
It is possible. But there is no other feedback about this issue. May be a compatible issue with specific terminal. We will try to test it. What is the brand and model of the terminal?

“Hi support team,

I confirm that past thursday I replaced the power adapter with a 12V 4A one, updated the firmware to version 2.4.25, and re-enabled 802.11ax on the Cudy P5 router. Interestingly, I noticed that today, after being active for 17 hours, the router restarted after having been up and running for 7 days the wifi config 802.11ac on 5Ghz band without any issues.

Therefore, I reconfigured 802.11ac on the 5GHz band and 802.11n on the 2.4GHz band on the Cudy router to see how the service behaves.
My question is, could this be related to a bug with 802.11ax on 5Ghz band?"

Hi support team,

I confirm that past thursday I replaced the power adapter with a 12V 4A one, updated the firmware to version 2.4.25, and re-enabled 802.11ax on the Cudy P5 router. Interestingly, I noticed that today, after being active for 17 hours, the router restarted after having been up and running for 7 days the wifi config 802.11ac on 5Ghz band without any issues.

Therefore, I reconfigured 802.11ac on the 5GHz band and 802.11n on the 2.4GHz band on the Cudy router to see how the service behaves.

My question is, could this be related to a bug with 802.11ax on 5Ghz band?

Reading the previous comments too, I’m almost certain that the intermediate file is to blame and is not accepted by the WR1500 v1.0 router.
I tried installing it via laptop and ethernet using Chrome or Explorer as the browser. The result was exactly the same.
Then I tried via WiFi with my Android mobile phone using Chrome or Opera.
Again the same results.
In the meantime, I have already updated easily on both the WR3000 and the WR3600 using the phone method without any hassle…
On the WR1500 v1.0 it simply does not work!
I believe that none of those commenting, managed to install the intermediate update.