I'm almost done setting up my new RedMagic 8, and I have a couple of issues:
Disney+ won't install. This might be because I'm rooted, but I've installed Universal Safetynet fix, and I'm supposedly passing.
Gpay isn't working for me. This is _probably_ a rooting issue, but I'm confused because, again, I'm passing safetynet.
I'd probably chalk this all up to being rooted, but my old phone (OnePlus 7 Pro) is rooted, and I can use both of these apps on there. I've read about MagiskHide Props Config, and it warns that device simulation should only be done if you have to, but I'm starting to wonder if there's any other way to get these apps running.
Have you tried installing Shamiko?
I've never heard of that before, but I've installed it now. So far there isn't any difference. Do you know how it's different from Magisk enforcing the hide list?
jfsat said:
I've never heard of that before, but I've installed it now. So far there isn't any difference. Do you know how it's different from Magisk enforcing the hide list?
Click to expand...
Click to collapse
To get Google Pay/Wallet working, I used Universal SafetyNet Fix by kdrag0n and did the usual under Magisk settings -
Enable Zygisk
Enable Enforce DenyList
Configure DenyList -> Add your Google Pay/Wallet here
yoonhx said:
To get Google Pay/Wallet working, I used Universal SafetyNet Fix by kdrag0n and did the usual under Magisk settings -
Enable Zygisk
Enable Enforce DenyList
Configure DenyList -> Add your Google Pay/Wallet here
Click to expand...
Click to collapse
That worked on my old phone (OnePlus 7 Pro), but not my new phone (RedMagic 8 Pro).
I swear, it's getting harder and harder to be a rooted user. I just want to use Adaway! Why is that so much to ask?!
Related
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.
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.
Hi, I'm trying to run Google Pay on my OnePlus with Lineage 18.1 + MicroG. I passed the SafetyNet, but Gpay still doesn't work. I added my Google account in the MicroG settings and hid root from Gpay in the Magisk's DenyList
My banking app also gives me issues. Can't use NFC payment because it detects root. It was the same on my previous Realme X2 Pro and I wask never able to solve it. Magisk hide, then later denylist; safetynet passes, but nothing. If someone finds a solution that would be great.
I'm on OOS 11 though.
Arcide said:
My banking app also gives me issues. Can't use NFC payment because it detects root. It was the same on my previous Realme X2 Pro and I wask never able to solve it. Magisk hide, then later denylist; safetynet passes, but nothing. If someone finds a solution that would be great.
I'm on OOS 11 though.
Click to expand...
Click to collapse
Denylist works great for me, all bank apps didn't detect anything. Are you sure that you selected all activities corresponding to your bank app and enabled enforcement?
happyrage said:
Denylist works great for me, all bank apps didn't detect anything. Are you sure that you selected all activities corresponding to your bank app and enabled enforcement?
Click to expand...
Click to collapse
No sadly it doesn't work, and there's only one process that is shown. This app is a real f***ing piece of work.
I managed to get my Gpay up and running on Lineage. I can't exactly open the app, but I can access GPay to add a card via Settings. Youtube video to explain below.
Hi,
after bricked my device, I wipe, reinstalled new on July patch and root.
All is working but not the certified in Play Store.
SafetyNet is passes.
Male a new fingerprint with props and the OS isn't loading.
Anyone has an idea?
Hi,
try redoing a fingerprint, reboot. Have had this problem myself and that solved it.
Leave it for a few days, normally it will be certified back after 2 days
Close the Play Store and clear the app data/cache and it'll fix the certification.
You shouldn't have to do anything to the fingerprint to pass.
Latest Magisk (25.1)
Universal SafetyNet Fix 2.3.1
DenyList enabled on Google Play Store
This is on a Pixel 5, but it shouldn't make any difference. SafetyNet passes, and device is Play Certified.
Spoiler: Screenshots
This is old story - Please clean google play store data and cache and then reopen google play store to make it download necessary files to certify again and then it will pass certification.
Not an old story, there's much discussion on the release of a new "aggressive" API that passes safteynet but failed other, stronger tests that Netflix and Gpay use to detect root. So far, I have not seen anyone overcome it on P6P without changing fingerprint.
rhetorician said:
Not an old story, there's much discussion on the release of a new "aggressive" API that passes safteynet but failed other, stronger tests that Netflix and Gpay use to detect root. So far, I have not seen anyone overcome it on P6P without changing fingerprint.
Click to expand...
Click to collapse
I've had no problem with Magisk zygisk and UNSF 2.3.1 with Google pay/wallet and netflix. Google play has always shown my P6P as certified.
Go to the GitHub page and look at the discussion posted on this issue. If you're able to use GPay on the July firmware with updated Google services, then you appear to be in the minority.
New Google Integrity API update breaks universal safetynet fix · Issue #203 · kdrag0n/safetynet-fix
New Google Integrity API update breaks universal safetynet fix Describe the bug Google Play device is certified. YASNAC safety net passes. Google Pay is now Google Wallet which detects device as ro...
github.com
I am also running July firmware on a rooted P6P, can use GPay and PlayStore says its certified. I've applied all updates, Play Store says it's up to date at v31.6.13-21.
YASNAC passes. Magisk 25.2, Shamiko for Denylist enforcement. Play Store, GPay, and Netflix on denylist.
A modified safetynet fix should fix this problem. Make sure to clear data from google play services. Goodluck.
wanttotree said:
A modified safetynet fix should fix this problem. Make sure to clear data from google play services. Goodluck.
Click to expand...
Click to collapse
Where did you get this from? The official USNF file has only reached V2.3.1.
@Lughnasadh Ahh, thanks for the clarification. I appreciate it =).
NippleSauce said:
Where did you get this from? The official USNF file has only reached V2.3.1.
Click to expand...
Click to collapse
That's from Displax. He actually updated the mod but also lowered the version number so it would coincide with kdragons. So the latest, updated version of Displax's mod is 2.3.1, not 2.3.2.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
I apologize for not crediting Displax.
Seems I am doing something wrong, play store certification status of the devices will still stay on "not certified".
Pixel 5, lineageos 20 freshly installed, magisk (zygisk enabled, enforce deny list, play store + play services fully checked), Displax' USNF v.2.4.0-Mod_1.2 installed, wiped data+cache from play store + play services, Google Services Framework ID registered. Safetynet basic integrity + CTS profile match passed.
Any idea?
ssdnvv said:
Seems I am doing something wrong.
Pixel 5, lineageos 20 freshly installed, magisk (zygisk enabled, enforce deny list, play store + play services fully checked), Displax' USNF v.2.4.0-Mod_1.2 installed, wiped data+cache from play store + play services, Google Services Framework ID registered.
Any idea?
Click to expand...
Click to collapse
You need to install Shamiko to hide su binary (disabling enforce deny list) and check Play Integrity, SafetyNet is depracated: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck
swer45 said:
You need to install Shamiko to hide su binary (disabling enforce deny list) and check Play Integrity, SafetyNet is depracated: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck
Click to expand...
Click to collapse
Thanks for your quick answer, but still not certified. Does this "let the device wait for some time"-idea help?
ssdnvv said:
Thanks for your quick answer, but still not certified. Does this "let the device wait for some time"-idea help?
Click to expand...
Click to collapse
Oh, you are using Lineage, I don't like it because doesn't include any patch of this. Try this module: https://github.com/Magisk-Modules-Alt-Repo/sensitive_props/releases/latest
But I recommend you to use another ROM, Lineage is for testing purposes.
ssdnvv said:
play store + play services fully checked
Click to expand...
Click to collapse
wipe the app data of Play Store and force stop it. another option would be flashing the 'Universal SafetyNet Fix' as Magisk module.
Seems shamiko does anyways not bypass CTS on lineageos which I'd like to keep - used to it for several years by now ;-). Or can you recommend another AOSP android 13 ROM, that is still well maintained?
Displax' Universal SafetyNet Fix mod is working in combination with deny list to pass safetyNet but not Playstore integrity check.
The sensitive_props module doesn't seem to change the situation. I just freshly reinstalled and only logged in into google account and entered playstore after YASNAC showed both checks passed.
edit: for the record - I just had to wait roughly two days and the certification was shown in playstore. But even with this not all apps run fine - Microsoft Intune / Teams for accessing company networks for example refuse to connect (yet can be installed, so this seems to be some security initiative from M$).
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Vattu said:
Just install safetynet-fix-v2.3.1-MOD.zip in Magisk. That worked on my OnePlus Nord CE (EU).
Click to expand...
Click to collapse
Yeah this thread is now out of date. The updated safetynet fix is a much better option now.
You don't need just the safetynet module. You need Shamiko along that.
So latest Safetynet + Shamiko 0.5.2 (the latest version right now) and you're all set. You gotta whitelist the banking apps you use and they'll work perfectly fine. These 2 were enough to allow my preferred ridiculous banking app to work without an issue, without any other modules or tweaking and such.
dragos281993 said:
You don't need just the safetynet module. You need Shamiko along that.
Click to expand...
Click to collapse
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
aurny said:
You only need Shamiko if you use LSposed, right? I don't use LSposed and it's been enough for me to put all of my annoying apps on the Magisk denylist.
Click to expand...
Click to collapse
No. I only had Magisk installed with Zygisk turned on. I first installed Safetynet Fix then Shamiko. The first module wasn't enough for my preffered banking app to not detect that the bootloader was unlocked. Shamiko fixed that. I simply installed it as a module in Magisk
Thanks, good to know. I haven't had that issue yet but I'll remember this in case I need it in the future!
aurny said:
If you rooted using the method on this forum, and your Google Pay app was recently upgraded to Google Wallet, you will probably find that it doesn't work anymore. Even if you have the Universal SafetyNet Fix installed and SafetyNet shows as passing, the new payment app will still detect your device as rooted. This is because it now uses Google Play Integrity instead of SafetyNet.
There's a lot of discussion in this thread. But the short version is, if you want to get payments working again:
1. Install MagiskHide Props Config.
2. Follow the instructions on that page to change your device fingerprint to Samsung Galaxy S21 (A11).
That's it! Some people in the thread also cleared data for Google Play Services but I don't think I did. Also in that thread is a verification app (first version, official version) for Google Play Integrity that you can use to make sure your device fingerprint setting is correct.
So far I haven't noticed any side effects from changing the fingerprint. I was unable to receive any SMS messages after first changing, but I rebooted a second time and that issue went away.
Click to expand...
Click to collapse
Thank you very much, it worked perfectly.
This actually worked, thank you!