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!)
Device is OnePlus3. Data partition is F2FS filesystem. And I tried almost all Android 7.1.1 rom for this device.
When I just fresh flash the rom and SuperSU 2.78 SR5, app can get root permision. But after some while, root lost. App can't get root permision and also SuperSU can't find su binary.
But if I reboot device, root back again. But some time later(maybe half an hour?) root lost again.
Bump.. Same here and have tried everything I can
Try flashing SuperSU 2.79. It has some bugfixes that aren't included in earlier versions of SuperSU.
I had rooted with superSU than switched to magisk root which is now updated to Magisk v15.2(Magisk Manager 5.5.3) and I have some problems
Every Modules I intall gives Installation error(magisk_merge.img merge failed)
tried flashing modules via recovery but not showing into magisk manager
safetynet check failed what to do?
can i install viper4android or ARISE sound system(cant install from magisk modules)
If anybody can help would be great
Odds are good you didn't remove su properly
flash the unSU zip file to uninstall superSU
doesnt work
Bro I have seen a app that doesn't support MagiskSU......but that app supports only magisk.......so how can I enable magisk only without enabling MagiskSU?????
Did you flash the magisk zip after patching SuperSU? I don't think you can have two layers of different root access. but once again i could be wrong.
Run magisk uninstaller is what i would suggest because magisk is useless without patching the boot file..
open for suggestions
Magisk is MagiskSU... You can't get one without the other.
Flashfire was abandoned a long time ago. It used to work with an older version of Magisk, but hasn't been updated in a long time and therefore no longer works with any current releases.
Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
sysctl said:
Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
Click to expand...
Click to collapse
yes u should, always use the latest one
Is it good enough to uninstall SuperSU app when android is running or should I reboot to TWRP and do some magic there?