הורדת תוכנת OpenWrt

TR3000-256MB EAEU1.0 — request for intermediate firmware and recovery file

Hello Cudy Support,

I sent this request to support@cudy.com on September 28 and again on September 29 (full S/N included in the emails), but have not received a reply yet, so I am posting here as well.

- Model: TR3000-256MB, EAEU1.0
- Production week in S/N: 2623
- Current stock firmware: 2.5.27-20260804-190139

I have NOT flashed anything yet. Another TR3000 256MB owner (S/N week 2626) reported on your recovery FAQ page on September 26 that the router stopped booting after flashing the intermediate firmware from the TR3000-256MB download page (DTS_and_intermediate_firmware, May 2025) on top of stock 2.5.21. My stock firmware is even newer and is not listed on the download page, so I want to confirm compatibility before flashing.

Could you please send me by email:
1. The intermediate firmware confirmed to work with my unit and stock 2.5.27.
2. The stock firmware for TFTP recovery (recovery.bin), ideally 2.5.27.
3. Which NAND flash chip is used in TR3000-256MB units from this batch.
4. Which OpenWrt image to install afterwards (cudy_tr3000-256mb-v1-squashfs-sysupgrade.bin from OpenWrt 25.12.x?).

Thank you!

Cudy x6 v2

Hi, I bought a Cudy X6 v2, but it doesn’t have 5GHz DFS FCC channels. Could you please send me the US firmware? I would really appreciate it. Thank you.

Hello.
I have a Cudy WR3000H V1.0.

Serial number: S0001004261801871
Current stock firmware: 2.4.5-20250515-105059

I would like to install the latest official OpenWrt.
Please send me the latest Cudy-signed OpenWrt intermediate firmware compatible with my WR3000H V1.0 and the new Flash revision.

Thank you.

Hello Cudy Support,

I have a Cudy M3000 v2.0 (board R37) with Motorcomm YT8821 WAN PHY and ESMT F50L1G41LC SPI NAND. It is currently running stock firmware 2.4.19-20250828.

I want to install official OpenWrt 25.12.5. The M3000 1.0_2.0.zip archive contains cudy_m3000-v1-sysupgrade__20251119.bin, but this image refers to rtl8221b_phy, while my router has YT8821.

Could you please email me a Cudy-signed intermediate firmware confirmed to support this exact hardware combination? Please also confirm which OpenWrt image I should install afterward and provide the installation steps. I have not flashed the router yet.

Thank you!

Hello Cudy Support,
I have sent you this message as an email too.
My WR300 v1 bootloops after flashing the official OpenWrt intermediate
firmware (openwrt-ramips-mt76x8-cudy_wr300-squashfs-flash.bin). Stock firmware 2.5.24 works fine on this unit; the bootloop only starts after installing the
intermediate.
Serial number: S0000759261510557
Board marked as: 300100157 REV1.1
flash: cFeon QX64A-104HIP
Cause (from the UART boot log): this unit doesn’t recognize the flash chip
(JEDEC ID 1c 71 17). Newest firmware’s U-Boot recognizes it as `en25qx64a`,
but the kernel inside the intermediate (5.15.167, Sep 2024) has no driver
entry for it:
```
[ 0.350812] spi-nor spi0.0: unrecognized JEDEC id bytes: 1c 71 17 1c 71
17
[ 0.357913] spi-nor: probe of spi0.0 failed with error -2
…
[ 0.471677] Kernel panic – not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
```

Flashing the intermediate through tftp recovery also downgrades the
bootloader to an older U-Boot (Feb 11 2025) that prints
```
flash manufacture id: 1c, device id 71 17
Warning: un-recognized chip ID, please update bootloader!
```

Additionally, the TFTP recovery appears to only accept Cudy-signed images – an unsigned OpenWrt image passes the “R54” name check but is never flashed
(no “flash image / rsa verify” lines). So I could not install a patched
OpenWrt build myself;
I restored the router with the stock firmware via TFTP recovery and it
works again.

Could you please provide an updated intermediate firmware whose kernel
supports the EN25QX64A (1c 71 17)? A similar issue was fixed for the AX3000
series after its flash chip change.
Also, would you consider disabling RSA verification in the U-Boot TFTP
recovery, and/or providing a way to interrupt the U-Boot boot sequence to
reach a serial console? Otherwise an spi programmer adapter is required (like ch341a).
Thank you