Database Develop

Viper4Android drivers vs compatible mode

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

Advisory : Safetynet seems. to have been updated

EDIT: TOPJOHNWU IS WORKING ON A FIX RIGHT NOW, WAIT FOR MAGISK 13 RELEASE OR ENABLE CORE ONLY MODE AS A TEMP FIX.
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.

manor7777 said:
Posting this from my phone so sorry for any errors here.
Google seems to have updated safetynet within the last few hours, on 2 devices. That previously passed with magisk. There is an easy way to fix it, that I don't really want to post here as Google probably read the forums. Let's just say it's easy to fix, but you not using modules any more. Hoping for an update soon if that's possible and I can provide any logs or details to the dev if needed.
Click to expand...
Click to collapse
Yeah, it seems like Google has updated SafetyNet, now I can't pass the check
Sent from my Pixel using Tapatalk

Same here.

Using Galaxy s6, same here.

Thanks it works

Glad to know I'm not the only one. They will probably patch what I've done later on but at least I can still use my phone with root. Can back to stock as I'm on a OP3T but I don't want to lol

So i need to uninstall my youtube ad free module?

bam099 said:
Same here.
Click to expand...
Click to collapse
Yep... may not be related, but noticed random "unable to parse data" toast messages earlier today. Later caught google play downloading. Killed download, then ran safetynet check. Failed CTS profile mismatch. Again, any of those symptoms could be unrelated. Just reporting anomalies.
bummer

Nexus 6 running Pure Nexus 7.1.2 on Magisk v12.0
SafetyNet Failed: CTS profile mismatched
Yeah, looks like another swing from Google.

how can i pass safteynet i cant get to hide my root to log into snapchat

Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check

I thought i was the only one

If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.

Works but..
blk_jack said:
If you can live without modules, enable 'Magisk Core Only Mode' in Settings and you'll pass SafetyNet again.
Click to expand...
Click to collapse
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code

Btw, it seems not all modules trigger SafetyNet. My suggestion to people is to test each module one at a time and see which are affected.
To do this:
- Disable all modules
- Enable the first module
- Reboot
- Check if SafetyNet passes
- Disable the first module and enable the second
- Reboot
- Check if SafetyNet passes
- Repeat.......

angelus_kun said:
I have a problem with Mario run, safetynet pass And magisk hide is enabled but Mario run always give me the 804-5100 error code
Click to expand...
Click to collapse
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.

blk_jack said:
Maybe try clearing data in the game. You might have tripped a flag and the game is remembering that your device has failed.
Click to expand...
Click to collapse
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
andybfmv96 said:
Same here it definitely updated. Haven't done anything with my phone in a while. Suddenly failing the check
Click to expand...
Click to collapse
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module

angelus_kun said:
Nope, i tried that before And dosen't work, irñts very strange because on my moto G4 with magisk hide And safetynet pass i was able to play without issues until now, And i don't know why because i have the same modules like before, And i have the same issue on my galaxy Tab A6 t280 with the same modules, safetynet pass etc :\
---------- Post added at 03:10 AM ---------- Previous post was at 02:42 AM ----------
Mario run work again i solved the issue deleting all modules enable magisk core And systemless host (for adaway at least) magisk hide with Mario run selected, clear Mario run data And reboot oh Well :/ bye bye to ad away OGyoutube module
Click to expand...
Click to collapse
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.

MiuKing said:
Did you even read OP's post? Google updated a security patch and now most of us can't pass SafetyNet.
Click to expand...
Click to collapse
Yes And the solution is don't use modules anymore that work for me And you And everyone Even if you pass safetynet you need to enable magisk core to use broken apps like Mario run

I can confirm that enabling "Core Only Mode" in Magisk Settings does pass SafetyNet.
(Sigh), now magisk modules break SafetyNet. Now what do we do?

Safetynet checks failing with Magisk 20.4

hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.

jasonjiangyu said:
hi, i just flashed my xiaomi mix phone with Magisk 20.4. everything is new but the safetynet checks are failing.
i have previously tried on riru and edxposed. the checks say YES but i still cannot load pokemon go. i think those fixes are fake and not working, Google seems to be able to detect it still.
Can anyone help?
thanks.
Click to expand...
Click to collapse
Having the exact same issue with my Mix 3. Just flashed a few moments ago. Been looking at the other threads and it seems that no fix works as of now. Hoping that it isn't permanent as Google is cracking down on unlocked bootloaders.

Try to hide what you want via magisk hide.

Sorry, but that is not helpful. Same thing here. Device passed SafetyNet on 20.3. After upgrade to 20.4 it fails. What can I do to figure out what changed?

please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris

Kris Chen said:
please refer here to set it up in your phone.
Be notice: If you don't use edxposed, just skip it. If you do, please remember to install canary version of edxposed in Edxposed manager !
Kris
Click to expand...
Click to collapse
Thank you! You were right, this was not caused by the Magisk upgrade, but by EdXposed. After upgrading to Canary version SafetyNet passes again.

I'd also like to add (in case someone stumbles across this thread looking for answers) that Magisk v20.4+ has MagiskHide disabled by default. On a fresh install you will have to enable it before Hide will be able to do it's thing.

Viper4Android on Pixel 4A 5G

Has anyone been able to get Viper4Android working an Android 11? i flashed using the April 2021 Factory Image and have tried following multiple threads and guides, but have never gotten V4A to work consistently/completely.

