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
900 comments
@Marek M,
Would you please list the models that need downgrade the firmware? We will fix these models first.
“Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!”
@Dear Marek M.
Thank you for contacting Cudy support team. Thank you for your kindly advice. We will provide your feedback to the product department for evaluation. I think we will do better about this.
“Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!”
@cruday,
Our technical support has sent you the firmware via email. Please check.
“hi, I need cudy_ap3000indoor-v1-sysupgrade.bin…outdoor doesnt work”
@Dear Luis,
Our technical support has contacted you via email. Please check.
“Hi, Thank you for the fast answer.
Already flashed the file indicated (2.0) and it keeps saying the same… FILE IS INVALID… Any idea?
Thanks in advance.”
Would it be possible for Cudy to test all new official firmware releases to accept the intermediate firmware, without the extra step to downgrade to the old version first (then intermediate firmware, and finally full OpenWrt – flashing 3 times total)? Flashing is time consuming (imagine an ISP doing mass deployment for customers – small ISP like me, not big enough to order your hardware with OpenWrt pre-installed from factory) and each time there is also some risk of bricking the device (power failure etc.), better do it as few times as possible, ideally just make the official firmware accept OpenWrt sysupgrade images directly (maybe just with a warning that it’s not official, warranty void and ask the user for extra confirmation). If the reason for signed firmware is that you’re worried about possible security issues (like malicious remote hacked OpenWrt installs), the extra confirmation could require physical button press (similar to recent MikroTik RouterOS device-mode). Not complaining here, it’s already great that you support OpenWrt, many thanks for that but the process could be made even easier – thanks!