Archer C7 router seems bricked after force flashing wrong firmware

Hi,

I accidently force-flashed the wrong OpenWRT firmware (openwrt-22.03.5-ath79-generic-tplink_tl-wr1043nd-v2-squashfs-sysupgrade.bin) to my TP-Link Archer C7 V2 (Ziggo branded) router and now I am not able to SSH back into after flashing the following .bins using TFTP:

  • C7 V2 latest firmware from TP-Link
  • C7 V2 firmware that presumably was stripped
  • C7 V2 OpenWRT factory firmware
  • Stripped C7 V2 OpenWRT firmware
  • C7 V2 stock firmware (ISP/Ziggo branded)

TFTP seems to work fine:

Connection received from 192.168.0.86 on port 3398 [10/07 09:21:40.740]
Read request for file <ArcherC7v2_tp_recovery.bin>. Mode octet [10/07 09:21:40.740]
OACK: <timeout=3,> [10/07 09:21:40.740]
Using local port 55318 [10/07 09:21:40.740]
<ArcherC7v2_tp_recovery.bin>: sent 32002 blks, 16384512 bytes in 2 s. 0 blk resent [10/07 09:21:42.833]

Front lights of the device do not seem to change. LEDs on the back of the device seem to blink differently for some firmware versions, but all end up with a static LED. After that, I cannot SSH back into the device or ping it at 192.168.0.1 or 192.168.1.1.

Am I out of luck and did I just completely brick my device? Or is there something I am missing when flashing the firmware? I do not have access to a serial adapter.

Any suggestions or help is greatly appreciated!

You're probably going to need this in order to figure out what is happening. It is possible that the device is damaged, but you need to know what the boot loader is saying.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.