Posted: Thu Aug 24, 2023 20:18 Post subject: Bricked TP Link Archer C8 v1
Hello!
I believe i bricked a router again
This time TP Link Archer C8 1750 V1.
I did a factory reset.
Flashed Index of /dd-wrtv2/downloads/betas/2023/08-21-2023-r53396/tplink_archer-c8v1/
Router bricked.
3 Green lights sometimes light up continius sometime
Does this router have a TFTP function?
How do I activate it?
How do I recognize if it is in the TFTP mode?
Which IP does the router have in TFTP mode?
----
Is there an alternative solution to debrick?
Changed my PC IP address to 192.168.0.66 and renamed the firmware to ArcherC8v1_tp_recovery.bin and started TFTP server.
Powered off the router then waited a good 10 seconds and while holding the reset button pressed I powered it on.
After uploading it to the router it took a while to reboot but then I was able to load the TP-Link admin page and configure it.
_________________ "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
TP-Link Router Webside GUi-> factory resett
then i flashed dd-wrt via Gui
After the flash no wlan and ethernet was just trying to make a connection but failed.
- Windows says network is beeing identified
- unidentified network
- no network cable
and repeat
TFTP64 is running
Log File
Connection received from 192.168.0.86 on port 1998 [25/08 14:58:30.040]
Read request for file <ArcherC8v1_tp_recovery.bin>. Mode octet [25/08 14:58:30.040]
File <ArcherC8v1_tp_recovery.bin> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [25/08 14:58:30.041]
What firmware should i try to flash?
Archer C8_V1_151125
r44406?
r44467?
should i yolo r53396 again?
Is the router fail safe or can I kill the TFTP funktion and finally brick device?
The file "ArcherC8v1_tp_recovery.bin" should be in the root directory of the TFTPD server (folder listed next to the Browse button ...). It's always best to use the stock firmware file renamed to "ArcherC8v1_tp_recovery.bin"... _________________ "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 was optimistic but after resetting my IP in WIndows and the wifi Router creating no wifi.
TFTP64 log
File <rftest> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [25/08 17:16:29.566]
Connection received from 192.168.0.1 on port 45445 [25/08 17:16:29.603]
Read request for file <rftest>. Mode octet [25/08 17:16:29.603]
Thats not a good sgin isn't it?
Should I try if flashing the Archer C8(UN)_V1_160517 FW?
EDIT:
DHCP works
DNS works
ping Router works
wifi not working
switch funktion working
Router gui notworking
In TFTP recovery mode, the router IP address will be 192.168.0.86 and your PC should have a static IP of 192.168.0.66. The log says 192.168.0.1, which seems suspect, but that is the default IP of the router to access webUI. I can only guess this thread is going to turn into pages and pages of "troubleshooting".... _________________ "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
Flash was succesful (officially)
then i tried to reset Lad Adapter IP
then i recognized Wlan not working
then i watched this File <rftest> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [25/08 17:16:29.566]
Connection received from 192.168.0.1 on port 45445 [25/08 17:16:29.603]
Read request for file <rftest>. Mode octet [25/08 17:16:29.603]
I am not sure why there is no wifi from the device and why i cannot visit Gui of TP-Link OG webside.
I tried again with the newer FW.
Now its working with OG TP-Link FW
So which FW can I try to get DD_WRT Working?
Should I downgrade the TP-Link OG FW to an older version?
Note: the TFTP flashing process requires that the product hardware id and version in the new image header match those in the existing image in flash, otherwise the new image is rejected, flashing is cancelled and the bootloader proceeds to boot the old image.
Try an error with webflash dd-wrt it is i guess
Edit
From newest OG FW webflash 44715 works
Gui looks broken on firefox; on edge fine
But we still don't know where current releases have broken for this device and 44715 has several known vulnerabilities and is nearly 3 years old. Optimal situation would be to flash incrementally or flash current release with serial USB TTL UART adapter attached and serial console being logged and find what broke. This is not an ideal solution to flash what works and not contribute.
Also, TP-Link FW does have a point at which it locks out downgrading and 3rd party firmware flashing, generally speaking. _________________ "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
For me this Version would probably 44715 enough (cheap Wlan Repeater)
My experience with Putty and flashing ESP32 ESP8266 is limited.
I have a CP2102 Adapter.
What would I need to do to help?
Tear down Router look for RX TX
Flash back to OG FW
Start and connect Putty
Flash current DD-WRT Version via Webflash
Copy an publish contend from putty consol
From the Voltage to Ground
Antenna Up
leftest pin GND 3,3v
snd left pin GND 0,0v + Ohm 0 -> Ground pin
3rd left pin GND 0,0v no connection to Ground
right pin GND 3,3v
left to right 0,0v
I guess left an right are RX and TX
my multi meter is not able to measure ohm so I have to guess RX an TX.
Joined: 08 May 2018 Posts: 16917 Location: Texas, USA
Posted: Sun Aug 27, 2023 11:22 Post subject:
You'll have to ensure that no pins are missing components on the PCB. TP-Link has a bad habit of leaving components off so you cannot connect serial UART to an adapter without bridging solder pads. That definitely does not look the same as the C9 V4 US model that I still need to do a serial dump on.