> 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


1134 pagesV  « < 3 4 5 6 7 8 > »  
 
REPLY
> Â® Magisk - The Universal Systemless Interface | Route Manager and Off-System Platform
Anais10
Message#1
26.09.16, 23:35
Brain user
*********
[offline]

Group: Curators
Messages 12775
Check in: 09.12.11
Samsung Galaxy Tab S 8.4 LTE

Reputation:-  5332  +

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

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

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
Attached Image
Attached Image


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:
    • 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.

  • 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: Attached filemm-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.

  • 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 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
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 (216)] Displax
Past versionsCANARY
Modified Magisk Versions
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 # 76613184)
Version: 16.7 beta (Post Displax # 75219232)
Version: 16.6 beta (Post Displax # 74879510)
Version: 16.4 beta (Post by Alex0047 # 72861219)
Version: 16.0 stable (Post Displax # 70622711)
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)

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

Post has been editedesleer - Yesterday 22:51
Reason for editing: Module Addresses, by Goshvit
ilfat12
Message#82
15.10.16, 00:00
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

* gavrilaBut what about suhide for SuperSU?
tabikus
Message#83
15.10.16, 00:02
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* ilfat12,
Extra crutch. I did not even try it.
Phh is not visible to anyone yet. I decided to stay on it


--------------------
gavrila
ilfat12
Message#84
15.10.16, 00:11
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

gavrila @ Today, 0:02*
Extra crutch. I did not even try it.
so he is very cool in this matter.
tabikus
Message#85
15.10.16, 00:24
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* dadimon29,
Sp?
Or AP?
Sorry, I overlooked the question about the info about android pey. I saw only about sbonlayn.
Only yesterday I cleaned out the supersu from the sberbank, returned phh.
What's the problem with AR?

Posted on 10/15/2016, 00:25:

ilfat12 @ Today, 0:11*
so he is very cool in this matter.

In the same place everything seems to be registered in the config file. Not comfortable to me


--------------------
gavrila
ilfat12
Message#86
15.10.16, 00:35
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

gavrila @ Today, 0:24*
In the same place everything seems to be registered in the config file.
There is an unofficial Guy in the market. Chinfire writes that there is no such thing at the moment, as if hinting that he will be, but for the time being, use an unofficial type.
suhide 0.55 bypasses the latest Safety Net update.
Even topjohnwu (author Magyska) says that if Magisk burns, then use SuperSU + suhide, emphasizing that today it is a better solution in terms of hiding. I apologize that without proofs.
By the way, the author of phh and topjohnwu saw their Skryvalschiki.


Post has been editedilfat12 - 15.10.16, 01:17
tabikus
Message#87
17.10.16, 12:46
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

Ilfat12 @ 10/15/16, 0:35*
use SuperSU + suhide

Put.
Barely rolled back.
The phone began to hang, overload, warm up.
While my bundle - magic and pkh-superuser


--------------------
gavrila
ilfat12
Message#88
17.10.16, 14:44
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

Gavrila @ Today, 12:46*
Barely rolled back.
The phone began to hang, overload, warm up.
strange of course)), I have no problems.
I personally do not use Sberbank Online for want of a card, but in the SuperSU topic I was suggested that the best root checker is Sberbank Online)))
I decided to check my bundle Magisk + Xposed + SuperSU + suhide.
The result is interesting of course. First it gives:
Attached Image

And after a couple of seconds, this:
Attached Image

It is not clear who exactly of this ligament is burning.Nobody scorches) We must probably separately check SuperSU + suhide and Magisk + phh. And you can do it with Xposed. But while there is no time to mess with it.

P.S. I apologize for the misinformation, it's not like that.I reinstalled Sberbank Online and forgot to put a tick in the suhide. In fact, with suhide enabled, this whole bundle (Magisk + Xposed + SuperSU + suhide) is being tested by Sberbank Online.

P.P.S. A bunch of Magisk + Xposed + phh is also tested by Sberbank Online. What, in principle, already reportedgavrila, only here Xposed was added)

Post has been editedilfat12 - 17.10.16, 17:53
ilfat12
Message#89
17.10.16, 18:20
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

The presence of idle bizybox is tantamount to its absence.
I repaired myself like this:
In the /magisk/.core/ folder I put the symlink on the / data / busybox / folder for the symlinks to the bizybox applets are there.
And in the resulting folder /magisk/.core/busybox/ put the symlink on the binary / data / magisk / busybox
Now the bizybox works wherever it should

Ilfat12 @ 13.10.16, 19:29*
You will be surprised at my simlink that you have already created there. Therefore, I have all the BusyBox applets visible to the system.

Removed Magisk completely and reinstalled. I wandered into /magisk/.core/ and was surprised that there was really no symlink to the folder / data / busybox / and then I remembered that the last time I climbed in the settings of the Magisk Manager and touched the BusyBox on / off button. Despite the fact that the jackdaw is by default, BusyBox is turned off from the box. If you uncheck, exit the application and log in again, the jackdaw will still stand. It seems that this is a bug of the application. It is necessary to remove the checkbox and reinstall, then the symlink in /magisk/.core/ will appear on the folder with the bizybox applets, more precisely with the symlinks on them. That is, if the daw is on exiting the application, then BusyBox will be activated, if not, then no. The only thing is that the symlink to the bizybox binary itself will still need to be created manually, otherwise applications using bizybox applets directly through a call to the bizybox will be desperate))
tabikus
Message#90
20.10.16, 09:30
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

The manager himself updated from the manager to 2.1 and magic to 8, phh stopped seeing su, needs to be updated, but does not update ..
I deleted the magic, installed the magic 8 and phh from scratch, but the update su is also required ..
How to fix it?
While rolled back to 7


