Download Magisk Manager Latest Version 31.1 For Android 2026

What is Magisk?

Magisk is a free, open-source tool for rooting Android phones, created by John Wu (topjohnwu) in 2016. It's "systemless": instead of changing files on the system partition, Magisk patches the boot image and applies its changes while the phone starts up. Your system partition stays untouched, which makes Magisk easier to remove and easier to update than older root tools like SuperSU.

What is rooting?

Rooting gives you administrator ("root") access to your phone. Android normally stops you and your apps from changing system files. With root, apps you approve can do things like:

• Block ads system-wide or record internal audio.
• Back up apps together with their data.
• Remove preinstalled apps you can't uninstall otherwise.
• Tune the CPU, battery and display beyond what Settings allows.

What Magisk can do

• Root access (MagiskSU): choose exactly which apps get root, from the Superuser tab.
• Modules: install add-ons that change your phone's system without modifying it, and turn them off with one tap.
• Zygisk and DenyList: run code inside apps, or revert Magisk's changes for the apps you choose.
• MagiskBoot and resetprop: tools for unpacking boot images and changing read-only system properties.

What is the Magisk app?

The Magisk app is the APK you install to set up and manage Magisk. It used to be called Magisk Manager. Since Magisk v22 it's a single file that does everything: it patches your firmware to install Magisk, controls which apps get root, manages modules, and uninstalls Magisk when you're done.

From the app you can:

• See whether Magisk is installed and up to date.
• Grant or revoke root access for each app in the Superuser tab.
• Install, update and turn off modules in the Modules tab.
• Restart into safe mode if a module causes problems.
• Follow module installs and module actions in the built-in terminal.

Magisk v31 introduced a completely redesigned app, so older screenshots and videos online won't match what you see. The steps below use the current names for every button.

Download the latest Magisk version

Download Magisk 31.110.2 MB

Only download Magisk from its official GitHub page or a site that links to it, like this one. Modified "Magisk" APKs from other sources are a common way to spread malware. If you want new features early, see Magisk Beta.

Before you start

You'll need:

• An unlocked bootloader. The steps depend on your phone's brand. Unlocking usually wipes the device.
• A computer with ADB and fastboot (Android SDK Platform-Tools) and a USB cable.
• Your phone's official firmware for the exact version installed right now: the full OTA or factory image .zip, or just the image Magisk needs from it (which one?). On Pixel phones the Magisk app can download it for you.
• Android 7.0 or newer and at least 50% battery.

Planning to use a custom kernel too? Install Magisk first and flash the kernel afterwards.

How to install the Magisk app

1. Download the Magisk APK

   Tap the download button above. The file, Magisk-v31.1.apk, is saved to your Downloads folder.

2. Open the APK

   Open the file from your browser or the Files app. Android may warn that your browser isn't allowed to install apps. Tap Settings.

   

3. Allow installs from this source

   Turn on Allow from this source, then go back.

   

4. Install the app

   Tap Install and wait a few seconds.

   

5. Open Magisk and check Ramdisk

   On the home screen, find Ramdisk in the Magisk card and note whether it says Yes or No. You'll need it in the next section.

Installing the app alone doesn't root your phone. To root, patch your firmware as shown next.

Which image should you patch?

Magisk installs itself into the ramdisk, the small part of the start-up image that runs first when your phone boots. Phones keep the ramdisk in different places, so the image you patch depends on your phone. Check the Ramdisk line in the Magisk app, then find your phone below:

You flash the patched file to the partition with the same name: a patched init_boot.img goes to init_boot, a patched boot.img to boot, and so on. Not sure which one you have? Give the Magisk app the complete firmware package (OTA .zip, factory image .zip or payload.bin) and it picks the right image itself.

How to root your phone with Magisk (recommended method)

This is the method Magisk's developer recommends in the official installation guide. The Magisk app patches a copy of your phone's boot image, and you flash that copy with fastboot. Samsung phones work differently: skip to the Samsung steps.

