Thinking of getting this, does 160MHz AP work?
Not for me
Hello all. This is the first router I have ever tried flashing custom firmware onto.
Following the flash instructions here: https://openwrt.org/inbox/toh/xiaomi/ax3000t
I got up to step 5. Flash openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin
I ran the command:
sysupgrade -n /tmp/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin
However I got the response "Image metadata not present; Use sysupdgrade -F to override this check". Now, foolishly I did exactly that and ran the command with -F flag.
In hindsight I was not aware that this file had to be downloaded first (it is not mentioned in the flashing instructions, but is mentioned in the "Terminal Upgrade Process" section) using the command:
wget https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin
What I believe has happened now is that the rooter has become bricked as a result of trying to flash non-existent firmware.
I am unable to use the Xiaomi WiFi repair tool because holding the reset button while plugging in the power cable and holding it there for another 8+ seconds no longer produces the rapidly flashing orange light, and hence the repair tool does not deploy anything to the router.
The router, without fail, flashes slowly with the orange light, and periodically will do a rapid flash for only a few seconds, before going back to a slow orange flash.
I am wondering if there is any hope for me at this point in debricking it?
I did not even get to the step "Change to OpenWrt U-Boot", and the UART debricking instructions state "Assume that you have installed OpenWrt with stock layout, with original u-boot". I don't know if this is the end of the road for me now frankly, but if anyone has any suggestions on what I can do to revive my device I would be very grateful!
Thanks.
Restore the stock firmware and start again, after carefully reading and understanding the instructions.
Anything that is not U-BOOT will not cause permanent damage to your router.
Hold the RESET button until the flashing starts, and not 6, 10, or some other time according to the timer.
And slow blinking is the normal state of the LED if the router does not see the Internet. To restore, it is better to disconnect the cable from the provider, as it may interfere with the restoration process.
Thanks for your response.
Unfortunately it does not matter how long I hold the reset button for. It will begin to flash after a while, yes, but it will flash for no more than a few seconds. Then it will go for a steady orange light, flash again for a few seconds, steady again, etc.
I am familiar with restoring the stock firmware due to earlier mishaps, but I am certain it is behaving differently this time around. I also tried debricking with TFTP, however because I cant get it to reset properly as mentioned above, I get no response.
At the moment of blinking, this is the bootloader’s request to download the file. MIWIFIRepairTool.x86 is the Chinese analogue of a TFTP recovery server, which itself automatically renames the firmware file to the desired file name and all other actions that need to be done manually for TFTP.
Like the MESH setting, for Xiaomi it is solved by pressing one button, and for openWRT it is solved by long typing on the command line.
Follow the instructions.
192.168.31.100
255.255.255.0
Load the stock firmware xxx.47 into MIWIFIRepairTool.x.86.
Press reset, turn on the power, when the LED starts blinking yellow, release and wait for the firmware loading indicator.
Disconnect your provider's cable first
Hi. After installing OpenWRT yesterday, all seems to work fine. However, WIFI Speed is not yet optimal. Was anyone able to get 1GbPS speed over WIFI with OpenWRT (I was able to get this speed with the stock firmware, now only getting 700-900).
Also, assuming I installed U-boot. Is there is an easy way to install the stock firmware back if I have to? Would MIWIFIRepairTool.x86.exe work here even after installing U-boot?
Thanks!
Hi,
Thanks again for your support.
Unfortunately I have tried exactly as you have stated, but without success. To confirm:
- Set static TCP/IPv4 IP on my windows computer to 192.168.31.100 subnet mask 255.255.255.0 for the ethernet port network adapter.
- Loaded stock firmware .47 into MIWIFIRepairTool.x.86
- Connected the router LAN port to the PC, with the WAN cable unplugged.
- Plugged in the power to the rooter while holding the reset button, releasing once the LED starts to blink rapidly (it stops blinking rapidly a few seconds later however)
- Nothing happens, the firmware loading indicator does not appear
I was able to load stock firmware .47 before I bricked the router using the above method, however now it does not work. As I stated, the rapid flashing only lasts a few seconds, whereas before when the device was working, it would flash for much longer and the repair tool would load the firmware immediately.
I have also tried:
- Using different LAN ports (all 4 do not work).
- Attempting TFTP recovery on my Linux computer (did not work, no transmission from router)
- Using a different firmware file (did not work)
I am a bit stumped now. I cannot see a clear way to open the case either, as there are no rubber feet covering screws on my device, as the wiki suggests.
the procedure is very simple, dowload the 1.0.47 firmware but rename it to C0A81F02.img (this is very important).
Download tftpd64 this is a tftp server, configure it with the following screenshots. Xiaomi ax3600 bricked - #112 by sqrwv
put the file firmware that you've renamed to C0A81F02.img in the folder.
remove the power cable, hold the reset with a pin or a simcard remover tool, and put the power cable back, after a few seconds a msg on your computer will show that the router is downloading the file, once completed leave it a little while just to make sure, 5 minutes is ok power cicle your router, the first 2 power cicles for me took a little longer.
https://bitbucket.org/phjounin/tftpd64/downloads/tftpd64.464.zip
https://cdn.cnbj1.fds.api.mi-img.com/xiaoqiang/rom/rd03/miwifi_rd03_firmware_ef0ee_1.0.47.bin
I experimented with different OpenWRT firmware snapshots on my networking device and encountered some challenges that I hope the community can assist me with. Initially, I tried the vanilla snapshot, which performed adequately. However, my curiosity led me to explore alternative builds, including those by dmifish, ramitors, and x-wrt.
During my experimentation, I observed that the kernel versions varied across these snapshots. The vanilla snapshot seemed standard, while dmifish and ramitors appeared to be based on Kernel version 5.0. In contrast, x-wrt boasted a more advanced Kernel version, around 6.15 or thereabouts.
While using the x-wrt firmware, I started experiencing intermittent issues with the IPv6 daemon randomly crashing. This unexpected behavior significantly impacted the performance and stability of my network. Despite my attempts to troubleshoot and adjust configurations, the problem persists.
I'm reaching out to uou guys for advice on how to address this issue effectively. Has anyone else encountered similar problems with the x-wrt firmware or any other builds? Are there specific steps I can take to diagnose and resolve the IPv6 daemon crashes? Additionally, I'm open to suggestions for alternative firmware builds or potential solutions to enhance the performance and reliability of my networking device.
Router arrived today and installed immediatly opewrt + openwrt uboot. Easy install when on stock 1.0.47.
Is this legit? The virus detector on my computer keeps deleting it…
I’m having the same problem. Did you make it work? If you did, how?
Antivirus must be disabled, actually, I'm not sure whether the program is safe, but that's the only way I've tried successfully to downgrade.
Hi,
Thanks for reaching out. After attempting TFTP recovery over Linux, I saw your reply and tried to give it another go over Windows.
In short, I followed the instructions provided exactly as described, however was unable to establish any communication with the router over TFTP. The log was empty the entire time while I performed numerous reboots while holding down the reset button. I believe the router is unable to enter a stable recovery mode, which is why TFTP over windows/linux has not worked.
Just to clarify the LED behaviour however:
Reboot (no reset button) = Slow flashing orange light, eventually stable orange
Reboot (reset button) = Steady orange light 8s --> Rapid blink 4s --> Steady orange light 20+ seconds ---> Rapid blink 4s ---> Steady orange light 20+ seconds... (repeat forever).
Xiaomi support were useless however they were willing to offer me a replacement device, albeit on the condition that I fly back to China where I bought it... ...so I've purchased a USB TTL adapter instead and will see if I can revive it with a UART approach while sacrificing my warranty.
Since last Monday, out of nowhere, the 5 GHz connection is acting up on this router, which was flashed with the first 'official' snapshot after it was available. It is configured as an AP following the 'Dumb AP' guide on the wiki.
Nothing was changed in the OpenWrt config or on further upstream devices before this started.
Symptoms are that any client, connected on AC or AX, has trouble initiating sending and/or receiving data (e.g. loading a new web page). They hang for 5-10 seconds where no data seems to go in or out, after that it does load. It does not (visibly) drop the WiFi connection and reconnect at least. It looks similar to an unresponsive DNS server, but I've ruled that out as wired clients are not affected, and it also happens when trying to access the LuCI interface over the 5 GHz network by IP-address.
I already tried the basic things, like changing channels and switching between 40/80/160 MHz, fully disable IPv6, setting security to WPA2 instead of WPA3/WPA2 mixed. Some of the channels I tried are completely free of any interference from other networks, but that didn't make a difference.
Also, I tried a clean install of the latest (27-02-2024) snapshot, by doing a factory reset -> install latest snapshot -> factory reset again, but the problem remained.
I have yet to try a different location, switch to AC-only, see if 2.4 GHz is affected as well and try a different build than the official snapshot.
Fingers crossed that it is not a hardware problem, as it appeared out of nowhere.
When I find anything interesting while I investigate this further, I will mention it here.
1 Like
If the issue happens again, run dmesg command via SSH to check if there is any unusual error.
1 Like
I installed Openwrt snapshot firmware (official images) and OpenWrt U-Boot.
If I want to upgrade to a newer snapshot or a future official release:
- Is It sufficient to use sysupgrade command as usual?
- should i update also OpenWrt U-Boot?
Thanks in advance.
You can upgrade with the usual methods, but should use the sysupgrade images for devices with the modified U-Boot. (https://mirror-03.infra.openwrt.org/snapshots/targets/mediatek/filogic/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-squashfs-sysupgrade.itb)
No, this is not necessary. The U-Boot is usually a one time upgrade.
Seems there will be global variant also: https://www.mi.com/global/product/xiaomi-router-ax3000t/
Should i enable software and hardware flow offloading and wed on this router?
1 Like