Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[08/03/2019] AMlogic Tools [6.0.0][A new milestone][Donate Version Available]

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Tonian
    replied
    Fixed it. Hate myself for not checking this earlier. The "file_contexts_tool.exe" was trigging my virus software.

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post

    Yeah sure.


    tried deleting tmp folder, editing permissions etc. still same crash
    Try using this unpacker.dll, we will also take this conversation to PM

    Leave a comment:


  • Tonian
    replied
    Originally posted by ricky divjakovski View Post

    Can i send you a test version?
    Yeah sure.


    tried deleting tmp folder, editing permissions etc. still same crash

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post

    Yeah the program gets to Level 2/ Kernel unpack and then closes.

    would love to give more detail but the isnt a crash warning, error message etc.
    Can i send you a test version?

    Leave a comment:


  • Tonian
    replied
    Originally posted by ricky divjakovski View Post

    Im gonna resolve this issue, ill find out what it is and grt back to you, buy it itms kernel related right?
    Yeah the program gets to Level 2/ Kernel unpack and then closes.

    would love to give more detail but the isnt a crash warning, error message etc.

    Leave a comment:


  • Tonian
    replied
    Originally posted by jasonnimwegen View Post

    Can you delete the temp folder in AMLTools Folder? if not, you probably have a permission issue. eg You were working on a image, and say you then moved that image to another location. You then went to use AMLTools again and it still has files in the tmp folder, but because you moved that image, the tool will throw up an error now. You need to delete the tmp folder, if it won't let you, you can change permission on the tmp folder to let you delete it. Once the tmp folder is deleted, the tool should work again. To change the permission, right click on tmp, go to properties, security, advanced, click change, type your username, click Ok, Tick "Replace owner on subcontainers and objects", click apply, ok, ok,ok and you should be able to delete the tmp folder now in AMLTools. Tool should work now.

    Will try the editing the permissions later. Ta


    not sure about moving images though. i don't move images round that much. i have 1 folder with all my images in. i copy the 1 image i want to the AML Tools folder. When the program doesn't work, i delete the entire aml tools folder as it's no longer needed.
    if i need the aml tools again, i just extract the AML TOOLS folder from the zip again. The shouldn't be any old tmps files as its a new extract each time i use it.

    Hope that makes sense




    Leave a comment:


  • jasonnimwegen
    replied
    Originally posted by Tonian View Post
    Java version doesnt matter. got both 32 and 64. still same crash
    Can you delete the temp folder in AMLTools Folder? if not, you probably have a permission issue. eg You were working on a image, and say you then moved that image to another location. You then went to use AMLTools again and it still has files in the tmp folder, but because you moved that image, the tool will throw up an error now. You need to delete the tmp folder, if it won't let you, you can change permission on the tmp folder to let you delete it. Once the tmp folder is deleted, the tool should work again. To change the permission, right click on tmp, go to properties, security, advanced, click change, type your username, click Ok, Tick "Replace owner on subcontainers and objects", click apply, ok, ok,ok and you should be able to delete the tmp folder now in AMLTools. Tool should work now.

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post
    Java version doesnt matter. got both 32 and 64. still same crash
    Im gonna resolve this issue, ill find out what it is and grt back to you, buy it itms kernel related right?

    Leave a comment:


  • Tonian
    replied
    Java version doesnt matter. got both 32 and 64. still same crash

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post

    PM me the source code for 4.0 and ill run it via VS Debug and pin point exactly where its failing.
    hopefully get some time tonight
    It wont show with VS because its running on a seperate thread, ill pack source code soon

    Leave a comment:


  • Tonian
    replied
    Originally posted by ricky divjakovski View Post

    Thanks, ill look more into this but its hard to pin point the issue, i can however mod the kernel unpacker
    PM me the source code for 4.0 and ill run it via VS Debug and pin point exactly where its failing.
    hopefully get some time tonight

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post
    Not tried anything different for a few days so still the same issue as before.
    program crashes out at when trying to unpack the Kernel. only on 4.0. 3.5 works via Visual studios debug (unpacking, never tried repacking)

    Will have another play over the weekend
    Thanks, ill look more into this but its hard to pin point the issue, i can however mod the kernel unpacker

    Leave a comment:


  • Tonian
    replied
    Not tried anything different for a few days so still the same issue as before.
    program crashes out at when trying to unpack the Kernel. only on 4.0. 3.5 works via Visual studios debug (unpacking, never tried repacking)

    Will have another play over the weekend

    Leave a comment:


  • ricky divjakovski
    replied
    Originally posted by Tonian View Post

    honestly cant remember, in work at the moment so cant check.
    i just know i needed JDK for the original customization tool.

    i suspect i would go for x64 unless the customization tool specifically needed x86.
    What point do you get to? Flinux not being rin was my issue, seems its not so native after all

    Leave a comment:


  • Tonian
    replied
    Originally posted by ricky divjakovski View Post

    32 or 64 bit?
    I installed 32
    honestly cant remember, in work at the moment so cant check.
    i just know i needed JDK for the original customization tool.

    i suspect i would go for x64 unless the customization tool specifically needed x86.

    Leave a comment:

Working...
X