1971

Thank you. There was no issue uploading the firmware, it was because I was uploading the firmware to the stock miwifi firmware which it reverted to because I rebooted the device.

1972

I did manage to flash to factory firmware (MiWifi repair tool) and able to flash openwrt using Xmir patcher..Did the vi /etc/rc.local and confirmed that the counter set back to 0 after multiple reboot (via UART).
Thank you all for the tutorial and tips.

1973

I happen to be an unfortunate recipient of a 1.0.84 variant with the AN8855 switch. Should I hold off on flashing for now? I was hoping to deploy a couple of units next week in an 802.11s mesh but if there is a high likelihood that it'll crash or cause issues I might just buy something else in the meantime.

1974

This version is not officially supported, but there are custom builds based on the official OpenWrt.

1975

I think you can flash to openwrt with remittor or dimfishr firmware (AN8855).Use the xmirpatcher to unlock and flash the selected firmware (not the ubootmod bootloader or firmware).Just put the fw_setenv flag_try_sys1_failed 0 to /etc/rc.local and proceed to configure the router as your network requirement.

Just give some ample time to our motivated developers to backport all the necesssary patches/drivers to make a "save working" firmware.

1976

Thanks, that will probably be the plan. You mentioned your router bricked itself after a week, something I would really like to avoid, any idea what the root cause of this issue was? If it means I need to configure a daily reboot I can probably work with that.

1 Like
1977

As per writen on previous post, you need to apply the script to reset the flag counter to /etc/rc.local. i did see the log via UART, the counter did increase before applying the patch. After applying the script, the counter always stay 0.
It can be repair via miwifi if bootloop occured since the router still use stock bootloader.

1978

My apologies I must have missed that. I'll take a look, thank you.

1 Like
1979

No problem. I happen have missed that as well. Credits goes to hardworking developers and testers of this community. :wink:

1981

Nope, didn't work. Weird cause my old PC is significantly older than her phone, and it doesn't have any issue.

I made some tests with AX mode, and disabling 802.11r makes her phone able to connect with it. I have no idea what is going on, because I have a guest network on both routers, with 2.4ghz AND 5ghz, AND 802.11r, and guess what? Her phone works with that network

EDIT: Goddamnit, the issue is WPA3. Changing from WPA2/WPA3 PSK, SAE (CCMP) to WPA/WPA2 PSK (CCMP) fixes the issue

3 Likes
1982

This didn't output anything on my machine. I though maybe it would only show up shortly after boot, so I rebooted. Now I can't even ssh in anymore, even after running the stok-based script. I also tried changing the script to stop any firewall by appending the following, but that didn't help either:

sleep 1
curl -X POST "$url" -d "${pre}%0/etc/init.d/firewall%20stop%0A${suf}"
1983

Sorry for the noise. Got it figured out.

(1) I had the misystem exploit in my bash history, but I needed xq.
(2) Running the dmesg command right after rebooting seems to help. (FYI, I wouldn't trust the output of dmesg | grep AN8855 if dmesg | grep nand doesn't show anything, though I am not an expert on this).

Now it reports I have GigaDevice, which I understand is the supported (by looking at the kernel sources and the discussions re it just being another name for EMST). I think I am good to go.

1 Like
1984

For anyone who has come here and is confused on how to get their Redmi AX3000T with 1.0.84 firmware and AN8855 switch up and running with remittor's OpenWrt build, I wrote some notes:

  1. We will need to use the XMIR Patcher to get the firmware installed. The XMIR Patcher is a set of scripts that allows us to install a firmware. To get started:

  2. Go to to the OpenWrt official page to check if any more hardware changes have happened since I wrote this post, plus you will need to download the XMIR patcher: https://openwrt.org/inbox/toh/xiaomi/ax3000t

  3. Check the “firmware” subfolder. Download your compatible firmware and place it here. As of 2024-10-26, a modified OpenWrt firmware by the user “remittor” has worked well on current hardware. The build date of the tested firmware is 241021. Link to development post: OpenWrt support for Xiaomi AX3000T - #1817 by remittor

  4. Copy this folder to a local directory so we can run BAT files. E.g. c:\tools\

  5. Open the xmir-patcher folder and run “run.bat”.

  6. Select “1” to set the IP address to the default IP address of your router on factory firmware, which is 192.168.31.1

  7. Select “2” and follow the prompt to install the exploit.

  8. Select “7” to install the firmware. This will install the .ubi firmware in the “firmware” folder.

  9. After a minute or so, a temporary installation of OpenWrt will be available on 192.168.1.1

  10. Log into OpenWrt at 192.168.1.1. Follow the prompts to complete the firmware installation. We will need to use the “sysupgrade” firmware, available in the same folder.

  11. Once the firmware is installed, log into the WebUI and set a password.

  12. If all is OK, log into the router via SSH and run the following command:

  13. sed -i '/exit 0/i sleep 5\nfw_setenv flag_try_sys1_failed 0' /etc/rc.local

  14. You are done!

6 Likes
1985

Quick question.
I set up my ax3000t with openwrt in a mesh format, I need to access the dumb ap mesh now as I am in need of changing channels.
How do I go about doing that? Can I access it remotely or do I need to plug in to it?
Thanks

1986

This guide worked for me: https://bmaupin.github.io/wiki/other/openwrt/openwrt-80211s.html

On a similar note, has anyone achieved success with 160mhz channels in 802.11s mesh? I gave it a try and it doesn't seem to connect. I tried a few different regions and channels that should work fine and I had no luck, my units simply would not connect unless I set it to 80mhz.

1 Like
1987

Does the problem reoccur?

1988

I've noticed latency spikes and speed variation yesterday, but i suspect that have interference involved is this case, due the performance come back a normal a few minutes after, without manual intervention, but i'm still monitoring...

Screenshot_20241026-213456_Speedtest
Screenshot_20241026-213456_Speedtest1080×2400 175 KB

Screenshot_20241026-212545_Speedtest
Screenshot_20241026-212545_Speedtest1080×2400 152 KB

Screenshot_20241026-212536_Speedtest
Screenshot_20241026-212536_Speedtest1080×2400 147 KB

Screenshot_20241026-212357_Speedtest
Screenshot_20241026-212357_Speedtest1080×2400 171 KB

1989

Hey, the WED guide isn't very obvious, both the main router and the dumb AP are using OpenWrt 23.05.5, I edited /etc/modules.d/mt7915e on both routers and added mt7915e wed_enable=Y

When I use cat /sys/module/mt7915e/parameters/wed_enable it returns Y on both of them. It was mentioned that I should install a packaged called Bridger when I use a dumb AP, and so, I installed it on the dumb AP, not on the main router. Did I do fine? There is a bit of ambiguity if the Bridger package should be installed on both or just on the dump ap. I'm also not sure if I should have added the line to /etc/modules.conf, the guide mentioned to use it on snapshot, but the guide was written with 22.03.2 in mind, so maybe the Snapshot part is now part of stable...?

1 Like
1990

Thanks and keep us informed. MAy be a new entry in wiki ? Thanks a lot.

1991

Hi,

Did anyone have success configuring VLANs with the new AN8855 switch? Using remittor's 23.05 build and following this tutorial based on OneMarcFifty and after creating VLAN 99 and assigning it to LAN, half of luci breaks (most views wont load), no more ssh access etc. Luckily the reset page still worked in luci. Everything else was default settings.
Whats wrong?