GETDroidTipsGETDroidTips

Trending

Download Magisk v31.1 APK (Latest 2026) and Root Any Android Phone

Download the latest Magisk v31.1 APK from the official source, see what’s new, and follow our step-by-step guide to root your Android phone in 2026.

Stephen Ojo

Updated 10 min read

Share

The latest version of Magisk is v31.1, released on October 24, 2026. This page has the official download links for the Magisk APK, what’s new in the latest release, and step-by-step instructions to root your Android phone with Magisk, whether you’re rooting for the first time or updating an existing install.

Quick note if you searched for “Magisk Manager”: there’s no separate Magisk Manager app anymore. Since v22, Magisk and Magisk Manager have been a single app, simply called Magisk. The same APK installs the app on your phone and contains everything needed to root it, so ignore any site that still offers “Magisk Manager 8.0.7”.

Download latest Magisk APK v31.1 and root Android

Magisk latest version at a glance

Latest version Magisk v31.1
Release date October 24, 2026
Developer John Wu (topjohnwu)
File Magisk-v31.1.apk
Minimum Android version Android 7.0 Nougat
Android 17 support Yes (from v31.0)
Price Free and open source

Download Magisk APK (latest and older versions)

Only download Magisk from its official GitHub page. Every link below points to the official release files. Copies on other websites are a common way to spread malware, and an app with root access can do anything on your phone.

You’ll find every release ever published on the Magisk releases page. Older versions are only worth using if the latest one doesn’t work on your device. If your phone runs Android 6.0, v31.0 is the last version that supports it.

Advertisement

What’s new in Magisk v31.1

Version 31.1 is a big cleanup release, and a few of the changes affect how you use the app day to day:

  • Android 7.0 is now the minimum. Support for Android 6.0 has been dropped.
  • The option to hide the Magisk app (repackaging it under a random name) is gone, along with the stub app. Magisk also no longer reinstalls the app on its own if you uninstall it.
  • Apps no longer get a pop-up asking for root. You now grant root access ahead of time from the Superuser tab.
  • One patching flow now handles raw images, OTA zips, factory image zips and Samsung tar files, and it shows live progress and download speed while it works.
  • On Google Pixel phones, the app can suggest and fetch the official firmware for your build, so you don’t have to hunt for the boot image yourself.
  • Support for Googlebooks (Aluminium OS) and devices that use Headless System User Mode.
  • Several MagiskBoot fixes, including keeping Samsung’s signatures intact when a boot image is repacked.

What changed in Magisk v31.0

  • A completely redesigned app built with Jetpack Compose and Material 3
  • A built-in terminal for flashing modules and running action scripts
  • The ability to extract a boot image straight from an online OTA link
  • Zygisk support for Android 17
Older Magisk changelogs (v30.x)

v30.7 (February 23, 2026): support for Android 16 QPR2 in MagiskInit and Zygisk, support for Android XR and some Nubia phones, and MagiskSU now keeps Linux capabilities by default.

v30.6 (December 1, 2025): reverted a MagiskInit change that could cause bootloops.

Advertisement

v30.5: better command-line argument parsing and proper support for property overrides in resetprop.

v30.4: fixes for several MagiskSU bugs.

v30.3: support for installing Magisk to the vendor_boot partition, the new Android 16 QPR2 sepolicy format, and more of the core rewritten in Rust.

v30.2 and v30.1: module mounting fixes and an option to restrict Linux capabilities for root.

v30.0: module handling and compression code moved to Rust, plus general bug fixes.

The full history is in the official Magisk changelog.

What is Magisk?

Magisk is a free, open-source tool for rooting Android phones. John Wu (topjohnwu) first released it in 2016, and it soon replaced SuperSU as the standard way to root. Magisk gives you root access without touching the system partition, which is why it’s called a “systemless” root. Instead, it patches your phone’s boot image (or init_boot or recovery image, depending on the device) and loads its changes when the phone starts up.

The Magisk app is where you manage everything after rooting. You can install Magisk itself, update it, choose which apps get root access, add modules and uninstall it all again.

