MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0

Search This thread
By:
Advanced…
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,867
2,452
V0latyle said:
Hulu isn't available: "This app is not compatible with your device"
Click to expand...
Click to collapse
Is it possible that the device is identified something other than Pixel5a and the app is not compatible with that specific device.
I have seen people complain that with the SNF sometimes Three device is recognized as Nexus or something really old.
Somehow it does not happen to all.
Check your device at Google and see if it sees it correctly?
Perhaps uninstall SNF, reboot, and reinstall.
Just an idea.

Update, somehow I missed the last few responses,
All good then
 
  • Like
Reactions: V0latyle
P

pndwal

Senior Member
Jun 23, 2016
5,899
6,498
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
V0latyle said:
Settings > Apps > Google Play Protect Service
Click to expand...
Click to collapse
That's interesting... I've never seen this... I get:
IMG_20221122_135746.jpg

IMG_20221122_141439.jpg

IMG_20221122_140830.jpg

but don't appear to have Google Play Protect Service app... 🤔

What Play Store version do you have? PW
 
Last edited:
zgfg

zgfg

Senior Member
Oct 10, 2016
8,550
6,278
Xiaomi Mi 11 Lite 5G
casouzaj said:
All Apps > 3 dots > Show System
Click to expand...
Click to collapse
Xiaomi, A12

I have five apps and services containing the word Play in the name (including system ones - otherwise Google Play Services will not show), but none with the name Google Play Protect Service - screenshot(s)

And I've never seen that one

Please provide its package name?

However, I've found something about:
www.xda-developers.com

Google publishes Play Protect as separate app for quicker updates

Google is de-coupling its Play Protect service from Google Play Services, as evidenced by a new Play Store listing. Read more about it here.
www.xda-developers.com www.xda-developers.com

and accordingly, the package name seems should be:
com.google.android.odad

but I don't have a package with that name installed

Actually, I've searched in the Terminal emulator for all similar packages by:
su
pm list packages -f | grep protect
pm list packages -f | grep play
pm list packages -f | grep services
pm list packages -f | grep odad
...

and it finds Google Play Store app, Google Play Services app, etc, but nothing like Google Play Protect Services

Btw, do you happen to have Pixel (and maybe Android 13)?

PS: Google Play Protect Service can be found on ApkMirror
 

Attachments

  • Screenshot_2022-11-22-06-38-36-992_com.miui.securitycenter-edit.jpg
    Screenshot_2022-11-22-06-38-36-992_com.miui.securitycenter-edit.jpg
    297.3 KB · Views: 93
  • Screenshot_2022-11-22-07-26-24-035_sarangal.packagemanager-edit.jpg
    Screenshot_2022-11-22-07-26-24-035_sarangal.packagemanager-edit.jpg
    194.4 KB · Views: 93
Last edited:
  • Like
Reactions: ipdev, pndwal and 73sydney
P

pndwal

Senior Member
Jun 23, 2016
5,899
6,498
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
zgfg said:
Xiaomi, A12

I have five apps and services containing the word Play in the name (including system ones - otherwise Google Play Services will not show), but none with the name Google Play Protect Service - screenshot(s)

And I've never seen that one

Please provide its package name?

However, I've found something about:
www.xda-developers.com

Google publishes Play Protect as separate app for quicker updates

Google is de-coupling its Play Protect service from Google Play Services, as evidenced by a new Play Store listing. Read more about it here.
www.xda-developers.com www.xda-developers.com

and accordingly, the package name seems should be:
com.google.android.odad

but I don't have a package with that name installed

Actually, I've searched in the Terminal emulator for all similar packages by:
su
pm list packages -f | grep protect
pm list packages -f | grep play
pm list packages -f | grep services
pm list packages -f | grep odad
...

and it finds Google Play Store app, Google Play Services app, etc, but nothing like Google Play Protect Services

Btw, do you happen to have Pixel (and maybe Android 13)?

PS: Google Play Protect Service can be found on ApkMirror
Click to expand...
Click to collapse
Good share! 👍

The XDA article indicates it's still rolling out seperated Google Play Protect Service and reportedly it has only hit A12+ devices to date (I have only A10 + A11 devices at present)... It'll be one to watch...

