Compatibility

Magisk support by Android version (Android 6 to 17)

The current stable Magisk, v31.1, supports Android 7.0 and newer; v30.7 is the last release for Android 6.0. Each big Android change since then has needed a specific Magisk update. This page lists them, with the changelog line for each, so you can tell whether your Magisk version is new enough.

Last updated 14 sourcesHow we check pages

Short answer

On Android 7.0 or newer, use the current stable Magisk, v31.1 (October 25, 2026). It supports Android 7.0 through Android 17, including Zygisk support for Android 17 added in the v31.0 pre-release. On Android 6.0, use v30.7 (February 23, 2026), the last release that supports it; v30.7 also covers Android 16 QPR2, and users report rooting Android 17 with it.

Support at a glance

Which current Magisk release runs on which Android

Featurev30.7v31.0 (pre-release)v31.1 (stable)
Android 5.0 to 5.1NoLast: v25.2NoNo
Android 6.0YesYesNoDropped
Android 7.0 to 15YesYesYes
Android 16 and 16 QPR1YesYesYes
Android 16 QPR2 (API 36.1)YesFixed from v30.6 stableYesYes
Android 17 (API 37)PartlyRoots per user reports; no changelog lineYesZygisk support addedYes
From Magisk's changelog and README at each release tag (v30.7: “higher than Android 6.0”; v31.1: “higher than Android 7.0”) and issue #9928 for Android 17 on v30.7. Checked October 26, 2026.

For Android 6.0, use v30.7. Everything from Android 7.0 to 17 works with all three recent releases, with the Android 17 caveat explained below. Need an older version? See the release archive.

Which Magisk does my Android version need?

AndroidAPIReleasedWhat changed for rootingFirst Magisk changelog line
1737Jun 16, 2026No boot-layout change found in Android's release notes.v31.0 (pre-release, Sep 4, 2026): “[Zygisk] Support Android 17 (API 37)”, included in stable v31.1. Users report v30.7 also roots Android 17 builds.
16 QPR236.1Dec 2, 2025 (Pixel)A new binary SELinux policy format. Older Magisk bootloops back to fastboot.v30.3 (pre-release): “[MagiskPolicy] Support new sepolicy binary format introduced in Android 16 QPR2”. First stable: v30.6. v30.7 adds “[MagiskInit] Support Android 16 QPR2 sepolicy format” and “[Zygisk] Support Android 16 QPR2 and higher”.
1636Jun 10, 2025No separate rooting change.No explicit line; supported by the releases current at the time.
1535Sep 3, 2024Devices may use a 16 KB memory page size.v28.0: “[General] Support 16k page size”
1434Oct 4, 2023New SELinux rules; QPR2 changed a Zygisk signature.v26.0: “[MagiskPolicy] Update rules to support Android U”. v27.0: “[Zygisk] Support new signature introduced in U QPR2”
1333Aug 15, 2022Phones launching with 13 move the generic ramdisk to a new init_boot partition.v25.0: “[MagiskInit] Support Android 13 GKIs (Pixel 6)”
12, 12L31, 32Oct 4, 2021Devices with kernel 5.10 or later must ship the Generic Kernel Image.v24.0: “[General] Support Android 12”
1130Sep 8, 2020vendor_boot and boot image header v3 arrive with GKI.v21.0: “[General] Support Android 11”
1029Sep 3, 2019The root file system moves into system.img (two-stage init).v19.0: “[MagiskInit] Support Android Q”; v19.4 adds two-stage init on A/B devices.
928Aug 6, 2018System-as-root is mandatory for phones launching with 9.v16.1: “[MagiskPolicy] Add new rules for Android P”
7.0 to 8.124 to 272016 to 2017The minimum for Magisk v31.1 and later.Supported by every current release. v31.1's README: “supporting devices higher than Android 7.0”.
6.023Oct 2015Last supported by v30.7.v26.0 set the minimum to Android 6.0. v31.1 drops it: “Android 7.0 is now the minimum supported version”.
5.0, 5.121, 222014 to 2015No longer supported.Last release: v25.2 (Jul 20, 2022). v26.0: “Bump minimum supported Android version to Android 6.0”.

Changelog quotes are word for word from Magisk's official changelog. API levels are from the Android Open Source Project; release dates are for the first stable release. A version listed is the first whose changelog mentions the change, not a promise that every phone on that Android version works with it.

Boot image changes by Android version

Most Magisk updates for a new Android version follow a change in how Android boots. These are the ones that changed what you patch or why rooting broke:

Android changes that affected rooting

  1. Android 9: system-as-rootMandatory for phones launching with 9. Magisk v16.1 added Android P rules.
  2. Android 10: root file system moves to system.imgNo longer in ramdisk.img; first-stage init mounts system. Magisk v19.0 and v19.4 (two-stage init on A/B).
  3. Android 11: vendor_boot and header v3ARM64 phones launching on kernel 5.4 must have vendor_boot. Magisk v21.0.
  4. Android 12: GKI required on 5.10+ kernelsBoot header v4 allowed. Magisk v24.0.
  5. Android 13: init_bootLaunch devices move the generic ramdisk out of boot. Magisk v25.0.
  6. Android 15: 16 KB page sizesAOSP supports 16 KB page devices. Magisk v28.0.
  7. Android 16 QPR2: new SELinux policy formatOlder Magisk bootloops to fastboot. Fixed in v30.3, stable from v30.6.
  8. Android 17No boot layout change found. Zygisk support in v31.0.
  9. Magisk v31.1: Android 7.0 minimumAndroid 6.0 is no longer supported.
