> Attention!

New threads need to be created only inroot partition! In the future, they will be processed by moderators.

If you posted a new version of the program, please notify the moderator by clicking the "Complaint" button on your message.

Catalog of Android programs



В® Magisk | Route Manager and off-system platform



Rep: (5524)
В® Magisk
Version: 20.4 / 8.0.3

Last update of the program in the header:13.11.2020

Advance orders for modules Magisksavagemessiahzine.com | Catalog of modules for Magisksavagemessiahzine.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

Attached Image

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

The opening utility that boot patches allows you to get root rights (MagiskSU), set various system applications and mods in Systemless mode, i.e. without changing the / System. Allows you to run scripts at various stages of mounting and replacing files (for example, build.prop) before mounting the / DATA section. Allows you to hide the presence of the root / unlocked bootloader / PERMISSIVE-SELINUX mode from various banking / email / game applications and the Android Pay payment service, as well as receive on some OTA-update devices of stock firmware.

Screenshots
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image


About the application

  • Developer: topjohnwu
  • Russian interface: Yes
  • System requirements: Android 5.0+, an unlocked bootloader (required, because changes are made to ramdisk!), A pre-made nandroid backup.
  • Starting with Magisk 18.1, root is supported for Android 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 boot and its firmwareoroption in pictures. 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 that the bootloader is unlocked. Make sure that the device is installed correctly working recovery capable of mounting sections. Make sure the kernel is not encrypted (if encrypted - see paragraph 17 of this FAQ). If everything is in order, apparently, your device is simply not supported yet, so Magisk cannot disappear kernel. Touch with the Magisk developer and send it the kernel from the firmware of your device. No kernel - no help. It is not necessary to write in this topic - there is no developer here, there was no and will not.

  • 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 folder / data.

  • Problems with SafetyNet - fails validation, CTS profile mismatch error, etc. Obsolete, left for history
    • 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:
    • 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 enforce and reload the device afterwards (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.

  • 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?
    • All downloaded - in the internal memory to Download; Set - in / data / adb / modules; Loaded - in /sbin/.magisk/modules.Removing modules

  • Modules cannot be downloaded from Magisk Manager - the repository is unavailable, an error "incorrect update channel" appears.

  • 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?

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 any of the other Ruth, no root or update Magisk of Magisk Manager-a failed
    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. Sewn into custom rekaveri archive the latest 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
    1. Stitch in custom recovery orFlashfireuninstaller Magisk-uninstaller.zip. After flashing uninstaller it is desirable to make a wipe cache and dalvik cache.
    2. If the uninstaller does not help, restore the stock boot.
    3. NB! Magisk before performing the patches makes a backup in /data/magisk_backup_***/boot.img.gz, so if you have any problems, you can always manually unpack the backup, flash the boot in TWRP and so return the device to life.
    4. If after removal Magisk device dependent on prompt because the boot katabatic activated dm-verity, restore stock partition / system or sew alternative Root (SuperSU).

Useful links and solutions from members of the forum

Download:
Stable version: 20.4 (20400) | V8.0.3 (314) Displax
Beta versions:
Version: 21.1 / 8.0.3 21.1 (21100) | V8.0.3 (314) (Number one ')
CANARYversion: 21101 | 315 (14) Displax
Past versionsCANARY
Change channel updates CANARY

21006 | 313 (13) Displax
21005 | 311 (13) SCR_MegaRacerZ
21004 | 310 (12) SCR_MegaRacerZ
21002 | 309 (12) DisplaxIn reality version21004 | 310 (12)
21002 | 309 (12) Displax
21002 | 308 (12) Displax
21001 | 306 (11) Displax
21001 | 305 (11) Displax
21001 | 303 (11) SCR_MegaRacerZ
20427 | 301 (10) Displax
20426 | 300 (10) Displax
20425 | 299 (10) Displax
20425 | 298 (10) Displax
20424 | 297 (10) Displax
20420 | 297 (10) Displax
20420 | 296 (10) Displax
20420 | 295 (10) Displax
20420 | 294 (10) Displax
20420 | 293 (9) Displax
20420 | 292 (9) Displax
20419 | 291 (9) Displax
20419 | 290 (9) Displax
20419 | 289 (9) Displax
20418 | 289 (9) Displax
20418 | 288 (9) Displax
20418 | 287 (9) Displax
20417 | 286 (9) SCR_MegaRacerZ Bug installed modules are not visible, but they work.
20416 | 285 (9) Displax In this release, there are bugs.
20415 | 284 (9) Displax
20414 | 284 (9) Displax
20413 | 284 (9) SCR_MegaRacerZ
20412 | 284 (9) Displax
20411 | 284 (9) Displax
20409 | 284 (9) Displax
20408 | 284 (9) Displax
20407 | 283 (9) Displax
20406 | 283 (9) Displax
20405 | 283 (9) Displax
20404 | 283 (9) Displax
20403 | 283 (9) Displax
20402 | 283 (9) Displax
20401 | 282 (9) SCR_MegaRacerZ
20401 | 280 (8) Displax
20401 | 279 (8) Displax
20308 | 278 (7) M6R1ARTY
20307 | 278 (7) Displax
20306 | 276 (7) Displax
20.4 (20305) | 7.5.2 (275) (7) SCR_MegaRacerZ
20.4 (20304) | 7.5.2 (274) (7) SCR_MegaRacerZ
20.4 (20303) | 7.5.2 (273) (7) Displax
20.4 (20303) | 7.5.2 (272) (7) Displax
20.4 (20303) | 7.5.2 (271) (7) Displax
20.4 (20303) | 7.5.2 (270) (7) Displax
20.4 (20302) | 7.5.2 (269) (7) SCR_MegaRacerZ
v20.4 (20302) l v7.5.2 (268) (7) MONSTER_PC
20.4 (20301) | 7.5.2 (268) (7) SCR_MegaRacerZ
20.3 (20202) | 7.5.1 (266) (7) Displax
v20.3 (20201) l v7.5.1 (266) (7) N-e61
v20.2 (20110) l v7.4.1 (264) (6) MONSTER_PC
20.2 (20109) | 7.4.1 (262) (6) Displax
20.2 (20108) | 7.4.1 (260) (6) Displax
20.2 (20107) | 7.4.1 (259) (6) Displax
20.2 (20105) | 7.4.1 (257) (6) Displax
20.2 (20104) | 7.4.1 (256) (5) Displax
20.2 (20102) | 7.4.1 (255) (4) Displax
20.1 (20004) | 7.4.0 (252) (3) Displax
20.1 (20003) | 7.4.0 (251) (2) Displax
20.1 (20003) | 7.4.0 (249) (2) Displax
20.1 (20003) | 7.4.0 (248) Displax
20.1 (20001) | 7.3.5 (246) Displax
V20.1 (20001) l v7.3.5 (245) MONSTER_PC
19.5 (19407) | 7.3.4 (242) Displax
19.5 (19406) | 7.3.4 (241) Displax
19.5 (19405) l v7.3.4 (240) MONSTER_PC
19.5 (19404) | 7.3.4 (239) Displax
19.5 (19403) | 7.3.4 (238) Displax
19.5 (19402) | 7.3.4 (237) Displax
19.4 (19309) | 7.3.3 (234) Displax
19.4 (19308) | 7.3.3 (233) Displax
19.4 (19307) | 7.3.3 (231) Displax
19.4 (19307) | 7.3.3 (229) Displax
19.4 (19306) | 7.3.3 (228) Displax
19.4 (19304) | 7.3.3 (228) Displax
19.4 (19303) | 7.3.3 (227) Displax
19.4 (19302) | 7.3.1 (225) Displax
19.4 (19301) | 7.3.1 (223) Displax
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 (209210) 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.2 (18112) | 7.0.0 (193) N-e61
18.2 (18111) | 7.0.0 (191) Displax
18.0 (19001) | 6.1.0 (166) gjf
17.4 (17309) | 6.0.1 (155) gjf
Modified Magisk Versions
Past versions
Starting with release 20.1 (20100) | 7.4.0 (253) (3) fixed problem with slotom Magisk

v21.0 (21000) | V8.0.0 (302) Camerado
v20.4 l v7.5.1 MONSTER_PC
v20.3 l v7.5.1 MONSTER_PC
19.4 (19400) | 7.3.4 (235) Displax
20.2 (20200) | 7.5.0 (265) (7) Displax
20.1 (20100) | 7.4.0 (253) (3) Displax
Magisk v20.0 l v7.3.5 MONSTER_PC
Magisk v19.3 | v7.3.4 MONSTER_PC
Version: 19.2 stable Alex0047
Version: 19.1 stable Displax
19.0 | v7.1.1 Alex0047
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 treble Post belek1991
Version: 16.4 beta Post Alex0047
Version: 16.3 beta Post Alex0047
Version: 16.2 beta Post DanRub1995
Version: 16.1 beta Post Displax
Version: 16.0 stable Post Displax
Version: 15.4 beta 15.4 (1540) | 5.6.0 (100) Displax
Magisk v15.3, contains Magisk Manager v5.5.5, author astherion
Version: 14.5 beta 14.5 (1456) | 5.4.3 Displax
Version: 14.3 beta 14.3 (1437) | 5.4.0 Kisakuku
Version: 13.3 stable Post Kisakuku
Version: 13.2 stable Post Kisakuku
Version: 13.1 stable Post ogo2012
Attached fileMagisk-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:Attached fileMagiskManager-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 uninstallerAttached fileMagisk-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:Attached fileMagisk-v14.0.zip(5.53 MB)
5) Install Magisk Manager:Attached fileMagiskManager-v5.4.3.apk(2.29 MB)
Uninstall Magisk v14.0
Stitch in the recovery or FlashFire uninstaller Attached fileMagisk-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:Attached fileMagiskManager-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 uninstallerAttached fileMagisk-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:Attached fileMagisk-v13.3.zip(5.04 MB)
5) Install Magisk Manager:Attached fileMagiskManager-v5.1.1.apk(4.5 MB)
Uninstall Magisk v13.3
Stitch in the recovery or FlashFire uninstaller Attached fileMagisk-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:Attached fileMagiskManager-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 recoveryAttached fileMagisk-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 FlashFireAttached fileMagisk-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 flashingAttached fileMagisk-v12.0.zip(6.15 MB)
4) Install Magisk Manager:Attached fileMagiskManager-v4.3.3.apk(3.44 MB)

