MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0

Search This thread

Uzephi

Recognized Contributor
Apr 20, 2012
3,435
1,885
258
Phoenix
Google Pixel 3a
Hi, been trying to get this working correctly for the last few days with partial success.
Have Galaxy S5e tab with Android 10, user interface 2.5.
Magiskhide solves the basic pass.
Installed a number of recent builds including the latest to resolve cts profile fail.
Problem is I pass basic and cts and works fine as long as I don't set a screen lock. Once I put on a screen lock the tab reboots 5-6 times each time I reboot and and becomes unstable with occasional random reboots.
Have to set a lock due to organisation policy.
Any thoughts?
You're on a heavily OEM skinned OS. OneUI has the most modifications away from AOSP compared to almost all other OEMs. Heavily modified OEM skins like OneUI don't have full support as said in the readme and OP. Ymmv with those. Now if you ran LOS or another custom rom for your device, you might have better luck.

Edit: from OP: Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question. Please do not report problems on such ROMs.
 

Essentrix

Senior Member
Apr 4, 2013
864
175
63
You're on a heavily OEM skinned OS. OneUI has the most modifications compared to almost all other OEMs. Heavily modified OEM skins like OneUI don't have full support as said in the readme and OP. Ymmv with those. Now if you ran LOS or another custom rom for your device, you might have better luck.
Appreciate the quick reply mate and the great work you guys do. Also understood re LOS and support for OneUI. Just that I am so close to working fully... 😁
It was even stable for a while with 1.1.1 until reboot...
 

Uzephi

Recognized Contributor
Apr 20, 2012
3,435
1,885
258
Phoenix
Google Pixel 3a
Appreciate the quick reply mate and the great work you guys do. Also understood re LOS and support for OneUI. Just that I am so close to working fully... 😁
It was even stable for a while with 1.1.1 until reboot...
You could try what others have and use the MagiskHide Props module and try a different fingerprint in tandem with this module.
 

Jimmy Stat

Member
Mar 10, 2019
28
4
3
35
NYC & Louisville
which version of safetynet fix are you using and on which device? i'm on stock s9 snapdragon oneui 2.5, magisk 21.2 and xposed (tried both taichi and edxposed/riru). haven't been able to get fingerprint in banking apps to work
[/QUOTE]
Hey this is a little off topic but, I thought you couldn't root a Samsung s9+ Snapdragon, did I read correctly or did you find something I'm very unaware of? Thanks
 

wyt18

Senior Member
Jun 4, 2007
396
177
63
which version of safetynet fix are you using and on which device? i'm on stock s9 snapdragon oneui 2.5, magisk 21.2 and xposed (tried both taichi and edxposed/riru). haven't been able to get fingerprint in banking apps to work
Hey this is a little off topic but, I thought you couldn't root a Samsung s9+ Snapdragon, did I read correctly or did you find something I'm very unaware of? Thanks
[/QUOTE]
i have an s9 not s9+, but it should be just as straightforward to root:
 

eustachy

Member
Apr 5, 2016
20
2
33
Wrocław
www.djm-art.com
Hi, I am on miui xiaomi.eu 12.0.6 (Mi9), installed fix 1.1.1 and ... the system won't start, after a few minutes of MIUI logo it goes to TWRP. Unfortunately I haven't done a backup. Is there a way to remove the fix from the system?
 

Philnicolls89

Senior Member
Jun 28, 2019
588
234
48
32
A.C.T
Hi, I am on miui xiaomi.eu 12.0.6 (Mi9), installed fix 1.1.1 and ... the system won't start, after a few minutes of MIUI logo it goes to TWRP. Unfortunately I haven't done a backup. Is there a way to remove the fix from the system?
Through twrp navigate to /data/adb and delete the module then you should be able to reboot like normal.
 

alfred vierra

New member
Jan 17, 2021
1
0
11
Hi,
I have sm-a600n, installation failed cause ro.product.cpu.abi=armeabi-v7a on a10.
Do you have a plan to build for armv7?
Anyway, thank you for your great efforts.
 

xp99

Senior Member
Aug 28, 2011
180
81
48
Confirmed as working on Pixel 3a on android 11 January 2021 release. Used v1.1.1.

magisk: 21.3 (21300)
magisk manager: 8.0.6 (4826) (15)
 

Kurt Krummbein

Senior Member
Jul 19, 2011
518
389
98
I'm on Xioami Mi 10T Lite (gauguin), running AndyYan LOS 18.1-20210111-GSI
Used: v1.1.1
magisk: 21.3 (21300)
magisk manager: 8.0.6 (4826) (15)

Guess i also need MagiskHide Props Config ... tried that using Vendor-fingerprint (proposed for GSI), but that leads to a bootloop (saw in the logs some messages with camera3 HAL crashing) ... have a nice graveyard with many tombstones now :).

Will wait for a device-specifiy fingerprint :).

