I spoke with TP-Link. And the Archer C7 v2.0 has the "only" TP-Link firmware released for it.

Here's the version information:
-Firmware Version: 3.14.3 Build 151014 Rel.49676n
-Hardware Version: Archer C7 v2 00000000

I get this error message:
Error code: 18005
Upgrade unsuccessfully because the version of the upgraded file was incorrect. Please check the file name.

This is the name of the firmware on my harddrive. I sha256sum it and it is correct.:
openwrt-15.05-ar71xx-generic-archer-c7-v2-squashfs-factory.bin

(Last edited by Lou-ltef on 3 Mar 2016, 01:53)

Hi,

Please see this post:

https://forum.openwrt.org/viewtopic.php … 70#p312170

and the whole thread it's a part of.  It may help explain the likely cause of the 18005 error.

Clemmitt

Thanks for this.

Can you confirm I understand the post correctly?

1) I will flash the tp-link firmware to ddwrt firmware
2) then I flash the ddwrt firmware back to an older version of the tp-link firmware
3) then I flash openwrt

Anybody know if the openwrt developers plan to address this issue somehow within openwrt?

@Lou-ltef Can you supply information that's on the box so that we can tell the difference between an old, upgradable one, and one of these newer versions?

- Model/Version number
- UPC Bar code
- Other bar codes/numbers
- FCC Registration number
- etc

Thanks.

Would you be so kind as to begin here and not here?

Thanking you in advance.

Watch out, everyone!!!  The Forum Policeman has arrived!!!    Cheeze it!!!

Seriously, man? Really?

FYI, I did search the forum before posting and found some threads similar but they did not resolve the issue. The link I got from my new post was spot-on however. And the Title of the spot-on post:  "TP-Link confirms Wifi freedom is dead" is far from immediately clear it relates to Error 18005 or the problem I was facing.

So would you be so kind as to refrain from posts like this. Thank you.

# model
TP-Link Archer C7 v2.0 (AC1750)

# UPC Code
845-973-070-601

# P/N
1750502104

# FCC Registration number
where do I find this?

@richbhanover: I think the important thing is the hardware version you get, as I posted earlier. As long as your hardware version is 2.0 (and not 3.0), you can flash to dd-wrt, revert to old TP-Link firmware, and then go to openwrt.

TP-Link is the only manu I buy, because they've always been so good with openwrt. If the company is changing its ways, I'll be dumping them. I used to buy NetGear, but I couldn't get them to flash openwrt, and I haven't bought anything NetGear since.

The first reference to the TP-Link 18005 error code and the dd-wrt solution is here, posted some 43 days earlier. What does this say about the research effort applied?

A feeble attempt to keep the time bandits in check.

Come on people this thread reads like one from the ddwrt forums. Make love not war!

'Twas why I attempted to inject some humor and send a gentle message.  But, honestly, I don't expect that forum member to change their ways, not even a little

Clemmitt

@Lou-Itef - thanks for the info about what's printed on the box

@all - See the recent topic that purports to have a clean procedure for re-flashing TP-Link at https://forum.openwrt.org/viewtopic.php?id=63123

Correct. And nor you, yours.

@cmsigler - What is another term for two people on a bicycle ride?

Is it "Max Hopper?"

Nope.

Tandem?

Ths is how you fix it: https://www.gargoyle-router.com/phpbb/v … 210#p35053

1. Flash DD-WRT 3rd party firmware (passes firmware header check)
2. Revert to older version of TP-LINK firmware (w/o firmware header check)
3. Flash image of your choice (OpenWRT / LEDE / Gargoyle / etc)

I just updated my tp-link archer c7 v2 (serial starting with 217, so it has the newer chip that everything should be patched for now) to Lede without having to do the ddwrt/openwrt step first:

1. got ArcherC7v2_en_3_14_3_up(150427).bin from zippyshare (linked on a gargoyle forum page about the 18005 error)
2. flashed that via the tplink UI, which is an old firmware from tplink (150427) that validly flashes from even the current tp-link firmware (170525)
3. flashed Lede 17.01.2 ar71xx from the older firmware tp-link UI

network addresses change between the 0 subnet and 1 subnet for tplink/lede, but once Lede came up, it worked.
This forum wont let me post links, or anything it thinks is a link, so can't really post more details.