Viper4android Android 11??
There is viper4android for android11 or I need to wait?
forum.xda-developers.com
This is the Viper4Android I've used for 6+ months. Its the only working, plug and play version I've found for Android 11. You simply download the zip, flash in magisk -- and done. There's nothing else you need to do.
Its 100% safe. Its 100% working. So easy.
I can vouch for it... And love it!

Click on the youtube link, and the zip is in the info there. No need to watch the video. Just flash with magisk or a kernel manager... and done.

I'm on LineageOS for microG 18.1, Proton kernel 1.4, Magisk rooted and this is not working for me. Further more, it mess up with SElinux making it disabled. Fortunatelly, there is an app SElinux switch, that on every boot make it Enforcing again.

I have the 5a but there are no posts yet.....
are any of you getting V4a to work using the USB port ? I run my phone usually into a dac via the usb, but Viper's only working on my phone through the headphone jack.

That YouTube video has been removed. Any chance someone could post the .zip? TIA

Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.

mmarcz said:
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
Click to expand...
Click to collapse
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.

Are you rooted normally with magisk per the instructions in this forum? Thats all I've done. Do you have a phone from google or from a carrier?
I got mine from google. Im rooted per the normal instructions. I have magisk v2.7.2.1 and the magiskhide props config modules installed. Ive never had a bootloop with either.
Not really sure what else to try. For what its worth, I cant get viper working on a rooted pixel 3, no bootloops, but the status always says abnormal.
Danny St. Angelo said:
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Click to expand...
Click to collapse

mmarcz said:
Are you rooted normally with magisk per the instructions in this forum?
Click to expand...
Click to collapse
Yes. And updating using this thread (thank you @drdionysius).
(Thanks for the reply btw.)
mmarcz said:
Do you have a phone from google or from a carrier?
Click to expand...
Click to collapse
Bought from a 3rd party actually, sealed box, no carrier branding or firmware.
Magisk version (from Canary channel) is f822ca5b (23001) -- that doesn't look right lol... oh, and Systemless hosts module installed only.
I only lost Viper when I updated to the September factory image
<shrug> idk why </shrug->
don't think it happened with other updates.
I'm pretty sure tho that I'd be in top shape, also indebted, if someone could post ViperFX_Android11.zip since the above referenced YouTube vid is gone and, with it, the link and I can't find the same version anywhere else. Thank you very much.

I just received my used 4a 5g. Got V4A v2.7.2.1 downloaded from Magisk v23 working last night...but it was a long trial & error ordeal. First download it showed Unsupported and Abnormal. Thought maybe it needed the Audio Mod Library but that didn't work. Then I tried the Audio Compatibility Patch to no avail. I tried V4A Legacy. Mulitple installs and uninstalls of all the various modules and combinations. At this point I'm not even sure what I did, or in what order/combination, but V4A is installed and working as intended. I do NOT have any of the Audio modules installed, just V4A. Don't know why it didn't work originally, or what made it finally work after fiddling with it for about an hour, but for me, that's my story/advice. Wish I could give an exact process to follow.

Here you go

mmarcz said:
Here you go
Click to expand...
Click to collapse
Top man!
Thank you

mmarcz said:
Here you go
Click to expand...
Click to collapse
Thanks for posting this! The version I had (v2.7.2.1) didn't work as reliably as it should. Often times it wasn't "processing". I uninstalled it and installed yours. So far it seems to be working well.
BIG BONUS - your version allows to view settings for the speaker, ear-buds, & blue-tooth without actually being connected to said devices. I never liked that "feature" of the newer V4A versions.

what about android 13?

banking app detecting root

I got a new banking app today that detects root, its https://play.google.com/store/apps/details?id=no.vipps.bankid
no problem with the Swedish bankid or other Norwegian banking apps. google pay/wallet works.
I tried blocking it in magisk block list. then with Shamiko, I'm afraid to test too many thing since google wallet is working now.

Try this modified USNF module. The issue you may be having is the new Play Integrity API.

I tried the previous version and now this one, still the same. I'm in no hurry to fix it, all other stuff work and the old bankid solution works 2 more years I think (hope)

I'm in your exact same position.
I have the MagiskHide module and used the DenyList, I also tried Shamiko, no luck for this app.
I tried the modified USNF module and no luck either.
I have several other apps where the above methods to avoid detection are working without problems, but not this one.

In the same boat as you guys. Also tried the modified magisk delta project with the old magisk hide, no luck.
Where is this?
SafetyNet is good, all other banking-and wallet-apps is working. RootBeer is not detecting root.
Oneplus 7t pro, stock latest stable rom. Magisk delta. Hide root from all apps. Renamed magisk app.

same problem here. tried everything i could find and no luck. might be a DRM problem? because 1 other issue i cant fix is apps like Netflix and prime video which are currently unusable because of DRM.

My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.

jale said:
My app was updated today, and immidiatly after the update I tried activating/logging in, and to my surprise it worked. There is a one hour grace/waiting period to activate, and I'm currently waiting for that.
If it is not working after the wait, I will update this post. So if no update, it is working.
See my previous post in this thread about my setup.
Click to expand...
Click to collapse
same for me. so its probably okay for everyone for now. disable auto update on it now hahaha and lets hope it stays that way.

Can confirm, it works now without any change to Magisk or other modules.
I waited the 1h period and after that I was able to activate it and use it to login.
I am using Shamiko and a modified USNF module, but probably are not required.

Great to know that it's working now. But, for next time i can give u guyz some more option to keep in mind:
**renaming/deleting the "twrp/fox" folder of the recovery, deleting all files related to magisk or xposed. Also, hiding developer mode option by "devoptshide" from lsposed. **