[Discussion] Magisk - The Age of Zygisk.

Search This thread

bacevs

Member
Mar 19, 2015
17
2
Melbourne
Google Pixel 4 XL
This would have sufficed? Maybe @bacevs had this already done.
Nope, I hadn't added those google play services to the denylist. Just did now and removed integrity checker from the deny list and passing all but the last check. Not sure how to go about passing it.

Screenshot_20220805-032340.png
 

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
This would have sufficed? Maybe @bacevs had this already done.
When you use USNF, it removes Google Play Services from the DenyList

Below is the screenshot from
/data/adb/modules/safetynet-fix/post-fa-data.sh

that script is executed on each reboot

If you add GMS to your DenyList and reboot, GMS should be removed from DenyList after reboot if Zygisk is enabled and USNF 2.3 module is properly installed

It's because USNF is Zygisk module and it has it hardcoded in the native code to spoof GMS

EDIT:

It removes GMS only if DenyList is Enforced. But USNF nevertheless spoofs prints to GMS, by use of its native Zygisk code, no matter if GMS is in DenyList or not
 

Attachments

  • IMG_20220804_192045.jpg
    IMG_20220804_192045.jpg
    110.5 KB · Views: 102
Last edited:

m0han

Senior Member
Apr 30, 2012
5,115
2,127
... If you add GMS to your DenyList and reboot, GMS should be removed from DenyList after reboot if Zygisk is enabled and USNF 2.3 module is properly installed...

It removes GMS only if DenyList is Enforced. But USNF nevertheless spoofs prints to GMS, by use of its native Zygisk code, no matter if GMS is in DenyList or not
I don't know if it is due to my setup (I am using the latest Magisk Delta). I have 'Google Play Services' added to the Magisk Hidelist, but, MagiskHide is disabled. 'GPS' remains even after reboot. (Not sure if reference to forks are deemed OT here.)
 

Attachments

  • Screenshot_20220804_233959.jpg
    Screenshot_20220804_233959.jpg
    203.9 KB · Views: 132
  • Screenshot_20220804_234110.jpg
    Screenshot_20220804_234110.jpg
    135.7 KB · Views: 129
  • Screenshot_20220804_234158.jpg
    Screenshot_20220804_234158.jpg
    146 KB · Views: 114
  • Screenshot_20220804_234235.jpg
    Screenshot_20220804_234235.jpg
    132.3 KB · Views: 129

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
I don't know if it is due to my setup (I am using the latest Magisk Delta). I have 'Google Play Services' added to the Magisk Hidelist, but, Magisk Hide is disabled. 'GPS' remains even after reboot.
MagiskHide is not the same as DenyList. The two are separated in Delta

Moreover, MagiskHide list is managed by magiskhide applet (no more supported in official Magisk) , while DenyList is managed by magisk --denylist

When you look into my screenshot - or simply open your own USNF module post-fs-data.sh, you will see the command magisk --denylist that applies to DenyList, not to MagiskHide list

I'm not even sure if --denylist option for magisk is supported in Delta, but you can test yourself in your Terminal
 

bacevs

Member
Mar 19, 2015
17
2
Melbourne
Google Pixel 4 XL
Again down, I can not connect to the internet...
Is it normal that it is down so often?
Does anyone else get 401 error on modules hosted on Androidacy module repo when clicking description button on the module?
 

Attachments

  • Screenshot_20220805-220545.png
    Screenshot_20220805-220545.png
    274.7 KB · Views: 95
  • Screenshot_20220805-220538.png
    Screenshot_20220805-220538.png
    103.8 KB · Views: 94
  • Screenshot_20220805-220600~2.png
    Screenshot_20220805-220600~2.png
    202.9 KB · Views: 94
  • Like
Reactions: ipdev

pndwal

Senior Member
I also have this problem. And if I turn Zygisk off Magisk reverts to 24.1.
Is there a workaround?
This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
 
  • Like
Reactions: ipdev and J.Michael

maakosan

Member
Aug 24, 2012
39
6
Brisbane
This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
No A/B stuff..
 
  • Like
Reactions: pndwal

pndwal

Senior Member
It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
No A/B stuff..
Very interesting...

