[X]Assistant

[Anais10]

Magisk - The Universal Systemless Interface download

Stable official version: 19.3 / v7.2.0

Last update of the program in the header:5.06.2019

Magisk Module Collectionsavagemessiahzine.com | Magisk Module Discussionsavagemessiahzine.com | Fans Magisk Clubsavagemessiahzine.com | Google Pay does not work!savagemessiahzine.com | GitHub module selection | Selection of XDA modules | Themes XDA Modules



For the operation of the program requires root user rights.

Short description:
An open source utility that allows you to install various system applications and mods in systemless mode and hide the root from any applications and services.

Description

An open source utility that patches the kernel and allows you to get root-rights (MagiskSU) and install various system applications and modes in systemless mode, i.e., without changing the / system partition. Allows you to run scripts at various stages of mounting and replace files (for example, build.prop) before mounting the / data partition. Allows you to hide the presence of root / unlocked bootloader / permissive-mode SELinux from various banking / email / gaming applications and payment service Android Pay, as well as receive on some devices OTA-update stock firmware.

Screenshots

About the application

• Developer: topjohnwu
  
• Russian interface: Yes
  
• System requirements: Android 5.0+, unlocked bootloader (required, because changes are made to the kernel!), Custom recovery (TWRP, CWM) and a previously made nandroid backup.
  
• Starting with Magisk 18.1, root is supported for Android 4.1, 4.2.
  

XDA home page
Github releases

Important information and FAQ

Important information:

• Magisk Manager has been removed from Google Play, so download apk from the header of this theme or from repositories.
  
• Some applications do not support root Magisk (MagiskSU) and, accordingly, can not get root-rights. Fix it can only their developers.
  
• MagiskHide, as a rule, does not work on devices with Linux kernels below 3.8, and this cannot be fixed due to the lack of components in these kernels necessary to hide the Magisk (exceptions to this rule are possible if the firmware developer ports these components into the old kernel; sometimes happens, for example, on custom based on AOSP).
  
• Magisk does not fully support installation on an adapted drive ("adoptable storage" is an SD card formatted in internal memory), otherwise the root may not work. For any problems, it is recommended to first move the manager to the internal drive and only after that ask the question in the subject.
  
• Magisk and its shell (Magisk Manager) is desirable to update simultaneously. Obsolescence of one component when updating another leads to problems.
  
• Beta versions are installed / uninstalled on the same principle as the stable ones (see below for "Installation / Uninstallation Instructions"). When switching to beta from a stable version, you need to completely remove the stable one using an uninstaller and then install the beta.
  
• Beta versions are often updated, but like any beta, they may be unstable and contain bugs. Keep this in mind and always backup before installing.
  
• Unofficial beta - the same nightly builds - are less stable than official ones, however they can be updated themselves, and official updates need to be flashed manually (since they are automatically updated only to the stable version). If you are not ready to be a tester and constantly fight with bugs, just put the official beta or stable release.
  
• What should the post look like with the question "Why can't I pass the SafetyNet check"
  
  

FAQ and instructions:

• How to install Magisk without custom recovery:by patching the kernel and its firmware. Attention: these methods are only for experienced users, who are able to reanimate the device in case of anything without custom recovery!
  
• How to install Magisk on firmware that does not run without SuperSU
  
• Dolby Atmos and ViperFX collaboration instructions for the latest Android builds (8.1+) (AOSP / Omni-based)
  
• You have a Sony device, and Magisk does not work
  
• It is impossible to flash the Magisk zip archive in recovery - the recovery gives error 1 with the message "Boot image patched by other programs! Please restore stock boot image!" ( example ).
  
  • The boot of your device has already been changed. See paras. 1, 2 instructions for installing Magisk: you need to get rid of the probably existing root and restore the stock boot (flash a clean boot.img from your firmware). Procedurefollowing(this is one of the options, other methods are possible); All questions (where can you get a clean boot.img, how to flash, etc.) ask only in the theme of the firmware of your device.Solution for Xiaomi Mi6 with MiuiPro v7.8.31 firmware
    
  
  
• It is not possible to flash the Magisk zip archive in recovery - the recovery gives the error "Unable to unpack boot image".
  
  • Make sure the bootloader is unlocked. Make sure that the device has a correctly working recovery capable of mounting partitions. Ensure that the kernel is not encrypted (if encrypted - see clause 17 of this FAQ). If everything is in order, apparently, your device is simply not yet supported, so Magisk cannot patch the kernel. Contact the developer Magisk and send him the kernel from the firmware of your device. No core - no help. There is no need to write about this topic - there is no developer here, there has not been and never will be.
    
  
  
