Database Develop

How to make Magisk v7 work with chainfire SuperSU 2.65?

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!)

[BUG] Magisk refuses to install modules from repo (The zip is not a Magisk Module!)

I've had magisk installed since version 6, I've published some magisk modules already and never had a problem until today.
After a full clean reinstall of Nougat NBD90Z (with wipe) on my Nexus 6 and then flashing Magisk, phh's superuser for magisk, installing phh's superuser apk from play store and magisk manager apk I stumbled upon a previously reported (without details) bug where magisk manager would refuse to install modules from repo claiming they are not magisk modules.
I've struggled trying everything I could including the full wipe (more details here: http://forum.xda-developers.com/apps/magisk/module-app-systemizer-t3477512/69230448#69230448) and bounced some ideas off @pnwsr6 who's had the similar problem on Nexus 6 device.
I've achieved a partially working Magisk Manager (manual installs of ZIP files work, but installs from repo still fail) and here's the list of steps which lead to me having semi-working magisk manager again:
1. I flashed ZIP files of some modules in twrp (I'm attaching App Systemizer and Nexus 6 LED Enabler which I flashed)
2. After the phone booted up I saw the modules active and working
3. Within Magisk Manager I then added the ZIP file of the phh's superuser module from that thread (http://forum.xda-developers.com/attachment.php?attachmentid=3893967&d=1475554052)
4. Now at least manual installation of modules within Magisk Manager are working fine.
@topjohnwu -- I've enabled verbose logging and extra logging for bash commands, but I'm still not seeing anything in the log on top of the regular output.

Created an issue against Magisk Manager so it's easier to track for developers: https://github.com/topjohnwu/MagiskManager/issues/20

Looks like that even after flashing some modules in twrp, Magisk Manager only allows to install from zip only exactly the same ZIP I've already flashed (even a minor change and bump of versionCode results in "This ZIP is not a Magisk Module!"). So it might be an issue of Magisk Manager being unable to write to /magisk despite having storage permission and being granted root access.

Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!

I've seen this error as well on my Nexus 6 NBD90Z with Magisk v8. Started with v7 after some heavy modification on my part .
I was sometimes able to fix it by simply extracting the zip and then Magisk Manager would somehow recognize it as a module.. Other times I could extract the zip and then re-archive the contents and Magisk Manager would recognize that as a module. Weird, but doable.

stangri said:
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
Click to expand...
Click to collapse
I probably won't try again until next update, and hope the wipe just wasn't clearing something. I have the zip installed through twrp and working for now so I'm good till then.

just wondering if you're still having this issue with v9? I had modules installed fine under v6, but never really installed any modules under v8 to see if this problem occurred for me. now that I'm on v9, which has been wiped clean to start, I can no longer install any modules via Downloads or in the Modules section... any suggestions?

I have the same issue when trying to install viper with v9 on Nexus 6P DP2
Skickat från min Nexus 6P via Tapatalk

Same here. Find a fix ?

From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.

stangri said:
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
Click to expand...
Click to collapse
Just an FYI, I do still have this problem, but can install the zip through twrp. Maybe 10 will be the solution.

I had the same problem, I cleared magisk manager data and it works fine now

Didn't help
Sent from my SM-G532F using Tapatalk

I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.

stangri said:
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
Click to expand...
Click to collapse
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.

Meowdib said:
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Click to expand...
Click to collapse
Weird, do you have the same problem with magisk manager 161223?

stangri said:
Weird, do you have the same problem with magisk manager 161223?
Click to expand...
Click to collapse
Same

I need a Help to download modules using magisk
Lastest version, Included phh root, manager is from G. play,
But Modules download function is not working
Say "No modules found" for download to install via magisk.

Why my 3T stuck at oneplus logo after flashing xposed in magisk?

I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu

Somebody help me...

I am sure it has been mentioned many times in other threads and forums too.
Magisk 14+xposed seem to be incompatible.
This bootloop happened to me also. I just returned to TWRP and reflashed 13.3.
Problem solved.
Unleashed by ONEPLUS 3T rooted

Why don't flash system version of Xposed?

caryle said:
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Click to expand...
Click to collapse
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.

Aneejian said:
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Click to expand...
Click to collapse
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?

caryle said:
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
Click to expand...
Click to collapse
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
I've read the posts before. I just want to know if it caused by anything else.Now I'm going to flash the xposed system.

There is a better solution:
1 Get this zip file (thanks to @LarappsOfDongle)
2 Flash it by using adb sideload or adb push
3 Go to /magisk in recovery using built-in file manager if using TWRP or use Aroma
4 Delete ONLY folder with or similar name as xposed_framework_25 (be careful in TWRP you need to go into the folder first to delete it)
DON'T DELETE ANY OTHER FOLDER
I had the same issue. Tested with Xposed Framework 25 Magisk 14.0 Oxygen OS Open Beta 14 OnePlus 3T.

FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.

Didgeridoohan said:
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Click to expand...
Click to collapse
Which is this 87.3 version?
And which magisk module u need to uninstall before?
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
Which is this 87.3 version?
Click to expand...
Click to collapse
The one in the Magisk repo (Downloads section in the Magisk Manager).
And which magisk module u need to uninstall before?
Click to expand...
Click to collapse
Xposed... (@topjohnwu changed the module id with version 87.2, if you don't uninstall any previous version you'll get conflicts)

Viper4Android on Oxygen OS 5.x

Hello everyone, my question is simple: is there a way to install Viper4Android on Oxygen OS 5.x?

https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library

Gauravlonkar said:
https://drive.google.com/file/d/1an_JvpfjR_KNQJYeidqKBTJJeL_Bnddj/view?usp=drivesdk
Should be rooted
Use test fix apk
Use oreo audio library
Click to expand...
Click to collapse
test fix apk doesn't work... Always ask to install drivers.

Yes install the driver the screen will freez for some time until installation

Gauravlonkar said:
Yes install the driver the screen will freez for some time until installation
Click to expand...
Click to collapse
it does not work. I have already done it many times and when restarting it asks again to install the driver

Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status and see if Viper works (provided that you've already made the necessary changes to audio libraries). Your phone will reset SELinux every time it reboots though, so you will have to manually disable it again after every reboot. Alternatively, you can set up something like Tasker to automatically switch SELinux into permissive mode on reboot using the following shell command with superuser privaledge:
setenforce 0

Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A

Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
Just curious... Why the Mega links? All those downloads are available through official sources.

Didgeridoohan said:
Just curious... Why the Mega links? All those downloads are available through official sources.
Click to expand...
Click to collapse
Of course they are. Get it wherever you want, it is your choice. This was faster way for me to include dl links and I can say that combination of these files works without any issue. I cannot guarantee when you get different version on V4A it will still work.
For example the V4A module available in Magisk Manager never worked for me on any Oreo rom.

Nexus5-32GB said:
Am using viper4android on oreo for weeks, follow these steps:
1) install magisk 14.3 in twrp and reboot (I reccomend latest blue_spark version of twrp), get magisk here
2) Install Magisk Manager, get it here
3) Download V4A from here
4) Go to Magisk Manager and click on Modules, click + icon and choose V4A zip you just downloaded, reboot device
5) you are done, enjoy working V4A
Click to expand...
Click to collapse
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.

