Posted: Sat Jan 08, 2022 6:34 Post subject: TP-LINK Archer C9 v.1 in bootloop/bricked after dd-wrt updat
I upgraded my TP-LINK Archer C9 v.1 (US version) firmware from dd_wrt build v3.0_r44715 to
/dd-wrtv2/downloads/betas/2022/01-06-2022-r47976/tplink_archer-c9v1/archer-c9v1-webflash.bin.
I thought I was following the peacock thread, but obviously not well enough. On upgrading the firmware it said the update was successful, but after reboot the router has been in a constant boot loop.
I believe it is in a boot loop because the right three blue lights on the router will alternate on for several seconds, then off for several seconds, then on again. My MacOS 10.12 computer network settings will also show the ethernet as connected, then unconnected, then connected again. Pings to 192.168.1.1 router always return "Request timeout", but alternate periods that it returns "Host is down", and periods where it does not return that.
I tried to tftp upload the original tp-link firmware, as instructed in the bricked section of https://wiki.dd-wrt.com/wiki/index.php/TP_Link_Archer_C9 (with tp-link firmware filename set to ArcherC9v1_tp_recovery.bin, and chmod 766 permissions). With tftp server running and computer connected via ethernet, I turn off the router, hold the reset button, turn on the router, continue holding reset button for 5 seconds and then let go of the reset button. However I've never gotten any logs indicating that the router it is actually attempting a tftp upload. I'm not certain how be certain that the computer tftp server is setup correctly.
(I tried setting the computer static IP to 192.168.1.8, 192.168.0.66, and 192.168.1.66. The subnet mask is 255.255.255.0. Router IP address (on the computer) is 192.168.1.1, which is the setting the router last successfully worked at. Computer firewall is turned off.)
I never did a 30/30/30 reset, as that is supposed to be bad for arm hardware.
I did watch that video and use those IP addresses without success. I don't get any tftp log from the router.
Note: I used the tftp server on MacOs 10.12, because my Windows machine has no ethernet port. I think the tftp server settings are correct, but I'm not certain.
I did watch that video and use those IP addresses without success. I don't get any tftp log from the router.
Note: I used the tftp server on MacOs 10.12, because my Windows machine has no ethernet port. I think the tftp server settings are correct, but I'm not certain.
Joined: 08 May 2018 Posts: 13904 Location: Texas, USA
Posted: Sat Jan 08, 2022 12:31 Post subject:
One, two, three, four, five; release. Don't know why the wiki says 2-4 seconds. It's 5 seconds to enable TFTP recovery (or until the tftp server starts uploading the file). You can also try 192.168.1.66, but I doubt you'd need to.
Unfortunately I have not been able to get any sign that the tftp server on the router is active. I tried both 192.168.0.66 and 192.168.1.66 as IP addresses for the computer.
I have the v2 version, and the TFTP recovery never worked for me when it bricks, it uploads the FW sometimes via TFTP but the boot loop persists, the only way I recover it is using serial recovery.
The same happened for me when flashing r48138.
I have sent a serial bootlog to Sebastian. _________________ Kernel panic: Aiee, killing interrupt handler!
Thank you all for your input. I've decided not to attempt a Serial recovery.
On tftp:
@kernel-panic69 I was using the MacOs tftp server, as mentioned in the link you posted. Why is "put filename" known to not work? How else should tftp transfers on MacOs be done?
Should Wireshark be able to indicate whether or not the router is even attempting a tftp transfer?
Joined: 08 May 2018 Posts: 13904 Location: Texas, USA
Posted: Tue Jan 18, 2022 23:13 Post subject:
Because when you put a file, you are using client mode tftp, not server mode tftp. The folder you have to put the firmware image file in, unless you have manipulated the .plist file is /private/tftpboot AFAIK:
My ArcherC9v1 has taught me the following :
1. Always reboot before attempting an upgrade.s Everytime I forget to do it (and router has been up for more than a week usually) I end in a bootloop (I forgot again yesterday when updating to 48218... so had to serial restore to factory/stock...)
2. Recent ddwrt versions don't install from factory... They bootloop (to me the automatic CTF detection is to blame) (I tried again yesterday to see if things had changed)...
I end up doing :
a. install from factory with r46974 which does not bootloop
b. reboot (if activating CTF is not available on first boot which has happened...)
c. manually set CTF to enabled and select CTF+FA (hit apply which reboots)
d. upgrade to more recent versions...
My ArcherC9v1 has taught me the following :
1. Always reboot before attempting an upgrade.s Everytime I forget to do it (and router has been up for more than a week usually) I end in a bootloop (I forgot again yesterday when updating to 48218... so had to serial restore to factory/stock...)
2. Recent ddwrt versions don't install from factory... They bootloop (to me the automatic CTF detection is to blame) (I tried again yesterday to see if things had changed)...
I end up doing :
a. install from factory with r46974 which does not bootloop
b. reboot (if activating CTF is not available on first boot which has happened...)
c. manually set CTF to enabled and select CTF+FA (hit apply which reboots)
d. upgrade to more recent versions...
@dwardo
I also have done a reboot before every upgrade on my v2, but I was doing that as precaution, now with your confirmation, I will do it always.
Also don't do a factory reset after any successful upgrade (images later than 10/2021 bricks the router if reset is made).
My ArcherC9v1 has taught me the following :
...
b. reboot (if activating CTF is not available on first boot which has happened...)
c. manually set CTF to enabled and select CTF+FA (hit apply which reboots)
Is this confirmed that enabling CTF+FA helps? It seems rather random to me.
Yesterday I tried to upgrade 4 times to 3 different recent firmware versions. One of them was confirmed in the built thread to work with the C9v1. (https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1282506) I always ended up in the boot loop.
I'm still on built r40501 from 2019. There seems to be no CTF/FA (even after reboot, WAN DHCP, no QoS). And I assume it's not worth it with about 100 mBit/s. I will try r46974 and start from there. But I wonder if there are any updates regarding the boot loops with the Archer C9(v1).
