frollic
November 27, 2025, 1:25pm
1
Affected models:
AP3000 Outdoor v1
AP3000 Wall v1
M3000 v1/v2
TR3000 v1
WR3000E v1
WR3000H v1
WR3000S v1
WR3000P v1
Serials start with 2543 or later.
ref: https://www.cudy.com/blogs/faq/openwrt-software-download
Very nice of them to make people aware of it.
There's already a PR for the new flash chip pending for the TR3000, haven't checked other Cudy's.
IF you run into this, you can still recover using https://www.cudy.com/blogs/faq/how-to-recovery-the-cudy-router-from-openwrt-firmware-to-cudy-official-firmware .
10 Likes
I'll update some wiki pages with this info. Thank you.
I'm monitoring commits and haven't seen such.
1 Like
frollic
November 28, 2025, 10:31am
3
FYI, TR3000's already done.
2 Likes
I have done only WR3000S and WR3000H which I created or updated since the beginning.
EDIT : some news here
main ← IceblueSakura:add-support-F50L1G41LC-flash-chip
I encountered this problem with my router Cudy WR3000H serial number starts with… 2543.
CRITICAL WARNING: The "November 2025" Trap
Please read this carefully before buying.
Since today is November 2025, you are buying exactly when a hardware revision change is happening.
According to Cudy's official technical notices:
• Units manufactured starting November 2025 (SN code starts with 2543 or higher) use a new Flash chip (F50L1G41LC).
• The Issue: The current stable OpenWrt builds likely do not support this new flash chip yet. If you flash an older OpenWrt image onto these new "late 2025" units, you will brick the router.
Action Plan for Buying:
1. Check the Serial Number (S/N): Look at the box. You want an S/N lower than 2543 (e.g., 2530, 2512, 24xx). These are guaranteed to work with current OpenWrt builds.
2. If you get a new unit (S/N 2543+): Do NOT flash OpenWrt immediately. You must wait for the OpenWrt developers to patch support for the F50L1G41LC flash chip, or use the specific "Intermediate Firmware"
It would have been wiser from Cudy to label these new devices v2 rather than keeping v1.
1 Like
frollic
November 28, 2025, 10:54am
5
badulesia:
EDIT : some news here
yes, that's the PR I found the other day (and added to TR3000 wiki page).
at least they're identifiable using the serial #.
1 Like
I tried to link directly to the most recent post, it didn't work as expected.
frollic
November 28, 2025, 11:01am
7
I see I missed the comment by hauke (most likely made after I posted), there's also a back port for 24.10, that's nice.
1 Like
Thanks for the headsup. A batch of 50 WR3000 ordered 2 weeks ago still goes with 2532* serial numbers. I was contemplating on ordering WR3000S devices, too, which I will do in smaller quanitity to test the changes.
2 Likes
It is likely that devices sold during the next weeks would be compatible. Real question is when the newer will be shipped? I doubt that the incompatibility with OpenWrt can be a valid reason for refusing the delivery.
frollic
December 1, 2025, 9:48am
10
the PRs required for new flash chip support have been merged, meaning snapshots should already work, while stable requires a new major or minor release.
2 Likes
Good news.
Can you give the link to the commit please, I can't find it? I'd like to check which devices are concerned.
frollic
December 1, 2025, 11:49am
12
they're at the bottom of the PR you posted, but I guess they only relate to the TR3000 ?
openwrt-24.10 ← hauke:add-esmt-F50L1G41LC-24.10
opened 08:51PM - 27 Nov 25 UTC
Backport upstream patch to add support for the ESMT F50L1G41LC flash chip. It is… used in multiple Cudy products manufactured starting November 2025.
main PR: https://github.com/openwrt/openwrt/pull/20962
main ← hauke:add-esmt-F50L1G41LC
opened 08:38PM - 27 Nov 25 UTC
Backport upstream patch to add support for the ESMT F50L1G41LC flash chip. It is… used in multiple Cudy products manufactured starting November 2025.
24.10 PR: https://github.com/openwrt/openwrt/pull/20963
1 Like
I build an image on the weekend with the latest commits, flashed onto an “old” WR3000s, no issues. Will report once I have a device with new flash chip in hand, too.
2 Likes
That's what I feared, titles of theses commits are cryptic. Thank you.
EDIT
The commit says "multiple Cudy products" so I assume it is available for every devices involved.
Thanks to @hauke for such a quick solution. I'm always impressed by the devs' involvment to this project.
1 Like
Has a fix been released for Cudy WR3000H?
Apparently yes, but you'll have to wait for 24.10.5, or use a snapshot.