Losing internet access sounds like a configuration problem, an ISP doing things or a combination of both...
I only had trouble with my AX3000T because of overloading the ram with blocklists. Since reducing the blocklists it has been rock solid, internet-connection-wise.
Open a topic with your problem and all the details of your setup.
updated to OpenWrt 23.05.5 (supports the W25N01KV spi-nand driver).
I don't have a router with 'W25N01KV' to test, but it run on ESMT chip;)
hey Alexq, I tried this MiWifi Repair Tool procedure to get back to stock but although the procedure finished, after reboot it goes back to original state. Did I do something wrong?
I followed this youtube video:
Try one more time via MiWifi Repair Tool (I assume you didn't install a custom OpenWrt U-boot bootloader and have the ootb Xiaomi bootloader on your rd23).
If not, you can try to proceed with the "*** U-Boot Boot Menu ***" and select point 8 (8. Load image) and follow the Debricking instructions from the Wiki.
Also, you can try installing OpenWrt again via the UART method (just start from step 5).
update:
Also, make sure that the downloaded OpenWrt files contain the same SHA256 checksum as specified on the download page (ust to ensure that the downloaded file is not corrupted).
Tried MiWifi several times, same outcome.
Also, I tried this debricking and the result is the log I posted with kernel uncompressing issue.
A Chinese router with firmware 1.0.84 arrived. Today I have time to try the firmware. I have access to UART, I know how to use it, but it is at my friend's place for now, I can take it tomorrow. So if you don't want to wait until tomorrow, offer those that have less chance of bricking the router)))
root@XiaoQiang:~# dmesg | grep NAND
[ 0.720391] spi-nand spi0.0: Winbond SPI NAND was found.
root@XiaoQiang:~#
MTD partitions:
0 > addr: 0x00000000 size: 0x08000000 ro:0 name: "spi0.0"
1 > addr: 0x00000000 size: 0x00100000 ro:0 name: "BL2"
2 > addr: 0x00100000 size: 0x00040000 ro:0 name: "Nvram"
3 > addr: 0x00140000 size: 0x00040000 ro:0 name: "Bdata"
4 > addr: 0x00180000 size: 0x00200000 ro:0 name: "Factory"
5 > addr: 0x00380000 size: 0x00200000 ro:0 name: "FIP"
6 > addr: 0x00580000 size: 0x00040000 ro:0 name: "crash"
7 > addr: 0x005C0000 size: 0x00040000 ro:0 name: "crash_log"
8 > addr: 0x00600000 size: 0x02200000 ro:0 name: "ubi"
9 > addr: 0x02800000 size: 0x02200000 ro:0 name: "ubi1"
10 > addr: 0x04A00000 size: 0x02000000 ro:0 name: "overlay"
11 > addr: 0x06A00000 size: 0x00C00000 ro:0 name: "data"
12 > addr: 0x07600000 size: 0x00040000 ro:0 name: "KF"
Download file: "/tmp/kcmdline.log" ....
Kernel command line:
console=ttyS0,115200n1 loglevel=8 swiotlb=512 rootfstype=squashfs firmware=0 mtd=ubi
RootFS info:
num = 0
mtd_num = None
mtd_dev = "None"
partition = "None"
Base info:
Linux version: None
DISTRIB_TARGET = mediatek/mt7981
DISTRIB_ARCH = aarch64_cortex-a53
CPU arch: arm64
CPU name: mt7981
Version info:
UBoot: None
OpenWrt: unknown
Firmware: 1.0.84
Channel: release
BuildTime: Wed, 29 May 2024 03:44:13 +0000
Hardware: RD03
UBoot(2): 2022.04-rc1
Download file: "/tmp/nvram.txt" ....
NVRam params:
flag_boot_rootfs=0
flag_boot_success=1
flag_boot_type=2
flag_last_success=0
flag_ota_reboot=0
flag_try_sys1_failed=0
flag_try_sys2_failed=0
ipaddr=192.168.10.1
serverip=192.168.10.100
Bootloader info:
Download file: "/tmp/bl_BL2.bin" ....
addr: 0x00000000 (size: 0x00100000)
image size: 80 bytes
type: None
Download file: "/tmp/bl_FIP.bin" ....
addr: 0x00380000 (size: 0x00200000)
image size: 26972 bytes
type: None
ENV info:
Download file: "/tmp/env_Nvram.bin" ....
addr: 0x00100000 (size: 0x00040000)
CRC32: 0x82898A0C
max size: 0x10000
Download file: "/tmp/env_Bdata.bin" ....
addr: 0x00140000 (size: 0x00040000)
CRC32: 0x4116A185
max size: 0x10000
Download file: "/tmp/env_BL2.bin" ....
addr: 0x00060000 (size: 0x000A0000) breed
This
It doesn't work but can be repaired with MIWIFIRepairTool.x86.
Hi,
23.05.5 official is compatible with W25N01KV nand?
No.
Hi
Does the ESMT NAND chip support 23.05.5?
yes, it does
ESMT NAND == supported by 23.05.5
Winbond NAND == supported by Snapshot only
AN8855 switch == not supported neither 23.05.5 nor Snapshot (at least for now).
There are lots of these topics with the same problem, and no proper solutions have been found. Some of them got the problem solved by updating to some new version, others misconfiguration, and others had no solution.
As you said, your version is working very well.. but then I ask: how many VLANs do you have? How many Firewall rules? Are you working with static Leases? Are you using more than one router and using the WLAN roaming?
This is my scenario here, and the worst thing, sometimes I have this loss 5 times a day, sometimes two in less than 30 minutes. Sometimes I didn't experience this issue for weeks.
That's why I just want to keep a more tested version like the stable one.
What do you think? Is it Worth it to open a new topic even before changing?
What about the international version? Is it still supported? * model RD23: International (Global) version.
So far, there hasn't been any evidence from anyone that RD23 received a Winbond NAND chip or an AN8855 switch... But this could happen someday (so, please verify the NAND chip before flashing) 
So, until the RD23 (Global version) comes with an EMST NAND chip, it's supported by both Stable 23.05.5 and Snapshot.
I can't say about the rest, but the Winbond chip is not supported.
You mean if the USB is avaiable but withour port?
I didn't see any USB in bootlog...
I mean if the USB tracks from the SoC are mapped and accesible on the board. kernel will need to be patched for obvious reason.
do we know why a linux kernel change needs to be implemented before the winbond nand chips are supported? what is so different about these nand chips? I would expect there to be a standard manufacturers follow when manufacturing nand chips so these issues don't happen when oems change part suppliers?
We know, different partition tables, which is normal, just these partitions need to be added to the firmware so that it knows at what addresses to flash itself correctly, so that the bootloader can load it correctly. This has actually already been done in SNAPSHOT. All that remains is to add a driver for the new network switch, otherwise the router turns into a regular switch))).
So what's the problem? I read not long ago that when assembling the firmware you need to add only one parameter and it was written which one. But unfortunately I'm not a programmer.
But I could check this with ready-made firmware))) Which is what I did. And none of the proposed firmware works properly. Which is what I wrote a little higher.
Alex, my build support (implemented with patch for) Winbond spi-nand, but not support AN8855 switch.
According to https://openwrt.org/inbox/toh/xiaomi/ax3000t :
1.0.84 (CN) - (
AN8855hardware)