Posted: Tue Oct 03, 2017 1:50 Post subject: Archer c8 (ac1750) have V3 rev33413 cant go back to stock?
Archer c8 (ac1750) have V3 rev33413 9/27/17 cant go back to tplink stock?
Go easy on me, I am newbie.I have the DDWRT firmware on the Archer c8.It works except some features like keyword blocking,does absolutely nothing.Anyway,I want to go back to stock TPLINK firmware, it says successful then it never works. What can I do to get the factory firmware back on this thing.I do not see revert firmware for the C8. Supposedly it has the Broadcom Chip if that helps.
Posted: Tue Oct 03, 2017 6:07 Post subject: Re: Archer c8 (ac1750) have V3 rev33413 cant go back to stoc
k1nng wrote:
Archer c8 (ac1750) have V3 rev33413 9/27/17 cant go back to tplink stock?
Go easy on me, I am newbie.I have the DDWRT firmware on the Archer c8.It works except some features like keyword blocking,does absolutely nothing.Anyway,I want to go back to stock TPLINK firmware, it says successful then it never works. What can I do to get the factory firmware back on this thing.I do not see revert firmware for the C8. Supposedly it has the Broadcom Chip if that helps.
You can't _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Tue Jul 24, 2018 17:21 Post subject: Re: Any C8 owners answer this question?
k1nng wrote:
Anyone know why the website blocking portion of the
DDWRT does not work on the C8?
Are you sure your router is v3? Cause technically is not supported by dd-wrt...
tplink_archer-c8v1 is the firmware you have applied to your router? I'm curious cause if it works i'll try this at home _________________ How to read manpages and learn!
Sorry for the necrobump here but, has anyone successfully applied v1/v2 firmware on a v3 device?
k1nng does not seems to be an active member neither answers to PM regarding this thread to confirm what steps he/she made to apply dd-wrt on it. _________________ How to read manpages and learn!
OK. Sorry for the necrobumping but, i have to document my findings somewere about trying to force feed dd-wrt Archer C8 v2 firmware on a v3 hardware.
Got myself a Archer C60 and put openwrt on it(sorry guys) cause the 5.0Ghz antena of my Archer C8 was failing(signal very weak). What i've found so far:
- My router uses the last Archer C8(US)_V3_170606 firmware, and i think that this is the issue since tplink started that signed-image anti-feature.
- Whenever i say "dd-wrt firmware" on this topic, i'm refering to ArcherC8_v2 firmware.
- Tried to upload dd-wrt firmware using the default webpage but, couldn't reach it. It just does not load whatever ip i use on my Linux laptop inside 192.168.0.0/24 net(except 192.168.0.1 of course)
- Used the same logic of other devices to enable recovery mode holding reset+wps while powering the device. Set the 192.168.0.66 ip address on my notebook, and after some tcpdump i could notice that the device tried to fetch an image called ArcherC8v3_recovery.bin.
- Tried to rename "factory to ddwrt" and it didn't work. Started tftpd on my laptop and the router fetches the image, and visually it seems that the image is being written but after the reboot, factory image remains untouched.
- Ok, lets try an older factory firmware version like Archer C8(US)_V3_160804. Same tftp procedure, same flashing behavior with no results on downgrading the firmware. I was hoping that i could at least downgrade to put dd-wrt but seems it's not possible.
Since this is a spare router, I can do any testing you want with it. Just ping me on this topic if you have any ideas on what could i do.
Joined: 08 May 2018 Posts: 12614 Location: Texas, USA
Posted: Mon Jul 20, 2020 18:11 Post subject:
You most likely have to do some magic voodoo via serial and hexedit of the factory-to-ddwrt image. I don't have the device in hand to come up with the correct method of conjuring this up.
EDIT 05.17.21:
This device has only been officially supported since r45820: