How den4uk/andriller works
Project type and purpose
• Andriller is a desktop forensic utility written in Python that provides both a CLI and a Tkinter‐based GUI.
• Its purpose is to perform read-only data acquisition from Android devices (via ADB or backups), crack lockscreens, decode app databases, take screen captures, and generate HTML/Excel reports.
File structure
• Top level:
• andriller-gui.py (entry point for GUI)
• andriller/ (core application package)
• templates/ (Jinja2‐like report templates)
• bin/ (bundled ADB for Windows)
• tests/ (unit tests)
• configuration & packaging files (setup.py, requirements.txt, workflows)
• Inside andriller/:
• __main__.py (CLI entry point)
• adb_conn.py (manages ADB communications)
• driller.py / cracking.py (lockscreen cracking engines)
• decoders.py, decrypts.py, engines.py (data parsing & decryption)
• screencap.py (screen capture logic)
• gui/ (Tkinter windows, dialogs, preferences)
• templates/ (HTML templates for each data type)
• config.py (global settings), utils.py, messages.py, exceptions.py
README for additional insights
• Confirms key features: ADB‐based extraction, backup parsing, database decoders, lockscreen cracking, report generation.
• External dependencies: adb CLI tool, python3‐tk.
Main components & their interactions
a. User Interface Layer
• CLI Entry Point (andriller CLI via __main__.py)
• GUI Entry Point (andriller-gui.py → andriller.gui.core)
–– invokes Core Controller
b. Core Controller
• orchestrates requests from UI
• loads config, sets up logging
• routes tasks to Subsystems
c. Subsystems
1. ADB Subsystem (adb_conn.py)
– connects to device, issues ADB commands
2. Backup & Filesystem Parser (utils.py + classes.py)
– unpacks .ab backups, tarballs, file trees
3. Decoding Subsystem (decoders.py, decrypts.py, engines.py)
– per-app database parsers (contacts, SMS, WhatsApp)
– crypt file decryption
4. Lockscreen Cracking (driller.py, cracking.py)
– brute-force patterns, PINs, passwords
5. Screen Capture (screencap.py + gui/screen_cap.py)
6. Reporting Engine
– uses templates/REPORT.html and per-data templates via Jinja2‐style rendering
– generates HTML and Excel outputs
d. Configuration & Utilities
• config.py (global parameters)
• messages.py (localized strings)
• exceptions.py (error classes)
External dependencies & tools
• adb binary (bundled for Windows, system ADB for Linux/Mac)
• python3‐tk for GUI
• Python standard libraries + listed requirements
Architectural patterns & design principles
• Layered architecture: UI → Controller → Subsystems → Data & Templates
• Separation of concerns: decoding, cracking, ADB connection, UI are distinct modules
• Plugin-like decoders: extensible per-app templates and parser classes
• Forensically safe: all operations are read-only