1. Get your firmware onto the phone

   Copy the official firmware for your exact build to your phone: the full OTA or factory image .zip (or payload.bin), or just the image you need from it. The Magisk app finds the right image inside a full package by itself. On a Pixel, you can skip this step.

2. Patch it in the Magisk app

   In the Magisk card, tap Install. If you're patching recovery.img (Ramdisk: No), turn on Recovery Mode first. Under Method, choose Patch firmware / image, then pick the source:

   • Select from storage for the file you copied.
   • Enter image URL to use a direct link to an OTA or factory image.
   • Download latest Pixel factory image on Pixel phones.

   Tap Let's go. The patched file is saved in your Download folder as magisk_patched-[version]_[random].img.

3. Copy the patched image to your computer

   Use ADB rather than drag-and-drop over MTP, which can corrupt large files. Replace the file name with yours:

   adb pull /sdcard/Download/magisk_patched-31100_AbCdE.img
   

   Copy

4. Reboot into the bootloader

   adb reboot bootloader
   

   Copy

5. Flash the patched image

   Flash it to the partition the original image came from. On most phones that launched with Android 13 or later that's init_boot. On older phones it's boot.

   fastboot flash init_boot magisk_patched-31100_AbCdE.img
   

   Copy

   fastboot flash boot magisk_patched-31100_AbCdE.img
   

   Copy

   If you patched vendor_boot.img or recovery.img, use vendor_boot or recovery in the same command.

6. Optional: turn off vbmeta verification

   Some phones won't start a modified image until verified boot checks are turned off. If your phone has a separate vbmeta partition, you can flash the stock vbmeta.img from your firmware with the checks disabled. This can erase your data, so back up first.

   fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
   

   Copy

7. Restart and finish setup

   fastboot reboot
   

   Copy

   Open the Magisk app. If your data was erased, install the Magisk APK again first. When the app asks for additional setup, tap OK and let the phone restart once more. When Installed shows a version number, your phone is rooted.

If the app says Ramdisk: No (Magisk in recovery)

Some phones, mostly A-only models from late 2018 and 2019, have no ramdisk in their boot image. On these phones Magisk can only live in the recovery partition. Patch recovery.img with Recovery Mode turned on, then flash it to recovery as shown above.

After that, the way you turn the phone on decides whether Magisk runs:

• Power on normally: Android starts without Magisk.
• Hold your phone's recovery key combination, then let go of every button as soon as the phone vibrates and the logo appears: Android starts with Magisk.
• Hold the recovery key combination, then keep holding Volume up: the phone opens the real recovery.

