Cudy WR3000P unusable after 25.12.2 update. What went wrong?

[VFX]

Hi,

I've bought a used WR3000P v1. Someone already flashed OpenWrt on it as overview showed:

Model: Cudy WR3000P v1 (OpenWrt U-Boot layout)
Firmware Version: OpenWrt 24.10.5 r29087-d9c5716d1d / LuCI openwrt-24.10 branch 25.340.26705~d88390b
Kernel Version: 6.6.119

When I tried to update to 25.12.2 version, after downloading firmware file for WR3000P from firmware selector, it showed:

Image check failed:
upgrade: Device cudy,wr3000p-v1-ubootmod not supported by this image
upgrade: Supported devices: cudy,wr3000p-v1 R57 invalid sysupgrade file Image check failed.

After searching for a solution on this forum and online, I came across this PR. There was a link to yandex.disk where I downloaded 25.12.2 version called openwrt-25.12.2-mediatek-filogic-cudy_wr3000p-v1-ubootmod-squashfs-sysupgrade.itb and flashed it.

I'm not sure did I made a mistake flashing this file, but Wifi got disabled, so I thought I bricked it. Luckily, after connecting it to LAN port, web UI showed up, so I enabled WiFi again. Overview was showing 25.12.2 version, but the connection wasn't that great since websites were not loading from time to time.

Both Cudy and ISP's router had 192.168.1.1 IP address, so I wanted to switch Cudy to 192.168.0.1 in order to separate them. I did the same thing before the update to 25.12.2 and it worked with no issues. Now, after I did it, I can't access web UI neither on 192.168.1.1 nor 192.168.0.1. SSH doesn't work either. I tried with static IP, but no luck.

At this point I'm not sure what went wrong and what to do anymore, so I decided to try going back to stock firmware and follow Cudy's guide..

The procedure doesn't work, as nothing happens after turning the router on while holding the reset button. I saw some user having the same problem with WR3000S and the support replied him:

"You've modified your router's U-Boot. Restoring it via tftpd won't work. You can try searching for a recovery method online. We don't currently have one."

As I don't want to break this device completely, can someone tell me which recovery procedure to do from here? Also, what I did wrong? Because if I manage to recover this router, I would like to install and use OpenWrt again.

[elder_tinkerer]

Please try the Failsafe mode.
If this doesn't work, i assume you need to open the router to connect a USB2Serial adapter to gain access again.

[VFX]

I'll try that, thanks. Do you have any idea what might have caused this issue?

[elder_tinkerer]

Because that happened after you changed the LAN address, i assume it's related to

[OpenWrt Wiki] Change LAN IP in LuCI (to an IP on a different subnet)

Please read the part about OpenWrt 25.12 and CIDR notation.

[badulesia]

DO NOT use the ubootmod version unless you have made the proper change before. For most users it's unnecessary, keep with the normal version. Furthermore ubootmod is only available for main snapshots, not 25.12.2. So you may have flashed an unofficial file.

You can recover the device using TFTP. There is dedicated page on Cudy website for this. You will need to download the cudy firmware, and flash it. Than fully reinstall Openwrt. Let's hope installing ubootmod version didn't mess too much the partition layer.

Wie kann ich den Cudy-Router von der OpenWRT-Firmware auf die offiziel

[elder_tinkerer]

Since the router already came with the U-Boot-mod (as the OP mentioned) and the TFTP doesn't work

@VFX

At this point I'm not sure what went wrong and what to do anymore, so I decided to try going back to stock firmware and follow Cudy's guide..

The procedure doesn't work, as nothing happens after turning the router on while holding the reset button. I saw some user having the same problem with WR3000S and the support replied him:

"You've modified your router's U-Boot. Restoring it via tftpd won't work. You can try searching for a recovery method online. We don't currently have one."

this (otherwise good) advice will not work for the OP.

[frollic]

@badulesia

There is dedicated page on Cudy website for this

OP linked to it in their 1st post.

[VFX]

@badulesia The router already came with the ubootmod version. I don't know why this version was flashed, but I was actually hoping I could update the firmware from the firmware selector, without having to go on 4pda forum or yandex disk to download it.

@frollic Unfortunately, it didn't work. I've tried every LAN port and even tried WAN for the sake of trying. Also tried 192.168.0.88 instead of 192.168.1.88, but tftpd just doesn't start at all.

