Hey guys,
I have 2 questions about Viper4Android on Magisk and I would really appreciate it if someone could answer them.
First, how do I go about installing it? I flashed a custom ROM (SuperMan-Rom v1.1.4) to my Galaxy S7 edge yesterday, and a Magisk version of V4A was one of the options in the Aroma installer. Apparently, the only extra thing I had to do was to install the APK manually (despite V4A being present in my list of applications), which I don't the location of, and installing the driver was a big no-no, so I pressed "No" on the prompt but it kept coming back. Following these, I couldn't get any effect on my music (Spotify), so I decided to reboot my phone. Sadly, my phone was stuck on the S7 edge's splash screen, so I had to reinstall the ROM. Does anyone know why this happened? Is there a guide that shows all the steps in order to install V4A correctly? I should also mention that Magisk and PHH's SuperUser were correctly installed.
Second, is there an advantage to using the Magisk (systemless) version of V4A over the standard version? Because if there isn't, I might just install the latter to save me a headache.
Thank you.
bump
Where can I find download links for magisk v4a ?
What are the steps?
edit:
nvm it's here
http://forum.xda-developers.com/apps/magisk/collection-magisk-modules-t3445257
The update to v4a 2.5.0.5 apparently broke the driver. How can I fix this?
Edit: nvm fixed by updating the apk (link is present in magisk manager v4a module info)
Related
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.
I am on the latest MM release & kernel to hide unlocked boot loader, rooted with Magisk SU and hidden to use Android pay. I currently run Magisk module for V4A. I have been trying to get V4A to work with installed driver, but after trying several methods suggested in V4A and Magisk forums, it will only work in compatible mode with standard Google play music app. It will not work at all with Pandora or Amazon music player apps. I am not sure what compatible mode means other than it hides the driver information, so I assume it is functioning without driver (?) somehow, with lower quality results? Ultimately would like to get it to work with Pandora, my go to music source, with or without Magisk module interface. I am not sure what the Magisk module is doing if anything as the V4A works the same with the module uninstalled. Thanks if anyone has experience to share.
jrmt077 said:
I am on the latest MM release & kernel to hide unlocked boot loader, rooted with Magisk SU and hidden to use Android pay. I currently run Magisk module for V4A. I have been trying to get V4A to work with installed driver, but after trying several methods suggested in V4A and Magisk forums, it will only work in compatible mode with standard Google play music app. It will not work at all with Pandora or Amazon music player apps. I am not sure what compatible mode means other than it hides the driver information, so I assume it is functioning without driver (?) somehow, with lower quality results? Ultimately would like to get it to work with Pandora, my go to music source, with or without Magisk module interface. I am not sure what the Magisk module is doing if anything as the V4A works the same with the module uninstalled. Thanks if anyone has experience to share.
Click to expand...
Click to collapse
You have to get V4A magisk, audio modification library and universal deep buff remover (this one you might have to get from the xda thread, the one in the magisk repo seems to be broken) to get viper4android to process in all apps in normal mode.
zys52712 said:
You have to get V4A magisk, audio modification library and universal deep buff remover (this one you might have to get from the xda thread, the one in the magisk repo seems to be broken) to get viper4android to process in all apps in normal mode.
Click to expand...
Click to collapse
Thank you for responding, I did try both of these fixes by ahrion, plus he later put out his own magisk v4a module with the fixes incorporated in it, unfortunately no changes, I am wondering if it is something specific to the DT as I have never read of anyone running v4a in normal mode on a turbo.
jrmt077 said:
Thank you for responding, I did try both of these fixes by ahrion, plus he later put out his own magisk v4a module with the fixes incorporated in it, unfortunately no changes, I am wondering if it is something specific to the DT as I have never read of anyone running v4a in normal mode on a turbo.
Click to expand...
Click to collapse
I've been running that setup I described for a month now and it's survived rom updates as well, never had any trouble with it. Did you get the universal deep buff remover from the xda thread or within magisk manager?
zys52712 said:
I've been running that setup I described for a month now and it's survived rom updates as well, never had any trouble with it. Did you get the universal deep buff remover from the xda thread or within magisk manager?
Click to expand...
Click to collapse
I wasn't sure of source so just loaded deep buff remove from xda thread. Also running the audio mod v 1.4. After reboot neither Google play music or Pandora worked in compatible mode, rebooted to normal mode and no processing from either source. I removed deep buffer mod via his deep buffer restore mod, now Google play music back to running in compatible mode only. Thanks for trying to help me not sure what's different from your setup
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Giuskiller said:
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Click to expand...
Click to collapse
Is this via Magisk manager?
ashyx said:
Is this via Magisk manager?
Click to expand...
Click to collapse
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
I have the same problem. Trying to install viper4a.
I have no clue how to fix it
Giuskiller said:
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
Click to expand...
Click to collapse
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
ashyx said:
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
Click to expand...
Click to collapse
Actually i'm at university, but when i come back home i will try and let you know. What i can say for now is that every zip i've flashed so far worked just flawlessy (well, apart magisk's ones)
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
netgar said:
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
Click to expand...
Click to collapse
Well as far as i know, if you're on stock rom you won't be able to install audio mods because they're in conflict with something in the Rom. You should use a custom rom instead. However not sure 100% about this, maybe some audio mods can work, but you should ask someone else, i'm not so informed
Hi everyone,
I am pretty new to rooting, flashing, modding etc.
My problem is as follows:
I am on Pie 10.0.1.0PDIMIFJ, upgraded to it thanks to a guide in this forum.
After upgrading (bootloader has been unlocked beforehand of course) I got root through patched boot.img and Magisk Manager.
I did this in order to be able to gain some everyday treats such as Youtube background playing and especially V4A.
I could install these modules via Magisk, but they do not seem to work.
V4A is asking for driver installation everytime I reboot my phone, and I have to reboot after every driver installation.
This happens independently from the version of Viper I am trying to install.
After installing Youtube Vanced nothing changes. Playing stops when closing the app while a video is turned on.
I also tried a couple of other modules but none seems to be working.
I read somewhere that this could be connected to "SELinux permissive" something . I am sorry, I do not really know what that's about but maybe someone out there could give me a hint as to where I have to look.
I do not need a guide or anything, don't mind learning something on the way
Help would be greatly appreciated.
Thank you guys in advance
Anyone?
Same/similar issue
I am also experiencing the same issue, was able to install Viper and pixel Camera mod, then after no matter what module I install it does not show up in the app drawer atleast, I tried App systemizer , Cloudfare DNS and SF font.. nothing seems to work than the first installed two modules. Tried to install and remove them multiple times.
Cleared magisk cache
installed M<agisk from TWRP multiple times.
tried to install modules from TWRP as well.
I am so new to all these, please dont mind any mistakes.
Thanks.
The same problem I got.How to do to enable camera 2api.
So I had trouble installing Viper through Magisk on Pie on my Exynos Note 9. It always told me to reinstall the drivers, but that didn't seem to work.
But I found a solution:
On XDA-Labs is a new version of viper available (Version 2.6):
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Simply install this version (I chose the beta), give it root permissions and you are set!
I also installed audio modification lib from Magisk to be on the safe side.
Only issue I noticed is that YouTube videos seem to hang for a few seconds before they start playing (I am using YouTube vanced from Magisk). Apart from that everything seems to be working well!
Hope that helps everyone who is having trouble on Pie!
It isn't asking me for root permission?
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Rowe90 said:
Strange.
But you are rooted with Magisk and have Magisk Manager installed?
Is the app showing up in Magisk Manager under the SuperUser section?
Maybe trying to install the app again solves your issue.
Click to expand...
Click to collapse
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
aussiesausage said:
Correct, and nope it isn't showing up in the superuser section. Re-installing did nothing, it isn't working without root, atleast that's why I think it isn't working.
Click to expand...
Click to collapse
Yeah it needs root to put itself into some system files.
I just saw they released an update yesterday which is know marked as stable. (version 2.7). Maybe you have better luck with that.
It was working on 2.7 but it suddenly stopped
Now it's not enabled and not processing
Don't know how to fix
(Btw on Samsung Galaxy A8)
This was the only thing that worked. I've been trying different things and searching for hours. The stable version does not work on my exynos note 9. The beta does though!