Looking on the instructions on how to load the Firmware, and reading everything I found regarding to this Router on the Forum, I understand I should load this LEDE firmware directly on the TP-Link GUI.
Unfortunately, when I I try to load it that way, I receive an error:
Thanks for your reply.
I tried to find the TFTP mode with the WPS button pressed while powering the router, as on other TP-LINKs.
At the same time, I had a WireShark monitoring on LAN1 (also tried LAN4).
I couldn't find any packet from the Router until I release the button, in which case I see the normal packets when the Router starts.
In other words, I couldn't see any ARP request from any IP or any TFTP packet at all.
I have tried the LEDE firmware with my Archer C5 v2 (Japan model, but I think the hardware is the same as elsewhere).
I have tested with the following stock firmwares (for Japan model):
3.17.1 Build 20170313 Rel.49237
3.17.1 Build 20160824 Rel.52902
3.17.1 Build 20160524 Rel.69003
With the Web console, I got the same -25533 error code.
The TFTP method itself worked, but the firmware seems to be rejected.
Connect PC to one of the LAN ports.
Set PC's IP to 192.168.0.66/24.
Set up a tftp server, rename the LEDE firmware to "ArcherC5v2_tp_recovery.bin" and put it on the root of the server.
Turn on the router with WPS/Reset button hold, until the WPS LED stop blinking and keep on.
The log shows that there is a read request for file "ArcherC5v2_tp_recovery.bin" from 192.168.0.86.
Though the LEDE firmware was successfully transferred to the router, after rebooting it was still in previous stock firmware.
I have also tried with stock firmwares. They were accepted through this method, and got installed successfully. I can use the TFTP method to both upgrade and downgrade.
After the LEDE firmware transferred, the router reboots itself immediately. While after the stock firmwares transferred, the router reboots itself after a few seconds (flashing?).
So the TFTP method itself should work. Perhaps we need to make a firmware that can be accepted by the router (then we may not encounter the -25533 error with the web console though).
I haven't tried the FAQ-1482 method mentioned by @Klingon. It seems that method requires the router to get bricked first, which seems risky for me.
Thanks @ssnake. I could make my unit go into TFTP, but I'll give it a new try in the following days.
I agree that the hardware for the Japan/EU/US model is probably the same, but the firmware seems to be different.
I tried loading a TP-LINK from a different region to my US router and I received the same error.
"A same error loading a firmware from a different region" is a great hint. It predicts that the router may have checked something (may be the header as with the US model of Archer C7 v2) of the coming firmwares and reject those are not fit for it. We may need to include a proper region code in the header to make the firmware accepted by the router.
@ssnake, thats exactly what I was thinking. Probably I wasn't able to make myself clear about it.
Unfortunately, I don't have the neccesary knowledge to help with this.
What would the way to check what's the necessary header that should be included?
@ssnake If you are interested in doing some tests and can supply product_ver also, I will try to patch the source code.
Same thing for you @guidoa, if you supply me both product_ver and special_id, I will try to patch it and test it with your help. After the patch it should load right from the stock firmware Web interface.
I'm going to make the patch and build the firmware, so if you could just load the bin file using the stock firmware interface, that would be it. I'll let you know when the firmware is available, it will take a while to build.
@ssnake unless I'm mistaken, your router is JP localized and @guidoa your router is US localized.
A bit of advise: Before you flash this build, ensure that TFTP recovery is working while on stock firmware. It's possible that it's not the latest firmware that works, so flash the latest stock firmware and go backward until the TFTP recovery procedure works. No stripping of the firmware file is required to go back to stock using TFTP recovery.