[Discussion] Magisk - The Age of Zygisk.

Search This thread

73sydney

Senior Member
Fwiw

Delta is not entirely without its own issues, chiefly for me occaisonally losing root in the background, leaving me with having to reset my damn Watch 4 twice a day (if i was lucky) during the 3 days i tested it - once the link to watch is severed by root detection, theres NO way to recover it without reset....i soon went back to 25 debug and zero issues...luckily my bank app doesnt detect using zygisk/shamiko.

i.e. nothing is perfect and its still (relatively speaking) early days for zygisk/shamiko and im sure other zygisk alternatives
 
Last edited:
  • Like
Reactions: rodken

vietmobi

New member
Jun 28, 2022
2
1
It detects Zygisk.
You need Magisk Hide, ie.Magisk Alpha/Delta
Thank, i try magisk delta, turn off zygisk and use magiskhide. It finally works.

IMG_20220629_211324_227.jpg
 
  • Like
Reactions: shoey63

proza

Senior Member
Sep 18, 2012
169
3
I have a moto G7 plus.
I installed the Pixel OS 12 Plus. I installed Magisk 25.1. I enabled both Zygisk and Enforce DenyList. In the DenyList, I only selected the Google Play Services, enabled all the items except com.google.android.gms.
I rebooted and installed module MagiskHidePropsConf-v6.1.2.zip. Rebooted and installed module safetynet-fix-Zygisk-v2.2.1.zip. Rebooted and use the terminal to change the props to Google Nexus 6P.
Rebooted, run Root Checker. It shows SafetyNet request Failed. CTS profile match N/A. Basic integrity N/A.
What else can I do to pass the safetynet?
 

zgfg

Senior Member
Oct 10, 2016
7,797
5,198
It says "Something went wrong, Attestation response timeout"
Do you have GApos in your ROM?
SafetyNet goes through Google Play Services - if missing, it cannot work

AFAIK, there was a MicroG version (an open source alternative to GMS) but it must be provided with the ROM, proper version, etc

I don't know the details and frankly Im not interested (I use stock or custom ROMs with GApps), but I recall it was discussed here and/or in the USNF or MHPC threads, You could search

If you do have GApps, turn off all possible firewalls, blockers, etc - SN is not checked locally, GMS must connect to the Google servers
 

proza

Senior Member
Sep 18, 2012
169
3
Do you have GApos in your ROM?
SafetyNet goes through Google Play Services - if missing, it cannot work

AFAIK, there was a MicroG version (an open source alternative to GMS) but it must be provided with the ROM, proper version, etc

I don't know the details and frankly Im not interested (I use stock or custom ROMs with GApps), but I recall it was discussed here and/or in the USNF or MHPC threads, You could search

If you do have GApps, turn off all possible firewalls, blockers, etc - SN is not checked locally, GMS must connect to the Google servers

From the website, it says "PixelExperience is an AOSP based ROM, with Google apps included"
I have disabled the firewall and paused the adaway.
 

zgfg

Senior Member
Oct 10, 2016
7,797
5,198
From the website, it says "PixelExperience is an AOSP based ROM, with Google apps included"
I have disabled the firewall and paused the adaway.
Here you have the official SafetyNet API specifcation:

You can see that no response or timeout means that somewhere in the request/response channel (call to GMS, call to Google servers, responses back) is broken.
It does not mean that CTS or Basic integrity fail (hence you cannot fix with USNF or MHPC), but there is no response (and therefore no verdict about - they might be perfectly passing if attestation channel was not broken)

If one SN checker fails to answer, it can be that that something is wrong with that checker (or they went over quota with the number of requests to Google today or so).
But if it happens to you with different SN checkers (YASNAC now works perfectly for me), the pipe is broken in your ROM or on your line

Eg, ask in the group where you took the ROM from, how they test and pass SN
 
  • Like
Reactions: J.Michael

rodken

Senior Member
Jan 11, 2010
1,114
452
{Mod edit: Quoted post has been deleted}
You need to be more specific:

-- What device are you utilizing
-- Which version of Android
-- Custom ROM or Stock
-- What steps did you take [if any] to mitigate the issue
 
Last edited by a moderator:

GreekPilot

Senior Member
Jun 12, 2008
233
62
OnePlus 9 Pro
Good morning everybody. With new Shamiko v0.5.1 (117), no zygisk detected.
 

Attachments

  • Screenshot_2022-07-01-08-22-45-95_8ecd68a317969a903887707449183b6f.jpg
    Screenshot_2022-07-01-08-22-45-95_8ecd68a317969a903887707449183b6f.jpg
    487.1 KB · Views: 84

aximili

Member
Jun 29, 2007
18
0
I can't get HMA to work. I have enabled it in LSPosed but I don't have the module in Magisk.
(I have tried installing it from the APK and from the Play Store)
Help please?

Screenshot_20220701-172526 HMA not activated.jpg
 
Last edited:

m0han

