OpenWrt support for Xiaomi AX3000T

t1000 · 2024-09-08T15:24:13.807Z

it work for PPPoE ?

mamalux · 2024-09-08T15:25:35.292Z

Flash Nand With FlashDump Of Enother RD23, Fixed

alexq · 2024-09-08T15:31:55.214Z

t1000:

how install "opkg update && opkg install luci" then WAN not configured and router has no internet?

Connect the WAN port of your RD23 to the LAN port of your old router, which is currently connected to the internet. This will give the RD23 internet access and enable you to install Luci

alexq · 2024-09-08T15:58:41.900Z

or, if you're certain that your RD23 does not have a Winbond NAND flash chip, you can install the sysupgrade file from the Stable release (23.05.4) where Luci is present by default.

t1000 · 2024-09-08T16:14:21.333Z

yes, it work! my router have ESMT chip.

t1000 · 2024-09-08T16:16:09.955Z

t1000:

opkg update && opkg install luci

then try "opkg update && opkg install luci" - router again crash down bootloop(( had to reinstall again

cacodemon79 · 2024-09-08T16:21:13.630Z

This guide:
https://forum.openwrt.org/t/openwrt-support-for-xiaomi-ax3000t/180490/420
works whatever RD23 factory firmware version is installed (known till now)?

I would like to buy another AX3000T but I fear that if I chose RD03 I will receive firmware version 1.0.84 or newer. This is why I am thinking to the global version ...

alexq · 2024-09-08T16:51:33.856Z

cacodemon79:

works whatever RD23 factory firmware version is installed

There is no evidence of any stock firmware version other than 1.0.31 for the RD23. So, the current UART method should work until RD23 transitions to new hardware and updated firmware.
After that, installing OpenWrt will only be possible once support is added for the new hardware in the OpenWrt image, similar to the RD03 with firmware version 1.0.84+.

warrenfrost · 2024-09-08T19:42:00.125Z

I also have this exact same issue. No WiFi and same error in boot log

[ 7.239459] mt798x-wmac 18000000.wifi: Direct firmware load for mediatek/mt7981_eeprom_mt7976_dbdc.bin failed with error -2

This file is missing in my /lib/firmware/mediatek directory

Where should it come from? Is it a proprietary firmware file that has to be copied from somewhere? Can someone provide it as I don't seen to be able to find it anywhere.

Thanks

romanovj · 2024-09-08T20:31:25.534Z

You have erased the EEPROM in the factory partition. Restore it. You don't need default eeprom (mt7981_eeprom_mt7976_dbdc.bin).

alexq · 2024-09-08T20:49:26.479Z

t1000:

"fw_setenv flag_last_success 0" helped to avoid bootloop

@t1000 / @nemoforum / or anyone using RD23 who had to apply the command "fw_setenv flag_last_success 0", could you guys please run the cat /proc/cmdline command and verify the output log? Do you have returned "firmware=1"?

I've used "fw_setenv flag_last_success 1" in my RD23, and (because?) the cat /proc/cmdline returns me "firmware=0".

my full output log

root@OpenWrt:~# cat /proc/cmdline
console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=0 mtd=ubi uart_en=1

t1000 · 2024-09-09T02:52:59.242Z

From many installation attempts, I was given the message firmware=0 and firmware=1 . I don't know how it happened, almost by chance. Now the router works stably and it is dangerous to change anything)

warrenfrost · 2024-09-09T06:16:16.181Z

Hi, thanks for the reply.

Do you mean restore the backup of the factory partition I took to mtd3?

root@OpenWrt:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "BL2"
mtd1: 00040000 00020000 "Nvram"
mtd2: 00040000 00020000 "Bdata"
mtd3: 00200000 00020000 "Factory"
mtd4: 00200000 00020000 "FIP"
mtd5: 00040000 00020000 "crash"
mtd6: 00040000 00020000 "crash_log"
mtd7: 00040000 00020000 "KF"
mtd8: 02200000 00020000 "ubi_kernel"
mtd9: 04e00000 00020000 "ubi"

t1000 · 2024-09-09T14:44:16.141Z

root@OpenWrt:~# cat /proc/cmdline
console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=0 mtd=ubi uart_en=1

yesterday everything worked fine, but today I got bootloop again. To solve the problem, I selected "Upgrade software" in U-boot menu and transferred the file "openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb", then loaded 'openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-initramfs-factory.ubi' and then 'openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-squashfs-sysupgrade.bin'...applied fw_setenv flag_last_success 0 and it worked. But then it may random break again...why is that?
after installing applications the system can also break, this is not normal

remittor · 2024-09-09T14:57:12.287Z

t1000:

after installing applications the system can also break, this is not normal

Probably, you need to do something similar every time the system boots successfully:

github.com

openwrt/openwrt/blob/5eb8b7793dfdf251f6bf75ae2b1124504844c339/target/linux/ramips/mt76x8/base-files/etc/init.d/bootcount#L11-L14


      
          	xiaomi,mi-router-4c|\
          	xiaomi,miwifi-nano)
          		fw_setenv flag_boot_success 1
          		;;

github.com/openwrt/openwrt

ipq806x: Add support for Xiaomi Mi Router HD (R3D)

Commit by

remittor - ipq806x: Add support for Xiaomi Mi Router HD (R3D)

openwrt:main ← remittor-pr:r3d

Xiaomi R3D is a 2.4/5 GHz band 11ac router, based on IPQ8064. Specification: * …SoC: Qualcomm IPQ8064 * RAM: 512MB DDR3 * STOR: 256MB NAND (Macronix MX30UF2G18AC-TI) * ETH: 1x WAN 10/100/1000, 3x LAN 10/100/1000 * WiFi: Qualcomm QCA9984 (5GHz, 4T4R, n/ac) * WiFi: Qualcomm QCA9980 (2.4GHz, 4T4R, b/g/n) * USB: 1x 3.0 * SATA: 1x SATA 3.1 (only for internal HDD 3.5") * BTN: Power, Reset * LEDS: Status(Green/Blue/Red) * UART: present as 4-pads on the PCB (3.3V, 115200-8-N-1) MAC addresses as verified by stock firmware: | Interface | MAC | ART | Format | |-------------+-------------------+---------+--------| | WAN (label) | xx:xx:xx:xx:xx:B2 | 0x0 | binary | | LAN | xx:xx:xx:xx:xx:B3 | 0x6 | binary | | WiFi 2g | xx:xx:xx:xx:xx:B4 | 0x1006 | binary | | WiFi 5g | xx:xx:xx:xx:xx:B5 | 0x5006 | binary | Partition layout and boot: Stock Xiaomi firmware has the MTD split into (among others) - kernel0 (@0x0800000) - kernel1 (@0x0c00000) - rootfs0 (@0x1000000) - rootfs1 (@0x3800000) - overlay (@0x6000000) Xiaomi uboot expects to find kernels at 0x800000 & 0xc00000 referred to as system 1 & system 2 respectively. a kernel is considered suitable for handing control over if its linux magic number exists & uImage CRC are correct. If either of those conditions fail, a matching sys'n'_fail flag is set in uboot env & a restart performed in the hope that the alternate kernel is okay. If neither kernel checksums ok and both are marked failed, system 2 is booted anyway. Note uboot's tftp flash install writes the transferred image to both kernel partitions. Methods for getting SSH access: 1) https://github.com/acecilia/OpenWRTInvasion 2) https://github.com/openwrt-xiaomi/xmir-patcher Installation: The installation file for OpenWRT is a *squashfs-factory.bin file that contains the kernel and a ubi partition. This is flashed as follows: nvram flag_boot_success=1 nvram flag_boot_rootfs=1 nvram flag_last_success=1 nvram flag_try_sys1_failed=0 nvram flag_try_sys2_failed=0 nvram commit dd if=factory.bin bs=1M count=4 | mtd write - kernel0 dd if=factory.bin bs=1M count=4 | mtd write - kernel1 dd if=factory.bin bs=1M skip=4 | mtd write - rootfs0 reboot Reverting to stock: Download facinstall.ipk from link https://github.com/openwrt-xiaomi/facinstall/releases/latest and install its. Install miwifi_r3d_firmware_XXXXX.bin image via LuCI interface. Signed-off-by: Oleg S <remittor@gmail.com>

After such a fix, the changes that the bootloader makes in the nvram parameters section will not have bad consequences.

alexq · 2024-09-09T15:13:02.374Z

t1000:

yesterday everything worked fine, but today I got bootloop again.

Could you please run the fw_printenv command and check whether the values in the flags flag_try_sys1_failed and flag_try_sys2_failed are not changing (remains the same) after 1-2 router reboots?

Also, please share the output log of the fw_printenv command (mask MAC addresses and other sensitive info before sharing).

I completely agree with @remittor that some data in your flags is being changed by Xiaomi OOTB bootloader. To ensure a permanent fix (I hope), you can edit the /etc/rc.local file and include all the mandatory flags, so correct values will be enforced after every router reboot avoiding bootloop:

fw_setenv boot_wait on
fw_setenv uart_en 1
fw_setenv ssh_en 1
fw_setenv boot_fw1 "run boot_rd_img;bootm"
fw_setenv flag_boot_rootfs 0
fw_setenv flag_last_success 1 // or 0 in you case
fw_setenv flag_boot_success 1
fw_setenv flag_try_sys1_failed 0

alexq · 2024-09-09T16:34:32.819Z

@t1000 , also read this:

OpenWrt support for Xiaomi AX3000T - #452 by alexq

It would be quite interesting to determine which exactly nvram flags are modified by the standard Xiaomi bootloader in your case.

Ditti4:

It might be worth it to adjust the platform.sh accordingly, at least for the RD23. I'll try to get my hands on one and see what I can do.

maybe someday these adjustments will be added into the code, so that it won’t need to be added manually in /etc/rc.local file.

mrrdmr · 2024-09-10T09:58:44.659Z

If someone interested I've built hanwckf's
immortalwrt with Airoha AN8855 driver , but can't test it.

lemur1111 · 2024-09-10T15:48:57.383Z

Screenshot_10-9-2024_184455_192.168.1.11573×993 100 KB

RD23. Rebooted manually more than 6 times.
cat /proc/cmdline console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=0 mtd =ubi uart_en=1

Damian96 · 2024-09-10T16:16:19.098Z

Which file should I use to test it?