--------------------
gavrila
ilfat12
Message#91
20.10.16, 10:32
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

* gavrila, I'm fine with phh. I do not even know what to offer. It can reinstall the apk itself or clear the data. Also pay attention to Magisk Hide. Maybe because of him. I turned it on and after the first reboot, even the Magisk Manager itself did not see Ruth and even his modules. I rebooted again and everything became normal, but not a single application was seen by Ruth. I had to shut down and restart again. This implementation of Magisk Hide is no good.
I had other difficulties. Could not update Magisk Manager from the application itself. Crashed with an error. And when I tried to update myself, Magisk said that it was not a Magisk module. That is, I pressed the update button and wrote to me like that. Do not think that I tried to install the downloaded zip as a module))
In the end, I made everything from recovery. The symlink on the bizybox box went off naturally. It is necessary to create it somewhere else or to make a module at all and install it at boot.

Post has been editedilfat12 - 20.10.16, 10:33
Reason for editing: Typo
tabikus
Message#92
20.10.16, 10:39
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* ilfat12,
Well, at least the links to the applets have been fixed)
Yes, the manager also did not get out of the manager. Zaretila installation apk from the outside.


--------------------
gavrila
ilfat12
Message#93
20.10.16, 10:50
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

* gavrila, links and so worked. I wrote that you need to reset the checkbox in the settings)
tabikus
Message#94
20.10.16, 10:52
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* ilfat12,
I mean that now with the initial installation and missing links, the jackdaw is turned off, not turned on .. It is not misleading


--------------------
gavrila
ilfat12
Message#95
20.10.16, 23:16
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

Into its universal module added the creation / re-creation of a symbolic link to busybox each time it is loaded. Updates are no longer scary)))
And this is the only thing that this module does. From his junk cleaned. Maybe someone will come in handy)
All that you want to add to the system section of your android simply add to the system folder of this archive and flash it or install it through the Magisk Manager.
You can edit the archive applicationX-plore.
By default, folders are merged with existing ones. The existing file is replaced, the missing one is created. To completely replace the existing folder, add an empty file named ".replace".
In principle, everything is simple :)
Attached fileAll-In-One-Magisk-Module.zip(7.86 KB)


Post has been editedilfat12 - 21.10.16, 07:36
tabikus
Message#96
21.10.16, 09:27
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* ilfat12,
Thank you very much))
And all the hands will not reach such a module))
Plus flew away


--------------------
gavrila
tabikus
Message#97
21.10.16, 11:05
gavrila
*********
[offline]

Group: Banned
Messages 19699
Check in: 27.04.06

Reputation:-  2907  +

* ilfat12,
And can your module build.prop be replaced?


--------------------
gavrila
ilfat12
Message#98
21.10.16, 11:42
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

* gavrilaTo replace build.prop, you need a module working from the cache section. You can redo this module. In fact, it differs from the base one only in my data in module.prop and the line added in post-fs-data.sh
ln -s / data / magisk / busybox / data / busybox / busybox
and a small config.sh setting. It indicates the MODID and a couple more options, such as the activation of post-fs-data.sh. By the way, the placeholder file in the system folder can be deleted, it is created only because if the folder in the repository on the githaba is empty, it is deleted.
About build.prop. If you need to change only some values ​​and these values ​​are not read only, that is, the corresponding lines do not begin with ro., Then you can not even redo my module, but simply add the necessary line to post-fs-data.sh, for example
setprop dalvik.vm.heapsize 1024m
if they start with ro., then you have to copy the module and redo it to work from cache. Be sure to change the MODID. In this case, you will need to add a command already in post-fs.sh, for example
setprop ro.sf.lcd_density 240
Accordingly, to replace the entire build.prop post-fs and post-fs-data is not necessary to edit, but simply throw the modified build.prop into the system, but again the module should work from the cache. I have such a module installed only from the recovery. From the manager did not get up. Something like that. If that is not clear answer.
ilfat12
Message#99
21.10.16, 13:26
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

An example of a module for changing the Read Only parameters of build.prop. Took from repository.
Attached fileGoogle_Assistant-v1.5.zip(6.92 KB)

I guess I understood why my cache mode module did not get out of the manager, there was no magisk folder. Now gets up. But not completely removed, but like this module. From the cache is removed, and from / magisk must be removed by hand.

Post has been editedilfat12 - 21.10.16, 13:32
Reason for editing: Error
ilfat12
Message#100
21.10.16, 17:52
Old resident
*******
[online]

Group: Friendssavagemessiahzine.com
Messages 951
Check in: 17.07.13
Oneplus one

Reputation:-  107  +

It turns out the basic module has been updated. Corrections concern only CACHE modules. If you make yourself such a module, then make it based on it.
Attached filemagisk-module-template.zip(6.72 KB)

A link to the instructions for creating modules is in the header. The instruction is in English.
Jormovich
Message#101
23.10.16, 18:34
Local
*****
[offline]

Group: Friendssavagemessiahzine.com
Messages 255
Check in: 11.05.07
Oneplus 5T 8/128

Reputation:-  139  +

downloaded from the manager and tried to put through it on the LG G2. Now when loading it writes:
boot certification verify
secure booting error!

the inscription disappears and is not loaded further.
The second problem - fastboot does not see the phone, writes
<waiting for device>
Drivers are installed. Accordingly, it did not work in temporary recovery.

LG Flash Tool phone sees, flashed on D80230D_00_EUR.kdz
Magisk manager can not put anything on the stock, I put the root through the LG One Click Root.

Post has been editedJormovich - 23.10.16, 19:11

1134 pagesV  « < 3 4 5 6 7 8 > » 


 mobile version    Now: 09.06.19, 13:26