[Discussion] Magisk - The Age of Zygisk.

Search This thread

kramer04

Senior Member
Jan 15, 2011
597
230
France
Hello
Maybe i'm the only one with this problem. I didn't found nothing.
Zygisk isn't active on magisk.
tried with magisk 24 beta and canary.
 

Attachments

  • Screenshot_20220127-123644.jpg
    Screenshot_20220127-123644.jpg
    307.9 KB · Views: 208
  • Screenshot_20220127-123715.jpg
    Screenshot_20220127-123715.jpg
    264.3 KB · Views: 209

zgfg

Senior Member
Oct 10, 2016
7,168
4,622
My new Lisa is still growing up and under age for unlocking Bootloader till Saturday but I'm preparing for the day

1) OTA zip does not contain boot.img but 13.2 GB payload.bin.
However, there is Payload Dumper:
Found under OnePlus but it successfully unpacked my boot.img for MIUI

2) Now a newbie's question.
Since Lisa (Xiaomi 11 Lite 5g NE) is the a/b device:
Code:
getprop ro.build.ab_update
true
should I flash Magisk patched boot img to boot, or to boot_a, or both to boot_a and boot_b?

Per my understanding, boot will refer to the current slot (boot_a) while boot_b will be used for next OTA - hence even better not to patch boot_b

3) I'm confused that
Code:
getprop ro.build.system_root_image
false
but is this maybe 'normal' for a/b device or because of dynamic partitions?
 

Lughnasadh

Senior Member
Mar 23, 2015
3,327
3,294
Google Nexus 5
Huawei Nexus 6P
2) Now a newbie's question.
Since Lisa (Xiaomi 11 Lite 5g NE) is the a/b device:

should I flash Magisk patched boot img to boot, or to boot_a, or both to boot_a and boot_b?

Per my understanding, boot will refer to the current slot (boot_a) while boot_b will be used for next OTA - hence even better not to patch boot_b
Can't speak to your specific device, but I have 3 a/b devices (all Pixels) and I just flash the Magisk patched boot image like...

fastboot flash boot <nameofpatchedbootimage>

It will patch your current slot, whichever slot that may be. And yes, no need to and not a good idea to patch your inactive slot.

Then if you update via OTA you can use the "install to inactive slot" method in Magisk.

Again, all this based on experience with Pixel a/b devices only.
 

Ghisy

Senior Member
Mar 27, 2010
1,681
480
Hey, does anyone know how to go from Magisk v23 stable with Riru + LSposed to Magisk v24 with LSposed Zygisk on Android 11 (and 12)?
 

godenk789

Member
Dec 31, 2018
6
3
Thanks! ... Guess you have public Beta if 24.0. (The debug logging enabled synchronised Canary version is 24001.)

Please remind me what phone you have; MIUI OS that appears to have issues with HMA method now while other devices / OSs can pass easily. Also, can you show us Momo screenshot? 👍 PW
I also passed the S-pushtan root detection
with Zygisk enabled, and USNF + Shamiko module installed. The denylist option is unchecked to make sure that the Shamiko module is working fine...

I'm using a pixel-based custom ROM, with an "abnormal" environment status according to Momo apps.
 

Attachments

  • Screenshot_20220128-091801446.jpg
    Screenshot_20220128-091801446.jpg
    103.3 KB · Views: 217
  • Screenshot_20220128-091813128.jpg
    Screenshot_20220128-091813128.jpg
    249.2 KB · Views: 213
  • Screenshot_20220128-092101226.jpg
    Screenshot_20220128-092101226.jpg
    246.7 KB · Views: 204
  • Screenshot_20220128-091825859.jpg
    Screenshot_20220128-091825859.jpg
    189.8 KB · Views: 190

zgfg

Senior Member
Oct 10, 2016
7,168
4,622
Hey, does anyone know how to go from Magisk v23 stable with Riru + LSposed to Magisk v24 with LSposed Zygisk on Android 11 (and 12)?
Pls read OP posts.

Also, you can follow my post #14 from two days ago

In short:

- Uninstall all Riru modules, reboot

- If you had your Magisk app in Magisk v23, hidden, Restore Magisk app from its Settings.
Or uninstall that hidden Magisk app that you renamed/repackaged/hid

- Update from Magisk v23 to Canary v24 (read below about):

There are several possible paths. As it said in post #14, carefully read Magisk Documentation, Installation guide available from Magisk Github

E.g , I would prefer installing Magisk Canary v24 app, then patching the image, and flashing (details described in the mentioned guide)

But if you used to install your old Magisk v23 through TWRP, it should still work

You are talking about upgrading Msgisk but yoz also mention A12 - I doubt thar you had Magisk v23 on A12. In that case fully uninstall Magisk v23 and first upgrade your phone to A12.
Similarly if you need to update your A11

