How to Install ViPER4Android on Android 11/Android 10 Q (Alternate Method)

How to Install ViPER4Android on Android 10 Q

Can’t install ViPER4Android on your device running Android 11/Android 10? Don’t worry, it’s a known issue. In this guide, we will show you how to install ViPER4Android on Android 11 and Android 10 Q using an alternative approach. The method used here is fully working and has been personally tested by us on two different OEM devices including the Pixel 3 XL on Android 10.

ViPER4Android (Abbreviated as “V4A“) is one of the best Audio enhancing mods available for Android devices. And we already have a detailed tutorial on how to install it on any Android version, from 6.0 Marshmallow up to Android 11.

However, we have received reports that the original method sometimes fails to work on certain OEM devices. The problem? Basically the V4A drivers will fail to configure and prompt you to re-install them, again and again. This could probably be caused by the new changes implemented by device manufacturers in Android 11 and Android 10.

So, how can you install ViPER4Android on Android 11 or Android 10? Well, to be honest, the process is not the simplest one out there. It’s pretty much a hit and miss process, but it has a very high success rate as per the reports we have received. It has been tested and confirmed to be working on Pixel 3/2 XL, OnePlus 6/6T (Thanks priba77 for confirming!), OnePlus 7/7 Pro, Xiaomi Mi 9T Pro (Redmi K20 Pro), Samsung Galaxy Note 10+ 5G, along with several other devices running Android 10 (Q).

First off, we would like to thank XDA member 1dopewrx05, who shared this method on the Pixel 2 XL XDA thread.

Table of Contents

Before You Begin

Before you head over to the instructions, make sure to fulfill all the requirements as stated below.

  • Your Android 10 device must be rooted with Magisk. If it’s not rooted, then you can follow the instructions here on how to install Magisk or search our site’s database for your device-specific rooting guide.
  • Ensure that you uninstall any audio modification library and any previous version of ViPER4Android that you might have installed earlier. Once uninstalled, reboot your phone and then only proceed ahead.

Instructions to Install ViPER4Android on Android 11 and Android 10

  1. Download the latest ViPER4Android v2.7.1.0 APK from here.
  2. Install the downloaded APK on your Android 11/Android 10 device using a file manager app.
    Install ViPER4Android v2.7.1.0 APK on Android 10 Device - Do Not Install Drivers Yet
  3. Launch the ‘ViPER4Android’ app but do not install the drivers right now.
  4. Open ‘Magisk Manager’ and go to the ‘Downloads’ section of the app.
  5. Search and find the “Audio Modification Library” module and press the download icon next to it.
    Go to Magisk Manager and Install "Audio Modification Library" Module
  6. Tap on the ‘INSTALL’ button to install the module on your device.
    Install Audio Modification Library Module but Do Not Reboot Phone
  7. Magisk module installer will prompt you to reboot but do not reboot your phone yet.
  8. Now go back to the ViPER4Android app, tap on “OK” to install the required V4A drivers.
    Install ViPER4Android Drivers and Grant Superuser Permissions when prompted
  9. Grant the Superuser permissions to the app when prompted.
  10. After the drivers are installed, the device will automatically reboot.
  11. Once the device reboots, go to ‘Magisk Manager’ → ‘Modules’ and uncheck the ‘Audio Modification Library’ to disable it.
    Go to Magisk Manager and Disable Audio Modification Library Module
  12. Now head back to ViPER4Android, repeat the driver installation process, and let the device reboot.
  13. Once the device boots, launch the ViPER4Android app. Now, if the drivers are installed properly, you’re done! If not, only then follow the steps further.
  14. Go to ‘Magisk Manager’ → ‘Modules’ and re-enable the ‘Audio Modification Library’ module.
    Re-enable Audio Modification Library Module and Install ViPER4Android on Android 10
  15. Open ViPER4Android, install the drivers when prompted, and let the device reboot.

Note: For some users, rebooting the phone after disabling the AML module in step #11 can help in the proper installation of V4A drivers (Step #12). Thanks to our fellow reader skythian for the tip!

Important Note: If your device ends up in a bootloop due to the incompatibility of drivers, you can simply follow this guide and use TWRP to remove the ViPER4Android module. This should certainly fix the bootloop issue. And so, you wouldn’t have to go through all the trouble of re-installing the ROM and re-rooting the device.

This time, the drivers should be properly installed and ViPER4Android should be running on your Android 11/Android 10 device. You can now go ahead, enhance your phone’s audio using the available controls, and unleash the audiophile in you.