• After flashing the Magisk beta, the device freezes for about a minute on the boot screen.
  
  • Magisk process crashed or SELinux error occurred. Reboot into recovery, remove the beta version and send the developer the log magisk_debug.log from the / data folder.
    
  
  
• Problems with SafetyNet - fails validation, CTS profile mismatch error, etc.
  
  • Make sure that the MagiskHide option is enabled in the Magisk Manager settings. Try to turn it off and on again. Did not help? Try to enable Magisk in the settings of the Magisk Core Only Mode, which disables the add. Magisk features. Didn't help too? Try upgrading to the Magisk beta.
    
  • Perhaps the problem is in some module: Magisk can only hide itself and its root, this does not apply to modules (i.e. if you have installed, say Xposed, Magisk itself cannot hide it, and you will receive an eternal error SafetyNet ). Try using special Magisk modules to bypass SafetyNet checks, this is considered the most effective tool:
    
    • Universal fix (XDA / important detail / uninstaller): universal-safetynet-fix-v1.10.1.zip(8.86 KB)
      
    • Beta version for Magisk v12 / 13:universal-safetynet-fix-v2-beta-5.zip(2.5 MB)
      
    • Beta version for Magisk v14:universal-safetynet-fix-v2-beta-5-magisk-v14.zip(2.5 MB)
      
    • Beta version for Magisk v16:universal-safetynet-fix-v2-beta-5-magisk-v16.zip(2.5 MB)
      
    • For devices Xiaomi / Jiayu you can also trymagisk-gemini-safetynet-props-v3.zip(15.37 KB)
      (XDA / instruction / simplified instruction).
      
    • More modules and script.
      
    • If universal fix did not help, try installing the moduleMagiskHide Props Configfrom the Magisk repository:MagiskHidePropsConfig-v2.3.4.zip(38.46 KB)
      (proof / XDA)
      
  • If you have Xposed installed (even if it is non-system and installed as a Magisk module), you will need to deactivate SafetyNet for successful verification (you can useRoot switchfor quick deactivation) or delete, there are no other options. If you need SafetyNet only for Android Pay, you can trysuchorsuch a way. SafetyNet check will not pass anyway, but Android Pay, if you are very lucky, can earn.
    
  • If you use SuperSU, you will need to hide the root.suhideor other solutions. Magisk does not know how to hide SuperSU (and other ruts), only its own MagiskSU (seeHiding root and passing SafetyNet). And if you installed SuperSU before installing Magisk, this can cause problems with SafetyNet. Completely remove SuperSU from the device, flip through and go to MagiskSU.
    
  • Try to translate SELinux into permissive mode, then back to enforcing and reboot the device (you can use SELinux to switch modesSELinuxToggleror other similar utilities).
    
  • If USB debugging is enabled, try turning it off (Settings ->For developers ->USB debugging) and reboot the device.
    
  • SafetyNet persistently fails the test and no recipe helps? The problem may be in your firmware; Try to find and install another kernel (if such an option is available for your device). Best of all, Magisk is friendly with fully stock firmware. And, of course, there are still devices that Magisk may not support. Anything can happen.
    
  
  
• Periodically, the root stops working.
  
  • In some custom firmware (for example, in Lineage OS), turning on Busybox in Magisk Manager-e leads to instability of the root. If the root periodically stops working, just turn off Busybox in Magisk Manager (not relevant for Magisk v13 +). Also, the reason for the instability of the root can be in the moduleUniversal SafetyNet Fix.
    
  
  
• WebView crashes when you turn on MagiskHide.
  
  • This is a bug of your firmware, write it to the developers and ask to enablefixin the assembly.
    
  
  
• Magisk Manager crashes after update.
  
  • Clear the data of the Magisk Manager application. If it does not help, remove the drop log and send it to the developer.How to remove the application error log: instructions and tools
    
  
  
• You have a Sony device, and Magisk does not work.
  
  • If a stock core is installed on your device, it uses the Sony ELF corporate format. Magisk will repack it in the standard AOSP format, but for this it is necessary that the device be unlocked. With a blocked bootloader repacking is impossible, which means that Magisk will not work either. Unlock the bootloader or forget about Magisk.
    
  
  