- then follow post #14

- after all that, install Zygisk-LSposed and your LSPosed modules, configure them
 
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
Magisk - Modules - Apps - Force Basic Attestation - Basic Attestation - Adjust Prop values - Notes


This is post will be updated once Magisk v24 is released.
Why the Bold Circle flashing at launch of latest Magisk v24 beta?

Device: Redmi Note 8 Pro
OS: MIUI 12.5 (Android 11)
 

Attachments

  • 1643355994887.jpg
    1643355994887.jpg
    423.2 KB · Views: 113

crypticc

Senior Member
Aug 22, 2009
1,164
139
London
Magisk General thread, Dec 6, post #49346:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86055073

On the screenshot you can see that "Found Magisk" was not present

At that time I was running Alpha 23015 and some earlier versions of Shamiko and LSPosed. All the rest regarding Magisk, modules, LSPosed and its modules, root apps was the same


If it is relevant..
.when I briefly tried Shamiko it didn't work and lost Google certification. That was v23 too.

But I don't want to misdirect in case I missed a step and actually Shamiko v23 might be okay:.
I had downloaded and installed Shamiko then re-selected the 2 required GMS services into the deny list in Magisk that USNF disables, and then turned off the deny list in Magisk per Shamiko instructions. I turned off USNF. And then rebooted.
...I had lost CTS and Google certification in the Play Store realise not the same problem your trying to fix here but are the Shamiko alpha momentarily not working as intended? Or was removing USNF my error (you said earlier that it serves different purpose)



Chris
 

Zuikkis

Senior Member
Nov 20, 2013
90
32
I see in the changelog of v24:

"[General] Support Android 12"

What does that mean?

I have been running v23 (stable channel) with Android 12 for some time now with no issues. It is not supposed to work? SafetyNet passes, Google Play is certified, banking apps work.
 

pndwal

Senior Member
If it is relevant..
.when I briefly tried Shamiko it didn't work and lost Google certification. That was v23 too.

But I don't want to misdirect in case I missed a step and actually Shamiko v23 might be okay:.
I had downloaded and installed Shamiko then re-selected the 2 required GMS services into the deny list in Magisk that USNF disables, and then turned off the deny list in Magisk per Shamiko instructions. I turned off USNF. And then rebooted.
...I had lost CTS and Google certification in the Play Store realise not the same problem your trying to fix here but are the Shamiko alpha momentarily not working as intended? Or was removing USNF my error (you said earlier that it serves different purpose)



Chris
Yup, you need both; Shamiko initially only hid Zygisk (it's akin to RiruHide), then ability to hide Isolated process leaks etc were added... You may not even notice it's affect until you use bank apps etc that detect modified TEE by means other than relying on SafetyNet API.

USNF is pretty much the new MagiskHide - don't disable it! (allows SafetyNet to pass as long as your device used a certified fingerprint for CTS (Compatibility Test Suite) with matching security patch date... (MHPC can do the latter if using custom or China region stock ROM etc).

🤠 PW
 
  • Like
Reactions: crypticc

pndwal

Senior Member
I see in the changelog of v24:

"[General] Support Android 12"

What does that mean?

I have been running v23 (stable channel) with Android 12 for some time now with no issues. It is not supposed to work? SafetyNet passes, Google Play is certified, banking apps work.
Yup, very first A12 release previews worked w/ Magisk on some (many?) devices before John made any changes for compatibility!...

When moving to a different dessert (Android version) previously, Magisk had often spat it out until it grew up a bit / a taste was acquired, so this was a bit of a fluke & surprised even John...

Since then various fixes have been made for proper Android 12 compatibility, eg:
Support code injection on Android 12,
boot image header v4 - supports brand new devices launched with Android 12 w/ v4 boot images),
Target SDK 31 - This is the main reason for note in change log; - proper API (Application Programming Interface) Level 31 (Android 12) support.

Note: all the above ([General] Support Android 12) fixes arrived with the first Canary Magisk not synced w/ 23.0 back in October, ie. 23010 (many fixes since then too). The last 2 were authored by vvb2060 and were available in her Alpha builds months before that too!

🤠 PW
 
Last edited:

Zuikkis

Senior Member
Nov 20, 2013
90
32
Yup, very first A12 release previews worked w/ Magisk on some (many?) devices before John made any changes for compatibility!...

When moving to a different desert (Android version) previously, Magisk had often spat it out until it grew up a bit / a taste was acquired, so this was a bit of a fluke & surprised even John...

Since then various fixes have been made for proper Android 12 compatibility, eg:
Support code injection on Android 12,
boot image header v4 - supports brand new devices launched with Android 12 w/ v4 boot images),
Target SDK 31 - This is the main reason for note in change log; - proper API (Application Programming Interface) Level 31 (Android 12) support.

