Update: December 24,2025 Good news!
The OpenWrt forum has merged the pacth which supports the new Flash F50L1G41LC and update the OpenWrt firmware to the version 24.10.5. So if you download the OpenWrt firmware version 24.10.5 or newer version in the future to update the Cudy related models. There will be no problem.
Important Notice: November 24, 2025
Cudy AX3000 series routers manufactured starting in November 2025 (TR3000, SN code start with 2543 or later. 2543 in the SN means the 43th week in the year 2025 ) use the new Flash F50L1G41LC. Upgrading to older versions of OpenWrt intermediate firmware or OpenWrt firmware will prevent the device from booting. Therefore, we will be releasing new firmware updates for these products to add restrictions. If the device is detected to be using the new Flash, it will not be able to upgrade to older firmware versions 2.3.X or earlier. Additionally, previously provided OpenWrt intermediate firmware for older Flash devices will not be compatible.
Affected models include: AP3000 Outdoor 1.0, AP3000 Wall 1.0, M3000 1.0/2.0, TR3000 1.0, WR3000E 1.0, WR3000H 1.0, WR3000S 1.0, and WR3000P 1.0.
Cudy has released the new OpenWrt intermediate firmwares, which have been updated to Google Drive. Please switch to the new intermediate firmware.
Regarding the OpenWrt firmware, we are still waiting for the official OpenWrt forum to release an OpenWrt firmware compatible with the new Flash. Once released, please use the new OpenWrt firmware.
If the SN code is less than 2543. It uses the old flash. There is no such problem.
Warnings
This webpage lists software of devices which support OpenWrt system, before download and install the software, please note that OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Description
- This file can only be used when your router works under Cudy web UI.
- If the router already works under OpenWRT UI, user should restore it to Cudy official firmware first. And then upgrade the router with this firmware.
- How to restore the router to Cudy official firmware? Please read the readme in the file downloaded.
Warranty:
Cudy hereby declares
- We, Cudy, do not undertake warranty for any software that is not released by Shenzhen Cudy Technology Co., Ltd.
- We do not assume any warranty for products that have installed any software not released by Shenzhen Cudy Technology Co., Ltd.
- If you need to use openwrt software, we suggest you download it from Cudy's official website.
Download OpenWrt Firmware to Remove Signature Check: Drive
OpenWrt Firmware Finder (Not Released by Cudy): OpenWrt Firmware Selector
1294 comments
@Marek
Dear Marek,
The correct connection rate is 115200. Please have a try. You can try to recover the device according to the instruction on the website:
https://www.cudy.com/blogs/faq/how-to-recovery-the-cudy-router-from-openwrt-firmware-to-cudy-official-firmware?pos=1&_sid=cd51a5301&ss=r
“I’d like to work on adding official OpenWrt support for WR300, but having some trouble. Trying to access the u-boot on the WR300 using the TTL serial port, to be able to test OpenWrt images or recover factory firmware. On power-up without reset button, device boots normally and shows messages at 115200 and any characters entered are echoed back so the serial connection is working, but no Linux shell access possible. Now trying to power up the WR300 while holding the reset button, the serial console just shows some garbage which looks like wrong serial speed, but have tried all of 9600/19200/38400/57600/115200 and can’t seem to be able to see any u-boot messages, just the garbage. Does it use a non-standard serial speed and/or binary protocol (like x/y/zmodem) for recovery? Your help would be much appreciated – thanks!”
Wouln’t make more sense if Cudy would contribute to the OpenWRT project directly?
Your firmware is based on OpenWRT, so it would be a way to give back to the community and, also, facilitate a path for us, non tech-savy people, to use more up to date versions.
I understand you might want to keep you “secret sauce” under wraps, but if there’s a will, there’s a way…
Hello Cudy team,
I found that VLAN support in Cudy AP3000 is not up to the features I expected from business-oriented device (unfortunately after purchase). I would like to switch to OpenWrt (it now supports AP3000) to see if it can be done with that OS. But I found out that it will be impossible to recover to Cudy firmware, because tftp restore is not available in this AP. Do you have plans to resolve this issue with firmware update, or it is limited in hardware? Should I better return this AP and give up?
Hello my friend,
I was looking forward the latest OpenWrt 24.10.0 stable version. Finally it was released. I would like to upload it into my Cudy WR3000S v1. Should I follow your instruction above:
1/ Remove signature check from GoogleDrive.
2/ Use https://firmware-selector.openwrt.org/?version=24.10.0&target=mediatek%2Ffilogic&id=cudy_wr3000s-v1
or
to be 100% sure download OpenWrt from Cudy’s official website (but cannot find it yet)?
Regards,
Tadeusz
I’d like to work on adding official OpenWrt support for WR300, but having some trouble. Trying to access the u-boot on the WR300 using the TTL serial port, to be able to test OpenWrt images or recover factory firmware. On power-up without reset button, device boots normally and shows messages at 115200 and any characters entered are echoed back so the serial connection is working, but no Linux shell access possible. Now trying to power up the WR300 while holding the reset button, the serial console just shows some garbage which looks like wrong serial speed, but have tried all of 9600/19200/38400/57600/115200 and can’t seem to be able to see any u-boot messages, just the garbage. Does it use a non-standard serial speed and/or binary protocol (like x/y/zmodem) for recovery? Your help would be much appreciated – thanks!