Greetz
Kurt
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    working in Xiaomi redmi note 7 MIUI 12 Android 10

    if in magisk it says it passes the check, but in the store it still detects the root you also need to "clear all data" of these following apps:

    - Google Play store
    - Google Play services
    - Google Service Framework

    Then reboot your device. :)

    If Google Pay still not working, "clear all data" of this app too.
    2
    ok so I didn't know the app itself could be hidden and that was triggering certain Bank applications to close automatically I don't have TWRP folders but I don't know how to enable the biometrics using magisk hide props config what is is that exactly?
    Magisk Manager (since v22 only called Magisk) can be hidden and renamed in it's own settings.
    For further information check this great guide by @Didgeridoohan :
    You'll find information about MagiskHide Props Config there too. That all depends only detecting root by other apps, as said above I can't help you with your Samsung related problems.
    Someone with a Sammy may answer that or is able to give you some tips.
    2
    Test2 is confirmed to fix biometrics for S20, S20+, S21 Exynos.
    https://github.com/kdrag0n/safetynet-fix/pull/13#issuecomment-767863635 PW
    It works, you guys are seriously awesome!

    Just installed edXposed and it still passes!
    2
    I'm on DP2 and I couldn't get safetynet test2 to work.
    This one is working
    1
    I already tried this procedure on my Galaxy Note 9 but it didn't work.
    have your clear your Google Play services and Google Play Store apps data?

    great indication of your device being SafetyNet Certified is if you can search Netflix on Play Store and Install if not that means your device fingerprint in incorrect

    if you are sure that you have done all steps correctly there a chance that the device fingerprint provided by props config is incorrect you can also file a report via props config main thread


    edit: install this samsung version of safetynet fix by kdragon https://github.com/kdrag0n/safetynet-fix/files/5846085/safetynet-fix-v1.1.1-samsungmod.zip
  • 158
    Universal SafetyNet Fix
    Magisk module​

    This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.

    Passing basic attestation is mostly out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Nonetheless, it features a few basic attempts at helping pass basic attestation on some devices, especially older devices and devices running stock ROMs.

    No device-specific features (such as the new Pixel-exclusive Google Assistant design or screen-off voice match) will be lost with this fix.

    Android versions 8–11 are supported. Heavy OEM skins are not officially supported, but they may work depending on your luck and the particular ROM in question. Please do not report problems on such ROMs.

    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 ROMs instead of overriding part of the ROM in a Magisk module. The ROM changes for it are linked above for ROM developers to use.

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

    Telegram group
    Source code

    If this helped you, please consider donating to support development: recurring donation for sustainable support or buy me a coffee. Thank you for your support!
    19
    I managed to fix the 3rd party app fingerprint issue on my Samsung w/ Android 10 (commented on this Github issue too). Basically the AOSP keystore is not fully compatible with the Samsung one so I decided to binary patch the one on my phone and ended up with this module. Now both fingerprint and SafetyNet works.
    Notes:
    - This disables key attestation for every app, idk if it breaks anything, nothing broke so far
    - Only change is the replaced system_sdk29/bin/keystore with the Samsung one (8 bytes modified)
    - Only works on Android 10
    - Might or might not work for you, use at your own risk.
    13
    Universal SafetyNet Fix v1.1.1 is now available.

    Changes
    • Removed security patch fixup to fix CTS profile mismatches on some devices

    Download

    Some devices will now need to use MagiskHide Props Config in addition to this module in order to pass CTS profile checks as part of basic attestation. Altering the CTS profile is no longer in scope for this module as it breaks more devices than it fixes.

    If this module helped you, please consider a recurring donation for sustainable support, or alternatively buy me a coffee. Everything helps, but a recurring donation is the best way to keep the project alive in the long term.

    Issues on heavy OEM skins
    This is a reminder that heavy OEM skins are not officially supported. They may happen to work depending on your luck and the particular ROM in question, but nothing is guaranteed. Please do not report problems on such ROMs. It's surprising that it works at all on them; I wouldn't expect everything to be fully working. I will not provide more support for issues related to heavy OEM skins.

    The compatibility issue does not lie in the SafetyNet fix itself, but rather how the Magisk module is built. It's possible to make the Magisk module version of the fix slightly more portable, but I have no interest in supporting heavy OEM skins, nor do I have any devices running such ROMs.

    You will always have the best luck with a ROM not too far from AOSP, e.g. most custom ROMs and Pixel stock ROMs.
    6
    Everyone having issues passing basic attestation after installing the module, please try the attached versions.

    There have been quite a few reports of fingerprint unlocking in apps breaking on One UI. This is not something that is planned to be fixed, because One UI is a heavy OEM skin that is not officially supported. It's surprising that it works on One UI to begin with.
    4
    There is no need to delete the whole Data, but go to Settings, Apps and delete Data for Google Play, Google Play Services, Google Services Framework, and probably Google Pay (not using, hence cannot tell for sure).
    Go to Airplane mode before deleting, after deleting reboot and turn Airplane off
    Deleting data of Google services framework acts as a partial factory reset and it might cause late/missing notifications of many apps. I would definitely advise to avoid doing it. 🙂

    It is enough to wait a little, Google play store should "recertify" device after some time automatically if it meets the criteria. Cache or data cleaning of Google play store app should speed up this process, but it's not mandatory in my experience.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone