Stable Magisk v31.1 · released October 25, 2026

Magisk, explained root Android without touching /system

Magisk is the open-source tool most people use to root Android phones. This independent guide covers whether your phone can be rooted, how to install Magisk, which modules are still maintained, and how to fix what goes wrong. Every page is built from Magisk's own documentation and other primary sources, and links to them.

Can my phone be rooted? Install guide Fix a problem

What is Magisk?

A suite of open-source tools for customizing Android, by John Wu (topjohnwu) and contributors, licensed under GPL-3.0.

Systemless, in one paragraph

Magisk patches only the partition that holds your phone's boot ramdisk (boot, init_boot, vendor_boot or recovery). Root access, modules and property changes are applied in memory at every boot, so /system and /vendor stay untouched and restoring the stock image returns the phone to stock. It needs an unlocked bootloader and Android 7.0 or newer; v30.7, the previous release, still runs on Android 6.0. How Magisk works

What happens when a rooted phone boots

  1. BootPatched boot imageOnly its ramdisk is changed
  2. Firstmagiskinit runsHands over to Android's own init and patches the SELinux policy as it loads
  3. Early bootMagisk daemon startsLoads modules at the post-fs-data stage
  4. RunningRoot, modules, ZygiskAll applied in memory; /system is never written
Simplified from Magisk's own documentation and source (magiskinit, magiskd). Details: how Magisk works.
Root

MagiskSU

Root access for apps and shells, controlled per app in the Superuser tab.

 Customize

Magisk modules

Change system files, properties and SELinux rules without writing to /system.

 Inject

Zygisk

Run module code inside every app process; the base for LSPosed-style frameworks.

 Boot images

MagiskBoot

Unpack, patch and repack Android boot images, and extract them from payload.bin.

 Properties

resetprop

Change any system property, including read-only ro.* ones.

 SELinux

magiskpolicy

Patch the SELinux policy instead of switching it to permissive.

What changed recently

Checked October 26, 2026. Each tile links to the details.

  • Magisk stablev31.1October 25, 2026. Download
  • What v31.1 changedAndroid 7.0+, no pop-upsRoot is granted in the Superuser tab; app hiding is gone. Details
  • SamsungBlocked on One UI 8+What still works
  • LSPosedNow VectorThe original stops at Android 14. Vector guide
  • Play Integrity FixOriginal removedUse a maintained fork. Which one
  • Android 17RootableZygisk support from v31.0. Details

Where are you?

Jump straight to the guides for the stage you're at.

1

Before you root

2

Rooting

3

After rooting

!

Something broke

Rooting for the first time

The whole process, in the order you will do it. Every step links to its full guide.

  1. Check your phone can be unlocked

    Everything depends on unlocking the bootloader. Carrier-locked phones, Samsung phones on One UI 8 or later, and US and Canada Samsung models can't be unlocked. Your brand's guide shows the current status for your model.

  2. Unlock the bootloader

    This erases the phone, so back up first. Each brand does it differently: a fastboot command on Pixel, OnePlus and Nothing, an approval process on Xiaomi and Motorola.

  3. Get your stock firmware

    You need the image from the exact build you are running; there is no universal download. The root method checker tells you whether to patch init_boot.img, boot.img, recovery or the Samsung AP file.

  4. Patch it in the Magisk app and flash it

    Full steps: patch a boot image, or compare all install methods.

  5. Turn on USB debugging before installing modules

    Then a bad module can always be removed over adb, and Magisk's automatic Safe Mode covers the rest. See fixing a bootloop.

Rooting by phone brand

Unlock status as of October 2026. Each guide has a model finder and step-by-step instructions.

Google Pixel

Unlockable

One fastboot command, no waiting period. Patch init_boot.img on Pixel 7 and newer.

Pixel guide →

Samsung Galaxy

Blocked on One UI 8+

Samsung removed bootloader unlocking in One UI 8. Only Galaxy phones still on One UI 7, outside the US and Canada, can be rooted.

Galaxy guide →

OnePlus

Unlockable

Fastboot unlock, no wait on global units. Extract init_boot.img from payload.bin. Do not downgrade the 13 or 15.

OnePlus guide →

Nothing and CMF

Unlockable

Fastboot unlock, no wait, no regional locks found. init_boot.img on everything newer than Phone (2).

Nothing Phone guide →

Xiaomi, Redmi and POCO

