Database Develop

[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.

[ROM][KangV Tools][VNS-LX1] Arsenik Rom

Arsenik Rom
For Huawei P9 lite
ALL CREDITS GOES TO KangV !!
ASK PERMISSION BEFORE TAKING MY WORK(EVEN PARTIALLY)​
FEATURES
+based on b380/b385 version
+pre-rooted with chainfire's SuperSu, you can choose also MagikSu
+Kernel adiutor installed
+Emui theme editor installed
+Fingerprint quick action installed
+ double tap to wake up, draw a letter to wake up added
+ deleted all huawei chinese apps and added some missed google apps
+VNS-L31
+VNS-L21(need testers for other variants)
+transparent notification shade enabled
+App twin added
+p10 camera app added
+android O bootanimation added
+android O emojis
+3d panorama app added
+added the ability to make earpiece acting as a speaker and increased it ,you will have an amazing sound when you put your phone next to your ear,trust me
+more performance and less battery drain
+adblock -MoaAB- via k-setting
+new Viper4Android interface for 2.5
+raw image mode added
+June security patch
+slow motion camera mode
+KangVip framework added !
INSTRUCTIONS
1.download the zip file and extract it, you will find system.img and flash_patch.zip.
2..Reboot to latest TWRP
3..backup system,boot,vendor
4.flash system.img via install image (install image>choose system.img> select SYSTEM
5.Flash 'flash_patch.zip
6.reboot system(it will take about 10-15min)
7.reboot again to twrp(this is stupid, but sorry you have to do that otherwise magisk won't mount image)
8.go to third post and chose which root you want, you can choose between magisk or supersu
9.reboot(it won't be as long as the first boot)
DOWNLOAD LINK
Arsenik Rom-V2
THANK YOU ALL FOR THE 616 DOWNLOADS of Arsenik v1.1 IN LESS THAN 30 DAYS !
If you cant insert a pin code at first boot, please flash this zip
https://drive.google.com/file/d/0By4OnnXj6y6ebDF5Vk9OcW9ZUkU/view?usp=drivesdk
i recommend to download it and flash it, so that you will be sure that you wont have this bug
BUGS
+usb debugging is disabled when you reboot
NOTES
+do not update supersu binaries because it won't work, flash Special SuperSu for Arsenik Rom in 3rd post instead
CREDITS
+KangV for his awesome Kangvip Framework !
+ @Tecalote for helping me
+ @Chainfire for his awesome superSU
+ @OldDroid (openKirin team) for bringing us TWRP.
+ @millo1978 for giving a fix to call recording
+ @NoctisCaelumFFXV for testing in his VNS-L21
+ @Chisetdel31260 for testing in his VNS-L31
+ @BSDgeek_Jake for creating the amazing MoaAB !!
+ @zgomot for the tip of enabling raw mode
i spent endless hours so as to make kangvip framework working on our p9 lite, every donation will be much appreciated!​

Screenshots Of ArseniK rom http://bit.ly/2sojvYG

ROOT METHODS
======FOR ARSENIK V2 ONLY==========
- chainfire's SuperSu 2.78 (it is preinstalled)
***update Supersu to latest version 2.82:
http://bit.ly/2ublmkr thanks to @Tecalote highly recommended)
-Magisk v13.3(updated to latest version)
the old method doesn't work well, safetynet isnt bypassed, this new method works like a charm :
Follow this steps so as to k-setting would not crash:
-go to supersu app and remove all permissions,dont revoke it,juste remove it.
1/flash this file http://bit.ly/2ubcR8L
2/open kernel adiutor mod, open the left panel and enable init.d
3/uninstall Supersu app
4/check if usb debugging is enabled
5/done
ps: in kernel adiutor you will see that selinux is enforcing, but in truth selinux is permissive
==========FOR ARSENIK V1/v1.1==========
- chainfire's SuperSu 2.78 (it is preinstalled)
***update Supersu to latest version 2.82:
https://drive.google.com/file/d/0B-fDlEGo76S0Q0RwalRZNDROZFU/view?usp=drivesdk thanks to @Tecalote !***(highly recommended)
-Magisk v13 (updated to latest version)
the old method doesn't work well, safetynet isnt bypassed, this new method works like a charm :
Follow this steps so as to k-setting would not crash:
-go to supersu app and remove all permissions,dont revoke it,juste remove it.
1/flash this file http://bit.ly/2udKEii
2/open kernel adiutor mod, open the left panel and enable init.d
3/uninstall Supersu app
4/check if usb debugging is enabled
5/done
ps: in kernel adiutor you will see that selinux is enforcing, but in truth selinux is permissive
NOTE : IF YOU FLASHED MAGISK AND YOU WANNA INSTALL SUPERSU, UNINSTALL MAGISK BEFORE AND THEN INSTALL SUPERSU

CHANGELOG
Arsenic + BugFixer
✓first release
Arsenik + BugFixer2 :
✓Fixed Hw call recorder
✓Fixed camera force close
Arsenik-V1.1
✓Fixed hw sound recorder force close
✓increased earpiece sound for best dual-speaker
✓changed interface of Viper4android
✓mixed Arsenik and BugFixer 2 in one flash-able zip
✓set google play as a system app(now you can wipe data without flashing gapps)
✓added rotation of the home screen
✓Now you can use Adblock from K-setting !
Arsenik-v1.1 + SmallUpdate.zip
✓added the majority of gapps
✓added raw mode, stock gallery app can even read .dng files also !!
Arsenik-v2.0 :
✓based on b385, with june security patch
✓changelog of kangV , translated to English using Google translator : https://pastebin.com/a3t7SMp3

SOME TIPS&TRICKS
HOW TO ENABLE RAW FORMAT:
1)Open camera app, swipe to the top(it wil enable pro mode
2) swipe to the left( it will enable setting)
3)click on raw format
4) Done
Raw mode will take two pictures, one in .dng format, and another one in .jpg format .So don't worry if you see two pictures instead of one
HOW TO ENABLE GOOGLE ASSISTANT
1/go to settings=>app=>google=>permissions
2/enable all the permission
3/go to setting=>app=>setting=>voice assistant & outpout and set google
4/go to google app=>setting=>setting=>phone=> 'ok google detection' =>retrain voice model
5/train your voice and go back to homescreen and tell ok google, google assistant will appear

five

Hi simo255
Call recording...
With Nougat I used this:
http://www.androidiani.com/forum/showthread.php?p=7832522
(Italian forum)
It worked good with B370...
Maybe with B380 also, but I didn't test it.
(Now I have Android 6)
Try and tell me
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk

Hello. Installation it went well, I will continue to discover. Thank you for all your work.

millo1978 said:
Hi simo255
Call recording...
With Nougat I used this:
http://www.androidiani.com/forum/showthread.php?p=7832522
(Italian forum)
It worked good with B370...
Maybe with B380 also, but I didn't test it.
(Now I have Android 6)
Try and tell me
Inviato dal mio HUAWEI VNS-L21 utilizzando Tapatalk
Click to expand...
Click to collapse
yes it works !
thank you!
i will upload a fix soon
Chisetdel31260 said:
Hello. Installation it went well, I will continue to discover. Thank you for all your work.
Click to expand...
Click to collapse
thanks, check please and tell me if there is any bug

i found new bug, camera force close sometimes,
will try to fix it asap

new root method! !
magisk v13

Got an error on TWRP while flashing "zip file is corrupted" . Im on L31C432B380 using OpenKirin TWRP

nitroax said:
Got an error on TWRP while flashing "zip file is corrupted" . Im on L31C432B380 using OpenKirin TWRP
Click to expand...
Click to collapse
corrupted? are u sure
check if you downloaded the files correctly

simo255 said:
new root method! !
magisk v13
Click to expand...
Click to collapse
We can install magisk v13 beta now, directly or wait?

Chisetdel31260 said:
We can install magisk v13 beta now, directly or wait?
Click to expand...
Click to collapse
flash the zip that i provided, otherwise it won't work

simo255 said:
corrupted? are u sure
check if you downloaded the files correctly
Click to expand...
Click to collapse
will try again but know i cant boot to the stock system. Flashing this rom will work anyway?

nitroax said:
will try again but know i cant boot to the stock system. Flashing this rom will work anyway?
Click to expand...
Click to collapse
yes
did you backup system ? if yes restore it !

simo255 said:
yes
did you backup system ? if yes restore it !
Click to expand...
Click to collapse
I have a "old" backup in my home PC so i didnt backed up this time. Will try flash again without restore the system. If it doesnt work, later i will put the backup in the SD and restore it

nitroax said:
I have a "old" backup in my home PC so i didnt backed up this time. Will try flash again without restore the system. If it doesnt work, later i will put the backup in the SD and restore it
Click to expand...
Click to collapse
old backups won't work with 3.1.1-0 recovery, i suggest you to flaqh system.img through fastboot

simo255 said:
old backups won't work with 3.1.1-0 recovery, i suggest you to flaqh system.img through fastboot
Click to expand...
Click to collapse
yeah i know, i will restore it with the same recovery i did the backup. Anyway i downloaded your rom again and will try to flash it again
EDIT: This time worked, booting right now. Will give the feedback later. Thanks

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)

