We need more details and logs - serial logs would be the most beneficial to see what breaks, if anything at all. We must rule out user error. _________________ "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
You should try dirty flashing them to upgrade without ever resetting or NVRAM-erasing them for anything newer than r47528.
C8 user lupin3rd reported two years ago that the issue was the "Shortcut Forwarding Engine" found under: Setup -> Basic Setup -> WAN Setup -> Optional settings gets reset to default CTF "enabled" which results in a bootloop.
Be aware that if you ever have to reset or NVRAM-erase this device that recovery and reflash will be required, at least until this default setting ever gets changed. This is probably one of those things that should at least be added to the wiki, but it's just a hazard of running such an unpopular device on DD-WRT.
If you're going to reference something, at least link it so there is a hard connection instead of making people search for the thread, please. And this thread seems a continuation of the referenced thread in some respects, anyway.
Did anyone ever respond to hugosboss' query about acquiring the C8 v1 that was bricked? It would be indeed helpful if people would figure out serial access and provide information to fix whatever problem may exist. It should be noted that the CTF module's most recent public update is 56030, so anything newer than that must be vetted on this device and logs provided. _________________ "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
no details:
-about what you actually do when flashing...
-which file
-what browser and ect...
-any steps to reproduce
-any logs ??
-router version?
-did you do a google search
https://wiki.dd-wrt.com/wiki/index.php/TP_Link_Archer_C8
I do the 192.168.0.66 TFTP method, the famous TP-Link method. So it works for the said version. But not any other. I do this on windows. It's Archer C8 v1.
I'll try what you said Dale.
Okay I did it, thanks to you guys. this is how I did it: First I flashed 44715 factory to ddwrt bin file. I had to rename it ArcherC8V1_recovery.bin or something like that. It's neccessary. Then the TP-Link famous 192.168.0.66 TFTP method via tftpd32 program. Then, from dd wrt first flash to 47528 dd wrt version. Without using resetting anything before or after, like you said. Then from there, flash 55819 dd wrt. Then I flashed the latest one, released in 8 june. After flashing dd wrt I always used webflash images. factory to dd wrt images didn't get accepted anyway from ddwrt.
In other words, you finally realized that using the webflash file from the DD-WRT webUI is the correct way to upgrade as it's always been. _________________ "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
In other words, you finally realized that using the webflash file from the DD-WRT webUI is the correct way to upgrade as it's always been.
I think you got me wrong. When I uploaded dd wrt 2024 latest firmware from stock, with factory-to-ddwrt image, it would boot loop. I only got it working when I did 44715 first, then 45756, then the latest dd wrt.
Joined: 08 May 2018 Posts: 15528 Location: Texas, USA
Posted: Sun Jun 09, 2024 23:55 Post subject:
The device wiki still needs some finessing to show initial flash build recommendation, etc. Thanks for not giving any serial logs so we know what is wrong with current factory-to-ddwrt.bin files If anything). Just keep in mind, general rule of thumb for most supported-at-the-time (Broadcom) devices, 33772 is the initial flash file recommended to avoid most issues. Thanks for the feedback, albeit lacking pertinent information to help the developer fix anything.