Approval needed

Community app application, a 30-day-old account and a 72-hour or longer wait. China-region phones cannot be unlocked.

Xiaomi guide →

Motorola

Code required

Unlock code from Motorola, warranty void, no carrier models. The image to patch varies by model.

Motorola guide →

Most-read modules

With their maintainer, latest release and status. The module catalog lists 21 more.

  • PlayIntegrityFork

    Maintained

    Spoofs device properties to Google Play services. Restores the basic and legacy device verdicts; cannot give Android 13+ device integrity alone.

    Maintainer
    osm0sis
    Latest
    v18 (August 29, 2026)
    Needs
    Zygisk
    Read the guide →Source ↗

  • Vector (LSPosed fork)

    Maintained

    The maintained continuation of LSPosed: runs Xposed modules through Zygisk, scoped to the apps you pick.

    Maintainer
    JingMatrix
    Latest
    v2.2 (August 4, 2026)
    Needs
    Zygisk, Android 8.1 to 17
    Read the guide →Source ↗

  • Universal GMS Doze

    Unmaintained

    Lets Doze restrict Google Play services. Also disables Find My Device on every boot; officially supports up to Android 15.

    Maintainer
    gloeyisk
    Latest
    1.9.2 (November 28, 2024)
    Needs
    Magisk or KernelSU
    Read the guide →Source ↗

Magisk and the alternatives

KernelSU and APatch root from the kernel; Shizuku gives apps system access without root.

Magisk vs KernelSU

Magisk vs KernelSU compared: how each roots, GKI and LKM, metamodules, Zygisk, App Profile, switching safely between them, and which to choose.

Magisk vs APatch

Magisk vs APatch: kernel patching vs ramdisk patching, ARM64 and kernel 3.18 to 6.12 limits, the SuperKey, APM and KPM modules, and switching safely.

KernelSU vs APatch

KernelSU vs APatch: which kernels each supports, LKM vs KernelPatch, App Profile vs SuperKey, KPM modules, and how to switch between them safely.

Magisk vs Shizuku

Shizuku isn't root: it lets apps use system APIs with ADB or root privileges. What each can and can't do, how Shizuku starts, and when you need Magisk.

Questions about Magisk

What is Magisk?

Magisk is an open-source suite for customizing Android, developed by John Wu (topjohnwu) and contributors and licensed under GPL-3.0. It provides root access (MagiskSU), a module system, Zygisk and MagiskBoot, all without modifying the system partition. How it works

Can Magisk be installed without unlocking the bootloader?

No. Magisk's installation guide requires an unlocked bootloader, and no app or website can get around a locked one. Whether your phone can be unlocked depends on the brand and, for Samsung, the One UI version. Check your phone

Is Magisk safe to use?

Magisk itself is open source and published only on its GitHub repository. The risks come from what surrounds it: unlocking wipes the phone and weakens its security, a wrong image can stop it booting, and a bad module runs with root. Download only from GitHub, patch the image from your own build, and keep USB debugging on. Recovering from a bootloop

Does rooting void the warranty?

It depends on the manufacturer. On Samsung, installing Magisk trips the Knox fuse permanently; Motorola voids the warranty as soon as it issues an unlock code. Other brands' terms vary; each brand guide quotes what the manufacturer says.

Does Magisk hide root from banking apps?

No. Magisk's FAQ says it no longer handles root hiding, which is left to modules, and since 2025 Google's Play Integrity device verdict on Android 13 and later needs a locked bootloader. What can and can't pass

Can I remove Magisk later?

Yes. Uninstall it from the Magisk app, or flash your stock image back. Relock the bootloader only once everything is stock again. How to uninstall Magisk

Is this the official Magisk website?

No. Magisk has no official website beyond its GitHub repository and documentation. Magisk Guide is an independent, unofficial reference that summarizes those sources and links to them on every page. About this site

Every guide on this site

The complete list, grouped by topic.

Start here

Guides

Devices

Modules and Zygisk

Troubleshooting

Reference

About

About this site

Magisk Guide is an independent, unofficial reference, not affiliated with the Magisk project or its author. Pages summarize Magisk's documentation and release notes, Android's developer documentation and the documentation of the other projects covered, and each page lists its sources. Nothing is hosted here: links go to the official releases. Spot a mistake? Email hello@magiskguide.com. Read how this site is written.