OpenWrt Yazılımı İndir

It seems something has changed in the bootloader installed with the latest WR300 firmware (WR300-R54-2.2.8-20241015-162008-flash) – after downgrade to the older version (WR300-R54-1.16.15-20231130-131612-flash) I can see normal messages at 115200 again, no more garbage.
Could you tell me how to stop u-boot so I can load the OpenWrt image (built by me, not signed by you) – it boots the original firmware from flash without any delay, and no Linux shell access is possible.

@Paco,
Dear Paco Mercado,
Thank you for contacting Cudy support team. For now we don’t have plan to develop OpenWrt firmware. We will provide feedback to the R&D department for evaluation.

“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…”
,

Thank you for contacting Cudy support team. For now we don’t have plan to develop OpenWrt firmware. We will provide feedback to the R&D department for evaluation.

“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…”

@Denis,
Dear Denis,

The AP3000 doesn’t support to recover to Cudy firmware via TFTP now. We have plan to add this feature in future.

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

@Tadeusz
Dear Tadeusz,
Yes, you are right. First update the intermediate firmware from GoogleDrive to remove signature. Second Use https://firmware-selector.openwrt.org/?version=24.10.0&target=mediatek%2Ffilogic&id=cudy_wr3000s-v1.

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

@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!”