Technical Architecture

Engineered for Professional Android Servicing

Explore the modular engines powering AZEO DroidX. Built from the ground up for authorized repair centers, commercial technicians, and IT administrators.

Phase 02 Architecture

Multi-Interface USB, ADB & Fastboot Engine

Combines direct Windows SetupAPI / Win32 USB detection with Google platform-tools ADB and Fastboot integration. Automatically classifies device connection modes: Authorized ADB, Unauthorized (prompting on-screen RSA key confirmation), Fastboot Bootloader, Recovery, Sideload, and Offline states.

✓ Windows USB Vendor ID (VID) & Product ID (PID) hardware mapping.
✓ Safe getprop and getvar query execution with command injection guards.
✓ Multi-device hotplug concurrency and active target switching.

Hardware Connection Telemetry

[USB] Connected: VID_04E8 • Samsung Electronics
[ADB] State: Device (Authorized) • Transport: USB_3.0
[PROP] ro.product.model: SM-S918B • API: 34
[SECL] Security Patch: 2024-05-01 • Locked: 1

Phase 03 Architecture

Android Compatibility & Capability Intelligence

Rather than making unverified universal compatibility claims, AZEO DroidX uses an intelligent capability evaluator. It checks Android OS boundaries, bootloader restrictions, and manufacturer-specific protocols to advise technicians exactly which procedures are safe and supported.

✓ Multi-brand OEM normalizer handling Xiaomi, Samsung, OnePlus, Pixel, etc.
✓ Android version boundary evaluation (Android 5.0 Lollipop through Android 15).
✓ Risk ratings, technician guidance, and prerequisite warnings.

Compatibility Assessment Matrix

Capability: Read System Telemetry • Status: SUPPORTED
Capability: Factory Reset via Recovery • Status: SUPPORTED
Capability: FRP Guidance Assistance • Status: VERIFIED_ONLY
Capability: MDM Deprovisioning • Status: AUTH_REQUIRED

Phase 04 Architecture

Guarded Factory Reset & Safety Gate

Destructive operations require multi-point pre-flight checks: verified customer ownership record, explicit data loss consent on file, minimum 30% battery threshold, and hardware concurrency locking preventing double-execution on the same serial.

✓ Hardware concurrency mutual exclusion locks.
✓ Prominent data eradication disclosures and warnings.
✓ Complete operational audit logging into local SQLite database.

Safety Gate Interlock Verification

[CHECK 1] Customer Ownership Verified: PASS (INV-2026-09)
[CHECK 2] Customer Consent Documented: PASS (v1.0 Signed)
[CHECK 3] Concurrency Lock Acquired: PASS (LOCKED)
[CHECK 4] Battery Level > 30%: PASS (84%)
>> Ready to initiate authorized recovery procedure.

Phase 06 Architecture

Enterprise MDM & Device Owner Deprovisioning

Accurately inspects Android Device Policy Manager state (`dumpsys device_policy`). Distinguishes Fully Managed Device Owner deployments, Dedicated Kiosk configurations, and BYOD Work Profiles. Supports official disenrollment dispatch for Microsoft Intune, VMware Workspace ONE, Google Android Device Policy, Samsung Knox Manage, and MobileIron.

✓ Device Owner (DO) and Profile Owner (PO) classification.
✓ Corporate IT authorization reference validation.
✓ Post-deprovisioning device sync confirmation.

DPC Policy Analysis Engine

Classification: FULLY_MANAGED_KIOSK
Device Owner DPC: com.microsoft.windowsintune.companyportal
Organization: Retail Fleet Systems LLC
Deprovisioning Method: EMM Server Directed Disenrollment

View Commercial Licensing Plans →