Requirements: 4.2+ | ROOT
Overview: Installing Magisk will give you ROOT, a super powerful Systemless Interface,
Magisk Modules support, and hide from tons of integrity tests like SafetyNet!
100% fully open source and easy to build!
Allow you to do any system (vendor) modification without actually tampering the partitions.
Anything can be loaded with Magisk systemless-ly!
MagiskSU: Open Source Root Solution
Root your device with MagiskSU, based on phh’s Superuser, which is based on CM Superuser.
MagiskSU Root Management, Upgrade Magisk, Manage MagiskHide lists
Manage, Upgrade, Download, Install Magisk Modules from the community driven online Magisk Module Repo.
Hide Magisk from detections: Google SafetyNet, enterprise / bank system integrity checks, game tamper checks etc.
Allow you to do any modifications to system properties, including read-only props.
This is also used along with magiskhide to trick various device status sent from the bootloader
(Optional) Remove AVB 2.0, dm-verity, forceencrypt.
Unlock partitions blocks to support remount to rw
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!
Via Magisk Manager (Only support v14.0+):
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
– [MagiskSU] Support component name agnostic communication (for stub APK)
– [MagiskBoot] Set proper header_size in boot image headers (fix vbmeta error on Samsung devices)
– [MagiskHide] Scan zygote multiple times
– [MagiskInit] Support recovery images without /sbin/recovery binary. This will fix some A/B devices unable to boot to recovery after flashing Magisk
– [General] Move acct to prevent daemon being killed
– [General] Make sure “–remove-modules” will execute uninstall.sh after removal
– Hide Magisk Manager with stub APKs on Android 9.0+
– Allow customizing app name when hiding Magisk Manager
– Generate random keys to sign the hidden Magisk Manager to prevent signature detections
– Fix fingerprint UI infinite loop
This app has no advertisements
Magisk Manager v7.4.1-7fa2625a:
Magisk Uninstaller (2019.11.02):