Database Info

oneplus 6 rooted google pay issue

hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando

Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP

Google pay is working fine for me too also rooted with magisk

Some people have begun to have issues with Magisk and safetynet tripping over the past few days, we're trying to figure it out in the Magisk forums. This appears to have coincided with the Android Pie release and it's possible modifications have been made to safetynet. John Wu is looking into it. There are a few additional modules you can try along with Magisk Hide. Some work for some people. I've had no luck yet personally.

ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.

ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.

Yesterday 12:27 PM
Pundy
Try to hide google pay app with "magisk hide" in magisk app
Edit:
Google Pay is working with my OP6 [email protected] and TWRP
Click to expand...
Click to collapse
thanks for the tip but i already have it hidden.
Yesterday 11:25 PM
yldlj
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i Tried this as it sounded promising, but no joy, i still can't get it to work, thanks for the help though so far everyone, but nothing has worked.

texasaggie1 said:
Busybox always makes me fail safety net, even systemless. Make sure you haven't installed a magisk module with it or a custom rom with it. I think recent Google versions check for it.
Click to expand...
Click to collapse
Unfortunately removing BusyBox didn't change the fail

fireguy0306 said:
Unfortunately removing BusyBox didn't change the fail
Click to expand...
Click to collapse
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play

yldlj said:
Try clearing play store data. Same thing happened to me and my play store was uncertified from unlocking the bootloader. Once I cleared app data it was certified and could add my card.
Click to expand...
Click to collapse
i clear all data every time i change anything as standard practice, but thanks for the idea
texasaggie1 said:
Have you tried using the island app ?
Also you know you have to wipe/reset Google Play before you check again correct?
once you fail safety net it will always fail no matter what until you reset Google Play
Click to expand...
Click to collapse
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug

Have the problem as well..
I have the same problem. Running OP6, Android P Developer Preview 4, TWRP recovery and magisk (v16.7).
Magisk hide is enabled for GPay as well as many other banking apps. I know for sure its something to do with GPay, since the other apps that initially complained and triggered safetynet, started running as soon as I enabled Magisk hide for those apps.
ClassicRando said:
i clear all data every time i change anything as standard practice, but thanks for the idea
i don't know what the island app is, but as above i wipe all data as standard everytime i change something, i'll look inti island, but i'm starting to thing this is just a bug
Click to expand...
Click to collapse

Google pay issue with rooted oneplus 6 (PIE)
Hi all,
Try the steps as advised in the video, it worked for me
https://youtu.be/lyC1SpDWMNA
Thanks

Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....

android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
This worked for me thank you

Websterwjc said:
This worked for me thank you
Click to expand...
Click to collapse
Welcome...

ClassicRando said:
hi i have a magisk and twrp rooted oneplus 6 with radioactive kernel, and can't use google pay, i get an error message please check your settings after it's tried to verify with the bank, but the bank say everything is fine, and it was working before i unlocked bootloaders and installed custon software, any ideas out there, any help would be greatly appreciated, thanks
Rando
Click to expand...
Click to collapse
I finally found the route cause of gpay not working, it was my WiFi, I found the answer purely by accident when I was in a shop and had forgotten my wallet, so I did a last ditch attempt to set up gpay again with my mobile data and it worked first time, when I got home i deleted the app and reinstalled while trying to set up via WiFi again and I got the same error message, switched to mobile data and it set up perfectly.
I have no idea why my WiFi was stopping gpay from getting set up, but that was the cause, 100% certain.

android_smater said:
Clear data of your and force app
Magisk hide check your app and other google app
And most imp disable phone permissions for google play service.....
Click to expand...
Click to collapse
yes, this works.

Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks

antivirtel said:
Hi,
It was working before for me until 15th March, and now it completely stopped working. I've tried to re-add my card, but then it complains about the device is rooted or altered. I could keep device certification, and safetynet check passes. Tried these methods, nothing.
Does anyone has any suggestions?
Thanks
Click to expand...
Click to collapse
Update Magisk to v19 and clear data of the app, hide it in Magisk Hide and try to re-add it

I have a fix I u didn't have one, First of all hide all Google apps from Magisk hide.
Then goto setting, apps, permission and disable telephone permission of google play services. That's it.

Netflix gone?

Can't download Netflix for Pixel 3
In Google store says not available for my phone!
Anyone else?
Any links to most recent APK that I won't destroy my device with?

If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.

sliding_billy said:
If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.
Click to expand...
Click to collapse
My device has shown not certified for awhile. It never seemed to be an issue as I never had any problem with apps. But now I'm good [emoji4]

