[Discussion] Google Pay Magisk Discussion Thread

[BesoC]

that's normal and gwallet should work

Ah, I thought everything should be green Will clear PlayServices and Wallet data then...

 

[pndwal]

Ah, I thought everything should be green Will clear PlayServices and Wallet data then...

... PI strongIntegrity is like having S/N ctsProfileMatch=true + evaluationType=HARDWARE_BACKED, but even stricter... Banks/Google haven't gone there yet w/ S/N API nor PI API... PW

 

[zgfg]

• Set SELinux to enforcing - I set it to permissive earlier because of Viper4AndroidFX

If using V4A FX 2.7.2.1, it doesn't set SE Linux to Permissive and you should not need to force Permissive manually

And no need for Strong Integrity was already answered by others (and for the mater of fact, the same was commented numerous times in this thread already)

 

[BesoC]

... PI strongIntegrity is like having S/N ctsProfileMatch=true + evaluationType=HARDWARE_BACKED, but even stricter... Banks/Google haven't gone there yet w/ S/N API nor PI API... PW

that's normal and gwallet should work

Thanks a ton guys, Google trusts me again
One more question - if I update safetynet-fix to 2.4, will phone still pass the check?

 

[BesoC]

If using V4A FX 2.7.2.1, it doesn't set SE Linux to Permissive and you should not need to force Permissive manually

And no need for Strong Integrity was already answered by others (and for the mater of fact, the same was commented numerous times in this thread already)

No, it does not set by itself. I had problems enabling its driver, one thread on XDA was strongly suggesting to set SELinux to permissive. I did and it worked, so... . However, now when I reverted it back to enforcing, Viper still works
I did not search for STRONG_INTEGRITY, my bad

 

[BesoC]

Thanks a ton guys, Google trusts me again
One more question - if I update safetynet-fix to 2.4, will phone still pass the check?

SafetyNet-Fix 2.4.0 works for me

 

[zgfg]

No, it does not set by itself. I had problems enabling its driver, one thread on XDA was strongly suggesting to set SELinux to permissive. I did and it worked, so... . However, now when I reverted it back to enforcing, Viper still works
I did not search for STRONG_INTEGRITY, my bad

Good that V4A V2.7 works for you with Enforcing mode (as it should)

Btw, there are two newer versions:

1) Repackaged V4A - finding and patching audio drivers when they are scattered to other system folders (needed for some devices):

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com

2) (1) + Reverse engineered V4A alpha v0.2.0 support for 64-bit audio drivers (needed on some new devices that could not fall-back to 32-bit audio drivers):

GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX

Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.

github.com

Both also don't require SE Linux Permissive. Might need AML v4.2 (recently updated):

https://raw.githubusercontent.com/Zackptg5/Audio-Modification-Library/master/install.zip

PS:
And don't forget to enable Legacy mode (and of course, Master limiter)

 

[BesoC]

Good that V4A V2.7 works for you with Enforcing mode (as it should)

Btw, there are two newer versions:

1) Repackaged V4A - finding and patching audio drivers when they are scattered to other system folders (needed for some devices):

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com

2) (1) + Reverse engineered V4A alpha v0.2.0 support for 64-bit audio drivers (needed on some new devices that could not fall-back to 32-bit audio drivers):

GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX

Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.

github.com

Both also don't require SE Linux Permissive. Might need AML v4.2 (recently updated):

https://raw.githubusercontent.com/Zackptg5/Audio-Modification-Library/master/install.zip

Thanks for sharing

 

[pndwal]

No, it does not set by itself. I had problems enabling its driver, one thread on XDA was strongly suggesting to set SELinux to permissive. I did and it worked, so... . However, now when I reverted it back to enforcing, Viper still works

No... Days when that was needed are gone...

I used to use the install-and-disable-AML trick for fixing driver problem, but I realised we simply need a way to 'reset' driver once in Legacy mode...

Simply disabling module and rebooting, then enabling and rebooting again works and Neon driver installs properly without installing AML etc... If you do get Driver Status: Abnormal again in future, eg. If you need to reinstall, just use this trick to fix it...

Also, I use this build now which seems to fix old issues too:
https://github.com/programminghoch10/ViPER4AndroidRepackaged

PW

 

[BesoC]

No... Days when that was needed are gone...

I used to use the install-and-disable-AML trick for fixing driver problem, but I realised we simply need a way to 'reset' driver once in Legacy mode...

Simply disabling module and rebooting, then enabling and rebooting again works and Neon driver installs properly without installing AML etc... If you do get Driver Status: Abnormal again in future, eg. If you need to reinstall, just use this trick to fix it...

Also, I use this build now which seems to fix old issues too:
https://github.com/programminghoch10/ViPER4AndroidRepackaged

