@PowerlineFW reupload please, link is dead by now.

  @PowerlineFW @NNover 

Try: https://ddl.to/d/3RMtw

  @Ariek thanks a lot!

  @PowerlineFW and everyone else,

For some reason I didn't get the email notifications about new posts and messages.

Thanks again for the firmware @PowerlineFW , you are a lifesaver..

I added it to the dropbox folder.

Will make sure this delay doesn't happen again.

  @PowerlineFW Hello, I stumbled across your forum posts while trying to find a way to upgrade the firmware on my TP Link TL-PA8010P (Version 1) powerline Ethernet adapters as I've been having a lot of stability issues with them. The current firmware version on the adapter is: 2.0.0.382-05_801111_160229_912. I downloaded the latest stripped nvm file (QCA75XX-2.13.0020_modules_5-6_stripped.nvm) based on the instruction in post #1 and I also pulled the PIB files from my own adapters using the FRITZ Powerline Utility. However, when I attempt to update the adapter (via ethernet cable) using the tpPLC utility, the update always fails. Can anyone offer me some advice or suggestions as to what I might be doing wrong? Thanks for the help in advanced.

Kind Regards,

stealth260

  @stealth260 @turboleak @PowerlineFW 

To be sure I'll quote from your post

1) current firmware 2.0.0.382-05_801111_160229_912

2) extracted the pib files with the FRITZ Powerline Utility; you got the correct pib files. 

Answer:

2.0.0.3 is a very old firmware version. What is the size of your extracted .pib files? It probably less than 22kB (or 21,8kB). You should upgrade incrementally.

First, from 2.0.0.3 > 2.2.2 (the opening post contains a dropbox link to all matching .nvm firmware files

There is a firmware version update that changes the file size of the .pib files. They become a little larger and change to 22kB (or 21,8kB). Not sure if this is firmware version 2.2.3 or 2.2.4. From there you should be able to update straight to 2.13.

1. Update incrementally from 2.0.0.3 > 2.2.2, this should work
2. after a successful upgrade; extract new pib files using the Fritz Utility.
3. upgrade from 2.2.2 > 2.2.3
4. same as (2); after a successful upgrade; extract new pib files using the Fritz Utility
5. Has the file size of the extracted .pib files changed to 22 kB?

• Yes, try to upgrade from 2.2.3 > 2.13.0.0 directly. This should work. Try/use the normal .nvm file first on all devices, if it fails on a device use the _stripped version.
• No, upgrade to 2.2.4 and extract new pib files.

  @Ariek Thanks for the reply. Unfortunately I have some bads news to share. I believe I have managed to brick one of my adapters. Before seeing your reply, I had tried to update to 2.4 with a generic pib file thinking maybe I needed to do the updates incrementally, so I randomly decided to try 2.4. The update ran for about 2 minutes before failing. I believe the adapter then attempted to power cycle, but never came back on. I have no lights at all on my adapter now and it appears unresponsive. I am NOT able to detect it with the PLC Recovery tool, I fear I may have destroyed it. It seems like you are extremely knowledgeable of these adapters and I'm hoping you might have some recommendations on how to unbrick this adapter. At this point I've run out of ideas and I'm hesitant to try and update another one of my PA8010P adapters until I get this sorted out.Thanks again for your help, its always an adventure trying to do something like this and I greatly appreciate it!

Kind Regards,

stealth260

  @stealth260 I have ran into that situation a number of times, upgrading using the wrong pib. Usually, when not ignoring the update at all, the adapters fall back into a recovery mode where they switch to a default mac adress and do more or less nothing other than barfing at the network once in a while. So they are not necessarily bricked, you can still recover using the open-plc-utils.

If you have saved the old pib file, you can extract the adapter's mac adress, DAK and NMK from it, and write it to a fresh pib made for the current firmware (there is version 1.4 pib files with length 20888 bytes for early firmware, and 1.5 pib length 22344 for firmware starting 2.2.3 I think, like mentioned in another message already).

You may want to start Wireshark and look for traffic with source mac address of 00:B0:52:xx:xx:xx (don't know the default address by heart now). If you see those, there's a good change for recovery. However, I'm not sure if the recovery tool you mentioned already tries something like this!?

If you are not familiar with open-plc-utils, I can craft the pib for you if you want...