Posted: Mon Jan 25, 2021 2:24 Post subject: TPlink Archer C7 v5 beta firmware invalid file
Hello all, I own a tplink archer v5 Canadian version which works with US firmware no problem. When I go to the web interface to upgrade firmware to ddwrt it will not work saying invalid file. I'm afraid if I do tftp upgrade it will brick it. What should I do?
Posted: Mon Jan 25, 2021 13:23 Post subject: TP-Link firmware
If the router is currently running TP-Link firmware. Use the factory-to-ddwrt file in that folder. Then upgrade using the other file once the router is running DD-WRT.
If the factory-to-ddwrt file still causes the same error, you have to setup a TFTP server and do it the hard way. I can provide more info on the process but try via the GUI first. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
I have tried both with many other versions and still doesn't work. I am willing to do tftp, I'm currently on windows but if its easier on linux I'm willing to go back using linux on another drive.
Posted: Mon Jan 25, 2021 14:17 Post subject: TFTP Server
TFTP32
Create a folder C:/tftp
Put the factory-to-ddwrt file in there. Rename file to ArcherC7v3_tp_recovery.bin with another copy for ArcherC7v2_tp_recovery.bin and ArcherC7v5_tp_recovery.bin
Set the Network card (ethernet wired) on your PC to 192.168.0.66, subnet 255.255.255.0
Turn off any and all firewalls.
TFTP32 - Server tab. Select the folder created above.
Router - (from the wiki you linked to) To activate TFTP Recovery press and hold WPS/Reset Button during powering on until WPS LED turns on.
If this still fails, then like the OpenWRT wiki mentions, TPLINK_HWREV and TPLINK_HWID might be 0xffffffff or blank. The bootloader would reject the TFTPed firmware and refuse to flash it. This can be bypassed by modifying the firmware to be flashed at the appropriate locations (using HxD). If you don't know what I mean, then I can do it. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
I don't think I have wps led, I'm assuming it would be wifi since I've done that before it would turn on or off the wifi leds. Alright I'll do this later today or tomorrow and let you know. Whenever the family stops using wifi
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Mon Jan 25, 2021 15:38 Post subject:
If you are having issues updating via gui, TFTP is likely not going to work either.
I would not attempt it because I have a feeling you're going to end up with a brick and then need help recovering too...
My suspicion is that in Canada something must have recently changed at TP-Link. I believe they use a world-wide firmware file from TP-Link, though the C7v5 only has one file to use for dd-wrt... So I am not 100% sure what TP-Link really does do and if they make a regional firmware or not on this version.
For some of their other routers, they do indeed use different regional files and the one's for the USA, and, newer than 2018 can be flaky due to the FCC rules saying they don't want the USA messing around with the radio settings... There was a recent BCM C9v1 router made by TP-Link that had issues with this when someone installed a USA version on an EU piece of hardware. Go read that for what I think might be also affecting you... None of those files will apply to you...TL:DR is not an excuse if you brick your device applying bad files...
My advice is to find the oldest stock firmware file and load it and then try to use the factory-to-ddwrt file. If that doesn't work, you're going to have to ask TP-Link for a special file to un-region-lock your device since you may have installed the wrong regional file on your hardware. _________________ FORUM RULES
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Mon Jan 25, 2021 15:51 Post subject:
Also, you should be using 2020's 44715 as the most stable build for the time being. 45563 is a lot better than other recent builds, but there are still 2.4ghz bugs present for legacy clients and 44715 is using an older, more stable, wifi driver and should be used. _________________ FORUM RULES
Joined: 21 Jan 2017 Posts: 1782 Location: Illinois Moderator
Posted: Tue Jan 26, 2021 17:33 Post subject:
This is bad news if TP-Link is starting to lock down all their hardware...hopefully it won't turn into a EA8500 situation.... I guess all good things must come to an end....
I've added a warning on the main TP-Link Wiki side.
BUT TL:DR will come to haunt someone guaranteed! _________________ FORUM RULES
You'll need to copy and paste that whole link as the last bit gets cut off by the forum software.
Then try to update using the downgraded stock gui and the facotry-to-dd-wrt file using build 44715.
If you still can't, that means that TP-link has locked down the firmware and you need to invest in a USB-to-serial adapter and get ready for some "hacking." _________________ FORUM RULES
If you are having issues updating via gui, TFTP is likely not going to work either.
I would not attempt it because I have a feeling you're going to end up with a brick and then need help recovering too...
My suspicion is that in Canada something must have recently changed at TP-Link. I believe they use a world-wide firmware file from TP-Link, though the C7v5 only has one file to use for dd-wrt... So I am not 100% sure what TP-Link really does do and if they make a regional firmware or not on this version.
For some of their other routers, they do indeed use different regional files and the one's for the USA, and, newer than 2018 can be flaky due to the FCC rules saying they don't want the USA messing around with the radio settings... There was a recent BCM C9v1 router made by TP-Link that had issues with this when someone installed a USA version on an EU piece of hardware. Go read that for what I think might be also affecting you... None of those files will apply to you...TL:DR is not an excuse if you brick your device applying bad files...
My advice is to find the oldest stock firmware file and load it and then try to use the factory-to-ddwrt file. If that doesn't work, you're going to have to ask TP-Link for a special file to un-region-lock your device since you may have installed the wrong regional file on your hardware.
Yes I had a feeling if Web wouldn't work tftp wouldn't work either. I've noticed they changed as there used to be older versions available and been using US versions until they only had 3 versions available one being older US version and 2 Canadian. At that time I had problems with wifi and some settings that wouldn't disable. I'll ask them about that.