Posted: Thu Dec 07, 2017 7:43 Post subject: Archer C9 V1
Hello gents,
I have a very strange situation.
I have a Archer C9V1 (EU) and a tried to install the last version (beta) of ddwrt.(12-04-2017-r33986)
I install successfully this file: factory-to-ddwrt.bin. After this step when I tried to install the second bin file archer-c9v1-webflash.bin this hasn't been possible. I have to admit that I forgot to make a hard reset (30-30-30) of the router before to start to install the ddwrt firmware.
At this moment the router is working fine but the wan led is all the time orange and when I tried to make a repeater bridge for both frequencies(2.4 and 5 GHz) connection the router freeze. Is working fine with one wifi band (2.4)
I suppose that the router is not bricked since most of the function are active, but since the second bin file wasn't installed I think the firmware is not installed.
Any advice ?
Thank you in advance.
Happened to me as well, AFTER a successful implementation of factory-to-ddwrt. I tried to update to the latest build, now I'm bricked on a WPS light and I don't know what to do.
Happened to me as well, AFTER a successful implementation of factory-to-ddwrt. I tried to update to the latest build, now I'm bricked on a WPS light and I don't know what to do.
Happened to me as well, AFTER a successful implementation of factory-to-ddwrt. I tried to update to the latest build, now I'm bricked on a WPS light and I don't know what to do.
SAME HERE
Same. Nothing works when I try. I am able to upload a bin file using Tftpd, but when I check 192.168.0.1 I get the recovery page. Tried to upload everything US official fw, EU offical fw, dd-wrt fw, even D9's fw... nothing...
Also, that damn recovery page always fails at 40% on Edge. On Chrome it fails right away...
Bricked my Archer c9 v3, successfully installed dd-wrt via factory to dd-wrt but attempting to upgrade to the latest version, it just sits with the WPS light turned on. The recovery page at 192.168.0.1 fails at 40% with the official TP-Link firmaware and dd-wrt.
Someone please find a way to bring back the v3's from this bricking via the web interface. I don't have a serial port connection.
Posted: Tue Apr 17, 2018 10:00 Post subject: dd-wrt to stock
Can someone tell me what steps i have to do to revert my c9v4 to stock tp link firmware, please?
router: archer c9 v4
actual firmware: : DD-WRT v3.0-r35452 std (03/20/1
The router it is not bricked, but after i read many posts i'm scared, so, i need your help. Thank you
Posted: Tue May 01, 2018 13:48 Post subject: Re: dd-wrt to stock
gabirizescu wrote:
Can someone tell me what steps i have to do to revert my c9v4 to stock tp link firmware, please?
router: archer c9 v4
actual firmware: : DD-WRT v3.0-r35452 std (03/20/1
The router it is not bricked, but after i read many posts i'm scared, so, i need your help. Thank you
I hope someone can help me. I'm fairly new to installing dd wrt with the new routers. I have done it previously 4 years ago, quite easily with a DLINK DIR 615 but the other day, I bought a used Archer C9 v1 with 3.15.27 Build 20141013 Rel.53520n installed.
I followed all the instructions regarding hard reset, except that I did not upgrade the stock firmware before installing the factory-to-ddwrt.bin file. I used the file from /dd-wrtv2/downloads/betas/2018/05-13-2018-r35927/
The upload to the router went ok but after it restarted, the router went into a boot loop, all lights on for a few seconds, then all lights off.
I tried the TFTP method described here, and although it grabs the renamed firmware from the TFTP server, it still doesn't fix the boot loop problem. I have tried with the oldest firmware I can find from the official TP LINK site but the oldest downloadable file is newer than the firmware that came with the router. I have also tried using old factory-to-ddwrt.bin files from 2015 and 2016 but with no success.
I want to try with the oldorgArcherC9v1_tp_recovery.bin file that can be downloaded from the Polish TPLINK forum but the link doesn't seem to work.
I also want to try the solution provided by @chrisdmc but I don't have access to the dd wrt Webgui.
So now, I want to try the USB to TTL solution, unless somebody can suggest another solution, by using the document TP-Link Archer C9 v1 - Unbrick and back to stock step-by-step guide.pdf Is the solution still current?
Any help will be greatly appreciated! Thanks a lot!
Posted: Wed May 23, 2018 16:34 Post subject: Archer C9 V2 problem
Hello,
Sorry, I haven't enough time for searching.
I get an Archer C9 V2 with DD-WRT, I need to restore the original tp-link fw. I erased the NVRAM and tried the TFTP process, but after a successfully download, nothing happen. I don't know, which is the version of the previous original firmware. I not want to open the case, because the device under warranty. Probably erased the partition which need to restore. Is it possible to restore this partition from working DD-wrt? How?
Thank You!
I finally just decided to open my router and used the method described in TP-Link Archer C9 v1 - Unbrick and back to stock step-by-step guide.pdf and https://www.youtube.com/watch?v=fme7kwTkttk&t=982s and was able unbrick my router. I then was able to install the stock firmware again.
However, when I tried again to install dd wrt using any firmware, it bricked my router again. So, at my next attempt, after unbricking my router, I didn't bother installing any stock firmware and installed dd wrt firmware r27506 and this time it worked! After this, I upgraded to r33375 which according to some has the most stable openvpn implementation which is what I need the most.
I don't know about security patches, though, if it's the most secure. Anyone else can comment on a newer firmware with a stable openvpn implementation?
Thanks to the guys @Heinzek and @Aboshi and to the guy who wrote the PDF guide. It's still proving to be very useful!
Posted: Fri May 10, 2019 21:09 Post subject: Restore default-mac, pin, product-info etc... in ddwrt
So I had flashed with the early versions of DDWRT and overwritten the following "Factory" partitions:
* default-mac[/list]
* pin
* product-info
* partition-table
* soft-version
* support-list
* profile
* default-config
Given their adresses in the flash, these all end up inside the ddwrt's mdt3 partition (also named "ddwrt")
At boot ddwrt shows its mdt partition table
Code:
bcmsflash: squash filesystem found at block 30
Creating 6 MTD partitions on "bcmsflash":
mtd0 0x000000000000-0x000000040000 : "boot"
mtd1 0x000000040000-0x000000f00000 : "linux"
mtd2 0x0000001e0000-0x000000d30000 : "rootfs" <-- a sub layer partition of mtd1 "linux"
mtd3 0x000000d30000-0x000000f00000 : "ddwrt" <-- a sub layer partition of mtd1 "linux"
mtd4 0x000000ff0000-0x000001000000 : "nvram_cfe"
mtd5 0x000000fe0000-0x000000ff0000 : "nvram"
Now in ddwrt-to-factory.bin here are the adresses of the "Factory" partitions
Code:
01. partition os-image base 0x000000 size 0x200000
02. partition file-system base 0x200000 size 0xc00000
03. partition default-mac base 0xe00000 size 0x000200
04. partition pin base 0xe00200 size 0x000200
05. partition product-info base 0xe00400 size 0x000200
06. partition partition-table base 0xe10000 size 0x010000
07. partition soft-version base 0xe20000 size 0x000200
08. partition support-list base 0xe31000 size 0x00f000
09. partition profile base 0xe40000 size 0x010000
10. partition default-config base 0xe50000 size 0x010000
Instead, as I didn't want to have to hassle with doing that and then reflashing and reconfiguring dwrt I did the folowing :
1) Replaced MAC and PIN (and did not bother with the CRC as I won't be using it in the end... but you can still do it) with mine in ddwr-to-factory.bin using hexedit and saved as ddwr-to-factory_myMAC_myPIN.bin
MAC is at 0xe00000
PIN is at 0xé00200
2) Extracted the appropriate bytes from ddwrt-to-factory_myMAC_myPIN.bin
"ddwrt" (mtd3) data starts at 0xcf0000=hex(0x000000d30000-0x000000040000) in ddwr-to-factory.bin
"ddwrt" (mtd3) data would therefore end at 0xec0000=hex(0x000000f00000-0x000000040000) in ddwr-to-factory.bin.
However ddwr-to-factory contains only 0xe50000 bytes so 0x070000=0xec0000-0xe5000=458752 bytes are missing
So we just extract all bytes starting from adress 0xcf0000=13565952 so starting from byte 13565953