Thanks so I will be able to access the Luci interface on 192.168.1.1?
If you had luci before yep. It will reset all you setting, but will leave openwrt. If you do not know the currnent IP. Connect it via lan to other router, see what's the IP and you can access luci.
1 Like
Thanks I didn't think of that. I will try tomorrow and see what happens.....
Not been a good day so far
1 Like
If you are still on the original bootloader, these are the correct instructions.
It is unlikely you flashed the openwrt bootloader unless you had working openwrt before.
Is my English that bad? I had OpenWrt U-BOOT installed on this router. I was flashing a new AX6000 router and simultaneously updating the build for AX3000t and by mistake flashed the firmware from AX6000 instead of the required one. The question is about the functionality of the recovery mode in the custom bootloader U-BOOT AX3000t.
Can you ping 192.168.1.1? If yes, you can probably recover with tftpd. I did just a few days ago with 2 ax3000t router (one on openwrt u-boot and one on stock).
No, it doesn't ping, DHCP doesn't work, if you assign a static IP address to the computer’s network card, it also doesn't ping.
Then you need serial connection to see where it is failing
You may have overwritten the bootloader or uboot.
Do you have backups of all the factory partitions? As the calibration data will almost certainly be written over
I have 3 recommended partitions for recovery. I have a specific question! Does the built-in recovery work in the custom bootloader openWrt?!!! For AX6000 there was a problem and it did not work, because there was a bug in it!!! Is there an answer to a specific question!!! Or are we going to waste time and offer something that fell from the sky and we will try to portray it in the current situation?
I wrote a question to the developers, does it work or not?!!! It was transferred to the use of firmware. Is this a mockery?
For what it's worth, for some odd reason my initial flash of the firmware compatible with the modified bootloader failed after successfully flashing the modified bootloader. I was then able to successfully recover this router using the TFTP recovery method as outlined in the wiki (assigned a static IP address to the computer, made the correct file (using the correct name) available on the TFTP server, connected the two, then started the router). Took a couple of seconds, then the LED changed color, indicating that the firmware was booting.
So yes, TFTP recovery worked for me on the modified bootloader (if that is the recovery you were referring to).
Tftp recovery works fine. But not if you’ve wiped out the boot loader or uboot flashing firmware from a completely different device.
Pull your head in.
IP Computer 192.168.31.100
Mask 255.255.255.0
Name firmware C0A81F02.img
?????
Unplug the power, press and hold the reset button, plug the power back while still holding the button.
TFTP instructions for the stock layout
Just flashed your patched version on a RD03 with Winbond chip, it works fine for now.
You mentioned you flashed the modified bootloader, or did I read that wrong? If so, checkout the Debricking section of the wiki article: https://openwrt.org/inbox/toh/xiaomi/ax3000t#debricking
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.
2 Likes
Thank you! I'll try again, maybe the moon phase was just wrong the first time))
Sorry, I hadn't seen your original post! I'm unfortunately not sure anymore which of the LAN ports I ended up using - I may have even tried them all. 
Keep in mind that the TFTP recovery doesn't flash the image, it only boots it to RAM. You still need to manually flash the firmware afterwards.
Yes, thank you! I know that. At one time, when snapshots on the AX6000 were coming with an error and were not updated via LUCI, I updated it like this when necessary. Load the firmware image into memory, then flash the firmware from under it into flash memory.
Thank you for confirming the functionality of the recovery and not telling the basics of connecting the router to a power outlet)))
1 Like
Hi, I have a problem with OpenWrt AX3000T. I installed OpenWrt u-boot , but I’m stuck in initramfs mode. I’m trying to do a firmware upgrade via the Web interface (squashfs-sysupgrade), but it doesn’t help. I also tried through SSH, but it shows "fail." I attempted to upload the sysupgrade file to tmp using WinSCP and install it via SSH, but I got an error as well.
I’m left with TFTP, but I can’t enable recovery mode. The router normally powers on after about 15 seconds, with quick flashing, slower flashing, and then a blue light. When I press the reset button and plug in the power, the blue light comes on after 3 seconds. At that point, the Firmware update screen appears at 192.168.1.1, but it doesn’t accept anything, just like LuCI.
You got the upgrade screen, that means you flashed a customer bootloader, not openwrt bootloader.
Please use the customer openwrt image code which is matched your bootloader.
What is the ssh password?
I ran the bash script cited in the openwrt page to get ssh access but then it exits and when I try to ssh into it it's asking for a password and there's none on the website. I tried "root" and "admin" but it doesn't work