End directory files not showing

[BooM-141]

This is an issue with the

• [x] AhMyth Server

Describe the bug

The end directory files aren't showing in file manager.

To Reproduce

Steps to reproduce the behavior:

1. Setup application as per documentation
2. Bind payload to original APK with permissions camera and storage (Activity Method)
3. install generated APK on phone
   
   

Expected behavior

Expected to see end files in the directories to save

OS Information

1. OS: Windows 10 pro
   
   
2. OS Version: 19045.3693
   
   
3. OS Architecture:
   • [ ] 32bit
   • [x] 64bit
     
     

Checklist

• [x] Is this really an issue?
• [x] Have I looked at previous issues to see if this has already been addressed?
• [x] Have I used some initiative to try and solve the issue myself?

[Morsmalleo]

Could you produce a couple of screenshots of the problem for me please?

Also thank you for filling the issue report out properly as well it really helps 🙂

[BooM-141]

On my phone in the end directory 0/DCIM/Camera no files are showing (Camera take photo and receive works)

[Morsmalleo]

On my phone in the end directory 0/DCIM/Camera no files are showing (Camera take photo and receive works)

Crap, I had no idea that was happening, I'll jump on to this immediately, I'll let you know of the progress on here, I may already have a fix for this from another issue on here, I'm not sure I'll test it and let you know

[BooM-141]

That's awesome, Thank you

[Morsmalleo]

Could this be related to the APK I'm trying to Bind to?

If you're experiencing issues binding to an APK then you'll need to open up a B&B report for that one, usually most of the time it's either a problem modifying the manifest or that silly 64k Dalvik Method gets surpassed so the APK then can't be built, it's annoying but I am working on some experimental features that may help with binding a lot more

[BooM-141]

If you're experiencing issues binding to an APK then you'll need to open up a B&B report for that one, usually most of the time it's either a problem modifying the manifest or that silly 64k Dalvik Method gets surpassed so the APK then can't be built, it's annoying but I am working on some experimental features that may help with binding a lot more

Yeah binding is fine, just receiving the files

[Morsmalleo]

If you're experiencing issues binding to an APK then you'll need to open up a B&B report for that one, usually most of the time it's either a problem modifying the manifest or that silly 64k Dalvik Method gets surpassed so the APK then can't be built, it's annoying but I am working on some experimental features that may help with binding a lot more

Yeah binding is fine, just receiving the files

Ah cool, that's good then.

[BooM-141]

Crap, I had no idea that was happening, I'll jump on to this immediately, I'll let you know of the progress on here, I may already have a fix for this from another issue on here, I'm not sure I'll test it and let you know

Is there an ETA on fix by any chance.

[Morsmalleo]

Crap, I had no idea that was happening, I'll jump on to this immediately, I'll let you know of the progress on here, I may already have a fix for this from another issue on here, I'm not sure I'll test it and let you know

Is there an ETA on fix by any chance.

Going to take a look at it today

[BooM-141]

Going to take a look at it today

Awesome, really appreciate all the effort your putting in this repository. Great starting point for learning

[Morsmalleo]

Yeah just as I thought, a fix for a separate issue ended up fixing this at the same time, as you can see I'm now getting files arrive below, this also fixes this issue here #162 as explained above. I'll have this pushed to the master branch as soon as possible because a bug like this can't wait to be fixed in a new release.

[Morsmalleo]

Fix has been pushed to the master branch, please git clone AhMyth again, build another payload, install it and test it, then let me the results

[BooM-141]

Fix has been pushed to the master branch, please git clone AhMyth again, build another payload, install it and test it, then let me the results

Same issue still for me

[Morsmalleo]

Fix has been pushed to the master branch, please git clone AhMyth again, build another payload, install it and test it, then let me the results

Same issue still for me

Remove the payload you have installed on your victim device, build another one with the newly git cloned AhMyth, then install that one, the problem was happening for me, but it's been fixed with the fixes I pushed....

[BooM-141]

Remove the payload you have installed on your victim device, build another one with the newly git cloned AhMyth, then install that one, the problem was happening for me, but it's been fixed with the fixes I pushed....

Ill try again, but those are the steps I conducted already, Just to confirm this issue is occurring when binded to an existing APK

[BooM-141]

Ill try again, but those are the steps I conducted already, Just to confirm this issue is occurring when binded to an existing APK

The Issue is specifically when the payload is binded to the application, it seems it doesn't request permission for storage access.

[Morsmalleo]

