I wonder if you can add records call

The victim app records call last calls (ex: 50 calls) and I can listen, download and delete it to make to free up space on the victim's device

This is an issue with the

• AhMyth Client

Describe the bug

I've had the same issue on both, virtual device with Genymotion and an actual Android cellphone. If the files are small they are usually saved, but if their size are close to 16.7 megabytes, a disconnection may happen before the file is actually saved, although, in this case, the disconnection does not happen as soon as I click on the diskette icon, which happens for larger files.

To Reproduce

Steps to reproduce the behavior:
1 - Install standalone payload
2 - Connect to the target
3 - Go to the File manager
4 - Click on the diskette icon to save a file larger than 16.7 megabytes
5 - Target disconnects instantly, reconnecting right after and the file is not saved.

Expected behavior

The file to be saved on the Downloads directory and the connection to be kept.

Client Issue

please complete the following information:

• Android Version: 9

Checklist

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

This is an issue with the

• AhMyth Server

Describe the bug

Standalone APK Payloads fail to build.

To Reproduce

Steps to reproduce the behavior:

1. launch AhMyth
2. Navigate to the APK Builder tab
3. Input the Server IP and Port number
4. Click the Red ⚡ | Build button
5. See the Building Failed error!

Expected behavior

Standalone Payloads should build without any problems whatsoever.

Logs

Error: Command failed: java -jar "D:\AhMyth-master\AhMyth-server\app\app\Factory\apktool.jar" b "D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth" -o "C:\Users\Usuario\AhMyth\Output\Ahmyth.apk"
W: D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\AndroidManifest.xml:1: error: No resource identifier found for attribute 'compileSdkVersion' in package 'android'
W: 
W: D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\AndroidManifest.xml:1: error: No resource identifier found for attribute 'compileSdkVersionCodename' in package 'android'
W: 
W: D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\AndroidManifest.xml:3: error: No resource identifier found for attribute 'appComponentFactory' in package 'android'
W: 
W: D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\AndroidManifest.xml:3: error: No resource identifier found for attribute 'requestLegacyExternalStorage' in package 'android'
W: 
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\Usuario\AppData\Local\Temp\brut_util_Jar_87413819326590425484757727410613639632.tmp, p, --forced-package-id, 127, --min-sdk-version, 16, --target-sdk-version, 22, --version-code, 1, --version-name, 1.0, --no-version-vectors, -F, C:\Users\Usuario\AppData\Local\Temp\APKTOOL11673515462252475372.tmp, -e, C:\Users\Usuario\AppData\Local\Temp\APKTOOL10365649841591437502.tmp, -0, arsc, -I, C:\Users\Usuario\AppData\Local\apktool\framework\1.apk, -S, D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\res, -M, D:\AhMyth-master\AhMyth-server\app\app\Factory\Ahmyth\AndroidManifest.xml]

OS Information

please complete the following information:

• OS: Windows
• OS Version: 10

Checklist

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

Not sure why the hell this is happening, it's not related to the server it's just related to the script that's there for newer users who don't know how to start AhMyth properly based on their privilege level, hence why this is a blank issue, apologies to other users who tried to post this, I misinterpreted those issues as unfilled server reports when the problem was in the right category to be opened under a blank issue, so I could've just edited those issues instead of removing them but my dumb ass didn't realise at the time, so once again my apologies, I'll have the start script for Linux fixed ASAP.

This is an issue with the

• AhMyth Client

Describe the bug

I have a victim connected to the victims lab, however whenever the victim puts its device in sleep mode(i.e. phone is still on but screen off) then after 30 seconds of idle waiting the victim disconnects.
The victim doesn't disconnect if I keep using the victims lab, doing stuff like getting files or call logs, etc.
This happens on 2 different devices (android 11 & 12)

To Reproduce

Steps to reproduce the behavior:

1. Install standalone payload
2. Connect victim
3. Turn off the victim's screen
4. Wait for ~30 seconds
5. Victim disconnects

Expected behavior

I would've expected the connection to remain even after putting the device in sleep mode.

Client Issue

please complete the following information:

• Android Version: Android 11 & 12

Checklist

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

Feature description

Support for a wider range of java versions ranging from Java 8 upto Java 21

Motivation

Currently only Java 11 is supported, and as of Debian 12 users can't apt install openjdk-11-jdk anymore, they can only install Java 17 or 21, so therefore support for a wider range of java versions would be a great feature and would also solve the problem of higher java versions being utilised over older ones.

An example of this may be that one user may want to utilise Java 11 or Java 12 for AhMyth instead of the latest Java 17 or java 21 on Windows since another process could be using it (or whatever the case may be), this feature would allow this to happen in terms of AhMyth being able to use any version of Java 8 all the way upto Java 21 for Decompiling, Building & Signing on an OS with multiple Java installations.

