AhMyth
AhMyth copied to clipboard
TikTok v25.3.4 | Binding Failed
This is an issue with
- [x] Binding On Launch
- [x] Binding On Boot
APK Name & Origin
APK Name: TikTok v25.3.4
APK Origin: APK Pure || TikTok_v25.3.4
To Reproduce
Steps to reproduce the behavior:
- Click the
APK Builder
Tab - Tick the
Bind With Another APK
checkbox - Choose
On Launch
Binding method - Browse for the TikTok APK
- Type your IP & Port
- Click Bind
- See the error
OS Info
please complete the following information:
- OS: Debian
- OS Version: Kali 2022.4
The reason this APK fails to Bind using the On Launch
method is because the Launcher Activity declared by the <activity
class that extends the MAIN || LAUNCHER
attributes in TikTok's AndroidManifest.xml
file as you can see below
<action android:name="android.intent.action.MAIN">
<category android:name="android.intent.category.LAUNCHER">
<activity android:name="com.ss.android.ugc.aweme.main.MainActivity">
Is located within a smali_classes
directory instead of the original smali
directory as you can see below from the find
commands output
$ cd ~/Downloads/TikTok && find -name "MainActivity.smali"
./smali_classes11/com/ss/android/ugc/aweme/main/MainActivity.smali
Unfortunately AhMyth is still only able to search the original smali
directories for the Launcher Activity when using the On Launch
binding method.
Problems will be experienced with the On Boot
method as well for APK's like this.
Upcoming updates to AhMyth will fix this problem.