[Discussion] Magisk - The Age of Zygisk.

Search This thread

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
This is a discussion and help thread for the newer versions of Magisk.

The main goal of this thread is to help users migrate to Magisk v24+
  • SafetyNet
    Basic integrity Pass
    CTS profile match Pass
  • Play Protect certification
    Device is certified

Feel free to discuss or give links to other Magisk related issues.
Fixes for gPay, banking apps and/or other apps and games that detect a 'compromised' Android system.
Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds. 🙃

Please read John's State of Magisk (medium.com)

Starting with the Magisk 23 (23010) canary builds.
  • MagiskHide is removed.
    MagiskHide masked the sensitive properties of the device to hide it from SafetyNet.
    Renaming (repackaging) the Magisk app is/was not part of MagiskHide.
    You still have the option to Hide the Magisk app under setting.​
  • Magisk Module online Repo is removed.
    The Magisk Module online Repo is still available and can be accessed outside of the Magisk app.​
  • Everything SafetyNet is removed.
    This includes the SafetyNet check that was incorporated into the Magisk app.​
  • Zygisk is introduced.
    Zygote + Magisk = Zygisk​
  • The Deny list replaces the Hide list.
    The Hide list (more or less) hid Magisk from the process on the list.
    The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.​

Starting with the Magisk 23 (23017) canary builds.
  • Magisk supports update channels per module.
    Each module can include it's own update link.​
  • Hide Magisk offline.
    You do not need internet connection to rename (repackage) the Magisk app.​

What does this mean?
Not much.
It is just the next step in Magisk's development.
Zygisk is a big step forward. ;)

Even before these changes in Magisk, the xda family and the Android community have always been active and willing to share. :D

Jump to Post


This is post will be updated once Magisk v24 is released.
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
Modules

MagiskHide Props Config
This module allows you to add, change and adjust prop values systemlessly using Magisk.​

MagiskHide Props Config Links:

Download Links:

Credits:
Didgeridoohan
All who contribute and support this project.


Universal SafetyNet Fix
It has been a year now since kdrag0n figured out how to 'trick' SafetyNet.
This 'trick' has been implemented properly into quite a few custom roms.
For custom roms that do not include it and/or stock roms, he turned it into a module.​

Universal SafetyNet Fix Links:

Download Links:

Credits:
kdrag0n
All who contribute and support this project.
 

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
Apps

Fox's Magisk Module Manager
This app allows you to manage and install Magisk modules.
Including from an online repo.​

Fox's Magisk Module Manager Links:

Download Links:

Credits:
Fox2Code
All who contribute and support this project.

Play Intergrity API Checker
This app shows info about your device integrity as reported by Google Play Services.
If any of this fails could mean your device is rooted or tampered in a way (for example you have an unlocked bootloader).​

Development:

Download Links:

Credits:
1nikolas
All who contribute and support this project.

YASNAC - Yet Another SafetyNet Attestation Checker
YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​

YASNAC Links:

Download Links:

Credits:
RikkaW
All who contribute and support this project.
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
Force Basic Attestation

Newer devices are designed to support hardware attestation.
Currently there is no way to hide the sensitive device properties when checked using hardware attestation.​

To get around this, kdrag0n figured out how trick SafetyNet that the device does not support hardware attestation.
SafetyNet will then fall back to check using basic attestation.

Note:
This method will work for devices that support hardware attestation and devices that do not.
  • Enable Zygisk.
  • Install the USNF module.
  • Reboot

To keep posts short, the instructions are hid by spoiler tags.
If you have not installed Magisk.
Follow the installation link in the Magisk post.​

Download the Universal SafetyNet Fix module.
Download link is in the Modules post.​

  1. Enable Zygisk
    • Open the Magisk app.
    • Go to Settings.
    • Scroll down to the Magisk section.
    • Toggle Zygisk on.
    • Go back to the Magisk Home screen.
  2. Go to Modules.
    • Select Install from storage.
    • Navigate to the Universal SafetyNet Fix module zip file and select it.
  3. Reboot.

The USNF module will adjust the sensitive props that are needed to pass SafetyNet.
Depending on the device and system (ROM) configuration, you might need to adjust a few more.
See the Adjust Prop values post.​
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
Basic Attestation
<Reserve>
Older devices that can not support hardware attestation there are other options.
  • Enable Zygisk.
  • Enable Denylist.
  • Add com.google.android.gms.unstable to the Denylist.
    • Add com.google.android.gms to the Denylist if needed.
  • Reset the sensitive prop values for the device.

Due to other modules and methods that require DenyList to be inactive, this method is more for reference.