sliding_billy said:
If your device is showing as not certified in play store settings, Netflix doesn't show for new installs. Hide the Play Store with Magisk, and then clear the Play store cache and data and open it back up. You should then show certified, and Netflix will be available. There is also a version for sideloading on the Netflix website.
Click to expand...
Click to collapse
Play Store doesn't say anything about certification in the settings, but Netflix is missing so I assume I'm not certified. I tried following your instructions with Magisk Hide, but Netflix is still not showing. (If I try to search it from Google to get to the Play Store entry, it says my device is not compatible with this version.) I also tried sideloading the version from their website. It installs fine, but when I launch it, it says the device is not supported. I also tried using Magisk Hide on Netflix to no avail. Additionally, Magisk says my device passes both SafetyNet checks. Any other ideas?

fysix said:
Play Store doesn't say anything about certification in the settings, but Netflix is missing so I assume I'm not certified. I tried following your instructions with Magisk Hide, but Netflix is still not showing. (If I try to search it from Google to get to the Play Store entry, it says my device is not compatible with this version.) I also tried sideloading the version from their website. It installs fine, but when I launch it, it says the device is not supported. I also tried using Magisk Hide on Netflix to no avail. Additionally, Magisk says my device passes both SafetyNet checks. Any other ideas?
Click to expand...
Click to collapse
Not showing anything about certified means that it is not certified. Are you on a Pixel 3? Could be a handful of things causing it. Are you able to clear cache and data in Play Store? If not, you won't be able to get certified. That happens a lot if you have a Magisk Module that greys out that option like Edge Sensor. My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting. Once Netflix is installed, it doesn't matter if you are rooted. Keep Play Store hidden though.

sliding_billy said:
Not showing anything about certified means that it is not certified. Are you on a Pixel 3? Could be a handful of things causing it. Are you able to clear cache and data in Play Store? If not, you won't be able to get certified. That happens a lot if you have a Magisk Module that greys out that option like Edge Sensor. My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting. Once Netflix is installed, it doesn't matter if you are rooted. Keep Play Store hidden though.
Click to expand...
Click to collapse
Yep, pixel 3.
I'll give your suggestions a try as soon as I get a chance

sliding_billy said:
My sugestion is to flash boot.img to both slots and then clear cache/data in Play Store and get certification back before re-rooting.
Click to expand...
Click to collapse
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
Did it show anything about certification in Play Store Settings (at the very bottom)? It does sometimes take a couple of times entering Play Store and possibly rebooting to show as certified. There really is nothing else other than clearing cache/data in Play Store and being on a device that can show as certified (which clearly the Pixel 3 is). Normally, once you clear cache/data even rooting won't stop the certification (if you hide Play Store with Magisk Hide before opening it again) it just takes some little bit of time that I have not ever been able to completely narrow down to an exact action. I have to do this pretty much every month after loading the monthly update and it always works (Netflix does not need reinstalled or anything after the first time as long as the device is certified if an update shows up).

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
Two other thoughts. Are you passing SafetyNet? If not, that may point to the root cause. The other one just occurred to me, but are you running a custom kernel? If not, your unlocked bootloader is being exposed and may very well be keeping Netflix from showing up. If that is the case, you definitely want to look into one of the custom kernels here. I use ElementalX, and it is the closest to stock with minor adjustments and of course it hides the unlocked BL.

sliding_billy said:
Two other thoughts. Are you passing SafetyNet? If not, that may point to the root cause. The other one just occurred to me, but are you running a custom kernel? If not, your unlocked bootloader is being exposed and may very well be keeping Netflix from showing up. If that is the case, you definitely want to look into one of the custom kernels here. I use ElementalX, and it is the closest to stock with minor adjustments and of course it hides the unlocked BL.
Click to expand...
Click to collapse
Same problem here.
Passing SafetyNet
Play Store get certification
But can't download on Play Store. Try installation apk from Netflix, App does not support this device

beinanchen said:
Same problem here.
Passing SafetyNet
Play Store get certification
But can't download on Play Store. Try installation apk from Netflix, App does not support this device
Click to expand...
Click to collapse
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/

sliding_billy said:
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
Click to expand...
Click to collapse
yes, if my lock bl, I can download it from Play Store and working well, all the problem from Unlock bl

beinanchen said:
yes, if my lock bl, I can download it from Play Store and working well, all the problem from Unlock bl
Click to expand...
Click to collapse
Install a custom kernel. They all (as far as I know) hide the unlocked BL at this point.