Uninstall Magisk v12.0: Flash Uninstaller or FlashFire Recovery Attached fileMagisk-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 ManagerAttached fileMagisk 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 FlashFireAttached fileMagisk-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 flashingAttached fileMagisk-v11.6.zip(6.15 MB)

4. Install Magisk ManagerAttached fileMagisk 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 ManagerAttached fileMagiskManager-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 recoveryAttached fileMagisk-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 FlashFireAttached fileMagisk-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 flashingAttached fileMagisk-v11.1.zip(5.72 MB)

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


Uninstall Magisk v11.1: Flash Uninstaller or FlashFire Recovery Attached fileMagisk-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. InstallAttached fileMagiskManager-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:Attached fileMagisk-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 FlashFireAttached fileMagisk-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 flashingAttached fileMagisk-v10.2.zip(5.65 MB)

3. InstallAttached fileMagiskManager-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 Attached fileMagisk-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 recoveryAttached fileMagisk-v7.zip(2.18 MB)
5. To manage Magisk modules, install a shell -Attached fileMagiskManager-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 Attached fileMagisk-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 recoveryAttached fileMagisk-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 -Attached fileMagisk_Manager_v1.2.apk(78.07 KB)

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

Some applications, for example "exposure The"Use known spelling Magisk (mount leak). Hide from them Ruth will not work. So far it is impossible to fix this, go to the theme of your application and set the modification.
Unlock, installing custom rekaveri replacement kernels, backups and firmware are discussed only in the topics of their devices!

