2440

TFTP/MiWiFi repair tool fail in my many attemp. "not all case will success" that why we should warn people in wiki.

2441

The key here is "my". It's based on a single person's experience. There could be multiple reasons for your failure. We should warn users about general issues, not the experiences of just 1-2 people.

1 Like
2442

sound like you don't care, if new user brick there device. to prevent others brick there device one case is enough.

2443

I think that 1 case is enough to warn the users in this thread, but not in the Wiki.

Let's wait for other users' opinions, as I still believe that the statement claiming 1.0.31 RD23 requires UART only for debricking is a hasty and even harmful information to be used in the Wiki at the moment.
@Ser9ei , @dimfish, @remittor, @Lexeyko, and all others - please, guys, what do you think?

2444

I've seen the problem a few more times. When I move from another AP on the SSID to the AX3000T, external connectivity (5GHz AP <-> 2.5GHz client) works, but internal (5GHz AP <-> LAN) doesn't, for maybe 10 minutes. The 5GHz AP is bridged to the LAN, the 2.5GHz is a separate interface.

It looks like something in the bridging is not seeing the phone on the wireless device as opposed to the LAN device, except that responses from the other interface are presumably still passing through the same bridge and reaching the phone successfully. It's even possible the problem is elsewhere on the network, but I don't have it when I'm connected to other APs (there are 5 total on the SSID).

This thread is awfully noisy, should I be bringing this up somewhere else? I am using dimfishr's unmerged AN8855 patch, plus the others that kloon15 packaged, so it probably isn't right to report it as an issue elsewhere.

1 Like
2445

If u think its AN8855 related, report it here:

1 Like
2446

To me it looks like models with newer firmware/bootloader are all affected by this issue, it would be great if we could pinpoint the exact version/date where it changed, i would put smth like this there:

In newer revisions of this model running the stock bootloader, more than 6 reboots will result in a bootloop/soft-bricked device (but can be recovered using #link), so the following configuration is needed to prevent it:

1 Like
2447

I'm sure that you can use the reset button and TFTP to upload the stock firmware.

2448

Sorry, I have a similar experience, but I won't guarantee it, it looked like my mistake and I didn't double check.

Please see:

2449

More problems with bricks and UART from (OpenWrt U-Boot layout) since it is not specified that it should be installed only from the SNAPSHOT branch, and it is not necessary to install it on routers with 1.0.84 yet since it does not work in recovery mode even on test builds where the switch in the firmware works and here it is definitely UART in case of recovery.
And regarding your question. The author himself confirms, although not with certainty, that if you update the stock from 1.0.31 to 1.0.49 before flashing, there should be no problem.
Write this as a necessary step for flashing to OpenWrt.

2450

Thank you all for your responses.

I see @lessload has already updated the AX3000T Wiki, and now his statement doesn't sound as imperative as it did before. Thank you.

So, his new version uses "may" and "some cases" now. I would even use "might" there, though.

2 Likes
2451

I can confirm this. Using AX3000T + dimfish patch as an access point, wifi clients can connect and authenticate wifi but cannot get a valid IP address from the main router (i.e. DHCP broadcast packets are not traversing WLAN <-> LAN bridge). It seems that in fact broadcast packets are not being correctly bridged between Wireless radios and Ethernet ports. Manually setting the IP address in the Wireless clients enable connection, so this issue seems to be restricted to broadcast packets (like DHCP) not traversing the WLAN <-> LAN bridge.

I do agree. While we welcome less experienced users, it is hard to filter out real issues from ordinary issues like "how I de-brick my router". One possibility would be opening an specific topic for AX3000T de-bricking and moving all recover and de-bricking discussions over the new topic. This way this topic could be again useful for devs (who I believe stopped monitoring this thread due to the excess of noise).

2452

I already did a short report in the AN8855 pull request here about the issue of broadcast packets not being bridged between WLAN <-> LAN. @dimfish please let me know if any additional testing is required.

2 Likes
2453

There is new patchwork version v11 - I'm going to merge, but I think after xmas/ny

6 Likes
2454

Thank you. I will be away during the holidays, when I come back I can merge your new patch and repeat the tests.

Happy Holidays! :christmas_tree:

2456

24.10.0-rc3 - does it support modern switches or is it again a...?

2457

HELP! I just bought this router to flash OpenWRT on it. I did it successfully but after I restarted the router (I flashed the sysupgrade image as the page said of course) I got the orange blinking led issue (soft brick right?). There is any way to solve it? Will using MIWIFIRepairTool solve it if I try to flash https://cdn.cnbj1.fds.api.mi-img.com/xiaoqiang/rom/rd23/miwifi_rd23_firmware_153e1_1.0.49_INT.bin (1.0.49) with it? (since we don't have the official firmware binary for 1.0.31)

My router is the international model RD23, ESMT NAND with an and it came with the firmware 1.0.31. I backed up all the partitions successfully too! I'll leave the download of the partitions here:

I also have a CH341 in case I need to do some soldering for UART :sleepy:

2458

And before flashing, update the firmware to 1.0.49, why did you ignore it?
Probably because it is not written clearly? Too bad...
If you can't restore via TFTP, then UART, here you only need to change the bootloader.
And in general, if there is (OpenWrt U-Boot layout) for the router, you need to use it and there will be no such problems with it.
Good luck.

2459

dear, please help me.

I just bought one xiaomi AX3000T RD03 recently, the version is 1.0.84, but I checked the backed, it looks like ESMT on that chip. So I downgrade the version, and flash it to 23.05.5 initramfs-factory.ubi, after reboot, it shows blue light, but my PC can't get one IP from the lan port. even I manually change it to 192.168.1.x or 31.x, I still can't get the access.

so, what should I do next? thank you

2460

Restore with MIWIFIRepairTool (TFTP )and do not flash the original OpenWrt, but only custom ones provided in this thread by users. I will not list them, no more than 3-4 in total...
You can find them by searching.