• You have an Asus device, and Magisk does not work.
  
  • Some Asus devices require a kernel signature. Sign it manually, for this, refer to the theme of your device.
    
  
  
• You have a Motorola device, and Magisk does not work.
  
  • On some Motorola devices out of the box is incorrectly implementedF2fs. This can be fixed by installing a custom kernel, otherwise the Magisk functionality will be limited to basic mode (core only mode) - that is, only the basic functions of Magisk will work, all third-party modules will be disabled.
    
  
  
• After installing the module for Magisk, the device went into a bootlap; Is it possible to remove the module and reanimate the device without deleting the Magisk itself?
  
  • Yes. All the modules you installed are downloaded to the / sdcard / MagiskManager folder; To get rid of any of them, just flush it into the recovery again.
    If suddenly it did not help, download and flash in recoveryMagisk Manager for Recovery Mode: mm-2018.8.1.zip(19.75 KB)
    and use it to remove the problem module (how to do it).
  
  
• Where does Magisk download its updates and modules?
  
  • In its folder in the device's memory - / sdcard / MagiskManager.
    
  
  
• Modules are not installed from Magisk Manager, an archive processing error appears.
  
  • Create a new empty folder MagiskManager in the device memory.
    
  
  
• Modules cannot be downloaded from Magisk Manager - the repository is unavailable, an error "incorrect update channel" appears.
  
  • Decision.
    
  
  
• How to remove encryption from the kernel so that Magisk is installed?
  
  • Refer to the topic of your device. For some devices, scripts are available that are being stitched in recovery (sample script for Samsung).
    
  
  
• How to get rid of Xposed for Magisk, if after installing it the device went into the bootlap?
  
  • Flash Xposed Uninstaller into RecoveryMagisk-Xposed-Uninstaller_v1.0.zip(16.23 KB)
    If it did not help, remove Xposed manually: download and flash it in recoveryMagisk Manager for Recovery Mode: mm-2018.8.1.zip(19.75 KB)
    and use it to remove the problem module (how to do it).

Installation / Removal Instructions

• If you already have Magisk installed with MagiskSU root
  
  1. Install / update the Magisk Manager app.
     
  2. Install / update Magisk from Magisk Manager, restart the device.
     
  
  
