@JMCASH 

 

Hi,

 

How did the firmware update fail exactly? Did you try to update with a firmware meant for another hardware version or model?

 

Have you already tested what happens if you reset the WPA4220 via the small recessed "Reset" button?

 

Copied from the official user's manual:
-------------------------------------------------------------------
To reset the powerline device：
With the extender powered on, use a pin to press and hold the Reset button for about 5 seconds until all
LEDs go off. When the Power LED turns on and the Wi-Fi LED starts to blink rapidly, the reset process
is complete and the default settings have been restored.
Be careful, don’t power off when the device is in reset process.
--------------------------------------------------------------------

 

  @JMCASH Already performed factory reset.

 

1. Want to share that  extender seems to work (wireless & buttons working, Wireshark showing AV protocol broadcast[*]) but it doesn't pair after I press pair button (led goes from solid to off and then goes solid again but pair led remains off).

 

2. Update failed for same hardware version but tagged UK instead as EU.

 

 

[*] Wireshark log

 

  @JMCASH 

 

Have you already checked whether the WPA4220's web interface might still be accessible via http://tplinkplclogin.net/ or http://192.168.1.1 or http://192.168.0.254 ?

That could be a way to get the correct firmware back onto the device.

Hi Thanks, not working even if AV500 seems to be there ... Frame 7: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface \Device\NPF_{60C6231A-A8C4-416C-B6D3-C03922D48FC9}, id 0 Interface id: 0 (\Device\NPF_{60C6231A-A8C4-416C-B6D3-C03922D48FC9}) Encapsulation type: Ethernet (1) Arrival Time: Nov 21, 2023 09:27:58.312202000 ora solare Europa occidentale [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1700555278.312202000 seconds [Time delta from previous captured frame: 0.015289000 seconds] [Time delta from previous displayed frame: 0.015289000 seconds] [Time since reference or first frame: 1.500046000 seconds] Frame Number: 7 Frame Length: 60 bytes (480 bits) Capture Length: 60 bytes (480 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:homeplug-av] [Coloring Rule Name: Broadcast] [Coloring Rule String: eth[0] & 1] Ethernet II, Src: AtherosC_00:00:01 (00:b0:52:00:00:01), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Destination: Broadcast (ff:ff:ff:ff:ff:ff) Source: AtherosC_00:00:01 (00:b0:52:00:00:01) Type: Homeplug AV (0x88e1) HomePlug AV protocol MAC Management Header Vendor MME Embedded Host Action Required Indicate

Hi thanks, yet not working even if AV500 seems to be there (connected through ethernet) Frame 7: 60 bytes on wire (480 bits), 60 bytes captured (480 bits) on interface \Device\NPF_{60C6231A-A8C4-416C-B6D3-C03922D48FC9}, id 0 Interface id: 0 (\Device\NPF_{60C6231A-A8C4-416C-B6D3-C03922D48FC9}) Encapsulation type: Ethernet (1) Arrival Time: Nov 21, 2023 09:27:58.312202000 ora solare Europa occidentale [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1700555278.312202000 seconds [Time delta from previous captured frame: 0.015289000 seconds] [Time delta from previous displayed frame: 0.015289000 seconds] [Time since reference or first frame: 1.500046000 seconds] Frame Number: 7 Frame Length: 60 bytes (480 bits) Capture Length: 60 bytes (480 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ethertype:homeplug-av] [Coloring Rule Name: Broadcast] [Coloring Rule String: eth[0] & 1] Ethernet II, Src: AtherosC_00:00:01 (00:b0:52:00:00:01), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Destination: Broadcast (ff:ff:ff:ff:ff:ff) Source: AtherosC_00:00:01 (00:b0:52:00:00:01) Type: Homeplug AV (0x88e1) HomePlug AV protocol MAC Management Header Vendor MME Embedded Host Action Required Indicate

Hi, good morning.Yesterday I was able to access my extender through its wireless connection on IP 192.168.1.1. Don't understand why I couldn't access it through wired connection even if in both cases default gateway (192.168.1.1) and mask (255.255.255.0) were the same. As extender is still not showing on tplPLC utility and not pairing, my plan is to update firmware from extender's interface. Need to find now right version of firmware in ".bin" format (instead of ".nvm" and ".pib") as exterder's interface manages only bin format. Don't find any more hw V1 firmware on tp-links interface, can you help me were should I find latest V1 version in binary format? Thanks, regards

  @JMCASH 

 

There are several firmware files in *.bin format available for download on TP-Link's "Worldwide" and "UK" websites. (just download all the *.zip files and then check which one's contain a *.bin)

 

https://www.tp-link.com/en/support/download/tl-wpa4220/v1/#Firmware

https://www.tp-link.com/uk/support/download/tl-wpa4220/v1/#Firmware

 

Good morning and thanks again. I was able to find 2 different versions of v1 firmware in ".bin" format and apply them to the device. Upgrade was prompted as successfull, however device is still not accessible through ethernet connection (only wifi connection is possible) and it is never being recognized/discovered by either old or new scan utility. What is calling my attention is that when accessing the device through it's current IP address (192.168.0.254), while forms are showing wifi's MAC address they are not showing any value (only zeroes) for powerline MAC address. Think that it is very likely that in order to discover the powerline device a MAC address is required so at the end of the day first issue to be solved is getting back device's MAC address! Please note that also with non-beta fw MAC was missing. Thanks regards PD I have screenshots showing status of extender but don't know how to share them

  @JMCASH 

 

Other than applying the available firmware images I don't think there is anything else an end user could do.

 

By the way, I noticed that the firmware images available for download are vastly different in size. I don't know how they perform the updating, but maybe not every firmware image updates all parts of the firmware?
It is also possible that certain parts of the firmware (for example the part that got broken during your initial attempt to update) can't be applied at all via a *.bin file from the web interface.

 

Did one of the images you tested happen to be the one called "WPA4220(EU)1.0_update_1.2.8_20140401.bin", which is the largest of them at nearly 1 Megabyte in size?

https://www.tp-link.com/uk/support/download/tl-wpa4220/v1/#Firmware