can you share that ?? 
Hello!
I just installed xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin (sha256: fb76527c8b8f08f440c1571f815550dd7f553da2c2890273a83841ab77189b39) as an upgrade via LuCI.
Unfortunately, after that, the router stopped working. The LED lights up normally, but there is no communication with it (ssh/http). It only responds to pings.
After a reset using the reset button, the router returned to its default IP (192.168.1.1), whereas previously it operated as a dumb AP with a different address. Unfortunately, there is still no open SSH/HTTP port.
Does anyone have any ideas on how I can revert to the previous version of OpenWrt?
Thank you!
[update]
I have just installed the latest snapshot. It looks like the previous error has already been fixed. Working build is from Sun Jun 9 19:49:58 2024.
1 Like
Had the same issue with mine, but do not have serial to troubleshoot what was causing it.
Because I am running the ubootmod with recovery partition, it was very easy to fix. Simply unplug the power cable, keep the reset button pressed (the one in the hole not the easily accessible mesh button), and replug the power -- once DHCP serves you the IPv4 address the router should be ready to SSH into 192.168.1.1, and from there you can sysupgrade the last known working image (i.e., SCP the image to /tmp and run sysupgrade -v /tmp/imagename.itb).
If you are running the stock uboot, then you need to use TFTP (instructions here).
1 Like
Thanks! Unfortunately, I am running the stock uboot.
I have already tried TFTP but without success. The router seems to enter this mode, but even with the firewall disabled, I don't see anything in the tftpd logs on my computer.
I will try to work on it with another computer.
If that doesn't help, I will try to access it through the serial connection.
[UPDATE]
It worked with TFTP.
So I'm now fully up and running with Immortal thanks to hecataes help, but realised I'm way out of my depth with options 
I did eventually find my way on setting the wifi passwords and ssids for both 2.4 and 5ghz, but there are many many options that I'm not sure about, and thinks such as MU-MIMO that I can see that look to be turned off as default, when I'd have thought they should be on surely as a feature? plus it defaulted 20hz for 2.4 and 80hz for 5gh rather than 40 and 160?
So for baseline good starter for a noob like me is there any recommended overall settings/guides on what I should get for a main baseline to at least know I'm likely optimal?
Also, is it normal that CPU Usage seems to always show 100%? (tho no issues on running)
I have uploaded my build on GitHub-AX3000T-issue.
The admin IP is 192.168.31.1, luci / mtd-rw / ddns / wireguard / adblock / ttyd / sftp / nano.....added.
1 Like
I would fully recommend opening a new thread in the installing and using Openwrt forum.
I've been using Openwrt since Backfire on the Netgear DG834, so how I do things may not be how things are meant to be done.
1 Like
Cheers will do
Before i want to purchase this router, I want to ask if this processor has enough power for sqm and adblock. I have 250/50 mbits internet
Enough.......:!
1 Like
I installed adguardhome with 300000 rules from the blocklists, no SQM. Every time the list is updated (24h by default) the router reboots, most probably due to lack of memory. Then, I bought the redmi ax6000, no issues with adguardhome and SQM and mesh.
With cake, i can get a maximum is 450 mbps on a 1000/380 internet.
1 Like
Ok, that should be enough. Is the cpu fully used on heavy load?
Yes, it has more than 80% CPU load.
1 Like
Can someone please help me with low internet speed with the isp ap i got nearly 200 Mbps download n haft of that one upload but with openwrt ap i got nearly 50 Mbps download n 50 Mbps upload in my ap software, hardware offload, iqrbalace already enable
Hi everyone,
I'm trying to install openwrt on my AX3000T (RD23) and I'm stuck on the sysupgrade command. Using sysupgrade -n is not supposed to restart the router, but the command fails with the following message:
Cannot unmount /dev: resource busy
After that message, the router restarts. I'm out of ideas. Anyone knows what could possibly be wrong, or point me in the right direction?
full logs
verifying sysupgrade tar file integrity
Sat Jun 8 00:10:28 UTC 2024 upgrade: Commencing upgrade. Closing all shell sess ions.
Watchdog handover: fd=3
- watchdog -
Watchdog does not have CARDRESET support
Sat Jun 8 00:10:29 UTC 2024 upgrade: Sending TERM to remaining processes ...
Sat Jun 8 00:10:29 UTC 2024 upgrade: Sending signal TERM to ntpd (1890)
Sat Jun 8 00:10:29 UTC 2024 upgrade: Sending signal TERM to ntpd (1916)
Sat Jun 8 00:10:33 UTC 2024 upgrade: Sending KILL to remaining processes ...
Sat Jun 8 00:10:33 UTC 2024 upgrade: Sending signal KILL to ntpd (1890)
Sat Jun 8 00:10:35 UTC 2024 upgrade: Sending signal KILL to ntpd (1916)
[ 84.540836] stage2 (2254): drop_caches: 3
Sat Jun 8 00:10:43 UTC 2024 upgrade: Switching to ramdisk...
[ 85.814117] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[ 85.827850] UBIFS (ubi0:1): un-mount UBI device 0
Sat Jun 8 00:10:44 UTC 2024 upgrade: Performing system upgrade...
verifying sysupgrade tar file integrity
[ 86.182258] ubi1: default fastmap pool size: 10
[ 86.186818] ubi1: default fastmap WL pool size: 5
[ 86.191511] ubi1: attaching mtd8
[ 86.307082] ubi1: scanning is finished
[ 86.316215] ubi1: attached mtd8 (name "ubi_kernel", size 34 MiB)
[ 86.322227] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 86.329105] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 86.335891] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 86.342839] ubi1: good PEBs: 272, bad PEBs: 0, corrupted PEBs: 0
[ 86.348836] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 12 8
[ 86.356048] ubi1: max/mean erase counter: 6/4, WL threshold: 4096, image sequ ence number: 817418172
[ 86.365078] ubi1: available PEBs: 213, total reserved PEBs: 59, PEBs reserved for bad PEB handling: 19
[ 86.374383] ubi1: background thread "ubi_bgt1d" started, PID 2985
UBI device number 1, total 272 LEBs (34537472 bytes, 32.9 MiB), available 213 LE Bs (27045888 bytes, 25.7 MiB), LEB size 126976 bytes (124.0 KiB)
[ 86.465813] block ubiblock0_0: released
Volume ID 0, size 34 LEBs (4317184 bytes, 4.1 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "kernel", alignment 1
[ 86.834167] block ubiblock0_0: created from ubi0:0(rootfs)
Volume ID 0, size 34 LEBs (4317184 bytes, 4.1 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 71741440
Volume ID 1, size 565 LEBs (71741440 bytes, 68.4 MiB), LEB size 126976 bytes (12 4.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umoun[ 89.660856] reboot: Restarting system
t: can't unmount
EDIT: slightly different logs, after starting the full process all over again
full logs v2
verifying sysupgrade tar file integrity
Thu Jan 1 00:01:07 UTC 1970 upgrade: Commencing upgrade. Closing all shell sessions.
Command failed: Watchdog handover: fd=3
- watchdog -
Watchdog does not have CARDRESET support
Thu Jan 1 00:01:07 UTC 1970 upgrade: Sending TERM to remaining processes ...
Thu Jan 1 00:01:07 UTC 1970 upgrade: Sending signal TERM to ntpd (1930)
Thu Jan 1 00:01:07 UTC 1970 upgrade: Sending signal TERM to ntpd (1957)
Thu Jan 1 00:01:11 UTC 1970 upgrade: Sending KILL to remaining processes ...
Thu Jan 1 00:01:11 UTC 1970 upgrade: Sending signal KILL to ntpd (1930)
Thu Jan 1 00:01:13 UTC 1970 upgrade: Sending signal KILL to ntpd (1957)
[ 82.058121] stage2 (2306): drop_caches: 3
ubidetach: error!: cannot detach mtd9
error 19 (No such device)
ubiformat: mtd9 (nand), size 81788928 bytes (78.0 MiB), 624 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 623 -- 100 % complete
ubiformat: 624 eraseblocks have valid erase counter, mean value is 2
ubiformat: formatting eraseblock 623 -- 100 % complete
ubidetach: error!: cannot detach mtd8
error 19 (No such device)
ubiformat: mtd8 (nand), size 35651584 bytes (34.0 MiB), 272 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 271 -- 100 % complete
ubiformat: 272 eraseblocks have valid erase counter, mean value is 2
ubiformat: formatting eraseblock 271 -- 100 % complete
failed to access u-boot-env. skip env setup.
Thu Jan 1 00:01:30 UTC 1970 upgrade: Switching to ramdisk...
Thu Jan 1 00:01:31 UTC 1970 upgrade: Performing system upgrade...
verifying sysupgrade tar file integrity
[ 91.623172] ubi0: default fastmap pool size: 10
[ 91.627750] ubi0: default fastmap WL pool size: 5
[ 91.632443] ubi0: attaching mtd8
[ 91.749125] ubi0: scanning is finished
[ 91.758185] ubi0: attached mtd8 (name "ubi_kernel", size 34 MiB)
[ 91.764196] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 91.771073] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 91.777854] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 91.784802] ubi0: good PEBs: 272, bad PEBs: 0, corrupted PEBs: 0
[ 91.790799] ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
[ 91.798013] ubi0: max/mean erase counter: 4/3, WL threshold: 4096, image sequence number: 1384604883
[ 91.807133] ubi0: available PEBs: 247, total reserved PEBs: 25, PEBs reserved for bad PEB handling: 19
[ 91.816435] ubi0: background thread "ubi_bgt0d" started, PID 3045
UBI device number 0, total 272 LEBs (34537472 bytes, 32.9 MiB), available 247 LEBs (31363072 bytes, 29.9 MiB), LEB size 126976 bytes (124.0 KiB)
[ 91.852282] ubi1: default fastmap pool size: 30
[ 91.856839] ubi1: default fastmap WL pool size: 15
[ 91.861619] ubi1: attaching mtd9
[ 92.129816] ubi1: scanning is finished
[ 92.139106] ubi1: attached mtd9 (name "ubi", size 78 MiB)
[ 92.144509] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 92.151386] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 92.158176] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 92.165123] ubi1: good PEBs: 624, bad PEBs: 0, corrupted PEBs: 0
[ 92.171214] ubi1: user volume: 0, internal volumes: 1, max. volumes count: 128
[ 92.178430] ubi1: max/mean erase counter: 4/3, WL threshold: 4096, image sequence number: 1297790934
[ 92.187551] ubi1: available PEBs: 599, total reserved PEBs: 25, PEBs reserved for bad PEB handling: 19
[ 92.196859] ubi1: background thread "ubi_bgt1d" started, PID 3069
UBI device number 1, total 624 LEBs (79233024 bytes, 75.5 MiB), available 599 LEBs (76058624 bytes, 72.5 MiB), LEB size 126976 bytes (124.0 KiB)
Volume ID 0, size 34 LEBs (4317184 bytes, 4.1 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "kernel", alignment 1
[ 92.268778] block ubiblock1_0: created from ubi1:0(rootfs)
[ 92.274267] ubiblock: device ubiblock1_0 (rootfs) set to be root filesystem
Volume ID 0, size 34 LEBs (4317184 bytes, 4.1 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 71741440
Volume ID 1, size 565 LEBs (71741440 bytes, 68.4 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umoun[ 95.117824] reboot: Restarting system
t: can't unmount
F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [1000]
T0: 0000 024F [010F]
Jump to BL
Thank you!
A few notes:
fw_setenv flag_last_successshould be0forfirmware=1and/dev/mtd8as shown here. With1I got bootloops.- I was able successfully install OpenWrt U-boot as described here.
No moreflag_try_sys1_failed. - It's possible to access UART pins without opening the router, though the holes in a case. I realized that after opened it =) . Hair dryer will help not to damage sticker/label.
sysupgradewill reboot the router automatically.
@zeluis9 , try fw_setenv flag_last_success 0
2 Likes
Not sure where to put this information, but I had wired connection problems (roughly 50% packet loss) which prevented me from running xmir-patcher. The solution was to disable the auto WAN selection in the original FW.
My guess is that when the router is not connected to the internet, it tries all ports one by one as WAN, so it resets the network quite often.
Hope this helps someone...
2 Likes
trying to use fw_setenv always results in the following:
root@(none):/# fw_setenv flag_last_success 0
Cannot parse config file '/etc/fw_env.config': No such file or directory
Failed to find NVMEM device
Error: environment not initialized
I tried to create the file manually (vi /etc/fw_env.config) but the same error persists.
Is the router at a fresh install already have 40% of memory used for you guys?
i installed sqm, luci, and luci-ssl. So far it already has 55% memory used, anyone has other software installed? like can the router handle it without errors in the long run?
1 Like