Hello guys! I tried the last snapshot on my EAP245 V3, but the firmware is bugged with slow 5GHz speeds, so I tried to revert to original firmware from Tplink using uploading via Luci GUI with -f option.
Now my EAP245 are bricked but I get the green light, but I can't get acess. I don't have a computer for now, only my S9+ with a hub and using a RJ45 cable.
Any ideas on how to reverse this without using a serial port? Thanks in advance!
If you flashed TP-Link's firmware image as is, you've got a soft-brick now. Their firmware image uses a custom format, and cannot be written directly to flash (which is what sysupgrade does). You would need to build tplink-safeloader from the OpenWrt sources to convert a TP-Link firmware file into a valid OpenWrt firmware file.
I'm not entirely sure anymore, but I think this device will launch a failsafe web server at the default address (192.168.1.1) if it fails to boot. This failsafe page should accept TP-Link images.
Telnet isn't normally available on this device, unless you find a way to start it as root (I haven't)
If the IP address of your computer/smartphone is 169.254.x.y address, then this is a link-local address, and is assigned by the operating system itself because there is no DHCP server available. Like you noted earlier, you need to assign yourself another address in the 192.168.1.0/24 subnet to be able to access the failsafe page.
That being said, it is still odd that even the failsafe page fails to restore the device to a working state.
The device is an access point with no DHCP server normally. It would not normally be the case that you could connect a laptop and get a dhcp response. After reflashing factory firmware, @bkdwt should follow instructions from factory installation manual to configure the device... Which I think means connecting via wireless! Or at a minimum, setting a static IP and connecting on an appropriate default IP network.