Fyi, I got the the airplane mode trick from @osm0sis in https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
[Discussion] Magisk - The Age of Zygisk.
- Thread starter ipdev
- Start date
+1 from me. Metro Bank was working fine until a couple of days ago. Following with interest.
Hello
I have had a problem with various complications (I won't explain them all), and now I have a working mobile, but I can't re-root again.
Device:
- Xiaomi Lisa
- It was rooted with Magisk 25.2
- And various modules
- It does not have TWRP recovery, and Orange Fox does not decrypt data on Android 13
Situation:
- I received the OTA Android 12-> 13 (MIUI 13->14) (stock EU).
- I decided to download it to extract boot.img and patch it.
- Against the usual (and configured), instead of waiting for confirmation to install (time to apply the standard OTA update procedure: restore stock images and flash Magisk to empty slot), it started the process.
- When I realized I did the restore images, and let it reboot
- It ended up in a strange bootloop (at least for me): a few seconds after booting, showing the launcher, and even being able to open some app, the phone reboots and ends up in MIUI recovery.
- (...)
- Finally I manage to reflash the new ROM ("except storage"), and the phone boots fine.
- I patch the new boot
- But when I do the standard boot on the patched image, the problem of that "strange" bootloop is reproduced.
- Attempts to apply uninstall.zip fail because the recovery does not mount data.
- ((Finally, at home we have another Lisa. I opted to completely uninstall Magisk, flash the new ROM, then boot with the patched image and install Magisk, and it did not give any problems. I'm thinking to do the same in future...)).
The questions begin. I will also appreciate any rectification if something I say is not correct, to continue learning:
- It seems that there was something left of Magisk that creates a conflict, no?
- Since the modules and Magisk are inside \data, it is not possible to uninstall with uninstall.zip, is it?
(in fact in one of the tests with OFox (which does not see \data) it instead installed Magisk, giving the same problem
- as the mobile is not really rooted, there is no chance I could delete modules folder, right?
- And only with the mobile rooted I could ask the Magisk Manager to uninstall completely, no?
But as it does not give me time to run it because the phone restarts, and when it does is without rooting, I can't
- The time to reboot with the mobile temporarily rooted begins once I have entered the unlock pin. As I said, it doesn't give me time enough to interact with the applications.
Would there be any script (I'm not a developer) that I can run from terminal as soon as I have unlocked the phone, so it has effect before the device restarts? (stop process, remove folder...)
- Any idea (that does not involve formatting data...)?
Thanks
I have had a problem with various complications (I won't explain them all), and now I have a working mobile, but I can't re-root again.
Device:
- Xiaomi Lisa
- It was rooted with Magisk 25.2
- And various modules
- It does not have TWRP recovery, and Orange Fox does not decrypt data on Android 13
Situation:
- I received the OTA Android 12-> 13 (MIUI 13->14) (stock EU).
- I decided to download it to extract boot.img and patch it.
- Against the usual (and configured), instead of waiting for confirmation to install (time to apply the standard OTA update procedure: restore stock images and flash Magisk to empty slot), it started the process.
- When I realized I did the restore images, and let it reboot
- It ended up in a strange bootloop (at least for me): a few seconds after booting, showing the launcher, and even being able to open some app, the phone reboots and ends up in MIUI recovery.
- (...)
- Finally I manage to reflash the new ROM ("except storage"), and the phone boots fine.
- I patch the new boot
- But when I do the standard boot on the patched image, the problem of that "strange" bootloop is reproduced.
- Attempts to apply uninstall.zip fail because the recovery does not mount data.
- ((Finally, at home we have another Lisa. I opted to completely uninstall Magisk, flash the new ROM, then boot with the patched image and install Magisk, and it did not give any problems. I'm thinking to do the same in future...)).
The questions begin. I will also appreciate any rectification if something I say is not correct, to continue learning:
- It seems that there was something left of Magisk that creates a conflict, no?
- Since the modules and Magisk are inside \data, it is not possible to uninstall with uninstall.zip, is it?
(in fact in one of the tests with OFox (which does not see \data) it instead installed Magisk, giving the same problem
- as the mobile is not really rooted, there is no chance I could delete modules folder, right?
- And only with the mobile rooted I could ask the Magisk Manager to uninstall completely, no?
But as it does not give me time to run it because the phone restarts, and when it does is without rooting, I can't
- The time to reboot with the mobile temporarily rooted begins once I have entered the unlock pin. As I said, it doesn't give me time enough to interact with the applications.
Would there be any script (I'm not a developer) that I can run from terminal as soon as I have unlocked the phone, so it has effect before the device restarts? (stop process, remove folder...)
- Any idea (that does not involve formatting data...)?
Thanks
Last edited:
Much in this section of @Didgeridoohan's Wiki:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
Scroll down to Disabling/uninstalling modules manually... First option is w/ ADB from PC... Many more...
Look around that wiki first for other pointers too... It's old, but it's gold...
PWThanks, so you give me some hope...!!!Much in this section of @Didgeridoohan's Wiki:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
Scroll down to Disabling/uninstalling modules manually... First option is w/ ADB from PC... Many more...
Look around that wiki first for other pointers too... It's old, but it's gold...
As I said, for keep on learning: what I posted makes sense?
Or there is some mistake in the reasoning?
I'll read the wiki but was just thinking that a prepared and "fast" executed adb line to remove (knowing what to do!) moduls/Magisk, could do
Still facing some issues (don't know which module is causing problems), butMuch in this section of @Didgeridoohan's Wiki:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
Scroll down to Disabling/uninstalling modules manually... First option is w/ ADB from PC... Many more...
Look around that wiki first for other pointers too... It's old, but it's gold...
adb wait-for-device shell magisk --remove-modules
did it.
At least I've the phone rer-ooted
Thanks again
Just FYI, Zygisk does not appear to work on the Android 14 Developer Preview. Magisk patch works fine, root is good, but Zygisk always shows No, even after toggling and rebooting.
Yup... Thought that would fix bootloop with root...
What other issues? I'm guessing S/N ctsProfileMatch and PI deviceIntegrity w/ USNF?... If so, many users now face this:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88114877
PW
Last edited:
Hello
with A13, I can't see the work profile apps anymore, so I can't hide them from magisk and they detect the root
Is there anything I can do?
a bug with shelter ?
with A13, I can't see the work profile apps anymore, so I can't hide them from magisk and they detect the root
Is there anything I can do?
a bug with shelter ?
I really, really need to stay away from Reddit. The questions there. "How to flash modules in Magisk with locked bootloader?" 
On Reddit, everything is possible. Sky is your limitI really, really need to stay away from Reddit. The questions there. "How to flash modules in Magisk with locked bootloader?"
Dread it. Run from it.... The hardest choices require the strongest wills.
Dumb question...
Has anyone tried installing Magisk on an Android Device Emulator?
Has anyone tried installing Magisk on an Android Device Emulator?
Last edited:
Hello, some emulator like bluestasks or nox these possible there are explanations on the web.
If you're talking about the other android emulator I think it must be possible, as it must run on Android so I think it's possible.
nox player there is root option in parameter
https://forum.xda-developers.com/t/...win-macos-win-google-play-store-apis.4218123/
If you're talking about the other android emulator I think it must be possible, as it must run on Android so I think it's possible.
nox player there is root option in parameter
https://forum.xda-developers.com/t/...win-macos-win-google-play-store-apis.4218123/
Last edited:
If I could figure out where the Ramdisk image is, I could patch it.
Interesting to note is that it includes debug root - meaning you can su in shell...but Magisk doesn't detect root. SELinux probably?
Lloyds Bank mobile app continues to detect root.
https://play.google.com/store/apps/details?id=com.grppl.android.shell.CMBlloydsTSB73&hl=en_GB&gl=US
Device and Model Number: Motorola G7 Power XT1955-4 (ocean)
Android running version: 10 - stock firmware
Procedure implemented:
https://play.google.com/store/apps/details?id=com.grppl.android.shell.CMBlloydsTSB73&hl=en_GB&gl=US
Device and Model Number: Motorola G7 Power XT1955-4 (ocean)
Android running version: 10 - stock firmware
Procedure implemented:
- Zygisk is enabled.
- DenyList is enforced.
Lloyds Bank app was added to the DenyList. - Installed Universal SafetyNet Fix v2.4.0-Mod_1.1 modded by Displax, rebooted device; verified said app's presence in the DenyList.
Play Integrity API Checker app yields pass for Device Integrity and Basic Integrity. - Disabled Developer options.
- Hid the Magisk app and renamed it using the in-built feature.
- Froze the renamed Magisk app using the Ice Box app.
- Lloyds Bank app was force stopped, cache and data were cleared; device was rebooted.
- Attempt to authenticate into the said banking app, yielded the error depicted by the image below.
Last edited:
UK banking apps also stopped working for me.
I managed to get the chase banking app working again through this device id changer:
play.google.com
However my metro app doesn't show on the id changer list so I can't use that on it.
Any ideas?
I managed to get the chase banking app working again through this device id changer:
Device ID Changer - Apps on Google Play
Get, share and change the android device id for all Android version.
However my metro app doesn't show on the id changer list so I can't use that on it.
Any ideas?
I can't find list, at least on free version... Seems to change device ID globally... Does full app work differently?... Target only specific apps?... PWUK banking apps also stopped working for me.
I managed to get the chase banking app working again through this device id changer:
Device ID Changer - Apps on Google Play
Get, share and change the android device id for all Android version.
However my metro app doesn't show on the id changer list so I can't use that on it.
Any ideas?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10Hi all.
To put this in to the light (full sunshine).
Companies and their app(s) do not care if you or you device is at risk.
It is no concern to them if harm falls on you.
What concerns them is liable.
The companies that are more secure in how they handle sensitive data, do not care if you are using a 'rooted' device.
orHas anyone seen a post about Amazon not working on a rooted/insecure device?
- They have a legal team that can overpower the litigation.
- They have the finances to payout a settlement.
Cheers.
54Haha... I thought someone might bring up these things!
Of course the main point was always the need to tarball image files...
Seems the members issues stem from Odin flashing being incompatible with raw .img files... and I gave examples of differing extraction / tarballing / patching / flashing procedures that should work...
I actually read such claims but didn't repeat them as the need is far from clearly established as far as I can see (and Sammy users can always rename files if needed or if they wish)...
This may well be important as you say at least for some Odin versions. (Again, Sammy users may know better.) However many instructions don't indicate a need to use partition names, eg
https://forum.gsmhosting.com/vbb/f777/how-flash-custom-kernel-using-odin-download-2574060/
and
https://medium.com/@oliviaroborts/odin-download-to-flash-custom-kernel-on-galaxy-device-e53d3eac744f
And official TWRP instructions simply say "select the tar file that you downloaded (twrp-3.7.0_9-0-hlte.img.tar etc) and flash the device" so it seems Odin is smart enough to recognise this as a recovery image despite not including "recovery" in filename...
https://twrp.me/samsung/samsunggalaxynote3internationalexynos.html
Here's a guide that bears out the fact that Odin builds at least since 3.11 (May 2016) do "file analysis" to determine partition/image type and flashes files named differently to the correct partition (rather than using file names):
https://droidtechknow.com/how-to/twrp/install-twrp-recovery-on-samsung/
In this example TWRP.tar is detected as containing "Single download recovery.img" and flashed correctly as such per output log:
Well yes, but specifically for Sammy devices launched w/ SAR+ (ie SAR or 2SI) booting...
Members device launched w/ Android 4.3 (Jelly Bean), upgradable to stock 5.0 (Lollipop), and John does say "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section"...
I began giving advice based on pre A9 Android and guides make it clear that flashing Magisk patched AP binary alone is fine for these devices... Also, older devices didn't have vbmeta partitions, and only AP binary anyway... BL and CP binaries were seperated out more recently...
Once the member indicated device runs a custom AOSP build however (we still don't know if this is an A10+ however... Nb. legacy ramdisk devices don't convert to legacy SAR w/ A9 running version but necessarily become 2SI w/ updates to A10 RV incl. custom ROMs), I did point the possibility of some of John's cautions for SAR+ devices applying per:
... Of course flashing only the available boot.img (after patching and tarballing by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing) is quite different from John's prescribed method for A9+/SAR+ LV (launch version) devices of flashing the complete AP binary (after patching) along with other binaries anyway!... It's akin to flashing a discreet boot image w/ fastboot...Nb. 2 if you are running A10+ your legacy ramdisk boot type device has been converted to 2SI boot type which is a form of SAR for Magisk purposes... This means that despite official Installation instructions saying "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section", some of the caveats in the Samsung (System-as-root) section may now apply... Apart from knowing you are now using what John defines as SAR device (Google doesn't), it's hard to know which apply...
Guides indicate this method works fine for older Sammy devices however...
... Please let me know if I'm missing something obvious though... I may well be wide of the mark as I have no practical experience with Odin and have only done cursory searches...
PW4
I'm not a Sammy user, but doing a bit more digging just for fun, it seems Magisk actually has everything in place but Sammy users seem to be expected to know some stuff that's simply not detailed in current Installation Instructions to allow them to use standard in-app patching and flash w/o using .zip installer...
Flashing magiskpatched-boot.img
With TWRP installed, you can flash ROMs and 'addons' as .zip or .img.
This means you should be able to extract the boot.img from your custom ROM, patch it as you did, then flash magiskpatched-boot.img to /boot using twrp... You've simply swapped fastboot for custom recovery to flash a standard partition .img file...
Flashing magiskpatched-boot.img.tar
Basically, Odin uses a fastboot or download mode that can't flash standard images... Everything it seems must simply be in a tarball... This means you probably originally flashed something like twrp-3.7.0_9-0-hlte.img.tar for TWRP, not twrp-3.7.0_9-0-hlte.img...
Flashing magiskpatched-boot.img is similar... You'll need magiskpatched-boot.img.tar...
3 approaches:
1) I'm not sure if you can extract boot image from your ROM as a .tar file, but Magisk App will accept and patch either .tar or .img, so seems you could use an extracted boot.img.tar, Magisk patch it then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...
2) If only boot.img is available you can simply open a Command Prompt/PowerShell window in the PC folder where the file was extracted and TAR the file by running
tar -cvf boot.img.tar boot.img
then using the resulting boot.img.tar, Magisk patch it then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...
3) Further, you could take the boot.img and Magisk patch it then transfer file to PC and open a Command Prompt/PowerShell window in the folder with the magiskpatched-boot.img file and TAR it by running
tar -cvf magiskpatched-boot.img.tar magiskpatched-boot.img
then flash by clicking Odin "AP" button and loading the magiskpatched-boot.img.tar file before flashing...
Nb. Simply renaming a .img file to .tar won't work...
Nb. 2 if you are running A10+ your legacy ramdisk boot type device has been converted to 2SI boot type which is a form of SAR for Magisk purposes... This means that despite official Installation instructions saying "If your Samsung device is NOT launched with Android 9.0 or higher, you are reading the wrong section", some of the caveats in the Samsung (System-as-root) section may now apply... Apart from knowing you are now using what John defines as SAR device (Google doesn't), it's hard to know which apply...
Hope this helps... somehow sometime.
PW4@pndwal Point of order: If you have a magisk-patched-boot.img and you are going to make a tar, you meed to rename (or copy) magisk-patched-boot.img to "boot.img" and put *that* into a tar -- it's important for the names in the tar to match the partition names.
And John Wu warned against having less than boot, recovery, and vbmeta in the AP.tar; and against not filling all four slots in Odin -- many people's success stories to the contrary not withstanding. -
134This 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.69MagiskThe 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.61Modules
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.56Apps
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.47Force 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
