Develop Bugs

Safety net passes but Google pay doesn't work?

Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?

zee24 said:
Hey guys. So I have the latest magisk beta v19 and latest magisk manager. My safety net is passing but Google pay doesn't work. Did the new March update make it detect unlocked bootloader? My bootloader is unlocked with TWRP installed. Has anyone tested with and without TWRP installed?
Click to expand...
Click to collapse
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.

SageWilliams said:
Works for me but I had to make sure to hide the needed apps in MagiskHide (GPay, G Play Services, Framework) and even then, it required me to clear data in Pay, Services > then reboot > then proceed to add a card.
Also check to make sure that auto updates are not on for Google Pay. I think the version matters. My version is currently 2.84.237487748.
Click to expand...
Click to collapse
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this

zee24 said:
Wow so idk which one of the things you said did it but it worked, I downgraded my app, but I didn't have Google framework hidden from magisk so I did that I cleared the data and then rebooted that worked! Thanks so much and anyone else who's having this issue try this
Click to expand...
Click to collapse
Great, I will say its hit or miss sometimes. Mine worked in stores for a few days, then stopped saying I was rooted so I had to redo the method to get it back.

This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .

prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Great. Finally a fix. All like above but used Magisk 19.0. Thanks. I hope we're able to keep finding fixes like this. Google pay is a convenience.

According to this, it is to be expected on Pixel devices, vs others.
Advantages:
If you will see the list of the advantages and the list is too long of the magisk. This is the best Android application which you can use on your device. Let’s take a dive in the advantages of the Magisk.
You can use Financial/Banking applications.
You can use Snapchat without any issues.
You can also play Pokemon Go on your rooted Android device.
You can install OTA updates on your device.
You can also install System-less Xposed framework on your lollipop and marshmallow devices.
You can use Android Pay.
You can also bypass SafetyNet.
You might Face issues in:
Google Pixel and Google Pixel XL devices. The work is in progress, and we are working on i.
Magisk Manager cannot be placed in adaptable storage, or superuser will not work
MagiskSU does not support multi-user, and we are working on it to make multi-user support.
MagiskSU does not work on Android O preview, and we are working on it.
Click to expand...
Click to collapse
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com

Droid_Nut said:
According to this, it is to be expected on Pixel devices, vs others.
https://******************/
Since when are we not allowed to post links? Go to: magiskmanager dot com
Click to expand...
Click to collapse
Ever since that site was verified to be a fake.
https://www.google.com/amp/s/www.xd...kmanager-com-not-official-website-magisk/amp/

prot- said:
This is the fix
Magisk stable build, all latest official builds of everything else, nothing special. and Magisk hide on google play store, google play services and google pay then - Renaming com.google.android.gms to com.google.android.gms.bak (found in Data/Data) in root browser and then rebooting is the answer .
Click to expand...
Click to collapse
Thanks so much dude....much appreciated

Safety Net starts passing on rooted phone

I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.

The new update of EdXposed in the Magisk Manager passes SN, nothing new.

But John Wu (Magisk developer) said there was no way for hardware attestation on unlocked devices. Any software hiding will not work. That what he said.

QkiZMR said:
I don't know what happen but SafetyNet starts passing. I have rooted Moto Z3 Play, unlocked bootloader, Magisk 20.4, EdXposed 91.0 (YAHFA v0.4.6.4, updated today), a few Magisk, and EdXposed modules. Before hardware SafetyNet checks I could pay by phone. After Google forcing SafetyNet hardware attestation I could not. I accepted it because I was more concerned with control than with the possibility of paying by phone in the store.
Today morning I updated Riru - EdXposed (YAHFA) module in Magisk Manager. Then reboot. During the day I rebooted the phone once again. In the evening I ran Google Play Store to update my apps. I was surprised that Play was updating Netflix. Normally I updated it manually by downloading the apk file. Then I was testing Safety Net with Magisk, SafetyNet attest and SafetyNet test - all green. I was able to add a card to GPay. Even "attest" records in dg.db has 0, without blocking write mode. Here some screenshots.
Click to expand...
Click to collapse
Will gpay work, can you pay in shops?
Sent from my BASIC using Tapatalk

I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet ?
I think that is working because evaluation type is basic.

QkiZMR said:
I added card successfully to gpay. I suppose that it will be working but I need to check. I wasn't in shop yet [emoji846]
I think that is working because evaluation type is basic.
Click to expand...
Click to collapse
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Sent from my BASIC using Tapatalk

Al765436 said:
When you're in the gpay app and you turn on nfc, does it say-hold to reader?
Click to expand...
Click to collapse
Text in Polish, but it means "move closer to the reader".

QkiZMR said:
Text in Polish, but it means "move closer to the reader".
Click to expand...
Click to collapse
Yes that means it should be working, thx
Sent from my BASIC using Tapatalk

Al765436 said:
Yes that means it should be working, thx
Click to expand...
Click to collapse
I confirm payments works fine.

QkiZMR said:
I don't know what happen but SafetyNet starts passing.
Click to expand...
Click to collapse
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.

serajr said:
I second you mate ( see it here ) :good:
Hardware attestation hack to basic attestation is needed, I gotta say.
Click to expand...
Click to collapse
I know. I said it in my third post. The best thing is that I not needed to clear any google play/google services data. It just began working ?

Device uncertified after Magisk root on latest factory Android 11

