@netadair Thank you for weighing in on my situation, I greatly appreciate your assistance with this. I do have the original pib file that I extracted with FRITZ prior to attempting the failed update. However I am not familiar with the tools that you mentioned for creating a new pib file. Would you be able to link me to some resources that highlight the steps for building this new file? I would hate to burden you with having to build these files, but if its a cumbersome or complex process, I'd certainly appreciate the help. Also, I'd love to gain the knowledge of how to do this for the future should I run into this problem again.

In addition, I did as you instructed and I downloaded Wireshark to my laptop and then plugged it into the power line adapter via Ethernet. I performed a capture for about 20 minutes and I don't seem to be seeing any packets except the ones my laptop is sending. Do I need to mess with the filters or setting in wireshark to see any potential traffic the adapter maybe sending?

I also did a bit of research on the open-plc-utils. Unfortunately I don't have a Linux box at the moment, so I attempted to install it via Cygwin, but unfortunately it doesn't build correctly and the error message clearly state that Cygwin isn't supported.

Kind Regards,

stealth260

  @stealth260 

Try these plc tools for Windows (CMD)

http://ddl.to/d/3csSx

http://ddl.to/d/3csUR

Note: One file is a Zyxel PLC Utility. Do not use the utility itself. Install it and in the installation directory there will be a directory with several plc command line tools. Similar as the other file with plc tools. Not sure if they still work with W11.

It looks like there is only a really small chance left that your adapter is not bricked. It does not talk on ethernet from what I can tell from the trace, and obviously the usual recovery tool don't see it either.

If you want to give it a try and the pib you used it now trying to talk to the (non-existant) ethernet switch in your adapter, you may stil be able to see it via powerline after it reverted back to some default settings.

That is, it may be possibly so see by using the default NMK ie network name "HomePlugAV" (or, using the reset button in the Fritz powerline utility) on your working adapter, or using an off-the-shell new one with it's default settings.

After that, maybe you can see the adapter in the network map, and/or in Wireshark and/or in the recovery utilties.

If you don't see the bricked adapter with that small last test, I'd consider it gone.

  @PowerlineFW @stealth260

I read your message about bricked devices and I'm not completely sure if you tried:

To recover the bricked devices you need to connect them directly to a computer with a network cable: adapter > RJ45 cable > PC.

With the PLC Recovery Tool you should be able to unbrick them with your original .pib file and a matching .nvm file (the .nvm file must match the original firmware version of the .pib file; you should try both the normal and stripped version; I would start with the stripped version on adapters with a WIFI module) and the exact MAC Address of the device (see back of the device).

If the device contains a reset button/hole, press it and let the Recovery Tool scan for the adapter. Or unplug the adapter from the power outlet and start scanning with the Recovery Tool.

Probably not necessary but with multiple network adapters on your pc (i.e. also for WIFI, VPN or bluetooth) I would suggest to disable those temporarily.

  @Ariek Thanks for your reply. Yes, I've tried connecting directly to powerline adapter using an ethernet cord between it and my computer. The PLC recovery tool does NOT find the adapter when its directly connected to my computer using an ethernet cable. Unfortunately, I don't see any activity coming from the adapter when I run a packet capture using Wireshark. I looked for a reset button as you suggested, but this particular adapter (PA8010P Verson 1) doesn't have one. You are supposed to be able to reset it by holding the pair button for 15 seconds, but I've tried this a number of times and it doesn't seem to have any effect.

The only thing I have left to try is resetting one of my working adapters to the HomeAVPlug to see if I'm then able to see the bricked adapter with the tpPLC utility as @netadair suggested in post #34. I tend to agree with @netadair that the devices is most likely permanently bricked. I guess this is a lesson to everyone to be super careful trying to update adapters with extremely old firmware. When I finally get a chance to try resetting an existing adapter to HomeAVPlug and see if I can then see the "bricked adapter" over the powerline functionality, I will let you all know, but I do not have high hopes at this point.

Thanks to everyone on this thread who has tried to help or offered suggestions, I greatly appreciate it. If anyone thinks of anything else I could try, please let me know.

Kind Regards,

stealth260

Did you try this rescue? Search for 

PowerLine coupler firmware rescue of Wolfgang Herget

I was in a same situation as you and rescued the adapter. It is possible to rescue the adapters in every case. If the instructions did not work then PM me.

  @PowerlineFW I can't download the new firmware .30, it says premium access only.

  File expired on: 4/13/2023

  @PowerlineFW Thanks a lot!

  @PowerlineFW 

please reupload  2.13.0.0030

it downloads with 0 bytes, tryed it over 10 times.