Acknowledgements

• This issue is not a duplicate of an existing feature request.
• I have chosen an appropriate title.
• All requested information has been provided properly.

Is your feature request related to a problem? Please describe.

No, This feature request aims to enhance our client app by implementing a Notification Receiver functionality. The Notification Receiver will allow our app to receive and analyze notifications from third-party applications, providing valuable insights into user interactions with those apps. By capturing relevant notifications, our app can gather data on user behavior, preferences, and engagement with external services.

This is an issue with

• Standalone Payload
• Binding On Launch
• Binding On Boot
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Configure the Server IP and Port
3. Attempt to build a payload (either standalone or bound)
4. See the [x] Signing Failed! error.
   
   
   

Logs

Always add the log files located at AhMyth/Logs based on your problem.

Error: Command failed: java -jar "/home/kali/AhMyth/AhMyth-Server/app/app/Factory/sign.jar" -a "/home/kali/AhMyth/Output/Ahmyth.apk"
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
could not execute zipalign
Run with '--debug' parameter to get additional information.

OS Info

1. OS: Kali Linux
   
   
   
2. OS Version: Kali 2023.3
   
   
   
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Dependencies Check

1. Checked dependencies by running...

apt-cache policy openjdk-11-jdk

If on 32bit linux then run...

apt-cache policy openjdk-11-jdk zipalign

2. See the results below.

openjdk-11-jdk:
  Installed: 11.0.20~7-1
  Candidate: 11.0.20~7-1
  Version table:
 *** 11.0.20~7-1 100
        100 /var/lib/dpkg/status
zipalign:
  Installed: 1:10.0.0+r36-1
  Candidate: 1:10.0.0+r36-1
  Version table:
 *** 1:10.0.0+r36-1 100
        100 /var/lib/dpkg/status                        

This is an issue with the

• AhMyth Server

Describe the bug

A clear and concise description of what the bug is.

• When we run AhMyth after installation the Interface is completely unusable.
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Install NodeJS & npm + Java 11
2. Install any version of electron after electron v11.5.0 via npm
3. Run AhMyth
4. See the broken interface.
   
   
   

Expected behavior

A clear and concise description of what you expected to happen.

• User Interface should be clickable.
  
  
  

OS Information

1. OS: N/A
   
   
   
2. OS Version: N/A
   
   
   
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Checklist

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

when i try to take photo they said snap as picture but nothing can somebody help me

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Code Editor v0.7.3
APK Origin: APK Pure || Code Editor

To Reproduce

Steps to reproduce the behaviour:

1. Open APK Builder
2. Type in server IP and Port
3. Without permissions
4. Browse for the APK
5. Bind with original APK
6. Building Failed

Logs

_Error: Command failed: java -jar "/root/AhMyth/AhMyth-Server/app/app/Factory/apktool.jar" b "/root/apk/editor" -o "/root/AhMyth/Output/Ahmyth.apk"
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method La03;->get()Ljava/lang/Object;
  at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1047)
  at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:346)
  at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:301)
  at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
  at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
  at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:430)
  at brut.androlib.Androlib.buildSources(Androlib.java:361)
  at brut.androlib.Androlib.build(Androlib.java:313)
  at brut.androlib.Androlib.build(Androlib.java:280)
  at brut.apktool.Main.cmdBuild(Main.java:255)
  at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x2
  at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1320)
  at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1043)
  ... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 68771
  at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
  at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
  at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1280)
  ... 11 more_

OS Info

please complete the following information:

• OS: Debian
• OS Version: Kali 2022.4

take a realtime screenshot from victim's phone

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Stopwatch Timer v2.1
APK Origin: APK Pure || Stopwatch Timer

To Reproduce

Steps to reproduce the behavior:

1. Open APK Builder
2. Type in server IP and Port
3. Customisation of permissions
4. Browse for the APK
5. Bind with original APK
6. Building Failed

Logs

Error: Command failed: java -jar "/home/kali/AhMyth/AhMyth-Server/app/app/Factory/apktool.jar" b "/home/kali/Desktop/APKs/Stopwatch Timer Original_v2.1_apkpure.com" -o "/home/kali/AhMyth/Output/Ahmyth.apk"
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method L$r8$java8methods$utility$Boolean$hashCode$IZ;->hashCode(Z)I
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1047)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:346)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:301)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:430)
	at brut.androlib.Androlib.buildSources(Androlib.java:361)
	at brut.androlib.Androlib.build(Androlib.java:313)
	at brut.androlib.Androlib.build(Androlib.java:280)
	at brut.apktool.Main.cmdBuild(Main.java:255)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x0
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1320)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1043)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65725
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1280)
	... 11 more