https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error

Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.

Gauravlonkar said:
https://drive.google.com/file/d/13OopG8QnHisqB0hyDflFS5EgJAG4xCjQ/view?usp=drivesdk
Try this one flash using TWRP and choose only v⁴a and Dolby other just skip or uninstall set Linux to permissive
And even if this doesn't work again flash and select uninstall for every option and try test fix APK it should fix io error
Click to expand...
Click to collapse
Thank you, I already solved with the classical procedure for Nougat, deleting audio_effects.conf and installing the test fix apk but with SELinux Mode Changer in order to set SELinux to permissive too.
Nexus5-32GB said:
Don't bother telling me it doesn't work when you clearly didn't follow the steps above. On top of that your ROM is already messed up. Start with clean flash and follow the steps above.
Click to expand...
Click to collapse
"don't bother"
Dude, calm down and relax.
"you clearly didn't follow the steps"
I followed every steps you wrote, and they didn't work for me. Did you watch me working with my phone?
"your ROM is already messed up"
No, you didn't watch me working with my phone, otherwise you would know I have the absolutely clean OxygenOS 5.0.
Too much arrogance.

Markster93 said:
It didn't work for me. When I open Viper4Android and try to install the drivers, it gives me an I/O error.
Click to expand...
Click to collapse
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.

