About Magisk Guide
Magisk Guide is an independent, unofficial reference for people using Magisk. This page explains who is behind it, how the pages are written, and how to tell us when something is wrong.
Last updated
What this site is
Magisk is developed by John Wu (topjohnwu) and contributors, and its official documentation lives in the Magisk GitHub repository. That documentation is precise but brief, and it assumes you already know things like which partition your phone uses. Magisk Guide exists to fill that gap: plain-English walkthroughs, organized by task and by phone brand, that always point back to the upstream source.
We are not affiliated with, endorsed by or connected to the Magisk project, Google, or any phone manufacturer. Magisk has no official website besides its GitHub repository and documentation.
Independence. No project, phone maker or module developer pays for coverage, and there are no affiliate or sponsored links on the site. When we recommend one module over another, the reason is on the page: who maintains it, when it was last released and what its own documentation says.
Contact. Email hello@magiskguide.com for corrections, questions about a page, or anything else. We read every message.
How pages are written
- Sources first. Every guide is based on primary sources: Magisk's documentation and changelog, Android and AOSP documentation, manufacturers' own unlock and firmware pages, and the READMEs of the projects we describe. Each page lists the sources it uses at the bottom.
- No guessing. If we can't confirm something from a source, we leave it out or say plainly that it is uncertain. We don't publish device specifications, statistics or test results we can't back up.
- AI-assisted drafting. Pages are drafted with the help of AI writing tools, then checked line by line against the linked sources before publishing.
- Checked against the code, not just the docs. Magisk's documentation is short, so claims about how Magisk behaves (file names, boot stages, command options, error messages, Safe Mode) are checked in Magisk's source code at the release tags v30.7, v31.0 and v31.1. Where the source and the documentation disagree, the page says so.
- Every status has a date. Which phones can be unlocked, which modules are maintained, which release is current: these change, so each status banner shows the day it was last checked.
- Real dates. "Last updated" on each page is the date its content last changed.
How a page is made and kept current
- 1Primary sourcesMagisk's docs, source code and changelog; AOSP; manufacturers; project repos
- 2DraftWritten with AI writing tools
- 3Check each claimAgainst the linked source, or against Magisk's source code
- 4Automated checksEvery build: links, anchors, dates, banned claims
- 5Re-checkRelease data synced from GitHub; statuses dated
What we have checked ourselves
We don't own a lab of phones, so most pages rely on the sources they cite. These are the checks we ran ourselves, with the raw output published. None of them involved flashing a phone.
| Date | What we checked | Result | Where |
|---|---|---|---|
| October 27, 2026 | Read the partition lists of 79 official update packages (40 Xiaomi, Redmi and POCO, 31 Pixel, 8 Nothing and CMF) from the makers' servers, and extracted and opened boot and vendor_boot where it mattered, each matched against the hash in the update's manifest | Settled the image to patch for the 14 Xiaomi model groups that had no source (40 packages); found 8 models that launched with Android 13 or 14 without init_boot | Xiaomi guide, raw logs and tool |
| October 27, 2026 | Downloaded Google's full Android 17 update for the Pixel 7 (build CP3A.261005.002.A1), checked it against Google's SHA-256, extracted init_boot.img with magiskboot, patched it with the v31.1 boot_patch.sh and restored it | Same single swap of init; no kernel involved; restore returns the stock file list exactly | Patching guide, raw logs |
| October 27, 2026 | Built magiskboot from the Magisk v31.1 source and ran the official APK's boot_patch.sh on Google's GKI boot image android12-5.10-2026-07_r2, then restored it | Only init is swapped for magiskinit (original kept in .backup); kernel untouched; restore returns the original init byte for byte | Patching guide, raw logs |
| October 26, 2026 | Downloaded Magisk-v31.1.apk from GitHub, hashed it and read its signing certificate | SHA-256 matches GitHub's published digest; signed by John Wu's certificate | Download page |
| October 26, 2026 | The same check on Magisk-v30.7.apk | Hash matches; same certificate fingerprint as v31.1 | Download page |
| October 26, 2026 | Behaviour described on the guides, read in Magisk's source at v30.7, v31.0 and v31.1 | Several pages corrected (see the log below) | Each page's sources |
Have you followed one of our guides on your own phone? Send your device, Android build, Magisk version and what happened to hello@magiskguide.com. With your permission we add confirmed reports, credited to you, to the page.
What we don't do
- We don't run a device test lab, and we don't claim to have tested guides on your phone. Before flashing anything, check the steps against your manufacturer's instructions and the upstream documentation.
- We don't host or mirror Magisk or any module. Download links go to the official release pages.
- We don't publish leaked keys, shared fingerprints or patched images. Magisk's documentation warns never to flash images patched on another device.
Corrections
If a page is wrong, out of date or unclear, use the Report a problem with this page button at the bottom of it, or email hello@magiskguide.com with the page address and what needs fixing. If you can, include a link to the source that shows the correct information. We check every report against the source, fix confirmed errors, update the page's date and add the fix to the log below.
In October 2026 we rewrote the site so that every page is traceable to its sources, merged pages that repeated each other, and removed content we could not verify.
Corrections log
Factual errors we found and fixed. Wording and layout changes aren't listed.
| Date | Page | What was wrong, and the fix |
|---|---|---|
| October 27, 2026 | Xiaomi, Redmi, POCO | The guide said Xiaomi phones that launched with Android 13 or later use init_boot. Their official firmware shows the POCO F5 and F5 Pro, the Redmi Note 13 5G, 13 Pro 4G and 13 Pro 5G, the Note 14 4G and 14 Pro 4G and the Redmi 14C 5G have no init_boot; they patch boot.img. |
| October 27, 2026 | magiskboot | An answer said a phone with no ramdisk in boot and no init_boot must use the recovery method. Phones like the Pixel 6 keep the ramdisk in vendor_boot, and Magisk patches their boot.img by adding a ramdisk; recovery is only for phones where the app shows Ramdisk: No. |
| October 27, 2026 | Google Pixel | The patch step used v30.7's button name. In v31.1 it is Patch firmware / image, and the app can download the factory image for your current build itself. |
| October 27, 2026 | All pages | Magisk v31.1 was described as a pre-release. GitHub now marks it as the latest release, so it is the stable version; v30.7 is now described as the last release for Android 6.0. |
| October 26, 2026 | Patching guide, root method checker | The patched file is named magisk_patched-<version code>_<random>, not magisk_patched_<random> (from MagiskInstaller.kt). |
| October 26, 2026 | Patching guide, download | v30.7 can already patch full OTA zips and payload.bin; only factory-image zips and links need v31.1. |
| October 26, 2026 | Root method checker | Magisk patches init_boot only on kernels newer than Android 12's; the checker now asks about the kernel. |
| October 26, 2026 | magiskboot | Installing into vendor_boot arrived in v30.3, not v30.6. |
| October 26, 2026 | Android versions | v30.7 supports Android 6.0, not only 7.0 and newer. |
| October 26, 2026 | Magisk vs APatch and other comparisons | APatch build 11282 was released on October 15, 2026, not October 17. An unsourced claim about APatch's module support was removed. |
| October 26, 2026 | Zygisk | Zygisk Next needs KernelSU 10940 or Magisk 26402 or newer; its README doesn't list APatch. |
| October 26, 2026 | Play Integrity | The statement that every verdict uses hardware-backed signals since May 2025 applies to Android 13 and later only. |
| October 26, 2026 | Release history | The page claimed to list every release since v24.3; six releases were missing. The description now says so, and the missing versions are named. |
| October 26, 2026 | Devices | The brand comparison said OnePlus and Nothing offer official firmware downloads; neither has a public firmware page. |
Analytics and advertising
We use Google Analytics to see which pages are read, so we know what to improve. Details are in the privacy policy. The site may show advertising in the future to cover its costs. Ads will never be placed inside instructions or disguised as download buttons.