Begin Debug Mode Fireware Upgrade
Upgrade fireware size is 5268643 bytes
Upgrade fireware md5 checksum is correct!
Now upgrade fireware...
######################################################################
###############
Done.
Firmware upgrade successfully! Please reboot manually.
I then unplugged and replugged the AP. After it booted, I cannot access it at 192.168.1.1 either directly connected to the computer with static ip 192.168.1.10, or connected it to a spare router with DHCP. With the router, I used the 192.168.1.10 computer to access the router DHCP list which only listed the computer. The AP status LED is green (AP must be in working order?)
I just connected the AP to the "live" router (network 192.168.0.XXX) and I could see the AP listed as:
Hostname: Unknown(unknown)
IP adress: fe80::52c7:bfff:fe76:e5
Type: Self-assigned
Try using http://[fe80::52c7:bfff:fe76:e5] in Chrome but "Site can't be reached".
My computer is set to static ip 192.168.1.10 when connected directly to the AP. I also connected to a spare router with ip 192.168.1.254, and it provides my computer with ip 192.168.1.100 (computer set to receive ip from DHCP server from the router). Ping 192.168.1.1 failed for both situation.
Did I brick the AP by unplugging it after successfully flashed the firmware? I should have used "reboot" command. But then the router shows the internet is active for this AP but there is no ip address.
I ping from a computer with ip 192.168.1.10.
Don't what to do now... I think the AP is bricked but how can I tell? Can someone confirm? My router said the port connected to this AP is active. But there is no ip address so I can't access it.
I don't know what device used to debrick from this instruction:
Debricking:
* Serial port can be soldered on PCB J3 (1: TXD, 2: RXD, 3: GND, 4: VCC)
* Bridge unpopulated resistors R225 (TXD) and R237 (RXD).
Do NOT bridge R230.
* Use 3.3V, 115200 baud, 8n1
* Interrupt bootloader by holding CTRL+B during boot
* tftp initramfs to flash via the LuCI web interface
setenv ipaddr 192.168.1.1 # default, change as required
setenv serverip 192.168.1.10 # default, change as required
tftp 0x80800000 initramfs.bin
bootelf $fileaddr
From the looks of it, installing the factory firmware upgrade worked. Replugging the AP should be the same as rebooting it, there isn't any unmounting of disks to be done, or things like that.
Can you ping the LL IPv6 address you're seeing? Note that you may need to add the interface name, because link-local addresses can be on any link:
$ ping -6 fe80::52c7:bfff:fe4f:e0a6
PING fe80::52c7:bfff:fe4f:e0a6(fe80::52c7:bfff:fe4f:e0a6) 56 data bytes
ping: sendmsg: Invalid argument
$ ping -6 fe80::52c7:bfff:fe4f:e0a6%enp0s31f6
PING fe80::52c7:bfff:fe4f:e0a6%enp0s31f6(fe80::52c7:bfff:fe4f:e0a6%enp0s31f6) 56 data bytes
64 bytes from fe80::52c7:bfff:fe4f:e0a6%enp0s31f6: icmp_seq=1 ttl=64 time=0.808 ms
The same probably holds for the http connection to the bare IPv6 address.
Edit: Looks like Firefox doesn't support LL IPv6 addresses, don't know the situation on Chrome.
As suggested, tried ping with IPv6 address but destination not reachable.
Also tried this https://community.tp-link.com/en/home/forum/topic/81462?page=1 but nothing is displayed on the tftpd log viewer window.
OK I will try to debrick with with the debrick instructions below. I will have to buy the USB TTL 3.3v adapter.
I don't fully understand the debrick instructions. Here is what I think the steps are:
Hardware mod:
Open EAP245v1
Connect USB TTL addapter to PCB J3 (1:TX, 2:RX, 3:GND, 4:3.3V)
Solder coper wire from R237 to connect RX
Solder coper wire from R225 to connect TX
Connect an ethernet cable between your computer and one of the LAN ports
Set computer IP address to static 192.168.1.10
Client side (connected via serial to the EAP245):
When the boot starts, hit ctrl-b key to stop autoboot.
Instead of http you should try ssh. Since snapshots have no http interface. You will have to include the name of the interface on your computer that is connected to the network as well, with %eth0 at the end etc
It has worked for me since Firefox enabled IPv6 support. But it is true that you cannot specify an interface in your URL though - nor can you in Chrome either. Unless I misunderstood your post, it just doesn't match the information you linked from Mozilla BugZIlla.
Maybe it could work if you only have one IPv6-capable interface? Bare IPv6-addresses work, but since you can't specify a zone-id (which is what the Mozilla ticket is about), I wouldn't expect a bare IPv6-LL address to work in Firefox.
Then, on the serial console you should be able to run the tftp and bootelf commands as you listed before. The filename used for the tftp command should match the one of the file present in your TFTP-root (i.e. your /tmp directory).