Informative explanation about why using a backup of partitions from another RD03/RD23 router isn't a good idea:
https://www.youtube.com/watch?v=WvVIT3gXZak this work for me download firmware for ax3000at from https://cdn.cnbj1.fds.api.mi-img.com/xiaoqiang/rom/rd03/miwifi_rd03_firmware_14680_1.0.64.bin chine version
What was the original shipped firmware version?
1.0.90 reléase date: 2025/02
OK, you cannot downgrade from that, if the ssh exploit does not work update just one version at a time.
yes, i did. Thanks
Fix for the Foresee
NAND bug has finally been accepted and is already available in the official Snapshot builds.
Backporting to the 24.10 branch is awaiting to be accepted into the official stable 24.10.x release:
Updated:
PR #19297 has been accepted as well, so the fix should be available in the next stable 24.10.3 release.
But the fix for the U-Boot bootloader likely won't be included...
Less than half a year has passed! Lightning McQueen))).
With your involvement, everything could have happened sooner.
Merged.
We need testers here.
I have a forsee nand ax3000t running uboot mod / snapshot uboot.
Is there a build I can test? Do I just need to flash the BL2 and FIP?
Here is my build of that PR. Flash FIP is enough. Need to test tftp recovery process and ensure that we can write and run OpenWrt.
https://mega.nz/folder/ks4R2S4D#g1l_wH-nBOMONrDqOkeEvQ/folder/U1hXELQR
So to confirm
Flashing fip from your file (adjusting name)
mtd write /tmp/openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-bl31-uboot.fip FIP
Then for testing tftp? I could test flashing the latest stable build using the below instructions? Or do I need to do it from uart?
Yes.
Yes. You can use this guide (don't pay attention that it's for another device) https://openwrt.org/toh/netis/nx31#openwrt_u-boot
Then just flash sysupgrade image (the better is latest SNAPSHOT with FORESEE fix).
UART is necessary only if something will go wrong.
How does uboot determine what filename to look for?
Snapshot
openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb
24.10.2
openwrt-24.10.2-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb
U-Boot is always searching for openwrt-mediatek-filogic-xiaomi_mi-router-ax3000t-ubootmod-initramfs-recovery.itb
on tftp server.
It has long been tested on assemblies collected by enthusiasts, as soon as PR appears, they compile assemblies based on them and post them. Almost 99% of the Russian-speaking Internet sits on these assemblies and does not know any problems, but the assembly is not official - this is not an official assembly. What is the Snapshot branch for? Is it not to check exactly what really needs to be checked and if OK, then immediately implement it into the stable branch?
Probably not? (((.
And you also need to check not only the boot via TFTP, but also the boot from the recovery partition, the one that is ~10 MB.
So I flashed the fip, then booted openwrt using the tftp recovery method, then flashed the latest snapshot via ssh. All seemed to go OK.
I have restored the device back to its previous image/settings now. I guess there's no harm in running the new fip?
That's ok. Thanks for the test!