For ease of use and compatibility, I would recommend using the USNF module instead.
See the Force Basic Attestation post.​

This post will be updated in a few days.
 
Last edited:

ipdev

Recognized Contributor
Feb 14, 2016
2,405
1
4,846
Google Nexus 10
Nexus 7 (2013)
Adjust Prop values
<Reserve>
Reset sensitive prop values.
Download the MagiskHide Props Config module.
Open the Magisk app and select the Modules option.
Select Install from storage option.
Navigate to where you saved the MHPC module and select it.
When the install is done, reboot.

Open a terminal app (or adb shell) and type props in the command line.
Make sure to grant root access

Select the Edit MagiskHide props (active) option.
(Currently option number 4)

It will show you the sensitive props that need to be adjusted.
If they all show (active) no changes needed.

If there is a prop value that shows as (enabled, not active) then you need to activate it by selecting it or a for all.
You will be prompted to set MagiskHide sensitive props?
Enter y(es), n(o) or e(xit):

If you are using a custom rom, you might also have to adjust the build fingerprint and security date.
From the MHPC main menu select Edit device fingerprint option.
(Currently option number 1)
Select Pick a certified fingerprint option.
(Currently option f)

Select the latest certified print for your device.
If your device is not listed, choose a device that is close to yours.​

This post will be updated soon.
 
Last edited:

pndwal

Senior Member
Yay! I get post no. 10!

Good to see this thread up Doc! ... How are you linking / promoting it?

Want mentions in Magisk General Discussion thread, or not for now?...

I note that this thread has the advantage of having an active OP...

So what? - Means I can post rubbish and it will be cleaned! ... Love a clean house... Hope you're a good housekeeper @ipdev! 😀 PW
 
Last edited:

pndwal

Senior Member
Hi all,
I'm on TJW's canary 23019.
Does anyone know/could explain what is/are the difference(s) with enforce denylist activated and not activated ?
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...

Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW

Edit: Lets kickstart things here! 😜
 
Last edited:

zputnyq

Senior Member
Apr 19, 2013
619
278
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...

Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW

Edit: Lets kickstart things here! 😜
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
 
  • Like
Reactions: pndwal

pndwal

Senior Member
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
You could do worse than read the first 5 posts here! 😉 PW
 
  • Like
Reactions: zputnyq

zgfg

Senior Member
Oct 10, 2016
8,996
6,741
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
Thanks @ipdev

I tried to put a short help for probably the most frequent posts/questions soon to expect.
(Sorry for cross-posting, I first put to the old and cluttered General Magisk thread but this is now better place)

===

Please carefully read Magisk Changelog and OP posts in this thread

Study the Magisk documentation from the official Magisk Github page - particularly about installing Magisk (if not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- different from the old school about flashing Magisk zip through TWRP)

a) No more MagiskHide. New technology instead (for more or less the same - to help hiding root): Zygisk+DenyList

b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC to check your SN

c) Modules window does no more connect to the old Modules repository.
You must download module zip files manually and "Install from local storage".
Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository and the old 'official' repo, allowing you to install from both

---

0) If upgrading Magisk and if you previously did "Hide Magisk app/Mngr" from Magisk app/mngr - always "Restore Magisk app/Mngr" before upgrading Magisk

1) Make sure that both Magisk app and Magisk are installed and updated to the new version v24 version. Inspect version numbers on the main Magisk window/page

2) Make sure to uninstall all Riru modules (Riru is not compatible with Zygisk that comes with Magisk v24)

3) Settings, Enable Zygisk and reboot.
Then check on the main window does it show Zygisk Yes

4) Settings, enable Enforce DenyList.
Configure DenyList, enable filters to Show OS and System apps.
Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.
You will have to check in all your banking apps and so as you used with MagiskHide.
Always reboot upon reconfiguring DenyList

5) If SafetyNet does not pass, install USNF 2.2.1 and test again.
Always reboot upon installing a module, also if/when you enable Systemless Hosts

Note: Once you install/enable USNF 2.2.1, it will remove Google Play Services from your DenyList - but don't worry, USNF takes care of GMS

6) If you are on non-certified custom ROM and you still don't pass SN - then you will need Magisk Hide Props Config module - check for and consult the MHCP thread

---

If you want to hide Zygisk, then instal Shamiko module - and you must disable Enforce DenyList (although DenyList must stay configured).

