Hi y'all,
Can someone confirm if you're still able to make contactless payments with your rooted Pixel 6a? Mine worked fine until today, getting "Your phone can't make contactless payments as it doesn't meet software standards. Find out why at Google Pay help" message
January update, Magisk and Google Wallet up to date.
Just had this same problem, probably related to some server-side update by Google.
Updating USNF Magisk module to latest v2.3.1-MOD_3.0 by Displax solved the issue for me:
[DISCUSSION] Play Integrity API
chichino84 said:
Just had this same problem, probably related to some server-side update by Google.
Updating USNF Magisk module to latest v2.3.1-MOD_3.0 by Displax solved the issue for me:
[DISCUSSION] Play Integrity API
Click to expand...
Click to collapse
latest would be version 2.4.0 by kdrag0n, it got updated just recently.
that said, both work currently for passing play integrity / safety-net
edit: nevermind, me dumb dumb, I didn't see the _3.0
does v.2.4.0 not work anymore?
G5-User7080 said:
latest would be version 2.4.0 by kdrag0n, it got updated just recently.
that said, both work currently for passing play integrity / safety-net
edit: nevermind, me dumb dumb, I didn't see the _3.0
does v.2.4.0 not work anymore?
Click to expand...
Click to collapse
Not since the February release.
I'm still on A13 Jan 2023 update & security patch but stopped working for me too
chichino84 said:
Just had this same problem, probably related to some server-side update by Google.
Updating USNF Magisk module to latest v2.3.1-MOD_3.0 by Displax solved the issue for me:
[DISCUSSION] Play Integrity API
Click to expand...
Click to collapse
Thank you, updating the module solved the problem.
To save people the trouble of searching, v2.3.1-MOD_3.0 by Displax can be found here on github.
VoLTE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
My device is on RR-OS RR-N-v5.8.3 with android 7.1.2
I use only Magisk for rooting, and installed sony module and remoteplay module, and then I set the hide magisk with remote play related apps (remoteplay and dualshock)
but whenever I try to open the app error code 88001003 is keep appearing and I searched for it, could find it's from root detection but I didn't even install any other SU or root system.
Cos I clean installed RROS after turning it back to stock firm,
could anyone please help to find solution for this?
I am trying to figure it out for few days but still couldn't
Which version of Magisk are you using?
Single_Core said:
Which version of Magisk are you using?
Click to expand...
Click to collapse
Hi, thank you for replying! I am using the newest one 12.3 with 5.06 manager version.
zecz321 said:
Hi, thank you for replying! I am using the newest one 12.3 with 5.06 manager version.
Click to expand...
Click to collapse
Could you show a screenshot of passing safety-net and being successfully rooted?
Single_Core said:
Could you show a screenshot of passing safety-net and being successfully rooted?
Click to expand...
Click to collapse
I don't know why but uploading keep makes error so I will post the link of image
this is the screenshot of test passing scene of magisk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zecz321 said:
I don't know why but uploading keep makes error so I will post the link of image
this is the screenshot of test passing scene of magisk
Click to expand...
Click to collapse
That seems to be fine, I'd suggest uninstalling the app and try to install this one:
https://forum.xda-developers.com/android/apps-games/ps4-remote-play-android-thread-t3068225
Single_Core said:
That seems to be fine, I'd suggest uninstalling the app and try to install this one:
https://forum.xda-developers.com/android/apps-games/ps4-remote-play-android-thread-t3068225
Click to expand...
Click to collapse
I've tried it when I was using stock kernel, this app isn't 2.00 so doesn't work anymore.
I just tried it in case, as I guessed it gives error like this app need to be updated
Here is the post that helped me have a look at it
https://forum.xda-developers.com/showthread.php?p=73069982
Hit thanks if I have helped.
can you use android pay have you tested by making any purchase?
sam00561 said:
can you use android pay have you tested by making any purchase?
Click to expand...
Click to collapse
I can't test it because in India it is not yet available.
Hit thanks if I have helped
Yep this work for me as well. The main thing is that it changes ro.build.fingerprint to an acceptable fingerprint. You can do this manually without the module.
After updating to 13.3 it's not working.
Any idea why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
abhayruparel said:
After updating to 13.3 it's not working.
Any idea why?
Click to expand...
Click to collapse
Working still...
Just a warning: Android Device manager now thinks my phone is a Xiaomi Mi6. It's a side effect of this module using Mi6 prop values.
Just made a module that fixes SafetyNet while not changing your device name in 'Find My Device'
https://github.com/Sporif/lenovop2-safetynet-fix/releases
You can just add the zip file from Magisk Manager, or flash form recovery.
razr96 said:
Just made a module that fixes SafetyNet while not changing your device name in 'Find My Device'
https://github.com/Sporif/lenovop2-safetynet-fix/releases
You can just add the zip file from Magisk Manager, or flash form recovery.
Click to expand...
Click to collapse
This is what I get after flashing your module. Also see the reinstall button? Strange.http://cloud.tapatalk.com/s/5970a04e38dc9/Screenshot_20170720-175028.png?
abhayruparel said:
This is what I get after flashing your module. Also see the reinstall button? Strange.http://cloud.tapatalk.com/s/5970a04e38dc9/Screenshot_20170720-175028.png?
Click to expand...
Click to collapse
The reinstall button is there for me. I'm pretty sure it's supposed to be there. I think you might have a deeper problem that no module can fix. Have you enabled magisk hide? Also what rom are you on?
razr96 said:
The reinstall button is there for me. I'm pretty sure it's supposed to be there. I think you might have a deeper problem that no module can fix. Have you enabled magisk hide? Also what rom are you on?
Click to expand...
Click to collapse
I'm in aosgp. Initially i fixed the issue as mentioned above in this thread. Then updated to v13.3 after updating it stopped working. Luckily I net safety net access only for Snapchat login which I did successfully.
Hello,
I upgraded my Pixel 3a to Android 12 recently via an OTA update. I have put the root back on Magisk in the latest version (version 23011) and my phone indicates at startup that the bootloader is unlocked. I changed the kernel to ElementalX in last version and installed the last version of the Universal SafetyNet Fix module (v2.1.1) and Riru (v26.1.3).
However, when I check if my Android passes SafetyNet by installing the YASNAC application, it says "Fail" for both "Basic Integrity" and "CTS Profile".
It says "HARDWARE_BACKED" for the evaluation type and "RESTORE_TO-FACTORY_ROM, LOCK_BOOTLOADER" for Advice.
How do I pass the SafetyNet? Did I make a mistake?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disable/remove all modules and test again. Then test which module causes basic integrity to fail by enabling one by one.
The current Magisk Canary builds have a new hiding mechanism, Zygisk and the Deny list. That means a few things, but in your specific case it means you need to use Universal SafetyNet Fix v2.2.0 that's currently available as a paid update (and should be released for free in a week or so).
Riru doesn't work with Zygisk, and without Zygisk you can't use the Deny list on Magisk build 23010+... USNF v2.2.0 uses Zygisk instead of Riru, which is why you need that version instead.
Thanks for your help.
After reading some elements on this forum, I added both com.google.android.gms and com.google.android.gms.unstable, and added MagiskHide Props to come back to Basic evaluation type.
But, for the moment, CTS Profile Match remains in Fail.
in your specific case it means you need to use Universal SafetyNet Fix v2.2.0 that's currently available as a paid update (and should be released for free in a week or so).
Click to expand...
Click to collapse
Where do you find it ? I'm ok with paying for this module. Kdrag0n works incredibly well so why not helping ? But I can't find this version on his GitHub
Didgeridoohan said:
The current Magisk Canary builds have a new hiding mechanism, Zygisk and the Deny list. That means a few things, but in your specific case it means you need to use Universal SafetyNet Fix v2.2.0 that's currently available as a paid update (and should be released for free in a week or so).
Riru doesn't work with Zygisk, and without Zygisk you can't use the Deny list on Magisk build 23010+... USNF v2.2.0 uses Zygisk instead of Riru, which is why you need that version instead.
Click to expand...
Click to collapse
Oh, I found it : https://patreon.kdrag0n.dev/buy/exclusive/safetynet-fix-v2.2.0.zip
Thanks. It does work now !
Hello , if anyone can help me please ... I was rooted on oos11 and using magiskhide props config i edited my fingerprint so i was able to use google pay. When i recently updated to oos12and rooted google pay diddnt work i was not meeting security standards so i thought i would do the same procedure with editing fingerprint props, but on the list of devices that appear oos12 does not seem to appear for oneplus 7 pro. Is there a solution to have rooted oos 12 and google pay?
Yes brother, I have oneplus7pro 1917 and my problem was that I use cdma and I want to update but after the update the network disappears and there is no code to open diag to modify efs so I did the following downgrade to oxygen 11 and after that flasht twrp 3.6.2 and then install majsk root and then download the following add-on TWRP_A_B_Retention_Script and I did the backup efs via twrp and after that I downloaded the update ota12.1 and after the update did not reboot go to majsk and choose instal to inactive slot and choose reboot and then you will notice that the device has been updated to Android 12.1 and you have root and you also have twrp installed, go to twrp and do a restore I hope that this experience helped you, and I am sorry that my English is not very good and I used google translate
Thank you for the kind reply , i perfectly understood what you say no problem from tour english, but my problem is not to root the phone i was rooted already with the nethod tou said , my problem is to install working google pay on rooted oneplus 7 pro!
If you use magisk try enable zygisk
and deny google service and google play
next step install saftynet from this repo
Release v2.4.0 · kdrag0n/safetynet-fix
Highlights Play Integrity bypass without breaking device checks or causing other issues Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109) Other changes Updated instruc...
github.com
and follow the instruction of this module
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your reply i have already enabled zyisk and cofigured deny list but to no luck. Previously on oos11 the problem was solved by editing the fingerprint through magisk hide pro config. But this procedure is not supported now because i cant find there a fingerprint for oos 12 (only 9,10,11, see attached photo).
Is there anyone managed to make google pay work on rooted oos12 ? And if yes how?
Used s21 fingerprint. So far no issues
I rooted my phone yesterday. I am running android 13 nov sp (pixel experience plus). I installed many magisk modules. I will post the ss of the modules. I made sure I downloaded them from their Github pages. Today I noticed my privacy dots aren't working and the torch toggle says camera in use. I want to know if I am hecked or if thats like a failsafe trigger on android side after rooting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Aosp mods why notntry disabling this magisk module trial error
samsungics1200 said:
Aosp mods why notntry disabling this magisk module trial error
Click to expand...
Click to collapse
Omg it worked. I am a noob to rooting. But any idea why this happens?
samsungics1200 said:
Aosp mods why notntry disabling this magisk module trial error
Click to expand...
Click to collapse
Also I heard aosp mods is reputable. But why did this happen? Like I like the customisation i get from it. Any alternative?
SampreethSivakoti said:
Also I heard aosp mods is reputable. But why did this happen? Like I like the customisation i get from it. Any alternative?
Click to expand...
Click to collapse
I think it might be good idea to try other customizable roms like crdroid ,arrow os , evo x
SampreethSivakoti said:
I rooted my phone yesterday. I am running android 13 nov sp (pixel experience plus). I installed many magisk modules.
Click to expand...
Click to collapse
New member + all of the above. Recipe for disaster.
Don't come crying later on how your Poco suddenly bricked... without any reason whatsoever...
Tomo123 said:
New member + all of the above. Recipe for disaster.
Don't come crying later on how your Poco suddenly bricked... without any reason whatsoever...
Click to expand...
Click to collapse
Bruh i am just a new member but not my first time for all this. 🫡