Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 9 of 9
  1. #1

    TP-link TL-PA7020P KIT error in firmware update: how to restore the original firmware or a correct one?

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    Good afternoon,
    I made a mistake in upload the rigth firmware into one of the unit (I uploaded v2 instead of v1) - to do it I used the software provided in the box (powerlineutility). The unit is now a brick since it does not show any ligth and it does not seem to start. I installed the tpPLC software available on the internet and the tpPLC software does not recognise it.
    What can I do to restore the previous firmware or a correct one? Since the tpPLC software does not recognise the unit, there is no chance to use it and after some Internet research I did not find any useful information on how to do it.
    Thanks in advance for any support you may provide

    PS: While it is clearly my mistake in upgrading the firmware, TP-link softweare(powerlineutility) should not allow to upload a firmware which is not related to the version of the hardware to avoid mistakes like mine's

  2. #2
    Members QAQ is on a distinguished road
    Join Date
    Aug 2016
    in this case I suggest you to call up TP-Link support for a replacement
    Last edited by QAQ; 01-16-2017 at 00:55.

  3. #3

    another solution?

    Hello, is there another solution?

  4. #4
    If all the lights are off even the power light, then I think no other ways to try.

  5. #5
    Junior Member JayWalk is on a distinguished road
    Join Date
    Jul 2017
    https://wolfgangherget.de/powerline-...rmware-rescue/ I found the solution for same issue on my 4010 here if you want to try it at your own risk. I've added a post to document this however it's waiting approval.

    [h=1]PowerLine coupler firmware rescue[/h] So, I just botched a firmware update on one of my PowerLine couplers. The model I had trouble with is a TP-Link TL-PA4020P. However, this quick guide should work with pretty much any Atheros-based PLC device.
    [h=3]Steps to Reproduce[/h]
    • Download manufacturer’s setup tool
    • Download firmware files (“nvm” and “pib” files)
    • Refrain from directly connecting the PLC to the computer, instead leave it hooked up to a switch and other hardware.
    • Start firmware update using the aforementioned setup tool
    • Have a bit of bad luck
    • “Firmware Upgrade failed” error message.
    • Next up, “Local device not connected” error message.
    • After unplugging and re-plugging the PLC, no lights light up.
    • Faint hissing from the device, in normal operation it is silent.
    [h=3]Diagnosis[/h] OK, keep calm. This is a modern piece of hardware, surely it wouldn’t need to be disassembled to flash a firmware. Right? Or so my hopes went as I started panicking. Looks like I’m not getting the manufacturer tool to retry the update on the (hopefully just) soft-bricked device. That piece of software only tells me that it can’t find the local device. A quick web search (“TP-Link PowerLine failed firmware fix” and similar) didn’t come up with anything good right away.
    Well then, I thought, let’s see if it gives off any signs of life. I directly connected the PLC to my trusty MacBook and fired up WireShark. When the first packets started appearing I breathed a sigh of relief. The PLC still manages to get an ethernet link up. Amidst the stuff the Mac fires off when detecting a link (DHCP, MDNS, etc.) I finally found what I was looking for: Broadcast packets, “HomePlug AV” protocol, “Atheros_something” MAC, “Action Required Notification (Bootloader)”. Awesome! This thing is even politely asking me to remote-boot it. Let’s figure out how.
    Armed with the right keywords to feed to my preferred search engine, I finally found “Qualcomm Atheros Open Powerline Toolkit” aka “open-plc-utils“. BSD-Licensed tools to set up Atheros-based PLC equipment. And, not really surprisingly, that includes a “plcboot” tool, which does just that – feed the PLC a firmware such that it can proceed to boot.
    [h=3]The Fix[/h]
    • Rename the .nvm and .pib files from the manufacturer firmware package to nvm and pib (The atheros utilities are picky when it comes to file names, something I only found out after head-scratchingly reading the code.)

    • git clone https://github.com/qca/open-plc-utils.git cd open-plc-utils make plc/plcboot -N nvm -P pib
    • Finally, flash the firmware again, using the manufacturer tool. plcboot only performs a one-time boot when given the options above. To make the firmware permanent again, the flash needs to be rewritten. (Allegedly, plcboot can do that too, but it needs a “softloader” file, which I couldn’t be bothered to extract from the TP-Link software.)
    [h=3]Conclusions[/h] I love the fact that chip manufacturers are building in sensible bootloaders, and that there is open source software available to access these. This is for example also the case with the Atmel ARM processor families of Arduino Due fame. I, for one, welcome this trend, making it increasingly hard to turn your hardware into a paperweight. On the downside, OEMs like TP-Link try to hide these as best as they can: the manual just says to return the device to the distributor for service when experiencing the symptoms I’ve encountered.
    Bottom line: When a firmware update goes bad, don’t panic. It’s just a matter of finding the right tools. Also, it helps a lot having a general grasp of how things work on the inside to actually know what may or may not be possible.

  6. #6

    light is ok

    Dear, the light is ok.

  7. #7
    Quote Originally Posted by demerivas View Post
    Dear, the light is ok.
    Oh, ok, I thought your unit is now a brick, too. If the ligths are ok, can you pair them via the pair button or the utility? If the utility can't detect the unit, and nothing happens after the pair button(normally the power light will flash after you press the pair button for 1s), then I don't think there is another solution for it.

  8. #8

    i lost

    Dear, the light is ok but the system does not go up. unfortunately. I think this one is dead, I already lost.

  9. #9


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright © 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.