Interactive Mode (TUI)
Sandroid’s default interface is a keyboard-driven terminal UI built with Textual. It is ideal for manual analysis, exploring an app, and complex investigations that need several tools at once.
Starting the TUI
sandroid # default config discovery
sandroid --config my-analysis.toml # explicit config
sandroid --network --screenshot 5 # pre-configure analysis options
sandroid --log # also print log messages to the terminal
Note
Sandroid 2.1 removed the legacy Rich menu (sandroid -i) and the
Forensic/Malware/Security views (TAB / --view). All actions now
live in one flat, rebindable catalog.
Screen Layout
Glance band (top, boxed, device name in the border): frida-server state, mitmproxy engine, Device Proxy and App Proxies, spotlight app – derived from the live device state.
Activity log: real-time command output and status messages.
Tool tabs (always visible): Spotlight, Network, Snapshots, Files – see below.
AI Chat dock (optional,
Ctrl+Y, experimental): see AI Chat (EXPERIMENTAL).
Tool Tabs
Spotlight
The app under investigation. c attaches to the foreground app, C
(Shift+C) spawns an installed app as spotlight. With the tab focused:
Enterstart (or resume a paused start), Shift+``A`` attach, Shift+``P`` start paused, Shift+``R`` restart with the armed hooks, Shift+``K`` kill and tear down hooks, Shift+``X`` clear the selection1-5toggle/arm the Frida bypass categories SSL, Root, Frida, Debug and Integrity (PairIP/licensing/attestation).Ctrl+Ptoggles SSL unpinning globally.
Warning
The bypass suite is EXPERIMENTAL. SSL unpinning covers Java/Conscrypt/ OkHttp/WebView/TrustKit/Certificate Transparency, native BoringSSL, Chromium/cronet BoringSSL and mbedTLS / Meta Network Stack, but hardened apps may still detect or defeat it. Verify results independently.
Network
Two sub-tabs:
Mitmproxy – embedded mitmweb (requires pip install mitmproxy):
Enterstart/stop mitmweb (proxy127.0.0.1:8080, web UIhttp://127.0.0.1:8081/). Start does not touch the device unlessmitmproxy.auto_device_proxy = true; stop (and quitting Sandroid) clears the Device Proxy Sandroid setCtrl+Dtoggle the Device Proxy (globalhttp_proxy)Ctrl+Ninstall the mitmproxy CA into the system trust store (APEX bind-mount on Android 14+, Zygote namespace on Android 10-13)yProxy Settings: Device Proxy, per-app App Proxies (iptables UID rules + on-devicegostredirector, to Sandroid’s mitmproxy or an external proxy such as Burp/ZAP; QUIC blocked by default) and CACtrl+Rrestart and re-apply proxies,Ctrl+Oopen the web UI,Ctrl+Amanage custom mitmproxy addons,Ctrl+Lclear the log
friTap – status header and live log tail of friTap TLS key extraction
(h starts friTap for the spotlight app).
Snapshots
AVD snapshot list: c create, l load, d delete, a assign to a
slot, Ctrl+R refresh. Globally, 0 opens the tab, 1-8 pressed
twice (within 3 s) load a slot – the first press only asks, because loading
reverts the emulator and 1-5 are also Spotlight’s bypass toggles – and
Ctrl+1-Ctrl+8 save the current state into a slot (8 slots per AVD).
Snapshots require an emulator.
Note
Ctrl + digit can only be sent by terminals that speak the kitty
keyboard protocol (kitty, WezTerm, foot, Ghostty, recent iTerm2).
Terminal.app, GNOME Terminal/VTE and tmux never deliver it. In any
terminal, press S (Shift+S) and then the slot digit 1-8
instead (Esc cancels).
Files
Monitor – live filesystem events (
o/Enterstart/stop). The defaultkprobebackend uses kernel tracefs kprobes (per-process and child-tree attribution, path-scoped capture, nothing pushed to the device) and falls back tofsmonautomatically (tui.monitor_backend). Per-category visibility is configurable in the Monitor settings.Watchlist – Spotlight Files: add device files to watch (
n), pull and diff them (uone, Shift+``U`` all;lopens the list).Diffs – Record/Play results and the run history (
r/pwork from every panel; Shift+``P`` here generates the PDF report of the selected run):rRecord: name the run and the number of replays, then Sandroid snapshots the device and records your input (Esc in the settings form cancels without recording).Interact with the device, then stop:
Esc/Enter(or Stop) stop and save, and the replay starts automatically; Discard throws the recording away.pPlay (again): the emulator is reverted to the snapshot, the recording is replayed, background noise is measured with a dry run, and changed / new / deleted files (with inline diffs), processes, sockets and network activity are shown.
Every Play is saved as a run bundle under
<results_path>/runs/<run_id>/and listed in the run history (per device).x/iexport / import a recording.
Other Actions
Key |
Action |
|---|---|
|
Frida server: download, install, start |
|
Reconfigure Frida hooks |
|
Static analysis of the spotlight APK (Dexray-Insight) |
|
Dexray-Intercept malware monitor |
|
Dump memory (Fridump) |
|
TrigDroid malware triggers |
|
Objection shell / resume objection session |
|
Forensic evidence scan (MVT) |
|
Manage forensic APKs |
|
Emulator information / device settings & country presets |
|
Screenshot / screen recording |
|
Install APK |
|
Network capture (PCAP) |
|
Proxy settings / friTap |
Press ? for the authoritative, up-to-date list.
AI Chat (EXPERIMENTAL)
Ctrl+Y opens a chat dock backed by any OpenAI-compatible chat-completions
endpoint. The assistant can query the device and drive ~76 Sandroid tools
(app lifecycle, flows, certificates, file transfer, monitor, record/replay),
spawn background subtasks, and use tools from configured MCP servers. Each
state-changing tool call asks for approval (once / always / never).
Warning
Prompts, the live device/session context and tool output (file contents,
flows, package data) are sent to the configured endpoint. Prefer a local
endpoint such as Ollama for sensitive evidence, and pass the API key via
SANDROID_AI__API_KEY instead of writing it into the config file.
[ai]
base_url = "http://localhost:11434/v1" # e.g. Ollama
model = "qwen2.5:14b" # a tool-calling capable model
# api_key via: export SANDROID_AI__API_KEY=... (any non-empty value for Ollama)
Tips
Start with Frida: install/start frida-server (
f) before dynamic analysis.Use snapshots: save a clean state into a slot (
Ctrl+1, orS1) before each experiment and reload it (1) afterwards.Focus on one app: set a spotlight app; App Proxies and the kprobe monitor can be scoped to it.
Combine tools: App Proxy + CA injection + SSL bypass for HTTPS inspection, friTap for apps that defeat proxies, the file monitor while exercising features.
Troubleshooting
frida-server does not start: check root (
adb root && adb shell id) and see Device Requirements.No device detected:
adb devices; switch devices withD.TUI rendering issues: run with
--logand checkresults/<timestamp>/sandroid.log.See Troubleshooting for more.