Ill try again, but those are the steps I conducted already, Just to confirm this issue is occurring when binded to an existing APK

The Issue is specifically when the payload is binded to the application, it seems it doesn't request permission for storage access.

Is there an actual option in the permission settings of the bound payload for enabling access to storage? Or no? Send me a screenshot of the client side's permission settings in its App Info

[BooM-141]

Is there an actual option in the permission settings of the bound payload for enabling access to storage? Or no? Send me a screenshot of the client side's permission settings in its App Info

The bound payload permission when asked:

there is no storage permissions asked for even though it was selected on the server when attempting the bind.

[Morsmalleo]

I see the problem now, this could be due to the SDK version change that AhMyth makes when binding to applications that are above SDK 22, this was done until client updates could be made.

Are you familiar with using apktool?

[BooM-141]

@Morsmalleo I am learning with android studio and i know how to unpack an apk with the apktool

[Morsmalleo]

@Morsmalleo I am learning with android studio and i know how to unpack an apk with the apktool

Fair enough, what APK are you binding to I'll take a look at it, also this issue will need to be reverted to a B&B report, but I'll do this for you since you filled this report out beautifully anyway

[Morsmalleo]

I see the problem now, this could be due to the SDK version change that AhMyth makes when binding to applications that are above SDK 22, this was done until client updates could be made.

Are you familiar with using apktool?

Another reason for this automatic SDK change when binding using the On Activity method, is simply because legit apps above SDK version 22 won't ask you to enable payload permissions at all after binding due to the AhMyth payload only targeting SDK 22 and below instead of SDK 23 and up, and a lot of things changed in Android SDK 23.

so in short, the payload permissions won't be granted at all unless the request to do so is implemented properly and reflects on how's it's done in SDK 23 and up, which presents a problem also because in order to do this, we would have to drop support for older android versions, but I noticed that reverting the targetSdkVersion back to 22 allowed permissions to be requested to be granted with some apps when you bind to them, so the SDK change function was implemented

[BooM-141]

Fair enough, what APK are you binding to I'll take a look at it, also this issue will need to be reverted to a B&B report, but I'll do this for you since you filled this report out beautifully anyway

The APK im using is a modified open source project, you won't find it anywhere. I have made a github and provided you access to the source code for you to have a look at.

The SDK and permission are above my head, I had a look at an unpacked binded APK and the permission seem fine. But I don't know much about APK's yet

[Morsmalleo]

Fair enough, what APK are you binding to I'll take a look at it, also this issue will need to be reverted to a B&B report, but I'll do this for you since you filled this report out beautifully anyway

The APK im using is a modified open source project, you won't find it anywhere. I have made a github and provided you access to the source code for you to have a look at.

The SDK and permission are above my head, I had a look at an unpacked binded APK and the permission seem fine. But I don't know much about APK's yet

For an application that I can't retrieve the source code on openly, then I can't do much on this problem, I need to be able to openly get ahold of this application, I'll take a look at the GitHub repo you've provided, but note that binding success happens when I can freely get ahold of the APK

[BooM-141]

For an application that I can't retrieve the source code on openly, then I can't do much on this problem, I need to be able to openly get ahold of this application, I'll take a look at the GitHub repo you've provided, but note that binding success happens when I can freely get ahold of the APK

I understand, the source code is in the github repository, however I can provide the APK without the payload if required

[Morsmalleo]

For an application that I can't retrieve the source code on openly, then I can't do much on this problem, I need to be able to openly get ahold of this application, I'll take a look at the GitHub repo you've provided, but note that binding success happens when I can freely get ahold of the APK

I understand, the source code is in the github repository, however I can provide the APK without the payload if required

Provide the APK without a payload bound to it, yes that's what I meant

[BooM-141]

Provide the APK without a payload bound to it, yes that's what I meant

Sure what is the best method to send you the APK? I'll add it to the git hub repository I invited you to (edit: APK is too big for me to add), let me know if there is a better way.

Edit 2: https://github.com/ShiftHackZ/Stable-Diffusion-Android That is the link to the Open source version of the app that I have modified. I didn't make any core changes to the app so any fixes that would be made for the APK provided there would fix the modified version that I have.

[Morsmalleo]

Provide the APK without a payload bound to it, yes that's what I meant

Sure what is the best method to send you the APK? I'll add it to the git hub repository I invited you to (edit: APK is too big for me to add), let me know if there is a better way.

