Hi
I have AX3000T RD23 with Global Firmware, its possible Flash (recover mode com tftpd) the firmware RD03 (chinese version ) ? I think and change to chinese version by stability i have many problems with global version…
I'm wondering if anyone has done this successfully before
Hi I installed OpenWRT, but suddenly the router stopped working and I'll have to recover it... then I was wondering if it's possible to install the Chinese firmware.
I had problems with version 25.12.1 on Google Wifi and also on the AX3000T; the routers simply stopped working and you couldn't access them either via web or SSH. I had to install version 24.10.6 on both, still testing...
I had a mesh network with 4 routers running OpenWRT 02 Google Wi-Fi and 02 AX3000T The Google Wi-Fi routers were running version 23.05 and the AX3000T routers were running version 24.10 as of routers were running different versions i decided to update everything to 25.12.0 After the update, it worked for about one hour, then they started stopping (losing web and SSH access) and also losing Wi-Fi. I had to reset everything to factory settings. In short if your network is working perfectly, dont update OpenWrt at least that was my opinion, now running OEM firmware with 03 AX3000T. I will try OpenWrt again in the future i wait to stable version.
Without specific details and configs, your opinion remains just that - an opinion. From the information provided, it is impossible to determine if the problem is config related or if there is an actual openwrt bug that affects these devices in the general topology you’ve setup.
The config:
one google wifi as pppoe and other 03 only mesh 802.11s. i did one test because had doubt i recover AX3000T to OEM and after put OpenWrt 25.12.0 without configuration, after some minutes stop works (without ssh and web page…) and after restore OEM by recover mode… no problems my friend only opinion…
This is not a config. It is a description. The config files tell the complete story and are useful for finding the issues (or determining if there is an underlying bug).
I understand now. Unfortunately, we can't know for sure if it was the settings or the firmware. No problem, I'll test it again in the future and post the results here...