Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/apktoolReverse engineering and fuzzing

apktool

⁨Auth/lab ref: decode and rebuild Android APK resources and smali for patching, manifest edits, resource inspection, and repackaging.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsApache-2.0synced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/apktool

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
BxzEdPAkPy…nRO4D/Cw==The CLI checks the SHA-256 and the signature before it writes a file.
Package88ab76d5…35711885
88ab76d5db7f…b48e357118851 file · ⁦1.5 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/apktool@21cd568

Resource and smali decode/rebuild workflow for Android APKs.

When to use Apktool

Use Apktool when you need to:

  • decode AndroidManifest.xml, resources, and smali from an APK
  • patch permissions, intents, strings, layouts, or smali logic
  • rebuild a modified APK for testing
  • inspect resources without full Java decompilation

Use jadx when you want readable Java/Kotlin. Use Apktool when you intend to edit the app.

Quick Start

bash
# Decode APK into a project-like directory
apktool d app.apk

# Decode for analysis-only resource inspection
apktool d -m app.apk

# Rebuild after edits
apktool b app

Typical output after rebuild is under app/dist/.

Core Workflow

1. Decode

bash
apktool d target.apk

This produces a folder containing at least:

  • AndroidManifest.xml
  • apktool.yml
  • res/
  • smali/ or smali_classes*/
  • assets/

2. Patch

Common edit points:

  • AndroidManifest.xml — exported components, permissions, debuggable flags
  • res/values/strings.xml — hardcoded UI strings and toggles
  • res/xml/ — config and network security settings
  • smali/ — bypass checks, short-circuit logic, redirect flow

3. Rebuild

bash
apktool b target

4. Sign and reinstall

Apktool rebuilds the APK but does not make it production-signed. Sign it separately before install.

bash
apksigner sign --ks debug.keystore target/dist/target.apk
adb install -r target/dist/target.apk

Common Use Cases

Patch app logic in smali

Use when the decompiled Java in jadx shows the method to change, but you need a reliable rebuild path.

bash
apktool d app.apk
# edit smali/com/example/MainActivity.smali
apktool b app

Change manifest or resources

bash
apktool d app.apk
# edit AndroidManifest.xml or res/values/*.xml
apktool b app

Pair with adb

bash
adb shell pm path com.example.app
adb pull /data/app/.../base.apk app.apk
apktool d app.apk

Practical Notes

  • Apktool is strongest for resource decode + smali round-trip, not for pretty source code.
  • If rebuild succeeds but install fails, check signing, package conflicts, and android:sharedUserId or min SDK constraints.
  • If static analysis is the goal, open the same APK in jadx alongside Apktool output.
  • -m is useful when you mainly want manifests/resources and do not care about a rebuild-ready tree.

Caveats

  • Complex OEM apps may require extra framework handling before clean decode/rebuild.
  • Rebuilt apps may still fail at runtime because of integrity checks, signature checks, or native anti-tamper logic.
  • Some Java-level edits are easier to understand in jadx, but safer to apply in smali.

Resources

No bundled scripts/, references/, or assets/. Use upstream docs at apktool.org for version-specific CLI details and build caveats.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd56888ab76d5Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login