too bad. Get a new one?
Why should I? I still want to fix this one.
If you want to rewrite the nand flash, not easy. Maybe cost you much + your time.
1 Like
Perhaps you could get it back up and running using the mtk_uartboot tool that's been used to recover a lot of dead Linksys E8450 (see the other thread here on the forum): https://github.com/981213/mtk_uartboot
1 Like
Hello
Just flashed up my 2nd Chinese AX3000T.
I got OpenWRT & U-Boot installed successfully, but...
opkg is showing signature check fails. I can't intall luci properly.
> root@OpenWrt:~# opkg update
> Downloading https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/packages/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_core
> Downloading https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/packages/Packages.sig
> Signature check passed.
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_base
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/base/Packages.sig
> Signature check failed.
> Remove wrong Signature file.
> Downloading https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/kmods/6.6.34-1-87871967b2c86131796a36f4d5034b27/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_kmods
> Downloading https://downloads.openwrt.org/snapshots/targets/mediatek/filogic/kmods/6.6.34-1-87871967b2c86131796a36f4d5034b27/Packages.sig
> Signature check passed.
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_luci
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/luci/Packages.sig
> Signature check passed.
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_packages
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/packages/Packages.sig
> Signature check failed.
> Remove wrong Signature file.
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_routing
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/routing/Packages.sig
> Signature check passed.
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/Packages.gz
> Updated list of available packages in /var/opkg-lists/openwrt_telephony
> Downloading https://downloads.openwrt.org/snapshots/packages/aarch64_cortex-a53/telephony/Packages.sig
> Signature check failed.
> Remove wrong Signature file.
Never mind.. my own stupidity.
Didn't set the time properly 1st
2 Likes
I came across this yesterday during my Google searches for a solution, but I was hesitant because it is not for the same model (although it says it is compatible with the same chip). If no one answered me, I would ask if anyone would know it. Has anyone used this program and had success in recovering a Xiaomi AX3000T?
The README states
It's been tested on MT7622/MT7629 and MT798x.
which means that it should work fine on the AX3000T as it has the MT7981.
1 Like
OK Have tried everything now, still the same.
Only thing I can think of is to return to stock including stock bootloader and checking (Which I should of done before installing Openwrt)
I think that I will leave as is and use it as a WiFi extender.
Many thanks for your sugestions and help.
Tested my AX3000T, the speed: (my main router is Netgear R7800, not wifi6)
WiFi 5G wwan to main router, all Lan-2/3/4 to PC, 500Mbps / 420Mbps for Download / Upload.
wan port(Lan-1) to main, all Lan-2/3/4 to PC, I got the same 930 / 900 results.
No difference on AX3000T Lan-2/3/4.
Hi All,
As a long time OpenWRT user I ordered the RD03 version of the AX3000T. Unfortunately it seems broken on arrival. The device keeps blinking red.
I tried TFTP recovery which uploaded file, but same result after boot. Blinking red. Do you one of you have fix I overlooked? Else I am returning it. Seems they either send me someone elses mess or a device with broken flash.
I used and now I think the router is dead. The tool returned an error and now is not showing any messages during boot thru UART. 
mtk_uartboot - 0.1.1
Using serial port: /dev/ttyUSB0
Handshake...
hw code: 0x7981
hw sub code: 0x8a00
hw ver: 0xca00
sw ver: 0x1
Baud rate set to 460800
sending payload to 0x201000...
thread 'main' panicked at src/bootrom.rs:106:13:
send_da cmd status: 7442
Judging from the source code and your logs, the router does respond to some of the tool's commands, but throws an error when the tool tries to send the payload to the specified load address. Maybe the payload is incorrect somehow? Which payload are you trying to use?
It looks like someone else did get the tool to work before, maybe something in that thread would be of help: AX3000T Bricked
1 Like
Now the router doesn't return any message during boot. I don't think any software based solution would work now.
As payload I used the BL2.bin file I backup before starting to install OpenWRT.
The thread you shared, I couldn't find there anything that would help me. Thanks anyway.
I'm trying to identify the NANDs and a how I could update the firmware directly with a friend that did this kind of thing before (but not with this router model).
If anyone has some other ideas, please share.
Maybe you find a jtag port where the router gets programmed in the factory?
I'm on @Ser9ei build 23.05.3 r23809-234f1a2efa
and from time to time (no particular pattern) one of the lan ports, the one that is connected to my Proxmox server, starts limiting bandwidth to 100mbps.
If I run:
ip link set lan4 down
ip link set lan4 up
it goes back on working at 1000mbps.
Is anyone else experiencing the same issue?
Might have something to do with this similar issue:
Hello, I solved this problem by putting port 1000 on all devices in openwrt. Network > Interface > Devices > Wan (Lan2, Lan,3..) > TX queue length > 1000
1 Like
Hi folks. After several attempts, during many days, I was able to put the uboot recovery menu to appear while boot. So now I don't need to use UART method send upload a payload and FIP file to initialize the router.
One of the problems I was having and that took some time to identify was with the cables from the USB to TX/RX/GND holes in the AX3000T, I changed the cables and from then I was able to start using the payload e FIP file every time I needed. Before discover this, I needed 20-30 tries to obtain a succesful transmission. This is why I though the router was dead. But now the router starts by itself, although without Luci web interface and I think there is still some issues. Any suggestions to what I should do now?
which OpenWRT build should I use? There's some with Luci web interface working?
I still can access the router using UART, but ssh is now working.
Any output during boot sequence or a specific boot option that I can run , save and share here to help understand the state of the router?
Thanks!
try opkg update && opkg install luci to install luci.
Or try to flash my build, which is luci enabled.