But Shamiko is really not essential (might help for some banking apps but it's irrelevant for SafetyNet)

---

Banking apps - out of scope for this post (also, this thread is about the Magisk v24 itself, not abkut the particular banking apps)

Go to Magisk Github documentation, read Wiki, there is a section with tips you should try first

If putting your banking app to DenyList (now, instead of the old Magisk Hide) and hiding Magisk app does not help, and the other tips from Wiki do not help (like renaming TWRP folder and so), search in this thread how to use Hide My Applist (Zygisk-LSPosed module)

Every time you apply another tip to your troublesome banking app - go to Settings, Apps, and delete Cache and Data for that banking app before you try to open it again (some apps will cache that they previously found the phone was rooted)

Even with HMA, there are certain banking apps that cannot be tricked (on some phones like Xiami, etc)

---

Momo - absolutely not essential for your life

When you pass SN, Momo might still detect that your Bootloader is unlocked - you cannot hide it from Momo on e.g. Xiaomi phones

Generally, treat Momo as 'banking' apps (add to DenyList and reboot)

Momo does not look for apps (Magisk app, LSPosed mngr, LSPosed modules), hence for Momo you don't need to bother with HMA

Basic tips for Momo: Remove/rename TWRP folder, disable USB Debugging - for the rest, search for Momo posts in this thread - but still, there will be findings you could not hide from Momo (not encrypted Data, custom ROM, etc)

===

PS: Magisk Alpha v24.1 (vvb2060 and her team) has departed their way (different package name, revival of MagiskHide?), hence this post is now (mainly) for the official TJW Magisk Stable and Canary v24

(Some parts do apply also to Alpha but use Alpha on your own risk and ask the other Alpha users about the Alpha status and practices)

===

Last but not the list - there night be specifics for certain phones (like flashing with Odin for Samsung, end so on)

This post is generic, for your specific practices read/search through this thread and also on your phone/model subforuns on XDA
 
Last edited:

crypticc

Senior Member
Aug 22, 2009
1,248
171
London
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."

Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.

This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1

Thank you
Chris
 
  • Like
Reactions: kurtn

pndwal

Senior Member
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."

Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.

This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1

Thank you
Chris
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879

Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
 

crypticc

Senior Member
Aug 22, 2009
1,248
171
London
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879

Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
Yes I appreciate that. I guess my question was if it is correct that after reboot USNF deselects the gms and gms.unstable

Thanks for the explanation.

FYI found what was triggering the app and got it working. Before I had just renamed Magisk (I renamed to MagicApp if that matters) but that didn't work. Also "pausing" the app wasn't enough.
I needed to actually uninstall the Magisk Manager app itself.

So the mechanism being used by the other app wasn't looking for Magisk/SU, but the app iself.
The App failing doesn't have any local file permissions so must've been something else.


Actually I found two apps failing root check and both were resolved by uninstalling the (renamed) Magisk APK.

So I wondered if the app was simply listening to debug messages.
So I reinstalled and then reproduced the failure looking into ADB logcat.

I could see during opening and just before the protection was triggered logcat events against the ".Magisk" app related to denying access. Uninstalling Magisk app stopped those messages and then the app was able to start.

Should Magisk "hiding" the magisk manager app by renaming it from ".Magisk" also have relabelled all of the messages and such related to the app?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Well yeah, i wouldn't mind a company using something like that in their apps. Bank apps are made by banks, there is a name behind them, there's someone accountable, and most important of all they dont have the kind of access that either Magisk or Xposed do, so in my opinion it is pretty much safe to trust them
    Sure... So you can vote with your feet in any case, but remember this is not about vv's Alpha fork where Appcenter implementation is simply vv's decision... She's free to implement test and debug it in her fork... The objections discussed were to her PR for telemetry in official Canary Magisk which, of course, you'll always have source for.

    Microsoft can ensure private data isn't compromised/abused with Appcenter as it uses their back end, but Magisk is also open to scrutiny by coders in general anyway... Bank apps will need skilled reversers to prove that they're acting honourably.

    So would Jorrit's (chainfire's) SuperSU for that matter, but most rooters in that era wouldn't have given a second thought to the possible (very serious) security breaches they were permitting with closed source root!

    As for Alpha fork, vv has always used it as a test bed for experimental fixes and never promoted it as an alternative Magisk for daily use; it was only ever for those wanting to test innovations or fixes, or as a stop-gap solution until her fixes are merged in Magisk... It seems apparent to me that, with telemetry data continuously coming in, she no longer needs many testers and may be actively discouraging Alpha takeup as a 1100+ Chinese userbase delivers ample data for her prolific contributions to Magisk.

    FWIW, vvb2060's Magisk commit production has been second only to John's (who merges most commits including those of others) for several years now... Just in recent months Shana has been at the top of the leaderboard however, but there's clearly much collaboration also:
    IMG_20230517_193901.jpg


    vv's fixes, and her changes have been at the forefront of Magisk development for some years now... So many major innovations in official Magisk have been developed in vv's Alpha fork and her experimental branches.

    Just to mention a sampling I posted more than a year ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, Renamable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

    Alpha is thus no rogue fork, much less a vehicle for stealing data or scamming any of us and many members here know that the evidence of vv's beneficent motivation is more than anecdotal...

    Whether I choose to do early testing of upcoming Magisk innovations with Alpha or not, I'm certainly not suspicious, rather I'm happy it exists as I am that other test forks and Magisk benefactors are contributing so much to this essential staple modding solution. 😋 PW
    8
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    From what I've read in the Magisk threads, Yes, it's an excellent idea.

    It's not for everyone. The people who know what they are doing can identify which situations make Alpha or Delta worth trying. The "full control over your phone" is no greater than that possessed by the "regular" Magisk.

    As for not bothering to provide English translations, why should she? She has a big enough fan base that I keep seeing references to her releases. Use it or don't. She doesn't charge anything, and you get your money's worth.
    7
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    Screenshot_20230516-130542_1.jpg
    See the devs below @topjohnwu down the bottom?
    They are the Alpha devs. Also massive contributors to the main Magisk branch.
    You can trust their software.
    6
    Of course they understand... Seems those that don't are the paranoid... And nobody's saying you can't be paranoid if you want!... 🤪

    [ ... etc. ... ]

    Irrespective of the fact that most of them probably have valid, understandable reasons for wanting to keep their source closed and to be difficult to communicate with in their TG channel, the fact that this is the current reality of Alpha is enough to motivate me not to use it.

    I don't hold it against those developers personally, and I respect their feelings and priorities and decisions about this.

    It's just that if I have a choice (and in this case, I do), I prefer not to use this kind of software that is provided under those constraints.

    As for telemetry, given the way that the current Chinese government utilizes similar telemetry aganst not only their own citizens, but also against others in other countries, I have more fear than usual about this particular telemetry. Even if none of the developers are knowingly working with the Chinese government, it's still possible that people from that government might be able to access the fruits of this telemetry.

    I have as much right to be paranoid about this telemetry as do any of the Alpha developers have a right to be paranoid about discussion-group participants.
    6
    As I understand it, Alpha is not meant for widespread use. Its developers are not looking for lots of users. Its a testbed, meant to be used by a few of their friends, and even then only to address specific problems.

    The rest of the world should wait for the changes to bubble into the official Magisk release.
    Well put...

    This discussion began because we mentioned that Alpha allows Volkswagen app to run and a member wondered if Alpha is trustworthy...

    Alpha solves the issue because it builds Shana's test branch commits and she's got native bridge Zygisk loading working to the point where it's quite useable (but still unfinished)
    IMG_20230506_090803.jpg

    over the last few months...

    The test branches for vv (Nangong Xueshan, @vvb2060), Shana (LoveSyKun, @yujincheng08), Canyie (@canyie) and others are open source, so you could easily build any of their experimental fixes yourself (it's not hard using a GitHub action run), or simply run one of the test branch CI (continuous integration) builds...

    For example, the last collaborative published Refactor zygisk to use native bridge to inject commit was authored by Shana and committed in LSPosed/Metagisk Zygisk branch by 3 weeks ago, and an associated CI build is here:
    Refactor zygisk to use native bridge to inject Magisk Build #61 pushed by yuijincheng08

    That might work fine but many CI builds don't; they're simply test runs with varying usefulness and even successful functioning... Alpha release builds on the other hand, are built using selected commits and have been checked at least for basic functionality by vv, so there's a greater level of reliability despite being bleeding edge stuff.

    I personally haven't used Alpha since John was producing viable Zygisk but not releasing any Canary builds (vv's Alpha served as a Zygisk testbed and POC for many months at the time) due to his mandatory period of restriction on creating/contributing to personal open source projects and Google review of his Magisk Android mod project... The new Zygisk refactoring that is native bridge loading simply made current Alpha builds too tempting for me! 😜... I'll be back to TJW Canary just as soon as we have N/B Zygisk, which Canyie has indicated should arrive with public 27.0 (or perhaps in an earlier Canary build).

    I may be tempted by some other off-the-chart innovation LSP Devs introduce in future and hop on the Alpha bandwagon again, but I'm really eager to see what official Magisk delivers...
    -----------
    FYI: For anyone interested in what changes / innovations are in the works for Magisk or just being tested,

    vv's test branches currently include:
    Shana / LSP project have:
    Canyie has:
    In TJW (official), @osm0sis has:
    🤠 PW
  • 137
    This is a discussion and help thread for the newer versions of Magisk.

    The main goal of this thread is to help users migrate to Magisk v24+
    • SafetyNet
      Basic integrity Pass
      CTS profile match Pass
    • Play Protect certification
      Device is certified

    Feel free to discuss or give links to other Magisk related issues.
    Fixes for gPay, banking apps and/or other apps and games that detect a 'compromised' Android system.
    Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds. 🙃

    Please read John's State of Magisk (medium.com)

    Starting with the Magisk 23 (23010) canary builds.
    • MagiskHide is removed.
      MagiskHide masked the sensitive properties of the device to hide it from SafetyNet.
      Renaming (repackaging) the Magisk app is/was not part of MagiskHide.
      You still have the option to Hide the Magisk app under setting.​
    • Magisk Module online Repo is removed.
      The Magisk Module online Repo is still available and can be accessed outside of the Magisk app.​
    • Everything SafetyNet is removed.
      This includes the SafetyNet check that was incorporated into the Magisk app.​
    • Zygisk is introduced.
      Zygote + Magisk = Zygisk​
    • The Deny list replaces the Hide list.
      The Hide list (more or less) hid Magisk from the process on the list.
      The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.​

    Starting with the Magisk 23 (23017) canary builds.
    • Magisk supports update channels per module.
      Each module can include it's own update link.​
    • Hide Magisk offline.
      You do not need internet connection to rename (repackage) the Magisk app.​

    What does this mean?
    Not much.
    It is just the next step in Magisk's development.
    Zygisk is a big step forward. ;)

    Even before these changes in Magisk, the xda family and the Android community have always been active and willing to share. :D

    Jump to Post


    This is post will be updated once Magisk v24 is released.
    72
    Magisk
    The Magic Mask for Android.

    Magisk Links:
    GitHub
    Release Notes

    Download Links:
    Stable and Beta releases.
    Canary
    • GitHub
      The notes.md file is the change log.
      The app-debug.apk is Magisk canary.
      Click on app-debug.apk and choose View Raw or click on the Download option.​

    Credits:
    topjohnwu
    All who contribute and support this project.
    62
    Modules

    MagiskHide Props Config
    This module allows you to add, change and adjust prop values systemlessly using Magisk.​

    MagiskHide Props Config Links:

    Download Links:

    Credits:
    Didgeridoohan
    All who contribute and support this project.


    Universal SafetyNet Fix
    It has been a year now since kdrag0n figured out how to 'trick' SafetyNet.
    This 'trick' has been implemented properly into quite a few custom roms.
    For custom roms that do not include it and/or stock roms, he turned it into a module.​

    Universal SafetyNet Fix Links:

    Download Links:

    Credits:
    kdrag0n
    All who contribute and support this project.
    58
    Apps

    Fox's Magisk Module Manager
    This app allows you to manage and install Magisk modules.
    Including from an online repo.​

    Fox's Magisk Module Manager Links:

    Download Links:

    Credits:
    Fox2Code
    All who contribute and support this project.

    Play Intergrity API Checker
    This app shows info about your device integrity as reported by Google Play Services.
    If any of this fails could mean your device is rooted or tampered in a way (for example you have an unlocked bootloader).​

    Development:

    Download Links:

    Credits:
    1nikolas
    All who contribute and support this project.

    YASNAC - Yet Another SafetyNet Attestation Checker
    YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​

    YASNAC Links:

    Download Links:

    Credits:
    RikkaW
    All who contribute and support this project.
    48
    Force Basic Attestation

    Newer devices are designed to support hardware attestation.
    Currently there is no way to hide the sensitive device properties when checked using hardware attestation.​

    To get around this, kdrag0n figured out how trick SafetyNet that the device does not support hardware attestation.
    SafetyNet will then fall back to check using basic attestation.

    Note:
    This method will work for devices that support hardware attestation and devices that do not.
    • Enable Zygisk.
    • Install the USNF module.
    • Reboot

    To keep posts short, the instructions are hid by spoiler tags.
    If you have not installed Magisk.
    Follow the installation link in the Magisk post.​

    Download the Universal SafetyNet Fix module.
    Download link is in the Modules post.​

    1. Enable Zygisk
      • Open the Magisk app.
      • Go to Settings.
      • Scroll down to the Magisk section.
      • Toggle Zygisk on.
      • Go back to the Magisk Home screen.
    2. Go to Modules.
      • Select Install from storage.
      • Navigate to the Universal SafetyNet Fix module zip file and select it.
    3. Reboot.

    The USNF module will adjust the sensitive props that are needed to pass SafetyNet.
    Depending on the device and system (ROM) configuration, you might need to adjust a few more.
    See the Adjust Prop values post.​