All about HARDWARE certification (verification) SafetyNet

For questions about filling the caps contact the curator of the topic. esleer

Post has been editedesleer - 24.11.20, 23:49
Reason for editing: Revision



Rep: (379)
* GAL_AS So zip file is the same version magisk lived through twrp? What do they say in the subject vehicle on the installation magisk?

Post has been editedBoreySlav - 23.04.19, 22:02



Rep: (246)
* GAL_AS, you judging on the device is locked bottles and Ruth is activated via a hidden menu. If so, the latest versions of magisk not get. If it is not - tells how flashed magisk.

Post has been editedhrap1919 - 23.04.19, 22:25



Rep: (164)
GAL_AS @ 23.04.19, 21:43*
Magisk 19,
Well, judging by the screen, Magisk you have not installed ??? : Wacko:



Rep: (3855)
GAL_AS @ 23.04.19, 21:43*
Is it possible to run on the device magisk
There is little information ..
Clean boot and immediately Magisk sewed?



Rep: (135)
max9620 @ 04.23.19, 17:23*
Immediately install the version of Magisk Canary.
that is, delete the old version, and you can immediately roll the canary without installing the kernel from the firmware?



Rep: (3855)
* Turbodiman ,
Yes.



Rep: (0)
Device Zuk Z2
OS lineage-16.0-20190324-UNOFFICIAL-z2_plus
It was 7 android without root rights, but I tried to put a superSU on it. Now completely reinstalled android. I installed gapps. Recovered your old applications. Ie I launched the phone, set up Google accounts and waited until it downloads all the old programs.
The phone constantly in the TVRP produces errors about this folder vendor. I xs what it is, but I cannot wipe this folder into a TV folder.
Log
************************
* Magisk v18.1 Installer
************************
- Mounting / system, / vendor
mount: can't find / vendor in / etc / fstab
! Cannot mount / vendor
- Unmounting partitions
Updater process terminated with ERROR: 1
I: Install took 3 second (s).
Error installing zip file '/ sdcard / Download / super su / Magisk-v18.1.zip'
Updating partition information ...
I: Data backup size is 5636MB, free: 35851MB.
Cannot mount '/ vendor' (Invalid argument)
I: Actual block device: '', current file system: 'ext4'
I: Unable to mount '/ usb_otg'
I: Actual block device: '', current file system: 'vfat'
... done



