Skip to content

MAGISK_VS_XPOSED.md

Latest commit

 

History

History
41 lines (30 loc) · 1.31 KB

MAGISK_VS_XPOSED.md

File metadata and controls

41 lines (30 loc) · 1.31 KB

Magisk vs Xposed/LSPosed

Understanding the differences and when to use each.

Architecture

Magisk LSPosed
Root method Systemless (mount) Zygisk (process-level)
Framework None (modules are scripts) Xposed API (Java hooking)
Persistence Survives OTA Survives reboot (with Magisk/KernelSU)
Detection evasion Native (mount hiding) Via Shamiko module

Use cases

Magisk alone — file patching, init scripts, system prop spoofing

  • Universal GMS Doze (battery mod)
  • PlayIntegrityFix (hardware attestation)
  • Custom fonts, icon packs

Xposed/LSPosed — app-level behavior modification

  • Hide My AppList (prevent app detection)
  • XPrivacyLua (granular permission control)
  • TrickyStore (banking app bypass)
  • ReVanced Extended (YouTube mods)

Combined stack (recommended for max customization)

Magisk → Zygisk → LSPosed → individual modules
   ↓
Shamiko (hide root from apps needing it)
   ↓
PlayIntegrityFix (pass Play Integrity checks)

Can I use both?

Yes. Magisk provides root and modules, LSPosed hooks into processes via Zygisk. They're complementary.

But: Some apps detect Zygisk even with Shamiko. For banking apps, use only PlayIntegrityFix without LSPosed modules, or rely purely on TrickyStore hardware attestation spoofing.