Dates are each Android version's first stable release. Sources: AOSP pages on system-as-root, vendor boot partitions, the Generic Kernel Image and the generic boot partition; Android Developers on 16 KB pages; Magisk's changelog and issue #9348.

The change that matters most when rooting is Android 13's init_boot partition. According to the Android Open Source Project, phones that launch with Android 13 keep only the GKI kernel in boot and put the generic ramdisk in init_boot. Phones upgraded to Android 13 or later keep their original layout.

So the image you patch depends on the Android version the phone launched with, not the one it runs today: a Pixel 6 running Android 17 still uses boot.img. Some phones break the rule (the Nothing Phone (2), the POCO F5, several Redmi Note 13 and 14 models and several Motorola phones launched with Android 13 or 14 without init_boot; we checked the Xiaomi ones in their firmware), which is why the device guides list the image per model. The rule of thumb: if your firmware contains init_boot.img, patch that.

A few devices keep the ramdisk in vendor_boot instead. Installing Magisk there was added in the v30.3 pre-release and first shipped in stable v30.6; Magisk's guide flashes it with fastboot flash vendor_boot. Magisk does not publish a list of devices that need it. Devices with no ramdisk in any boot image use Magisk in recovery mode, as the patching guide explains.

Android 17

Android 17 (API 37) was released on June 16, 2026, first for Pixel phones, with other devices following through 2026. Magisk v30.7 has no Android 17 changelog line. Magisk issue #9928 reported a Pixel 7 on an Android 17 build returning to fastboot with a v30.7-patched init_boot. In the same thread a project collaborator reported Magisk “works perfectly” on a Pixel 6a on that build and suspected modules, another user withdrew a similar Pixel 8 Pro report after finding a module at fault, and a third rooted a Pixel 11 Pro XL with v30.7. The issue was closed without a code change. The v31.0 pre-release then added Android 17 support for Zygisk, and the stable v31.1 includes it.

Practical advice: install v31.1. If the phone returns to fastboot, flash the stock init_boot.img and try again with modules disabled. If you stay on v30.7 and Zygisk modules fail on Android 17, update to v31.1. Older builds are in the release archive. GrapheneOS is not supported by Magisk.

Android 16 QPR2

Android 16 QPR2 changed the binary format of the SELinux policy. Magisk v30.2 and older bootloop straight back to fastboot on it (“magiskinit: Fail to load policy”, issue #9348). The fix shipped in the v30.3 pre-release and in stable from v30.6. Use v30.7 or newer: v30.7 also updates MagiskInit and Zygisk for QPR2, and v31.1 includes those changes.

Updating Android on a rooted phone

If a new Android version needs a newer Magisk, update the Magisk app first, then update Android. On A/B phones you can keep root through the update by restoring images, installing the update, and installing Magisk to the inactive slot; see keeping root after an update. On other phones, flash the new firmware's stock image patched with the current Magisk.

Common questions

Does Magisk work on Android 17?

Yes. The current stable release, v31.1, includes the v31.0 change “[Zygisk] Support Android 17 (API 37)”. The older v30.7 has no Android 17 changelog line, but in issue #9928 a project collaborator reported it working on a Pixel 6a, and another user rooted a Pixel 11 Pro XL with it.

Which Magisk should I use on Android 6.0?

v30.7, the last stable release for Android 6.0 (the v31.0 pre-release also still runs on it). v31.1's changelog says “Drop support for Android 6.0; Android 7.0 is now the minimum supported version”, and its app is built for Android 7.0 (API 24) and newer. Don't install v31.1 on Android 6.0.

Can I root Android 5 (Lollipop) or 4.4 (KitKat) with Magisk?

Only with old versions. v26.0 raised the minimum to Android 6.0, so v25.2 (July 2022) is the last release for Android 5.0 and 5.1. v23.0 removed “all pre Android 5.0 support”, so v22.1 (April 2021) is the last for Android 4.2 to 4.4. Both are old and unmaintained; get them only from the official GitHub releases.

I upgraded to Android 13 or later. Do I patch init_boot now?

Not necessarily. Android's documentation puts the ramdisk in init_boot only on phones that launched with Android 13; upgraded phones keep their old layout. Look inside your firmware: if it contains init_boot.img, patch that, otherwise patch boot.img. The patching guide and compatibility checker help you decide.

My phone bootloops to fastboot after an Android update. Is Magisk too old?

Possibly. The best-known case is Android 16 QPR2, where Magisk v30.2 and older fail with “magiskinit: Fail to load policy”. Flash the stock image for the new build to boot again, update the Magisk app to v31.1, then patch the new image. See bootloop after flashing.

Does Magisk work on Android betas and QPR betas?

Often, but nobody promises it. Magisk adds support after Google publishes a change, and new SELinux or Zygote changes can break it until then. On a beta, keep the stock image for that exact build so you can unroot, and use the newest Magisk release.

Should I update from v30.7 to v31.1?

On Android 7.0 or newer, v31.1 is the current stable release and the one to install, especially on Android 17. Know what changes first: it removes app hiding and root pop-ups (access is granted ahead of time in the Superuser tab). If you depend on hiding the Magisk app, v30.7 is the last release with it. Read the release notes before updating.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page