Hi,
i bought a Cudy WR1300 for usage as VPN-Client and for better WiFi. When i download the openwrt software from cudy website (https://www.cudytech.com/openwrt_software_download) and flash the new firmware the router doesn't startup anymore. 3 LEDS (USB, WPS and SYS) are blinking slowly and the device is not reachable over Ethernet via 192.168.1.1.
From there i can only recover the router to factory firmware.
Any ideas how to proceed?
Thanks,
Martin
The software coming from the cudy website is not an official version of OpenWrt. You should contact Cudy's support or user forums for help.
i also tried the original files from OpenWrt but the router doesn't allow to flash these binaries via GUI.
Follow https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=cd2b661453a8a2b8260dfb9b9c0dc5297b98133
You need to flash it twice, if I understand it correctly.
I used this guide. After flashing the openwrt binary from cudytech via luci the router doesn't run properly.
What do you mean with twice?
Flash cudys openwrt, then proper openwrt.
Reset the settings in the process.
okay that doesn't work. After flashing cudy openwrt the router isn't acessible anymore. Flashing openwrt directly is not allowed by standard OEM firmware. I directed it to cudy support.
The recovery in the github link should still work, doesn't solve your openwrt problem though.
I got an image from cudy support for version 19.07. which is working. But with the version 19.07. i am not able to install "opkg install openvpn-openssl" package so i cannot configure OpenVPN. Is it possible to update from this version to a newer one (eg. 21.02.3). After Flashing the sysupgrade image (21.02.3) the router is not booting up.
it should, if it doesn't, you'd need serial port access to the router to figure out why...
The initramfs images literally just load OpenWrt into RAM and it will not survive a reboot... The next step is to make it persistent by flashing the sysupgrade image (if you're using LuCI: System > Backup / Flash Firmware)
thank you for good explaining 
no problem.
If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
For future reference, how did you manage to get it installed?
I got an image called "openwrt-ramips-mt7621-cudy_wr1300-19.07-flash.bin" from cudy support via email. I am not able to attach it here because format is not allowed. With this image i was not able to install the images from: https://openwrt.org/toh/hwdata/cudy/cudy_wr1300 but latest stable version 22.03.0-rc6 : https://firmware-selector.openwrt.org/?version=22.03.0-rc6&target=ramips%2Fmt7621&id=cudy_wr1300 is working now.
Thanks for the help. It is a very nice community here
thnx for the update.
thx for this information. Last year i bought some of the cudy wr1300 with the w25q128 and now i've one with XM25QH128C. I wrote yesturday to cudy, because more people have issues with the version from the website, but they reply only with the link to the website. Is it possible to send me your Firmware file and can you approve you have the XM25QH128C. It is shown in dmesg.
dmesg | grep spi
this firmware work with XMC-XM25QH128C but i cant upgrade to 22.03.0-rc6. UART says following error message.
[ 1.708692] mt7530 mdio-bus:1f: Link is Up - 1Gbps/Full - flow control rx/tx
[ 1.718701] VFS: Mounted root (squashfs filesystem) readonly on device 31:5.
[ 1.729892] Freeing unused kernel memory: 1260K
[ 1.734455] This architecture does not have kernel memory protection.
[ 1.740885] Run /sbin/init as init process
[ 1.781275] SQUASHFS error: xz decompression failed, data probably corrupt
[ 1.788301] SQUASHFS error: Failed to read block 0x1971ba: -5
[ 1.794040] SQUASHFS error: Unable to read fragment cache entry [1971ba]
[ 1.800709] SQUASHFS error: Unable to read page, block 1971ba, size e1ac
[ 1.807415] SQUASHFS error: Unable to read fragment cache entry [1971ba]
[ 1.814106] SQUASHFS error: Unable to read page, block 1971ba, size e1ac
[ 1.820788] SQUASHFS error: Unable to read fragment cache entry [1971ba]
[ 1.827470] SQUASHFS error: Unable to read page, block 1971ba, size e1ac
[ 1.834170] SQUASHFS error: Unable to read fragment cache entry [1971ba]
[ 1.840837] SQUASHFS error: Unable to read page, block 1971ba, size e1ac
[ 1.847546] SQUASHFS error: Unable to read fragment cache entry [1971ba]
[ 1.854230] SQUASHFS error: Unable to read page, block 1971ba, size e1ac
[ 1.861018] Starting init: /sbin/init exists but couldn't execute it (error -5)
[ 1.868309] Run /etc/init as init process
[ 1.876699] Run /bin/init as init process
[ 1.883295] Run /bin/sh as init process
[ 1.932954] SQUASHFS error: xz decompression failed, data probably corrupt
[ 1.939905] SQUASHFS error: Failed to read block 0x6e: -5
[ 1.945298] SQUASHFS error: Unable to read data cache entry [6e]
[ 1.951276] SQUASHFS error: Unable to read page, block 6e, size 269ac
[ 1.957772] SQUASHFS error: Unable to read data cache entry [6e]
[ 1.963768] SQUASHFS error: Unable to read page, block 6e, size 269ac
[ 1.970218] SQUASHFS error: Unable to read data cache entry [6e]
[ 1.976210] SQUASHFS error: Unable to read page, block 6e, size 269ac
[ 2.030053] SQUASHFS error: xz decompression failed, data probably corrupt
[ 2.036983] SQUASHFS error: Failed to read block 0x6e: -5
[ 2.089870] SQUASHFS error: xz decompression failed, data probably corrupt
[ 2.096795] SQUASHFS error: Failed to read block 0x6e: -5
[ 2.102311] Starting init: /bin/sh exists but couldn't execute it (error -5)
[ 2.109386] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[ 2.123519] Rebooting in 1 seconds..
so i tested the daily snapshot and i got a another error
[ 1.579146] /dev/root: Can't open blockdev
[ 1.583297] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 1.590794] Please append a correct "root=" boot option; here are the available partitions:
[ 1.599113] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.607366] Rebooting in 1 seconds..
i was able to recover via tftp this "openwrt-ramips-mt7621-cudy_wr1300-19.07-flash.bin" working image.
complete logfile and images:
https://drive.google.com/drive/folders/1xfVDv-Qm7g0Qz5d7X8PitZ3pSax_35S4?usp=sharing
The SQUASHFS errors might be caused by a heat problem that is not related to the XM25QH128C issues.
I got them on my WR1300 (with W25Q128) today after it had been running at ~27°C room temperature for a while with the metal shield getting quite hot. They disappeared when unplugged it and let it cool down for a while, and they re-appeared when it had gotten hot again.
@obazda20 Can you tell how hot your room and device was when you got these SQUASHFS errors, and was it different when you tested the snapshot?