Try to use recovery mode of xiaomi routers and Xiaomi mi wifi repair tool (it’s a tftp tool) + stock official firmware.
Not a bad, but there is only MIMO 2x3:2 and 1gb lan (no 2.5g). You will get speed more than 1200mb (more than with he80) just only between WiFi-6 clients (in theory). As for me, he160 is a marketing here.
1 Like
Thanks for trying. I've tried it, but for some reason, the app just closes by itself, and as this is Chinese and the windows can't show properly, I can't understand what was happening. I just follow a tuto I've found on the internet. Anyway, all those ask for potting in recovery mode which is supposed to blink some orange light and then steady.. but mine, only white light. but I held it for long and tried, but no success.
But, something good came, I could see the router was responding to ping command on 192.168.1.1, I need to fix my IP address because there is no DHCP, I've tried some GUI, SSH, but nothing. Then I ran zenmap on the IP and that was the result.
Starting Nmap 7.94 ( https://nmap.org ) at 2024-04-19 14:15 Hora oficial do Brasil
NSE: Loaded 156 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 14:15
Completed NSE at 14:15, 0.00s elapsed
Initiating NSE at 14:15
Completed NSE at 14:15, 0.00s elapsed
Initiating NSE at 14:15
Completed NSE at 14:15, 0.00s elapsed
Initiating ARP Ping Scan at 14:15
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 14:15, 0.09s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 14:15
Completed Parallel DNS resolution of 1 host. at 14:15, 13.04s elapsed
Initiating SYN Stealth Scan at 14:15
Scanning 192.168.1.1 [1000 ports]
Completed SYN Stealth Scan at 14:16, 23.30s elapsed (1000 total ports)
Initiating Service scan at 14:16
Initiating OS detection (try #1) against 192.168.1.1
NSE: Script scanning 192.168.1.1.
Initiating NSE at 14:16
Completed NSE at 14:16, 5.03s elapsed
Initiating NSE at 14:16
Completed NSE at 14:16, 0.00s elapsed
Initiating NSE at 14:16
Completed NSE at 14:16, 0.00s elapsed
Nmap scan report for 192.168.1.1
Host is up (0.00023s latency).
All 1000 scanned ports on 192.168.1.1 are in ignored states.
Not shown: 1000 filtered tcp ports (no-response)
MAC Address: 42:86:67:A0:88:22 (Unknown)
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: VoIP adapter|general purpose
Running: Avaya embedded, IBM OS/400 V4, Linux 2.6.X|4.X
OS CPE: cpe:/o:ibm:os_400:v4r3 cpe:/o:linux:linux_kernel:2.6.24 cpe:/o:linux:linux_kernel:4.4
OS details: Avaya G350 Media Gateway VoIP adapter, IBM OS/400 V4R3, Linux 2.6.24 (Debian), Linux 4.4
Network Distance: 1 hop
TRACEROUTE
HOP RTT ADDRESS
1 0.23 ms 192.168.1.1
NSE: Script Post-scanning.
Initiating NSE at 14:16
Completed NSE at 14:16, 0.00s elapsed
Initiating NSE at 14:16
Completed NSE at 14:16, 0.00s elapsed
Initiating NSE at 14:16
Completed NSE at 14:16, 0.00s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 45.28 seconds
Raw packets sent: 2019 (90.386KB) | Rcvd: 3 (354B)
What do you think? still have a chance?
it's in the wiki i linked above.
Assume that you have installed OpenWrt with stock layout, with original u-boot:
Connect to router via UART
Select Load Image in the u-boot
Set start address to 0x48000000, then set TFTP parameters to load the initramfs-kernel.bin.
Start the loaded kernel, then perform sysupgrade on OpenWrt.
If you have installed OpenWrt with u-boot mode layout, you can still use above UART recovery procedure, but u-boot will also look for a file called openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb in a tftp server at IP address 192.168.1.254
If you provide that file in a tftp server, it'll be automatically loaded and run, so system can be recovered without using a UART connection.
it's not dead, you made a mess switching from openwrt to x-wrt and back, just go uart and see what's wrong and eventually boot from uboot according to the guide.
May be closed by antivirus, please find video of work this tool in the youtube (may be with other router)
Hey man.. thanks again.
I did try it, but I have no any knowledge about this UART process.. I have no equipment for this. I read somewhere it could be done using a Raspberry PI wich I have, but I couldn't found any detailed instructions how to do it.
If you can point me a place where I can find some information for noobies like me, I would appreciate it.
Thanks.
I've followed this video, after 6:30...
But, as I said, I've followed and clicked the same buttons, but for some reason, the app closes by itself just after I click on the button to start.
I have disabled my antivirus, but I'll try something else to make sure it's not creating the problem.
If you know some other more detailed video, please, give me the link.
Thanks.
Ok.. Finally, I did recover my router. Thanks @Volenski for the crucial help. Thanks all for tips and support.
Let's share what I did. I used the Tiny PXE and have already tried a lot of options I've found on the internet. The solution came with from message @Volenski. All videos and sites on the internet said to configure my LAN adapter to TP 192.168.1.2 or some other on the 192.168.1.X range. But, the only one which really works is 192.168.1.254. This is the IP that the recovery was looking for. After that, the Tiny Pix screen showed me the file it was looking for, so I placed the file there and Voila... seconds later it was alive again. Another important information is if the router is straight on the white light, no need to press reset, just turn it on and it's already on recovery mode.
Thanks all again.
Back to work.
1 Like
well it was already explained in the wiki, and i also copypasted the ip 192.168.1.254 in my previous comment
well good for you glad you fixed it!
Hi I am in need of some help,
I've tried to use the easy method but when it connects for an SSH it has an error and then I cannot connect back to the router.
My router is an rd03 and arrived on 1.047 fw
I am using the Putty SSH method and have SSH, I backed up all of the nand but the guide says now copy these to your PC but doesn't specify how to?
How do you copy from the nand?
Secondly, I have the openwrt file for flashing, but am not sure how to copy it to the /tmp directory. I tried the youtube guide but it cannot find the directory.
Any help much appreciated.
I had the same problem, after every restart Wifi stopped working. See my posts above for the solution!
Hi,
First installation on my new AX3000T (with latest snapshot from April 20, uboot version), everything works fine but old wifi 2.4GHz devices cannot connect. More precisely, I see them trying to connect in logread, but always fail. Setting the AP in N mode doesn't change anything.
If I take back my previous router, a Xiaomi 3G running OpenWrt 23.05.3, with its AP in N mode (802.11b/g/n), all these old devices connect immediately (of course, I checked the other parameters: ssid, key, ecryption...).
Any idea? Can it be the snapshot which is wrong? My config?
Have a look here to flash the firmware with the Easy method.
You can copy the firmware to the /tmp directory using WinSCP.
I have now flashed firmware with easy method,
it rebooted and is solid blue
Putty SSH shows it as openwrt
but I cannot connect to the web interface? 192.168.1.1 does not work
Hello, I have flashed with two routers using Easy Method first Openwrt Xiaomi Mi Router AX3000T snapshot and then OpenWrt U-Boot.
I have now flashed the firmware version OpenWrt SNAPSHOT r25736-d1eb0bec39 / LuCI Master using Attended SysUpgrade and then did not want to update any further, as this version turned out to be particularly stable.
1 Like
did you install luci?
The snapshot version has no Luci interface.
You must first
opkg update
opkg install luci
To do this, you must connect your 1st router via LAN to the WAN port of your 2nd router (Xiaomi Mi Router AX3000T).
However, this is only possible if the 1st router does not have the same IP address as the 2nd router.
Therefore, you must first do this on the Xiaomi Mi Router AX3000T using Putty SSH:
vi /etc/config/network
press i
and change '192.168.1.1' to '192.168.2.1' in option ipaddr
press wq
I also had this version OpenWrt 23.05.3, but had problems and then switched back to Snapshot and it works.
Hi,
No I didn't I just followed the guide in the op using the easy method
What do I do next?
I flashed to stable build from the first repository