Rep: (1968)
Tel constantly in TVRP gives errors about this folder vendor
Maybe inby thisproblem?



Rep: (363)
Magisk v19.0 (19005) / v7.1.1 (207) [CANARY]

Changes:
Magisk
  • For detecting volume up: track all input devices that is supported. In theory should support more devices such as unlocked Snapdragon S10s
  • Monitor app_process binary usage in case zygote daemons are spawned
  • Prefixing / sbin tmpfs overlay setup
Magisk Manager
  • Upgrade libsu
  • Update post_ota.sh

Download:
Magisk ZIP(release): Attached filemagisk-release.zip (4.72 MB)
Magisk Manager(release): Attached fileapp-release.apk (2.27 MB)

Magisk ZIP(debug): Attached filemagisk-debug.zip (7.49 MB)
Magisk Manager(debug): Attached fileapp-debug.apk (5.05 MB)
* to create bug reports.

Uninstaller: Attached filemagisk-uninstaller.zip (2.2 MB)

A source: XDA

Post has been editedMad_Johnny - 24.04.19, 10:15



Rep: (307)
GOG4IK @ 04.24.19, 10:44*
QUESTION: HOW IS IT DECIDED?
Install the magisk manager corresponding to your version of the majisk. There look tab superuser.
To start, I would download cpu-z from the market and see if the root works on the device (system tab) should be Root Access - Yes.



