Download Magisk v31.1
Magisk is published only on its official GitHub repository. This page links straight to the current release, lists the checksum GitHub publishes for it, and shows our own check of the file. We do not host or mirror any files.
Last updated 7 sourcesHow we check pages
What changed from v30.7 to v31.1
v31.1 is the current stable release: GitHub marks it as Latest, and the Magisk app's stable update channel offers it. It follows the v31.0 pre-release (September 4, 2026) and changes how the app works:
- Android 7.0 or newer. v31.1 drops Android 6.0. On Android 6.0, stay on v30.7.
- No root pop-ups. Apps no longer ask for root when they need it; you grant access ahead of time in the app's Superuser tab.
- No app hiding. The option to hide the Magisk app under another name, and the stub app, are gone. The release notes suggest uninstalling the Magisk app once root access and modules are set up.
- Easier patching. The app can patch straight from a factory image zip or a link, and on Pixels it offers the matching factory image. (v30.7 already reads full OTA zips and
payload.bin.) - A new app. v31.0 rewrote the interface and added a built-in terminal for module installs and module actions, plus Android 17 support for Zygisk.
Already rooted with v30.7? Read moving from v30.7 to v31.1 before you update, especially if you hid the app: unhide it first.
Which file to download
Each GitHub release has a normal APK named after its version and an app-debug.apk. Magisk's README accepts bug reports only from debug builds, and its build documentation says switching to an official debug build (and reinstalling Magisk from it) turns off the signature check described below. Everyone else wants the normal APK.
Which APK fits you?
| Feature | Magisk-v31.1.apk | Magisk-v30.7.apk | app-debug.apk |
|---|---|---|---|
| Runs on Android 6.0 | No | Yes | PartlySame as its release |
| Root permission pop-ups | NoGrant in Superuser tab | Yes | PartlySame as its release |
| Hide the Magisk app | No | Yes | PartlySame as its release |
| Patch from a factory zip or a link | Yes | PartlyOTA zip and payload.bin only | PartlySame as its release |
| Daemon rejects non-matching Magisk apps | Yes | Yes | NoCheck turned off |
| Accepted for bug reports | No | No | Yes |
| For everyday use | Yes | Yes | NoDevelopers and bug reports |
Recent releases
Recent Magisk releases
- v29.0Large internal refactoring; stable
- v30.3 (pre-release)Install into
vendor_boot; Android 16 QPR2 sepolicy - v30.6Stable; reverts a change that could cause bootloops
- v30.7Previous stable; the last release that supports Android 6.0
- v31.0 (pre-release)New app, built-in terminal, Zygisk on Android 17
- v31.1Current stable: Android 7.0 minimum, no root pop-ups, no app hiding
Only use the official APK
Many websites offer "Magisk" downloads. Magisk's README says GitHub is the only source for official downloads. Magisk's build documentation explains that release builds use the certificate of the key that signed the official APK as a reference, and Magisk's root daemon rejects and uninstalls Magisk apps that don't match, to protect users from modified APKs.
"Magisk Manager" is an old name. Since v22.0 the manager and Magisk itself are a single app, the Magisk app, so there is nothing separate to download.
Verify the download
Compare the file's SHA-256 hash with the value above, which is the digest GitHub lists for the release asset:
Our check of v31.1 on October 26, 2026
We downloaded Magisk-v31.1.apk from the GitHub release on a Linux x86_64 machine and ran the same checks. This is the unedited output. The hash matches the release digest above, and the APK is signed by the same John Wu certificate as v30.7: the fingerprints are identical. This was a check of the download only, not an install on a phone.
Our earlier check of v30.7 on October 26, 2026
We downloaded Magisk-v30.7.apk from the GitHub release on a Linux x86_64 machine and checked it. This is the unedited output. The hash matches the release digest, and the APK is signed by John Wu's certificate. To check the signer yourself, compare the certificate fingerprint with the one below. This was a check of the download only, not an install on a phone.
What to do with the APK
- First install: install the APK like any app, then follow patching a boot image (or the Samsung guide). Installing the app alone does not root the phone. See how to install Magisk to pick your method.
- Already rooted: Magisk's documentation recommends upgrading from inside the Magisk app with Install → Direct Install. See updating Magisk.
- Custom recovery users: the APK can be renamed to
.zipand flashed, but Magisk describes this method as deprecated.
Questions people ask
What is the latest version of Magisk?
Magisk v31.1, released October 25, 2026. GitHub marks it as the latest release. It needs Android 7.0 or newer; the previous release, v30.7, is the last one for Android 6.0.
Where can I get Magisk for Android 6.0?
Use v30.7, the last release that supports Android 6.0. It is still on GitHub: Magisk-v30.7.apk (11.08 MB). Its SHA-256 is e0d32d2123532860f97123d927b1bb86c4e08e6fd8a48bfc6b5bee0afae9ebd5. Don't update it from inside the app: v31.1 won't run on Android 6.0.
I updated and apps no longer ask for root. Is it broken?
No. Since v31.1 there are no root pop-ups: grant access ahead of time in the Magisk app's Superuser tab. See root not working for the details.
Android won't let me install the APK
Android blocks apps from outside the Play Store until you allow the app you opened the file with (your browser or file manager) to install unknown apps. Android asks when you open the APK; allow it for that app, then go back and install.
I installed the app. Am I rooted now?
No. The app is the tool that installs Magisk; root needs a patched boot image flashed to the phone. Next step: how to install Magisk.
Where do I download Magisk Manager?
"Magisk Manager" is the old name. Since v22.0 the manager and Magisk itself are a single app, the Magisk app, so there is nothing separate to download.
Where is the Magisk zip?
There isn't a separate one. For the deprecated custom recovery method, rename the APK to .zip. For uninstalling from a custom recovery, rename it to uninstall.zip.
Is it safe to download Magisk from other sites?
Magisk's README says GitHub is "the only source where you can get official Magisk information and downloads". A file from elsewhere may be modified. If you have one, compare its SHA-256 with the value on the GitHub release before installing.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk releases on GitHub (topjohnwu/Magisk)
- Magisk v31.1 release notes
- Magisk v30.7 release notes
- Magisk changelog (topjohnwu)
- Magisk build documentation: signing and distribution (topjohnwu)
- Magisk README: downloads and bug reports (topjohnwu)
- NetworkService.kt: update channels and the debug APK (Magisk source)
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