[Discussion] Magisk - The Age of Zygisk.
- Thread starter ipdev
- Start date
You can check with all list bankings i left in previous comment.
Video 1, zygisk+shamiko, imobile detect rooted
Video 2, magiskhide, imobile not detect rooted
HMA is also needed for iMobile. As I said on TG, MagiskHide is still relevant, and it's great to have Magisk Delta (thanks for that!) as an alternative that has MagiskHide, but iMobile works with Zygisk + Shamiko + HMA. Some apps don't, but this one does.
I updated to Magisk stable v. 25.1 about a week ago the recommended way. Everything went smooth. Then a couple of days ago my banking app detected root. Momo (4.3.1) tells me that the environment is broken, but I pass Safetynet (both), Applist Detector finds nothing, Rootbeer shows everything is ok and my phone shows as certified in Play Store settings.
I’m on MIUI 12.5.1 stock rom. Modules USNF 2.2.1 and Shamiko 0.4.4 (v. 0.50 crashes my banking app). I don’t use LSPosed. Magisk app is hidden.
The only change I made is updating HuskyDG’s module Magisk Bootloop Protector to v. 1.8. I removed the module, but still root is detected.
I have then returned to Magisk 24.3 with an OrangeFox Recovery backup. Everything is fine. My banking app does not detect root. Momo only finds Zygisk. I have tried several times to update to Magisk 25.1 again but every time my banking app detects root and Momo tells me the environment is broken.
Can someone tell what to do next, please? Why can’t I suddenly install Magisk 25.1 without my banking app detecting root?
I’m on MIUI 12.5.1 stock rom. Modules USNF 2.2.1 and Shamiko 0.4.4 (v. 0.50 crashes my banking app). I don’t use LSPosed. Magisk app is hidden.
The only change I made is updating HuskyDG’s module Magisk Bootloop Protector to v. 1.8. I removed the module, but still root is detected.
I have then returned to Magisk 24.3 with an OrangeFox Recovery backup. Everything is fine. My banking app does not detect root. Momo only finds Zygisk. I have tried several times to update to Magisk 25.1 again but every time my banking app detects root and Momo tells me the environment is broken.
Can someone tell what to do next, please? Why can’t I suddenly install Magisk 25.1 without my banking app detecting root?
Maybe refactoring magiskinit cause this, think you should stay at v24.3
Just an FYI: I’m on crDroid v8.6 A12.1 rom. I have modules USNF 2.2.1,
Momo v4.3.1 reports that the environment is abnormal (see screenshot - init.rc is modified is new for me; Magisk Detector has been saying 'unexpected' for long), but I pass SafetyNet, Applist Detector reports 'All Clear', Rootbeer shows 'Not Rooted' and my phone shows as 'Certified' in Play Store settings. GPay worked when I last checked.
Attachments
Thanks. Don't really understand your answer so what causes this "refactoring" of magiskinit? Is it Magisk Bootloop Protector? What puzzles me is that Magisk 25.1 was working flawless for 3-4 days.
Last edited:
OK. I don't rely that much on Momo but when my banking apps detect root I listen to her
Attachments
Hi, I don't use iMobile Pay, but I just tried this app on my phone (A12, Magisk Stable 25.1, USNF, Shamiko) and it detects root if I don't disable the Magisk App (even if it's repackaged to another name). But disabling the Magisk App, the iMobile App works fine. It's pretty much the same as HSBC App that has been discussed before.
Hello Sir,@martyfender @m0han Switched from Alpha to Delta.Works perfectly fine so far. The steps are as usual:
- Unhide if hidden (restore the hidden app)
- Install delta apk
- Grant delta apk root from original Magisk / Alpha
- Flash Magisk through Delta using Delta's direct install
- Reboot
- Uninstall original Magisk / Alpha
I tried this method and now my mobile boots into TWRP, not in system. PLEASE HELP
After uninstalling original magisk from magisk.apk, mobile rebooted automatically and goes in TWRP
Tagging @huskydg sir
What hide methods do you have selected in HMA? You didn't cover that in your screen recording. Also, there's no need to repackage the Magisk app. HMA is being utilized to prevent iMobile from finding the Magisk app.
As usual so much information. Ah, you're using this phone and using those options. And you're trying to install that version of Magisk...Hello Sir,
I tried this method and now my mobile boots into TWRP, not in system. PLEASE HELP
After uninstalling original magisk from magisk.apk, mobile rebooted automatically and goes in TWRP
Tagging @huskydg sir
Sorry for being sarcastic, but if I'm already considering not to root my phone anymore, I really can't understand people rooting and modifying their phones without having any idea what they're doing.
You only need to uninstall original Magisk App after switching to any custom Magisk (alpha, cygisk, delta,...) not Fully uninstall Magisk from the app (completely removing Magisk from boot image and system)Hello Sir,
I tried this method and now my mobile boots into TWRP, not in system. PLEASE HELP
After uninstalling original magisk from magisk.apk, mobile rebooted automatically and goes in TWRP
Tagging @huskydg sir
Last edited:
As he said you didn't use Hide Magisk app option.
In additional, if you try everything (Hide Magisk App, Hide my applist, zygisk+shamiko, ...) but it doesn't work, you can try to switch to magisk delta, turn off zygisk and use only MagiskHide or downgrade to Magisk v23 official to use MagiskHide which is still guaranteed to work for almost banking apps. If you are using magisk delta, you don't need to use Hide Magisk App option because delta already came with custom package name.
zygisk itself is the problem at hiding and leaves obvious traces.
Last edited:
a new safetynet update has been released https://github.com/kdrag0n/safetynet-fix/releases
thanks to kdrag0n and osm0sis and benjibobs
thanks to kdrag0n and osm0sis and benjibobs
FWIW
This may not be applicable here at all, but it's worth noting that for some apps, incl. Sparkasse PushTAN, neither one method is enough; Magisk's Hide the Magisk app as well as HMA hiding (using the three 'safe' methods, or just Intent queries) must be employed to successfully thwart their (Promon) protection engine.
This not only looks for known app names and signatures, but uses simple pattern matching on installed apps. Magisk's Hide the app will patch the package name in AndroidManifest.xml, repack it and sign it with a random signature for obfuscation, but the classes.dex with code remains and can be / is used to identify even the stub app.
Further, at least for S PushTAN, since a recent release mileage seems to vary per device... The above method was working across the board for some time, but it seems that no Xiaomi device users now have success (with latest releases) while OnePlus and other device users can still use this method...
The above distills the basics from this (very long) issue:
https://github.com/topjohnwu/Magisk/issues/1084
PWSome very interesting news re. apps that use the QUERY_ALL_PACKAGES permission (S PushTAN & many others) FINALLY being pulled into line by Google (from former XDA Editor in chief):
Reasons / excuses for the delay:
https://www.xda-developers.com/google-play-store-query-all-packages-rule/
What it means in practice:
My guess is that it will depend a lot on Google... Here's hoping...
PW
www.twitter.com/MishaalRahman/status/1511452117214679053
Reasons / excuses for the delay:
https://www.xda-developers.com/google-play-store-query-all-packages-rule/
What it means in practice:
My guess is that it will depend a lot on Google... Here's hoping...
PW
Last edited:
Similar threads
Top Liked Posts
-
1
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):
skkk/TWRP/A12 • AKR DL
dl.akr-developers.com
-
6Latest Official TJW Canary (release) & Debug (debug) Magisk builds:
Magisk (f42c089b) (25102)
- [MagiskInit] Fix a potential issue when stub cpio is used
- [MagiskInit] Fix reboot to recovery when stub cpio is used
- [General] Better data encryption detection
- [General] Move the whole logging infrastructure into Rust
Diffs to v25.1
- [MagiskInit] Fix a potential issue when stub cpio is used
- [MagiskInit] Fix reboot to recovery when stub cpio is used
- [General] Better data encryption detection
- [General] Move the whole logging infrastructure into Rust
PW5
I just tried it on my phone (stock rom, Magisk 24.3, Shamiko 0.5.0, USNF).
Without doing anything, it detects root.
Adding it to denylist, still detects root.
Freezing the Magisk app, goes through!5
It's now been reported a number of times that freezing the Magisk app helps thwart root detection in many cases.
So ... I now believe that what we need to do is not talk about that publicly too much, so that the banking-and-other-kinds-of-app developers who might check these forums don't catch on to the fact the Magisk app itself doesn't actually provide any run-time Magisk functionality.
This way, those developers will keep thinking that checking for the existence of a non-frozen Magisk app itself is sufficient.
Given the intelligence level of some of the banking people who lamely think that it's important to block root access under Android in order to "protect" their provided banking functionality, this ruse might actually be quite effective in many cases.
After all, anyone who accesses a bank via their desktop computer is doing so on a rooted machine, and those idiotic banking software designers don't even care about "protecting" us against that. And those same banks issue us debit cards that we carry in our stealable wallets, and they don't prohibit us from using those debit cards, either. They go crazy only over trying to protect people against rooted Android devices, which are no more insecure than desktop computers and wallet-borne debit cards.5
Just to avoid confusion/ be clear, Shamiko does not hide apps (in denylist or otherwise)...
It's akin to old MagiskHide, and hides traces of root from apps in the list...
@appleman_wp
If you wish to hide apps detected by banks etc, try the Hide My Applist LSPosed module...
(Edits mine.)
Generally Shamiko is used without settings / extra configuration.
However it can actually be reconfigured (by those game / mavericks
) for whitelist mode usage. Note caveats:
Sadist!
PW4
"Magisk" *does* need to be "resident". You have been advised to freeze "the Magisk Manager app".
You can see if freezing could possibly help by uninstalling the Magisk app -- not Magisk, the Magisk app. If that solves your detection problem, you might find the freezing more convenient than repeatedly uninstalling/reinstalling. -
120This 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.
Jump to PostMagisk - Modules - Apps - Force Basic Attestation - Basic Attestation - Adjust Prop values - Notes - Points of Interest
This is post will be updated once Magisk v24 is released.63MagiskThe Magic Mask for Android.
Magisk Links:
GitHub
- Installation Instruction
- Frequently Asked Questions
- Magisk Documentation
- Magisk Troubleshoot Wiki (by Didgeridoohan)
Download Links:
Stable and Beta releases.
Canary
- GitHub
Thenotes.mdfile is the change log.
Theapp-debug.apkis Magisk canary.
Click onapp-debug.apkand choose View Raw or click on the Download option.
Credits:
topjohnwu
All who contribute and support this project.57Modules
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.53Apps
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.43Force 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.
- 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.
- Go to Modules.
- Select Install from storage.
- Navigate to the Universal SafetyNet Fix module zip file and select it.
- 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. - SafetyNet
