Joined: 01 Mar 2012 Posts: 22 Location: Nairobi, KE
Posted: Fri Dec 24, 2021 8:37 Post subject: Recovering a bricked TP-Link Archer C7
Hi,
I accidentally flashed dd-wrt firmware meant for Archer C7v5 into C7v2 thereby bricking the C7v2.
I have done the TFTP recovery as documented and the V2 retrieves the firmware from TFTP, but it still remains bricked - rebooting in a loop.
Is there a way to go around this or this device must now be sent to the bin?
You can find the filename being requested by turning on a TFTP log in TFTPd32 / TFTPd64. It will list the filename the router is looking for.
Make sure to remove the first 20200 bytes of the factory file, using a hex editor (HxD), not required for DD-WRT factory files.
I can edit the file if required.
It is looking for ArcherC7v2_tp_recovery.bin and I have been using the factory file one downloaded from their website. I just renamed it but did not edit to remove the first 20200 bytes.
I'd really appreciate it if you could share the edited file.
Perhaps that is all I need, instead of going the way of the USB to TTL cable.
Thanking you in advance while waiting for the edited file.
Posted: Sat Dec 25, 2021 13:21 Post subject: Factory TP-Link Files
Hello odhiambo,
Merry Christmas.
I have attached 3 files (need to be logged in to see them).
TP-Link releases firmware for US, Global, and Israel.
For some odd reason I decided to do US, Global and Canada. Whatever. I think the global one is also the EU version in this case. It depends on where you purchased the unit. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Joined: 01 Mar 2012 Posts: 22 Location: Nairobi, KE
Posted: Mon Dec 27, 2021 8:11 Post subject: Re: Factory TP-Link Files
ian5142 wrote:
Hello odhiambo,
Merry Christmas.
I have attached 3 files (need to be logged in to see them).
TP-Link releases firmware for US, Global, and Israel.
For some odd reason I decided to do US, Global and Canada. Whatever. I think the global one is also the EU version in this case. It depends on where you purchased the unit.
Hi @ian5142,
Thank you so much for the files. My C7 having been purchased from the US, I used the US version of the firmware you provided. I flushed it via TFTP, but the router still remains bricked. The rebooting loop still happening.
Posted: Mon Dec 27, 2021 13:47 Post subject: TFTP Server
You need to setup a TFTP server on your computer. Set the computer's LAN port address to 192.168.0.66. Make sure TFTP32 is pointing to the correct folder and the correct Network adapter (should say the same IP address as above). You should see the router grab the file from the computer (file transfer dialog pops up).
Then wait, at least 5 min. It takes time for it to flash and sort itself out. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Joined: 01 Mar 2012 Posts: 22 Location: Nairobi, KE
Posted: Tue Dec 28, 2021 7:59 Post subject: Re: TFTP Server
ian5142 wrote:
You need to setup a TFTP server on your computer. Set the computer's LAN port address to 192.168.0.66. Make sure TFTP32 is pointing to the correct folder and the correct Network adapter (should say the same IP address as above). You should see the router grab the file from the computer (file transfer dialog pops up).
Then wait, at least 5 min. It takes time for it to flash and sort itself out.
The router grabs the file, yes. Then I even wait for 30 minutes and it is still in the loop flashing almost all lights on/off. I have now decided to go for the JTAG option. If that fails I just discard the junk.
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Tue Dec 28, 2021 8:48 Post subject: Re: TFTP Server
ian5142 wrote:
You need to setup a TFTP server on your computer. Set the computer's LAN port address to 192.168.0.66. Make sure TFTP32 is pointing to the correct folder and the correct Network adapter (should say the same IP address as above). You should see the router grab the file from the computer (file transfer dialog pops up).
Then wait, at least 5 min. It takes time for it to flash and sort itself out.
Joined: 01 Mar 2012 Posts: 22 Location: Nairobi, KE
Posted: Tue Dec 28, 2021 11:13 Post subject: Re: TFTP Server
kernel-panic69 wrote:
ian5142 wrote:
You need to setup a TFTP server on your computer. Set the computer's LAN port address to 192.168.0.66. Make sure TFTP32 is pointing to the correct folder and the correct Network adapter (should say the same IP address as above). You should see the router grab the file from the computer (file transfer dialog pops up).
Then wait, at least 5 min. It takes time for it to flash and sort itself out.
You're not following the instructions and you are trying to do it over wifi from your screenshot. This device is not that difficult to TFTP.
I am actually following instructions to the letter.
I have two computers at my disposal. One is my laptop and another is a headless Desktop. I have installed TFTPd32 on the Desktop and put the file there. I have connected the C7 via ethernet to the Desktop and the Desktop which is dual-homed had its ethernet IP address set to 192.168.0.66. The WLAN interface on the Desktop is what enables me to connect to it via RDP from my laptop.
So the screenshot I shared is captured from an RDP session to the Desktop. It shows the C7 fetching the file. It does fetch the file successfully. However, it does not change after that as it still exhibits the signs associated with bricking.
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Tue Dec 28, 2021 11:23 Post subject:
Then it's probably a matter of you don't need to strip the bootloader for the C7 because it does not say anywhere in the OpenWRT wiki that it needs to be stripped. Download the appropriate stock firmware for your router and try that. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 01 Mar 2012 Posts: 22 Location: Nairobi, KE
Posted: Tue Dec 28, 2021 11:43 Post subject:
kernel-panic69 wrote:
Then it's probably a matter of you don't need to strip the bootloader for the C7 because it does not say anywhere in the OpenWRT wiki that it needs to be stripped. Download the appropriate stock firmware for your router and try that.
I already tried with the stock firmware and that did not work. @ian5142 was gracious enough to give me a stripped firmware, which is what I have flushed via TFTP, but that still did not un-brick the C7.
And that is why I am thinking the JTAG method is now my only option, no?
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Tue Dec 28, 2021 11:55 Post subject:
All you should have to do is rename the stock firmware file without stripping anything to ArcherC7v2_tp_recovery.bin and put it in TFTP mode with a properly configured TFTP server at 192.168.0.66. I doubt your router now thinks it's a v5....