ViPER4Android Installed on Android 10 Q

The method might seem a bit lengthy at first but isn’t complicated at all. It seems like the installation of ViPER4Android and Audio Modification Library should be done in a specific order in order to make it work.

Alternative Method

If your device entered a bootloop following the above method, then we do have an alternative method to install ViPER4Android on Android 11/Android 10. This substitute method has been confirmed to work on Samsung Galaxy devices running Android 10 (One UI 2.0) and may work on other OEM devices as well, especially with custom ROMs installed.

  1. Download the required files on your device:
    1. ViPER4Android v2.7.1.0 APK: XDA Labs
    2. Zackptg5’s Rootless Driver Installer:
  2. Go to the app drawer and launch the Magisk Manager application.
  3. Press the menu icon and select ‘Downloads’.
  4. Search the module repository for the ‘Audio Modification Library’ module and install it. Do not reboot yet!
  5. Now install the V4A APK file on your device using a file manager.
  6. Once the application is installed, reboot your device into TWRP recovery mode.
  7. Tap on the ‘Install’ button in TWRP and select the Rootless Driver Installer zip file (e.g.
  8. Swipe the button on the bottom of the screen to flash the file.

When the flashing process finishes, press the ‘Reboot System’ to reboot your device into the OS (system). You should now have V4A installed on your Android 11/Android 10 device.

Once the original developers of the mod pittvandewitt and MrWhite214 (Team_DeWitt) update it to support Android 10, we are certain that the installation will again be much easier and direct.

So, you have just been able to install ViPER4Android on Android 11 and Android 10 Q. If you have any questions regarding the process, make sure to ask us by commenting below. Make sure to include your device name (with the model number, if applicable) and the ROM you’re using. We will try to the best of our knowledge to help you. Also, don’t forget to let us know which ones of the above method worked for your particular device and ROM.

A huge thanks to all the readers who confirmed that this method works, and also to those who stuck around to help others!


  1. Hey my Samsung galaxy m21 is rooted but is on stock recovery. Is there a way to install this?

    1. Have you tried installing the ViPER4Android module from Magisk Manager and see if it works out-of-the-box?

    2. Have you tried performing the primary instructions in this guide that involve using the Android Modification Library module?

    3. Okay, I just tried this on my S10e and Galaxy Tab A7 running One UI 2.5 and it worked using the trick above with AML. I am not sure if I have any further guidance for you.

      However, you could try removing everything AML, V4A app, and V4A module and then attempt the steps again.

      One more thing, do you have any other modules installed on your phone apart from V4A and AML?

    1. Yes. Installing ViPER4Android through any method requires Root permissions.

    1. I think there are two ways to do this:
      1) Download v2.7.2.1 APK and install it. I might prompt you to re-install the drivers.
      2) Go to Magisk Manager > Modules. When the drivers are installed, they also install the corresponding Magisk module. Check if that module needs updating.

  2. Is there a way to uninstall the rootless drivers? I want to retry installing it with root but the app always recognize the rootless drivers first and doesn’t request root permissions.

    1. I suppose the Rootless Driver by Zackptg5 is a unity installer. In simpler words, reflashing the ZIP will remove the drivers.

      Note that I am not 100% sure about this. But this how it used to work before Team_DeWitt came out with the new V4A version.

  3. Do I need to uncheck AML module in magisk manager once I have flashed rootless driver in the alternative method? Or let it remain enabled? It isnt explained in the alternative method

    1. Sahej, you’ll need to keep it installed. At least that’s what I had to do to keep it working on my Galaxy S10e running Android 10.

  4. Hey I’m on a OnePlus 7 pro rooted with magisk the rootless link for v4ax is broken can you resend pls? Thank you

    1. I have updated the download link. Please refresh the page and check again.

  5. Thank you, the first method just bootloop my device, the alternative method works perfectly. My device is a Xiaomi Mi Mix 2 runnig Lineage 17

  6. Hello, it worked on my mi 9t pro device with Android 10, MIUI 12. I used the first method. Thank you!

  7. I was foolish enough to install V4A directly from Magisk downloads and ended up hard bricking my Galaxy M30. After getting it working again by flashing stock firmware I followed the alternate method from here and it worked. I’m yet to test the app in itself but so far its installed with the drivers. Thank You!

    1. Good to know that the method worked out for you.

      On a side note, the kind of brick you faced is a soft-brick, which can be recovered just by flashing the stock firmware using Odin. A hard-brick is much more severe, where the device could not enter Download/Recovery modes and thus, cannot be recovered through an Odin firmware flash.

  8. first one isn’t working for me and in the second method, rootless driver download link is broken so can’t download that to try it. can you maybe reupload that if you have it. the only reason i rooted my phone was for viper and i just can’t get it working now. using realme 3 pro with android 10 on stock rom.

    1. Hi Atul, I have added the link to the latest version of the Rootless installer. Please check now.

      BTW, have you tried direct V4A installation via the APK? Without any tricks.

  9. Thanks for detailed walk-through. It seems very comprehensive. That said I’ve had no joy. Tried all you options and the links you recommended on the XDA site.

    I’m using a Samsung S6, and I’m running a Custom OS and Android 10 (Lineage). This may well be the issue. Seems there’s some noise around Samsung, Android 10 and driver installation.

    If anyone has any workaround, I’d be pleased to hear them.

    Thanks again.

    1. Hi Swanlee. Yes, you’re correct. Both Samsung and Lineage have known to cause a bit of issue with V4A drivers.

      First of all, undo everything you have done by following this tutorial. Next, download the latest V4A APK from here and install it. After installation, reboot the phone, open V4A, and perform the driver installation. After this is done, your phone will automatically reboot. See if the drivers work at all.

      This is the only thing (normal installation) I can suggest trying.

  10. If you guys are facing any abnormaln state issues..
    i just did these steps to make it work on Mi A2 with Havoc 3.5

    1. remove all.viper installations
    2. have Audio Mod Library installed in Magisk
    3. download rootless drivers installer
    4. flash it in TWRP
    5. reboot
    6. install apk from xda app
    and here we go it works

    1. Thanks a lot, Masleyko for taking the time to share your solution for others. I am sure it will be of help.

      In my personal case on the Pixel 3 XL, I do not need to install AML or do any other tricks to get V4A working now. With the new V2.7.1.6 V4A APK, it works out of the box.

    2. This works for me. Thanks lot broi. Looking for best solution in more days. This is the best solution I ever shown. Thanks lottt

  11. Hey bro i have followed the steps until 11 but how to do the step 12 , means after disabling the AML MODULE when i head back to viper its already drivers installed, and there is no option to re-install the process, so, how should i do the drivers installation process in step 12

    1. Both the method dnt work for for me,
      My device is Asus Max Pro M1
      Im in havoc 3.5 custom rom

    2. Hi Manish. If the drivers already show as installed before step #12, just reboot the phone. Then open V4A and check if the drivers are still installed. If they are, then V4A is correctly installed on your phone.

    3. Hi Manish. I was recently able to install V4A on my Pixel 3 XL without having to do this trick anymore. You could try the same.

      Just download the new update of ViPER4Android (v2.7.1.6) from here:

      Install the APK, install the drivers, and reboot the phone. That’s exactly what I did.

      Before anything, make sure to remove AML and V4A modules from Magisk Manager and also delete the existing V4A app, then reboot your phone and try the latest update. Please do let me know how it goes.

    4. Reboot your phone manually
      Then open magisk and re-enable the audio
      Then go to viper it will prompt you to install the drivers and will reboot and then you’re ready to go
      I tried it on my rooted Poco F1 and it’s working fine

    5. Hey Avinash. Thanks for helping out others here, as well as for the confirmation that it works for you. Much appreciated.

    6. Reboot your phone manually
      Then open magisk and re-enable the audio
      Then go to viper it will prompt you to install the drivers and will reboot and then you’re ready to go
      I tried it on my rooted Poco F1 and it’s working fine

      What Avinash ammisetty says works for me on my MI A2 (Pixel Experience Plus July patch) with one extra step. Basically what you have to do is –
      After following the 1-11 no. steps of the post you have to

      12. After disabling Audio Modification Library reboot your phone manually.
      13. Open Magisk and Re-enable the Audio Modification Library.
      14. Go to viper4android. It will prompt you to install the drivers. Install it. the phone will reboot automatically after installation.

      And here comes the one extra step –
      15. Open viper4android after the reboot. It will again ask you to install the drivers. Do as it says. Phone will reboot automatically.

      That’s it. Viper4Android is now properly installer on your MI A2.

      Don’t forget to enable ‘Master Power’ from inside viper 😀

    7. Thanks, Oxnyz for sharing your observations regarding the Mi A2. I am sure Mi A2 users would benefit from this.

    1. Hi Paul. Thanks a lot for the confirmation. I recently discovered that on my Pixel 3 XL running Android 10, I no more have to follow this method.

      I just used the old method and it worked flawlessly. While it may not work for every device (yet), but it’s worth a try.

  12. Hi I installed Viper4Android with this method on the pixel 3a, and it works for some time, but at some point, I could not exactly identify the cause, the driver status becomes abnormal and it does no longer work. after a restart of the phone it works again but its really annoying. any experience with that?

    1. Hi Mike. That’s odd. Are you using any custom ROM on your Pixel 3a?

      I have had V4A installed on my phone for months now and have occasionally faced the issue where the driver status turns abnormal and V4A stops working. On my end, instead of restarting the phone, I simply discard and force-close the V4A application. After doing that, I re-run the app and also restart the music app (YouTube Music, Spotify, etc) I am using.

      However, there’s something else I have observed lately. Since Team DeWitt updated ViPER4Android recently, it now works out-of-the-box on my Pixel 3 XL running Android 10. So, I do not need to perform this method anymore.

      Could you try the same? First off, uninstall the currently ViPER4Android and Audio Modification Library modules from Magisk Manager. Then reboot your phone and make sure that the existing V4A app has also been removed. Once this is done, simply download the V4A v2.7.1.6 from here, install the app and run it. When the app prompts to install the drivers, install them and let the phone reboot. See if it works after this and is stable enough.

  13. Hi, thanks for these advises, i got v4a finally work this way on oneplus 7 pro android 10 havoc os 3.4. after many hours fighting,
    First from developer options set bluetooth AVRCP- version from 1.4(default) to 1.6 then i followed your guide all the way but noup. Maybe i miss some part but anyway i uninstall usual way. Then go to magisk, let audiolibrary be installed, download from magisk latest v4a, install, after install phone will reboot. I was 99.9% sure that is go bootloop but wtf, system start, everything works, v4a works and its really awesome app for that(never try before) but happy now, cause that was main reason me to root. And sorry bad english. I’am from finland😁

  14. bonsoir j’ai essayer les deux méthode cela ne fonctionne pas malheureusement (oneplus3, lineage 17. , root magisk) pour la deuxième méthode boucle donc désinstaller v4 via twrp et reflasher la rom (sans perte).
    Dans v4 j’ai driver status neon enabled:yes enabled: yes status: normal audio format :supported processing:no sampling rate: 48000
    Quelqu’un aurait t-il une autre solution ?

    1. Hi Malaury. So with none of the method, you were able to install to V4A?

      With both the methods it caused bootloop?

  15. hola..hice todo lo del primer paso, pero cuando abro viper me dice que debo instalar los controladores y se reinicia y asi continuamente, desabilito audio modification library, abro viper y ahi si deja descargar los controladores, pero al habilitar nuevamente audio modification library, me pasa que viper me pide otra vez los controladores y se queda en ese proceso una y otra vez.
    tengo un redmi note 8 pro andoid 10. saludos

    1. Hi Martinez. Is your Note 8 Pro rooted? I believe you’ll need to follow a different method to get it working on your phone.

  16. How do I uninstall the Rootless Driver Installer on the second method? I went on to the second method in mu first try and the driver is abnormal and now I can`t uninstall it. V4A can`t uninstall it.

    Is there a file to flash on TWRP to uninstall it?


    1. Hi Gabriel. Unfortunately, the developer who provided this (zackptg5 @XDA), hasn’t provided an uninstaller. Although, before Team DeWitt took over, Zackptg5’s unity installer is what I used. The added advantage was that flashing the installer file twice would work as an uninstaller.

      I am not sure if the same is applicable with the rootless installer, but you might want to give that a try.

      If it doesn’t work, please let me know. Also, which phone is it and which ROM/software version is it running?

    1. Hi Rose. I haven’t got any confirmation for Galaxy smartphones. Did it result in a bootloop?

    1. Hi Florekx, thanks for confirming that! I have my Mi A3 updated to Android 10 last night, still haven’t tried this.

  17. Worked on the oneplus 6(android 10, stock OOS, magisk and twrp installed) like a charm and have been looking for driver installation issue solution for a long time, thanks a lot!!

  18. On S9+ with stock Android Q stable, After following the guide Viper4Android fully working!!

    1. Hi Bibi. Thanks a lot for confirming that! Not many people who have provided confirmation for Samsung devices. Kudos!

    2. Hi Akha. So, the method did work for you? And the driver status is showing ‘Abnormal’, right?

    3. Hi Akha, I have added an alternative method that has proved to work on Galaxy phones. Could you try that and let me know if it works?

    4. I have also tried alternative links, and the results are the same. Only on Samsung S9 + Android 10 Viper does not run.

  19. Hi. I did everything you said but when after I go in viper it says the driver is installed but nothing else is working

    My phone is redmi note 6 pro. I use a custom kernel, venom kernel.i use evolution ROM

    1. Hi Joy. Have you enabled the “Master Limiter” button in the ViPER4Android app?

    1. Hi Ayush. Thanks a lot for confirming. You’re probably the first one here to get it working on PE ROM.

      May I know if you did anything special to make it work?

  20. tried on Samsung galaxy note 8exynos rom lineage17.1. after installed driver it reboots phone. it then bootloops. cant get into twrp. have to reinstall Samsung original and reroot

    1. Hi Colin. There must a software conflict between the audio drivers/libraries installed Magisk and that which are pre-installed on Lineage.

      If you or anyone else faces a bootloop, you can simply use TWRP to manually delete the V4A module. The instructions for which can be found in this post.

      I have also added the link to it in the post above.

    2. Hello I’m on redmi 6 pro using revenge os android 10 and followed the methods above but my device booted into fastboot mode i tried deleting the module from twrp and now it boots fine but i still cannot get the viper to work for me.

    3. Hi Marshal. Have you tried following this method on a different ROM? Possibly something that’s close to stock/vanilla Android.

  21. Hi!I did all the things you said ,but i got stuck in a bootloop after installing v4a drivers every time.I doesn’t make a difference if i try to install through magisk.I’m running android 10 pixel experience on my op3t.

    1. Hi Horia. Have you tried using this method on a different ROM? There have been several reports in the comments regarding the driver failure on Pixel Experience ROM.

  22. 10. After the drivers are installed, the device will automatically reboot

    After step 10 my phone is stuck on boot loop, what to do to install it smoothly…

    Asus Zenfone Max Pro M1 (using Pixel Experience ROM-Android 10)
    (Bootloader unlocked with TWRP+Magisk)

    Before doing this, I’m happy and glad to seen your another post which is bootloop bypass tweaks. It’s saved my time and my data/settings.
    Again thanx for that, please let me know how to fix this and install the app…

    1. Hi ShafiqueAJ. I am glad you found that post. I prepared that post to link with this article but unfortunately forgot to do it.

      I have added the link for the same towards the end of the instructions. So users who may face a bootloop can easily get out of it.

      As for your V4A setup, I am quite certain that it’s the Pixel Experience ROM that could be causing a conflict. If you scroll through the comments below, you will find several others readers who have faced this, and most of them have used Pixel Experience.

    2. Hi Bishek. Could you please share the original source of the APK file you shared?

    3. it worked for me.
      generic app was constantly crashing.
      this one did the trick. Thanks man

    1. Hi Paulo. That’s great! Can you please enlist the device name and the ROM you’re using? It would help other readers get the confirmation.

  23. I have a Galaxy Note 9 running Devbase 7.0 and this process is resulting in the device booting to download mode. Luckily I have installed Magisk for recovery so I can toggle Magisk core only mode on and off in recovery. Maybe there will be a fix on this Rom. Dr ketan’s Q03 has V4A working on the same device.

    1. Hi Mqphill. Have you asked around on the ROM thread if anyone else has found a possible fix? Cause now that you mention that Dr. Ketan’s ROM has working V4A, it could surely be an issue with internal conflicts by the ROM?

  24. Worked great on my Pixel 2. Am so glad I found this site after being Viper-less for a long time. At first, I didn’t realize that the ‘Master Limiter’ is the on switch. Normally a limiter is half off a compressor. It should be renamed On/Off.

    1. Great! As for the ‘Master Limiter’ button, I too was confused the first time used the updated V4A app on Pie. It’s a bit confusing, especially for those who are new to the UI changes in the latest version.

    1. hi.
      its working for speaker and bluetooth..
      but not for headset.

      mipad 4 blissrom/Q

    1. Hi Tom, thanks for the comment and confirming. I had to moderate your comment due to the comments policy, although I know it was solely an expression for your joy.

  25. Working very well on Xiaomi Mi 9T Pro Rom Xiaomi EU Miui 11.2 Beta 9.12.26 / 27

    Thank you so much!

  26. Bro drivers installing without these steps. In order to work. Device need to set selinux permissive. You are giving this solution for this selinux problem?

    1. Hi. SELinux is quite a big deal to tackle. Yes, setting Permissive can help, but I would suggest not doing it since it’s a major security layer in Android.

  27. I successfully booted it’s installed but no audio modification takes place.
    Device pocoF1 and Rom EvoX3.5

    1. Hi Varun. Did you try enabling the Master Limiter toggle in the V4A app? Once you do that, check the driver status, it should show as “Processing”.

      You can then tweak other settings and test them by playing music on the output channel (speaker, earphones, Bluetooth, etc).

  28. Tried to install it on Poco f1, PE10, magisk 20.1. Nothing…

    Driver installation lead to bootloop every time. also tried this to install AML and AINUR SAURON 3. AML works but Sauron also causes bootloop.

    I had youtubevanced installed, but i disabled that module.

    When trying to install sauron i also had AML installed.

    Frustrated to try any other combinations.

    Can’t wait for update on the thing…

    1. Hi Taavi. I know it can be very frustrating when we especially can’t figure out exactly what is causing the issue.

      If you go through the comments, you will see that a majority of people using different devices have reported that it doesn’t work. The only thing I could find that is common between all of them is the Pixel Experience ROM.

      Could you please try it using a different ROM? Possibly a one that’s built directly from AOSP sources.

  29. Friend I managed to install viper in Havoc 3.0 Adroid 10 Redmi Note 5 pro, but with a different file without magisk because it made me conflict at the time of restarting, the file has a name: + apk file 20190502 -ViPER4Android-v2.7.1.0 look for it on youtube, it’s super simple and it worked for me

  30. those who after point 10 – the phone does not turn off (fastboot) – go to Recovery mode – File Mangaer – data – adb – modules – ViPER4AndroidFX and delete the file

    Phone – Xiaomi Redmi Note 5, Android 10 (Pixel Experience)

    1. Hi Davron. Thanks for taking the time to comment and help others. I have added a note box towards the end of the instructions, which points to a guide for uninstalling modules via TWRP.

      BTW, I believe you didn’t succeed in install V4A either, am I right? I suspect Pixel Experience. The ROM may have some audio library modifications that could be causing the conflict.

      Have you tried the method on a different Android 10 ROM? If you really want to stick to PE ROM, then I suggest you take a look at the comment posted by another reader (J Delgado). The files you will need are the rootless V4A driver installer zip and the V4A APK.

  31. Thank you for this excellent guide!! Works exactly as described on oneplus 6 oxygenOS 10.0.1, with magisk 20.1 No need to go past step 13.
    NO WAY would I have found this solution by myself.

    1. Hi Pjotrski. I am glad it worked. And thanks for confirming the device name along with the rest of the information.

  32. Doesn’t working, just stuck on bootlogo and rebooted on fastboot after 20 second.
    My phone Xiaomi Redmi Note 4X with Pixel Experience Q 10 ROM

    1. Hi Steven. I have received various reports for different devices where the method doesn’t work. And the only particular thing common in all of these is Pixel Experience.

      Have you tried using a different Android 10 ROM? I suggest something that’s built directly from AOSP.

  33. I’m using a Mi 9T Pro running MIUI Global 11.0.1. Installed V4A with this tutorial, all the options appear in the app but none of them work. In the driver status, processing is stuck at NO.

    My Magisk modules are:
    VIPER4Android FX 2.7.1
    Audio Modification Library 2.4

    1. Hi FS. The same happens with me too sometimes on my Pixel 3 XL. To fix it, I simply force-stop V4A and re-launch it.

      Before any of this, make sure that you have the “Master Limiter” enabled in V4A’s audio channel tab (Bluetooth, Headset, etc) for which you want to tweak the audio.

  34. Don’t work for me.
    I’m tryed to install V4A in my Mi 8 Lite with beta, version 9.12.6 (MIUI 11, Android 10).

    After the step 10, the device reboots in fastboot mode.

    Before, when I’ll tryed to install V4A direct from Magisk, the device is stuck on the bootlogo.

    Any suggestion?

    Thank you!

    1. Hi Alex. It could mean a lot of things. Maybe it’s the ROM or maybe another Magisk Module that could be conflicting.

      First of all, use the steps in this guide to uninstall the AML and V4A modules directly using TWRP. This shall help fix the bootloop.

    2. Hola tengo un poco f1 Android 10 y tuve el mismo problema de arranque al instalar desde magisk. ¿Lo has solucionado?

    1. Hi George. I am glad it did. Can you please share your device name and the ROM you’re using? It will help other users with the same device get confirmation.

  35. Works great on a OnePlus 7 Pro with Paranoid Android Quartz beta 3. I would just add that on Step 11, after uninstalling the Audio Mod library, you need to reboot before re-installing V4A drivers.


    1. Hi Skythian. I am glad you were able to get it up and running on your OP7 Pro. Actually, I tried the same and it failed for me both on my Pixel 3 XL and Pixel 2 XL.

      Since it’s a “trick”, I think some users might be able to get it running without a reboot, while others would need to reboot. Anyhow, I have still added a note after the instructions for others to try. May be this will help them get it working. Thanks for sharing the tip!

    1. Hi Javier. I am sorry that it doesn’t. Have you tried it on a different ROM?

  36. Didn’t work on my Moto G5+ running HavocOS 3.0 (Android 10) on the latest build, I followed the steps and after Viper does it’s first automatic reboot. My logo.bin showed up, then immediately crashed to bootloader.

    Therefore, straight up flashed Magisk Uninstaller (using Magisk 20.1), rebooted to check all was okay. Was fine, then installed Magisk Manager + Magisk + Modules, put back all my app presets and all is okay.

    Just gonna have to wait for an official release. In the meantime, non-rooted equalisers with Kernel Auditor’s volume control will have to do.

    Hope this helps if you have a similar issue. – Josh

    1. Hi Josh. I am glad you took all the time to provide a very decent explanation and an alternative to other users.

      As for you Josh, you can also uninstall the culprit modules with TWRP, without having to uninstall Magisk completely and repeat the whole installation again.

    2. You don’t need to uninstall whole of magisk,just boot to recovery>advanced>file manager>data>adb>magisk>modules & delete viper4android or any other module that might be causing issues with booting.
      Hope that helps!

    3. Hi Gulshan. Thank you so much for taking the time to comment here and assist others.

      I have prepared a post on removing Magisk modules via TWRP and have linked the same towards the end of the instructions, for users who might end up with a bootloop.

    4. Guys I’m using redmi note 7 pro with android 10 Q. If I install audio modification library then the mobile is going into boot loop. What do I do?

    5. Try without the AML module, just do it the normal way and see if it works.

  37. Hi will this method work with the OnePlus 7T Pro? I’ve tried to install it with other method on XDA forum with no success I get stuck in a bootloop. I’ve already had to unbrick my phone 6 times and go through process of rerroting and installing all my apps. Don’t want the same thing to happen with this process. Thank you

    1. Hi Martin. Yes, it should work. I don’t have the 7T Pro. But I did saw users with the same device succeed with this method.

      If you face a bootloop again for some reason, then you can try uninstalling the AML and V4A Magisk modules directly via TWRP recovery to fix it. So, you will no more need to flash the stock ROM to fix the bootloop. The instructions for uninstalling Magisk Modules via TWRP can be found here.

    1. Hi Allan. Thank you so much for the confirmation! Enjoy V4A on your K20 Pro now.

    1. Hi Tejas. I am glad it worked for you. Could you please let me know your device name/model number? This shall help other users with the same device get the confirmation.

  38. Very very thanks bro! Ur writing and screenshot make it so much easier for installing viper fx! thank you!

    1. Hi Tonmoy! Thank you for such kind words. I am glad it worked for you. Could you please state your device and the ROM you’re using? It should help provide the confirmation for other users.

    1. Hi. Thanks a lot for the confirmation! I am glad this tutorial helped you get V4A running on your Mi 9T.

  39. Not working for me
    I’m using leeco le max 2 x820 with revenge os 3.0 android 10
    Followed exactly the same steps but while rebooting my phone enters the fastboot mode and cannot reboot
    So i have to delete viper from magisk modules using twrp to get the phone reboot again..
    Any solution?

    1. Hi Saksham. This is the only confirmed method that I could find, and it works across many major OEM devices like I have mentioned.

      There could be several causes, but I suspect two:
      1) Either there’s something in the ROM that’s preventing the installation.
      2) OR, another Magisk Module is conflicting with the AML or V4A module. Which other modules do you have installed on your phone?

  40. I manage to have it working but my earpiece for calls does not have sound anymore

    1. Hi Dennis. Please go to Magisk Manager > Settings and enable “Magisk Core Only Mode”. Then reboot your phone and check if the issue has been fixed. If it’s fixed, then we can be certain that there’s a conflict between two or more modules, or an individual module (Like AML and V4A) in this case, that could be the cause.

    1. Hi TT. Thanks a lot for the confirmation! It would really be helpful for new users coming here.

    2. Hi Nick! I am glad it worked out for you. Could you please list your device name/model number as well? This shall help provide confirmation to other users who come here.

  41. Hi,

    i am using samung note 3 n9005 hlte.
    on havoc os 3.0 with built-in kernel.

    used above methods, both with and without audio modification module activated. but after install v4a drivers, phone will indefinitely reboot into odin mode… pls help

    1. Hi. It means that something with the software (Or, maybe your custom ROM) is triggering a conflict.

      So now that your device is in a bootloop, it’s quite easy to recover it by uninstalling the V4A and AML modules using TWRP. You can boot your phone into TWRP, am I right? Let me know so that I can guide you further.

    1. Hi. Glad that it worked for you. I recently updated my 6T to OOS 10 and I can confirm as well that the method works. I have added the info in the first few paragraphs of this post along with credits.

  42. Hi,

    My Mi8 enters fastboot mode after step 10 and won’t turn on.

    İnstalled Rom:Eu Beta 9.10.31

    Device : Xiaomi Mi 8

    1. Hi Emin. Have you previously had success installing V4A on your Mi 8 running Pie?

      It surely seems like the mod is conflicting with either another equalizer or the Android 10 beta is itself the cause for this isse.

    2. No…I made a clean flash of based custom rom with android 10 on my Mi 8 today and got the same fastboot problem. Only when I disable the modules I was able to boot my phone again.

    3. And yes, when I used pie (same rom) I was able to use Dolby Atmos and Viper on my phone without problem. For info, my rom is stable version…not beta.

      But thanks for your work!

    4. Hi yannahzinha. Android Pie is supported by V4A, that’s why there isn’t an issue with installing it.

      On Android 10 though, some new changes have been introduced that prevent the normal installation method. So, that’s when I found this method, tried it and wrote a guide on it. However, it hasn’t worked for everyone, especially with varying custom ROMs.

      And you’re welcome! I am glad you took the effort and tried it. I will surely be updating this guide if there’s any update from the development team, or if I find a new/much easier method.

    1. Hi. I couldn’t vouch for custom ROMs. They might have several changes to the audio library that could prevent the installation.

      Anyhow. Could you please let me know at what point does your Redmi Note 5 Pro hangs? Also, please list the current Magisk Modules installed on your phone?

    2. it was ok with PE pie and older versions. something was changed in android 10, but i can’t say is it was exactly PE change. the problem (stuck on Mi logo stage) shows after driver installation, it doesn’t depend on AML installation. you must flash magisk uninstallator to let it boot

    3. Hi Alex. Thanks for sharing your observations.

      Yes, surely there’s something changed in Android 10 that prevents the direct installation. But I am sure there’s something else in Pixel Experience ROM as well that causes the conflict between the installed modules. thus leading to a bootloop.

      This method is a hit-and-miss sort. It works great for my Pixel 2 XL/3 XL running Android 10 and OnePlus 6T running Android 10 via OxygenOS 10 update. Another user confirmed it for the OnePlus 6, and another who confirmed the same works perfectly for his Mi 9 on MIUI 11 Global version.

      As you said, it doesn’t work with PE ROM on your device. The result could be subjective, depending upon the device setup. It could be anything, from the ROM to another Magisk Module that might have caused a possible conflict. In such a case, you can either flash Magisk Uninstaller or use TWRP to uninstall the AML and V4A modules from your device.

      Do you have any other modules installed on your phone apart from AML?

      Thanks, Alex, for taking the time to comment here.

    4. Hello, I own a Oneplus 6T with OxygenOS 10.0.1, I followed your method. The apps starts and 5 second later stops automatically with the message: Viper4Android FX has stopped, App Info or Close.

      Have you got any solution ?

    5. Hi Nathan. I can confirm that it works on OP6T with OOS10, along with some other users as well in the comments.

      Could you please let me know which other Magisk Modules you have installed on your phone? Since the driver installation was successful and the app only stops to respond after it runs, I suspect there could be a conflict with another app/service.

    6. You don’t have to flash the uninstaller every time. I simply deleted the module using TWRP file manager

    7. Hi Avinash. Thanks for helping others out here. I have done an article on the same and have added the link towards the end of the steps for users that might encounter a bootloop.

Leave a Reply

Your email address will not be published. Required fields are marked *