Hi all,
Got a new phone and finally decided to see if I could root the old Pixel 2 XL. It's unlocked, bought directly from Google. Never before unlocked bootloader until now.
It was flashed to factory Android 11 2020-12, and rooted from there. Magisk 21.1 beta was installed from zip while booted into TWRP 3.0.4, as advised in this thread. The latest Play System Update (Oct 5, 2020) was automatically installed while I was messing around afterwords.
I confirmed root access thru a checker and Termux, which is pretty neat! Hadn't rooted a device in a long time!
Unfortunately, device certification fails in Play Store, Magisk SafetyNet check and being unable to add a credit card to Google Pay. Magisk says basicIntegrity passes, but CTSprofile fails.
Things I've tried, mostly from this exhaustive guide:
Hidden Magisk Manager
Enabled MagiskHide, rebooted
Remove Magisk zip from storage
Lock bootloader again, rebooted
Clear app storage for Play store and Play services, rebooted
Disable USB debugging
Disable Play Protect scanning
Looked over XDA boards, Magisk changelog/documentation/guides
Things I haven't done (yet?):
Spoofing device fingerprint. I wouldn't expect this to be necessary, since it's actually authentic! But maybe there's more to it that I don't understand?
Start over from scratch, with Magisk Canary build - doesn't appear to be any improvements to MagiskHide according in current release notes
Is this possible to achieve?

composition said:
Is this possible to achieve?
Click to expand...
Click to collapse
SafetyNet:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Google I believe is using hardware-backed CTS profiling, which Magisk cannot circumvent. Your only chance of passing CTS is to hope Google ISN'T using the hardware-backed version, so you can employ one of the workarounds I gave in the link above.

There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.

Larzzzz82 said:
There is a setting in magisk manager that let's you switch the attestation check. I'm having a brain fart as to where it is atm but I'll poke around and if/when I find it, I'll reply again.
Click to expand...
Click to collapse
Apparently we're both having brain farts. I didn't even think there was such a setting. Then again, I don't use Google Pay.

Question Banking apps on rooted Pixel 6/Pro?

Hello everyone,
I haven't unlocked my P6P's bootloader or rooted yet, but have read that banking apps won't work after rooting/unlocking the bootloader.
Does anybody use Monzo and can confirm the app doesn't work? Also, do you think they'll find a solution to this issue any soon?
Thanks a lot!

Monzo won't work if device is rooted. Magisk used to have the Hide feature but I'm not sure if it's still working as I no longer root.
Many apps like banks or GPay also won't work if SafetyNet is tripped, again something MagiskHide used to be able to mask.

Yes all working here gpay, Banking apps and so on. Just use the guide for rooted and safety net pass here on xda. And additional do one thing:
Install Airfrozen app from Playstore,
Freeze magisk app in Airfrozen that's it all will work, if you need root just unfreeze it again use your root stuff and freeze again

All banking apps working for me...rooted.. without safetynet fix...

This is not Pixel 2 forum lol

Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
I mean if you read the contents of the post you'd know he was talking about the pixel 6 pro lol

Nekromantik said:
This is not Pixel 2 forum lol
Click to expand...
Click to collapse
Thanks for heads up! Just fixed the title
And thanks everyone else for your replies! Good to know it's still possible to use banking apps, though with some tweaks.

This guide has all you need: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/
Basically as long as you hide the Magisk app, and use the USNF module (latest Zygisk version is available for free now), you should be golden with most banking apps - just add them to the exception list.

anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF

dimm0k said:
anyone able to get fingerprint working with the Chase and Amex apps? both of these were fine, but now they won't let me unlock with fingerprint. running the latest Canary with 2.2 USNF
Click to expand...
Click to collapse
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.

eg1122 said:
I got chase working fine. I made sure chase was in deny list then cleared chase data/cache. Reboot. I uninstalled magisk app then was able to get fp to work. Even works after I installed Magisk app again.
Click to expand...
Click to collapse
when you added the Chase app to the deny list, did you select both entries under it or just the default one?

dimm0k said:
when you added the Chase app to the deny list, did you select both entries under it or just the default one?
Click to expand...
Click to collapse
Both

I didn't have to deny a single thing for GPay or Chase.
Install Magisk alpha. Enable zygisk. Install newest zygisk-based Universal SafetyNet Fix. Confirm that YASNAC shows you passing. Done.
There's no need to do exotic stuff but it's best to do this before ever trying your apps to avoid having to clear their storage.

Monzo does work on a rooted device. Starling doe not.

How To Guide EASIEST method to unblock McDonalds app and many more

Hello everyone, after a long time of not being able to figure out on how to make the McDonalds app work on a magisk rooted phone with twrp + custom rom. I finally managed to do it.
I want to share my method with you, hopefully it will work for everyone.
At first, install the McDonalds app (If not already done).
1. Install app manager from play store
2. Force stop + clear cache
3. In magisk, enable magiskhide and follow the steps.
4. In the new magisk app. Select Systemless hosts
5. Also, enable denylist and add McDonalds to it.
6. Install Universal Safetynet Fix by kdrag0n from github.
7. After installing, the apps should work.
Good luck!

which version of magisk?

I don't know exactly, I am using the latest version. Should work on most versions that includes MagiskHide

kyanbarth330 said:
I don't know exactly, I am using the latest version. Should work on most versions that includes MagiskHide
Click to expand...
Click to collapse
Open magisk and it will shiw you what version you have

I'm using 25.2

can you show screen shot of your magisk and the magisk hide function, it is not in mine. i usually use magisk delta which does have magisk hide in it

Or just use the browser when ordering.

It still doesn't work I think they detect an unlocked bootloader even if you don't have root

I saw a module in Lposed that blocks root in the macdonalds app.
Thread '[MOD][XPOSED][4.1+] McRoot (McDonalds Global App)' https://forum.xda-developers.com/t/mod-xposed-4-1-mcroot-mcdonalds-global-app.4265069/

Hey, thanks for the "tutorial"! Kinda surprised that it works even on banking apps or it could be another thing that i tried before.
Edit: I think that you need LSPosed + Hide My Applist for the banking apps