I think it is released before some minutes
At least it flashes unlike 24.10.0 release 
Did you upgrade any rc(1-7) version to 24.10.1 via luci?
p.s. did the following:
uci set system.@system[0].compat_version="2.0"
uci commit
UPDATE:
tested rc7 to 24.10.1 with two lines above, seems ok.
I guess, if works with Luci, should also work with sysupgrade.
I tried. Its worked.
facinstall too
Had rc7 for few weeks and had no problems, but couple of days back 5ghz radio stopped working.
Mon Apr 14 18:24:54 2025 daemon.notice netifd: radio1 (4010): WARNING: Variable 'data' does not exist or is not an array/object
Mon Apr 14 18:24:54 2025 daemon.notice netifd: radio1 (4010): Phy not found
Mon Apr 14 18:24:54 2025 daemon.notice netifd: radio1 (4010): Could not find PHY for device 'radio1'
Mon Apr 14 18:24:54 2025 daemon.notice netifd: Wireless device 'radio1' set retry=0
Mon Apr 14 18:24:54 2025 daemon.crit netifd: Wireless device 'radio1' setup failed, retry=0
Mon Apr 14 18:24:54 2025 daemon.notice netifd: radio1 (4018): WARNING: Variable 'data' does not exist or is not an array/object
Mon Apr 14 18:24:54 2025 daemon.notice netifd: radio1 (4018): Bug: PHY is undefined for device 'radio1'
Mon Apr 14 18:24:54 2025 daemon.notice netifd: Wireless device 'radio1' is now down
Upgraded rc7 to 24.10.1, than did firmware reset, and this is the screenshot of what's there now (radio1 is not there at all):
What's this about?
1 Like
Yes I did upgrade from 23.05.5. AFTER I MADE A BACKUP OF THE CURRENT CONFIG, I followed these instructions: https://openwrt.org/toh/xiaomi/ax3200#upgrading_from_2305_and_earlier_to_upcoming_2410_or_snapshot
But I changed the path from the snapshot image to the image used in the firmware selector (https://downloads.openwrt.org/releases/24.10.1/targets/mediatek/mt7622/openwrt-24.10.1-mediatek-mt7622-xiaomi_redmi-router-ax6s-factory.bin)
All went fine, after the last command from the instructions the router booted with factory defaults. I restored my backup and have the old configuration running on the new 24.10.1 firmware.
1 Like
on 24.10.1 with wed enabled there is again stability issues as like 24.10 rc7
Peoples, any ideas? 5ghz radio is just not there
Hello! As of approximately April 14, 2025, version "24.10.1" is available.
Iām seeking help for newcomers. Is 24.10.1 considered production-ready?
Questions:
-
Is the soft brick issue after six reboots still present? If so, what is the current method to resolve it? Should it be addressed using
init.rc?
Please explain this to me as if I were a preschooler!
Additionally, is there still any concern regarding the bootloader version? -
On the OpenWrt download page for 24.10.1 targeting MediaTek MT7622, only "Xiaomi Redmi Router AX6S" is listed.
Should this firmware also be used for the Xiaomi AX3200? -
Does WED (Wireless Ethernet Dispatch) work in this version?
Are there any performance benefits if only the 2.4 GHz Wi-Fi band is used (for example, in regions where the 5 GHz band is restricted by local laws or regulations)? -
Is the Ubi-loader required only for updates from OpenWrt versions prior to March 23, 2025?
If Iām performing a fresh installation of 24.10.1 using Xmir-Patcher (which is clearly a post-March 2024 release), am I correct that the Ubi-loader is not necessary?
Additionally, what could happen if the Ubi-loader is installed on version 24.10.1 due to a misunderstanding of the instructions?
Thank all for your support!
1 Like
23.05 firmware, on Wifi 2.4Ghz, the clients seem to experience a temporary drop on connection, then it catches up. Any reason, setting that can be tweaked on the router or phone? These are phones that don't have a 5Ghz Wifi.
versions 24.10 and 24.10.1 are not stable on the ax3200/ax6s
I have 4 devices here, 1 rb03 and 3 rb01.
On the rb03 device, it was hell to upgrade from 23.05.05 to 24.10. Even after following the step-by-step instructions on the wiki, the device was soft bricked and only came back with the original FW recovery via tftp.
I was persistent and managed to get version 24.10 on the rb03, and since it is a remote device, I haven't even tried to upgrade to 24.10.1 yet.
Now on the 3 rb01s, the process of unlocking ssh/telnet on the original FW -> flash version 23.05.05 -> upgrade 24.10 (using the wiki's step-by-step instructions) happens without any apparent problems.
I only discovered that, being on version 24.10, with the power outage that occurred here, 2 devices were soft bricked upon reboot, and on the 3rd device, after ~24h after the power was restored, the 2.4Ghz wifi simply stopped working and upon rebooting the device it was soft bricked.
Now with the new version 24.10.1, I took one of the RB01s and did the process, tfpt fw stock 1.0.71 -> unlock ssh/telnet -> flash 23.05.05 -> upgrade 24.10 (using the wiki step by step) -> upgrade 24.10.1 via luci, the device does not stay on for 2h and is soft bricked.
I really don't know what's going on, the rb01 and rb03 versions are identical in hardware, the rb03 I have has been with me for 2 years and I've been through all the versions since the initial snapshot until the latest 23.05.05 without any problems, and with the release of 24.10 problems started right away.
and in the 3 rb01 units, I received them the week of the release of version 24.10, and since I basically installed this version directly, I'm having problems with them right away.
and speaking of Wireless Ethernet Dispatch (WED), it doesn't matter if you use version 23.05.05 or 24.10, if you follow the wiki's step-by-step instructions you'll be soft bricked right away.
by the way, my 4 devices work like dumb APs. They don't do nat, no firewall, no sqm, literally just vlan config, wifi networks, 802.11rkv and use of the usteer package.
2 Likes
The Xiaomi AX3200 (RB01) and Redmi AX6S (RB03) are exactly the same device in terms of PCB and components.
The difference between them is in the original FW, which the RB01 version has some locks and is more "annoying" to enable Telnet and SSH.
The RB03 version released an original FW for testing with Telnet enabled, which makes it much easier to install OpenWRT.
I am maximally sorry, but personally i do not accept this as a straightforward answer. Even more, I am confused now - is the WED causes soft bricks?
I'll keep the questions.
-
Is the soft brick issue after six reboots still present on 24.10.1? Should i add nvram (or any other) commands to init.rc or do whatever else to prevent soft brick upon reboots?
-
Is it right to use firmware named "xiaomI" "ax6s" for ax3200?
-
Should i worry about WED if no 5Ghz is planned to be used? (Due to local restrictions, for example, or client devices simply not have 5Ghz transceivers)
-
What the heck is the ubi-loader? Is it patch only for 23.x to 24.x firmware update? What will happen if any one try to install ubi-loader after 24.x firmware already up and running?
-
Taking @dudu1505 story into account, is the WED causes soft-bricks? Is the wiki misleading?
-
Taking @dudu1505 story into account, IS 23.05.05 stable? Is the softbrick after reboots have to be manually handled?
There are 2170+ messages already on the thread, and a lot of confusing/outdated/contradictory info, including probably missleading wiki. I've spend a day reading, but no luck to figure out the results.
I believe so.
No one cares. Hardware is the same.
Why would you be worried at all? It comes disabled. Just don't enable it.
What exactly is misleading? I don't recall having problems using it.
Thank you, @timur.davletshin.
So what is the current method of preventing reboots-counter-related softbricking?
And, should anyone take care of bootloader version (it started long ago as i can see - post 1688, for example)?
Here with me, when the device is soft bricked, the system LED, which when everything is working normally, stays solid blue. During the boot process, the color stays yellow/orange for 5 seconds in solid color and then it reboots automatically.
Since it is a soft bricked case, uboot is still working correctly, so much so that it is possible to recover the device via tftp.
But something is happening in this process of uboot booting into openwrt.
Unfortunately, I don't have a uart adapter here to connect to the PCB and see the uboot boot logs.
I forgot to mention, there is a way to force soft bricking in version 24.10, when the system is booting with the system LED flashing blue, randomly if the power is cut, the device goes into soft bricking.
It doesn't always happen, but in my tests here, this soft bricking happened 3 times, in 20 attempts.
the problem is, the wiki's step by step:
"
Edit /etc/modules.d/mt7915e and append this line mt7915e wed_enable=Y
This change requires a reboot
"
If I do this procedure, just need to reboot and soft bricking is guaranteed.
Set flag_try_sys1_failed and flag_try_sys2_failed to anything bigger than 7.
EDIT: The link you have provided is correct.
That is odd because it works for me just as it is described in wiki. Last tested on 24.10.0.