Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Use magisk for v4A
"I've updated V4A to the 2.7.2.1 version through magisk"
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Juwapa said:
Does anyone know how to get Viper4Android working on 10.3.7?
I updated from 10.3.5 and I remember I had problems installing it on there too and I had to force stop the app before it would work each time. I've updated V4A to the 2.7.2.1 version through magisk and it just says Status: Abnormal, am I supposed to use a different one or?
If anyone knows, thanks
Click to expand...
Click to collapse
Julortiz said:
Has anyone managed to make it work? I'm installing it for the first time on 10.3.7 using magisk and I'm also getting the Status: Abnormal message.
Click to expand...
Click to collapse
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Mr.FREE_Bird said:
Hello guys,
So what I think that might prevent V4A to be working is having the latest version of Magisk installed. I had the same issue as you guys till I reverted back to Magisk v21.0 from v21.1.
Click to expand...
Click to collapse
Thanks for the shout, Mr. Freebird. So yeah I guess it is a problem with new versions of Magisk. I tried on the newest update as well, 21.2, and still couldn't get it to work.
For Julortiz and anyone needing help getting it to work again, the exact steps I did were
- Downgrade Magisk to 21.0
- Download V4A 2.7.2.1 from Magisk and open the app but do not install driver yet
- Go back to Magisk and install Audio Modification Library but do not let Magisk reboot
- Go back to V4A and let it install the driver and reboot
- After reboot, open V4A, go to settings and check Legacy Mode
- Enjoy
Also this is probably really obvious, but make sure you screenshot or take note of all other modules you have installed because downgrading will delete all modules. Again this is probably obvious, just don't be dumb like me and lose all your other modules lol
Related
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
I believe It's because it requires new magisk template. Give developers some time to update.
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
MarcTremonti said:
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
Click to expand...
Click to collapse
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
theduke7 said:
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
Click to expand...
Click to collapse
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
MarcTremonti said:
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
Click to expand...
Click to collapse
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
theduke7 said:
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
Click to expand...
Click to collapse
Yea bluspark is enforcing. I guess they are on gitlab from freedomOS.(check FOS thread for gitlab link)
But i guess easiest way would be just to flash freedomOS. Its nothing else anyway, than debloated stock ROM with a few tweaks. Everything selectable in aroma to your needs.
Try this...
kokesh said:
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
Click to expand...
Click to collapse
You can try this:
Update to the latest Magisk version and get everything set. for example, Snapchat and other apps that you might need to pass safety.
After that, you can downgrade to the V.12.0. And V4A it should work fine.
The only bad thing here is that you can't use Android pay or pass safetynet.
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
I use the one from ahrion, too. Works fine.
I am 6
Sent from my ONEPLUS A3000 using Tapatalk
siwan05 said:
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
I've tried both. It installs, but once I launch Viper, it asks either for driver install, or shows the driver state as abnormal. Never has any effect on the audio.
Hi guys! I am having some issues when trying to install magisk. I am currently running the latest twrp-3.2.2-0-enchilada. When trying to install magisk I'm currently having a constant error. Attached are the recovery log and a screenshot.
Magisk Error 1 fix
Hi, it looks as though you are trying to install an unsupported version of magisk you need to use the 16.4 installer not the 16.0 installer this will most likely fix your issue, I hope this helped. PS it is a beta version of magisk not the latest stable build.
16 is the stable build and SHOULD work!
Did for me.
It looks like the problem was a bad install of magisk. I went to the forums of magisk and found an uninstaller. I flashes it and then flashes the stable version. It looks like it worked. I have root back.
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
abati said:
I used for a while HAVOC-OS, I completely cleaned my device then flashed Stock OXygen OS 5.1.11, so no TWRP and magisk on device but bootloader is still unlocked.
Next step, I temporrarely booted into TWRP 3.2.1.0-Enchilada.img, then installed TWRP 3.2.1.-enchilada.zip and also Magisk 16.7.zip. Phone booted fine, but I got a notification saying ( There is an internal problem with your device. Contact manufacturer for details). But the phone works fine, and the storage data is correct, but this notification appears after each reboot.
What did I do wrong ? and what should I do to make this notification go away, please let me know.
Click to expand...
Click to collapse
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
tabletalker7 said:
Use Magisk uninstaller and then install Magisk 16.4. Let Magisk update from there.
Click to expand...
Click to collapse
Amazing, it worked ! thnx bro
abati said:
Amazing, it worked ! thnx bro
Click to expand...
Click to collapse
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
tabletalker7 said:
Now keep a copy of Magisk 16.4 on hand. It has always worked on OP6 and many other versions of Magisk cause weird problems. Just let the Magisk manager update things from here.
Click to expand...
Click to collapse
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Barsky said:
17.1 seems fine. I haven't had any problems with it. 16.7 was the culprit.
Click to expand...
Click to collapse
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
tabletalker7 said:
Did you install 17.1 or did you let 16.4 update to 17.1? On the Oreo builds 16.4 was the only one guaranteed to work right, but I was on the Pie betas when I got my hands on 17.1
Click to expand...
Click to collapse
This was a clean install of open beta straight to 17.1.
Barsky said:
This was a clean install of open beta straight to 17.1.
Click to expand...
Click to collapse
Yeah the OP installed 5.1.11. He is still on Oreo. He needs 16.4
hi. i have the same pop up msg after a clean install of 17.1 from here - https://forum.xda-developers.com/gr...om-lineageos-17-0-galaxy-grand-prime-t4034919. magisk was not preinstalled on this rom.
my phone specs - samsung galaxy grand prime
sm-g530h - A.P - XXS2BRLI
CP - XXU2BPB2
MSM - 8916
i tried removing assert line from udater script and reflashed ( clean install again). but the pop p appears still. any ideas how to get rid of it? thank you in advance.
Soft reboot after installing magisk modules. Phone is OOS latest stable & encrypted
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
bramhc said:
Guys, I will never post a new thread to xda if I ain't doing research for at least 1 day and found a solution. But here I am, so please read this.
Just bought OP6 yesterday, updating to latest stable Pie OOS 9.0, unlock the bootloader, install blu_spark twrp, magisk 17.1 (but haven't install the modules at this point), then reboot just fine like my other magisk rooted phone. HAVEN'T DECRYPT my OP6 until this post.
Now this where it began. I install BUNCH OF MODULES, KEEP REBOOT TO TWRP and ASK FOR MY PASSWORD TO DECRYPT which I did with the pattern I set, and IT DECRYPT just fine. But when I try to REBOOT TO SYSTEM, IT KEEPS REBOOTING TO TWRP AGAIN . The way I fix this is to uninstall then REINSTALL MAGISK 17.1. BOOT JUST FINE, just minus that modules
I try to INSTALL just ONE MODULE, same things happen. The way I fix it is same as before.
Anyone has this same problem? Should I decrypt my phone with this tutorial https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775 in order to have Magisk modules work?
Click to expand...
Click to collapse
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
yldlj said:
Maybe it's the modules your installing. ALOT of people have modules installed on this phone without this issue. Don't Decrypt data because it's not necessary.
Click to expand...
Click to collapse
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
bramhc said:
Okay man. I just figured out some modules just don't work. Cause I can install Camera2Api and some kernel modules with Magisk.
Modules that always crash to install are James DSP, Audio Modification Library, and Viper4Android from official Magisk repo
Click to expand...
Click to collapse
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
yldlj said:
I'm using VIPER4AndroidFX 1.7.5 materialized just fine. I have magisk 17.2
Click to expand...
Click to collapse
Okay. Will try now. Thanks
EDIT: Confirmed. Viper4android works. Maybe it's James DSP that hasn't been updated to work with Pie. Cheers.
So I just updated my pixel to Android 10. And besides the issue with getting TWRP to work, I've been trying, and failing, to get Magisk installed.
I havn't tried the newer Magisk beta yet. Does anyone know if this would work instead?
Thanks
it works with me with the latest TWRP and Magisk
henk-jan said:
it works with me with the latest TWRP and Magisk
Click to expand...
Click to collapse
Okay, so with TWRP 3.3.0 with the no-pin workaround, I wasn't able to install magisk 19.3. However, I was able to get the Beta 19.4 to work.