Rep: (670)
* DenZsavagemessiahzine.com,
the manager is not tied to the version of magix, if that



Rep: (3855)
Kiriga @ 04.24.19, 11:06*
the manager is not tied to the version of magix, if that
The cap reads and Magisk often does not want to upgrade until you update the Manager .. if that: yes2:
Magisk and its shell (Magisk Manager) is desirable to update simultaneously. Obsolescence of one component when updating another leads to problems.


Post has been editedmax9620 - 24.04.19, 11:20



Rep: (1968)
Root is not seen for the reason that the manager is built with a random package name
I’m sucking, however. :) Applications do not request a root from the Manager, it intercepts the request and processes it to give / not.



Rep: (1778)
Goshvit @ 04.24.19, 11:30*
Applications do not request root from Manager
May be. But for some reason on the branch there are questions why programs do not see the root. Sometimes this is due to the installation of the manager with a random package. And sometimes a program of the wrong version is chosen to work with root from Magisk.
In any case, waiting for details from* GOG4IK,
Plus I want to know the name of the device, firmware. Well, and probably still need to update root, because another 18.0 version is worth it.

Post has been editedesleer - 24.04.19, 11:39



Rep: (246)
Goshvit @ 04.24.19, 11:30*
I’m sucking, however. Applications do not request a root from the Manager, it intercepts the request and processes it to give / not.

I do not understand something for you. Who intercepts? The request goes to the magic daemon on a UNIX socket. The demon first looks at its base, is there permanent permission or prohibition? If there is nothing like that, then go to the manager request.



Rep: (1968)
hrap1919 @ 04.24.19, 13:39*
Who intercepts?
Well, maybe I put it wrong, but the package name should not affect once this function is provided.



Rep: (246)
Well, maybe I put it wrong, but the package name should not affect once this function is provided.

Well, think for yourself. The daemon's settings are initialized, for example magisk.zip has been reset from scratch. How does a demon know that the prog with the package name "com.DfgGGpsX" is exactly the manager you need to obey, not the exploit? A random package name can only work after some communication between the daemon and the manager that has the original package name.

The fact that such a "problem" was in the old versions is 100%. Although this is not such an acute "problem", if you understand what's the matter. Maybe in the new versions, the author of the cunning one invented something, but then it is better to study the source codes and commits in general if there are any holes there. I myself do not get into the GUI part because I don’t really understand Java, but the functionality of the database (written on it) suits me.

Post has been editedhrap1919 - 24.04.19, 12:25



Rep: (3)
* hrap1919,
Indeed, the bootloader is blocked, not a word about the magic in our topic, there is only a dance with a tambourine to install the supersu and xposed, but have not tried it yet



Rep: (4)
For a very long time I broke my head like a break of Ruth (Mazhisk 19.0 on the firmware of the husk. Sabzh ski B30). As a result, put Magisk Pros and BusyBox. There was no sense, I smoked for a forum for 3 hours. I found this post. I put the last fix V3 and the phone went to the bootlup, I thought that it was not for me then I saw that you need to pour a file in bin systems. I tried to boot into the recovery but the phone after the reboot was loaded. Jought Safetynet. Everything is. Immediately cleaned the cache of GPI and the GPLE and the GPE started as sweetly thank you very much !!!!!
.
Lord of the Lost @ 03/28/19, 21:04*
I decided to collect in one post all popular SafetyNet patches for all time.


Post has been editedesleer - 24.04.19, 17:33
Reason for editing: Removed overclocking (overquoting)



Rep: (2)
People can anyone know - when copying with a Total commander in the SYS catalog is denied access. This is what writes - Permission denided.

Ruth is (Magisk). I tried through ES - the same thing. Reloaded-caf Pie firmware.

And if you copy to the / then copied, but it is remounted to write.

Post has been editedjoker_37 - 25.04.19, 10:14
Reason for editing: 111


Full version    

Help     rules

Now: 28.11.20, 05:48