Senior Member
Apr 30, 2012
5,104
2,123
Did you checkbox all for momo processes in denylist?
This is how I have Momo configured in DenyList at the moment. The middle item was disabled after reading somewhere that it is advisable. (I don't recall where I read it.) Would my Momo situation change for the better if I enable that also?
 

Attachments

  • Screenshot_20220701_153402.jpg
    Screenshot_20220701_153402.jpg
    181.2 KB · Views: 66

dohanin

Senior Member
Mar 26, 2011
231
128
Sony Xperia X Compact
Xiaomi Mi Pad 4
This is how I have Momo configured in DenyList at the moment. The middle item was disabled after reading somewhere that it is advisable. (I don't recall where I read it.) Would my Momo situation change for the better if I enable that also?
Probably the same.

If you like to hide Init.rc, you can install another magisk module InitRcHider. Or use Shamiko which has included initrc hider since 0.4.3. Although it doesn't make much difference I guess as not many apps would try to look for it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Mod Info:

    Dear people of this thread,
    pls stay on topic and do not engage in world-events related discussions. This thread has seen enough of it already.

    In the name of peace and prosperity,
    Happy Zygisk-related posting,
    Cheers everyone
    8
    ... Needless inconvenience from banks ... its none of the banks business to stop their clients from using rooted devices. Theyre just adding another hindrance to smooth banking operations thereby possibly hampering their own business by wasting both their and their clients time. Thats Stupidity!
    Bank Devs did you hear? Pls discuss this with your bosses. Its like going backwards instead of forward.
    I totally agree!

    And as I've mentioned here before, every desktop computer is a rooted device, and of course we don't see the banks trying to hinder us from accessing their services from our computers.

    And banks gladly issue us debit cards which we keep in our wallets that are just as easy to steal as mobile devices.

    Rooted Android devices are just low-hanging fruit. And the amount of fraud that's prevented by trying to fight against Android root is minuscule, given the extremely small percentage of mobile device users who want to use rooted Android devices. I wouldn't be surprised if the amount of money that banks spend for anti-Android-modding software development exceeds the maximum amount of money that could be lost via the hacking of modded Android devices.
    4
    Currently, I have no info about Device Certified or not in Google Play Settings (screenshot)

    I observed that yesterday night when I upgraded my Xiaomi 11 Lite 5G NE from the previous week Xiaomi.eu weekly (MIUI 13/A12) to the current.
    I thought it would become Certified over the day, but it's still in limbo

    Frankly, last week when I installed Xiaomi.eu Weekly (first time) I forgot to check

    Everything else is ok, SafetyNet (with Basic CTS), Play Integrity (Basic Integrity), Play Protect is ok, Netflix eg running with L1, etc

    I'm kind of worried to wipe Google Play Data - not knowing would it become Certified or Not

    I'm pretty sure I did have similar cases in the past with previous devices, ROMs, Magisk setup, but they used to settle down by itself in
    After wiping only the Cache for Playstore and waiting few more hours, now Certified
    3
    Now 2 bank apps are working out of 3 after the recent update to the bank apps.
    I used A11 GSI, PhhTreble App Signature Spoofing, TWRP, Magisk 24.3 & a couple of important modules like Hide-User-Debug, USNF Moded, Hide-Props-Config, microG Gapps module safety net : All passed, Installed the bank apps through Aurora.
    For the 3rd bank app Dev Options need to be OFF & Only PlayStore Install allowed not PackageInstaller.
    Needless inconvenience from banks, they can just add more steps of verifications instead like Voice Recognition IVR AI (Voice Recognition IVR AI Bots are already functional in these banks helplline numbers) so they can just use that for bank app login verifications on top of other verifications. Its none of the banks business to stop their clients from using rooted devices. Theyre just adding another hindrance to smooth banking operations thereby possibly hampering their own business by wasting both their and their clients time. Thats Stupidity!
    Bank Devs did you hear? Pls discuss this with your bosses. Its like going backwards instead of forward.
    3
    Why kdragon doesn't update it, or there are no good solution for that?
    As you know, he's aware and thanked @Displax for his fix / PR... And he does clearly want to improve the solution and scope the method
    to Play Integrity code by identifying methods it calls near the beginning and end of integrity checks, and adding hooks to set and restore the fingerprint ...
    https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1195452147

    He has already suggested an idea for adding an end hook, but said:
    Of course, this is all theoretical as it depends on the exact order of steps in the integrity checking process. Worst case scenario, we could just sleep for 1 second or so and revert the fingerprint change in a background thread. Not sure when I'll have time to look into it myself, but feel free to try implementing this idea: ...
    https://github.com/kdrag0n/safetynet-fix/pull/207#issuecomment-1200437447
    - So it seems he's in no rush himself, and he's happy for other Devs to test / contribute (although none appear to have tried adding hooks etc yet)...

    I guess he'll do more on this PR as time allows... If other Dev's haven't had time to test even proposed
    • Set the fingerprint in the key attestation hook
    • Spawn a thread to revert it after 3 seconds:
    thread(daemon = true) {
    Thread.sleep(3000)
    /* revert */
    }
    idea, then he may think 'why should I rush?'... He probably has a ton of more important maintenance on his plethora of apps, utilities, Proton ROM / kernel builds, etc to do...

    Meanwhile, @Displax solution seems a pretty good one to tide us over, for most devices... PW
  • 125
    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.
    66
    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.
    58
    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.
    54
    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.
    46
    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.​