PW

Yes, legacy mode switch trick worked for me . Many thanks for your help

 

[DerGriechisch]

Same issue with me? Did any solution found yet?

this summer google introduced a new api and thats why youa re having touble
install this https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck&hl=en&gl=US and check

you need to get MEETS_DEVICE_INTEGRITY and MEETS_BASIC_INTEGRITY green
you can do this with magisk hide and various magisk modules
i managed to do it by selecting EVERYTHING in magisk denylist (every single app including system apps)

once these two are green you need to delete
1.google play services app data
2.play store app data
3.wallet app data

if everything works you can now go to wallet tap to pay setup and you will see that "Your phone meets security requirements"
enter your card number etc and you are ready !

let me know if it works

 

[m0han]

I don't know about you @pndwal, but I believe @zgfg was using v2.7.2.1 which is just 1.62 MB in size, whereas the new one is 85.1 MB in size. Just wanna ask you guys whether there is any significant improvement in sound over the old version. I believe the two of you are not on A13 (yet).

 

[zgfg]

I don't know about you @pndwal, but I believe @zgfg was using v2.7.2.1 which is just 1.62 MB in size, whereas the new one is 85.1 MB in size. Just wanna ask you guys whether there is any significant improvement in sound over the old version. I believe the two of you are not on A13 (yet).

Repackaged is not an 'official' V4A

It was still v2.7.2.1 but enhanced to search for the other/duplicated folders with copy of (32-bit) audio drivers that also need to be patched for the newer phones (actually, I had my post-fs-data.sh modifications and the developer incorporated them into the V4A Java code)

Depending on the phone/ROM, that might be enough for installation of V4A on A13, or not.
However, as I mentioned in my previous post, some new phones (even with A12) require the use of 64-bit drivers and for that you would need the Re-engineered v4A (currently Beta v0.2.0, IRS and some other filters are not yet supported - but generally Beta was confirmed to work even by A13 users)

---

If you unzip (or install) the Repackaged V4A, you could see that developer also included an archive of 80 MB IRS filters - that's why his zip file is that big

Anyway, there is another thread dedicated to V4A, hence please use that one for further V4A discussion:

[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7

ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...

forum.xda-developers.com

 

[pndwal]

I don't know about you @pndwal, but I believe @zgfg was using v2.7.2.1 which is just 1.62 MB in size, whereas the new one is 85.1 MB in size. Just wanna ask you guys whether there is any significant improvement in sound over the old version. I believe the two of you are not on A13 (yet).

... Yup, audio engine is the same, so doubt much has changed for audiophiles... Ease of installation seems to be improved w/ this package installer; Neon driver setup just works IIRC... PW

 

[raulci]

So, after some months without any issue, now Google Wallet/Pay is complaining that my Xiaomi Mi9 is rooted...

I have safetynet fix 2.4.0 installed.

Anyone is having issues too?
Thanks!

Edit: just read here https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-142 and it's happening the same to some other colleagues. Reverting to 2.3.1 mod.

Thanks! Great community!

 

[Fry-kun]

+1, wallet stopped working in the last couple of days
Had safetynet 2.2.0 (updating to 2.4.0 now) & shamiko 0.6

 

[pndwal]

So, after some months without any issue, now Google Wallet/Pay is complaining that my Xiaomi Mi9 is rooted...

I have safetynet fix 2.4.0 installed.

Anyone is having issues too?
Thanks!

Edit: just read here https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/page-142 and it's happening the same to some other colleagues. Reverting to 2.3.1 mod.

Thanks! Great community!

+1, wallet stopped working in the last couple of days
Had safetynet 2.2.0 (updating to 2.4.0 now) & shamiko 0.6

Yup...

Clearly new 2.4.0 is failing intermittently for many, and Google Pay/Wallet users particularly are getting failures w/ 'Device doesn't meet Security requirements' message as Google monitors device security even when Pay/Wallet is not invoked... I recommend using @Displax's USNF modded fork at least until official USNF is updated...

I gave what clues I have in post in USNF thread:

MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...

forum.xda-developers.com

Many more comments there follow... PW

 

[Fry-kun]

I gave what clues I have in post in USNF thread:

https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88049087...

Broken link

 

[Fry-kun]

I recommend using @Displax's USNF modded fork at least until official USNF is updated...

Installed Displax' usnf 2.3.1-MOD_2.1 (from GitHub) and seeing the same issue.

Edit: cleared Wallet cache and it's not complaining now... So maybe it did work.
Will test payments later

 

[pndwal]

Broken link

... Fixed.

Installed Displax' usnf 2.3.1-MOD_2.1 (from GitHub) and seeing the same issue.

What symptoms?... PW