So can I assume 7T has recovery_a/_b partitions as I believe 8T does, and that you also patched either recovery_a or _b in Magisk App some time back?

If this is correct, I'm guessing Zygisk-off somehow causes device to reboot to system via recovery, and you thus have old Magisk since you patched recovery image (which is also a boot image containing ramdisk of course) with that some time ago...

Note: Magisk in recovery and customised protocol for reboot via recovery to system w/o special adapted recovery key combo was designed for A-only legacy SAR devices specifically as these require Magisk in recovery partition as they have no ramdisk in boot... You seem to have used it on your 2SI device and there is no reason it shouldn't work apart from the fact that Magisk in boot partion is far more desirable / convenient...

If I'm correct about a/b partitioning in 7T, your modern 2SI boot type device will of course have ramdisk in 4 partitions, recovery_a and _b, also boot_a and _b... This is fairly unique as most 2SI devices use recovery in boot partition (w/ a hybrid ramdisk) and have no actual recovery partitions.

Again, if I'm right you can test theory by booting from powered down state using recovery key combo with this adjustment: As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. (If you wanted to boot into the actual recovery mode, you would long press volume up until you see the recovery screen.)
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Please reply to confirm (or correct) this! 😛 PW
 
  • Like
Reactions: J.Michael and ipdev

Dr_Strangelove

New member
Aug 3, 2022
2
0
Hello friends .
I have a Redmi 9 (Global) Codename : Lancelot
Installed magisk via custom recovery (twrp and shrp) and root is sucess , but zygisk doesnt work , when I enable it in settings and reboot , in magisk zygisk : no . I used official MIUI 11.0.4. 11.0.7 11.0.9 12.0.1 12.0.4 Android 10 and zygisk still no success , although it worked on Lineage 18.1 Android 11 and Pixel Experience 12.1 Plus but I want to use MIUI and I want it to be MIUI android 10 to be exact because of some complexity of android 11 in Xiaomi devices I avoid android 11 . now back to MIUI 12.5.6 Android 11 to see if works at all or not , then I'm gonna try EEA or Europe MIUI Roms But before that I'm here to see if others have the same problem with their Xiaomi ? If yes , any fixes yet ?

Edit : Fixed by flashing latest Global MIUI Rom ,for almost a week I was looking for a way around Redmi 9 android 10 zygisk but was not successful . Switch to android 11 and it worked like a charm but I lost TWRP decryption , on Android 11 my internal storage is encrypted while in TWRP . Didnt try EEA roms though and will never Since I got what I wanted .
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
Hello friends .
I have a Redmi 9 (Global) Codename : Lancelot
Installed magisk via custom recovery (twrp and shrp) and root is sucess , but zygisk doesnt work , when I enable it in settings and reboot , in magisk zygisk : no . I used official MIUI 11.0.4. 11.0.7 11.0.9 12.0.1 12.0.4 Android 10 and zygisk still no success , although it worked on Lineage 18.1 Android 11 and Pixel Experience 12.1 Plus but I want to use MIUI and I want it to be MIUI android 10 to be exact because of some complexity of android 11 in Xiaomi devices I avoid android 11 . now back to MIUI 12.5.6 Android 11 to see if works at all or not , then I'm gonna try EEA or Europe MIUI Roms But before that I'm here to see if others have the same problem with their Xiaomi ? If yes , any fixes yet ?

Edit : Fixed by flashing latest Global MIUI Rom ,for almost a week I was looking for a way around Redmi 9 android 10 zygisk but was not successful . Switch to android 11 and it will work like a charm but I lost TWRP decryption in Android 11 my internal storage is encrypted while in TWRP . Didnt try EEA roms .
It's of-topic (TWRP and encryption) but:

- Generally, when switching ROMs, it's required to Format Data.
Don't know what exactly you did but you can try that

- Sometimes it may also help to experiment by switching between pin, pattern and no Android unlock screen setting

- Make sure you use the latest TWRP

- TWRP.me does not support A12 encryption yet. However, there are SKKK TWRP versions (for various Xiaomi models) that do support (beta development stage):
 

pndwal

