bricked Archer C50 possible not fix due to tftp error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

bricked Archer C50 possible not fix due to tftp error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
bricked Archer C50 possible not fix due to tftp error
bricked Archer C50 possible not fix due to tftp error
2022-07-17 02:21:59 - last edited 2022-07-17 07:42:46
Tags: #bricked router
Model: Archer C50  
Hardware Version: V4
Firmware Version:

long story short i've bricked my router I have tried all the fix no of them work and I mean basically all of them even removing the header and keeping the header of the bin file. I was looking at the tfttpd logs and noticed that the port was changing and it was sending it to 192.168.0.2 is this normal or is there a fix to this

 

here are the log files

 

Connection received from 192.168.0.2 on port 2893 [17/07 11:52:46.258]
Read request for file <tp_recovery.bin>. Mode octet [17/07 11:52:46.263]
OACK: <timeout=1,> [17/07 11:52:46.263]
Using local port 50868 [17/07 11:52:46.263]
<tp_recovery.bin>: sent 15488 blks, 7929855 bytes in 7 s. 0 blk resent [17/07 11:52:53.067]
Connection received from 192.168.0.2 on port 2619 [17/07 11:56:33.747]
Read request for file <tp_recovery.bin>. Mode octet [17/07 11:56:33.747]
OACK: <timeout=1,> [17/07 11:56:33.747]
Using local port 50108 [17/07 11:56:33.747]
TIMEOUT waiting for Ack block #2777  [17/07 11:56:36.860]
Connection received from 192.168.0.2 on port 3441 [17/07 11:57:36.285]
Read request for file <tp_recovery.bin>. Mode octet [17/07 11:57:36.286]
OACK: <timeout=1,> [17/07 11:57:36.291]
Using local port 50123 [17/07 11:57:36.291]
TIMEOUT waiting for Ack block #2369  [17/07 11:57:39.377]
Connection received from 192.168.0.2 on port 2422 [17/07 12:03:53.153]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:03:53.153]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:03:53.163]
Connection received from 192.168.0.2 on port 2731 [17/07 12:05:12.058]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:05:12.068]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:05:12.068]
Connection received from 192.168.0.2 on port 1293 [17/07 12:05:15.028]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:05:15.028]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:05:15.028]
Connection received from 192.168.0.2 on port 2206 [17/07 12:05:17.997]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:05:17.997]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:05:17.997]
Connection received from 192.168.0.2 on port 1431 [17/07 12:05:20.957]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:05:20.957]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:05:20.957]
Connection received from 192.168.0.2 on port 3498 [17/07 12:05:23.927]
Read request for file <tp_recovery.bin>. Mode octet [17/07 12:05:23.927]
File <tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [17/07 12:05:23.927]
Message received on an unbound interface (IP 192.168.0.6) [17/07 12:14:20.691]

 

  0      
  0      
#1
Options