OS Info

please complete the following information:

• OS: Debian
• OS Version: Kali 2022.4

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Termux v0.118.0
APK Origin: APK Pure || Termux_v1.118.0.apk

To Reproduce

Steps to reproduce the behaviour:

1. Click APK Builder Tab
2. Browse for the Termux APK
3. Type IP & Port
4. Click Bind
5. See the error

OS Info

• OS: Debian
• OS Version: Kali 2022.4

This is an issue with the

• AhMyth Server

Describe the bug

A clear and concise description of what the bug is.

• When we accidentally click the Listen Button twice, then click the Stop Button once, and then click the Listen button a third time on the same port, we are greeted with an error message that tells us we are already listening on that specific port which indicates that the Stop function isn't working properly.
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Click Listen twice on a specific port
2. Click Stop
3. Click Listen a third time on the same specific port
4. See the error message stating the server is already listening on that port when it shouldn't be due to the stop button being clicked.
   
   
   

Expected behavior

A clear and concise description of what you expected to happen.

• The Stop button should be disconnecting the server from the client once it's clicked, meaning that we should not be greeted with any errors saying we are already listening on specific ports when we start listening on said specific ports, after we have clicked stop on that specific port.
  
  
  

OS Information

1. OS: All
   
   
   
2. OS Version: N/A
   
   
   
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Checklist

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

I will be building and integrating The Multiport Listener into the AhMyth interface, which will then allow users to listen on multiple ports for multiple victims at the same time without interfering with any relative connections.

[Half Done]
The option to also stop listening on any chosen port number will be added as well so if users make a mistake while entering the port numbers, they don't need to close AhMyth completely to fix it.

This is an issue with the

• AhMyth Client

Describe the bug

Firstly, I'd like to pay my respects to you for your hard work and dedication. It is much appreciated.

I have installed the app on Windows 10 and on a Samsung S23 with Android 13.

I am unable to listen to the phone or see the phone on the GUI. I have tried turning on port forwarding at the router, and using ngrok. I guess we can start from the beginning.

Here are my details:

My external IP Address appears to be 184.22.159.188

I have exhausted all the information I could find online and in all the other reported issues before writing this.

Thanks for your help.

This is an issue with the

• AhMyth Client

Describe the bug

When connected to a device and attempting to retrieve SMS messages, only the devices incoming SMS messages are retrieved. None of the device's outbound SMS messages (the texts sent from the device) are retrieved.

To Reproduce

Steps to reproduce the behavior:

1. Begin listening and connect to target device
2. Retrieve SMS messages from Victim Panel
3. View SMS messages and only incoming SMS messages are retrieved

Expected behavior

Upon SMS retrieval I expected that all SMS messages would be retrieved, incoming and outgoing SMS messages.

Client Issue

please complete the following information:

• Android Version: 10

Checklist

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

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Google Calculator v8.4.1
APK Origin: apkmirror || Google Calculator

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Input server IP and Port
3. Select all permissions
4. Select bind with original apk
5. Select on boot
6. Select browse apk and select the file
7. Click Bind

Logs

Error: Command failed: java -jar "C:\Users\stuar\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\stuar\Downloads\com.google.android.calculator_8.4.1_(520193683)-84100198_minAPI23(nodpi)_apkmirror.com" -o "C:\Users\stuar\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
W: C:\Users\stuar\Downloads\com.google.android.calculator_8.4.1_(520193683)-84100198_minAPI23(nodpi)_apkmirror.com\AndroidManifest.xml:33: error: attribute android:enableOnBackInvokedCallback not found.
W: C:\Users\stuar\Downloads\com.google.android.calculator_8.4.1_(520193683)-84100198_minAPI23(nodpi)_apkmirror.com\AndroidManifest.xml:33: error: attribute android:localeConfig not found.
W: error: failed processing manifest.
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:\Users\stuar\AppData\Local\Temp\brut_util_Jar_173494249983691841084702287587039902499.tmp, link, -o, C:\Users\stuar\AppData\Local\Temp\APKTOOL5973548283615952638.tmp, --package-id, 127, --min-sdk-version, 23, --target-sdk-version, 33, --version-code, 84100198, --version-name, 8.4.1 (520193683), --no-auto-version, --no-version-vectors, --no-version-transitions, --no-resource-deduping, -e, C:\Users\stuar\AppData\Local\Temp\APKTOOL12172866367051291597.tmp, -0, arsc, -I, C:\Users\stuar\AppData\Local\apktool\framework\1.apk, --manifest, C:\Users\stuar\Downloads\com.google.android.calculator_8.4.1_(520193683)-84100198_minAPI23(nodpi)_apkmirror.com\AndroidManifest.xml, C:\Users\stuar\Downloads\com.google.android.calculator_8.4.1_(520193683)-84100198_minAPI23(nodpi)_apkmirror.com\build\resources.zip]

