Can you tell me how to change the region from CH to EU?
I installed hanwckf Chinese bootloader and use it to flash rd23 ubi image.
I think there are other possibilities. For example, write rd23 FIP backup and then use MI repair tool with rd23 image. I didn't test this option.
Sorry I am from medicine world, flash rd23 ubi image Is stock firmware?
You can find out more here - https://4pda.to/forum/index.php?showtopic=1074874&st=10140#entry134707547
1 Like
Is it normal that the repair tool gets flagged by windows as a virus? Brave browser refused to even download it.
I removed my attempt at putting headers on it. Nothing on Putty with Rx/Tx either way round. Not sure how people get it to work by poking pins through the case.
For many antiviruses, this is normal.
Since the program changes the settings of the computer's network card, they consider it a virus.
Of course, you can do this through some regular TFTP server, but you need to do a lot of things manually and not make a mistake in the same specific name of the firmware file, which you need to rename the stock firmware... There is information in WIKI, but it is much easier with this program.
Thanks. I will have a go later.
Appeared 24.10.1.
Not yet assembled via the site.
As far as I understand, no changes to bad blocks for ForeSee have been added? Will we be restoring bricks again, or am I wrong and everything will already be fixed?
The PR (pull request) by @dimfish to fix the bad blocks issue is still open (https://github.com/openwrt/openwrt/pull/17963). It would need to be first merged into main (snapshot builds) and then backported to 24.10 branch. So, no, the fix for the bad blocks issue will not be included in 24.10.1 stable release.
And to be honest, considering this comment in the PR, it is likely it will be merged only when OpenWrt kernel is upgraded to 6.12 in the main branch (snapshot builds). So after this, the 6.12 kernel patch will need to be backported to 24.10 branch (kernel 6.6) to be included in a future 24.10.x release.
This is disgusting news!(((('. Well...
I hope this will be announced loudly and everywhere, so that we don't have tens or even hundreds of pages asking for help in reviving the router!
And such were the hopes!...
Since it impacts a kernel patch, it is usually slower to be fixed than other issues.
But I agree, a comment should be done in the 24.10.1 release notes that some AX3000T devices with FORESEE flash affected by the bad blocks issue can be bricked by installing OpenWrt. At least this is already crystal clear in the AX3000T Wiki:
Agree that there is a small difference between the fact that if you take this pill, there is a 1% chance that it will not help, or 1% - 100% will die(((.
Somehow it needs to be written so that it is clear that 1% will die.
1 Like
Asus routers had a problem with the compatibility of the bootloader and the code from the 24 branch.
The maintainer said six months ago that he did not want to add an additional patch file for the kernel to the repository, since there were already too many of them.
But after the release of the 24 branch, bricks appeared and users started howling.
Well, having heard this howl, the maintainer still added a new patch for the kernel.
1 Like
I have a classic RD03 from ALI. I wanted to upgrade the firmware but I don't know if I have the uboot version. How do I know? Can I then upgrade to 24.10.1? Should I just use sysupgrade when upgrading?
You need to follow the instructions on the wiki
Login to Luci and check the text next to Model on the main page.
The text Xiaomi Mi Router AX3000T (OpenWrt U-Boot layout) indicates that you're running uboot version.
Unless you previously installed some random custom non-official image, you'll need to check the specifics. Otherwise yes, you only need the 24.10.1 sysupgrade file when upgrading:
Luci -> System -> Backup / Flash Firmware -> Flash image...
Make sure you're downloading correct 24.10.1 version based on your bootloader type (stock or U-Boot).
p.s> keep in mind that the fix for the Foresee NAND issue #17963 is still not present in 24.10.1. So, check your chip, and if it’s Foresee decide whether to take the risk (1%) or not.
Did anyone managed to get an encrypted mesh network (802.11s, WPA3-SAE) running with this device and OpenWrt 24.10?
My stations won't associate. It only works if it's unencrypted.
Works ok.
root@AX3000T_6:~# iwinfo
phy0-mesh0 ESSID: "mesh24"
Access Point: 50:4F:3B:33:
Mode: Mesh Point Channel: 1 (2.412 GHz) HT Mode: HT40
Center Channel 1: 3 2: unknown
Tx-Power: 20 dBm Link Quality: 54/70
Signal: -56 dBm Noise: -91 dBm
Bit Rate: 191.8 MBit/s
Encryption: WPA3 SAE (CCMP)
Type: nl80211 HW Mode(s): 802.11ax/b/g/n
Hardware: embedded [MediaTek MT7981]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
phy1-mesh0 ESSID: "mesh36"
Access Point: 50:4F:3B:33
Mode: Mesh Point Channel: 36 (5.180 GHz) HT Mode: VHT80
Center Channel 1: 42 2: unknown
Tx-Power: 23 dBm Link Quality: 48/70
Signal: -61 dBm Noise: -92 dBm
Bit Rate: 274.6 MBit/s
Encryption: WPA3 SAE (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [MediaTek MT7981]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
1 Like
Build with new patch for Foresee + Bad Block is here:
5 Likes
In the previous version of the bootloader, the version and build date (17.02.2025) were written in colored letters. I don't see that in this bootloader, but it was convenient to know what kind of bootloader was installed on the router. Also, if I'm not mistaken, it was written somewhere that this bootloader prevents the entire NAND Foresee from being filled with bad blocks. Does this version also have a similar function?
I got a router with a release date last month, it has NAND ESMT installed, I have already tried the bootloader on this one, so as not to suffer with UART).