I have also tested all 4 files from within dd-wrt and none of them work. The next test will have to be done in recovery mode. When I have time later today I will try to TFTP them over in recovery and see if they brick the router or not.
Hi. This is not webrevert file.
This firmware works on recovery mode and system update on factory firmware.
If You have DD-Wrt use this file only on recovery mode.
1. Download firmware from tplink-forum.pl site.
2. Unzip firmware.
3. Rename firmware from oldorgArcherC9v1_tp_recovery.bin to ArcherC9v1_tp_recovery.bin
4. Run TFTP server and share ArcherC9v1_tp_recovery.bin on root directory. How to configure TFTPD server
5. Change TFTP Server IP to 192.168.0.66 on wired interface.
6. Connect TFTP server to LAN port on Archer C9.
7. Press and hold Reset/WPS button on router.
8. Power on router.
9. after 5 sec. release button.
10. wait 120 sec.
goodluck getting back to stock firmware. _________________ Please state what make and model router plus the build number and type of DD-WRT you are using. Screen prints and a network diagram can are also helpful. Before you create a new post, use the search function. Chances are your issue has happened to someone else.
If you've tried to revert to stock via the TFTP method and end up with a unit where the power light flashes slowly (like during a normal boot) then rapidly, I have bad news.
The Archer C9 (and C8 )'s radio and power amplifiers require factory calibration. Normally, this calibration data is stored in NVRAM (see below), but since the NVRAM can be erased by the user it's also automatically backed up to a separate partition on flash ("radio", @ 0x00fe0000-0x00ff0000) and restored if the NVRAM is cleared.
If that partition is lost or corrupt, the system goes into 'RF test' mode: The power light starts flashing rapidly and the unit will hang until a special 'WLTEST' version of wl.ko ('wl_rf.ko') and an 'rftest' program are uploaded via TFTP. The rftest program stores calibrated values in NVRAM and sets bit 0 of the rftestflag NVRAM variable; when the system reboots it reads this flag and creates a new radio partition with the new calibration settings.
Unfortunately, DD-WRT isn't aware of this radio partition, and on some units seems to have chosen that exact region to store its own NVRAM data.
I'm not sure if it's worth trying to use someone else's calibration settings to fill in any missing from your own (it might cause your unit to go out of FCC spec, or even cause hardware damage depending on how competent the RF designer was), but for people brave enough to try Heinzek's link contains an NVRAM dump from stock with all the values for the Archer C9 (rftestflag should be set to 4709 to trigger the firmware to rebuild the radio partition).
Damage to any of the following may also cause issues, since they're contained in the TP-Link partition table but not updated by firmware updates nor properly represented in the MTD partition map:
partition default-mac base 0xe40000 size 0x00200
partition pin base 0xe40200 size 0x00200
partition product-info base 0xe40400 size 0x00200
partition profile base 0xe70000 size 0x10000
partition default-config base 0xe80000 size 0x10000
partition user-config base 0xe90000 size 0x50000
partition log base 0xee0000 size 0x100000
partition radio_bk base 0xfe0000 size 0x10000
partition radio base 0xff0000 size 0x10000
In particular I suspect that if product-info is corrupt it won't be able to restore the radio partition from NVRAM and will be stuck in RF-test mode (if it even gets that far).