Root using Magisk v14

Hello,
I just got my P10 (VTR-L29) yesterday, coming from a P8 Lite that I used to play a lot with and I already miss the adblock and the clean debloated system.
According to the new version of Magisk here, there is a new install method that works if you don't have a custom recovery like it used to be in the past. The new method modifies the boot.img via Magisk Manager, stores it in a folder and then you have to flash it with adb.
My question is: Do I have to unlock my phone in order to do that trick? Anyone else that tried something similar?

Nobody?
Maybe I'm not clear enough..
Steps to reproduce:
-install Magisk Manager 14 and use the inside app patcher
-find the patched boot.img on storage
-move the boot.img in PC storage
-use the PC in order to flash the patched boot.img
-reboot and wait
It's supposed to work that way but I don't want to unlock the bootloader,atleast for now.
Is it safe to do?

Xperias do not boot with the bootloader locked if boot.img is changed. I guess it will be the same for Huaweis.

So the only way to do that is to unlock the bootloader..seems like I have to do it lol.

Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?

Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.

Firicel69 said:
Working but I Guess that You unlocked the bootloader,right?
You can try to use the universal safetynet fix, flash it in twrp and check.
Click to expand...
Click to collapse
Already tried that (the new one for v14). Unfortunately, it didn't work.
Thank you anyway

garris_bibop said:
Magisk v14 is working on my device. Unfotunately, i cannot pass safetynet. How about you guys?
Click to expand...
Click to collapse
I had the same problem. Maybe my experience will help:
Open Magisk manager and check Log->Magisk. Are there any messages from MagiskHide? It should be.
Try this:
1. Open Magisk manager and disable Magisk hide.
2. Reboot
3. Open Magisk manager and enable Magisk hide.
I used commands in Terminal Emulator
Code:
su
magiskhide --disable
magiskhide --enable
At first it didn't work out but after a lot of desperate enabling/disabling and few reboots MagiskHide started to work (I couldn't determine the reason of its misbehaving).
For now I successfully pass SafetyNet checks.

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.