[frollic]

I deleted my post (twice ,) ), since your device already had ubootmod installed, it won't work, as elder_tinkerer (and Cudy) pointed out.

[VFX]

Yeah, I see now, there was a cached version in my browser since I had to go afk while replying.

So failsafe method which elder_tinkerer suggested is the next thing to try?

[frollic]

if a proper reset (https://openwrt.org/docs/guide-user/troubleshooting/failsafe_and_factory_reset), doesn't work, yes, serial's your only option.

[konus]

The uboot mod code is here: https://git.openwrt.org/openwrt/openwrt/diff/package/boot/uboot-mediatek/patches/468-add-cudy_wr3000p-v1.patch?id=6b3b7c7dc1e9b139c337fe28034dabace62188dc

If I understand the code correctly you can press the reset button during power up and that will cause uboot to load a recovery image (openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb) using tftp from 192.168.1.254

That is something you can try if reset doesnt work. However serial is still recommended since that shows exactly what is happening.

[frollic]

@konus

If I understand the code correctly you can press the reset button during power up and that will cause uboot to load a recovery image (openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb) using tftp from 192.168.1.254

I don't think you do, the recovery image isn't written to flash while converting to ubootmod - https://github.com/openwrt/openwrt/pull/21943/changes/6b3b7c7dc1e9b139c337fe28034dabace62188dc.

recovery via button when using ubootmod would have been nice though.

although the steps in the instruction aren't really very detailed...

[konus]

I think you end up with a device running initramfs from RAM and should be able to do step 8 and 9 to make it a permanent install again.

[frollic]

you might be right, but step 6 seems unneeded, it's only to verify it's booted ?

feels like the ubootmod initramfs recovery's undocumented, assuming it can be triggered externally (haven't looked for it very hard though) ... ?

[konus]

yes I agree that the instructions are confusing. The install sequence seems to indicate it will default to tftp without any action.

However this line seems to indicate that the reset button needs to be pressed:

++boot_first=if button reset ; then led $bootled_rec on ; run boot_tftp_recovery ; setenv flag_recover 1 ; run boot_default ; fi ; bootmenu

[konus]

OK I understand the install instructions now. The environment partitions have not been created yet so the device will just go into a tftp recovery loop automatically.

++boot_default=if env exists flag_recover ; then else run bootcmd ; fi ; run boot_recovery ; setenv replacevol 1 ; run boot_tftp_forever

[VFX]

Sorry, everything about this is new to me, so I'm not sure did you mean to change PC's IP to x.x.x.254? Powering it on while holding a reset button does nothing. On the router itself, USB LED is turned on, while LAN1 is blinking (where the cable is plugged), while in tftpd64.exe, in the log viewer, I see this:

Summary