I've only ever had viper working on Oreo on the 3t with SElinux permissive. there are other threads where others have said the same.
I've tried multiple v4a magisk modules all of which have given me abnormal status.
If you wish to get it working inside the following magisk modules
Magisk SElinux Permissive script
Viper4Android FX for magisk v14+
Apart from that I think we may have to wait for an update to fix the SElinux permissions for enforcing

Nexus5-32GB said:
Of course you didn't follow my steps as this error you got never comes up when you use my files I have uploaded for you. There is no need to play with Linux mode nor the I/o fix etc. I have flashed these files on many oreo ROMs, in total like 30x and everytime works as a charm. So before you say something doesn't work, make yourself a favour and do a clean flash because clearly you didn't.
Only trying to help you.
Click to expand...
Click to collapse
You don't understand me, or maybe you don't want to. I did a clean flash of the OxygenOS 5.0, then I flashed your Magsisk 14.3 zip. After that, I installed your Magisk Manager apk, and I added your Viper4Android module. Everytime I tried to open the Viper4Android app, it was always asking me to install the drivers, who always failed because of an I/O error.

So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.

Anova's Origin said:
Viper4Android requires permissive SELinux to work in OOS Oreo. Turn on developer mode in the Viper app and use it to switch SELinux status ...
Click to expand...
Click to collapse
Thanks a lot man. I followed your advice and V4A is working on OOS oreo

JiiJii said:
So has anyone installed Viper succesfully? I tried Nexus5-32GB's solution, but the magisk module would not install, there was magisk_merge.img mount failed error.
Click to expand...
Click to collapse
Try my solution. I followed the Nougat procedure, deleting audio_effects.conf and installing the test fix apk, but setting SELinux to permissive too.

V4A showing that to install driver I need to have Busybox, I installed BusyBox and the driver installed later rebooted. But again when I open it, It is asking to install driver and reboot. I am running V4A version 2.3.4.0, OOS 5 Magisk 14.6 and Manager 5.5.0.
Not able to find V4A developer mode, appreciate some help, please.

[ROOT] [SM-J327P] How to move from SuperSU to Magisk and pass SafetyNet (+Xposed)

NONE OF THESE ARE MY WORK, THANK THE DEVELOPERS
YOU NEED ASHYX TWRP - https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
BEFORE STARTING - Some apps like Pokemon Go detect BusyBox apps, Xposed Installer and the Magisk Manager. Enable the general Magisk Hide as well Magisk Hide for the specific app in Magisk Manager. Activate in Magisk Manager 'Repackage Magisk Manager with random package name.'
Then you have to try renaming the package name of the Xposed Installer apk with APK Editor or something else.
STEP 1 - Download the Magisk 18.0 zip and move to External SD Card - http://www.mediafire.com/file/4rmzov...%29.zip/file.
STEP 2 - Install the Xposed Installer app but DO NOT INSTALL IT FROM THE APP, YOU WILL GET SOFT BRICKED - https://forum.xda-developers.com/showthread.php?t=3034811
STEP 3 - Download the generic Samsung Xposed zip and uninstaller by wanam and move to External SD Card - https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960.
STEP 4 - Uninstall Xposed completely if you had it already.
STEP 5 - Unroot in SuperSU. MAKE SURE YOU SELECT 'RESTORE STOCK BOOT IMAGE' OR YOU WILL HAVE TO REFLASH THE BOOT IMAGE FROM ODIN.
STEP 6 - Reboot to TWRP and flash the Magisk zip. Reboot to system and wait a while, make sure everything is working properly.
STEP 7 - Reboot to TWRP and flash the generic Samsung Xposed zip.
STEP 8 - Reboot to system and and wait a while, make sure everything is working properly. Enable in the Xposed Installer 'No Device Check' or download it - https://forum.xda-developers.com/xposed/modules/xposed-device-check-t3199705.
STEP 9 - Install BusyBox and then delete any BusyBox app.
Now you should pass SafetyNet.