Database Users

V4A on AEX Nougat (tutorial)

I had a rough time with this so I thought I'd share my fix. This may work on other Nougat ROMs as well. If your ROM uses Chainfire SuperSU you can skip all of the Magisk stuff and go straight to step 4.
1: Clean install AEX + gapps
2: Boot system and update Magisk(via settings/Magisk Manager) and BusyBox(via play store app) and reboot
3: Flash Magisk SELinux Permissive Script
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
4: Use Root Explorer to copy ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk to System/Privapp and set permissions rw-r--r--
https://forum.xda-developers.com/showthread.php?t=2191223
5: Reboot, launch V4A app, grant Root, install driver, reboot
Bonus: AdAway works if copied to Privapp with correct permissions rw-r--r--, reboot and launch

aaron.a said:
I had a rough time with this so I thought I'd share my fix. This may work on other Nougat ROMs as well. If your ROM uses Chainfire SuperSU you can skip all of the Magisk stuff and go straight to step 4.
1: Clean install AEX + gapps
2: Boot system and update Magisk(via settings/Magisk Manager) and BusyBox(via play store app) and reboot
3: Flash Magisk SELinux Permissive Script
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-permissive-script-t3577549
4: Use Root Explorer to copy ViPER4Android_FX_v2505_A7.x_Nougat_IO_test_fix.apk to System/Privapp and set permissions rw-r--r--
https://forum.xda-developers.com/showthread.php?t=2191223
5: Reboot, launch V4A app, grant Root, install driver, reboot
Bonus: AdAway works if copied to Privapp with correct permissions rw-r--r--, reboot and launch
Click to expand...
Click to collapse
If you do so, I think you lost all benefit of systemless system, as you are touching directly to the system.

casual_kikoo said:
If you do so, I think you lost all benefit of systemless system, as you are touching directly to the system.
Click to expand...
Click to collapse
Good call. Not a problem for me. I think dudes selinux script enables permissive system wide which may also turn people off. But my app selection is minimal and I use my phone more like a media tool than anything else.

You don't need to change to Permissive at all. Just install V4A latest apk and flash the driver with Magisk. Works with Enforcing fine.

[V4A] Viper4Android I/O Error (Driver Installation Failure) [FIX]

Hey everyone! I seem to have found put together 3 methods of installing/bypassing the V4A App on android. These methods include:
Regular Installation, and 2 Error bypasses/fixes.
If you get the error "superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!", then you've come to the right place.
Requirements: ROOT, (maybe) TWRP (or anything you can flash the zip onto your phone with. With this tutorial I'll be using TWRP.)
If you don't have TWRP, here's the link to that \\ https://twrp.me/Devices/
Type in/select your device, click download, and flash it to your phone.
====================================================================================
Regular installation:
1.) Download V4A from Google Play Store \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) Open, and grant root permission.
3.) Install drivers, and reboot phone. DONE!
==================================================================================================
V4A SuperSU Manager Error:
1.) Download V4A from Google Play Store (the newest one) \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
Open it, grant permissions, click "install drivers" <- just get through the driver menu. This is a troubleshoot test. If it fails, keep going on with the tutorial. If not, You're A-Okay.
2.) Download V4A Flashable ZIP from here \\ https://drive.google.com/file/d/0By-5wpCgi7OHMjFZRU1PYXljbDQ/view
Drag and drop from your computer onto your phone in your "Downloads" folder.
3.) Open TWRP and click "Install" and navigate to your "Downloads" folder where you Installed the V4A Flashable ZIP (Viper4AndroidMM_v2.4.0.1.zip)
Install the ZIP in TWRP, and reboot.
4.) Open your apps/app menu, navigate to the new (it's an older version, but it's newly installed) V4A. It should be a purple logo instead of a blue logo. At this point in the tutorial, you should have both the Google Play Store APK, and the TWRP Flashed APK. Open the PURPLE V4A, and Install drivers now.
5.) Reboot phone, go to the NEW (blue logo) V4A, and install drivers on that one too.
The rest is clean-up. You may now delete the older version of V4A (purple logo).
========================================================
Bypass/fix #2, The SELinuxModeChanger issue:
1.) Download V4A (newest version) from \\ https://play.google.com/store/apps/details?id=com.vipercn.viper4android_v2_fx&hl=en
2.) (Grant root access) Attempt to install drivers. If this succeeds, then Idk why you're still here.
3.) Download SELinuxModeChanger APK from \\ http://forum.xda-developers.com/devdb/project/dl/?id=12506
4.) Open it, grant root access, and click "Permissive".
5.) Re-boot phone, and open V4A when done.
6.) Install drivers!
Sources/credit go to:
https://forum.xda-developers.com/showthread.php?t=2524485
^ SELinuxModeChanger
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
^ Driver install failure/ Disc I/O error/"superuser manager doesn't allow app to access su or you don't have root at all. fix this to use this selinuxmodechanger!" error
https://twrp.me/about/
^ Team Win
https://forum.xda-developers.com/member.php?u=7249915
^ Me, I contributed very small amounts, that's why I'm last (I guess I contributed some common sense .. ?)

