OpenWrt szoftver letöltése

@Dear Misha Gorbunov,
cudy_m3000-v1-sysupgrade__20251119.bin is the correct firmware for your router.

“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!"

@Dear enjoyer,
OK, We will check it
“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"

@Dear Alex,
Our technical support has sent you the firmware via email. Please check.

“Hello Cudy Support Team,

I have a Cudy WR3000 V1.0 (EU 1.0).

Current stock firmware:
2.4.19-20250828-192837

Serial number:
WR3000243506896

I would like to install official OpenWrt.

Please provide the latest Cudy-signed OpenWrt intermediate firmware compatible with my WR3000 V1.0 and my flash memory revision.

Thank you."

@Dear Henrique,
OK. Our technical support has sent you the firmware via email. Please check.
In addition, the firmware is in the Google Drive. I don’t know why you said this.

“Hi, I have a Cudy WR3000 EU 1.0 router with serial number starting with 2451 running firmware 2.2.6 US. I would like to install OpenWRT. Can you provide me the intermediate firmware for my device?

By the way, is there any reason not to have it available in the Google Drive folder along with the other models?"

I would like the Cudy-signed intermediary file for flashing my router with OpenWrt. What I have is Firmware Version 2.5.28-20260807-120317 and Hardware M3000 V2.0 with the YT8821 variant. Why is this file specifically not available on Google Drive where all the other files are?