OS Info

• OS: Windows 10 Enterprise x64
• OS Version: 21H2
• OS Build: 19044.3086

Dependencies Check

• Java(TM) SE Development Kit 11.0.16.1 (64-bit) installed

This is an issue with the

• AhMyth Server

Describe the bug

Building APK payloads with AhMyth on Operating Systems running 32bit architecture are failing everytime.

To Reproduce

Steps to reproduce the behavior:

1. Install AhMyth on any OS with a 32bit architecture.
2. Open AhMyth and Build a Standalone APK
3. See the Building Failed Error.

Expected behavior

A standalone APK Should be generated.

Logs

Always post the log files found at AhMyth/Logs to help us determine the problem further.

32bit support is deprecated, support for 32bit arch will not be present in Apktool 3.0.0

OS Information

• OS Name: Any Windows, Linux or macOS running 32bit architecture.
• OS Version: N/A

Checklist

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

Feature description

It's more likely a suggestion rather than a request. I have been using Ahmyth for a long time and have modified much of the frontend. I would like it if everyone had my custom theme for Ahmyth. I'm adding a screenshot. if you like, we can manage to get it into the next release of AhMyth

Motivation

Having a cool-looking UI is kinda sexy, lol

Acknowledgements

• This issue is not a duplicate of an existing feature request.
• I have chosen an appropriate title.
• All requested information has been provided properly.

For the Linux Root users of AhMyth who are facing this issue, please run the following command in your terminal to launch AhMyth manually as root. You must run this command in a terminal over the AhMyth/AhMyth-Server directory.

npx electron ./app --no-sandbox start

This is an issue with

• Binding On Launch
• Binding On Boot
  
  
  

APK Name & Origin

• APK Name: gfx tool pro 30.5.0
• APK Origin: gfx tool pro 30.5.0 || modyolo
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab

2. PASTE NGROK PUBLIC IP AND PORT IN REQUIRED FIELD

3. TICK ON ALL THE PERMISSION CALL LOG, CAM , MIC etc.

4. TICK ON BIND WITH AN ORIGINAL APK AND BROWSE APK

5. TICK ON "ON BOOT"

6. START BUILD APK
   
   
   

Logs

Always add the log files located at AhMyth/Logs based on your problem.

i am using dpkg version of ahmyth and unable to fine log file ... tell me the location so i can edit this report.

OS Info

• OS: kali GNU/Linux Rolling
• OS Version: Kali 2023.2 latest build
  
  
  

Dependencies Check

1. Checked dependencies by running...

apt-cache policy openjdk-11-jdk

2. See the results below.

openjdk-11-jdk:
  Installed: 11.0.20~7-1
  Candidate: 11.0.20~7-1
  Version table:
 *** 11.0.20~7-1 500
        500 http://http.kali.org/kali kali-rolling/main amd64 Packages
        100 /var/lib/dpkg/status

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

A Seperate Window for a Settings Menu accessible by clicking a small ⚙️ icon in the main GUI ultimately for:

• changing the path where payloads are stored
• possible built in reverse tunneling configuration — haven't decided on this one yet

Describe alternatives you've considered

• ngrok
• no-IP
• playit-gg

All require some sort of account setup.

Additional context

None to add.

I have successfully built and deployed the RAT, for the IP and Port configuration I've used the output given to me by portmap.io, so say the portmap.io output was something like

tcp://xyz.portmap.io:69696 ==> 5050

so i've inputted xyz.portmap.io for the Server IP, and Port "69696" for the Server Port,
turned on "openvpn" configuration on my PC, and connected to my portmap server.

However when listening for Victims Connections to come back in AhMyth nothing happens, I've listened for connections on Port "5050" but I'm not able to get any connections and I've also tried listening on Port "69696" but I still can't get any connections.

how do I properly configure AhMyth with "portmap.io" with portmap??

