OpenWrt on xiaomi-4a-gigabit will infinite restart

this is the breed,I don't know how to see my flash chip version,but it not 44mhz

Have you tried opening the case to inspect the flash chip if you cannot identify it through the holes in the plastic case?

The 8 pin legged flash chip is located near the DC power socket.

Okay, I'll take it apart tomorrow and take a look

Does your R4AG have the chinese language or Global International firmware?

It's known problem.
See this topic.
You can update breed. At least breed r1337 support EN25QX128A (
JEDEC id=1c7118).
But openwrt don't :frowning:


this is the flash chip

i have open the case

there is nothing on it :joy:

ok,i look forward to the update :sob: :sob: :sob:

It doesn't seem to be very clear, I will take pictures tomorrow when I take it apart.


please check the IC p/n.

As pointed out by @123serge123 , it would appear the chip ID 1c7118 is for the EN25QX128A.

Known issue appearing in very latest chinese language model R4AG, and R4C devices.
Issue 9442

BTW you can (and I think have to) update breed without solder iron.
breed support to start new breed version from memory.
Connect to breed with telnet do execute commands:

boot breed 0x80001000

Than make sure that flash is recognized in Web-interface and upgrade bootloader as usual.

i open again,the photo is too blurry,but it is QX128A

@EpicDogger, did you try to flash my build? here:

1 Like

Not yet, can this be swiped directly in Breed?

I'm not sure. If Breed could flash openwrt ......-sysupgrade.bin code, then ok.
Otherwise, you have to back to stock fw first.....

I tried so many builds to flash and this is the one that finally worked. Are you able to let me know what's different on this build? Also, I set this up with mesh and I'm getting pretty slow speeds and wondering if you've experienced this and thanks for the build!

It's kernel un-supported new flash IC EN25QX128A issue.

I met this on my 4C, refer to here:

Also here:

Then, I try to add a PR for the issue, not success:

The issue / my solution, not related mesh function, and I do not know how to use mesh, cannot help.

You didn't implement the requested changes. socram8888 mentions that you should remove SECT_4K from the changes, because the chip supports SFDP.

SFDP is small amount of information within the chip itself that tells the system what features it supports, so manually specifying SECT_4K is redundant. If the chip supports 4K-sectors, that information will be in the SFDP and the system will use the feature automatically.

If you just make the changes socram8888 wanted, maybe they'll approve the PR.