Related
On latest Xiaomi.eu got safety net test passed. Card added successfully, but when I try to pay nothing happens. But on custom roms like los or rr AP working as it should.
MIUI 9 from xiaomi.eu 7.8.31, Magisk v13.6 + Universal safetynet fix v2 beta 5. Safety net passed.
Did anybody got ap works on Xiaomi.eu?
Maybe try flashing latest eu rom and latest magisk will help
I found out that all miui I had to try wasn't work with android pay. I repeat that on lineage and rr all works perfect
I agree with Zubodub. MIUI 9 safetynest pass, you are able to add card but when payment made, the phone doesn't react. It works perfectly well in lineage OS. I would like to get it working too.
I can't remember the exact options, but have you changed the wallet type from the Chinese version to, I think, HCE wallet? These are under the NFC options if I remember correctly. It worked fine as you say but no success scanning, until setting the NFC options correctly.
you should go to buglist
I've unlocked the bootloader. I've grabbed boot.img and patched it with Magisk, etc. and now I'm rooted. Great.
But I cannot pass SafetyNet.
I've done MagiskHide, easy enough.
But I also installed the "Universal SafetyNet Fix" module ("This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders or custom verified boot keys. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.")
And I've also installed the "MagiskHide Props Config" module and run the "props" command. I've tried going through various options, changing the signature (they don't have OnePlus 9 Pro though, best I could do was OnePlus 8T Pro) and even doing full emulation. No matter what options I try, I cannot pass SafetyNet. As a result, things like Netflix won't show up in the play store.
Anybody had any luck?
In the past I've additionally installed a custom kernel, one that would hide the fact that the bootloader was unlocked and help pass safetynet. I think that's the "puzzle piece" I'm missing.
I can't stand the new xda forums. Can't easily find the kernel development threads or even the custom ROM's threads.
There's an issue with safetynet on the latest Magisk. You need the canary version to pass safetynet.
entropism said:
There's an issue with safetynet on the latest Magisk. You need the canary version to pass safetynet.
Click to expand...
Click to collapse
Really? Omg I've been fighting with SafetyNet for 2 days trying different modules and options...
Ok let me try Canary.
Son of a ... Ok, well that worked. Kind of annoyed I learned all about "Universal SafetyNet Fix" and hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. And then I learned about
MagiskHide Props Config and props files and device fingerprints, etc.
Oh well, at least I can pass safetynet.
Should I delete this thread? Help reduce some clutter.
glitchsys said:
Son of a ... Ok, well that worked. Kind of annoyed I learned all about "Universal SafetyNet Fix" and hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. And then I learned about
MagiskHide Props Config and props files and device fingerprints, etc.
Oh well, at least I can pass safetynet.
Should I delete this thread? Help reduce some clutter.
Click to expand...
Click to collapse
I would leave the thread so that people can search if they have the same issue. Not everyone knows to use canary (obviously... lol) and there are other good ideas in your post that may resolve other issues.
This literally happened last week, and it will be pushed to the main Magisk module shortly. I learned about it when my 7T wouldn't pass safety.
I've enabled magical hide, have added props config module and changed fingerprint to Pixel 5, and have flashed universal safetynet fix, and lastly I updated to canary build. I still don't pass CTS. Any help?
I installed this Canary version from Magisk GitHub and pass... T-Mobile variant running it with Omega Kernel.
I am passing safety net, but can't get Netflix to work. It is saying it's not compatible with my device and to update to latest version
the bolt of thunder said:
I am passing safety net, but can't get Netflix to work. It is saying it's not compatible with my device and to update to latest ve
Click to expand...
Click to collapse
Did you clear data and cache for the play store and also Magisk hide all the Google Play Service information.. it's working for me..
I cleared data and cache for Netlfix only. I did Magisk hide all the Google Play Services. Unfortunately I unrooted and re-locked my bootloader. I will root again maybe after some time. Very sad.
the bolt of thunder said:
I am passing safety net, but can't get Netflix to work. It is saying it's not compatible with my device and to update to latest version
Click to expand...
Click to collapse
I had to uninstall all updates to Netflix and then update again in the Play Store to get it working again. Before the last OTA I had to install a standalone APK over the system Netflix because Play Store version didn't work at all. Netflix does work on rooted devices, it's just a bit of a hassle for some reason.
entropism said:
There's an issue with safetynet on the latest Magisk. You need the canary version to pass safetynet.
Click to expand...
Click to collapse
thanks
glitchsys said:
Son of a ... Ok, well that worked. Kind of annoyed I learned all about "Universal SafetyNet Fix" and hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. And then I learned about
MagiskHide Props Config and props files and device fingerprints, etc.
Oh well, at least I can pass safetynet.
Should I delete this thread? Help reduce some clutter.
Click to expand...
Click to collapse
Did you uninstall magisk and all the modules? Having the same issue won't pass CTS profile match.
I would really like to use my banking apps on my phone, but because of failing SafetyNet, I can't.
It seems that kdrag0n's safetynet-fix won't work on the 10Ts -- there is this GitHub issue concerning MIUI.
I also tried MagiskHidePropsConf but I couldn't get the boot scripts to run, no matter which of the 3 boot stage options I picked, or whether using backgrounding or not.
Has anyone got a 12.5.1+ stock MIUI passing SafetyNet?
If no, which ROM would you recommend for regular stable releases? I see that Pixel Experience currently has no maintainer for our device.
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
HW898 said:
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
Click to expand...
Click to collapse
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
deathblade said:
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
Click to expand...
Click to collapse
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
HW898 said:
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
Click to expand...
Click to collapse
I just remembered, the unofficial is setup to pass safteynet out the box, but more maybe needed for Gpay to work. Once you flash it try it out, if you run into issues I can provide what I did to get Gpay working
deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
HW898 said:
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
Click to expand...
Click to collapse
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
deathblade said:
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
Click to expand...
Click to collapse
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
HW898 said:
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
Click to expand...
Click to collapse
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
deathblade said:
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
Click to expand...
Click to collapse
I see... I will try installing the official one without magisk as I won't want to meddle with rooting stuff for now, will get back with results asap!
deathblade said:
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Click to expand...
Click to collapse
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
HW898 said:
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
Click to expand...
Click to collapse
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
Aite thanks for the help mate! just installed but apparently, i couldn't find gapps despite sideloading it.. might have to reinstall again
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
HW898 said:
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
Click to expand...
Click to collapse
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
deathblade said:
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
Click to expand...
Click to collapse
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
HW898 said:
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
Click to expand...
Click to collapse
You install the pixelify module? Also can you explain how it's not working?
deathblade said:
You install the pixelify module? Also can you explain how it's not working?
Click to expand...
Click to collapse
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
HW898 said:
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
Click to expand...
Click to collapse
This is the pixelify module I installed then removed, you can give it a try.
GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
Magisk module to enables pixel exclusive features and ui - GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
github.com
Hello guys,
I just upgraded from oxygen 12 to 13 last week.
Since than, google pay does not work for me. It used to work perfectly with oxygen 12.
As i have mentioned at title, my one plus 9 pro model is LE2121, im quite sure its related to this.
I've looked for a solution for this here and also in other forums, but i cannot find one at the moment.
Hard reset is my last option .
Does anyone facing this issue and managed to solve it?
Many thanks.
I'm using GPay and all banking apps on rooted LE2121. This is what I did.
Installed Safetynet Fix and Shamiko modules
Configured Zygisk & Denylist
Turned OFF "enforce denylist" (according to Shamiko instructions)
Renamed Magisk to something else (look in Magisk settings)
See if that works for you.
tathagatab said:
I'm using GPay and all banking apps on rooted LE2121. This is what I did.
Installed Safetynet Fix and Shamiko modules
Configured Zygisk & Denylist
Turned OFF "enforce denylist" (according to Shamiko instructions)
Renamed Magisk to something else (look in Magisk settings)
See if that works for you.
Click to expand...
Click to collapse
This was working for A12.
For A13 it's a different story and a solution is to remove the Work profile or any cloned apps.
RASTAVIPER said:
This was working for A12.
For A13 it's a different story and a solution is to remove the Work profile or any cloned apps.
Click to expand...
Click to collapse
It works for me on OOS 13. Maybe because I have only one profile and zero cloned apps.
More information here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
Had this one. Via ADB I had to delete second profile which was created when I cloned WhatsApp.
Google Wallet/payments doesnt work with cloned apps enabled. its many times reported bug and still is here in stable. same problem was in upgrade from 11 to 12.
In FAQ OnePlus stated they fixed it. But still in Stable the issue persists.
l_mike said:
In FAQ OnePlus stated they fixed it. But still in Stable the issue persists.
Click to expand...
Click to collapse
yes, because promises of new 1+ are trash. is not fixed on stable F.16.
l_mike said:
Had this one. Via ADB I had to delete second profile which was created when I cloned WhatsApp.
Click to expand...
Click to collapse
There is no way I delete my second whatsapp profile just to get this upgrade.
First they need to solve such important bug.
Hello all,
thanks for all the replies.
What fixed the issue for me was to make hard reset.
Luckly, its very easy on one plus with the google cloud backup and restore method.
So i made it, and everything works fine. (Had also few bugs that where fixed also.. on the way..).
Also, Gpay works in my galaxy wacth 4!! with oxygen 12 i couldn't use it!
After all, happy ending!
davidz85 said:
Hello all,
thanks for all the replies.
What fixed the issue for me was to make hard reset.
Luckly, its very easy on one plus with the google cloud backup and restore method.
So i made it, and everything works fine. (Had also few bugs that where fixed also.. on the way..).
Also, Gpay works in my galaxy wacth 4!! with oxygen 12 i couldn't use it!
After all, happy ending!
Click to expand...
Click to collapse
nice, but for other people who use xy apps hard reset isnt easy. for me is "5 days settuping.." its main bug with cloned apps. you just delete 999 user with hard reset.