It was Working Fine But today on launch it gives this error
[16798:0420/092018.834203:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.

This is an issue with the

• AhMyth Server

Describe the bug

A clear and concise description of what the bug is.

• Both the Boot and Activity methods for Binding are broken, activity bound payloads crash, and boot bound payloads don't connect back after restarting the victim device regardless of how long we wait for it.
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Template an original application using either one of the Binding methods.
2. Install the bound payload on the victim device.
3. See the application crash if using the Activity method, or see that the payload won't connect back after restart when using the Boot method
   
   
   

Expected behavior

• Boot bound payloads should connect back after the device has been restarted.
• Activity bound payloads should connect back immediately without any Runtime Exceptions
  
  
  

OS Information

1. OS: All
   
   
   
2. OS Version: N/A
   
   
   
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Checklist

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

Have access to the sd card from the storage tab.

I have successfullly install java version (jdk 8)

"java version "1.8.0_391"
Java(TM) SE Runtime Environment (build 1.8.0_391-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.391-b13, mixed mode)

but this AhMyth Showing

Wrong java version installed . java version 1 detected

showing please help me how to fix it

It will be so good if you added the dark theme to the AhMyth RAT .

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Whatsapp Plus (mod)
APK Origin: mediafire

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Tick all Custom Permissions Boxes
3. Choose the App to bind to
4. Click the bind button
5. See the failure

Logs

Always add the log files located at AhMyth/Logs based on your problem.

Error: Command failed: java -jar "/Users/jack/AhMyth/AhMyth-Server/app/app/Factory/apktool.jar" b "/Users/jack/Downloads/WhatsApp_Plus_v19.40" -o "/Users/jack/AhMyth/Output/Ahmyth.apk" --use-aapt2 ""
W: /Users/jack/Downloads/WhatsApp_Plus_v19.40/res/values/public.xml:38955: error: trying to add resource 'string/check_for_internet_connection' with ID 0x7f123e3e but resource already has ID 0x7f122912.
W: /Users/jack/Downloads/WhatsApp_Plus_v19.40/res/values/public.xml: error: file failed to compile.
brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [/var/folders/8r/npx3slfd7pg896fsl33c668w0000gn/T/brut_util_Jar_12834941623857753975711467054200346884.tmp, compile, --dir, /Users/jack/Downloads/WhatsApp_Plus_v19.40/res, --legacy, -o, /Users/jack/Downloads/WhatsApp_Plus_v19.40/build/resources.zip]

OS Info

• OS: macOS
• OS Version: 12.4 Monterey

This is an issue with;

• Binding On Launch

APK Name & Origin

APK Name: Tracker Insight v1.2.1
APK Origin: Tracker Insight v1.2.1 || ApkPure

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Tick all the Custom Permissions Boxes
3. Set the Server IP & Port
4. Browse for the original APK
5. Click the On Launch Binding Method
6. Click the Bind button

Logs

None to report, they weren't written!

OS Info

PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2022.3"
VERSION_ID="2022.3"
VERSION_CODENAME="kali-rolling"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"

Dependencies Check

1. Checked dependencies by running...

apt-cache policy openjdk-11-jdk aapt android-framework-res zipalign

2. See the results below.

openjdk-11-jdk:
  Installed: 11.0.16+8-1
  Candidate: 11.0.16+8-1
  Version table:
 *** 11.0.16+8-1 100
        100 /var/lib/dpkg/status
aapt:
  Installed: 1:7.0.0+r33-1
  Candidate: 1:7.0.0+r33-1
  Version table:
 *** 1:7.0.0+r33-1 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status
android-framework-res:
  Installed: 1:7.0.0+r33-1
  Candidate: 1:7.0.0+r33-1
  Version table:
 *** 1:7.0.0+r33-1 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages
        500 http://deb.debian.org/debian stretch/main i386 Packages
        100 /var/lib/dpkg/status
zipalign:
  Installed: 1:7.0.0+r33-1
  Candidate: 1:7.0.0+r33-1
  Version table:
 *** 1:7.0.0+r33-1 500
        500 http://deb.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

A big issue I've noticed with the Linux *.deb binaries for AhMyth, when they've been unpacked & installed using either apt install or dpkg -i, the Application is always owned by root which prevents regular non-root users from using some of the applications features such as the Building Feature.

Launching AhMyth via a Linux Desktop shortcut, or from the Linux Applications Menu

If AhMyth is launched by a regular non-root user using the Application Launcher from a Linux Applications Menu such as Kali Linux's "Whisker Menu" or from a manually created Linux Desktop Shortcut, it's not possible to use the building functions and possibly some other functions as well because there are no root privileges being escalated with the Application Launchers internal system command!

Root privileges should not have to be invoked, users should be able to use AhMyth regardless of their privilege status after unpacking and installing AhMyth from Binary (i.e regardless if they're root or non-root)

Launching AhMyth via the Linux Terminal

Regular non-root users need to invoke the use of sudo with the ahmyth System Shortcut Command , otherwise the only other way to use AhMyth via the ahmyth System Shortcut Command without problems, would be to invoke the su command in order for the user to switch to their root account, which in turn would allow the user to invoke the ahmyth System Shortcut Command without the use of sudo.

This should not be the case, any user should be able to Launch AhMyth from the terminal via the ahmyth System Shortcut Command without having to force root privileges with sudo or by a using their root account altogether!

They should just able to call the ahmyth System Shortcut Command and be able to use the application without any problems regardless of their privilege status (i.e regardless if they're root or non-root)

Payload Options

• Activity-method bound payload
• Boot-method bound payload

binding issue description

APK Name: YouTube ReVanced
Origin: Patched by myself using the Revanced Manager and the stock apk from: https://www.apkmirror.com/apk/google-inc/youtube/youtube-19-04-37-release/youtube-19-04-37-android-apk-download/

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Tick all Custom Permissions Boxes
3. Choose the apk from above
4. Click the bind button
5. Fails at:
   10.2.2024, 17:06:42 [★] Building Ahmyth.apk...
   10.2.2024, 17:07:10 [x] Building Failed
   10.2.2024, 17:07:11 [¡] Error written to "Building.log" on

Error logs

Error: Command failed: java -jar "C:\Users\yanni\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\yanni\OneDrive\Desktop\amyth\YouTube ReVanced" -o "C:\Users\yanni\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method Laaak;-><init>(Lbt;Lzyd;Landroid/os/Handler;Lzss;Lczg;Lzhp;Landroid/content/SharedPreferences;Lzkr;Lxlc;Lawkm;Lausj;)V
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1058)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:354)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:309)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:437)
	at brut.androlib.Androlib.buildSources(Androlib.java:368)
	at brut.androlib.Androlib.build(Androlib.java:320)
	at brut.androlib.Androlib.build(Androlib.java:287)
	at brut.apktool.Main.cmdBuild(Main.java:263)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x7
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1331)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1054)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65664
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1291)
	... 11 more