The recovery key combination depends on the model (on a Galaxy S10 it's Power + Bixby + Volume up). On these phones you can't install or update Magisk with a custom recovery such as TWRP.

A few phones, mostly certain Xiaomi models, report Ramdisk: No but still start a patched boot image. There's no way to detect this in advance. If you want to try the normal method, keep your stock boot image so you can flash it back if the phone doesn't start.

How to root a Samsung phone with Magisk

Samsung phones don't use fastboot. Instead, you patch the AP file from Samsung's firmware in the Magisk app and flash it in download mode.

Check that your Samsung can be unlocked

In Settings → Device care, turn on Maintenance mode. Then turn the phone off and start it in download mode with your model's key combination. Look for these two lines:

Unlock the bootloader

1. Allow unlocking. In Settings → Developer options, turn on OEM unlocking.

2. Start download mode. Turn the phone off and hold your model's download mode key combination.

3. Unlock. Press and hold Volume up to unlock the bootloader. The phone erases everything and restarts.

4. Set the phone up quickly. Skip what you can, because the phone will be erased again later, but connect to the internet during setup.

5. Check the result. Turn on Developer options again. OEM unlocking should be there and greyed out. That means KnoxGuard hasn't locked the phone, and download mode now accepts modified firmware.

Patch and flash the AP file

1. Download your firmware. Get the latest official firmware for your exact model, for example with samloader-rs, a tool from Magisk's developer that downloads it straight from Samsung's servers. Unzip it.

2. Copy the AP file to the phone. Its name looks like AP_[model]_[version].tar.md5.

3. Patch it. Install the Magisk app and tap Install in the Magisk card. If the app shows Ramdisk: No, turn on Recovery Mode. Choose Patch firmware / image, then Select from storage, and pick the AP file.

4. Copy the patched file to your computer with ADB. Don't drag it over MTP, which is known to corrupt large files.

   adb pull /sdcard/Download/magisk_patched-31100_AbCdE.tar
   

   Copy

5. Flash it in download mode. Restart into download mode. Flash the patched file as AP, together with BL, CP and CSC from the original firmware. Use CSC, not HOME_CSC: the first install needs a full wipe. You can flash with samloader-rs or with an Odin-style flashing tool, which has the same AP, BL, CP and CSC slots.

6. Let the phone reset. It restarts by itself after flashing. If it asks to factory reset, agree. On a Ramdisk: No phone, start it with the recovery key combination this time so Magisk loads.

7. Finish in the app. Install the Magisk app again and open it. When it asks for additional setup, let it finish. The phone restarts once more, and then it's rooted.

Installing system updates on a rooted Samsung

A rooted Samsung phone can't install system updates over the air. To update, download the new firmware, patch its AP file in the Magisk app the same way, and flash it. This time, use HOME_CSC instead of CSC, because you're updating and want to keep your data.

How to install Magisk on a Googlebook

Googlebooks are Google's Android-based laptops. They don't use fastboot either: the Magisk app writes a patched recovery image to a USB drive, and the Googlebook reinstalls itself from that drive. Your data isn't erased, because Magisk removes the factory reset step from the image while patching it.

1. Unlock the bootloader by following Google's instructions for Googlebooks.

2. Patch the recovery image. Install the Magisk app on the Googlebook, tap Install in the Magisk card and choose Patch firmware / image. Pick Download latest Googlebook recovery image, which the app suggests automatically, or choose your own file with Select from storage or Enter image URL.

3. Choose where to write it. Under Output destination, select a USB flash drive plugged into the Googlebook. Everything on the drive is erased. You can also choose Save to file and write the image to a drive later with Google's Device Recovery Utility for Chrome.

4. Boot from the drive. Start the Googlebook in recovery mode and pick the USB drive. The Googlebook reinstalls its system from the drive, with Magisk included.

Googlebooks use A/B system updates, so you can install updates and keep root the same way as on a Pixel: see How to update Magisk.

How to install Magisk with TWRP (custom recovery)

Magisk's developer now calls this method deprecated and keeps it working with minimal effort. It only works on phones with Ramdisk: Yes, and it fails on many phones from the last few years. Use it only on older phones where patching isn't possible.

1. Install TWRP

   Flash TWRP for your exact phone model.

2. Rename the APK to .zip

   In your Files app, rename Magisk-v31.1.apk to Magisk-v31.1.zip.

   

3. Boot into TWRP

   Turn the phone off, then hold Power + Volume down (the combination varies by brand) until TWRP opens. Tap Install.

   

4. Select the Magisk zip

   Go to your Download folder and tap the Magisk .zip file.

   

5. Swipe to flash

   Swipe the slider at the bottom to confirm and wait for the install to finish.

   

6. Reboot and install the app

   Tap Reboot System. When the phone starts, install the Magisk APK if it isn't on your phone yet.

   

7. Finish the install in the app

   Open the Magisk app. When it offers to reinstall Magisk, do it from inside the app and restart. When Installed shows a version number, you're rooted. On some MediaTek phones the boot partition is locked once Android is running, so this step fails. On those, patch the boot image and flash it with TWRP or fastboot instead.

How to update Magisk

When a new version is out, the Magisk app offers to update itself. Update the app first, then tap Install in the Magisk card and choose Direct install (Recommended). Restart when it's done. This is the recommended way to update; you don't need to patch and flash an image again. Want new features before everyone else? Switch to the beta channel.

Keep root through a system update

A system update (OTA) replaces your patched boot image and removes root. On phones with A/B partitions (seamless updates) you can keep root, as long as you've never modified read-only partitions such as system or vendor yourself. Even mounting one of them as writable makes the update fail its checks.

1. Turn off Automatic system updates in Developer options so updates don't install on their own.
2. When an update arrives, open Magisk, tap Uninstall Magisk, then Restore images. Don't restart, or Magisk will be gone. Pixel phones and Googlebooks can skip this step: Google sends them a full update when it detects changes.
3. Install the system update and wait until it has completely finished, including the optimizing stage. Don't tap Restart now yet.
4. In Magisk, tap Install and choose Install to inactive slot (After OTA).
5. Go back to the system update screen and tap Restart now.

Magisk's developer only tests this routine on Pixel phones, so other brands may behave differently. On phones without A/B partitions, patch the new firmware and flash it again after updating. Samsung phones need a different routine.

How to uninstall Magisk

The easiest way is from the app: open Magisk, tap Uninstall Magisk, then Complete uninstall. Magisk restores your original boot image, removes all modules and restarts the phone.

If your phone doesn't start or the app won't open, you can flash Magisk as uninstall.zip from TWRP or flash your stock boot image with fastboot. Don't flash stock boot images on a Samsung phone, though: see why. Our full uninstall guide covers every method.

How to hide root from apps (DenyList, formerly Magisk Hide)

Older guides tell you to turn on Magisk Hide. That option was removed in Magisk v24. Today the DenyList is the closest replacement: for each app on the list, Magisk reverts its changes so the app sees an unmodified system.

1. Turn on Zygisk

   Open the Magisk app, go to Settings, turn on Zygisk, and restart your phone.

2. Enforce the DenyList

   Back in Settings, turn on Enforce DenyList.

3. Choose apps

   Tap Configure DenyList and select the apps that refuse to run on rooted phones, for example your banking app. Tap an app to expand it and make sure all of its processes are selected.

4. Clear the app's data

   Clear the storage of the app you're hiding root from, then open it again.

Some apps look for the Magisk app itself. Magisk v31.1 removed the option to hide the app under a random name. Instead, once you've granted root and set up your modules, you can uninstall the Magisk app from Android Settings. Root and modules keep working, and you can reinstall the app whenever you need to change something.

Common problems and fixes

An app says it doesn't have root. Since Magisk v31.1 there's no pop-up when an app asks for root. Open the Magisk app, go to the Superuser tab and grant access to that app.

The Magisk app crashes or freezes. Clear the app's storage in Android Settings, or uninstall it and install the latest APK again.

"There was a problem while parsing the package." The download is incomplete or your Android version is too old. Download the APK again, and check that your phone runs Android 7.0 or newer.

Installed shows "N/A". Magisk isn't in your boot image yet. Patch the firmware again and make sure you flashed it to the right partition. On a Ramdisk: No phone, Magisk only runs when you start the phone with the recovery key combination.

The phone won't start after flashing the patched image. Flash the stock image from the same firmware back to the same partition to get your phone working again (not on Samsung phones). Check that the firmware matches the exact build on your phone, and that you picked the right image. If your phone has a vbmeta partition, it may need verification turned off.

The phone is stuck on the boot logo after installing a module. Magisk protects you automatically: if the phone fails to start twice in a row, the next start uses Magisk's safe mode, with every module and Zygisk turned off. You can also turn on safe mode yourself:

• If the phone still starts: in the Magisk app, tap the power icon at the top of the home screen, choose safe mode and restart.
• With the volume button: press and hold Volume down a few seconds before the boot animation appears and let go as soon as it does. Many guides say to press it when the logo shows, which is too late for Magisk. If you keep holding until Android has started, Android's own safe mode turns on as well.
• Over USB: if USB debugging is on, connect the phone to a computer and run the command below. It removes every module and restarts the phone.

adb wait-for-device shell magisk --remove-modules

Our uninstall guide covers more ways to recover a phone that won't start.

Root doesn't work in a work profile or second user. By default only the device owner gets root. Change this under Multiuser mode in the Magisk app's settings.

Frequently asked questions