Database Users

Viper4Android Fix for Lollipop

Most Samsung users reported that V4A is not working after upgrading to lollipop cause of the unswitchable SELinux, switching SELinux mode compromises the security of the device, so here is the solution without flashing custom kernel:
Note:
*This method should be used with Systemless SU(not magisk) installed*
Con's:
Not working with some music apps with built in equalizers
Steps:
1. Assuming that you have installed systemless root, but still check if /su/bin/supolicy exists...* WORKING IS NOT GUARANTEED ON OTHER SYSTEMLESS METHODS eg. Magisk*
2. Download the latest build of V4A in this thread: https://www.google.com.ph/url?sa=t&...uRG6XJ1DsKgOZngeg&sig2=O8sZ4LawAMMb_9I4inOJ-Q
3. Install the apk as a system app and reboot, after open Root Explorer and create su.d folder in /system partition , set permissions rwxr-xr-x
4. Create 50viper.sh inside the folder and edit and paste:
#! /system/bin/sh
/su/bin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
5. Save and set permissions rwxr-xr-x
6. Now launch V4A and grant permissions and install drivers.
7. After finished installing of drivers, reboot
8. Disable and clear data of SoundAlive in settings and reboot
Tested with my device: SM - T235(Galaxy Tab 4 7.0 LTE)

http://forum.xda-developers.com/showpost.php?p=65106000

Viper4Android Installation Guide for Stock ROM and Official LineageOS

LineageOS
>Root addon
>busybox install to /system/xbin
>install SELinuxmodechanger apk set to permissive always (v4a will stop working if enforcing..confirmed)
>install v4a nougat-io fix apk (present in ViPER4Android_FX_v2505.zip)
>can disable fx music app
>reboot
>install v4a drivers from viper app
>reboot
>enjoy
Stock B331 rom
>Root with SuperSu
>busybox install to /system/xbin
>install Viper4Android SELinux Policy fix via **TWRP** recovery
>install v4a apk (present in ViPER4Android_FX_v2505.zip) [do not install v4a-nougat-io apk]
>can disable fx music app
>reboot
>install v4a drivers from viper app
>reboot
>enjoy

Or just use Magisk + V4A addon and do everything systemlessly without that much hassle.
Why? No need to patch SELinux (works under Enforced), no need for busybox, no need for flashed zips and more important - no modifications to the system partition. Literally easiest, three step process, you'll find out there.

ShadySquirrel said:
Or just use Magisk + V4A addon and do everything systemlessly without that much hassle.
Why? No need to patch SELinux (works under Enforced), no need for busybox, no need for flashed zips and more important - no modifications to the system partition. Literally easiest, three step process, you'll find out there.
Click to expand...
Click to collapse
lol:laugh::laugh::laugh:

ViPER4Android on Magisk

I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.

Tried this on an HTC One M8 with LOS and Team M8 Kernel - it caused a bootloop for me.

Help with step 4 please...
EncryptedCurse said:
I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.
Click to expand...
Click to collapse
Sorry new to modding,
Step 4: not sure exactly where to paste? I tried but when saving I get error no permission..? I've been trying to get this working for weeks...
SM-G925F
Stock Rom
Magisk 13.3
Busybox. Stericson

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.

Magisk 25.1 for Fire TV

As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"

Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?

Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?

Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI

mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.

Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho

Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...

Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.

tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?

hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.

mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release

tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks

What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.

yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp

I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)

I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.