Error: Command failed: java -jar "C:\Users\yanni\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\yanni\OneDrive\Desktop\amyth\YouTube ReVanced" -o "C:\Users\yanni\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method Laaak;-><init>(Lbt;Lzyd;Landroid/os/Handler;Lzss;Lczg;Lzhp;Landroid/content/SharedPreferences;Lzkr;Lxlc;Lawkm;Lausj;)V
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1058)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:354)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:309)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:437)
	at brut.androlib.Androlib.buildSources(Androlib.java:368)
	at brut.androlib.Androlib.build(Androlib.java:320)
	at brut.androlib.Androlib.build(Androlib.java:287)
	at brut.apktool.Main.cmdBuild(Main.java:263)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x7
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1331)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1054)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65663
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1291)
	... 11 more


Error: Command failed: java -jar "C:\Users\yanni\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\yanni\OneDrive\Desktop\amyth\youtube-revanced_v19.04.37-patches_v4.2.0" -o "C:\Users\yanni\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method La;->bs(Latkw;)Ljava/lang/Object;
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1058)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:354)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:309)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:437)
	at brut.androlib.Androlib.buildSources(Androlib.java:368)
	at brut.androlib.Androlib.build(Androlib.java:320)
	at brut.androlib.Androlib.build(Androlib.java:287)
	at brut.apktool.Main.cmdBuild(Main.java:263)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x35
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1331)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1054)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65536
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1291)
	... 11 more


Error: Command failed: java -jar "C:\Users\yanni\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\yanni\OneDrive\Desktop\amyth\youtube-revanced_v19.04.37-patches_v4.2.0" -o "C:\Users\yanni\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method La;->bs(Latkw;)Ljava/lang/Object;
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1058)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:354)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:309)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:437)
	at brut.androlib.Androlib.buildSources(Androlib.java:368)
	at brut.androlib.Androlib.build(Androlib.java:320)
	at brut.androlib.Androlib.build(Androlib.java:287)
	at brut.apktool.Main.cmdBuild(Main.java:263)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x35
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1331)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1054)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 65536
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1291)
	... 11 more

Solution

