# mSpy ## Identification [[LineageOS|LineageOS]] succeeded CyanogenMod as a community Android distribution. ROM managers, root managers, alternate app stores, system-app removers, SMS-control apps, and commercial monitoring software operate at very different trust levels. [[mSpy|mSpy]] is marketed as monitoring software; “Black Mart Pro” names an unofficial app source. A historical list like this can document prior Android experiments, but it is not a safe installation recommendation. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 14 — Android root, ROM, app-store, monitoring, and removal tools|PDF page 14: Android root, ROM, app-store, monitoring, and removal tools]] — The author is assembling ways to escape a stock Android environment: obtain root, replace the ROM, bypass an app store, remove bundled software, and remotely observe/control the device. That is consistent with the notebook’s sovereignty theme, but the list collapses liberating tools and high-risk surveillance or piracy-adjacent tools into the same search space. ## Relationships and overlays The source places this note in a shared evidence cluster with [[LineageOS|LineageOS]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads A modern reconstruction should add provenance, signatures, source availability, permissions, legal status, and threat-model fit for every tool before execution. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]] ## Scanned_20260730-1235 overlay The probable “M spy” entry on [[Scanned_20260730-1235#Scanned_20260730-1235.pdf — PDF page 5|PDF page 5]] appears beside Qualys VMDR and Cisco Meraki iOS enrollment. The page explicitly contrasts authorized vulnerability and fleet management with intimate-device monitoring; the spelling remains probable rather than conclusive.