Posted: Wed Jan 31, 2024 18:59 Post subject: Another TP-Link Archer C8 V1 bricked
Hi community,
As I am using DD-WRT for more than 3 years, I thought that this can go that wrong, so I tried to flash my Archer C8 V1 that had 3.16.28 build 20141023 with this version:
Downloads › betas › 2024 › 01-29-2024-r55033 › tplink_archer-c8v1
First I performed a GUI Factory Reset
Then flashed successfully factory-to-ddwrt.bin
After restarting, router entered in a bootloop
Then I connected via Serial and with TFTP opened I flashed OEM firmware Archer C8_V1_150316 using this comand:
Device eth0: hwaddr 30-B5-C2-92-4E-DA, ipaddr 192.168.0.1, mask 255.255.255.0
gateway not set, nameserver not set
Invalid boot block on disk
flash0.0: Device not found
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: Image compressed with unsupported method
Failed.
Could not load flash0.os:: Unsupported function
Than I performed a new flash via TFTP 192.169.0.66 with OEM Archer C8_V1_150515 and the router lost Serial connectivity and when I turn it on, all lights remain on.
The TFTP recovery still works.
Did I bricked it for good or there is anything I can do to recover it?
Support for TP-Link Archer C8 and Huawei E5786 #2 _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
I read all the treads, but they are not helping in my situation.
I have a friend with same C8 v1 and he was able to flash DD-WRT r44715, no problem.
Then he flashed latest release r55033 and the rooter entered bootloop. So definitely r55033 have some problems.
Some updates regarding my bricked Archer C8 v1:
- I am able to upload recovery file via TFTP, but it seems router is not able to run and apply it
- after TFTP te router does not restart and remains with all leds on, having fixed IP 192.168.0.66 I am able to ping router to IP 192.168.0.86
- if I manually restart the router, all leds remains on, router is not in bootloop, and I am able to ping it to IP 192.168.0.1, only if is use static IP on laptop (DHCP doesn't work)
- no web interface available
- no WIFI SSID is available
- no SSH connection
- no telnet connection
- lost SERIAL connectivity
I have a friend who helped me and he was able to take out flash memory chip and write a flash dump.
After that, Serial is working again and router was resurrected.
UPDATE: I was able to flash latest DD-WRT with just renaming the BIN file
I tried first to flash DD-WRT factory r55109 from OEM TP-Link web interface by renaming it to c8v1_un-up-ver4-0-0-P4[20160517-rel44603].bin, but the router end in bootloop.
Then flashed DD-WRT factory r44715 via TFTP and this was a success.
Then flashed DD-WRT webflash r44715 from DD-WRT user web interface.
Then flashed DD-WRT webflash r55109 from DD-WRT user web interface but with bine file renamed to c8v1_un-up-ver4-0-0-P4[20160517-rel44603].bin and this was success.
Some oversights in documentation will be corrected. One of the linked threads in the wiki tells you to 30-30-30 the device, and it being Broadcom ARM and TP-Link, that's an easy way to brick the device into bootloop. Anyhow, we expect more confirmation of your method than blindly approving it because there are many other documented bits in the community that don't seem to require such smoke and mirrors. _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