sadly no idea from my side :(

Additional context

i can provide the patched apk if needed

Acknowledgements

• This issue is not a duplicate of an existing binding report.
• I have chosen an appropriate title.
• All requested information has been provided properly.

whenever i launch ahmyth im getting the following error:

ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[64062:0521/000139.794215:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
^C/home/kali/.npm/_npx/1323dbbc85759269/node_modules/electron/dist/electron exited with signal SIGINT

Heres my neofetch output:

OS: Kali GNU/Linux Rolling x86_64 
Kernel: 5.16.0-kali7-amd64 
Packages: 2958 (dpkg) 
Shell: zsh 5.8.1 
Terminal: qterminal 
CPU: Intel i5-4200U (4) @ 2.600GHz
GPU: AMD ATI Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile 
GPU: Intel Haswell-UL

I bind an original APK (FM WhatsApp) with your default payload with all custom permissions selected. Everything works fine and injected APK is generated. Then I Install this generated APK In my Physical Android of Version 13. During APK Installation I figure Out 2 Problems that look suspicious to a user and also it's not a good way and cause trust issues. A user may postpone the APK installation.

1st : As attached screenshot, Google Play Protect detecting app as a older android version because generated APK via Ahmyth is targeted by older version of SDK . It will be suspicious to the user and if a User clicks on "Got It" , backdooring finishes at that instance. HAHAHA

2nd : Same like error as described above. It also looks suspicious.

Permissions Note : At that stage custom permissions are working perfectly and app is requesting all the permissions.

WHAT I HAVE DONE MANUALLY

Then I decided to Decompile the Generated Ahmyth Binded APK (Of FM WhatsApp) using latest version of APKTOOL. Then I changed the SDK Version to 30 In the Manifest of decompiled APK and also changes the Value of SDK to Latest Version 30 In apktool.yml file.

After that I recompile the project with 100 percent success in APKTOOL. Then I installed this newly generated APK into my Physical Android Device. Now there are no suspicious popup as seen in 1st and 2nd Screenshot above and app installed successfully. Device connection is also active and victim is connected.

BUT...

Now, there is no custom permission selection activity or page popups at App first startup and also there is no access to sms, call log or camera or other permissions in Ahmyth Server.

Manually allowing permissions in APP Info page is not a good practice and also this is not convincing method.

I Hope I am able to describe my problem well to you. Thanks

I've tried it hundred times it don't show the phone in victims lab. I'm using a Samsung Galaxy star for test run, changed ports, ip, anything BUT still doesn't work

This is an issue with

• Binding On Launch
• Binding On Boot

APK Name & Origin

APK Name: Snaptube
APK Origin: SnapTube Modded

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Tick all Custom Permissions Boxes
3. Choose the App to bind to
4. Click the bind button
5. See the failure

Logs

Always add the log files located at AhMyth/Logs based on your problem.

Error: Command failed: java -jar "C:\Users\PC\AppData\Local\Programs\AhMyth\resources\app.asar.unpacked\app\Factory\apktool.jar" b "C:\Users\PC\Downloads\Snaptube_7.01.1.7016801_7016801_d7d4dc" -o "C:\Users\PC\AhMyth\Output\Ahmyth.apk" --use-aapt2 ""
Exception in thread "main" org.jf.util.ExceptionWithContext: Exception occurred while writing code_item for method Lahmyth/mine/king/ahmyth/ConnectionManager$c;->a([Ljava/lang/Object;)V
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1047)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:346)
	at org.jf.dexlib2.writer.DexWriter.writeTo(DexWriter.java:301)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:58)
	at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:37)
	at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:430)
	at brut.androlib.Androlib.buildNonDefaultSources(Androlib.java:376)
	at brut.androlib.Androlib.build(Androlib.java:314)
	at brut.androlib.Androlib.build(Androlib.java:280)
	at brut.apktool.Main.cmdBuild(Main.java:255)
	at brut.apktool.Main.main(Main.java:82)
Caused by: org.jf.util.ExceptionWithContext: Error while writing instruction at code offset 0x7
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1320)
	at org.jf.dexlib2.writer.DexWriter.writeDebugAndCodeItems(DexWriter.java:1043)
	... 10 more
Caused by: org.jf.util.ExceptionWithContext: Unsigned short value out of range: 67805
	at org.jf.dexlib2.writer.DexDataWriter.writeUshort(DexDataWriter.java:116)
	at org.jf.dexlib2.writer.InstructionWriter.write(InstructionWriter.java:356)
	at org.jf.dexlib2.writer.DexWriter.writeCodeItem(DexWriter.java:1280)
	... 11 more

OS Info

• OS: Windows
• OS Version: Windows 11

Is your feature request related to a problem?

No

Describe the solution or enhancement you'd like

A clear and concise description of what you want to happen.

Update documentation to reflect changes.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered (if any).
Soultion 1:

openjdk-11 was removed from latest Debian's 12 repos thus making the documentation obsolete,

sudo apt install openjdk-11-jre*

will not work as mentioned in the documentation

i suggest to change the documentation for linux based disto's based on debain and their derivatives (ubuntu parrot kali etc)

Soultion 2:

Update the project to use jdk 17 or later for the same,
this would still require to update the documentation.

Same applies for using electron@11 but its not that big if a issue because you can still install it through npm.

Feature description