• If you have some other root, while there is no root or Magisk Manager cannot be updated from Magisk Manager
  
  1. Get rid of a third-party root, if there is one (ask questions about this in the theme of this root or in the theme of the firmware of your device).If you have SuperSU, the easiest way is to flasharchive with delete script.
     
  2. Get rid of the old version of Magisk, if it is installed, flash the uninstaller of the version of which Magisk is installed in the custom recovery. After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
     
  3. Restore the stock boot (reinstalling the boot itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device.
     
  4. Stitch archive in archive with the current version of Magisk.(If there is no custom recovery for your device, but you are ready to take a risk, see the FAQ on how to install Magisk without custom recovery.)
     
  5. Install the Magisk Manager application to manage Magisk and its modules.
     
  
  
• Uninstall Magisk v15.3 +
  
  1. Stitch in custom recovery orFlashfireuninstallerMagisk-uninstaller-20180708.zip. After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
     
  2. If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox.
     
  3. NB! Magisk makes a backup of the kernel in / data / stock_boot_ before performing the patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the kernel in TWRP and so bring the device back to life.
     
  4. If after deleting the Magisk device hangs on the splash screen, because dm-verity is activated in the sink core, restore the stock partition / system or sew an alternative root (SuperSU).

Useful links and solutions from furumchan

• Addresses where the modules are, by Goshvit
  
• All popular Safetynet description in one post, by Lord Of The Lost
  
• Removing the built-in root LOS, by Zin-Uru
  
• A way to change the minimum required version of Magisk
  
• We correct the error of the SafetyNet test
  
• The way programs give root access
  
• Built in Magisk Busybox
  
• Universal boot patching instruction using Magisk Manager
  
• Option to hide root from Qiwi wallet by aga75
  
• Hide root from Microsoft Intune corporate portal from timotv links to XDA
  
• Solutions to the problem of resetting the time zone from BoT4iK
  
• Universal Safetynet for 16 mag running on MIUI 10 beta mi5
  
• How to run su.d scripts
  
• How to replace SuperSU with MagiskSU due to SafetyNet issues
  
• Non-system Xposed for Magisk onsavagemessiahzine.comorXDA
  
• Hiding the root and checking SafetyNet XDA
  

Download:
Stable official version: 19.3 Magisk v19.3 | v7.2.0 MONSTER_PC
Official beta version: 19.0 19.0 | v7.1.1 Alex0047
Current official versionCANARY: 19.4 [19.4 (19301) | 7.2.0 (219)] Displax

Past versionsCANARY

[19.4 (19301) | 7.2.0 (218)] Displax
[19.4 (19301) | 7.2.0 (216)] Displax
[19.3 (19203) | 7.2.0 (214)] Displax
[19.3 (19202) | 7.2.0 (214)] Displax
[19.3 (19201) | 7.2.0 (214)] Displax
[19.2 (19102) | 7.1.2 (212)] Displax
v19.2 (19101) / v7.1.2 (209) Mad_Johnny
v19.0 (19005) / v7.1.1 (207) Mad_Johnny
v19.0 (19004) / v7.1.1 (206) Mad_Johnny
[19.0 (19003) | 7.1.1 (205)] Displax
[19.0 (19002) | 7.1.1 (205)] Displax
[18.2 (18122) | 7.0.0 (200)] Displax
[18.2 (18121) | 7.0.0 (199)] Displax
[18.2 (18120) | 7.0.0 (199)] Displax
[18.2 (18119) | 7.0.0 (199)] Displax
[18.2 (18118) | 7.0.0 (198)] Displax
[18.2 (18117) | 7.0.0 (197)] Displax
[18.2 (18116) | 7.0.0 (196)] Displax
[18.2 (18115) | 7.0.0 (196)] Displax
[18.2 (18114) | 7.0.0 (194)] Displax
[18.0 (19001) | 6.1.0 (166)] gjf
[17.4 (17309) | 6.0.1 (155)] gjf

Modified Magisk Versions

Magisk Manager in settings by kirill22092
Magisk Manager Mod, by Vildanoff
Magisk Manager MD2 by vsmhell
Easy mod repack Magisk 5.5.3 and magisk-installer 15.2: Р’В® Magisk - The Universal Systemless Interface (Post Alex.Strannik # 60100798)

Past versions

Version: 19.2 stable Alex0047
Version: 19.1 stable Displax
Version: 18.1 stable Alex0047
Version: 18.0 stable Alex0047
Version: 17.4 r29 UNOFFICIAL Post Cosiopey
Version: 17.4 r28 UNOFFICIAL Post Cosiopey
Version: 17.4 r27 UNOFFICIAL Post Cosiopey
Version: 17.4 r26 UNOFFICIAL Post Cosiopey
Version: 17.4 r24 UNOFFICIAL Post Thoughts
Version: 17.4 r21 UNOFFICIAL Post Thoughts
Version: 17.1 stable Post Displax
Version: 16.7 beta Post Displax
Version: 16.6 beta Post Displax
Version: 16.4 beta Post Alex0047
Version: 16.0 stable Post Displax
Version: 15.4 beta 15.4 (1540) | 5.6.0 (100) Displax
Magisk-Xposed-Uninstaller_v1.0.zip(16.23 KB)
Beta Magisk:
Official beta on XDA | Unofficial beta on xdaandRepository
Safetynet Props Mi5 Gitlab
Mi5 passing SafetyNet with unlocked bootloader! XDA

Install and uninstall past versions of Magisk

Install Magisk v14.0:

If you already have Magisk installed with MagiskSU root

1) Install / update Magisk Manager:MagiskManager-v5.4.3.apk(2.29 MB)
2) Install / update Magisk from Magisk Manager, restart the device.

If you have some other root, while there is no root or Magisk Manager cannot be updated from Magisk Manager

1) Get rid of a third-party root, if there is one (ask questions about this in the theme of this root or in the theme of the firmware of your device).If you have SuperSU, the easiest way is to flasharchive with delete script.
2) Restore the stock boot (reinstalling the boot itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device.
3) If the old Magisk is already installed, delete it by flashing the FlashFire uninstallerMagisk-uninstaller-20171123.zip(2.64 MB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
4) Flash archive with Magisk in recovery or FlashFire:Magisk-v14.0.zip(5.53 MB)
5) Install Magisk Manager:MagiskManager-v5.4.3.apk(2.29 MB)

Uninstall Magisk v14.0