what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.

masri1987 said:
what if you already have permissive kernel , and still get i\o error during driver install?
using android auto 7.1.1 head unit.
Click to expand...
Click to collapse
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8

zahidm said:
Follow this guide for installation if already permissive
https://forum.xda-developers.com/moto-x-2014/themes-apps/mod-viper-4-android-oreo-tested-t3700287
For i\o error you should do step No.8
Click to expand...
Click to collapse
my head unit doesn't have vendor/etc or the audio effects configuration file....

Thanks
I had the Viper.apk from their website and the Google play version loaded also and I was getting the I/O error when trying to load the driver and the Google Play version didn't work at all. I did try to load SuperSU and busybox before attempting to load the driver again and it still didn't work. I don't know about permissive kernel, I'm running Resurrection ROM on a Rooted Note 3. The way I got this to work was to uninstalled the V4A Viper APK version that I had retrieved and loaded from their website. Next I booted into TWRP recovery and installed the V4A Flashable ZIP from the link that I found here. Next I ran the flashed version and granted SU permissions when asked during the install driver process. The driver finally loaded and bingo it works now.

Viper4android
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance

Banty448 said:
Hi I have installed viper4android fx but in Driver status it shows no processing my phone(samsung j700f) is rooted with Supersu and using Wycked custom Rom nougat based I have done All the method like rename audio_effect.conf file but nothing to happened. All are waste of time.i spend too much time on xda site for solution but not found any solution...can anybody help me please?...Sorry for my bad English.. Thanx in Advance
Click to expand...
Click to collapse
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot

zahidm said:
Follow simple steps, first Rename file.bak
Then flash V4A,
Than open V4a it will ask to install driver
Just hit install and wait, it freez for sometime.. and it will say done
Reboot
Click to expand...
Click to collapse
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx

Banty448 said:
But I did it already many times but U tell me little bit different you said rename it before flashing but I did it After flashing .I flashed the zip file and after that rename than open Viper4android fx...ok I will try it...Thanx
Click to expand...
Click to collapse
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk

0
zahidm said:
You have to rename file before opening V4A app for the first time, now you rename it before or after flashing no matter,
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I already told u that I did it before opening the v4a

Banty448 said:
0
I already told u that I did it before opening the v4a
Click to expand...
Click to collapse
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk

zahidm said:
The error you are saying it never been seen, please try again
Sent from my Nokia 5.1 Plus using Tapatalk
Click to expand...
Click to collapse
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies?

Banty448 said:
I have done it many times but nothing happened. I tired to install this so now I install Devinebeats it's working fine.Thanx for us replies[emoji106]
Click to expand...
Click to collapse
You didn't followed this guide?
https://forum.xda-developers.com/mo...od-viper-4-android-oreo-tested-t3700287/page2
Sent from my Nokia 5.1 Plus using Tapatalk

When I install drivers for ViPER4Android FX I get "Driver installed, please reboot your device." and when I reboot, I'm asked to install drivers again. Did anyone figure out how to successfully install these drivers? I saw fixed around the forum, but they don't seem to work for me.
My phone huawei p10 lite rom Resurrection Remix OS Beta 3!

