Morsmalleo

First command ```zsh apt-cache policy openjdk-11-jdk ``` Second command ```zsh apt-cache policy aapt android-framework-res ``` Run these both in your terminal & print their outputs here

Alright so it's the APK itself, can you please print the contents of the original APK's manifest file please and we will see from there what the problem is.

Ok so inside the `

> ```shell > ┌──(kali㉿kali)-[~] > └─$ find -name "MainActivity.smali" > > ./smali_classes2/stopwatch/timer/app/activities/MainActivity.smali > ``` > > Yep just as I suspected, the Activity is located within a `smali_classes` folder, so...

Ok so I have been working on fixing this bug ALL NIGHT 🌑🌒🌓🌔🌕🌖🌗🌘🌑 and it seems it's going to take a bit longer than expected, don't worry though, I WILL...

If I need help I will, updates on research into fixing this bug will be posted here

DevLog - Monday, 15 July 2022, 7:08am (AEST) Ok so further research into this problem has confirmed for me that AhMyth certainly does locate the correct `.smali` file to hook...

The reason this APK fails to Bind using the `On Launch` method is because the Launcher Activity declared by the `

DevLog - TUESDAY, 5 July 2022, 11:47am (AEST) My research into the instability of AhMyth on Windows machines, has brought me to find that it's mainly due to two issues...

Be more specific with what's happening, and I might be able to help you