Broken Binding Features

[Morsmalleo]

This is an issue with the

• [x] 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:
   • [x] 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]

This is a repost of an issue that was present in the release of 1.0-beta.5.

The reason the Binding features were broken were because of the following reasons.

• For crashing activity bound payloads, the problem was coming from the function responsible for copying the payload files to the original application. The function responsible for this first creates a seperate smali_classesX directory (where X corresponds to the directory's appropriate numbering) for storing the AhMyth payload files, what was happening was that the function was removing both the android and androidx directories for the AhMyth payload after copying them into the smali_classesX directory, when they should have been moved to the original application's smali directory first before removing them, this has been fixed.
  
  
• For unresponsive Boot bound payloads the problem was because I'm a fucking idiot lol, I forgot to add the RECEIVE _BOOT_COMPLETED permission to the revamped permission arrays for the checkboxes, so that has been fixed as well, another problem with unresponsive Boot bound payloads also came from the Activity based problem stated above as well which has also been fixed.

Unfortunately I've had to reopen some issues about specific APK's that failed to be bound to because of this, only certain ones were able to remain closed, this is because moving the android and androidx payload folders for AhMyth into the original apps smali directory sometimes ends up surpassing the 64K Dalvik Method, a lot of users will find that [x] Building Failed errors with Binding, come from Unsigned short value out of range errors with Apktool , this means the 64k Dalvik Method has been surpassed and the application can't be built, I will be continuing to work on these Dalvik Method surpassed errors by continuing to update the function responsible for creating the payload directory and spiting the payload files