Device method debugger.
Read every device value through every method that can read it, and line them up so you can compare.
Releases · Wiki · User guide · AI agents · Export format · Architecture · Catalog · Changelog · XDA thread
Languages: English · العربية · Čeština · Deutsch · Español · فارسی · Français · हिन्दी · Bahasa Indonesia · Italiano · 日本語 · 한국어 · Nederlands · Polski · Português · Русский · Svenska · ไทย · Türkçe · Українська · Tiếng Việt · 中文
Android is a super powerful and versatile operating system; what nobody tells you is that all your personal details and confidential information are available to every application you install, and protecting yourself against these invasions of privacy is an obligation. VD Infos shows you an example of what can be captured from your device, and it does so as a method debugger: for each piece of information it reads the value through every method that can read it: framework APIs, native interfaces, shell commands, system managers, content providers, files, syscalls, and hardware key attestation (TEE), and lines them up so you can compare. When one reading disagrees with the others, something in between is rewriting that surface: a hooking framework, a spoofer, a resolver shim. NO INFORMATION IS STORED, SENT OR TRANSMITTED TO ANY FILE¹ OR SERVER: everything runs on-device, identity-bearing values are masked until you reveal them, and a report only leaves the device when you explicitly share or save it; if you want, block internet access with a firewall or just turn it off.
¹ Exception: each scan keeps its full report in the app's private storage (
files/last_snapshot.json). Only the app itself or root can read it, the next scan overwrites it, and it never leaves the device. It exists so AI agents can read the complete result; see For AI agents: the full report as JSON.
Each item is read through every method that can read it (Java SDK / native / shell), compared side by side:
- ~488 system properties read through several independent paths: the Java API,
the native property interface, and the
getpropshell command reached different ways, then lined up and compared. Because these paths do not all pass through the same layer, a value rewritten on one but not another shows up as a disagreement. - Device identity: model, manufacturer, brand, device, product, board, hardware,
fingerprint, bootloader, build id/tags/type, each
Build.*field against all itsro.product.*(system/vendor/odm) variants, native, and shell. - Identifiers: serial (many getters), Android ID (settings and provider), GSF ID, advertising ID, IMEI/primary IMEI/MEID/IMSI/ICCID, user serial.
- Telephony: the TelephonyManager surface (operator, SIM, network, roaming...), SubscriptionManager (multi-SIM), cell info.
- Network: per-interface MAC (
NetworkInterfacevs/sys/class/netvs shell), Wi-Fi (SSID/BSSID/IP/MAC), Bluetooth, DNS. - Kernel / process / system:
uname, boot id, uptime, UID/PID, SELinux, timezone, locale, environment, running services/processes. - Hardware / media: CPU, memory, sensors, display, cameras, system features, GPU, Widevine DRM ID.
- Packages / accounts / WebView: installed package list and count, per-app signing digests, this-app signature, self-package introspection, intent-resolution enumerations, accounts, call-log count, user agent.
- Sandbox conformance: low-level identity and kernel surfaces, plus a set of
dumpsysservices, that a properly sandboxed app should not be able to reach. For these the app checks whether access is correctly refused; a surface that is reachable when it should not be is flagged for review. - Advertising identifiers: the GAID from the Play Services binder, plus the whole
key family (AAID, OAID/VAID and Huawei's
pps_*) swept across the three settings stores. - Root / hook / emulator detectors: artifacts and signals left by common root managers, hooking frameworks and emulators (Magisk, KernelSU, APatch, Xposed/LSPosed, Riru and the like), plus verified-boot state.
Each release publishes two APKs: SDK_35 targets the strict modern sandbox and is the one to use; SDK_27 targets an older API level, useful for comparison. Both install on Android 8.0 and newer.
- Release (APK): https://github.com/VD171/VD-Infos/releases
- https://github.com/VD171/VD-Infos
- https://xdaforums.com/t/VD-Infos.4097379/
- https://t.me/RootDetected
- https://t.me/BlankAssistance
Made for AI agents and LLM tools that work on the device through a shell (coding assistants, analysis scripts). Instead of reading screenshots, the agent reads the whole result with one command:
su -c cat /data/data/ru.vd171.vdinfos/files/last_snapshot.json- What it contains: every probe with its verdict and the value from every lens, in the same JSON as the export button. The screen shows only the first reading of a collapsed item; the file has all of them.
- When it updates: at the end of every scan, so run a scan first; the file always holds the latest one.
- Requirement: root, because the file lives in the app's private storage.
core/model immutable domain: Lens, Category, Verdict, ProbeSpec, ProbeResult
probe/ NativeBridge (JNI), SystemProps (reflection), PropCatalog (data)
SemanticProbes, IntegrityProbes, ProbeRegistry
engine/ ProbeEngine: coroutine fan-out, streams results as a Flow
data/ SnapshotStore (persist + diff), Exporter (JSON/text share)
ui/ Jetpack Compose, Material 3, dynamic colour, live progress
cpp/ native_probes.cpp: the native lens, dependency-free
- Parallelism: 996 probes fan out across the default dispatcher with a bounded permit count; results stream into the UI as they land.
- Nothing in the background: no services and no scheduled scans; the app runs only while it is open and closes itself when left idle.
- Native layer: one small, dependency-free
.so, bound by name viaRegisterNatives, kept deliberately tiny and simple.
Most contributions need no Kotlin: the lists live as plain text under VDInfos/app/src/main/assets/data/. Add or remove one line and open a pull request.
*_apps.txt: one package name per lineprops.txt: the system-property catalog,CATEGORY<tab>keyspoof_keys.txt: the settings-spoof matrix,key:TYPEknown_certs.txt: the signing-certificate catalog,SHA-256<tab>owner(full hash, taken from a real APK withapksigner verify --print-certs)- other
.txtfiles: one entry per line too (kernel-module name fragments,/data/local/tmpfile names)
A # starts a comment; blank lines are ignored. Some files pack a few space- or tab-separated fields per line, or optional markers (S and @field in props.txt); keep the shape of the lines already in the file. Code contributions are welcome too. By contributing you agree your work ships under this project's AGPL-3.0-or-later.
Root hiding and detection references (guides, modules, frameworks, detectors) live in a dedicated catalog: CATALOG.md.
Special thanks to frknkrc44, developer of HMA-OSS, for the care put into it. HMA-OSS is where several of the fixes this app suggests are applied (hiding target apps and setting spoof presets), and every in-app mention of it links back to its source.
Its links, channels and how to support it: HMA-OSS.md.
- Wiki: all the docs, browsable online in 22 languages.
- User guide: installing, running a scan, reading the result and sharing a report.
- For AI agents and Export format: the machine-readable report and its schema.
- Architecture and Building: how it works and how to build it.
- Privacy, Security and Code of Conduct: the privacy statement and the governance docs.
- Catalog: root-hiding and detection references (guides, modules, frameworks and detectors).
- Changelog: what changed in each release.
- HMA-OSS: the hide-apps module the app's fixes build on (its links, channels and how to support it).
- Contributing: how to add detection targets (mostly plain-text lists, no Kotlin needed).
Sibling projects by the same author:
- VDGoogle: your Google services (RCS, Wallet, Play Integrity attestations), read on your device with no internet.
- VDBackup: full app and data backup and restore as root, driven entirely from a WebUI.
- COPG-VD: a device spoofer that turns a fresh fingerprint into a coherent, consistent profile.
- VD-dropbear: a standalone rooted SSH daemon (Dropbear).
Pixel build.prop: @VictorGabriel7Dev/build.prop (fork of @T3SL4).
- https://vd171.ru
- https://vd.priv8.ru
- Telegram: @VD_Priv8 https://t.me/VD_Priv8
- Channel: @Priv8_VD https://t.me/Priv8_VD
- Discord: @VD.Priv8 https://discord.com/users/1296831918989639721
- E-mail: vd.priv8@pm.me
- XDA-Developers: @VD171 https://xdaforums.com/m/vd171.4699873/
- XDA thread: https://xdaforums.com/t/VD-Infos.4097379/
- GitHub: @VD171 https://github.com/VD171
GNU AGPL-3.0-or-later: see LICENSE. Copyleft, including the network clause: anyone who runs a modified version (even as a service) must offer its source. Chosen deliberately for a research/anti-detection tool, to keep forks open.
VD Infos is an independent, unofficial research and diagnostics tool. It is not affiliated with, endorsed by, or sponsored by any of the vendors whose software, services or marks it reads, detects or names (including Google LLC and the Android Open Source Project). "Android", "Google", "Google Play", "Play Integrity", "Widevine" and all other product names, logos and trademarks are the property of their respective owners. VD Infos only reads what is already on your device and sends nothing anywhere.
android privacy security root-detection hook-detection spoof-detection anti-detection tamper-detection device-fingerprint magisk kernelsu lsposed play-integrity attestation tee keystore scanner diagnostics reverse-engineering kotlin