Magisk features

  • Systemless root. Because the system partition stays untouched, it’s easier to keep your phone working normally and to remove root later.
  • MagiskSU. Root access is granted per app from the Superuser tab, so you decide which apps get it.
  • Magisk modules. Modules change your phone’s behavior without editing system files. There are modules for fonts, emojis, audio, performance tweaks and much more.
  • Zygisk. Zygisk lets modules run code inside apps. Many popular modules depend on it.
  • DenyList. DenyList stops Magisk’s changes from loading in the apps you choose.
  • Keeps root through OTA updates. On phones with A/B partitions, Magisk can install itself to the inactive slot after a system update, so you stay rooted.

One thing has changed since older guides were written: MagiskHide no longer exists. It was removed in Magisk v24 and replaced with Zygisk and DenyList. DenyList alone won’t hide root from banking apps or Google’s Play Integrity checks, and an unlocked bootloader is enough for many apps to refuse to run. If you depend on banking or payment apps, check whether they work on rooted phones before you start.

Before you install Magisk

  • Unlock the bootloader. Magisk can’t be installed on a phone with a locked bootloader, and unlocking it wipes all your data.
  • Back up your data. Copy your photos, files and app data somewhere safe first. On Samsung phones, the first install also requires a full wipe.
  • Get your phone’s stock firmware. You’ll need the boot image (or the full firmware package) for the exact build your phone is running now.
  • Set up ADB and Fastboot on your PC. Install the Android USB drivers, then follow our guides to install ADB and Fastboot on Windows or on Mac.
  • Turn on Developer options. Enable Developer options, then turn on OEM unlocking and USB debugging.

Rooting your device may void its warranty, and on Samsung phones it permanently trips the Knox warranty bit. GetDroidTips is not responsible for any damage to your device from following this guide. Proceed only if you are comfortable with the steps involved.

Watch the video on how to install Magisk and root your phone

How to root Android with Magisk (patch boot image method)

This is the method the Magisk developer recommends, and it works on most phones apart from Samsung, which has its own section below.

Step 1: Install the Magisk app and check your device

Download the latest Magisk APK from the links above and install it like any other app. Open it and look at the Ramdisk line on the home screen. If it says Yes, you’ll patch the boot image. On newer phones that launched with Android 13 or later, this is usually init_boot.img. If it says No, you’ll patch the recovery image instead. The Magisk in recovery section below explains what changes in that case.

Step 2: Give Magisk the stock image

Copy your phone’s stock boot.img or init_boot.img to the phone. Since v31, you can also select a complete OTA zip, payload.bin file or factory image zip, and Magisk will pull out the right image by itself. On a Pixel, you can let the app download the matching factory image for you.

Step 3: Patch the image

  1. Tap Install on the Magisk card.
  2. If you’re patching a recovery image, turn on Recovery Mode.
  3. Choose Patch firmware / image, then pick your file with Select from storage or paste a direct link with Enter image URL.
  4. Start the installation and wait for it to finish. Magisk saves the patched file in your Download folder with a name like magisk_patched-[version]_[random].img.

Patch boot image in the Magisk app

Step 4: Copy the patched image to your PC

Connect the phone over USB and pull the file to your computer with ADB:

adb pull /sdcard/Download/magisk_patched-[version]_[random].img

Use ADB rather than dragging the file across in Windows Explorer. MTP transfers are known to corrupt large files.

Step 5: Flash the patched image in Fastboot

Reboot the phone into Fastboot (bootloader) mode, then flash the patched file to the partition it came from:

fastboot flash boot magisk_patched-[version]_[random].img

If you patched init_boot.img, use fastboot flash init_boot instead. For a patched recovery image, use fastboot flash recovery.

Step 6: Reboot and finish setup

fastboot reboot

Open the Magisk app once the phone boots. If it asks for additional setup, accept and let it reboot again. When the home screen shows a version number next to “Installed”, your phone is rooted.

Check Magisk installed status

Always patch the image on the same phone you’re rooting. Never flash a patched image someone else made, even for the same model, because it can leave your phone unable to boot.

