I have bricked my EAP225 by uploading Version 2 factory to it.
Upon checking the Openwrt site more carefully, I realize that the EAP V2 is only for the wall mounted. The firmware I should have loaded is Version 1.0. It is sort of hidden and I wish I knew how to add some extra warning re: this in the documentation here!!
EAP225 v2 22.03.3 https://downloads.openwrt.org/releases/22.03.3/targets/ath79/generic/openwrt-22.03.3-ath79-generic-tplink_eap225-v1-squashfs-factory.bin
Anyway, I have tried holding the reset button to see if will go into TFTP mode. Also used the three IP addresses 192.168.0.66 and 192.168.0.100, and 192.168.0.225 with no avail.
Any of the super guru here have any suggestions?
All EAP models most likely have tftp recovery methods. I have had a number of TP-Link models both amada and archer and other models and everyone of them came with tftp recovery in the boot loader.
I notice you did not try configuring your PC adapter to 192.168.1.100 which you should try first. If that doesn't work then most likely a firewall or tftp server config issue.
recover to stock first then back to openwrt.
tftp recovery also requires a correct firmware file name as well. make sure the filename is correct...usually includes "recovery" in the name.
Hi, Thanks for the reply. Yes, I did not try the 192.168.1.100 and will now.
I was looking for some tell tale on IP address and the file name in the log.
The other thing is despite holding the reset down it blinks four times to solid green
hmmm...that would suggest to me the AP booted up without errors. With which firmware though.
Try using your mobile phone and see if you can see an SSID with TPLINK in the name.
No SSID, NO IP address nothing.
And it goes to solid green in just 3.5 seconds from power on. Quick blink of each and done.
first let's make sure the bootloader is working. Assuming windows PC.
- set network adapter IP to 192.168.0.66. Always disable adapter then reenable adapter to make sure the settings take effect.
- open command line and type in ping 192.168.0.1 -t.
- turn on AP and watch the command line box to see if ping can get a reply. You should see about 3 or 4 successful replies appear in the command line box. This is the access point assigning an IP address to itself which is usually a .1 IP address and looking for a tftp server.
if not successful repeat the above but this time hold down the reset button while turning on to see if it requires the reset button to be held down during boot.
if not successful repeat all of the above but this time set your windows computer to 192.168.1.100 again disable/enable adapter.
Background: the bootloader initially gets an IP address from a variable in NVRAM at boot. Some models will do this without needing to hold down the reset button while other you need to hold down the reset button. In all events, if you see a successful ping on startup you know the bootloader is good and that tftp is possible.
The bootloader reads another variable in NVRAM called $server_ip which contains the IP of the tftp server. If you get a successful ping on 192.168.0.1 then you can be reasonably confident that the tftp server should be on 192.168.0.66. If you get a successful ping on 192.168.1.1 then tftp server is on 192.168.1.66 or 192.168.1.100
In the rare circumstance that the $server_ip is overwritten for some reason or other and you have no idea what ip address it could be (think long and hard in the past for possible IP addresses) then you will need to use a serial cable to login to manually issue the tftp commands.