Related
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
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
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
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.
i've been trying for 2 whole days now to install viper4android on my oneplus 9 pro, i just can't get it to install. I'm basically stuck in an install loop and i've tried almost everything (permissive, AML, clean install, v4a repackaged, android 12 fix) but none of them work.
I wonder if anyone got viper working on their device running a custom android 12 rom
Take a look:
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
Hammerhand.17 said:
Take a look:
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
tried that too and just now tried it on just stock lineage os on A11 but still no luck nstalling v4a
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Hammerhand.17 said:
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Click to expand...
Click to collapse
i did follow every step with the reboots after each module but i'm still stuck in an install loop so i cant even get to the settings unfortunately... i've never had so much trouble with a device
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
Awesome, i'll try as soon as a custom rom is up and running
Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
So install magisk, reboot, AML, reboot, JamesDSP, reboot, V4A, install drivers and let it reboot? kernel can stay in enforcing?
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Hammerhand.17 said:
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Click to expand...
Click to collapse
Got it working finally!! Could you supply me with the modification i need to make in the post fs file? So i follow you exactly? Also can i remive jamesdsp now or does it need to stay installed?
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Hammerhand.17 said:
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Click to expand...
Click to collapse
But can i remive jamesdsp from magisk or does it need to be installed in order to keep viper working? Like the moment you remove it viper just stops working?
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Hammerhand.17 said:
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Click to expand...
Click to collapse
If you uninstall it viper is once again stuck in an install loop so you do need jamesdsp to stay installed
Ok. Good to know. Will left it installed, then.