Requirements: 5.0 and up | ROOT
Overview: installation Magisk will give you ROOT, a super powerful Systemless Interface, Magisk Modules support, and hide from dozens of integrity tests like SafetyNet!
100% fully open source and easy to build!
Allow you to do any system (vendor) modification without actually meddling 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, transfer, Install Magisk Modules from the community driven online Magisk Module Repo.
Allow you to do any modifications to system properties, including read-only props.
This is besides used on 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 not yet have Magisk installed, it is strongly suggested to upgrade directly via Magisk Manager
Instructions for installation the first time are bestowed below:
If you plan to flash a custom kernel, flash it AFTER installation Magisk
Make sure to remove any other root, your best bet would be restoring your boot image back to stock
Via custom recovery:
transfer 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 mechanically , please install/upgrade it manually!
Via Magisk Manager (Only support v14.0+):
This method does not need root, and besides does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you besides 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 boot. Here is the command if exploitation fastboot:
fastboot flash boot /path/to/patched_boot.img
Remember Magisk Zygisk and Riru are incompatible so if you have any modules of Riru, don’t update to this build. Lsposed has an experimental build on it’s wire group and more and more Riru based modules will eventually be compatible with Zygisk. besides remember Zygisk != magiskhide. Magiskhide is done now from magisk and everything will be done through deny lists and they are open to any apps.
If you want to flash magisk through custom recovery, just rename the apk’s extension to zip and it’ll be a flashable zip file.
– Make Zygisk survive fertilized ovum restarts
– Fix crashes when Magisk environment was not properly setup. This
will fix the crashes experient after installation Magisk with patching
This app has no advertisements
Need help? Join our community and get assistance!.