Stitch in the recovery or FlashFire uninstaller Magisk-uninstaller-20171123.zip (2.64 MB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
If you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

NB! Magisk makes a backup boot to / data / stock_boot_ before performing patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the boot in TWRP and so bring the device back to life.

Install Magisk v13.3:

If you already have Magisk installed with MagiskSU root

1) Install / update Magisk Manager:MagiskManager-v5.1.1.apk(4.5 MB)
2) Install / update Magisk from Magisk Manager, restart the device.

If you have some other root, while there is no root or Magisk Manager cannot be updated from Magisk Manager

1) Get rid of a third-party root, if there is one (ask questions about this in the theme of this root or in the theme of the firmware of your device).If you have SuperSU, the easiest way is to flasharchive with delete script.
2) Restore the stock boot (reinstalling the boot itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device.
3) If the old Magisk is already installed, delete it by flashing the FlashFire uninstallerMagisk-uninstaller-20170813.zip(2.76 MB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
4) Flash archive with Magisk in recovery or FlashFire:Magisk-v13.3.zip(5.04 MB)
5) Install Magisk Manager:MagiskManager-v5.1.1.apk(4.5 MB)

Uninstall Magisk v13.3

Stitch in the recovery or FlashFire uninstaller Magisk-uninstaller-20170813.zip (2.76 MB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
If you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

NB! Magisk makes a backup of the kernel in / data / stock_boot_ before performing the patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the kernel in TWRP and so bring the device back to life.

Install and uninstall Magisk v12

Installing Magisk v12.0:
If you already have root-rights supported by Magisk (MagiskSU, Magisk phh's superuser or the official non-system SuperSU):
1) Install / update Magisk Manager:MagiskManager-v4.3.3.apk(3.44 MB)
2) Install / update Magisk from Magisk Manager, restart the device.

If you have some other root, there is no root yet, or it was not possible to install Magisk from Magisk Manager:
1) Restore the stock kernel (reinstalling the boot itselfor reinstalling the entire firmware completely - your choice). Ask questions about this in the theme of the firmware of your device.
2) If the old Magisk is already installed - delete it by flashing the uninstaller or FlashFire into the recoveryMagisk-uninstaller-20170608.zip(617.59 KB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
3) Determine the root:

• If you need easy hiding of the root and minimal problems with SafetyNet (i.e. minimum problems with Android Pay, banks, games), choose MagiskSU. In this case, you must first flash in recovery or FlashFireMagisk-v12.0.zip(6.15 MB)
  If there is no root, Magisk will install it on the MagiskSU device.
  
• If you have Android 6+ and you need exactlySuperSUflashingSuperSUBefore installing Magisk. Then to hide the root rootsuhide, because Magisk itself does not hide SuperSU. Then already flashingMagisk-v12.0.zip(6.15 MB)
  

4) Install Magisk Manager:MagiskManager-v4.3.3.apk(3.44 MB)

Uninstall Magisk v12.0: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170608.zip (617.59 KB)
After the uninstaller firmware, it is advisable to make a wipe cache and dalwick cache.
If you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.
NB! Magisk makes a backup boot to / data / stock_boot_ before performing patching<sha1>.img.gz, so if you have problems, you can always manually unpack the backup, flash the boot in TWRP and so bring the device back to life.

Install and Uninstall Magisk v11.6

Magisk v11.6 does not work on: Pixel / Pixel XL and some Asus devices. It may not work correctly (Magisk Hide and, as a result, SafetyNet will not work) on Samsung stock firmware and their mods.

