I recently installed CM12.1 after rooting my canvas a1. But when i am opening viper4Android after installing it from play store, it asks for driver installation and completes to ask for reboot. And after reboot this process is happening same continuosly. I have already installed BUSYBOX.
Please help.
Download selinux mode changer (google it) and change selinux to permissive
That will solve the problem
hp5942 said:
Download selinux mode changer (google it) and change selinux to permissive
That will solve the problem
Click to expand...
Click to collapse
i tried that already and it hadn't worked. after that my audioFX was closing forcely repeatedly.. i had to flash cm12.1 rom again.
madhurajkumar said:
i tried that already and it hadn't worked. after that my audioFX was closing forcely repeatedly.. i had to flash cm12.1 rom again.
Click to expand...
Click to collapse
V4A was working fine on my CM12.1. Try downloading from official website instead of Playstore
http://vipersaudio.com/blog/?page_id=48
Dont forget to press Thanks if that helped
hp5942 said:
V4A was working fine on my CM12.1. Try downloading from official website instead of Playstore
Dont forget to press Thanks if that helped
Click to expand...
Click to collapse
Tried again but it still asks to install driver after many reboots(reboots because it says that driver has installed.)
madhurajkumar said:
Tried again but it still asks to install driver after many reboots(reboots because it says that driver has installed.)
Click to expand...
Click to collapse
Try flashing this zip
http://forum.xda-developers.com/attachment.php?attachmentid=3431648&d=1438967541
Fixed
That worked really! Thanku very much
Related
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
Install Twrp or other custom recovery, dissable update cm recovery first in dev option, then install supersu.
Hello thanks a lot for your reply but twrp custom recovery requires root access
Diaa toulba said:
Hello thanks a lot for your reply but twrp custom recovery requires root access
Click to expand...
Click to collapse
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
NeoLogY said:
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
Click to expand...
Click to collapse
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Diaa toulba said:
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Click to expand...
Click to collapse
check it under Grand Android Development thread, there are twrp and cwm in zip file, can be flash through recovery. Same thread with cm12.1 that you flashed.
Flash superuser zip.
Your Rom is Pre-Rooted But you need to flash latest Superuser.zip to gain Root accesses .
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Diaa toulba said:
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Click to expand...
Click to collapse
Try type this in dialer *#1234#* or *#*#1234#*#*. If any of 5hose doesn't work, visit supersu thread.
OK I tried these lines but nothing happened can you give me link to supersu thread?
cm12 has root disabled by default. Activate it from developer options.
Or you can flash supersu
Diaa toulba said:
OK I tried these lines but nothing happened can you give me link to supersu thread?
Click to expand...
Click to collapse
After you flash supersu, did any app need root worked? Which version supersu did you flashed?
Used the non systemless one( 2.56 and below).
http://forum.xda-developers.com/showthread.php?t=2868133
Also might wanna try twrp recovery.
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Diaa toulba said:
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Click to expand...
Click to collapse
Good to know. New thing I've learned from your issue. Thanks for that.
I got the same problem as above I just flash su2.76 but it didn't worked out the cm update rec. Is disable ... It give installation completed but doesn't get rooted..
Hello guys. Anyone succeeded to install Viper4android after the update to oos 3.1.3? I have root and twrp, I tried to install drivers through the app and flash a general zip for marshmallow but I did not succeed. Any idea?
Dis you see that post and links inside?
http://forum.xda-developers.com/oneplus-x/help/dirac-hd-audio-sound-oxygen-os-3-x-x-t3472002
Download the latest APK, copy it to /system/priv-app. Change Permissions to rw- r-- r-- . Install APK you just changed permissions on. Open app, install drivers (you must also have BusyBox installed if it's failing to install the driver), change SElinux to permissive (search XDA here for the app that does it automatically), turn off AudioFX and reboot. That's how it goes on Marshmallow and even then Viper may sometimes get closed in the background.
im on OOS 3.1.3 & this works great for me, no hassle just flash via twrp & your done.
http://forum.xda-developers.com/attachment.php?attachmentid=3683972&d=1458053955
Hi,
How did you get TWRP on 3.1.3 ? I tried with Rashr, but phone wont boot into recovery.
I havent unlocked BootLoader.
ajeesh.m said:
Hi,
How did you get TWRP on 3.1.3 ? I tried with Rashr, but phone wont boot into recovery.
I havent unlocked BootLoader.
Click to expand...
Click to collapse
You answered your own question. BootLoader needs to be unlocked.
coldfear00 said:
im on OOS 3.1.3 & this works great for me, no hassle just flash via twrp & your done.
http://forum.xda-developers.com/attachment.php?attachmentid=3683972&d=1458053955
Click to expand...
Click to collapse
hi sir this is safe tto use ?
Kharizmisg said:
hi sir this is safe tto use ?
Click to expand...
Click to collapse
Of course it's safe but use at own risk. Just preform a back up and your good to go.
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
Yes, it works for me and I installed couple of modules as well...
Great thanks will try again.
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
marvi0 said:
Hello I have installed magisk and tried to install some module's but they're not showing up. Is magisk working fine on Android p beta 3?, Especially in terms of installing modules?
Click to expand...
Click to collapse
marvi0 said:
Great thanks will try again.
Click to expand...
Click to collapse
gigatex said:
Wow I thought I was the only one. Modules not showing up here either and I've tried reinstalling in a bunch of different ways.
Click to expand...
Click to collapse
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
For me I noticed I have to reboot when I install each and every module. On my oneplus-5t I could install a bunch and then reboot once but on the pixel presumably due to the new firmware, you have to reboot after each module is installed and this definitely helped me.
Badger50 said:
There's a list of modules out there that do/don't work on the developer previews. If I can find it again, I'll post a link :good:
Click to expand...
Click to collapse
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
gigatex said:
I don't think its a module specific compatibility issue. Every single module I try to install seems to install fine but just doesn't show up in the list of modules. I've tried a lot of different ones.
Click to expand...
Click to collapse
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Badger50 said:
Interesting. That's kinda weird because I've seen many users running them on the DP's. Does clearing magisk manager app cache/data help at all? And I'm sure you've granted storage permissions as well.
Click to expand...
Click to collapse
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
gigatex said:
Yep, tried that and also installing through manually patching boot image, flashing through TWRP and installing through direct installation through magisk manager. Sometimes the installation fails and on reboot it'll say it's installed but safetynet will fail. Even when it installs fine modules never work though. Module downloading is all fine, during installation it goes ahead just fine as well but the modules just don't show up in the list after installation/reboot.
Click to expand...
Click to collapse
Don't know what to tell you my friend. Grab some install logs and head over to the magisk forums for some additional help is all I can suggest. I wish you luck :good:
I'm trying to figure out where i went wrong, because the last time i tried ROOTing PDP3, i couldnt boot and i am yet to see and PDP3 Patched_Boot.img or TWRP Recovery...
I did the following:
-Fastboot Flash-ALL PDP3
-Boot and set-up device PIN
-Boot into Fastboot
-Fastboot boot TWRP3212.img
-Use TWRP Installer to install Custom Recovery on device
-Reboot Recovery
-Flash Magisk v16.4
-REBOOT SYSTEM
-I think i ended up Looping @ G
Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T
HACK3DANDR0ID said:
Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T
Click to expand...
Click to collapse
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
The compatibility mode switch has been added back. This seems to be mandatory for car mode and some android q builds.
Click to expand...
Click to collapse
Worth a try
TENN3R said:
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
Worth a try
Click to expand...
Click to collapse
Yea thanks for trying but no go. The apk did install the Magisk Module, Drivers took 2-3 times but finally took. Driver Status is all NOs and Unsupported Sometime soon i'm sure...
Has anyone gotten viper4android to work on 9pro global yet? I've tried several versions with no luck.
Yes, you just need to install the "Ainur Narsil" and "Audio Mod Library" modules in magisk first. Reboot, then install viper. Good luck!
hllywd said:
Has anyone gotten viper4android to work on 9pro global yet? I've tried several versions with no luck.
Click to expand...
Click to collapse
There is a thread in here in reference to this very topic. You have to install more than just Viper to get the drivers to install. The thread I referred to says to install JamesDSP, reboot, install the DeWitt version on the Viper app (2.7.2.1 I think) it'll prompt you to install the drivers, reboot and done. I had mixed results with this method, sometimes the processing would just stop, start, stop....
I install AML v4.0 first, install Ainur Sauron, reboot, install Viper apk, the drivers, reboot, Dolby Digital Plus reboot and done. You can remove the Ainur Sauron module after all that if your so inclined, the Dolby Digital Plus isn't necessary either but it all works flawlessly.
Install in order
Viper4androidFX via Magisk
Reboot
Audio Modification Library via magisk
Reboot
Push the file (extract from the zip) to data/adb/modules/ViPER4Android/ that i have uploaded and set permission 644
(it should now be data/adb/modules/ViPER4Android/post-fs-data.sh)
Reboot
Open viper, set to legacy mode, then check if status is now normal
Amazingly this has been working on all my phones with A11
This is the process that worked for me:
Uninstall any previous versions of Viper and other audio mods
Install SELinuxModeChanger or use another method to change your SELinux to permissive
Install Audio Modification Library from Magisk > Reboot
Install Audio Compatibility Patch from Magisk > Reboot
Install Viper4Android 2.7.2.1 from Magisk > DONT REBOOT
Open the newly installed Viper app and download the drivers > Reboot
Open Viper and hit the Settings in the top right
Turn on Legacy Mode
Good Luck
stryver said:
Yes, you just need to install the "Ainur Narsil" and "Audio Mod Library" modules in magisk first. Reboot, then install viper. Good luck!
Click to expand...
Click to collapse
This worked for me! I had to disable AML, reboot, re-enable, reboot as additional steps but got it working at the end of the day. Thank you a ton for this, I've been trying to get V4A to work ever since I got this phone. JamesDSP works and has been fine but I much prefer the UI of V4A.
Seems like the EQ isn't doing anything but the master limiter seems to increase the overall volume so that's a good sign.
Thanks again!
How about full dolby atmos (not talking about dolby digital Plus). Has somebody managed to get it work finally ?
Is it possible to install V4A with SELinux enforcing?
ahh123 said:
Is it possible to install V4A with SELinux enforcing?
Click to expand...
Click to collapse
Pretty sure you need it set to permissive to install but then you can reset it back to enforcing after install is complete. That's what I did anyway
ahh123 said:
Is it possible to install V4A with SELinux enforcing?
Click to expand...
Click to collapse
Yep. It certainly is. A lot of what people are recommending to do are extraneous and unnecessary.
stryver said:
Yes, you just need to install the "Ainur Narsil" and "Audio Mod Library" modules in magisk first. Reboot, then install viper. Good luck!
Click to expand...
Click to collapse
This one worked for me thanks
HessNL said:
This one worked for me thanks
Click to expand...
Click to collapse
Would you be so kind and post a link what version on v4a did you install?
One more question z before I screw up something
To install v4a:
1. Install Ainur Narsil in magisk,
2. reboot.
3. Install Audio Mod Library
3. Reboot
4. Install v4a
is it correct?
bamemanxxa3416 said:
This is the process that worked for me:
Uninstall any previous versions of Viper and other audio mods
Install SELinuxModeChanger or use another method to change your SELinux to permissive
Install Audio Modification Library from Magisk > Reboot
Install Audio Compatibility Patch from Magisk > Reboot
Install Viper4Android 2.7.2.1 from Magisk > DONT REBOOT
Open the newly installed Viper app and download the drivers > Reboot
Open Viper and hit the Settings in the top right
Turn on Legacy Mode
Good Luck
Click to expand...
Click to collapse
How I did it but still needed to modify the data/adb/modules/ViPER4Android/post-fs-data.sh upon subsequent tries after removing magisk and reinstalling.
stryver said:
Yes, you just need to install the "Ainur Narsil" and "Audio Mod Library" modules in magisk first. Reboot, then install viper. Good luck!
Click to expand...
Click to collapse
Thx, working perfect thanks to your info
Flying Fox said:
Thx, working perfect thanks to your info
Click to expand...
Click to collapse
Nada... Can't make it to work.
Installed everything in your post. Need help guys.
netgar said:
Nada... Can't make it to work.
Installed everything in your post. Need help guys.
Click to expand...
Click to collapse
Switch to legacy mode in settings
Flying Fox said:
Switch to legacy mode in settings
Click to expand...
Click to collapse
Ok, made it work.
Thank you
Now I have another problem.
For some reason v4a doesn't see my presets in viper4android.
Any suggestions?
netgar said:
Ok, made it work.
Thank you
Now I have another problem.
For some reason v4a doesn't see my presets in viper4android.
Any suggestions?
Click to expand...
Click to collapse
Anyone was able to run presets ?
For some reason my v4a can not see
presets
I copied presets to android/data folder and nothing. I noticed that v4a is not detecting my presets folders. Tried everything.
netgar said:
Anyone was able to run presets ?
For some reason my v4a can not see
presets
I copied presets to android/data folder and nothing. I noticed that v4a is not detecting my presets folders. Tried everything.
Click to expand...
Click to collapse
I have the same issue. Looks like viper has no permission to read data in the folder.
DeanR97 said:
I have the same issue. Looks like viper has no permission to read data in the folder.
Click to expand...
Click to collapse
Yeap.... I have the same problem. V4a just doesn't see presets folders at all.
Hopefully someone smart will figure it out what is wrong.