Old integrated Play Protect seems to be still using S/N API... I'm wondering if Play Protect calls new PI deviceIntegrity for device certification... If so, I'm guessing (as I've indicated previously) Google will probably wait for banks to pre-empt any move to strongIntegrity...

No doubt if this service does use PI API, both the Device intgrity and the additional available PI payload responses (Application integrity and Account details) will be useful in combination with scans for harmful software / malware... Nb. The additional responses were a major reason for overhauling the original S/N API... PW
 
  • Like
Reactions: 73sydney and ipdev
C

cbomb1337

Senior Member
Jan 22, 2019
250
68
melbourne
Samsung Galaxy Tab S7 / S7 Plus
Google Pixel 6
pp085ster said:
Been having this issue since day 1 on my Pixel 7 trying to have root and contactless working side by side. Whenever I flash the USNF MOD 2.0 via Magisk, I gain the ability to pass 2/3 integrity checks, however I lose the ability to enter my Google settings page (clicking on settings -> Google does nothing), and GPay stops working altogether - cannot access the "wallet" section. I have tried flashing USNF MOD 2.0 then going into airplane mode, clearing cache for Google Play Services, Google Play Store and GPay, rebooting and deactivating airplane mode.
This also hasn't worked. Does anyone have any idea as to what is going on here? It looks like some conflict with a Google service, but have no idea how to troubleshoot it.
Thanks in advance!
Click to expand...
Click to collapse
I get a weird issue like that when installing the universal safetynet fix I lose my google wallet and it reverts to gpay. I wonder why. I'm using Pixel 6 I have yet to test if the tap and go g pay if it works ill try it today.
 
P

pndwal

Senior Member
Jun 23, 2016
5,899
6,498
Sydney
Redmi Note 8
Xiaomi Redmi Note 8 (2021)
pp085ster said:
Been having this issue since day 1 on my Pixel 7 trying to have root and contactless working side by side. Whenever I flash the USNF MOD 2.0 via Magisk, I gain the ability to pass 2/3 integrity checks, however I lose the ability to enter my Google settings page (clicking on settings -> Google does nothing), and GPay stops working altogether - cannot access the "wallet" section. I have tried flashing USNF MOD 2.0 then going into airplane mode, clearing cache for Google Play Services, Google Play Store and GPay, rebooting and deactivating airplane mode.
This also hasn't worked. Does anyone have any idea as to what is going on here? It looks like some conflict with a Google service, but have no idea how to troubleshoot it.
Thanks in advance!
Click to expand...
Click to collapse
Looks like your enquiry may have fallen through the cracks here... Sorry!

Did you get it sorted?

Nb. Clearing cache is usually not enough for such a scenario... always clear data, or do so if cache clearing fails...

Clear data for the three apps you mentioned (but may incl. Google Wallet now instead of Google Pay) and reboot before first trying G Play/Wallet again (nb. rebooting first is critical or you may have persistent issues w/ Activity list/other later)...

I put details on this here:
https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-87481637

If this doesn't help it may be a P7 or P7 series / A13 launch version specific issue with latest prop mismatch based hardware verdict enforcement bypass added in @Displax's USNF mod 2... I haven't seen such an issue mentioned, but users / OP in this thread will likely have the best advice:
https://forum.xda-developers.com/t/unlock-bootloader-root-pixel-7-pro-cheetah-safetynet.4502805/

🤠 PW
 
pp085ster

pp085ster

Senior Member
Sep 5, 2010
355
103
Santa Cruz
Google Pixel 7
pndwal said:
Looks like your enquiry may have fallen through the cracks here... Sorry!

Did you get it sorted?

Nb. Clearing cache is usually not enough for such a scenario... always clear data, or do so if cache clearing fails...

Clear data for the three apps you mentioned (but may incl. Google Wallet now instead of Google Pay) and reboot before first trying G Play/Wallet again (nb. rebooting first is critical or you may have persistent issues w/ Activity list/other later)...

I put details on this here:
https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-87481637

If this doesn't help it may be a P7 or P7 series / A13 launch version specific issue with latest prop mismatch based hardware verdict enforcement bypass added in @Displax's USNF mod 2... I haven't seen such an issue mentioned, but users / OP in this thread will likely have the best advice:
https://forum.xda-developers.com/t/unlock-bootloader-root-pixel-7-pro-cheetah-safetynet.4502805/

🤠 PW
Click to expand...
Click to collapse
Issue turned out to be due to a custom font I was using. Here's what ended up working for me to be able to continue using a custom font as well as get gpay working simultaneously. Thanks!
 
  • Like
Reactions: 73sydney and pndwal
7

73sydney

Senior Member
Jul 21, 2018
3,056
3,226
Sydney
Google Pixel 6 Pro
Samsung Galaxy Watch 4
cbomb1337 said:
I noticed the safety net modules seem to make my play services use alot more cpu is that normal. I tested it by removing the module and clearing play services data and it fixed it.
Click to expand...
Click to collapse
i dont see that here, Pixel 6 Pro

had you tested and were you passing Integrity Test

because i could see if you hadnt and play services was banging around in the background failing that *might* explain it - if that were true, id do the perennial advice...put the device in airplane mode, clear data for Google Play Services and Store, reboot, toggle airplane mode off and test again
 
  • Like
Reactions: pndwal
C

cbomb1337

Senior Member
Jan 22, 2019
250
68
melbourne
Samsung Galaxy Tab S7 / S7 Plus
Google Pixel 6
After testing for a week this module by displax and husky dg on my p6 it eats my battery up. Google play services gms goes crazy. It sometimes stops draining when I was tinkering with components of the app but ended up going back to draining heavy I remove module and draining stops. I reflashed rom and flashed module and drain comes back. It also removed my google wallet and brings gpay app back. Not sure if it works I tried it days ago using zip pay and it worked and tried my bank card yesterday and it failed.
 
Last edited:
You must log in or register to reply here.

Similar threads

Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
apb_axel
[ZIP] Synapse + Script => Universal Kernel Manager v3.8.1
Replies
3K
Views
766K
D
Dildoman
repey6
[6.0-12.0][Magisk]Dolby Digital Plus[upd.20211005]
Replies
2K
Views
737K
B
b4minee
Chainfire
[2014.05.01][ROOT] Mobile ODIN v4.20
Replies
5K
Views
3M
Zagnutty
Zagnutty
DooMLoRD
[04/Jan][ROOTING/UNROOTING] DooMLoRD's Easy Rooting Toolkit [v4.0](zergRush Exploit)
Replies
927
Views
3M
B
bishoy ashraf

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    P
    pndwal
    For those using Canary builds

    Please be aware that in 25207+ major refactoring (of selinux rule patching) has broken many modules etc... This is likely the cause of issues with hiding using recent builds as Shamiko is affected... Please see discussion in Magisk Discussion thread...

    You could revert to 25206 or wait for fixes hopefully in 25211... 👀 PW
    View
    3
    jasonbiggs
    jasonbiggs
    zgfg said:
    With Integrity and CTS do you refer to the deprecated SafetyNet or the 'new' Play Integrity API?

    Also, are you using USNF from this thread or the newer/better safetynet-fix-v2.4.0-MOD_1.2 from the other thread?

    Look into the other USNF thread from Displax and find more info in the thread about GPay

    Btw, banking apps do not rely only on PI API - they try many other detections od root, hence you might need (things vary from app to app) Shamiko, Hide My Applist or even the Magisk Delta fork

    The best would be to search through the Magisk related threads here on XDA, how the other user(s) solved the root detection from your particular banking or similar app
    Click to expand...
    Click to collapse
    Yes! I was trying to find the link for that mod. This worked. Thanks!

    View
    3
    P
    pndwal
    nate911 said:
    Yes. Device and basic passes.

    I use the phone for 2 hrs

    I run the checker again and device and basic integrity fails.

    Reboot. It then starts passing again

    Edit: restarting gms fixes it too.

    Thanks @pndwal
    Click to expand...
    Click to collapse
    Ok, so NOT intermittently passing only basicIntegrity verdict...

    Sounds like the same issues w/ official 2.4.0... Are you sure you actually have v2.4.0-MOD_1.2 @Displax build?

    If so, please say device/ROM... Also, suggest reverting to v2.3.1-MOD_3.0... There may possibly still be issues with 2.4.0 builds... Please report your mileage with that if you do... PW
    View
    3
    zgfg
    zgfg
    jasonbiggs said:
    so I'm on android 13, pixel 6a. Got Integrity ✅ and CTS match ✅ and also Play Store as Certified. Although, still no google pay or banks access. Any hints to get this working or it this fix not fully functional on 13 as of yet?

    Thanks!
    Click to expand...
    Click to collapse
    With Integrity and CTS do you refer to the deprecated SafetyNet or the 'new' Play Integrity API?

    Also, are you using USNF from this thread or the newer/better safetynet-fix-v2.4.0-MOD_1.2 from the other thread?

    Look into the other USNF thread from Displax and find more info in the thread about GPay

    Btw, banking apps do not rely only on PI API - they try many other detections od root, hence you might need (things vary from app to app) Shamiko, Hide My Applist or even the Magisk Delta fork

    The best would be to search through the Magisk related threads here on XDA, how the other user(s) solved the root detection from your particular banking or similar app
    View
    3
    osm0sis
    osm0sis
    I was on 2.3.1_MOD_3.0 on Android 12 and now 2.4.0_MOD_1.2 on Android 13 and all was now well in both setups.
    View
  • 315
    kdrag0n
    kdrag0n
    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 profile attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.

    If you still have trouble passing SafetyNet with this module, use MagiskHide Props Config to spoof a certified device profile. This is a common issue on old devices, custom ROMs, and stock ROMs without GMS certification (e.g. Chinese ROMs).

    Android versions up to 13 Beta 3 are supported, including OEM skins such as Samsung One UI and MIUI.

    How does it work?
    The way this workaround works is relatively low-level. An in-depth explanation, as well as source code and ROM changes, can be found on GitHub.

    Ideally, this workaround should be incorporated in custom ROMs instead of injecting code with a Magisk module. See the ProtonAOSP website for more information.

    Downloads
    Downloads and changelogs can be found on GitHub. The topmost release is the latest.

    Latest release
    v2.4.0
    Highlights
    • Play Integrity bypass without breaking device checks or causing other issues
    • Disabled use of hardware attestation on Pixel 7 and newer (@anirudhgupta109)
    Other changes
    • Updated instructions for newer Android and Magisk versions
    • Better debugging for future development
    This version only supports Zygisk (Magisk 24 and newer).

    It's taken a while to find a way to bypass Play Integrity that doesn't require spoofing the build fingerprint permanently, but I wanted to make sure this module doesn't cause any unnecessary breakage. Just like the original goal of Universal SafetyNet Fix, this minimizes adverse effects by spoofing dynamically at runtime only when necessary. Enjoy!

    If you found this helpful, please consider supporting development with a recurring donation for rewards such as early access to updates, exclusive behind-the-scenes development news, and priority support.
    Alternatively, you can also buy me a coffee. All support is appreciated ❤️

    Source code
    View
    213
    Displax
    Displax
    So, here is my modification of USNF with Play Integrity API bypass.

    It changes fingerprint to old 7.1.2 6.0 (LOL) and apply it only for GMS SafetyNet process (by Zygisk injection), so your original prints/security path level does not change. This avoids many side effects/problems with global props changing.

    Updated 3.0:
    No words needed, you understand everything yourself 😜

    Updated 2.1:
    Hide "Enable OEM Unlock" setting

    Updated 2.0:
    Bypassing DEVICE_INTEGRITY for devices that shipped with Android 13+ (Pixel`s 7 )

    Updated:
    Drop fingerprint to lowest possible (6.0) to ensure that no one use same Android version

    Usage:
    1. Delete/disable/reset MagiskHidePropsConfig (if installed).
    2. Just install it over old Universal SafetyNet Fix and reboot device.
    3. You may be needed to wipe GMS data (not cache) if there is no result immediately.

    Many thanks to @1nikolas for integrity checker.

    Source code: https://github.com/Displax/safetynet-fix/tree/integrity
    View
    58
    Displax
    Displax
    So, here is my new modification of USNF with Play Integrity API bypass.

    It is now based on top of original v2.4.0 codebase instead of v2.3.1, with adding new hiding algorithm for current realities and some code refreshing.

    Changelog:

    Version 1.2
    * Fix crash and endless tests loop/failing on Android < 9.0 (bug from original version 2.4.0).
    * Do not unpatch (revert) changes. To prevent possible tests failing after a while on some ROMs (cross conflicts).

    Version 1.1
    * Fix KeyStore hook desynchronization (tests randomly failing problem).


    Usage:
    1. Delete/disable/reset MagiskHidePropsConfig (if installed).
    2. Just install it over old Universal SafetyNet Fix and reboot device.
    3. You may be needed to wipe GMS data (not cache) if there is no result immediately.

    Source code: https://github.com/Displax/safetynet-fix/tree/dev
    View
    31
    P
    pndwal
    Folks, the SafetyNet API was depreciated last Month with 'full turndown' slated for June 2024 and the introduction of the new Play Integrity API. It has also become clear that Google apps are simply the first to adopt the long foretold Play Integrity API; all responsible banks are bound to follow suit in short order, and at least before the June 2023 migration deadline.

    This means (assuming fully deployed Hardware Key Attestation doesn't come first 😬) that the need for a 'Universal Play Integrity Fix' has become quite urgent.

    We currently have workarounds involving using older fingerprint props by means of MHPC module (similar to fix needed for uncertified ROMs), but success/mileage varies per device and users of regular bank apps / gamers etc on stock devices will all soon be forced to experiment with MHPC prints also... This is hardly ideal.

    So I've made an issue report/request on USNF GitHub as follows. This information may be insightful to users here also...

    Please let me know here if I have missed anything important, or add any technically relevant details there...

    PLEASE DON'T spam that issue with unimportant details or queries... (The previous issue is already burgeoning w/ OT.) That's what this thread is for... 😛 :

    Please make 'Universal Play Integrity Fix' ... #204

    Fixes to expand 'Universal SafetyNet Fix' to become a 'Universal Play Integrity Fix' are needed.

    The SafetyNet Attestation API is deprecated and has been replaced by the Play Integrity API.
    https://developer.android.com/training/safetynet/deprecation-timeline

    New Play Integrity API is rolling out from June 2022, and evidently Google Play Store and Google Pay/Wallet are already using its verdict.

    June 2023 is the Migration Deadline for app developers. This will also allow their older app versions to continue working with SafetyNet API for a limited time.

    June 2024 is the End of life for SafetyNet API; its attestation will no longer work for any app version, and apps will receive an error.

    The new Integrity API has more strict requirements for passing attestation, and this seems to be enforced in Android 11+ particularly.

    Currently (evidently due to this), device security issues are detected by

    1. Google Pay/Wallet, which may state "You can't pay contactless with this device...(Your phone doesn't meet software standards)" on updating or attempting to add a card despite in-app Contactless setup stating "You're ready to pay contactless with your phone (Your phone meets security requirements)", and
    2. Google Play Store, which may no longer show apps like Netflix w/ Android 11+ (developers can 'exclude devices from their app's distribution based on their device integrity . Device exclusion is based on the latest device integrity verdict that the Play Store app receives from the Play Integrity API') despite in-app settings showing Play Protect 'Device is certified' result.
    I'm guessing that the 'passing' messages based on the old SafetyNet API are likely to realigned soon.

    A workaround that evidently allows Play Integrity API attestation to pass (and solve Wallet / Play Store issues also) has been discovered. It involves spoofing an earlier certified ROM, generally by using MagiskHide Props Config module to change fingerprint prop to one for Android 10 or earlier.

    Undoubtedly other apps will begin to detect broken TEE etc / fail as they migrate or begin integrating the Play Integrity API.

    A 'Universal Play Integrity Fix' will evidently require more understanding / research into how the fingerprint prop is used, and possibly other new behaviours.
    Click to expand...
    Click to collapse

    Here's hoping... 🙃 PW
    View
    29
    Displax
    Displax
    So, created separate thread for my mod. Welcome)

    [MODULE] [MOD] Universal SafetyNet Fix

    Universal SafetyNet Fix [MOD] Magisk module...
    forum.xda-developers.com forum.xda-developers.com
    View

New posts