Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Page 3 of 3 FirstFirst 1 2 3
Results 31 to 36 of 36
  1. #31
    Yes i see the CLP with your tplink utility.

  2. #32
    Quote Originally Posted by Uranium View Post
    Yes i see the CLP with your tplink utility.
    Well, that's good.
    Issue is: ATM I don't have access to the architecture and tools required to rebuild the PIB.
    Are you 101% positive the current PIB doesn't allow to write the update?
    What if you use the NVM from the archive upon the FIRMWARE DIRECTORY (where you found the utility) and the PIB you linked on your last post.
    Does it give you an error?
    USE the PORT1

    ELSE

    Know there are chances to brick the bootloader leaving the device semi/permanent dysfunctional since I don't have physical access to it.
    The device might require to be restored a few time till a way is found, so, you'll need to have the MAC ADDRESS handy ( at least ) and know how to change the device configuration with the tools provided within the same archive you found inside the archive utility RECOVERY directory.
    There could be additional tie, software verification implemented by the architect who's bonded the hardware's functionality to actually load the PLC stage, IDK.
    Last edited by NOLAN; 07-07-2017 at 21:01. Reason: T9

  3. #33
    I have already tried to update the PLC with the NVM from 8010P (it's the same) and the PIB i've linked but it fail in tpPLC (after waiting 10s, it fail instantly with 8010 or 8030 PIB), i will try with the tplink utility.

    I know i can brick the device, but i really like to tune lots of thinks :-)
    Last edited by Uranium; 07-08-2017 at 10:21.

  4. #34
    Quote Originally Posted by Uranium View Post
    I have already tried to update the PLC with the NVM from 8010P (it's the same) and the PIB i've linked but it fail in tpPLC (after waiting 10s, it fail instantly with 8010 or 8030 PIB), i will try with the tplink utility.

    I know i can brick the device, but i really like to tune lots of thinks :-)
    I've made the PIB.
    Chance are that PIB will either fail or brick the bootloader since I've made it without any verification. It could also successfully flash the chipset who's know. I don't have any device nearby I could feed it to check the flashing procedure.
    If you want I can give you trough PM the link but I might not able to give you the support required to unbrick till I put mine hands on the same PLC ( won't happen ).
    Keep in mind your device is fairly different from mine: your has additional software & hardware layer and I don't know if the recovery procedure are the same.
    If you can wait september, unless tplink decided to update, I will check the PIB by using mine as test device.
    Your call.
    Last edited by NOLAN; 07-08-2017 at 22:31.

  5. #35
    Yes please you can give me the link for the PIB, I don't know yet if I will flash it but I am beginning to take an interest in the modification of PIB.
    Thank you for taking the time to made the PIB.

  6. #36
    Junior Member
    Join Date
    Jul 2017
    Posts
    1
    Nolan, hey. Just found this threat and I'm quite happy to see somebody with enough knowledge able to modify the firmware. Is there any chance you can fix the drop of connection by implementing content ping between the 2 devices? (with powersaving mode off I still experience this from time to time.)

    Additionally I was wondering if for example wpa8630 can be turned into a router? I believe technical it can support just the firmware needs to be modified a bit. I do understand this could take more time and I'm willing to financially support if necessary

    Let me know what you think, thanks.


 

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-2017 TP-LINK Technologies Co., Ltd. All rights reserved.