Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sat Aug 27, 2022 12:06 Post subject:
Information about builds can be found in the build threads, that is the place people are (or should) reporting about the builds and thus where you can find information about builds.
See the forum guidelines with helpful pointers about how to research your router, where and what firmware to download, where and how to post and many other helpful tips:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
New Build - 08/25/2021 - r47256 (Don't use if you want access restrictions working) _________________ "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
ok whom ever need it after dozens of firmware hours of going back and forward here it is how ive done
first ive wrote after stuck tpling
44715 then 45219 then 48068 then 49866 as latest.
at the end its works again in pretty good shape for few days already.
hope be usefull for someone else.
thnx
I also have a C9 V2, just to give my 5c to this thread, starting from the r47528 (see my post on https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=330444&highlight=) any factory reset bricks the router, it doesn't matter if you have done or not any update before, the simple reset using the UI produces the brick, also updating without restarting first, also bricks the router, I have seen other users reporting this second issue (ex: C9 V1 @dwardo).
Last year when I found this issue, I reported it on Trac, but never got any answer, maybe I filled the ticket incorrectly...
I have been updating regularly (always restarting before update) and everything is OK.
ok whom ever need it after dozens of firmware hours of going back and forward here it is how ive done
first ive wrote after stuck tpling
44715 then 45219 then 48068 then 49866 as latest.
at the end its works again in pretty good shape for few days already.
hope be usefull for someone else.
thnx
Thanks for this info! You saved me! And this thread has been very helpful to un-boot-looping my C9 v1.0.
My C9 v1.0 ran stably on 45219 for over a year (I use it for WiFi and for OpenVpn client), all when bad when I decided to updated it to play around with WireGaurd tunnels. Long story short, I tried a few versions after 45219 (including 48068 then 49866, and some newer ones Feb 28, 2023 and Mar 28, 2023) and all seem to have the boot-looping issue.
I'd like to share how I get my C9 v1.0 out of the boot loop, and back working again with 45219:
1. I used OpenTFTPServer from Sourceforge, ran it stand-alone config'd it to listen on 192.168.0.66:69
and successfully TFTP'ed ArcherC9v1_tp_recovery.bin (from tplink us website, renamed archer_c9v1_us-up-ver3-17-0-P1[20161008-rel64225].bin).
2. IMPORTANT: After the above successful TFTP flash, it it seemed to still boot-loop, and WireShark told me it was asking to receive via TFTP a filed called "rftest" (what the heck is that??), I got past that by creating a blank .txt file and renamed it to rftest, and the C9 happily accepted it from my TFTP server, it rebooted and presented it's factory TP-link web interface at 192.168.0.1.
**Why does it want rftest from TFTP??** (regardless of why, I got past that loop)
3. From the the factory web page (archer_c9v1_us-up-ver3-17-0-P1[20161008-rel64225]) I upgraded firmware to dd-wrt using v3.0 Build 44715 (using factory-to-ddwrt.bin file), and after reboot I successfully reached the dd-wrt web login and password change page.
4. From dd-wrt 44715, I updated firmware to dd-wrt 45219, rebooted, and restored my config bin file (saved before all this mess!)
Done, all back to normal working again.
Does anyone have a C9 v1.0 successfully running any newer dd-wrt from 2022 or 2023?
Anyone got the LED's working, and how?
I have the v1 Hardware. Other than a boot loop a few years ago on a bad firmware, from which I had to unbrick via the serial interface I havé not had an real issues upgrading. I generally update once or twice a year.
I have the v1 Hardware. Other than a boot loop a few years ago on a bad firmware, from which I had to unbrick via the serial interface I havé not had an real issues upgrading. I generally update once or twice a year.
Okay great thanks! Mine is a v1.0, I might try the same version you're on now r53112.
And I'm wondering if using what I posted above, serving up a blank rftest file via TFTP, for getting out'a the bootloop, would work instead of serial connection if I end up in a boot loop with any versions newer than what mine is on.