Senior Member
Hello friends .
I have a Redmi 9 (Global) Codename : Lancelot
Installed magisk via custom recovery (twrp and shrp) and root is sucess , but zygisk doesnt work , when I enable it in settings and reboot , in magisk zygisk : no . I used official MIUI 11.0.4. 11.0.7 11.0.9 12.0.1 12.0.4 Android 10 and zygisk still no success , although it worked on Lineage 18.1 Android 11 and Pixel Experience 12.1 Plus but I want to use MIUI and I want it to be MIUI android 10 to be exact because of some complexity of android 11 in Xiaomi devices I avoid android 11 . now back to MIUI 12.5.6 Android 11 to see if works at all or not , then I'm gonna try EEA or Europe MIUI Roms But before that I'm here to see if others have the same problem with their Xiaomi ? If yes , any fixes yet ?

Edit : Fixed by flashing latest Global MIUI Rom ,for almost a week I was looking for a way around Redmi 9 android 10 zygisk but was not successful . Switch to android 11 and it will work like a charm but I lost TWRP decryption in Android 11 my internal storage is encrypted while in TWRP . Didnt try EEA roms .
I think you just need to Learn to Stop Worrying and Love the Bomb. 😜 ...

The whole point is:
You didn't keep the Machine
a secret; You've told the world!...
... all is NOT lost!!!


In case you still want Android 10 w/ root (downgrade again):

Your issue is very similar to this (but root was lost also for some):
https://github.com/topjohnwu/Magisk/issues/6095

Fix just completed (by Canyie, who incidentally became an adult a few days ago! 😃 ); Affected Redmi Note 4 on A7, Realme 6 on A12, etc...

Root fixed here:
https://github.com/topjohnwu/Magisk/issues/6095#issuecomment-1207255175
Zygisk fixed here apparently:
https://github.com/topjohnwu/Magisk/issues/6095#issuecomment-1207369066

You could try the early test build linked there...

Fix merged in Magisk (still downstream of any releases) here:
52ba6d1 Don't let remote errors crash Zygisk
with a further fix merged for Zygisk loading in:
1735a71 Use ANDROID_DLEXT_FORCE_LOAD to load second stage if possible

You could try the final Actions run trial Magisk build here:
Use `ANDROID_DLEXT_FORCE_LOAD` to load second stage if possible
(build in artifacts .zip at end, need to log in to download.)

...Or just wait for next official Magisk release, most likely Canary...

🤠 PW

"I'm afraid I don't understand something. Is the Premier threatening to explode this if our planes carry out their attack?"
"No sir. It is not a thing a sane man would do. The doomsday machine is designed to to trigger itself automatically."
"But this is absolute madness, ambassador. Why should you build such a thing?"
"There are those of us who fought against it, but in the end we could not keep up with the expense involved in the arms race, the space race, and the peace race. And at the same time our people grumbled for more nylons and washing machines. Our doomsday scheme cost us just a small fraction of what we'd been spending on defense in a single year. But the deciding factor was when we learned that your country was working along similar lines, and we were afraid of a doomsday gap."
"This is preposterous. I've never approved of anything like that."
"Our source was the New York Times."
"Dr. Strangelove, do we have anything like that in the works?"
 
Last edited:

zgfg

Senior Member
Oct 10, 2016
7,814
5,226
How to fix this A12L using magisk hide

magisk alpha
Edit:
Oops, if Magisk Alpha you should better ask in Magisk Alpha thread:

Alpha is proprietary fork, closed source and they manage a close Chinese Telegram support group

Not many users here

Generally some different settings than in the official TJW, but supposedly they removed the old MagiskHide and in that case you should use DenyList the same/similar way as described in the OP posts here for the official Magisk v24/v25
 
Last edited:

Top Liked Posts

  • 9
    oh good, a new Momo discussion in the thread

    let me grab some popcorn....
    1
    oh good, a new Momo discussion in the thread

    let me grab some popcorn....
    🍿🍿🍿
  • 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
    9
    oh good, a new Momo discussion in the thread

    let me grab some popcorn....
    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.
    6
    I was follow your every steps carefully but instead of zygisk hide in momo, now it's start detect debugging mode enable 😮💨.
    It detects what it says. If bothering you, turn off USB/ADB debugging mode.
    Or give up on Momo - it will always detect something
    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
  • 127
    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.
    59
    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.​