Latest Stable Magisk Version: v16.0
Latest Magisk Manager Version: v5.8.3
Hello, welcome to the official Magisk Release / Announcement thread!
Installing Magisk will give you ROOT, a super powerful Systemless Interface,
Magisk Modules support, and hide from tons of integrity tests like SafetyNet!
Magisk does NOT have a website. Do NOT download Magisk from unofficial sites.
Official Links: Magisk Github Release
- Open Source:
100% open source and easy to build on all Google supported platforms.
- Magic Mount:
Modify system (vendor) without tampering the partitions.
Unleash your device's root access.
Hide Magisk from detections: Google SafetyNet, enterprise / bank system integrity checks, game tamper checks.
Modify or delete any system properties, including read-only props.
- Online Module Repo:
Install Magisk Modules from the community driven Magisk Module Repo.
- If you already have Magisk installed, it is strongly recommended to upgrade directly via Magisk Manager
- Instructions for installing the first time are presented below:
- If you plan to flash a custom kernel, flash it AFTER installing Magisk
- Make sure to remove any other root, your best bet would be restoring your boot image back to stock
- Via custom recovery:
- Download the latest Magisk zip file
- Reboot to a custom recovery and flash the flashable zip
- Reboot to system, and check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install/upgrade it manually!
- This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
- Install the latest Magisk Manager
- If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
- Press Install > Install > Patch Boot Image File, and select your stock boot image file
- Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
- Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
- Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
- If you experience any bugs, check whether there is a newer version in beta, as the bug might have already been fixed. Please follow the instructions in Beta Thread OP to report a bug properly.
- Please read this if you plan to use the "Hide Magisk Manager" feature: When using the hide Magisk Manager feature, the app will generate a random package name, repackage, and replace itself. Once you've repackaged Magisk Manager, please ALWAYS upgrade the app within Magisk Manager itself. If you plan to restore to official Magisk Manager, either use the Restore Magisk Manager option in settings, or uninstall the repackaged manager and manually reinstall the official APK.
- MagiskHide relies on ns proc mnt file descriptor introduced in Linux 3.8. Even if you are running a kernel lower than 3.8, it is very likely this feature is already backported. If your kernel lacks this feature, you can build (or ask your custom kernel dev) with some additional patches. The relevant patches are: set CONFIG_NAMESPACES=y in defconfig, and apply this patch. More info: Namespace file descriptors (2010 original article)
- Additional info are presented below:
- Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
- Some Motorolla devices' stock kernel ships with a flawed F2FS implementation. Change to a custom kernel with the fix or format data to ext4.
- Magisk Manager CANNOT be placed in adoptable storage
- Q: WebView is crashing on my device when I enable MagiskHide
A: It's a bug in your ROM, please ask your ROM developer to include this commit to fix the issue
- Some of the ASUS devices requires boot image signing, search the forums and sign them yourselves.
- Sony Stock ELF Boot: Please refer to the info when flashing Magisk in custom recovery
- Q: Safety Net isn't working!
A: If your ROM itself is not able to pass SafetyNet, then there is nothing Magisk can help.
Your best bet is to run 100% stock ROMs, since your phone manufacturer is forced to release a device passing CTS.
- I spent endless hours on Magisk. If you like my work, feel free to donate.
- @phhusson for the original sepolicy injection tool, boot image tools, superuser, hide su tools
- @Chainfire for many shell script code, his supolicy in older versions, and the complete documentation How-To SU
- @nkk71 (RIP) for the original resetprop
- @osm0sis for unSU, addon.d hack, boot image unpacking knowledge
- Every contributor of Magisk Manager
Removed Files Download Count: 25,490,945
v1: 8746 v2: 2251 v3: 3790 v4: 1220 v5: 2914
v6: 138838 v7: 119744 v8: 116796 v9: 203836 v10.2: 215176
v11.1: 573322 v11.6:438886 v12.0: 3263706
1300: 274438 1310: 1018692 1320: 403556 1330: 1844372
1350: 39188 1360: 69874 1400: 4456314
1410: 11512 1420: 112020 1437: 247988 1455: 30652
1456: 253042 1468: 85978 1500: 434572 1510: 460120
1520: 927436 1530: 218164 1531: 3143686 1540: 97368
1600: 6043710 1610: 87628 1620: 140382