TP-Link CPE510 V1.1 bricked, trying to read recovery.bin and vmlinuz during TFTP recovery
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TP-Link CPE510 V1.1 bricked, trying to read recovery.bin and vmlinuz during TFTP recovery
Hello,
after flashing back from openwrt to original firmware the cpe510 became bricked.
i have tryied to recover the original firmware through Tftpd32 but as i can see
the Cpe510 asks for recovery.bin and vmlinuz again and again.
The proccess starts without having to press the reset button.
Same thing happens when i press reset during power up.
The version of the Cpe510 is V1.1.
i have downloaded the original firmware fron Tplink website and vmlinuz from https://openwrt.org/toh/tp-link/cpe210#debricking_a_router_that_is_waiting_for_vmlinuz_that_had_installed_openwrtlede
Bellow you can see the log of the Tftpd32
Connection received from 192.168.0.254 on port 4009 [16/03 09:46:08.656]
Read request for file <recovery.bin>. Mode octet [16/03 09:46:08.656]
OACK: <timeout=5,blksize=512,> [16/03 09:46:08.656]
Using local port 2384 [16/03 09:46:08.656]
<recovery.bin>: sent 9643 blks, 4936747 bytes in 1 s. 0 blk resent [16/03 09:46:09.812]
Connection received from 192.168.0.254 on port 2340 [16/03 09:46:13.125]
Read request for file <vmlinuz>. Mode octet [16/03 09:46:13.125]
OACK: <timeout=5,blksize=512,> [16/03 09:46:13.125]
Using local port 2385 [16/03 09:46:13.125]
<vmlinuz>: sent 2598 blks, 1330140 bytes in 0 s. 0 blk resent [16/03 09:46:13.453]
The copy process trying to start but then a "resent" process starts and the ap reboots.
i have also tryied to connect through ssh to 192.168.0.254/22 but nothing happens.
Can you suggest anything else before doing more complex things like jtag..etc ?
thanks for your time
C.