Check functionality, system and kernel log. If no errors and everything works as before you are ok 
1 Like
Yep, seems to be fine. Wifi and all works perfectly. Lucky me
To be fair, I do also tend to not keep setting while upgrading and setup from scratch, to be sure that I check all the new features.
However, it should technically work. Are you also using the sysupgrade image from the default link (like I've added it), or you're modifying the image?
If you make modifications to the image, it's somewhat more likely that you won't be able to keep the same configuration
Sorry for the long delay. Just followed your instructions, and I'm now finally running OpenWrt 23.05.5 r24106-10cc5fcd00 / LuCI openwrt-23.05 branch git-24.264.56413-c7a3562 version.
All went well, I just forgot that the WiFi wouldn't come up since it is a factory image, took me 2 minutes to plug an ethernet cable, restore the config backup and its up and running. Thank you.
Good info , run fw_setenv boot_fw1 'run boot_rd_img;bootm' can prevent router brick for me now.
1 Like
Awesome! Thank you for the reply and glad to hear that it's useful for fixing the boot issue
This should be added to the openwrt page for the AX6S, my router also bricked after several reboots and thank god after days i found someone post on reddit that pointed here on your findings.
The steps i did to debrick my AX6S production date 04.2024.
-
connected USB to TTL adapter directly on the motheboard
-
opened putty serial connection window and chose to boot from the first slot. The router booted in Openwrt currently running 23.05.5 r24106
-
i connected through ssh and executed
fw_printenv | grep -e ^flag -e ^booti saw that thetry_sys1_failedwas stuck at 6 -
i executed this three commands
fw_setenv boot_fw1 'run boot_rd_img;bootm',
fw_setenv flag_try_sys1_failed 0
fw_setenv flag_try_sys2_failed 0 -
finally i edited the file
/etc/rc.localand added two lines
fw_setenv flag_try_sys1_failed 0
fw_setenv flag_try_sys2_failed 0
Everything working fine now and the try_sys values stay 0 after every reboot.
Thanks @xabolcs
4 Likes
I'm using the OpenWrt 23.05.5 version on my OpenWrt device. I tried to upgrade to the latest snapshot version, but I noticed that the sysupgrade file for the latest snapshot version is in .itb format instead of .bin. When I attempted the upgrade with this file, I encountered the warning shown in the screenshot below. How can I resolve this issue?
I didn't want to directly proceed with a force upgrade because I am concerned that changes to the partition layout might cause issues if I need to revert or perform future upgrades. How can I address this situation safely?
The new snapshot images use Linux kernel 6.1 and they seem to be too big to fit on the existing partition of the Xiaomi AX3200.
You can expand the partition manually and upgrade at your own risk. Here is more info about it: https://github.com/openwrt/openwrt/pull/14768
Please note that you'll also need to make changes again if you want to install back the official OpenWrt 23.05.5 version after you expand the partition.
1 Like
Hi, I have a Xiaomi AX3200 RB01 router with a dead U-boot. How do I restore the factory firmware through the programmer? If I fill dump_AX6S_1.0.19_data_512-16.bin with the programmer, how will the router react? Thank you.
Not sure if that is the correct file or workaround. You can try using the guide on its Table of Hardware page to restore Xiaomi AX3200 to factory firmware:
https://openwrt.org/toh/xiaomi/ax3200#debricking
Hi, this method assumes that u-boot partition is not damaged.
I have u-boot partition is damaged.
I did not find a dump on RB01, only on RB03.I read the flash in the router by the programmer, made an image. Many tapes coincide with RB03. I'm thinking of writing down the entire AX6S_1.0.19_data, or can only the editor insert U-boot ?
Hey!
I have the issue, that the router bricks itself after several restarts. I already did 2 debricks using Windows. But I want to do it with Linux now because I mainly use this (though I'm no expert at all).
I can not run the command to start the tftp server successfully. It throws me an error which I can not solve myself. Did not find any hint online. Tried on two PC with different OS and same result.
dnsmasq: cannot open or create lease file /var/lib/dnsmasq/dnsmasq.leases: Keine Berechtigung (no permission)
At first there was no file. I created one then. I changed ownership and rights to dnsmasq:dnsmasq but that does not help. Even changed ownership and rights of the containing folder with same result. I don't get it. What's the f..in issue? :-/
Mainly trying on Nobara (Fedora based) 40. Other PC has SolusOS 4.5.
Did you use these commands? if you don't apply them after 5 restarts it brick.
1 Like
Not yet. Did just read about it here. Should be mentioned in the docs. But that is not the actual problem I need help.
Trying on Arch (Endeavour) now.
Without sudo I get same result. With sudo I get unknown interface.
EDIT:
Getting further now on Arch. dnssec starts but the file does not get copied over. Not getting further than
dnsmasq-tftp: TFTP root is /tmp/debrick
No errors. Only difference I see is that my "compile options" has "nftset" instead of "no-nftset".
EDIT 2:
Got it! Needed to stop the firewall systemctl stop firewalld.
What a journey...
So if anyone stumbles over this: 1. Use Arch 2. Disable firewall
You could try booting your device through serial with the already linked mtk_uartboot.
See my earlier comment here, in this topic!
Hi. I connected the AX3200 router through the UART. Tried the device CP2102 and CH341-USB. RT-TX, GND. the same result. Turning on the power outputs the following in putty. The following photo appears.
What do these lines say?
I created a BAT file and ran it
mtk_uartboot -s COM3 --payload openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-preloader.bin --fip openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip && putty.exe -serial COM3 -sercfg 115200,8,n,1,N
and
mtk_uartboot -s COM3 -p bl2-mt7622-1ddr-ram.bin -a -f openwrt-23.05.2-mediatek-mt7622-linksys_e8450-ubi-bl31-uboot.fip -serial COM3 -sercfg 115200,8,n,1,N
Stops at Handshake...
Does not respond to power connection.
What could be the problem?