警告
本網頁列出了支援OpenWrt系統的設備的軟體，在下載和安裝軟體之前，請注意OpenWrt Project是一個針對嵌入式設備的Linux作業系統。 OpenWrt 並沒有嘗試建立單一靜態韌體，而是提供了一個具有套件管理功能的完全可寫入檔案系統。這使您無需選擇供應商提供的應用程式和配置，並允許您透過使用軟體包來自訂設備以適應任何應用程式。對於開發人員來說，OpenWrt 是建立應用程式的框架，而無需圍繞它建立完整的韌體；對使用者來說，這意味著完全客製化的能力，以前所未有的方式使用裝置。
描述
- 此檔案僅當您的路由器在 Cudy Web UI 下運作時才能使用。
- 如果路由器已經在OpenWRT UI下工作，用戶應先將其恢復到Cudy官方韌體。然後用這個韌體升級路由器。
- 如何將路由器恢復至Cudy官方韌體？請閱讀下載文件中的自述文件。
保固：
Cudy特此聲明
- 我們 Cudy 對非深圳市 Cudy 科技有限公司發布的任何軟體不承擔任何保證。
- 對於安裝了非深圳市酷迪科技有限公司發布的任何軟體的產品，我們不承擔任何保證。
- 如果您需要使用openwrt軟體，建議您從Cudy官網下載。
下載 OpenWrt 韌體以刪除簽名檢查：驅動程式
OpenWrt 韌體查找器（不是由Cudy 發布）：OpenWrt 韌體選擇器
1319 則留言
@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!