Ability to bypass google play mechanism

Motivation

A lovely code you have on here, for pentesting can it bypass google play store or can you work on it.

Acknowledgements

• This issue is not a duplicate of an existing feature request.
• I have chosen an appropriate title.
• All requested information has been provided properly.

This is an issue with the

• AhMyth Server

Describe the bug

When I try to listen on multiple ports I have a problem, when I input the First Port Number to listen on, it replies with:

Started Listening on Port: 1st PortNumber

But when I type the Second Port Number to listen on, it replies with:

Already Listening on Port: 2nd PortNumber

Even though we are not listening on the second port number.

To Reproduce

Steps to reproduce the behavior:

1. Create a payload and send it to the Victim.
2. Create another payload with different Port Number and send it to the Victim.
3. Try to listen on both ports and be greeted with an error when trying to listen on the Second Port saying that we are already listening on the Second Port when we are actually already listening on the first port, not the second one.

Expected behavior

It should listen to multiple ports like It was doing before the release of v1.0-beta.5 .

OS Information

• OS Name: Any OS
• OS Version: N/A

Describe the solution you'd like

Live android camera preview in the Victims Lab Camera Option

Additional context

I'm french, not english, excuse me.

On Android 13 if you snap a camera picture on server, the snap sound is heard on the client side. I would appreciate if you find any way to get rid of the sound or just allow us to look at the live camera recording and take screenshots just on the server side.

I create apk file and copy it to device. But the installation won't start?

This is an issue with the

• 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
• 64bit
  
  
  

Checklist

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

This is an issue with

• Standalone Payload
• Binding On Launch
• Binding On Boot
  
  
  

APK Name & Origin

Remove this section if the problem is with building a standalone payload

• APK Name: flappy bird 1.3
• APK Origin: N/A
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Install as root user with sudo commands in nethunter kali armhf for android
2. Start with command ahmyth
3. But ip and port and click apk build
4. It show building the apk and then building failed without showing the signing step
   
   
   

Logs

Always add the log files located at AhMyth/Logs based on your problem.

Unfortunately cant find this folder 

OS Info

1. OS: kali
   
   
   
2. OS Version: nethunter 2024.1
   
   
   
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Dependencies Check

1. Checked dependencies by running...

apt-cache policy openjdk-11-jdk

If on 32bit linux then run...

apt-cache policy openjdk-11-jdk zipalign

3. See the results below.

openjdk-11-jdk:
  Installed: 11.0.20~7-1
  Candidate: 11.0.20~7-1
  Version table:
 *** 11.0.20~7-1 500
        500 http://http.kali.org/kali kali-rolling/main armhf Packages
        100 /var/lib/dpkg/status
zipalign:
  Installed: 1:10.0.0+r36-1
  Candidate: 1:10.0.0+r36-1
  Version table:
 *** 1:10.0.0+r36-1 500
        500 http://http.kali.org/kali kali-rolling/main armhf Packages
        100 /var/lib/dpkg/status

Firebase Request to avoid Port forwarding

Is your feature request related to a problem? Please describe.

No, just a limitation.

Describe the solution you'd like

The ability to delete files and folders on the Client Device from the Server, as well as the ability to Upload files and folders to the Android Client from the Server.

This is an issue with

• Standalone Payload
• Binding On Launch
• Binding On Boot
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Click the APK Builder Tab
2. Configure the Server IP & Server Port
3. Build either a Standalone Payload or Bind to an original application.
4. See the [x] Signing Faile!d error.
   
   
   

OS Info

1. OS:

• All 32bit Linux Systems
  
  
  

2. OS Version:

• All 32bit Linux Systems regardless of their version build
  
  
  

3. OS Architecture:

• 32bit
• 64bit

This is an issue with the

• AhMyth Server

Describe the bug

A clear and concise description of what the bug is.

• When building standalone payloads the Server IP & Port input is not written to its respective file (e.smali) which results in standalone payloads not connecting back to the server due to unmodified IP and Port string.
  
  
  

To Reproduce

Steps to reproduce the behavior:

1. Build a Standalone Payload
2. Decompile the Standalone Payload
3. Open the e.smali file located in Ahmyth-aligned-debugSigned/smali/ahmyth/mine/king/ahmyth in a text editor.
4. Locate the section that contains const-string v2, "http://
5. See that the string has not been modified with users IP and Port input from the Server.
   
   
   

Expected behavior

A clear and concise description of what you expected to happen.

• The user's Server IP and Port input should be written to its respective file (e.smali)
  
  
  

OS Information

1. OS: N/A
2. OS Version: N/A
3. OS Architecture:

• 32bit
• 64bit
  
  
  

Checklist

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