File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:10.585]
Connection received from 192.168.1.1 on port 2416 [06/05 11:32:11.643]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:11.643]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:11.643]
Connection received from 192.168.1.1 on port 3461 [06/05 11:32:12.678]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:12.678]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:12.678]
Connection received from 192.168.1.1 on port 1434 [06/05 11:32:13.720]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:13.720]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:13.720]
Connection received from 192.168.1.1 on port 2478 [06/05 11:32:14.771]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:14.771]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:14.771]
Connection received from 192.168.1.1 on port 3529 [06/05 11:32:15.828]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:15.828]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:15.828]
Connection received from 192.168.1.1 on port 1501 [06/05 11:32:16.863]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:16.863]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:16.863]
Connection received from 192.168.1.1 on port 2545 [06/05 11:32:17.914]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:17.914]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:17.914]
Connection received from 192.168.1.1 on port 3590 [06/05 11:32:18.956]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:18.956]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:18.956]
Connection received from 192.168.1.1 on port 1563 [06/05 11:32:20.007]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:20.007]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:20.007]
Connection received from 192.168.1.1 on port 2608 [06/05 11:32:21.047]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:21.047]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:21.047]
Connection received from 192.168.1.1 on port 3653 [06/05 11:32:22.098]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:22.098]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:22.098]
Connection received from 192.168.1.1 on port 1625 [06/05 11:32:23.131]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:23.131]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:23.131]
Connection received from 192.168.1.1 on port 2669 [06/05 11:32:24.187]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:24.187]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:24.187]
Connection received from 192.168.1.1 on port 3713 [06/05 11:32:25.222]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:25.222]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:25.222]
Connection received from 192.168.1.1 on port 1686 [06/05 11:32:26.264]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:26.264]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:26.264]
Connection received from 192.168.1.1 on port 2731 [06/05 11:32:27.315]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:27.315]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:27.315]
Connection received from 192.168.1.1 on port 3776 [06/05 11:32:28.363]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:28.363]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:28.363]
Connection received from 192.168.1.1 on port 1749 [06/05 11:32:29.404]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:29.404]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:29.404]
Connection received from 192.168.1.1 on port 2793 [06/05 11:32:30.454]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:30.454]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:30.454]
Connection received from 192.168.1.1 on port 3838 [06/05 11:32:31.496]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:31.496]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:31.496]
Connection received from 192.168.1.1 on port 1812 [06/05 11:32:32.545]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:32.545]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:32.545]
Connection received from 192.168.1.1 on port 2857 [06/05 11:32:33.587]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:33.587]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:33.587]
Connection received from 192.168.1.1 on port 3901 [06/05 11:32:34.637]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:34.637]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:34.637]
Connection received from 192.168.1.1 on port 1873 [06/05 11:32:35.670]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:35.670]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:35.670]
Connection received from 192.168.1.1 on port 2918 [06/05 11:32:36.727]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:36.727]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:36.727]
Connection received from 192.168.1.1 on port 3963 [06/05 11:32:37.762]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:37.762]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:37.762]
Connection received from 192.168.1.1 on port 1936 [06/05 11:32:38.804]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:38.804]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:38.804]
Connection received from 192.168.1.1 on port 2981 [06/05 11:32:39.856]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:39.856]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:39.856]
Connection received from 192.168.1.1 on port 4026 [06/05 11:32:40.907]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:40.907]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:40.907]
Connection received from 192.168.1.1 on port 1999 [06/05 11:32:41.948]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:41.948]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:41.948]
Connection received from 192.168.1.1 on port 3044 [06/05 11:32:42.998]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:42.998]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:42.998]
Connection received from 192.168.1.1 on port 4088 [06/05 11:32:44.040]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:44.040]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:44.040]
Connection received from 192.168.1.1 on port 2061 [06/05 11:32:45.075]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:45.075]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:45.075]
Connection received from 192.168.1.1 on port 3106 [06/05 11:32:46.132]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:46.132]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:46.132]
Connection received from 192.168.1.1 on port 1078 [06/05 11:32:47.168]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:47.168]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:47.168]
Connection received from 192.168.1.1 on port 2123 [06/05 11:32:48.219]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:48.219]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:48.219]
Connection received from 192.168.1.1 on port 3168 [06/05 11:32:49.259]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:49.259]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:49.259]
Connection received from 192.168.1.1 on port 1141 [06/05 11:32:50.309]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:50.309]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:50.309]
Connection received from 192.168.1.1 on port 2185 [06/05 11:32:51.350]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:51.350]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:51.350]
Connection received from 192.168.1.1 on port 3230 [06/05 11:32:52.401]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:52.401]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:52.401]
Connection received from 192.168.1.1 on port 1203 [06/05 11:32:53.435]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:53.435]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:53.435]
Connection received from 192.168.1.1 on port 2247 [06/05 11:32:54.492]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:54.492]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:54.492]
Connection received from 192.168.1.1 on port 3292 [06/05 11:32:55.527]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:55.527]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:55.527]
Connection received from 192.168.1.1 on port 1265 [06/05 11:32:56.583]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:56.583]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:56.583]
Connection received from 192.168.1.1 on port 2310 [06/05 11:32:57.617]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:57.617]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:57.617]
Connection received from 192.168.1.1 on port 3354 [06/05 11:32:58.667]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:58.673]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:58.673]
Connection received from 192.168.1.1 on port 1327 [06/05 11:32:59.708]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:32:59.708]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:32:59.708]
Connection received from 192.168.1.1 on port 2372 [06/05 11:33:00.758]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:00.758]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:00.758]
Connection received from 192.168.1.1 on port 3416 [06/05 11:33:01.799]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:01.799]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:01.799]
Connection received from 192.168.1.1 on port 1387 [06/05 11:33:02.848]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:02.848]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:02.848]
Connection received from 192.168.1.1 on port 2432 [06/05 11:33:03.889]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:03.889]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:03.889]
Connection received from 192.168.1.1 on port 3476 [06/05 11:33:04.940]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:04.940]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:04.940]
Connection received from 192.168.1.1 on port 1449 [06/05 11:33:05.975]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:05.975]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:05.975]
Connection received from 192.168.1.1 on port 2494 [06/05 11:33:07.016]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:07.032]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:07.032]
Connection received from 192.168.1.1 on port 3539 [06/05 11:33:08.081]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:08.081]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:08.081]
Connection received from 192.168.1.1 on port 1519 [06/05 11:33:09.122]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:09.122]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:09.122]
Connection received from 192.168.1.1 on port 2564 [06/05 11:33:10.172]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:10.172]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:10.172]
Connection received from 192.168.1.1 on port 3609 [06/05 11:33:11.213]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:11.213]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:14.340]
Connection received from 192.168.1.1 on port 1643 [06/05 11:33:15.390]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:15.390]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:15.390]
Connection received from 192.168.1.1 on port 2687 [06/05 11:33:16.430]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:16.430]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:16.430]
Connection received from 192.168.1.1 on port 3732 [06/05 11:33:17.480]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:17.480]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:17.480]
Connection received from 192.168.1.1 on port 1704 [06/05 11:33:18.531]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:18.531]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:18.531]
Connection received from 192.168.1.1 on port 2748 [06/05 11:33:19.572]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:19.572]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:19.572]
Connection received from 192.168.1.1 on port 3793 [06/05 11:33:20.606]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:20.621]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:20.621]
Connection received from 192.168.1.1 on port 1766 [06/05 11:33:21.663]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:21.663]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:21.663]
Connection received from 192.168.1.1 on port 2811 [06/05 11:33:22.699]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:22.699]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:22.699]
Connection received from 192.168.1.1 on port 3856 [06/05 11:33:23.755]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:23.755]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:23.755]
Connection received from 192.168.1.1 on port 1828 [06/05 11:33:24.790]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:24.790]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:24.790]
Connection received from 192.168.1.1 on port 2873 [06/05 11:33:25.840]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:25.840]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:25.840]
Connection received from 192.168.1.1 on port 3918 [06/05 11:33:26.882]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:26.882]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:26.882]
Connection received from 192.168.1.1 on port 1891 [06/05 11:33:27.933]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:27.933]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:27.933]
Connection received from 192.168.1.1 on port 2936 [06/05 11:33:28.973]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:28.973]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:28.973]
Connection received from 192.168.1.1 on port 3980 [06/05 11:33:30.023]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:30.023]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:30.023]
Connection received from 192.168.1.1 on port 1953 [06/05 11:33:31.058]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:31.058]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:31.058]
Connection received from 192.168.1.1 on port 2998 [06/05 11:33:32.115]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:32.115]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:32.115]
Connection received from 192.168.1.1 on port 4043 [06/05 11:33:33.150]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:33.150]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:33.150]
Connection received from 192.168.1.1 on port 2016 [06/05 11:33:34.207]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:34.207]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:34.207]
Connection received from 192.168.1.1 on port 3060 [06/05 11:33:35.243]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:35.243]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:35.243]
Connection received from 192.168.1.1 on port 1033 [06/05 11:33:36.294]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:36.294]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:36.294]
Connection received from 192.168.1.1 on port 2078 [06/05 11:33:37.335]
Read request for file <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb>. Mode octet [06/05 11:33:37.335]
File <openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb> : error 2 in system call CreateFile The system cannot find the file specified. [06/05 11:33:37.335]```

WebUI times out after some time, SSH connection as well.

[konus]

Yes you need to set your PC to 192.168.1.254 It looks like it is requesting the file 'openwrt-mediatek-filogic-cudy_wr3000p-v1-ubootmod-initramfs-recovery.itb' but can't access the tftp server. You may have to temporarily disable the firewall on your system to allow tftp traffic.

I have no experience with tftpd64.exe but you need to make sure the file is in the correct location. Not sure what it defaults to?

[frollic]

@konus

but can't access the tftp server

it can, or those entries wouldn't be in the tftpd64 log, only the file's missing.
transfer could still fail due to firewall though.

@konus

you need to make sure the file is in the correct location. Not sure what it defaults to?

same folder as the tftpd64.exe