V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks
No
Did you install from magisk? Not twrp. Follow the instructions as mentioned above
ariber14 said:
Did you install from magisk? Not twrp. Follow the instructions as mentioned above
Click to expand...
Click to collapse
Yes, from magisk.
I will try again when reinstall miui eu.
omerhodzic1 said:
Yes, from magisk.
I will try again when reinstall miui eu.
Click to expand...
Click to collapse
Hey, miui eu is working?
---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------
[/COLOR]
Linkonlk said:
Hey, miui eu is working?
Click to expand...
Click to collapse
Found it on the telegram group.
Redmi Note 8 Pro | OFFICIAL
Redmi Note 8 Pro - Official Telegram Group
t.me/RedmiNote8ProOfficial
ariber14 said:
V4A Fx installation (Rooted with magisk required)
Download following modules:
https://drive.google.com/folderview?id=10Q_4QsFAe8cW63GH3VrM0jtuIOAPP8t1
1.Install magisk_selinux_manager_v1.0.zip magisk module in magisk manager and set selinux to permissive.
2.install ViPER4Android_FX-v2.7.1.0(2710).zip magisk module in magisk manager.(requires internet)
3.Reboot and open V4A it will ask for driver installation .Allow it
4.After installation of driver it will automatically reboot .
5.Enjoy V4A
Credits to @santoshhh000
If you like this post press thanks
Click to expand...
Click to collapse
Which miui you install?
omerhodzic1 said:
Which miui you install?
Click to expand...
Click to collapse
On miui 11.0.2.0 eu
ariber14 said:
On miui 11.0.2.0 eu
Click to expand...
Click to collapse
I tried multiple times, miui eu 11.0.2.0, with a clean install at the end, without an account and any backup, different versions of magisk, ect. 1 or 2 sim card.
With one, one sim card work, when I installed the Viper with 2 sim, stop working both.
Maybe I'll be lucky with some new version. The Viper is my favorite.
Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned
ariber14 said:
Search for a zip called clean+soundmod.zip.it will remove any audio mod that might create conflict.flash it ftom twrp then repeat the procedure again as mentioned
Click to expand...
Click to collapse
Can you post it here. I could not find it.
Here it is. Flash it from twrp then restart
ariber14 said:
Here it is. Flash it from twrp then restart
Click to expand...
Click to collapse
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work
MarkLev said:
Thank you!!
Your phone is using xiaomi.eu rom, but Is it China version or Global version?
I have China one with same xiaomi.eu rom, but cant seem to make viper work
Click to expand...
Click to collapse
M1906G7G - Global 64mb - not working for now.
omerhodzic1 said:
M1906G7G - Global 64mb - not working for now.
Click to expand...
Click to collapse
Problem with magisk_selinux_manager_v1.0.zip
If use 2 SIM they stop working.
Viper working with setenforce 0 in terminal.
Found this on telegram group:
t.me/RedmiNote8ProOfficial
I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.
santoshhh000 said:
I have noticed . Selinux manager module when flashed through latest magisk .It Doesn't work ,so if possible flash it through older version magisk 20.0 or earlier version .After that you can update your magisk to latest.
Click to expand...
Click to collapse
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,
omerhodzic1 said:
I tried with magisk 19 and the problem is the same.
I also have a problem with SIM cards, when install magisk_selinux_manager_v1.0.zip with permissive, only when I take out one SIM card GSM works, when two are not working, no registered cards in mob, if install with enforceing is ok, that's weird. It is no problem for me to use the terminal, it is also safer for the system, it may be safer not to be in permissive mode all the time.
Thank you for your help.
And most importantly, I have ViPER4A!
All the best,
Click to expand...
Click to collapse
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer
MarkLev said:
1. Install SELinux Mode Changer app from here
2. Install lates viper4android app
3. Start SELinux Mode Changer and set to "permissive" then start viper4android and Enjoy!
you can set autostart for SELinux Mode Changer
Click to expand...
Click to collapse
That's it.
Thnx
I totally forgot Tasker.
Related
Good news for Mi A1 user's
I tested Dolby Atmos™ Axon 7 Oreo port
Standard 20180219 -
- Expiration met for the Dolby Atmos
Demo Video component after confirmation
of its lack for volume support indicated a
native "bug" and not a porting shortcoming.
- A reduction of 67MB, uncompressed, now
totaling 15.49MB uncompressed, without
the Dolby Atmos Demo Video component.
- Abandonment of the recently introduced
libsurround_proc.so library (suspect of recent
audio unpleasantness) from the Nokia
6 Official Oreo build that was paired with
that same firmware's Dolby Surround Sound
Settings' menu as an additional apk that is
currently still included and still in its trial
period.
- SUBSTANTIAL adjustments, additions, and
improvements to every script - installation
and boot scripts, the most comprehensive
update for this shell component thus far.
Warning !!!
Originally Posted by Ni9e.
If after flashing this you are stuck on bootloop or boot screen then dont worry it happened with me aswell and here is the complete tutorial to successfully install this module. Follow step by step:
1. Reboot to recovery and flash Dolby file
2. Goto Reboot menu in recovery and select partition B
3. Now Reboot to recovery again
4. Flash Dolby file again
5. Goto Reboot menu and this time select partition A
6. Reboot system now and enjoy !!!
https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
Flash ok with TWRP 3.2.1.2 Magisk v16.4
Could you give me a feedback on your audio impressions of this Dolby Atmos ....
Works fine on mi a1 with last firmware.
Thanks for share.
app force closes before even starting
Does it require the magisk audio modification library?
Alexx237 said:
app force closes before even starting
Does it require the magisk audio modification library?
Click to expand...
Click to collapse
Same here , it says "DolbyAtmos has stopped"
Alexx237 said:
app force closes before even starting
Does it require the magisk audio modification library?
Click to expand...
Click to collapse
AlwaysWin said:
Same here , it says "DolbyAtmos has stopped"
Click to expand...
Click to collapse
Have installed SELinux permissive script module in Magisk?
pedrazadixon said:
Have installed SELinux permissive script module in Magisk?
Click to expand...
Click to collapse
Yes have it installed already v1.1
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
Device Mi A1 , with Magisk v15.3 and TWRP 3.2.1 SELinux permissive v1.1
it force closed on me too, i have installed selinux permissive script v1.2
pedrazadixon said:
Have installed SELinux permissive script module in Magisk?
Click to expand...
Click to collapse
Yes, I have the 1.2 version installed
Alexx237 said:
Yes, I have the 1.2 version installed
Click to expand...
Click to collapse
Works fine here .
Working fine for me now , The issue was with the SELinux magisk module , I just completely removed it and reboot , everything works fine now
Alexx237 said:
app force closes before even starting
Does it require the magisk audio modification library?
Click to expand...
Click to collapse
AlwaysWin said:
Same here , it says "DolbyAtmos has stopped"
Click to expand...
Click to collapse
AlwaysWin said:
Yes have it installed already v1.1
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
Device Mi A1 , with Magisk v15.3 and TWRP 3.2.1 SELinux permissive v1.1
Click to expand...
Click to collapse
jack404 said:
it force closed on me too, i have installed selinux permissive script v1.2
Click to expand...
Click to collapse
Alexx237 said:
Yes, I have the 1.2 version installed
Click to expand...
Click to collapse
Reinstall pemissive module restart
If still not working
Flash dolby zip again without deleting it
Working fine for me now
t0per666 said:
Reinstall pemissive module restart
If still not working
Flash dolby zip again without deleting it
Working fine for me now
Click to expand...
Click to collapse
Working fine here too , prblm was with the module itself!
Thanks though
Alexx237 said:
Yes, I have the 1.2 version installed
Click to expand...
Click to collapse
No other mod sound installed ?
give me screenshot of module in magisk
For all who have trouble to run Dolby Atmos make sure that you have no other sound module that could cause a bug ... and install selinux magisk 1.2 before flashing dolby Atmos zip with TWRP 3.2.1.1 ok Boys
laugeek57 said:
No other mod sound installed ?
give me screenshot of module in magisk
Click to expand...
Click to collapse
So, I did a fresh rom install;
I then installed magisk, through magisk I installed the SElinux permissive script(v1.2), and proceeded to flash dolby atmos.
But still... It force closes...
Alexx237 said:
So, I did a fresh rom install;
I then installed magisk, through magisk I installed the SElinux permissive script(v1.2), and proceeded to flash dolby atmos.
But still... It force closes...
Click to expand...
Click to collapse
Rom? prerooted 16 jan bye Sooti or other?
Screenshot modules in magisk
laugeek57 said:
Devices and Rom ??
Screenshot modules in magisk
Click to expand...
Click to collapse
I tried it on both A-ONE 8.0 - OPR1.170623.026 Jan, and 7.12.29 - OPR1.170623.026.
But the result is the same
Oh, and The only modules in magisk are dolby atmos, SElinux permissive script v1.2
Alexx237 said:
I tried it on both A-ONE 8.0 - OPR1.170623.026 Jan, and 7.12.29 - OPR1.170623.026.
But the result is the same
Oh, and The only modules in magisk are dolby atmos, SElinux permissive script v1.2
Click to expand...
Click to collapse
There is a step that did not work properly because before posting this thread I installed and reinstalled this module several times and it worked perfectly
What version of Dolby Atmos ?
laugeek57 said:
There is a step that did not work properly because before posting this thread I installed and reinstalled this module several times and it worked perfectly
What version of Dolby Atmos ?
Click to expand...
Click to collapse
I don't know what I may have done wrong, mate :/
The version of dolby I flashed is: DolbyAtmos_Axon7_Oreo_20180122-2(I also tried 20180122-1)
Has anyone been able to get a v4a module working on 16.4 and the may update? I tried installing the module by viper50 and ahirion that has worked so well in the past... Doesn't seem to be enabling for me this time around for some reason. Any ideas?
Or other mods to recommend?
V4a v2.5.05 working fine with magisk 16.4 and may update here.
EnIXmA said:
V4a v2.5.05 working fine with magisk 16.4 and may update here.
Click to expand...
Click to collapse
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.
Taebom said:
Same here, everything working smoothly with v4afx_v1.6.9.zip and magisk 16.4. Viper also works on P dp2.
Click to expand...
Click to collapse
Are you flashing in magisk or twrp? Which module are you using? Thanks!
I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.
Strephon Alkhalikoi said:
I'm neither of the other posters, but flash V4A via Magisk using the module authored by Viper520, ZhuHang, Ahrion, and Zackptg5. Be certain that you select the new driver and the materialized version of the app for V4A to work properly.
Click to expand...
Click to collapse
This ^^ : point upwards: ! Especially the underlined part; it took me a whole lot of trial and error to figure this last part out...
In any case, I used the latest Magisk module (if you check the details of the modules, it'll show when it was last updated). If anything, supposedly you could just install straight away, but V4A gave me errors. I had to uninstall the existing V4A, reboot, install via Magisk module, and reboot before it worked. You (@Cowbell_Guy) might, at the very least, have to walk through the same steps for whatever reason...
Hope this helps...
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
zk_eu said:
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
Click to expand...
Click to collapse
I´m in CrDroid Pie + Magisk 18.1 + Riru 18 + EdXposed 0.4.01_beta_SNAPSHOT and all working fine
Have a similar problem when haved 3.1.7 but i´m not sure the EdXposed, reinstalled crdroid and works fine, now upgraded to EdXposed 0.4.01_beta_SNAPSHOT and all works fine
I tried the EdXposed 0.4.01_beta_SNAPSHOT, but unfortunately it is the same.
zk_eu said:
I tried the EdXposed 0.4.01_beta_SNAPSHOT, but unfortunately it is the same.
Click to expand...
Click to collapse
Maybe the rom or kernel, i´m in custom rom and all works fine
Riru 17.1
EdXposed 3.1.7
Stock pie 10.0.7.0
No issues here
I think I have found the problem. I seems that EdXposed and Camera 2 API are somehow interfering with each other.
I does not matter if I use Magisk module Camera2_API_Enabler-v1.0.0 or activate camera 2 API threw SU ADB with:
1. setprop persist.camera.HAL3.enabled 1
2. setprop persist.camera.eis.enabled 1
The result is always the same. My mobile data won't work. If I disable Camera 2 API, then mobile data works.
Well, I posted this bug on EdXposed GitHub site and got an answer. Apparently this bug can be solved by changing selinux to permissive. Worked also for me (even on v0.4.1.2_beta). Hope it helps someone with the same issue.
Can someone send a quick guide on installation process?
ncar123 said:
Can someone send a quick guide on installation process?
Click to expand...
Click to collapse
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
leechgid said:
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
Click to expand...
Click to collapse
DONE
but my gcan doesn't work...
---------- Post added at 02:27 PM ---------- Previous post was at 01:47 PM ----------
zk_eu said:
Well, I posted this bug on EdXposed GitHub site and got an answer. Apparently this bug can be solved by changing selinux to permissive. Worked also for me (even on v0.4.1.2_beta). Hope it helps someone with the same issue.
Click to expand...
Click to collapse
Can you elaborate?
ncar123 said:
DONE
but my gcan doesn't work...
---------- Post added at 02:27 PM ---------- Previous post was at 01:47 PM ----------
Can you elaborate?
Click to expand...
Click to collapse
Gcam nothing about with Xposed
Maybe you need activate Camera2Api or need a custom kernel (Ex. Butterfly)
Have a stock Rom o custom rom?
leechgid said:
Gcam nothing about with Xposed
Maybe you need activate Camera2Api or need a custom kernel (Ex. Butterfly)
Have a stock Rom o custom rom?
Click to expand...
Click to collapse
Stock rom
root
Magisk
Edxposed
camera2api in magisk
10.0.9.0
Also tried manually in build.prop
Doesn't work....
ncar123 said:
Stock rom
root
Magisk
Edxposed
camera2api in magisk
10.0.9.0
Also tried manually in build.prop
Doesn't work....
Click to expand...
Click to collapse
Uninstall camera2api in magisk
Try with this
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414
Steps -> 1,3,4,5,10,11 and try with this cam https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_6.2.024_IPSGCA_V18ORE.apk
leechgid said:
Uninstall camera2api in magisk
Try with this
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414
Steps -> 1,3,4,5,10,11 and try with this cam https://f.celsoazevedo.com/file/cfiles/gcm1/MGC_6.2.024_IPSGCA_V18ORE.apk
Click to expand...
Click to collapse
Tried manually in build.prop, it doesn't work maybe it is something in selinux
---------- Post added at 06:16 PM ---------- Previous post was at 05:35 PM ----------
Something really weird, turned the selinux to permissive , didn't work, tuned back to enforcing and now it works
Well hope it stays that way, thx everyone
EDIT:
Now it stopped working, I'm clueless
2ndEdit:
Played with build.prop and magisk camera2api
It works, I guess some stuff turn that off, well I don't know
leechgid said:
Download the files:
EdXposed Manager
https://github.com/ElderDrivers/EdX...eowcat.edxposed.manager-4.5.0-450-release.apk
--------------
Riru-Core
Ver. 19 (If you use Magisk 19+)
https://github.com/RikkaApps/Riru/releases/download/v19/magisk-riru-core-v19.zip
Ver. 19.1 (if you use Magisk 17-18.+)
https://github.com/RikkaApps/Riru/releases/download/v19.1/riru-core-v19.1-magisk-v17.zip
--------------
EdXposed (Select one, i´m using Sandhook without problems)
SandHook
https://github.com/ElderDrivers/EdX...osed-SandHook-v0.4.5.1_beta.4463.-release.zip
or
Yahfa
https://github.com/ElderDrivers/EdX...dXposed-YAHFA-v0.4.5.1_beta.4463.-release.zip
After download the files, intall EdXposed Manager apk
Go to Magisk Manager -> Modules -> + -> Flash Riru-Core (Not reboot)
Modules -> + -> Flash EdXposed
Reboot System
Thats all
Click to expand...
Click to collapse
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
What should I do:
Flash the original boot image, or can I flash the magisk patched img file ?
Thanx !
I was using it with AOSP Extended Last build and magisk 18.1...but signal phone is not working sometimes...so i leave it.
takhama said:
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
What should I do:
Flash the original boot image, or can I flash the magisk patched img file ?
Thanx !
Click to expand...
Click to collapse
It is strange:
If I flash the stock image, the phone will start
If I reflash it with the magisk patched file, it will stay stuck (I removed edxspoed apk, and resinstalled magisk apk)... This edxposed framewok seems to have broken something. I think I'm good to reflash the ROM....
takhama said:
Hi,
I followed this method, and my phone is now stuck on the loading bar on start-up (the multi color moving bar)... What happened ?
Click to expand...
Click to collapse
EdXposed is a magisk module. If you disable Magisk or EdXposed then the system will boot again. Flashing/booting the vanilla boot image is one way to do it. You could then use Magisk app to disable EdXposed.
Another way is to start TWRP and use the shell to modify/remove files in /data. I don't know the specifics of this, but the mm (Magisk manager cli) module puts a script in /sdcard that allows managing Magisk modules from TWRP.
a1291762 said:
EdXposed is a magisk module. If you disable Magisk or EdXposed then the system will boot again. Flashing/booting the vanilla boot image is one way to do it. You could then use Magisk app to disable EdXposed.
Another way is to start TWRP and use the shell to modify/remove files in /data. I don't know the specifics of this, but the mm (Magisk manager cli) module puts a script in /sdcard that allows managing Magisk modules from TWRP.
Click to expand...
Click to collapse
Unfortunately, I am not able to do this:
My phone can start with the stock boot image, but here magisk will show no module (because saying magisk is not installed)
With the magisk patched boot image , impossibe to start....
I'll try using TWRP before flashing everything. Thanx !
zk_eu said:
Hi,
does anybody use EdXposed module for Magisk?
I flashed Riru core v18 and EdXposed v0.3.1.7_beta in Magisk.
If EdXposed v0.3.1.7_beta magisk module is activated, mobile data does not work? Is anyone facing a similar problem?
The problem is definitly with EdXposed, since it does not matter which Riru core version I use. If I use EdXposed v0.2.9.9_beta2, then mobila data works, but this version of EdXposed is really buggy.
I am on stock Pie rom V10.0.7, but it was the same with V10.0.4.
Click to expand...
Click to collapse
This is an outdated EdXposed, Riru - Core and Magisk. I recommend installing the latest one.
Hello I got the OnePlus 9 pro as a birthday gift it's the unlocked version wanted to know if there is a guide on how to install viper on the plus9 pro I have the 7pro with viper and it's amazing
Root your phone (via Magisk)
Download the v4a.zip from the official thread
Install the .zip via the Magisk app (install as a module)
Reboot
et voila!
dxcim said:
Root your phone (via Magisk)
Download the v4a.zip from the official thread
Install the .zip via the Magisk app (install as a module)
Reboot
et voila!
Click to expand...
Click to collapse
Man I dumb on how is it
gokou46 said:
Man I dumb on how is it
Click to expand...
Click to collapse
you're talking about Viper4Android right? the audio eq thingie?
dxcim said:
you're talking about Viper4Android right? the audio eq thingie?
Click to expand...
Click to collapse
Yes viper I did not know it was that easy to install
I was thinking that you are talking about Viper rom. That's Awesome !
dxcim said:
Root your phone (via Magisk)
Download the v4a.zip from the official thread
Install the .zip via the Magisk app (install as a module)
Reboot
et voila!
Click to expand...
Click to collapse
That will not work, you just get a driver install infinite loop in V4A app. You need to install JamesDSP before V4A.
Check this thread for details, read all the posts on the 1st page
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Arcide said:
That will not work, you just get a driver install infinite loop in V4A app. You need to install JamesDSP before V4A.
Check this thread for details, read all the posts on the 1st page
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Click to expand...
Click to collapse
I guess the JDSP requirement is specific to the 9 Pro then. I just followed the steps I mentioned for my 8T and worked fine. I did get a processing issue (not related to driver installation), but I found a fix in the V4A thread. You can go through the official V4A thread here.
I'm using Dolby Atmos and I think it works fine for me
demonio666 said:
I'm using Dolby Atmos and I think it works fine for me
Click to expand...
Click to collapse
What does that have to do with V4A?
dxcim said:
I guess the JDSP requirement is specific to the 9 Pro then. I just followed the steps I mentioned for my 8T and worked fine. I did get a processing issue (not related to driver installation), but I found a fix in the V4A thread. You can go through the official V4A thread here.
Click to expand...
Click to collapse
Yeah it's specific here I guess. All these people, including me, had this issue. Even after managing to install V4A properly I'm still on JamesDSP, as V4A gives me issues with convolvers and profile loading.
Hello everyone,
After a bit of research, I found out that many people with a OnePlus 9 Pro, myself included, struggled with installing viper4android.
Luckily and accidentally I discovered this GitHub repository!
It all works only with a magisk module installation.
After a reboot you're good to go.
I've tested it on Nameless AOSP 13 with SELinux enforcing.
Users have reported incompatibility with OxygenOS.
Nonetheless you can try and see if it works for you.
Cheers!
WOW
It actually worked, what a godsend. Thank you for this kind sir. I've tried so many methods and this is the solution.
I couldn't get it to work on oos13 ...
ffejy462 said:
I couldn't get it to work on oos13 ...
Click to expand...
Click to collapse
Thank you for the info!!
Just switched to nameless from extended. No worky on nameless
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Try with JamesDSP, it usually has fewer compatibility issues and works just as well as V4A.
bbortel93 said:
Just switched to nameless from extended. No worky on nameless
Click to expand...
Click to collapse
Naah... I'm still on Nameless latest version and it's still working. You must be doing something wrong.
Check the repository's instructions again, although I don't think they are difficult to follow, it's just one module to flash... Also make sure you don't have any other audio mods installed. It's okay if you have the built-in Dolby Atmos.
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
tathagatab said:
Installation fails with the following message:
----------------------------------------------------
- Copying zip to temp directory
- Installing ViPER4AndroidFX-repackagedhoch25-1b03ff9.zip
- Current boot slot: _b
- Device is system-as-root
unzip: can't open /data/user/0/vaet.gunkqwa/cache/flash/install.zip[.zip]
! Unable to extract zip file!
! Installation failed
----------------------------------------------------
Anyone tell me what's going on?
Click to expand...
Click to collapse
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
David_#27 said:
Do you have SELinux enforcing?
Do you have the latest magisk installed?
Did you flash it through magisk manager?
If the answer is yes, then try again after a reboot,
Else if the error insists, then idk, try reading the repository's instructions carefully.
It also might be that your ROM or ro your Android version is incompatible.
I hope this helps!
Click to expand...
Click to collapse
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
tathagatab said:
Yes, turned out that setting selinux to 0 solved it. Thanks for the suggestion. I didn't try it before because the repo instructions said it didn't matter.
Running stock OOS 13 with Magisk 25.2. Let's see if V4A works after the reboot.
[Edit after reboot]
No go, it's the same old "Do you wish to install the driver now" loop
Click to expand...
Click to collapse
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
David_#27 said:
Good to know that it works with SELinux enforcing.
As for OOS, I don't see it working as one user above said it doesn't.
Click to expand...
Click to collapse
As I learned, it doesn't work on OOS 13, irrespective of selinux setting. Or at least I couldn't make it work.
For me it works perfectly, using the Pixel Ex rom. Thank you very much!