I installed OpenWrt on a Archer A9 V6. Eventually figured out 2.4 ghz wasn't supported, so I figured I would roll it back to the OEM software. I downloaded the firmware from tp-link site, went into LuCI and uploaded the .bin. Router reset, now it has become inaccessible. I can plug in an ethernet cord and my pc recognizes it is plugged in. The web interface (still uses the static IP I assigned it in LuCI before it bricked) gets to the first page before the login where it just says " [LuCI - Lua Configuration Interface]) but never loads past that page. The ssh connection times out. When I turn it own the power light goes straight to solid green. I've tried pressing the wps and the reset button the entire time, but nothing seems to kick it into failsafe mode. The lan port lights work when I plug in devices. When I push the reset button, the wps light does come on for a few seconds.
All of TP-links recovery methods don't seem to be working either.
Also, I believe that tp-link sets the default address of many of their devices to 192.168.0.1. Make sure your computer is connected by Ethernet and set to obtain an ip address via dhcp. What happens?
I only assume its still the TP-Link firmware because the landing page that comes before the login page is still loading. I've tried this on both Chrome and Firefox
Sorry, it was late and I was really tired last night. I have tried the TFTP method last night. I could not get a response from the router at all. Most of the guides explaining that method talk about watching the log to make sure a request is being received. As I mentioned holding the reset button doesn't seem to affect the router. So for what ever reason, As far as the second method goes. How do I use CTRL+C on a router with no keyboard? Plug in a keyboard into the usb slot?
If I plug the PC directly I don't receive any gatway address. If I set a static ip of 192.168.0.66 (required by the recovery guides) it doesn't change my ability to get a response from the router.
The TFTP server method mentioned above should be there as it is in the u-boot bootloader, so it should be there for both OpenWrt and OEM firmware. But it requires setting a fixed IP and running the TFTP server on PC, so many steps where mistakes can be made.