Latest Magisk Version: v12.0
Latest Magisk Manager Version: v4.3.1
Hello, welcome to the official Magisk Release / Announcement thread!
Magisk can ROOT your device, along with standard common patches.
It packs with a super powerful Universal Systemless Interface, allowing unlimited potential!
Magisk modifies boot image and add files to /data and /cache
It touches your /system partition only if root installed in /system is detected!
- 100% fully open source and easy to build!
- Magic Mount:
Allow you to do any system (vendor) modification without actually tampering the partitions.
- MagiskSU: Open Source Root Solution
Root your device with MagiskSU, based on phh's Superuser, which is based on CM Superuser.
- Magisk Manager:
MagiskSU Root Management, Install / Upgrade Magisk in-app,
Manage, Upgrade, Download, Install Magisk Modules within a few taps.
- Magisk Hide:
Hide Magisk from detection, including SafetyNet, which is used in Android Pay, Pokemon GO, Mario Run etc.
Allow you to do any modifications to system props (build.prop), including read-only props.
It is also used for tricking the bootloader state, and (for Samsung) the KNOX state
- Multiple Entry Points:
Provide several entry points to developers, reliably pausing the boot process before everything is done.
Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
- Standard Stuffs:
Remove dm-verity, forceencrypt; includes a super complete busybox to guarantee consistent behaviour, and can also be toggled to be used universally.
You are not forced to use MagiskSU if you're only aiming other features
However, the only other choice is systemless SuperSU
It will attempt to remove any other root, and install MagiskSU by default
- Anything that previously modifies /system can be loaded with Magisk. I ported Xposed and ViPER4Android just as an example.
- Use apps/features that uses Google's SafetyNet detection
- 100% systemless custom roms (take a look at our 100% Systemless Magisk ROM)
- (WIP) Universal Multirom for all Magisk supported devices (Proof Of Concept Video)
Before Magisk installs anything on your device, it will create a boot image backup in /data/stock_boot_<sha1>.img.gz
If anything goes wrong (e.g. bootloop), you can either use the uninstaller (recommended) or decompress the backup and manually restore your boot image
It should ALWAYS bring your device back to life (suppose you have a custom recovery that can decrypt your /data)
If you're already rooted with MagiskSU or Latest Official Systemless SuperSU
- Install/upgrade Magisk Manager from Play Store
- Install/upgrade Magisk as prompted in the application
- Reboot and you're done!!
- (Recommended) Restore your boot image back to stock (flash uninstaller if Magisk is previously installed)
- Download the latest Magisk zip file
- Reboot to a custom recovery
- If you choose to use SuperSU (only support Android 6.0+), flash SuperSU in systemless mode now
- Flash Magisk zip
- Reboot. Update the stub Magisk Manager to the latest from Play Store
Latest Uninstaller (Support v1+)
Magisk Manager | (direct link)
To all developer: please check out the WIKI for common issues you might face, for custom rom devs too!
- Q: I am losing root randomly!
A: In some custom roms (known: LineageOS), enabling the Magisk busybox will make root unstable
If you experience root loss issue, disable busybox in MagiskManager
- Q: Safety Net fails after enabling MagiskHide
A: Magisk can only hide Magisk core features, for Magisk modules it depends on what the module does.
If your ROM itself is not able to pass SafetyNet, then there is nothing Magisk can help.
Your best bet is 100% stock ROMs, because your phone manufacturer is forced to release a device passing CTS.
- Q: My device is not supported!
A: Please open an issue on Github, along with your boot image uploaded. No boot image, no fix.
- Sony Devices: If you're using stock kernel, it is using Sony's special ELF format.
Magisk will repack it to standard AOSP format, which requires your device to be unlocked
- Some of the ASUS devices requires boot image signing, search the forums and sign them yourselves.
Currently Known Issues (v12.0):
- Pixel / Pixel XL: WIP
- Magisk Manager CANNOT be placed in adoptable storage, or superuser will not work
- MagiskSU does not support multiuser: WIP
- MagiskSU does not work on Android O preview: WIP
I spent endless hours to create Magisk. If you like my work, feel free to donate.Sources
https://github.com/topjohnwu/Magisk (Magisk Core Scripts and Boot Image patching)Special Thanks
https://github.com/topjohnwu/magiskpolicy (sepolicy tools used in both Magisk and MagiskSU)
https://github.com/topjohnwu/MagiskSU (Open source root)
https://github.com/topjohnwu/selinux (libsepol, libselinux for sepolicy-injection and Superuser)
https://github.com/topjohnwu/ndk-compression (all compression libraries used in MagiskBoot)
https://github.com/topjohnwu/MagiskManager (Magisk Manager)
- @phhusson for his advice with sepolicy and his sepolicy injection tool, boot image tools, hide su tools, superuser
- @Chainfire for many bits of shell script code, his supolicy in older versions, and the complete documentation How-To SU
- @nkk71 for his original resetprop
- @osm0sis for his shell script for image/zip size detection and unSU, also providing numerous support for all kinds of boot image unpacking knowledge
- @tobias.waldvogel for the original code to unpack Sony ELF boot images (and_boot_tools project)
- @digitalhigh and @DVDandroid for massive contributions to Magisk Manager
- @Captain_Throwback for being the No.1 supporter, testing and finding bugs all the time
- @YashdSaraf for his super complete Busybox to obtain a reliable environment