If your new router has firmware 1.0.84 (or later), then it is very likely that you bought a new revision of the RD03 router (installed new switch AN8855). Official OpenWrt images is not support switch AN8855!
Also, do not downgrade the stock firmware on router with switch AN8855!
Note: official snapshot images do not have LuCI webui Note: remittor's images v23.05.5 support NAND chip Winbond W25N01KV Note: remittor's images v23.05.5 support NAND chip Foresee F35SQA001G Note: remittor's images v23.05.5 support switch Airoha AN8855
I just followed the "Easy Method" to install OpenWrt, and unfortunately it bricked my device (orange led during power on, then it turns off and nothing else happens). See XMiR-Pactcher output below.
My device was configured as Access Point in the original firmware, I'm not sure if this could cause the issue. When I have time I will try to unbrick it and try again.
==========================================================
Xiaomi MiR Patcher
1 - Set IP-address (current value: 192.168.1.128)
2 - Connect to device (install exploit)
3 - Read full device info
4 - Create full backup
5 - Install EN/RU languages
6 - Install Breed bootloader
7 - Install firmware (from directory "firmware")
8 - {{{ Other functions }}}
9 - [[ Reboot device ]]
0 - Exit
Select: 2
device_name = RD03
rom_version = 1.0.47 release
mac address = 7c:83:xx:xx:xx:xx
Current CountryCode = CN
Enter device WEB password: xxxxxxx
Run SSH server on port 22 ...
#### SSH server are activated! ####
==========================================================
Xiaomi MiR Patcher
1 - Set IP-address (current value: 192.168.1.128)
2 - Connect to device (install exploit)
3 - Read full device info
4 - Create full backup
5 - Install EN/RU languages
6 - Install Breed bootloader
7 - Install firmware (from directory "firmware")
8 - {{{ Other functions }}}
9 - [[ Reboot device ]]
0 - Exit
Select: 7
device: "RD03"
img_write = True
Image files in directory "firmware/":
"firmware/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-stock-initramfs-factory.ubi"
Download file: "/tmp/dmesg.log" ....
Download file: "/tmp/mtd_list.txt" ....
Download file: "/tmp/mtd_addr.txt" ....
Download file: "/tmp/mtd_ro.txt" ....
Download file: "/tmp/kcmdline.log" ....
Parse all images...
UBI: filetype: b'UBI#'
UBI: Decoding UBIFS...
UBI: volume: "kernel" size: 19173376
parse_ubifs = 1
FIT size = 0x123CA10 (18674 KiB)
FIT: name = "ARM64 OpenWrt FIT (Flattened Image Tree)"
FIT: def_cfg: "config-1"
FIT: def_fdt: "fdt-1"
FDT: desc = "ARM64 OpenWrt xiaomi_mi-router-ax3000t-stock device tree blob"
FDT: type = "flat_dt"
FDT: arch = "arm64"
KRN: desc = "ARM64 OpenWrt Linux-5.15.137"
KRN: type = "kernel"
KRN: arch = "arm64"
KRN: compression = "lzma"
KRN: data = 3770699 bytes
FDT: compatible = ['xiaomi,mi-router-ax3000t-stock', 'mediatek,mt7981']
FDT: model = "Xiaomi Mi Router AX3000T (stock layout)"
FDT: dt_part: ['/spi@1100a000/flash@0/partitions']
FIT: Founded "initrd-1" node
FIT: initrd image name: "ARM64 OpenWrt xiaomi_mi-router-ax3000t-stock initrd"
fw_img: 20224 KiB | kernel: 18674 KiB | rootfs: 14968 KiB
Download file: "/tmp/bl_BL2.bin" ....
Download file: "/tmp/bl_FIP.bin" ....
Download file: "/tmp/env_Nvram.bin" ....
Download file: "/tmp/env_Bdata.bin" ....
Download file: "/tmp/env_BL2.bin" ....
current flag_boot_rootfs = 0
install_method = 400
--------- prepare command lines -----------
fw_img: 20224 KiB | kernel: 18674 KiB | rootfs: 14968 KiB
------------- flash images -------------
Upload file: "tmp/fw/fw_img.bin" ....
Run scripts for change NVRAM params...
Boot from firmware [1] activated.
Writing firmware image to addr 0x02800000 ...
mtd -e "ubi1" write "/tmp/fw_img.bin" "ubi1"
The firmware has been successfully flashed!
Send command "reboot" via SSH/Telnet ...
ERROR: SSH execute command timed out! CMD: "reboot -f"
==========================================================
Xiaomi MiR Patcher
1 - Set IP-address (current value: 192.168.1.128)
2 - Connect to device (install exploit)
3 - Read full device info
4 - Create full backup
5 - Install EN/RU languages
6 - Install Breed bootloader
7 - Install firmware (from directory "firmware")
8 - {{{ Other functions }}}
9 - [[ Reboot device ]]
0 - Exit
Select:
Update 1: my device was not really bricked, OpenWrt install was actually sucessfull. Some notes here that may help others in the future:
It seems that the standard OpenWrt LED behavior is configured differently in remittor's build (I was expecting a quick orange blink then slow blink while OpenWrt loads, then steady blue when OpenWrt boot completes). So after OpenWrt boots with remittor's build, the AX3000T LED behavior is to go from solid orange to off (probably LED is reporting the WAN status, but I haven't tested to confirm this since I did not have a WAN connection during the flashing procedure).
This device does not have the WAN port clearly identified (I believe that the original firmware can use any port as WAN, but I'm not sure). The WAN port used by OpenWrt is the one close to the power connector. I was using this port after the initial OpenWrt flash, and for this reason I had no access to 192.168.1.1. I just connected the ethernet cable to another Ethernet port and everything worked as expected.
Update 2: just flashed the WR30U image and the AX3000T LED is now working fine (it is reporting system status, orange flashing quickly then slowly when OpenWrt boots, then steady blue when OpenWrt boot completes).
FWIW I firstly flashed ubootmod build from Dimfish and since I wanted to use builds from eko.one.pl, I flashed WR30U image and everything seems to be working fine - except for NFC, which I don't use.
At one point I made a mistake and feared I bricked my router (with i_want_a_brick) - it powered on with a blue light, responded to ping on 192.168.1.1 but with no open ports. It turned out that this is a recovery mode and it looks for a TFTP server at 192.168.1.254.
Does it matter where I buy this router from when it comes to channel availability/restrictions?
Since routers for the Chinese market usually do not support 5GHz channels between 96 - 144, for Mediatek based platforms like this Xiaomi is it hardware limited in the SOC or it it only software limited and can these channels be used in OpenWRT?
Thanks, I flashed many devices that were sold for my region with OpenWRT before and they worked fine. I just never tried a router for a different market and with different stock channel restrictions, I assume the AX3000T has no hardware limits in which channels you can use then.
Just flashed the latest build from Remittor using XMiR-Patcher. The instructions worked first try, my AX3000T was on stock firmware 1.0.47 from the factory.
Looking good so far, I did a quick iperf3 test;
Server: Laptop, wired connection (1Gbit) direct to router.
Client: iPhone 12 connected to 5 GHz network from router @ 1 meter distance.
I also got good Wifi speeds (802.11ax@80MHz) close to the AX3000T (line of sight, same room).
However when testing WiFi speed in another room with a brick wall between the device (iPhone 13 Pro) and the AX3000T, Wifi speeds were really bad. If possible, could you please test AX3000T WiFi speeds in another room, especially upload speeds?
I am wondering this device is suffering the same issue as the Redmi AX6S/Xiaomi AX3200/Belkin RT2000, which was only solved after disabling 160MHz support from the build - details below:
When I have time I will do additional tests with the AX3000T and apply the workarounds in the above thread to see if it improves the Wifi speeds in this situation.
Sure, if I don't forget I will try more tests one of these days and report back.
I was playing around with 80 and 160 MHz on different channels and noticed something interesting.
When I select 160 MHz and set the channel to 149 or higher the wireless overview shows the corresponding frequency somewhere in the 6 GHz band (channel 165 as 6.775 GHz, suggesting WiFi 6E?!). My WiFi 5/6 devices can't see the network at all anymore, unfortunately I can't tell if it's actually transmitting at 6 GHz as I don't have any 6E devices yet.
So far I found one post mentioning this on a different MTK chipset, but it seems the other way round than what I see:
No problem for me though, I can set 160 MHz on channels 100 - 128 where it seems to work normally.
Just did some more tests, with the same conditions as before (laptop with iperf3 running wired to AX3000T, build 12-12-2023 from Remittor).
I tested with both iPhone 12 and Samsung Galaxy A52s, only A52s has 1x1 configuration compared to iPhone 12 with 2x2.
On the A52s I used the app 'Aruba Utilities' which has a iperf3 client, I set it to run for 30 seconds and use 5 parallel streams (just like in the iPhone app).
iPhone 12 (2x2 AX, 5GHz 80MHz):
Download @ ~3 meter behind brick wall: 743 Mbits avg. (607 min / 844 max)
Upload @ ~3 meter behind brick wall: 654 Mbits avg. (618 min / 710 max)
Download @ ~7 meter behind brick wall: 513 Mbits avg. (274 min / 637 max)
Upload @ ~7 meter behind brick wall: 162 Mbits avg. (35 min / 425 max)
It looks like I get upload speeds as low as 35 Mbits with the iPhone 12 when behind a brick wall at about 7 meter distance. The A52s had much better performance, and the speeds looked pretty stable between each update period even on upload at 7 meter.
I can't tell if it is related to iPhone vs Android, or the fact that the A52s only uses 1x1 configuration.
Thank you for the additional testing! This issue seems to be the same as the Redmi AX6S/Xiaomi AX3200/Belkin RT2000. It affects mostly Apple mobile devices. It was only solved when 160Mhz was disabled in the mt76 driver.
Using remittor's 'Easy Method' (Xmir-Patcher) and their 23.05 build I got my AX3000T converted to OpenWRT in 15 minutes.
Original firmware was version 1.0.47
I did have one issue where the initramfs would not complete the firmware upload with the sysupgrade image. This may have been due to using Safari on a mac. I scp'd the sysupgrade image to the AX3000T and completed the upgrade from the commandline without any issue.
For anyone who doesn't know how to use scp the command was
I'm trying to downgrade the firmware from 1.0.64 to 1.0.47 without success: after choosing and trying to install the correct 1.0.47 firmware file from the Openwrt installation tutorial, i get the following message (in Chinese): "The file does not exist or is damaged. You can try downloading it again.", and then the upgrading/downgrading process proceeds, however when it ends the firmware ver. remains 1.0.64. I tried to redownload the firmware file in a different browser but the problem remains.