sliding_billy said:
Install a custom kernel. They all (as far as I know) hide the unlocked BL at this point.
Click to expand...
Click to collapse
Try to install Proton Kernel, same problem. ?
---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------
sliding_billy said:
I just looked at the Netflix support page with instructions for side loading the app. It claims it is only compatible up to Android 7.1.2, so clearly the one on their site will not work anymore. They even say to contact them if you are certified, but I am guessing all they are going to ask you is about BL unlocking. To my question of the other user, are you running a custom kernel? I am sure Netflix sees a BL unlock if it is exposed. The only other thing you can do is try APKMirror. https://www.apkmirror.com/apk/netflix-inc/netflix/netflix-6-26-1-build-15-31696-release/
Click to expand...
Click to collapse
Already install, it's working now, but still can't update on Play Store

fysix said:
Flashed the vanilla boot.img then cleared cache/data for Play store and I'm still not certified. Any other suggestions?
Click to expand...
Click to collapse
beinanchen said:
Try to install Proton Kernel, same problem. ?
---------- Post added at 02:33 PM ---------- Previous post was at 02:29 PM ----------
Already install, it's working now, but still can't update on Play Store
Click to expand...
Click to collapse
I wish I had more insight. I am using ElementalX and Magisk 19.3 with Play Store hidden. I actually factory reset my P3XL about a month ago to return to stock image from custom OS, and after all of the things mentioned was able to get Netflix from the Play Store and got the last update on June 14 (the one listed on the Play Store page). I'm not sure if something has changed since then. I am hesitant to uninstall and see if it is still there. I have 5 devices running Netflix including a P3 and P3XL. The other devices all are rooted with 19.3 as well and are running Nugget or Oreo with stock kernels. Just needed to get them to show certified and hide Play Store. The Pixels have been BL unlocked since the day they arrived last fall.
Fysix (and beinanchen if relevant)- I just read another post of your saying you are running Xposed. I mentioned that some Magisk modules could be an issue. I would disable all Magisk modules and reboot at least for testing.

sliding_billy said:
I would disable all Magisk modules and reboot at least for testing.
Click to expand...
Click to collapse
Currently I'm on a stock boot partition so no Magisk or Xposed is running. I did the little migration wizard from my old Pixel 2 to my Pixel 3 immediately after unlocking the bl and I remember Netflix being omitted then even with just the bootloader unlocked and no Magisk. I haven't had a chance to try ElementalX yet but I'm fairly optimistic that the kernel is ratting me out currently and ElementalX will fix it.

fysix said:
Currently I'm on a stock boot partition so no Magisk or Xposed is running. I did the little migration wizard from my old Pixel 2 to my Pixel 3 immediately after unlocking the bl and I remember Netflix being omitted then even with just the bootloader unlocked and no Magisk. I haven't had a chance to try ElementalX yet but I'm fairly optimistic that the kernel is ratting me out currently and ElementalX will fix it.
Click to expand...
Click to collapse
Either way, EX is a nice kernel. The EX Kernel manager is a really nice app and the dev deserves the financial support. He literally has that kernel updated normally before most folks have even installed their monthly Google update. I have separate copies on both of my Pixels. Plus, it beats the hell out of having to copy/flash the kernel manually. Let me know how it goes.

I have the same issue.
I'm on dirty unicorn with kirishakura kernel and magisk.
I'm passing safetynet thought and downloading the apk doesn't work as the app crash.
Edit: play store says I'm certified.

Same problem here.
Running a custom kernel that is based off of DU with some ElementalX cherry-picks. Rom is custom compiled AOSiP. Latest Magisk canary installed and passing SafetyNet. Only other thing I did was hack gms DB's to allow Google Pay to work. I'm also using Vanced YouTube.

sliding_billy said:
Either way, EX is a nice kernel. The EX Kernel manager is a really nice app and the dev deserves the financial support. He literally has that kernel updated normally before most folks have even installed their monthly Google update. I have separate copies on both of my Pixels. Plus, it beats the hell out of having to copy/flash the kernel manually. Let me know how it goes.
Click to expand...
Click to collapse
Tried ElementalX and it didn't make a difference

Google Pay with rooted Phone

Hi.
I have Pixel 2 on December patch. Stock kernel, and boot loader, but rooted with Magisk 18.1 installed. Yesterday my google pay stopped working. Jut kept getting error message that can't pay with this device, or something like that. I removed default card, and re-added. Now when I try to set it up to pay in store it keeps saying that it can't because phone is rooted, or modified. I haven't installed any updates, so not sure what changed.
Anyway, how can I get around this? Ran SafetyNet Check, but it didn't help.
Thanks