How to install Magisk on Samsung phones

Samsung phones need a few extra steps. Rooting permanently trips Knox, and the first install requires a full data wipe.

  1. Turn on OEM unlocking in Developer options, boot into Download mode and long-press Volume Up to unlock the bootloader. This wipes the phone.
  2. Download the full stock firmware for your exact model and copy the AP_...tar.md5 file to the phone.
  3. In Magisk, tap Install, choose Patch firmware / image and select the AP file.
  4. Pull the patched magisk_patched-...tar to your PC with ADB.
  5. Boot into Download mode and flash the patched file as AP, along with the BL, CP and CSC files from the same firmware. Use CSC, not HOME_CSC, because the first install needs a wipe. Magisk’s official guide uses the samloader tool for this step, and Odin is the usual Windows alternative.
  6. After the phone boots, install the Magisk app again and let it finish setup.

Magisk in recovery (devices without a boot ramdisk)

If the Magisk app shows Ramdisk: No, Magisk has to be installed to the recovery partition. On these phones, a normal power-on boots without root. To boot with Magisk, use your phone’s recovery key combination and let go of the buttons as soon as the splash screen appears. To open the real recovery menu, keep holding Volume Up instead. You can’t use a custom recovery like TWRP to install or update Magisk on these phones.

Can you still flash Magisk with TWRP?

Older guides tell you to rename the APK to a .zip and flash it in TWRP. The Magisk developer no longer supports installing this way, and it often fails on modern phones, so use the patch method above instead. TWRP is still useful for Nandroid backups, and if you’re moving over from an older root tool, read our guide to switch from SuperSU to Magisk first.

How to update Magisk

If you already have Magisk, you don’t need to repeat the steps above. Install the new APK over the old app, open it, tap Install on the Magisk card and choose Direct Install. Reboot when it’s done. This is the update method the developer recommends.

How to uninstall Magisk and unroot

  1. Disable and remove all your Magisk modules first.
  2. Open the Magisk app and tap Uninstall Magisk.
  3. Choose Complete Uninstall. The phone reboots without root.

Uninstall Magisk from the app

If you can’t open the app, rename the Magisk APK to uninstall.zip and flash it from a custom recovery. Our separate guide on how to uninstall Magisk and its modules covers more cases.

Magisk FAQ

What is the latest version of Magisk?

Magisk v31.1, released on October 24, 2026. It’s free to download from the official GitHub page.

Is Magisk Manager the same as Magisk?

Yes. Magisk Manager was merged into the main Magisk app in v22, so now there’s one APK called Magisk. Version numbers like “Magisk Manager 8.0.7” belong to the old separate app and are years out of date.

Does Magisk work on Android 17?

Yes. Magisk v31.0 added Zygisk support for Android 17, and v31.1 is the recommended version.

Is Magisk safe to use?

Magisk itself is open source and widely trusted, as long as you get it from the official GitHub page. The bigger risks come from what you do with root, such as flashing a patched image meant for another phone or installing untrusted modules.

Can Magisk hide root from banking apps?

Not on its own anymore. MagiskHide was removed in v24, and DenyList only stops Magisk’s changes from loading in the apps you choose. Many banking and payment apps check Google’s Play Integrity, which often fails on any phone with an unlocked bootloader.

Why don’t apps ask me for root permission anymore?

Magisk v31.1 removed the pop-up root requests. Open the Superuser tab in the Magisk app and grant root to the apps you want.

My phone is stuck in a bootloop after installing Magisk. What now?

Flash the original, unpatched boot or init_boot image back in Fastboot to get the phone booting again. Our Magisk bootloop fix guide walks through it step by step.

Written by

Stephen Ojo

Fascinated by tech in all dimensions, and likes to tell people what he knows of it. Head Chemist at <a href="https://techyne.com" rel="nofollow">Techyne</a>. Also develops Android apps.

Share

Leave a Comment

Share your thoughts, questions, or extra tips with other readers.

Comments are reviewed before appearing on the site.