Edit 2: https://github.com/ShiftHackZ/Stable-Diffusion-Android That is the link to the Open source version of the app that I have modified. I didn't make any core changes to the app so any fixes that would be made for the APK provided there would fix the modified version that I have.

Just add the legit app without a payload to the repo and I'll grab it from there and see what's happening 😁

[BooM-141]

Just add the legit app without a payload to the repo and I'll grab it from there and see what's happening 😁

The apk is in the repo https://github.com/BooM-141/CSDL Thank you for the help.

Just saw the issue you posted. That's very disheartening. I'm willing to pay to get this issue sorted if you no longer intend on working on this project. In terms of the Windows version it should still work. If you are interested please let me know. Thank you for your efforts

[Morsmalleo]

Just add the legit app without a payload to the repo and I'll grab it from there and see what's happening 😁

The apk is in the repo https://github.com/BooM-141/CSDL Thank you for the help.

Just saw the issue you posted. That's very disheartening. I'm willing to pay to get this issue sorted if you no longer intend on working on this project. In terms of the Windows version it should still work. If you are interested please let me know. Thank you for your efforts

No im not giving up, I was upset about it, but no I won't give up 👍 I'll take a look for you

[BooM-141]

No im not giving up, I was upset about it, but no I won't give up 👍 I'll take a look for you

Thank you, its definitely granted, it would be annoying

[BooM-141]

No im not giving up, I was upset about it, but no I won't give up 👍 I'll take a look for you

Any updates on the issue?

[Morsmalleo]

No im not giving up, I was upset about it, but no I won't give up 👍 I'll take a look for you

Any updates on the issue?

Hey mate, no I haven't managed to get onto this one yet, I'm still trying to get JDK 17 Support for Apktool which is used by AhMyth for decompiling and recompiling APK files.

Since JDK 11 is no longer installable via apt from the Terminal, I need to keep things like this up to date otherwise people would have to go through a headache just install one dependency if you get what I mean.

There's also 3 things I need to do with the AhMyth payload as well,

1. There's a Binding Bug I need to fix that malforms certain Androidmanifest.xml file's when modifying them for the AhMyth payload, which makes binding impossible to certain apps impossible unless it's fixed

2. I need to integrate Major Client updates made by a third party who contributed to AhMyth, his name is HiddenPirates

3. I need to Update the server to use a higher version of electron which is what the application is built on

[BooM-141]

Hey mate, no I haven't managed to get onto this one yet, I'm still trying to get JDK 17 Support for Apktool which is used by AhMyth for decompiling and recompiling APK files.

Since JDK 11 is no longer installable via apt from the Terminal, I need to keep things like this up to date otherwise people would have to go through a headache just install one dependency if you get what I mean.

There's also 3 things I need to do with the AhMyth payload as well,

1. A Binding Bug I need to fix that malforms certain Androidmanifest.xml file's when modifying them for the AhMyth payload, which makes binding impossible unless it's fixed
2. I need integrate Major client updates made by a third party who contributed to AhMyth, his name is HiddenPirates

Big tasks ahead, thank you for the hard work on this project

[Morsmalleo]

Just add the legit app without a payload to the repo and I'll grab it from there and see what's happening 😁

The apk is in the repo https://github.com/BooM-141/CSDL Thank you for the help.

Just saw the issue you posted. That's very disheartening. I'm willing to pay to get this issue sorted if you no longer intend on working on this project. In terms of the Windows version it should still work. If you are interested please let me know. Thank you for your efforts

OK I've taken a look at the APK you've listed in your repo and Binding to it works fine, all permissions were asked to be granted upon installation, and end directory files show up as normal.

see the results below.

Server Side

Client Side

So the fix that I have pushed recently for this issue #162 seems to have fixed this issue also because as you can see from the results above everything is working fine for me.

I'm not sure what's happening on your end, but everything is working fine for me.

[Morsmalleo]

Yeah believe it or every app I've bound a payload to so far works fine, all permissions are requested to be granted including Files and Media, and end directory files are also showing up as well.

Just for the record, every time you rebuild a payload that contains new updates, you need to install this new payload on the victim device just like how you installed the initial payload that wasn't working before by not showing end directory files.

The Server itself does not automatically update old payloads that are still live on the victim devices when new one is built...... although now that I think about it, that actually could be a nice little feature for a future release 😁

I'm going to close this issue as completed because I can't recreate the issue you were having literally AT ALl after pushing fixes for a seperate issue here #162, if your problem still persists, let me know and I'll reopen the issue