UDPoster said:
Hi.
I have Pixel 2 on December patch. Stock kernel, and boot loader, but rooted with Magisk 18.1 installed. Yesterday my google pay stopped working. Jut kept getting error message that can't pay with this device, or something like that. I removed default card, and re-added. Now when I try to set it up to pay in store it keeps saying that it can't because phone is rooted, or modified. I haven't installed any updates, so not sure what changed.
Anyway, how can I get around this? Ran SafetyNet Check, but it didn't help.
Thanks
Click to expand...
Click to collapse
+1 **bump** same thing happened to me about a week ago on in store payments. Was on November Patch....and 18.1 Magisk. Uninstalled Magisk....updated to March patch....reinstalled Magisk and Magisk manager....repackaged Magisk to hide it and hid google pay in Magisk Hide. I also pass Safety Net check so I am not sure why it isn't working
Everything was working fine and had been for well over a year until last week.
Just got off chatting with Google Pay support....apparently the bootloader unlock hide is no longer working and it is being detected somehow and not being hidden by Magisk. I guess wait on an update!
---------- Post added at 04:42 PM ---------- Previous post was at 04:15 PM ----------
bakemcbride21 said:
+1 **bump** same thing happened to me about a week ago on in store payments. Was on November Patch....and 18.1 Magisk. Uninstalled Magisk....updated to March patch....reinstalled Magisk and Magisk manager....repackaged Magisk to hide it and hid google pay in Magisk Hide. I also pass Safety Net check so I am not sure why it isn't working
Everything was working fine and had been for well over a year until last week.
Just got off chatting with Google Pay support....apparently the bootloader unlock hide is no longer working and it is being detected somehow and not being hidden by Magisk. I guess wait on an update!
Click to expand...
Click to collapse
We are not alone.....looks like the latest Google Play services is the culprit and is a little sneakier than before. There is a workaround posted in the thread:
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
I'll just wait for the Magisk Update.

I just updated my phone from 8.1 to 9.0 (edit: March security patch) and installed Magisk 18.1. Safetynet passes and I checked off every google-related app in Magisk Hide, but I still can not add my card because Google Pay is detecting root. My banking app (HSBC) is also able to detect root, but all that does it show a warning. Hoping the next Magisk version has a fix.
Edit: Just tried the fix linked above and it did not work.

jrbmed08 said:
I just updated my phone from 8.1 to 9.0 (edit: March security patch) and installed Magisk 18.1. Safetynet passes and I checked off every google-related app in Magisk Hide, but I still can not add my card because Google Pay is detecting root. My banking app (HSBC) is also able to detect root, but all that does it show a warning. Hoping the next Magisk version has a fix.
Edit: Just tried the fix linked above and it did not work.
Click to expand...
Click to collapse
It did work for me. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

jasonbiggs said:
It did work for me. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yeah I don't know why since I followed all the instructions, but I'll just wait for the next Magisk update.

Well... Even though I had background data services disabled it still updated libraries to 15. Now it stopped working again [emoji50] How to stop it from updating?
Sent from my [device_name] using XDA-Developers Legacy app

Question Safetynet fix for Android 12?

So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant

Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.

I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.

There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.

BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.

I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process

Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.

Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)

BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.

KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...

If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.

Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.

Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.

KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.

Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..

I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.

Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.

Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.

KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.

I dont have any issues with safetynet.

Question Suddenly can't use Google wallet

Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?

eddy92 said:
Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?
Click to expand...
Click to collapse
What does Play Integrity Checker or TB Checker report for Play Integrity results?

V0latyle said:
What does Play Integrity Checker or TB Checker report for Play Integrity results?
Click to expand...
Click to collapse
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?

eddy92 said:
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?
Click to expand...
Click to collapse
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.

V0latyle said:
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.
Click to expand...
Click to collapse
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me

eddy92 said:
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me
Click to expand...
Click to collapse
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.

erik2041999 said:
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.
Click to expand...
Click to collapse
Hi, thanks for the tip. Sorry stupid question maybe, but where can i find Displax safteynet fix? When searching I can only find Kdrag0ns version. Even on Displax Github it seems to link to the Kndrag0n version.
EDIT: Sorry, nvm I found it! (Link if someone else is looking: https://github.com/Displax/safetynet-fix/releases)
Still does'nt work though

I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?

erik2041999 said:
I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?
Click to expand...
Click to collapse
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?

Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.

erik2041999 said:
Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.
Click to expand...
Click to collapse
Excellent, I will try asap. Thanks for all help!!

eddy92 said:
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?
Click to expand...
Click to collapse
If you're on a custom ROM you may need to use MHPC to spoof a valid device profile.

I had the same problem here, I managed to solve it by installing Magisk delta and Universal SafetyNet modded.