OpenWrt support for Xiaomi AX3000T

Hi, follow the installation instructions: (https://openwrt.org/inbox/toh/xiaomi/ax3000t)

You did not do the nvram set: ?

set nvram

If firmware=0

ubiformat /dev/mtd9 -y -f /tmp/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi

nvram set boot_wait=on ----------------> enable "boot_wait" for boot menu
nvram set uart_en=1 --------------------> enable "uart_en" input
nvram set flag_boot_rootfs=1
nvram set flag_last_success=1
nvram set flag_boot_success=1
nvram set flag_try_sys1_failed=0
nvram set flag_try_sys2_failed=0
nvram commit
reboot


If firmware=1

ubiformat /dev/mtd8 -y -f /tmp/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi

nvram set boot_wait=on ---------------> enable "boot_wait" for boot menu
nvram set uart_en=1 --------------------> enable "uart_en" input
nvram set flag_boot_rootfs=0
nvram set flag_last_success=0
nvram set flag_boot_success=1
nvram set flag_try_sys1_failed=0
nvram set flag_try_sys2_failed=0
nvram commit
reboot

I do not know how to solve your problem.
Try to back to factory fw.

1 Like

I'm planning to buy one, is this router has the same issue in 160Mhz WiFi like the Xiaomi AX3200?

Try to loop your uart adapter (rx to tx). If it dont echo your adapter is toast, if it echos you mabe use a 5v rs232 adapter?

1 Like

And what issue AX3200 has?

For what it is worth: I'm currently running two AX3200 one AX3000T and one AX6000 all of them with 160Mhz, no issues regarding that...

Hi everyone, I just got myself a Xiaomi AX3000T.

Is there any downside to installing OpenWrt over stock firmware? eg: Weaker wifi signal, slower Lan etc Or anything at all?

How to I test to see what flash memory I have? I read if you install standard build on newer flash it will brick.

Thanks

To be honest haven't really given the stock firmware a chance (and I don't know Chinese...) OpenWRT works great for my usecase, fast wifi, strong signal, and features that is not available in the stock firmware, and updates.

What flash you have: look through the underside, at the right spot, with a flashlight and read the brand name of the chip..., wiki has the instructions...

2 Likes

Hello. I have problem with my Xiaomi AX3000T. I've got it with winbond chip and with 1.0.84 firmware. I couldn't downgrade. I tried to flash it with UART but no luck. I can't connect router to notebook via any port. Tried every of them, mostly tried 3rd from left side. Also tried tftp server on Windows with disabled firewall and ubuntu. No any devices between notebook and router - straight cable.

What WiFi settings are you currently using? The performance here (1000/800 Mbps bandwidth) is worse than the stock version.

Do you mean 1.0.64 or 1.0.84?

You can't get 1000mpbs from 1G port. So what it is?

1.0.84. Information about this firmware on internet is only on chineese telegram channel. I can't get ethernet ports to work. Do you know if is it possible to flash firmware via uart?

I'm not trying to achieve 1000 Mbps; I'm just providing information about my ISP.

With the stock firmware, I can achieve about 300 Mbps in the farthest room of my house. However, when using OpenWRT, I barely reach 40 Mbps in the same location.

Hi I Buy 10 of RD23 and this way is work for me
i make installation process For You . Good Luck.

Summary

install Process (Xiaomi AX3000T) Just RD23 Version Support ME (Even 1$)USDT Tron Network=TLbRrYzZEK9s3of71Xsj4EeWzLvWz6bVwu

In 1. Folder
Run CMD As Admin
mtk_uartboot -s COM10 --payload bl2-mt7981-bga-ddr3-ram.bin --aarch64 --fip openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip
mtk_uartboot -s COM10 --payload bl2-mt7981-bga-ddr3-ram.bin --aarch64 --fip openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip&& putty.exe -serial COM10 -sercfg 115200,8,n,1,N
Press ENter Fast

in 2. Folder
lan to middle port of router
ip 192.168.1.254
open tftpd64

in 3. Folder
upload openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi to /tmp/ With WINSCP
Run Command In Putty
ubidetach -p /dev/mtd8
ubiformat /dev/mtd8 -y -f /tmp/openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi
reboot

in 3. Folder
upload openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin to /tmp/ With WINSCP
Run Command In Putty
sysupgrade -n /tmp/openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin

After First Boot Run Command Again
fw_setenv flag_try_sys1_failed 0
sed -i '/exit 0/i fw_setenv flag_try_sys1_failed 0' /etc/rc.local
fw_printenv
reboot

in Uboot Select Load Image
Set Lan ip 10.100
Input load address: 0x46000000
Select (enter for default): 0
Input U-Boot's IP address: 192.168.10.1
Input TFTP server's IP address: 192.168.10.100
Input IP netmask: 255.255.255.0
Input file name:openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb
Open TFTPD
Run loaded data now? (Y/n): Y

Run Command
ubidetach -p /dev/mtd8; ubiformat /dev/mtd8 -y; ubiattach -p /dev/mtd8
mtd erase Nvram
(YOu Locked Uboot Not Worry) and Get Boot Loop OK Back TO First

In 1. Folder
Run CMD As Admin
mtk_uartboot -s COM10 --payload bl2-mt7981-bga-ddr3-ram.bin --aarch64 --fip openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip
mtk_uartboot -s COM10 --payload bl2-mt7981-bga-ddr3-ram.bin --aarch64 --fip openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip&& putty.exe -serial COM10 -sercfg 115200,8,n,1,N
Press ENter Fast

in 2. Folder
lan to middle port of router
ip 192.168.1.254
open tftpd64

in 3. Folder
upload openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi to /tmp/ With WINSCP
Run Command In Putty
ubidetach -p /dev/mtd8
ubiformat /dev/mtd8 -y -f /tmp/openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi
reboot

After 6 Bootloop intiram Booted

in 3. Folder
upload openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin to /tmp/ With WINSCP
Run Command In Putty
sysupgrade -n /tmp/openwrt-23.05.4-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin

After First Boot Run Command Again
fw_setenv flag_try_sys1_failed 0
sed -i '/exit 0/i fw_setenv flag_try_sys1_failed 0' /etc/rc.local
fw_printenv
reboot

Back to DHCP
Nice And Stady Good Luck DONE

(Extra)
Set ip & Gateway (Can Edit)
uci set network.lan.ipaddr="192.168.1.100"
uci set network.lan.gateway="192.168.1.1"
uci set network.lan.dns="8.8.8.8"
uci commit
/etc/init.d/network restart

Install Luci
opkg update
opkg install luci
opkg update
opkg install luci-ssl
/etc/init.d/uhttpd restart

and i Fix System Halt!
put process here if Support me

After a lot of struggle flashing, I seem to have lost wifi.


Eray — Today at 3:02 PM
<6>[    7.032528] mt798x-wmac 18000000.wifi: HW/SW Version: 0x8a108a10, Build Ti                                                                                                    me: 20221208201745a
<6>[    7.032528]
<6>[    7.263692] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Bu                                                                                                    ild Time: 20221208201806
<6>[    7.378642] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Bu                                                                                                    ild Time: 20221208202048
<4>[    7.469704] mt798x-wmac 18000000.wifi: eeprom load fail, use default bin
<4>[    7.476751] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/m                                                                                                    t7981_eeprom_mt7976_dbdc.bin failed with error -2
<4>[    7.488135] mt798x-wmac 18000000.wifi: Falling back to sysfs fallback for:                                                                                                     mediatek/mt7981_eeprom_mt7976_dbdc.bin
<4>[    7.549612] mt798x-wmac: probe of 18000000.wifi failed with error - 12

mtd1 and mtd7 appear blank. Can someone send me backups? I have the RD23 with the OWRT Uboot layout.

Thats scared me right off. So far this unit is heaps faster real world than the same spec AX3 I had before.

My wifi settings are about enabling wide channels and fast roaming for a few close clients. I can post some redacted parts of the wifi settinga, however

I saw you mentioned in a later post you measured from a long distance - I actively try to avoid that, adding more APs and making clients roam to something close rather than going for range. When all works well, all the connected clients are pretty much running at their top speed like this (2401.9 Mbit/s, 160 MHz, HE-MCS 11, HE-NSS 2) and as soon as I move away: they roam.


