android-re-decompile

Decompile Android APK, XAPK, JAR, and AAR files into readable Java source code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/warterbili/AUTO_REVERSE --skill android-re-decompile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-re-decompile
Source: https://github.com/warterbili/AUTO_REVERSE/tree/main/skills/android/android-re-decompile
Command: npx skills add https://github.com/warterbili/AUTO_REVERSE --skill android-re-decompile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires java, jadx, vineflower, dex2jar, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill solves the challenge of analyzing compiled Android applications by providing automated decompilation, API endpoint extraction, and call flow tracing. Without these capabilities, reverse engineering Android apps requires manual tool orchestration and deep expertise in multiple decompilers and analysis techniques.

Core Features & Use Cases

  • Multi-Engine Decompilation: Supports jadx, Fernflower, and Vineflower with automatic engine selection and comparison mode for optimal output quality.
  • Intelligent Triage: The fingerprinting phase detects the mobile framework (Flutter, React Native, Native) and HTTP stack before decompiling, preventing wasted effort on non-Java codebases.
  • API Discovery: Automatically extracts HTTP endpoints from Retrofit, OkHttp, Ktor, Volley, and Apollo interfaces, producing structured documentation with authentication patterns and request signing schemes.
  • Obfuscation Recovery: Recovers original Kotlin class names from R8-obfuscated apps using metadata mining, and provides deobfuscation support for both jadx and Fernflower.
  • Call Flow Mapping: Traces execution paths from UI entry points through DI frameworks (Hilt, Koin) down to network calls, producing readable architecture summaries.

Quick Start

Use the android-re-decompile skill to analyze the attached Android application file and produce a structured report of all discovered API endpoints and the call flows that lead to them.

Frequently Asked Questions about android-re-decompile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompile an Android APK and extract API endpoints?

To decompile an Android APK and extract API endpoints, you need a tool that orchestrates multi-engine decompilation using jadx, Fernflower, and Vineflower. This process converts compiled APK, XAPK, JAR, and AAR files into readable Java source code while automatically discovering HTTP endpoints from network interfaces.

Can I reverse engineer an Android app that is obfuscated with R8 or ProGuard?

Yes, you can reverse engineer an Android app obfuscated with R8 or ProGuard. Obfuscation recovery works by mining metadata to recover original Kotlin class names, with deobfuscation support applied across jadx and Fernflower decompilation engines.

What is the best way to extract API endpoints from Retrofit and OkHttp in a compiled app?

The best way to extract API endpoints from Retrofit and OkHttp is through automated API discovery during decompilation. This technique extracts HTTP endpoints from network interfaces, producing structured documentation with authentication patterns and request signing schemes.

Does Android reverse engineering work on Flutter or React Native apps?

Android reverse engineering with Java decompilers has limited effectiveness on Flutter or React Native apps. An intelligent triage phase fingerprints the mobile framework before decompiling, preventing wasted effort on non-Java codebases and directing analysis appropriately.

Do I need Java JDK 17 and dex2jar to decompile XAPK files?

Yes, you need Java JDK 17 and optionally dex2jar to decompile XAPK files. The multi-engine decompilation process requires Java JDK 17+, jadx, and optionally Fernflower, Vineflower, or dex2jar to perform framework detection and call flow analysis.