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!)
Hello
I have Resurrection Remix with OMS installed on my 3T and /data currently not encrypted. Everytime I flash SuperSU, it's working after boot, but then root stops working and SuperSU says "No su binary installed." In the recovery.log i can see that my boot image is full, but I have no idea how to fix that or if it's even the main problem. I tried SuperSU 2.79 Stable, SR1 and SR2.
Thanks for help
i ran into the same problem today after flashing tugapower 7.1.
after boot, root only works for a few minutes.
what i did then:
https://forum.xda-developers.com/moto-x-play/general/switching-supersu-to-phhs-su-t3495080
1. unroot via supersu app (settings)
2. reboot into android again
3. flash phh-supersu zip in recovery
4. install phh-supersu app from store
Hi to all
I have rooted OP3T and every time when I install new update, BETA small or full version zip file, I need again to install stock.zip from boatloader , then again, install TWRP and Super Su.
I hear that with Magisk I can easy install any update without lost TWRP and Root. I have flash Magisk and install from Google Store Magisk Manager.
So my question is how to install new update with Magisk and dont lost TWRP and Root?
Please tell me step by step
thx a lot for your answers
Magisk doesn't touch the recovery. And you'll still have to flash the Magisk zip since the boot image is updated whenever you update your system (Magisk modifies the boot image).
What does stay after an update (as long as you don't wipe /data) is any Magisk modules that you have installed. If you have a bunch of modules that change build.prop values, debloat system apps, change screen density, replaces system UI sounds, etc, you won't have to do those changes again after an update. They are found in the Magisk image in /data and will be loaded by Magisk at boot.
Even if you've wiped /data, it's just a matter of flashing the Magisk and module zips in TWRP after updating your system. No tedious manual editing of build.prop or deleting apps, etc. It literally takes seconds...
If you have issues with loosing TWRP after an update, you can easily fix that, right after updating. Just keep a copy of the recovery image on your device and flash it in TWRP.
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob
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?