config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option encryption 'psk2+ccmp'
        option dtim_period '3'
        option ieee80211r '1'
        option ft_over_ds '0'
        option ft_psk_generate_local '0'
        option ieee80211k '1'
        option time_advertisement '2'
        option time_zone 'CET-1CEST,M3.5.0,M10.5.0/3'
        option wnm_sleep_mode '1'
        option bss_transition '1'
        option proxy_arp '1'
        option reassociation_deadline '20000'

config wifi-device 'radio1'
        option type 'mac80211'
        option path 'platform/soc/18000000.wifi+1'
        option band '5g'
        option channel '52'
        option htmode 'HE160'
        option country 'SE'
        option cell_density '2'
        option ht_coex '1'
        option he_bss_color '33'
        option log_level '3'

looks like i got the same version as Damian96, chinese model (RD03) with firmware version 1.0.84

Tried to roll it back to 1.0.47, after getting blue flash confirmed I rebooted and haven't been able to get an IP from it since.

Tried flashing to 1.0.64 but hasn't made a difference, any ideas on how I might be able to recover it? I've asked the seller for the original firmware, hopefully they come through.

Despite not getting an IP from the device when i try and recover it via tftp a request comes in from 192.168.31.23, seems to take the firmware file and then gives the blue flash confirmation but on reboot it still wont serve an IP - log below:

Aug 30 17:55:23 dnsmasq-dhcp[9695]: 1895304018 available DHCP range: 192.168.31.2 -- 192.168.31.254
Aug 30 17:55:23 dnsmasq-dhcp[9695]: 1895304018 vendor class: U-Boot.armv8
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 DHCPDISCOVER(enp2s0) 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 tags: enp2s0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 DHCPOFFER(enp2s0) 192.168.31.23 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 requested options: 1:netmask, 3:router, 6:dns-server, 12:hostname, 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 requested options: 17:root-path
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 next server: 192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  1 option: 53 message-type  2
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option: 54 server-identifier  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option: 51 lease-time  1h
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option: 58 T1  30m
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option: 59 T2  52m30s
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option:  1 netmask  255.255.255.0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option: 28 broadcast  192.168.31.255
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option:  3 router  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895304018 sent size:  4 option:  6 dns-server  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 available DHCP range: 192.168.31.2 -- 192.168.31.254
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 vendor class: U-Boot.armv8
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 DHCPDISCOVER(enp2s0) 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 tags: enp2s0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 DHCPOFFER(enp2s0) 192.168.31.23 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 requested options: 1:netmask, 3:router, 6:dns-server, 12:hostname, 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 requested options: 17:root-path
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 next server: 192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  1 option: 53 message-type  2
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 54 server-identifier  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 51 lease-time  1h
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 58 T1  30m
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 59 T2  52m30s
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  1 netmask  255.255.255.0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 28 broadcast  192.168.31.255
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  3 router  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  6 dns-server  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 available DHCP range: 192.168.31.2 -- 192.168.31.254
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 vendor class: U-Boot.armv8
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 DHCPREQUEST(enp2s0) 192.168.31.23 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 tags: enp2s0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 DHCPACK(enp2s0) 192.168.31.23 44:f7:70:f7:99:58 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 requested options: 1:netmask, 3:router, 6:dns-server, 12:hostname, 
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 requested options: 17:root-path
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 next server: 192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  1 option: 53 message-type  5
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 54 server-identifier  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 51 lease-time  1h
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 58 T1  30m
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 59 T2  52m30s
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  1 netmask  255.255.255.0
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option: 28 broadcast  192.168.31.255
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  3 router  192.168.31.100
Aug 30 17:55:27 dnsmasq-dhcp[9695]: 1895306019 sent size:  4 option:  6 dns-server  192.168.31.100
Aug 30 17:55:28 dnsmasq-tftp[9695]: sent /tmp/firm/C0A81F17.img to 192.168.31.23

Hi, I've been trying to get OpenWRT working since yesterday. I tried the official snapshot and Remitor's snapshot but in both instances, while it ended up booting, and i could see a solid white LED, I was unable to access OpenWRT from my PC (yes, I set my ip as 192.168.1.2 on my pc manually, and I also pinged and tried to ssh both to no avail)
In an incredibly stupid move, I then decided to install the official 23.05.4 release on my device- without realising I was using a WinBond chip.
It's now bricked and stuck at a solid orange light. Anything that can be done? I know how to use Xiaomi's Mi Wifi Recovery tool but that does not seem to be working here