All fixes for these errors must be run from either the Linux/Unix Terminal or Command Prompt/Powershell over the AhMyth/AhMyth-Server directory!

• Running as root without --no-sandbox is not permitted
• libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
• libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
• sandbox_linux.cc(377) InitializeSandbox() called with multiple threads in process gpu-process
• Broken AhMyth Interface
• Decompiling Failed
• Adding Source IP: PORT Failed
• Cannot find the Launcher Activity in the Manifest
• Unable to locate the Launcher Activity
• Reading Launcher Activity Failed
• Building Failed
• Signing Failed

This happens because you are trying to start AhMyth as root, and by default electron does not allow applications to start as root outside of the chrome-sandbox for security reasons.

To run AhMyth as root out of the chrome sandbox, run the following command;

npx electron ./app --no-sandbox start

This error is usually seen when running recent versions of electron in Virtual Machines, AhMyth needs electron v11.5.0 to operate properly both on Host and Virtual PC OS's, run the command below to fix the issue

npm uninstall electron; npm uninstall -g electron; npm install -g electron@11.5.0

npm uninstall electron; npm uninstall -g electron; npm install -g electron@11.0.0

This usually happens when you have two electron installations trying to start one application, hence the error message being printed in the terminal;

InitialiseSandbox() called with multiple threads in process gpu-process

With AhMyth, you most likely have electron installed globally as well as locally inside the AhMyth/AhMyth-Server directory which means there will be a node_modules folder located inside the AhMyth/AhMyth-Server directory.

You have two options from here,

either remove electron globally with;

sudo npm uninstall -g electron

or you may choose to remove electron locally with;

rm -rf AhMyth/AhMyth-Server/node_modules

Removing either one will fix the problem, but it is recommended that you remove electron locally by removing the node_modules folder, instead of removing electron globally.

This error is seen a lot when it comes to using a more recent version of electron in Virtual Machines, when facing this terminal error, you will also experience a broken AhMyth interface.

Users facing this error will need to refer to the libva error: vaGetDriverNameByIndex error fix in order to resolve it until I can figure out what causes the error so it can be fixed.

This usually happens because of three reasons

A. You have the wrong electron version installed in which case you need to refer to the libva error: vaGetDriverNameByIndex error fix

B. You have two electron installations trying to start AhMyth, in which case you need to refer to the sandbox_linux.cc error fix

C. You are running a more recent version of electron inside a Virtual Machine, in which case you'll need to refer to the libva error: vaGetDriverNameByIndex error fix

This isn't a problem with AhMyth, it's a problem with Apktool as well as the APK it's being used on.

Most of the time this happens when you are trying to decompile an APK that is obfuscated or protected, other times the problem is related to Apktool.

The error log file generated by a failed Decompiling Process will determine why Decompiling fails, they are generated in the AhMyth/Logs folder, whatever the error with Decompiling is in the log file, just copy it and open an issue ticket about it.

This is happening because You've installed AhMyth with administrator privileges and you're trying to launch the application WITHOUT administrator privileges or Vice Versa

Remove AhMyth completely and reinstall it following the Binary Setup Instructions while maintaining the correct privilege escalation.

• For Windows if you install the Application as an Administrator, you'll need to Launch the Application as an Administrator and Vice Versa

• For Linux based Systems, install the Application using sudo and launch the application normally, or install it using the root account and launch it as root.

If the problem still persists then post and issue ticket containing the contents of the "IP:PORT.log" file which becomes generated at AhMyth/Logs after this error gets thrown.

Similar to the problem below, however this error happens when AhMyth tries to read the manifest of the original APK in order to find a Smali point to inject its hook, but unfortunately cannot find a Smali point to hook at all from reading the said manifest, therefore it doesn't bother searching for it, so when that happens that means that AhMyth "Cannot find the launcher activity in the Manifest" and you should "Please use the On Boot method" instead for a workaround.

This happens because the Main Launcher Activity for the Original APK being bound, has been found by reading the original APK's manifest, but cannot be found anywhere in any the "smali/smali_classes**" directories indicating that it's a weirdly modified APK.

There's nothing you can do about this other than use The Boot method until further research is conducted into APK's like this.

This error arises when using the On Launch Binding method, this happens because the Main Launcher Activity is not being converted to readable UTF8 format indicating that the APK is highly obfuscated.

There's nothing you can do about this other than use The Boot method until further research is conducted into APK's like this.

This error is quite a rare one as of AhMyth v1.0-beta.4, however if this error were to arise, it would be when using the On Launch Binding method because there is no point in the Launcher Activity with the string return-void, which is mostly never the case.

If this error ever does arise, then please open an issue ticket about it immediately, otherwise there's nothing you can do about this other than use The Boot method for the time being.

This happens because of a few reasons, see below for more information.

1. You are running the wrong Java version, when you should be running Java Development Kit 11.0.16.1

2. This should be done automatically, but just in case it's not, you may need to empty the framework directory for AhMyth's Apktool

java -jar path/to/AhMyth/AhMyth-Server/app/app/Factory/./apktool.jar empty-framework-dir --force

3. You have a broken java installation

If this is the case then you'll need to fix it yourself as this is problem that's not related to AhMyth but your OS.

4. AhMyth can't build the APK because Apktool is throwing an Unsigned Short Value error in which case you'll need to use another APK as a Template until further updates are implemented to fix this.
   

This happens because of the following reasons.

1. You are running the wrong Java version, when you should be running Java Development Kit 11.0.16.1

2. You don't have zipalign installed (32bit Linux Only)

If this is the case, then run the command below to fix the issue, zipalign is required because the new signer for AhMyth requires zipalign to operate properly.

apt-get install zipalign* -y

3. You have a broken java installation

If this is the case then you'll need to fix it yourself as this is a problem that's related to your Operating System, not AhMyth.