Installing Magisk v11.6:
If you already have root-rights (installed MagiskSU, Magisk phh's superuser or the official non-system SuperSU):
1. Install / Update Magisk ManagerMagisk Manager_v4.2.7.apk(3.55 MB)

2. Install / update Magisk from Magisk Manager-a, reboot the device.

If you do not have root-rights yet or you could not install Magisk from Magisk Manager:
1. (Recommended) Restore stock boot.
2. If the old Magisk is already installed - delete it by flashing the uninstaller using FlashFire or FlashFire [attachment = "9940712: Magisk-uninstaller-20170320.zip"]
3. Determine the root:
- If you need easy hiding of the root and a minimum of problems with SafetyNet (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choose MagiskSU. In this case, you must first flash in recovery or FlashFireMagisk-v11.6.zip(6.15 MB)
If there is no root, Magisk will install it on the MagiskSU device.
- If you have Android 6+ and you needSuperSUflashingSuperSUBefore installing Magisk. Then to hide the root rootsuhide, because Magisk itself does not hide SuperSU. Then already flashingMagisk-v11.6.zip(6.15 MB)

4. Install Magisk ManagerMagisk Manager_v4.2.7.apk(3.55 MB)

Uninstall Magisk v11.6: Flash Uninstaller in Flash Recovery or FlashFire [attachment = "9940712: Magisk-uninstaller-20170320.zip"] If your recovery curve and uninstaller didn't help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

Install and uninstall Magisk v11.1

Magisk v1-11.1 does not work for: Sony devices with stock boot, Pixel / Pixel XL, some Asus devices. It may not work correctly (Magisk Hide and, as a result, SafetyNet will not work) on Samsung stock firmware and their mods.

Installing Magisk v11.1:
If you already have root-rights (installed MagiskSU, Magisk phh's superuser or the official non-system SuperSU):
1. Install / Update Magisk ManagerMagiskManager-v4.2.6.apk(3.52 MB)

2. Install / update Magisk from Magisk Manager-a, reboot the device.

If you do not have root-rights yet or you could not install Magisk from Magisk Manager:
1. (Recommended) Restore stock boot.
2. If the old Magisk is already installed - delete it by flashing the uninstaller or FlashFire into the recoveryMagisk-uninstaller-20170206.zip(338.04 KB)

3. Determine the root:
- If you need easy hiding of the root and a minimum of problems with SafetyNet (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choose MagiskSU. In this case, you must first flash in recovery or FlashFireMagisk-v11.1.zip(5.72 MB)
If there is no root, Magisk will install it on the MagiskSU device.
- If you have Android 6+ and you needSuperSUflashingSuperSUBefore installing Magisk. Then to hide the root rootsuhide, because Magisk itself does not hide SuperSU. Then already flashingMagisk-v11.1.zip(5.72 MB)

4. Install Magisk ManagerMagiskManager-v4.2.6.apk(3.52 MB)


Uninstall Magisk v11.1: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170206.zip (338.04 KB)
If you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

Install and uninstall Magisk v10.2

Installing Magisk v10.2:
If you have Android 6 and have a non-system SuperSU installed / have already installed Magisk v7 + with phh's superuser:
1. InstallMagiskManager-v3.1.apk(3.43 MB)

2. Install / update Magisk (and phh's superuser, if installed) from the Magisk Manager, restart the device.

If you do not yet have a root / Magisk is already below v7 /, you could not install Magisk from Magisk Manager:
1. If you already have an old Magisk installed - remove it by flashing the Magisk Uninstaller:Magisk-uninstaller-20170102.zip(338.31 KB)

2. Choose the root.
- If you need easy hiding of the root and SafetyNet worker (i.e. a minimum of problems with Android / Samsung Pay, banks, games), choosephh's superuser. In this case, you must first flash in recovery or FlashFireMagisk-v10.2.zip(5.65 MB)
If there is no root on the device, Magisk will install phh's superuser for you. You will only need to installphh's root manager.apk.
- If you have Android 6 and you needSuperSU, first (!) flashing in recovery or FlashFireSuperSU(like nonsystem!), and then flashingMagisk-v10.2.zip(5.65 MB)

3. InstallMagiskManager-v3.1.apk(3.43 MB)
4. (Optional) To hide the root, flashingsuhide, because Magisk itself does not hide SuperSU.

Uninstall Magisk v10.2: Flash Uninstaller or FlashFire Recovery Magisk-uninstaller-20170102.zip (338.31 KB)
If you have a recovery curve and the uninstaller did not help, restore the stock boot and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

Install and uninstall Magisk v9

Installing Magisk v9:
1. If you have Android 6 and installed. non-system SuperSU / already installed Magisk v7 + with phh's superuser:
- InstallMagisk Manager v2.5.apk, install / update Magisk (and phh's superuser, if installed) from the Magisk Manager, restart the device.

2. If you don’t have root / there is already a Magisk below v7 / it was not possible to install Magisk from Magisk Manager:
- If you already have an old Magisk installed - delete it by flashing it in recoveryMagisk Uninstaller.
- Choose the root.
a) If you need phh's superuser, first flash it in recovery or FlashFireMagisk v9.zipthen flashingphh-superuser-magisk-r266-2.zipand installphh's superuser.apk.
b) If you have Android 6 and you need SuperSU, first flash it in recovery or FlashFireSuperSUand then flashingMagisk v9.zip.
- InstallMagisk Manager v2.5.apk.
Uninstall Magisk v9: flashing in recovery or flashfire Magisk Uninstaller . If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

Installing and uninstalling Magisk v6-8

Magisk v8

Installing Magisk v8:
1. If you have installed of. non-system SuperSU or already installed Magisk v7 with phh's superuser:
- PutMagisk Manager v2.1.apk, install / update Magisk from Magisk Manager and restart the device.

2. If you do not have a root / Magisk is already below v7 / Magisk Manager wasn’t put Magisk Manager:
- If you already have an old Magisk installed - delete it by flashing it in recoveryMagisk Uninstaller.
- Stitch in recoveryMagisk v8.zipandphh-superuser-magisk.zip.
- PutMagisk Manager v2.1.apkandphh's superuser.apk.

Uninstall Magisk v8: stitching in recovery Magisk Uninstaller .
If your recovery curve and uninstaller did not help, restore the stock kernel and manually delete /data/magisk.img, / cache / magisk, / data / busybox.

Magisk v7

Installing Magisk v7:
1. Make a nandroid backup.
2. Return the / boot and / system partitions to the original stock state,completelyDelete the root and Xposed, if they are installed (for all information about this, look in their topics!). If you want to use a custom kernel, sew it before installing the Magisk.
3. You decide which root you want to use -SuperSUorphh's superuser. If SuperSU - immediately put it, all questions about this ask inhis topic(to work with Magisk SuperSU must be set tonon-systemBefore installing Magisk!). If you decide to use phh's SuperUser, put it after installing Magisk (see below modules for Magisk, p. 1).
4. Stitch in recoveryMagisk-v7.zip(2.18 MB)
5. To manage Magisk modules, install a shell -MagiskManager-v2.0.apk(4.13 MB)
You can also install Magisk from Magisk Manager itself (if you have custom recovery).

Uninstall Magisk v7: stitching in recovery Magisk-uninstaller-20161004.zip (412.81 KB)

Magisk v6

1. Make a nandroid backup.
2. Return the / boot and / system partitions to the original stock state,completelyDelete the root and Xposed, if they are installed (for all information about this, look in their topics!). If you want to use a custom kernel, sew it before installing the Magisk.
3. Stitch in recoveryMagisk-v6.zip(2.72 MB)
4. Choose a root for Magisk (see below modules for Magisk, p. 1).
5. To control the root and SELinux mode, install the shell -Magisk_Manager_v1.2.apk(78.07 KB)

Uninstall Magisk v6: stitching in recovery Magisk-uninstaller.zip (185.44 KB)

Discussion of the modules is now in the next branch.

It does not discuss the unlock, installation of custom recovery, replacement of cores, backups and flashing!
Handle it to the topic of your device!

For filling caps contact in QMS

User activity

Post has been editedesleer - 12.06.19, 13:51

Reason for editing: 19.4 (19301) | 7.2.0 (219)

[ilfat12]

JormovichIf there is Ruth, install TVRP with Flashify, for example, and flash Magisk from TVRP. But first make a full backup. Magisk patches ramdisk, so the first installation is needed from the recovery.
As for the fastboot, then deal with it in the branch of your device;)

[Jormovich]

ilfat12,
If you flash through the recovery, the system is not loaded. When rebooting, it hangs on the LG logo, and then it reboots again in recovery.

on xdais written, then you need to sew a CBUMP script after installing Magisk from under the recovery, but this leads to the consequences above.
I put a bootloader from Lollipop, maybe I should put KitKat.

[ilfat12]

Jormovich, what is your Android?

[Jormovich]

ilfat12,BlissPop 6.0 was, until I had to roll back to the stock Lollipop.

[chelaf]

Tell the newcomer how to enable and configure the Viper - the usual set up, but here I don’t understand - do I need to install some kind of shell?

[imageMaster]

chelaf
Yes, of course, go to Downloads, tap in the middle of the field with V4A, the list item will open, there tap on the question mark, throw on the download page apk.

[ilfat12]

chelafcan also use fullylocalized versionfromKutep0v. Only one "Help" is worth something.

Post has been editedilfat12 - 24.10.16, 21:17

Reason for editing: corrected link

[tabikus]

ilfat12,
This new version of the viper is quite an amateur. So I could not achieve the same parameters in it as on 2.4. Moreover, it is not as updated, but next. Package name chtol changed?

Does someone follow the topic on the back? There, the people have problems with the root on the 8th magic? Or just two people on 4pd so lucky?)

[ilfat12]

gavrilaI only track the author's messages))
The option with SuperSU did not check on 8-ke? By the way, now Magisk does not crush the SuperSU, but stands nearby. Moreover, Magisk creates a script, thanks to which it will be restored after updating SuperSU.
And Viper on taste and color. I visually 2.5 more like it.

[tabikus]

ilfat12,
SuperSu 2.78 even before installation when installed from scratch, doesn’t work out as expected - it doesn’t see the binary ..
Accordingly, after installing the magic, too, nothing is visible ..
If I put over Supersu 2.78 Magisk 8, then the manager 2.1 does not see the module Supersu helper. Route from phh is visible, but does not work - the su binary is not seen ..
After installation, magic 7 works both supersu and pkhh

[ilfat12]

gavrila @ Today, 9:27

If I put over Supersu 2.78 Magisk 8, then the manager 2.1 does not see the module Supersu helper.

Now there is no module. Magisk no longer touches SuperSU, only adds its patches to the ramdisk.

SuperSU Integration
In the previous release (v7), I decided to convert the SuperSU into a Magisk module while installing Magisk. In this release (v8), I will make it Magical 100% compatible with SuperSU out of box, not needed. For the patched boot image.
Also, I’ve created an integration for Magisk and SuperSU: Magisk will create a script that was created in /data/custom_ramdisk_patch.sh when SuperSU is detected. SuperSU by flashing SuperSU zip in custom recovery, Magisk will automatically be injected. You can also apply OTA updates with Flash, and enable SuperSU injection, which will also inject Magisk on-the-go!

If you use the SuperSU v7 with the SuperSU along with the Helper Module, please manually restore your boot image, then flash the latest SuperSU, then flash Magisk-v8.

Post has been editedilfat12 - 25.10.16, 10:21

[ilfat12]

gavrilatry to remove Magisk with uninstaller, and then manually manually clean all tails, including / data / custom_ramdisk_patch.sh, as well as the cache section, you can format it, and everything related to Magisk. Restore the stock kernel and reinstall Magisk + phh. I think it should earn.

Post has been editedilfat12 - 25.10.16, 10:26

[tabikus]

ilfat12,
Yes, I once did not try ..
C phh does not come out at all ..
SuperSU older than 2.65 does not start at all on my firmware - it does not see the binaries .. Ie suhide does not take off ..

All this bodyguard managed to win only in the following sequence:

1. Put SuperSU 2.65 - non-systemic root earned
   
2. Put Magisk v8 - he saw the root
   
3. Updated SuperSU to 2.78 through the market to update the binary
   
4. Delivered SuperSU 2.78 through recovery, to update init.rc to work suhide
   
5. Put suhide

BUT..
If I do not put Magisk - Secure Settings works in full force. Just put Magisk - the Secure Settings root-functions shut up ((

Post has been editedgavrila - 25.10.16, 17:35

[ilfat12]

gavrila, mounted su using the module in / system / xbin / su, Secure Settings saw Ruth, Sberbank too))
It seems that Secure Settings is trying to run su in a certain way, which seems to me rather stupid. Yes, you ask for su and you will be Ruth, but no, you need to be clever and try to guess his location))
Especially old applications are wrong with this, and Secure Settings has not been updated for almost two years, at least in the market.
gavrila, other tools do not solve your problem?))

[tabikus]

ilfat12 @ Today, 19:08

mounted su using the module in / system / xbin / su

Your module?
Or phh rules?

[ilfat12]

gavrila, your own)) But, by the way, Titanium has ceased to receive the rights, although in the error window it shows that it is requesting / system / xbin / su.

[tabikus]

ilfat12,
Can you see a module?
And then my link is not created for some reason (

[ilfat12]

gavrilawhy link? You simply create the xbin folder in the module in the system folder and copy the su binary, which is in the phh module folder, into it. You sew the module and reboot. In the scripts do not need to write anything.

And, you have SuperSU. Accordingly, su lies elsewhere. which su will show where he lies.

Post has been editedilfat12 - 25.10.16, 22:57

[tabikus]

ilfat12,
No, I phh again set. It is more native for magic.
Thanks for the help. Secure Settings won, Titanium works too

[Psixopad]

Guys question on the module All-In-One-Magisk-Module, as I understand it if you put the APK I need there, will it work?