Note: all the above ([General] Support Android 12) fixes arrived with the first Canary Magisk not synced w/ 23.0 back in October, ie. 23010 (many fixes since then too). The last 2 were authored by vvb2060 and were available in her Alpha builds months before that too!

🤠 PW

Thanks for the super detailed answer!

I'm still probably not updating, as long as my current setup is working. :)

I'm not really using much of Magisk features, just need it to pass SafetyNet. So far it is working with my current apps.
 
  • Like
Reactions: pndwal

Ghisy

Senior Member
Mar 27, 2010
1,681
480
Pls read OP posts.

Also, you can follow my post #14 from two days ago

In short:

- Uninstall all Riru modules, reboot

- If you had your Magisk app in Magisk v23, hidden, Restore Magisk app from its Settings.
Or uninstall that hidden Magisk app that you renamed/repackaged/hid

- Update from Magisk v23 to Canary v24 (read below about):

There are several possible paths. As it said in post #14, carefully read Magisk Documentation, Installation guide available from Magisk Github

E.g , I would prefer installing Magisk Canary v24 app, then patching the image, and flashing (details described in the mentioned guide)

But if you used to install your old Magisk v23 through TWRP, it should still work

You are talking about upgrading Msgisk but yoz also mention A12 - I doubt thar you had Magisk v23 on A12. In that case fully uninstall Magisk v23 and first upgrade your phone to A12.
Similarly if you need to update your A11

- then follow post #14

- after all that, install Zygisk-LSposed and your LSPosed modules, configure them
Hey, thanks for that! I did read the OP posts but didn't see anything related to Riru/LSPosed. Will try your method then.

Edit: all good now! I even installed UNSF 2.2.1 so now my Pixel 4 XL also passes SafetyNet! (I'm still on Android 11 btw)
 
Last edited:

Top Liked Posts

  • 3
    Where do you guys get Momo? I can't download from Telegram on PC and I don't want to create an account.
    Exactly from TG, with the account.
    Sorry, that's the life
  • 8
    I am just curious why you don't want to install telegram. About a year ago, or so, I uninstalled telegram because I got tired of the juvenile, posts on an android app dev forum, lspeed. I feel now that telegram is better moderated, but that is mostly based on the magisk alpha, lsposed. etc that I am now on. Is there some other security issues with it that I am not aware? I have most notification in it turned off so it doesn't constantly annoy me.
    Nah just the childishness nonsense you mention. I was on a few Android groups at one point and they were all pretty obnoxious. That and when I tried having a public profile getting random "Hey are you THE osm0sis from xda? Cool! Just checking." roughly every couple days was ridiculous. Made me fairly certain I'm doing just fine with xda, Twitter, email, GitHub, Slack and TWRP's Zulip. 😜
    6
    But we can attach the file itself, can't we @pndwal ?
    5
    What do you'll think about this Xposed module?

    I can't find an app that doesn't work...momo still complains about broken tee.
    4.1.1 momo, 1.3.7 privacyspace, 0.5.0 shamiko and 1.8.3 lsposed
    Momo complains about broken TEE because of the way OnePlus implemented hardware key attestation. The same happens on my 8T.
    It's not something that can be fixed and it doesn't affect root detection or SafetyNet.
    5
    Seems not, but Canyie has fixed her GitHub link to Momo from MomoHider page https://github.com/canyie/Riru-MomoHider ('depreciation notice' introduces Shamiko - MomoHider may not be a 'thing' anymore...) however (Link to momo apk is dead #22 / Fix #22, 54d76a6), so at least we can link to that on XDA since we can't post TG links as file source...

    Momo is linked under 'Test':
    https://github.com/canyie/Riru-MomoHider#test

    👀 PW
    Sigh.. guess I'll secretly install Telegram just to download things. 🤷‍♂️🙄🥲
    4
    Does anyone know why I am not play store certified and thus cannot install apps like netflix after passing both integrity check and CTS.

    I have lineage-18.1-20220425-nightly-cheeseburger-signed installed on my oneplus 5. I have rooted using magisk and used a combination of Universal safetynet fix together with changing the fingerprint of my device to pass the CTS.

    I also registered my device on the google certification site using the GSF ID.

    Any help would be highly appreciated.
    After passing SafetyNet, you need to clear cache and data for PlayStore and (not always) for PlayServices.
    This will clear data and updates.

    Then wait for them to update again.

    Play will scan your device again and mark it as certified.

    ---

    Registering your current install does not certify the device.

    You are telling Google that you are using a non-certified rom. ;)


    Cheers. :cowboy:
  • 112
    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.
    61
    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.
    55
    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.
    51
    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.


    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.
    43
    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.​