[ROOT][Magisk 14][09/11/2017] SUPER Easy systemless root for B580+

Since OTA updates NXT-L09CxxxB580+ for our devices is out and because of the fixes in the kernel, we are now able to root our device using Magisk.
This is a step-by-step guide leading you throughout the process and also stating the pros of using Magisk over using SuperSU.
News:
09/11/2017
- Magisk was updated to v14 which adds more root hiding mechanisms and also more devices compatibility.
07/18/2017
- Magisk was updated to version 13.3 and will once again pass SafetyNet without any issues
- To update, just open MagiskManager and press Download and Install (if you are new to Magisk, just follow guide below)
07/14/2017
- Google updated SafetyNet and Magisk devices will not pass it
Pros of using Magisk over SuperSU:
Automatic updates
Does not break OTA updates
Does not break SafetyNet (you will be able to use AndroidPay, play Pokemon Go, install Netflix from Google Play and use apps requiring SafetyNet pass)
Ability to install modules from the repository (much like xposed modules)
Before installation:
Unlock your bootloader
Make sure you have stock boot.img
Make sure you are on B580+ as Magisk cannot be installed on older versions
Installation:
Flash this recovery in fastboot: https://forum.xda-developers.com/mate-8/orig-development/twrp-t3576364
Flash latest Magisk in TWRP recovery: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Boot into system
Check your apps for Magisk Manager
[OPTIONAL] In the magisk manager, you can check if you pass SafetyNet
Troubleshooting:
Magisk Manager was not installed
- Open the Magisk.zip, inside open common folder and install magisk.apk
SafetyNet does not pass
- First try disabling and enabling Magisk Hide in the Magisk Manager
- If above does not help open stock Huawei dialer, dial *#*#2846579#*#*, tap Background settings, tap LOG settings, check all checkboxes, open Magisk Manager and disable and enable Magisk Hide
Supported devices:
All NXT-L29 B580+ devices
All NXT-L09 B580+ devices
All other Mate 8 versions with B580+
Basically any other device as Magisk is not device dependent (works with like 95% of all devices, as long as the device's kernel supports loop mount and few other things)
My Magisk Modules for Mate 8:
[Magisk] Official Huawei Automatic Call Recorder
Hope this will help you guys!

car nikolaj
. I recommend this app to anyone who want for the root acces. :good::good::good::good::good::good::good:

Does this method and the TWRP attached work on B585?
Thanks.

Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?

xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
Same here. CTS profile mismatch
Fresh B581

Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?

necc0 said:
Does this method and the TWRP attached work on B585?
Thanks.
Click to expand...
Click to collapse
Yes
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
sZx1 said:
Same here. CTS profile mismatch
Fresh B581
Click to expand...
Click to collapse
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
shestolemyusrname said:
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
Click to expand...
Click to collapse
You just press uninstall button in Magisk manager

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?

Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk

woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?

Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk

Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
xxlap1xx said:
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Open Magisk Settings and enable Systemless hosts data.
Systemless root means you can't directly edit /system partition, because editing it voids SafetyNet. Magisk uses Magic Mount to systemlessly replace /system files and folders on-the-fly without actually modifying the original ones. All you need is appropriate modules from magisk manager "Downloads" tab.

woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
Try installing it as user app and use App Systemizer module in magisk manager to convert it to system app.

xxlap1xx said:
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Yea you are right, I have it working, but the process is a bit tedious. We better wait for new Magisk version, where it should be fixed.

shestolemyusrname said:
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Click to expand...
Click to collapse
Keep it Read Only.

Boosik said:
Open Magisk Settings and enable Systemless hosts data.
Click to expand...
Click to collapse
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.

Hilton.Swart said:
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Click to expand...
Click to collapse
sZx1 said:
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Click to expand...
Click to collapse
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Boosik said:
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Click to expand...
Click to collapse
Can you, please, share. I'm pretty handy with terminal and willing to experiment. Worst - have to return to stock.
Thanks

Viper4Arise on Android Oreo 8.1

For anyone who's interested, here's what I did. based on the directions given by quinny899 in the thread here: https://forum.xda-developers.com/pixel-2-xl/help/viper4android-8-1-0-t3711474
I used the contents of the ZIP posted by quinny899 (for step 9, below) in post #8 on that thread: https://forum.xda-developers.com/showpost.php?p=74681544&postcount=8
The steps I took were:
1. Clean install of the Android 8.1 full factory images (with the -w option removed from the flash-all.bat file)
2. Completed the initial set up, then got rid of the lockscreen PIN (so that I wouldn't have decryption issues with TWRP in the next steps)
3. Put phone into fastboot, then booted into the TWRP 3.2 image
4. Installed Magisk (version 14.1456 beta)
5. Rebooted
6. Installed Buysbox for Magisk, and downloaded (did not install) the Vipe4Android Magisk module by ShadySquirrel
7. Extracted the Viper4Android.apk from the Magisk module that I downloaded
8. Rebooted
9. Copied the contents of quinny89's zip file into root/Magisk (using SolidExplorer, after granting it root privileges)
10. Rebooted. Now, Magisk thinks it has Viper installed (but it doesn't, yet!)
11. Install the Viper4Android.apk that I extracted in Step 7, as a normal user app
12. Reboot
13. In Viper4Android, put it in Compatibility mode, enable Developer mode, and disable seLinux (or use some other method to set seLinux to permissive, I suppose)
14. Reboot, and Viper is working for phone speakers, and Bluetooth, tested with Spotify and Poweramp. Convolvers, and all
All credit to quinny899 for figuring this out for the PixelXL.

anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks

quinejh said:
anyone have a link to this busybox? man I search and get all kinds of junk but not the one I need. thanks
Click to expand...
Click to collapse
Can't you download and install it directly from MagiskManager?

pavanmaverick said:
Can't you download and install it directly from MagiskManager?
Click to expand...
Click to collapse
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing

quinejh said:
Strangest thing. The one that the manager downloads doesn't work. But I found another link in I believe it was the xl thread and after flashing it when I start playing music I get a viper has stopped error but u can hear it processing
Click to expand...
Click to collapse
Weird, indeed! Glad you got it working though!

I couldn't get it working using the apk from the magisk viper 14+, but using the apk from v4afx_v2.2.zip worked perfect.
---------- Post added at 04:02 AM ---------- Previous post was at 03:44 AM ----------
I notice with this method for viper it takes a sec to kick in when I change songs, which makes a little shift at the beginning. Anyone know how to get rid of that?

This works.
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058/page126

Did any of you have to use a Magisk SELinux Permissive Script to get Viper to work?
If i disable the script in Magisk, Viper doesnt, work but if the script is enabled, it works.
IF you guys aren't using a script how did you get viper to work?
Im using the following Magisk Modules
Audio Modification Library v2.5 by ahrion, zackptg5
Busybox for Android NDK v1.27.2 by osm0sis
Magisk SElinux Permissive Script v1.1 by jman420
ViPER4Android FX v2.5 (2.3.4.0) by ahrion, zackptg5

I'm using the permissive script. Permissive is required for viper.

Question iOS Emoji Magisk module not working on 1.1.8 (ROOT)

Hello guys,
ive been using magisk module of ios emoji (from here) just fine on 1.1.7. Then I updated on 1.1.8 (via OTA method - lost root, fastboot booted patched boot.img - rooted again) and the module suddenly stopped working - simply doesnt appear anywhere. I tried to delete it, install it again, reboot device, but no luck. Tried even different modules of iOS emojis, still not working.
My ionly other module Fullscreen/immersive gestures is working fine after the update. Magisk app updated on thle latest version.
Any idea what could be the issue?
Thank you!

Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update

paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
You're a life saver, thank you so much, I really appreciate it, worked perfectly!

paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
I couldn't get it to work no matter what procedure I tried to follow. Currently running on 1.1.7 with the 16.4 beta magisk module but I have zero luck.
I just noticed that I'm a beta tester of GBoard. Can it have an impact? Not sure if anyone tried it with Beta version.