I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Code:
Installation Instructions
(NOTE: I don't feel comfortable to redistribute SuperSU unless I have explicit permission, so for now, if you want to use SuperSU with Magisk, you are required to have systemless SuperSU installed before flashing Magisk. Magisk will detect SuperSU installation and automatically convert systemless SuperSU into a Magisk Module, using the files that are already installed to your boot image. System installed SuperSU is obviously not supported, since it is not systemless. Actually, it is a trivial task to add official Magisk support to a SuperSU zip package, however the decision is not in my hands.)
If you're rooted with Official Systemless SuperSU, or using Magisk v3+ with Magisk version of phh's superuser
Install the latest Magisk Manager
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, rooted with the depreciated Magisk Version of SuperSU, using Magisk version older than v3, or you got issues when flashing in Magisk Manager (some devices requires Magisk to be flashed in recovery to find boot image location)
(If you have Magisk installed) Flash Magisk Uninstaller to get a clean start
Download the latest Magisk zip file
Download the latest Magisk Version phh superuser from this thread:
[Magisk] [2016.10.4] phh's SuperUser
Flash both zips in custom recovery
Install the latest Magisk Manager for a complete Magisk experience
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
NotExist said:
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
Click to expand...
Click to collapse
Am using an honor 7 PLK-L01 with MM build B370.
Also tried the first method you described with SuperSU 2.62, difference being that magisk manager could not install v7 zip so flashed it manually. It said something about
Insufficient storage for boot image
and kind of aborted.
Since then flashing SuperSU says seplocy failed and aborts.
Tried flashing a new boot and rooting, still the same.
Flashed boot and Cust, the same error both with magisk and SuperSU.
Cleared dalvik and cache, still the same.
Tried the magisk uninstaller, no success...
Would appreciate a solution.
Sent from my PLK-L01 using XDA Labs
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
ibrokemypie said:
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
Click to expand...
Click to collapse
Had to flash system, boot and Cust to root again using SuperSU.
Otherwise it was failing and flashing only boot did not cut the deal.
Sent from my PLK-L01 using XDA Labs
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
HyperCriSiS said:
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
Click to expand...
Click to collapse
Magisk ver 6 works well but have to have that zip and it's corresponding apk I guess 1.2 that is.
Used it a couple of days ways back just to make sure it works.
An update that it works after Magisk v8, although there's no information about it.
(Flash SuperSu v2.65 -> Update to SuperSU v2.78 with Google Play -> update su binary to v2.78 with SuperSU -> install Magisk Manager v2.1 -> Install Magisk v8 with Manager -> done!)
Installed manually, trying to reinstall via the direct install method results in the manager crashing.
Installing modules via TWRP fails as well.
The error given in Magisk Manager is that it can't extract the zip.
im using a samsung galaxy s9 with pie installed and could install edxposed.zp only via magisk manager. in twrp i get the error 1 wich states that magisk is not installed, which isnt true. anyways i installed an incompatible app which coused a bootloop and now i cant install the uninstaller
my question is, is there a module.list like discribed in the following link so i can just prevent the module is beeing loaded manualy?
https://forum.xda-developers.com/xposed/howto-disable-xposed-modules-via-t3227175
edit:
i worked around thios problem via uninstalling magisk via zip file:
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Phone: Huawei P20 Lite
ROM: Omni
Magisk: 20.3
Downloaded the Magisk.zip file through Magisk manager.
Flashing the Magisk zip using TWRP is success.
But rebooting to system showing Magisk isn't installed.
So I was to try flash it again. But booting TWRP is failed.
It ended up booting to system. At this time Magisk manager showing it as installed.
To be concluded:
1) Rebooting to system will delete Magisk root.
2) Rebooting to recovery (TWRP) will fail and boot to system. In that case Magisk manager saying root installed
Any solution to make root access stable and keep TWRP in recovery partition?
4n3y3 said:
Phone: Huawei P20 Lite
ROM: Omni
Magisk: 20.3
Downloaded the Magisk.zip file through Magisk manager.
Flashing the Magisk zip using TWRP is success.
But rebooting to system showing Magisk isn't installed.
So I was to try flash it again. But booting TWRP is failed.
It ended up booting to system. At this time Magisk manager showing it as installed.
To be concluded:
1) Rebooting to system will delete Magisk root.
2) Rebooting to recovery (TWRP) will fail and boot to system. In that case Magisk manager saying root installed
Any solution to make root access stable and keep TWRP in recovery partition?
Click to expand...
Click to collapse
you can patch magisk to your firmware and install (flash) it with odin. but from my experience, the jhonwu method is really work (magisk in system as root) but I am unable to install twrp alongside that system. I mean yes indeed I can flash twrp into the device but then I lose root access. (many case I got random restart all over again).
now I am kinda confused because I need root and also that twrp is really usefull tool for idiot like me.
FYI; I already try install twrp pre-patched magisk from geiti, but its very unstable. random reboot, and sometimes I am losing the magisk it self (magisk manager suddenly show that magisk isnt intall). thats why I am kinda prefer to root with jhon wu method,
can you guys help me how to flash twrp without ruin magisk that already installed on patched stock firmware?
Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.
Wrichik Basu said:
Device: Samsung Galaxy On7
Android: 6.0.1
I have Magisk Manager 8.0.7 and Magisk 20.4 installed on my device. I went to the GitHub repo and found that the app and the zip have been combined in Magisk 22.0. Fine. But how do I upgrade to v22.0? When I open the app, it asks me to upgrade the app first. Okay, I do that. When I open the upgraded app, it can no longer find Magisk. I click on "Install" beside Magisk, choose Direct Install, and then it gives me an error: Device signature invalid.
Any help is appreciated.
Click to expand...
Click to collapse
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have
xHvlios said:
if you have a custom recovery, change the magisk.apk file to.zip so it would be magisk.xx.zip then just flash it via twrp or whatever you have
Click to expand...
Click to collapse
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?
Wrichik Basu said:
Okay. Do I leave the old Manager as it is, or should I uninstall it before I flash the zip from TWRP?
Click to expand...
Click to collapse
I think it will update it, so just flash the new one