Related
What is SafetyNet?
"SafetyNet provides a set of services and APIs that help protect your app against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users." -Android Developers
Like stated above, SafetyNet is a set of APIs embedded in Google Play Services to see whether a device has been tampered with from its factory state (e.g. a custom ROM is installed). Developers can use this API to block smartphones in which SafetyNet fails to pass.
How will this affect me and my usage of the device?
Several apps use this API to block users with custom ROMs, such as Google Pay, Netflix, and others, especially banking apps. If you don't use any of these, then failing SafetyNet probably won't matter to you. But if you do use some of these apps, you'll find that they often refuse to run.
How to pass SafetyNet:
You will need Magisk and Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You will need this ZIP:
https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680
After you have downloaded both of these, go ahead and flash Magisk through TWRP. After installation is complete, Go to the Modules section in Magisk Manager and press the + button and select the SafetyNet spoofer ZIP. After it's done, reboot your phone. Then go to Settings in Magisk Manager and turn Magisk Hide off and then on again. Go to the Magisk Hide section and select the following apps to hide Magisk from:
Google
Google Services Framework
Google Play Store
(and other apps requiring SafetyNet to pass)
Then go to Play Store>Settings and see if it says your Device is certified. If not, clear Play Store data and try again.
Done! Now you will have passed SafetyNet!
JarlPenguin said:
What is SafetyNet?
"SafetyNet provides a set of services and APIs that help protect your app against security threats, including device tampering, bad URLs, potentially harmful apps, and fake users." -Android Developers
Like stated above, SafetyNet is a set of APIs embedded in Google Play Services to see whether a device has been tampered with from its factory state (e.g. a custom ROM is installed). Developers can use this API to block smartphones in which SafetyNet fails to pass.
How will this affect me and my usage of the device?
Several apps use this API to block users with custom ROMs, such as Google Pay, Netflix, and others, especially banking apps. If you don't use any of these, then failing SafetyNet probably won't matter to you. But if you do use some of these apps, you'll find that they often refuse to run.
How to pass SafetyNet:
You will need Magisk and Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You will need this ZIP:
https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680
After you have downloaded both of these, go ahead and flash Magisk through TWRP. After installation is complete, Go to the Modules section in Magisk Manager and press the + button and select the SafetyNet spoofer ZIP. After it's done, reboot your phone. Then go to Settings in Magisk Manager and turn Magisk Hide off and then on again. Go to the Magisk Hide section and select the following apps to hide Magisk from:
Google
Google Services Framework
Google Play Store
(and other apps requiring SafetyNet to pass)
Then go to Play Store>Settings and see if it says your Device is certified. If not, clear Play Store data and try again.
Done! Now you will have passed SafetyNet!
Click to expand...
Click to collapse
I am on Lineage 15.1 based on 8.1, I followed every step you have mentioned but it shows ctsProfile : False and basicintegrity : true
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)
State of Magisk: 2021
State of Magisk: 2020
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.
MagiskThe Magic Mask for Android.
Magisk Links:
GitHub
Installation Instruction
Frequently Asked Questions
Magisk Documentation
Magisk Troubleshoot Wiki (by Didgeridoohan)
Release Notes
Download Links:
Stable and Beta releases.
GitHub
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.
Modules
MagiskHide Props Config
This module allows you to add, change and adjust prop values systemlessly using Magisk.
MagiskHide Props Config Links:
GitHub
xdaThread
Download Links:
GitHub
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:
GitHub
xdaThread
Download Links:
GitHub
Credits:
kdrag0n
All who contribute and support this project.
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:
GitHub
Download Links:
GitHub
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:
GitHub
Download Links:
PlayStore
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:
GitHub
PlayStore
Download Links:
GitHub
PlayStore
Credits:
RikkaW
All who contribute and support this project.
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.
Spoiler: Instructions
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.
Basic Attestation<Reserve>
Older devices that can not support hardware attestation there are other options.
Enable Zygisk.
Enable Denylist.
Add com.google.android.gms.unstable to the Denylist.
Add com.google.android.gms to the Denylist if needed.
Reset the sensitive prop values for the device.
Click to expand...
Click to collapse
Due to other modules and methods that require DenyList to be inactive, this method is more for reference.
For ease of use and compatibility, I would recommend using the USNF module instead.
See the Force Basic Attestation post.
This post will be updated in a few days.
Adjust Prop values<Reserve>
Reset sensitive prop values.
Spoiler: Instructions
Download the MagiskHide Props Config module.
Open the Magisk app and select the Modules option.
Select Install from storage option.
Navigate to where you saved the MHPC module and select it.
When the install is done, reboot.
Open a terminal app (or adb shell) and type props in the command line.
Make sure to grant root access
Select the Edit MagiskHide props (active) option.
(Currently option number 4)
It will show you the sensitive props that need to be adjusted.
If they all show (active) no changes needed.
If there is a prop value that shows as (enabled, not active) then you need to activate it by selecting it or a for all.
You will be prompted to set MagiskHide sensitive props?
Enter y(es), n(o) or e(xit):
If you are using a custom rom, you might also have to adjust the build fingerprint and security date.
From the MHPC main menu select Edit device fingerprint option.
(Currently option number 1)
Select Pick a certified fingerprint option.
(Currently option f)
Select the latest certified print for your device.
If your device is not listed, choose a device that is close to yours.
This post will be updated soon.
NotesandCommon Issues<Reserve>
Spoiler: SafetyNet
<Reserve>
Spoiler: Play Protect certification
<Reserve>
Spoiler: PlayStore App Purchases and Updates
<Reserve>
Points of Interest.
LSPosed
Zygisk releases are now included.
Download Links:
GitHub - Releases
Shamiko
Download Links:
GitHub - Releases
Denylist Unmount
Download Links:
GitHub - Releases
Yay! I get post no. 10!
Good to see this thread up Doc! ... How are you linking / promoting it?
Want mentions in Magisk General Discussion thread, or not for now?...
I note that this thread has the advantage of having an active OP...
So what? - Means I can post rubbish and it will be cleaned! ... Love a clean house... Hope you're a good housekeeper @ipdev! PW
zputnyq said:
Hi all,
I'm on TJW's canary 23019.
Does anyone know/could explain what is/are the difference(s) with enforce denylist activated and not activated ?
Click to expand...
Click to collapse
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!
pndwal said:
denylist (which preserves some of MagiskHide infrastructure) is active, or not active...
Nb. For Zy-Shamiko hiding module solution to work, this needs to be deactivated for Shamiko to do the hiding itself; Shamiko just uses the same list for convenience / simplicity... PW
Edit: Lets kickstart things here!
Click to expand...
Click to collapse
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
zputnyq said:
Ok, I get it. Thank you.
I was confused since I use an old device which doesn't really need this part to do the hiding & on v23017 John made that part work along with the configure denylist, I mean configure denylist is greyed out when denylist part isn't active.
Click to expand...
Click to collapse
You could do worse than read the first 5 posts here! PW
Thanks @ipdev
I tried to put a short help for probably the most frequent posts/questions soon to expect.
(Sorry for cross-posting, I first put to the old and cluttered General Magisk thread but this is now better place)
===
Please carefully read Magisk Changelog and OP posts in this thread
Study the Magisk documentation from the official Magisk Github page - particularly about installing Magisk (if not familiar with patching the image in Magisk app and flashing the patched img from Fastboot- different from the old school about flashing Magisk zip through TWRP)
a) No more MagiskHide. New technology instead (for more or less the same - to help hiding root): Zygisk+DenyList
b) No more built in SafetyNet checker. Install from PlayStore e g: YASNAC to check your SN
c) Modules window does no more connect to the old Modules repository.
You must download module zip files manually and "Install from local storage".
Or search for and install Fox Magisk Module Manager (Fox Mmm) app - it will connect to the new, alternative repository and the old 'official' repo, allowing you to install from both
---
0) If upgrading Magisk and if you previously did "Hide Magisk app/Mngr" from Magisk app/mngr - always "Restore Magisk app/Mngr" before upgrading Magisk
1) Make sure that both Magisk app and Magisk are installed and updated to the new version v24 version. Inspect version numbers on the main Magisk window/page
2) Make sure to uninstall all Riru modules (Riru is not compatible with Zygisk that comes with Magisk v24)
3) Settings, Enable Zygisk and reboot.
Then check on the main window does it show Zygisk Yes
4) Settings, enable Enforce DenyList.
Configure DenyList, enable filters to Show OS and System apps.
Find Google Play Services and check-in only the two processes ending with gms and gms.unstable.
You will have to check in all your banking apps and so as you used with MagiskHide.
Always reboot upon reconfiguring DenyList
5) If SafetyNet does not pass, install USNF 2.2.1 and test again.
Always reboot upon installing a module, also if/when you enable Systemless Hosts
Note: Once you install/enable USNF 2.2.1, it will remove Google Play Services from your DenyList - but don't worry, USNF takes care of GMS
6) If you are on non-certified custom ROM and you still don't pass SN - then you will need Magisk Hide Props Config module - check for and consult the MHCP thread
---
If you want to hide Zygisk, then instal Shamiko module - and you must disable Enforce DenyList (although DenyList must stay configured).
But Shamiko is really not essential (might help for some banking apps but it's irrelevant for SafetyNet)
---
Banking apps - out of scope for this post (also, this thread is about the Magisk v24 itself, not abkut the particular banking apps)
Go to Magisk Github documentation, read Wiki, there is a section with tips you should try first
If putting your banking app to DenyList (now, instead of the old Magisk Hide) and hiding Magisk app does not help, and the other tips from Wiki do not help (like renaming TWRP folder and so), search in this thread how to use Hide My Applist (Zygisk-LSPosed module)
Every time you apply another tip to your troublesome banking app - go to Settings, Apps, and delete Cache and Data for that banking app before you try to open it again (some apps will cache that they previously found the phone was rooted)
Even with HMA, there are certain banking apps that cannot be tricked (on some phones like Xiami, etc)
---
Momo - absolutely not essential for your life
When you pass SN, Momo might still detect that your Bootloader is unlocked - you cannot hide it from Momo on e.g. Xiaomi phones
Generally, treat Momo as 'banking' apps (add to DenyList and reboot)
Momo does not look for apps (Magisk app, LSPosed mngr, LSPosed modules), hence for Momo you don't need to bother with HMA
Basic tips for Momo: Remove/rename TWRP folder, disable USB Debugging - for the rest, search for Momo posts in this thread - but still, there will be findings you could not hide from Momo (not encrypted Data, custom ROM, etc)
===
PS: Magisk Alpha v24.1 (vvb2060 and her team) has departed their way (different package name, revival of MagiskHide?), hence this post is now (mainly) for the official TJW Magisk Stable and Canary v24
(Some parts do apply also to Alpha but use Alpha on your own risk and ask the other Alpha users about the Alpha status and practices)
===
Last but not the list - there night be specifics for certain phones (like flashing with Odin for Samsung, end so on)
This post is generic, for your specific practices read/search through this thread and also on your phone/model subforuns on XDA
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris
@ipdev
Thread was pinned. Thx for your effort
Nice. Will we be able to run a module like fakegapps without riru/LSPosed?
crypticc said:
Hello - sorry if obvious but I'm having issues getting some apps checking for root to pass. I think the issue might well be the statement related to "Google Play Services and check-in only the two processes ending with gms and gms.unstable."
Regardless of whether I tick just these two, or if I tick the whole of Google Play Services, once I reboot and if I go back into Magisk the app reports that these services are no longer hidden.
This is Pixel6Pro Stock, January update, Magisk canary (but 24001 that synced with the public build) + Zygisk + USNF 2.2.1
Thank you
Chris
Click to expand...
Click to collapse
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
kurtn said:
Nice. Will we be able to run a module like fakegapps without riru/LSPosed?
Click to expand...
Click to collapse
Yes, Use Zygisk-LSPosed. PW
pndwal said:
No, you don't need to add Play Services processes w/ Zy-USNF as I explained here:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-86321879
Download YASNAC and check if you pass SafetyNet, then that you have Play Protect Device is certified in Play Store settings... If you have these, Bank app is using its own custom detection methods... PW
Click to expand...
Click to collapse
Yes I appreciate that. I guess my question was if it is correct that after reboot USNF deselects the gms and gms.unstable
Thanks for the explanation.
FYI found what was triggering the app and got it working. Before I had just renamed Magisk (I renamed to MagicApp if that matters) but that didn't work. Also "pausing" the app wasn't enough.
I needed to actually uninstall the Magisk Manager app itself.
So the mechanism being used by the other app wasn't looking for Magisk/SU, but the app iself.
The App failing doesn't have any local file permissions so must've been something else.
Actually I found two apps failing root check and both were resolved by uninstalling the (renamed) Magisk APK.
So I wondered if the app was simply listening to debug messages.
So I reinstalled and then reproduced the failure looking into ADB logcat.
I could see during opening and just before the protection was triggered logcat events against the ".Magisk" app related to denying access. Uninstalling Magisk app stopped those messages and then the app was able to start.
Should Magisk "hiding" the magisk manager app by renaming it from ".Magisk" also have relabelled all of the messages and such related to the app?
Hi all
I have samsung galaxy a22 5g rooted with magisk and my local government app service nsw which carries a bunch of licenses and stuff I need for work is unaccessable now. It says die to not using official software.
Is there something I can do to get this app working with magisk root?
TIA
Try to use magisk hide, which is in the app
Champdroid said:
Is there something I can do to get this app working with magisk root?
Click to expand...
Click to collapse
I think Magisk v23 stable was the last release with MagiskHide. For newer releases Zygisk to the rescue...
[Discussion] Magisk - The Age of Zygisk.
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...
forum.xda-developers.com
You'll probably need the safetynet-fix and Props Config modules.
In Magisk v24 enable Zygisk along with Enforce DenyList then Configure DenyList and select the app. You may need to uninstall the app and reinstall, then add it to DenyList before starting the app fresh. An alternative to reinstalling that usually works is clearing the app's storage in Settings/Apps.
If the app still won't play ball it may not be possible to spoof it.
manjaroid said:
I think Magisk v23 stable was the last release with MagiskHide. For newer releases Zygisk to the rescue...
[Discussion] Magisk - The Age of Zygisk.
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...
forum.xda-developers.com
You'll probably need the safetynet-fix and Props Config modules.
In Magisk v24 enable Zygisk along with Enforce DenyList then Configure DenyList and select the app. You may need to uninstall the app and reinstall, then add it to DenyList before starting the app fresh. An alternative to reinstalling that usually works is clearing the app's storage in Settings/Apps.
If the app still won't play ball it may not be possible to spoof it.
Click to expand...
Click to collapse
^
manjaroid said:
I think Magisk v23 stable was the last release with MagiskHide. For newer releases Zygisk to the rescue...
[Discussion] Magisk - The Age of Zygisk.
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...
forum.xda-developers.com
You'll probably need the safetynet-fix and Props Config modules.
In Magisk v24 enable Zygisk along with Enforce DenyList then Configure DenyList and select the app. You may need to uninstall the app and reinstall, then add it to DenyList before starting the app fresh. An alternative to reinstalling that usually works is clearing the app's storage in Settings/Apps.
If the app still won't play ball it may not be possible to spoof it.
Click to expand...
Click to collapse
Legend that did the trick. Thank you very much.
This is not an officially supported topjohnwu project.
If you are looking for official Magisk source, please go to this page
Introduction
Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide.
http://huskydg.github.io/magisk-files
REPORT BUG IS STILL ACCEPTED ON XDA THREAD BUT PLEASE INCLUDE ADDITIONAL INFORMATION SUCH AS LOGCAT AND MAGISK LOG
.
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
Keytrade Bank is working with Delta / magiskhide
do you have enforce or permissive?
try to flash momohider module or join telegram group we have husky files to flash
you dont need to hide magisk app and you should flash safetynetfix 2.1.3 riru
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
It's working on OOS 11.0.8 on my OP7 Pro. Your problem comes very probably from the hidden Magisk. If that doesn't solve it, Riru + Riru MomoHider should do the trick
Timmmmaaahh! said:
Hidden Magisk 25.1-delta (25100)
Click to expand...
Click to collapse
Try not to use "Hide the Magisk app" option
Timmmmaaahh! said:
Good day @huskydg! Delta has been running all things smoothly on my end except for the Keytrade Bank application.
I've briefly mentioned it before over here but I think this might be a better place to find a solution. I'm trying to avoid LSPosed but if there's no other solution I'll go for that anyway.
Any ideas are most welcome! Thank you for your time.
OnePlus 6T
OOS 11.1.2.2
Hidden Magisk 25.1-delta (25100)
Zygisk disabled
MagiskHide enabled
DenyList checked for pretty much all Google/Gov/Financial apps and com.google.android.gms
Click to expand...
Click to collapse
I installed this app out of curiosity on two my devices: 1) Xiaomi Redmi Note 4 with custom ROM Android 10, rooted with Magisk Delta 25.1 (using Riru, LSPosed and MagiskHide); 2) Xiaomi Mi Note 10 with Xiaomi.eu ROM Android 11, rooted with official Magisk 25.1 (using Zygisk, LSPosed and Shamiko). And what I observed:
1) On the first device with custom ROM I was not able to fool Keytrade Bank app even with using MagiskHide enabled, repackaged Magisk Delta app, (I know it's rather redundant, but just in case , hidden LSPosed manager and using HideMyApplist properly configured. I suppose it may be involved with the old security patches because my ROM isn't being updated for Android 10 anymore.
2) On the second device I couldn't fool Keytrade app until I used HideMyApplist LSPosed module. It suggests that Keytrade is looking for a specific packages installed... Then by a process of elimination I determined it was the HideMyApplist app itself which causes the Keytrade app to crash! But since you dont have LSPosed installed at all, maybe there is another package which Keytrade app is looking for... Anyway, looks like running Keytrade is possible even with official Magisk and Shamiko (maybe even with Enforce DenyList as well)
EDIT: Pardon, it turned out that with only HideMyApplist app hidden Keytrade crashes after a while too. But I have 13 different apps with root access hidden with another template and with that applied to Keytrade I'm able to start a profile creation process
Sir, i tried using this app in zenfone max pro m1 with latest masgik v25 with zygisk enabled. So after giving super user request YES 2 times (it prompts for 2 prompts one after another) i opening settings and enabled "magisk hide" and did reboot device.
But after reboot the root request automatically resets and i've to redo procedure again
BUT after disabling zygisk the root request reset issue didn't happened. So i did add the "instabiz ,My jio" apps to test if it detects root or not , but it still detects root.
SO how do i make it work ?
akhil17kr said:
Sir, i tried using this app in zenfone max pro m1 with latest masgik v25 with zygisk enabled. So after giving super user request YES 2 times (it prompts for 2 prompts one after another) i opening settings and enabled "magisk hide" and did reboot device.
But after reboot the root request automatically resets and i've to redo procedure again
BUT after disabling zygisk the root request reset issue didn't happened. So i did add the "instabiz ,My jio" apps to test if it detects root or not , but it still detects root.
SO how do i make it work ?
Click to expand...
Click to collapse
after enable magiskhide
flash riru module
flash safetynetfix 2.1.3
go to denylist , add google services
reboot
add apps to denylist
pitelasssss said:
after enable magiskhide
flash riru module
flash safetynetfix 2.1.3
go to denylist , add google services
reboot
add apps to denylist
Click to expand...
Click to collapse
which riru module to flash ? also do i need to disable the zygisk in order to use this app as with zygisk enabled the root request resets.
akhil17kr said:
which riru module to flash ? also do i need to disable the zygisk in order to use this app as with zygisk enabled the root request resets.
Click to expand...
Click to collapse
if you want to use delta with magiskhide disable zygisk
https://github.com/RikkaApps/Riru/releases/download/v26.1.6/riru-v26.1.6.r527.cdcb9f34c6-release.zip
https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.3/safetynet-fix-v2.1.3.zip
work perfectly fine with Livin, but i can't open Jago app.
Magisk Hide enabled
safetynet-fix 2.1.3
Riru - MomoHider
Lord Sithek said:
(...) Then by a process of elimination I determined it was the HideMyApplist app itself which causes the Keytrade app to crash! (...)
Click to expand...
Click to collapse
OMG, that's it!! How stupid of me. I had reinstalled HideMyApplist but couldn't configure it as it needs LSPosed and forgot about it. After uninstalling, Keytrade immediately worked! Thank you!
Timmmmaaahh! said:
OMG, that's it!! How stupid of me. I had reinstalled HideMyApplist but couldn't configure it as it needs LSPosed and forgot about it. After uninstalling KeyTrade immediately worked! Thank you!
Click to expand...
Click to collapse
Haha, glad I could help!
LSPosed has released new Shamiko which fixed Found zygisk for latest Momo but the banking apps that won't run with zygisk enabled like Livin by Madiri still not open.
Releases · LSPosed/LSPosed.github.io
Contribute to LSPosed/LSPosed.github.io development by creating an account on GitHub.
github.com
razael25 said:
work perfectly fine with Livin, but i can't open Jago app.
Magisk Hide enabled
safetynet-fix 2.1.3
Riru - MomoHider
Click to expand...
Click to collapse
nvm, its worked now
Tried Magisk Delta and sure enough it did pass the Instapay app. Used magisk hide, randomize package name, riru, momohider, unshare, and safety net. Downside is even though I have safetynet module, still can't pass basic attestation and somehow I broke momo app. For the momo app, I should only have init.rc as the failed test 'cause somehow momo can't see device is custom ROM and unlocked bootloader. Weird.
Edit: Safetynet passed, I just forgot to add gms and gms unstable in denylist.
BigChungus321 said:
Tried Magisk Delta and sure enough it did pass the Instapay app. Used magisk hide, randomize package name, riru, momohider, unshare, and safety net. Downside is even though I have safetynet module, still can't pass basic attestation and somehow I broke momo app. For the momo app, I should only have init.rc as the failed test 'cause somehow momo can't see device is custom ROM and unlocked bootloader. Weird.
Click to expand...
Click to collapse
Hide google gms from magisk denylist ,
restore magisk app with original name ,
instapay you need Egypt location to fully load the app, use Vpn if you want to try
momo app will show environment is broken with magiskhide
Will Shamiko work with this custom Magisk? I know Shamiko needs Zygisk enabled. But it also needs "enforce denylist" disabled. However, this app doesn't have that option. So, does this app enforce denylist or does it not enforce it? Since there is no toggle for this setting.
AnonVendetta said:
Will Shamiko work with this custom Magisk? I know Shamiko needs Zygisk enabled. But it also needs "enforce denylist" disabled. However, this app doesn't have that option. So, does this app enforce denylist or does it not enforce it? Since there is no toggle for this setting.
Click to expand...
Click to collapse
MagiskHide toggle is DenyList toggle
MagiskHide will keep zygisk to be loaded for apps on denylist
Shamiko will work even it say it's not working. It say it is not working because it receives denylist_enabled flag sent by zygisk.
And.. If you use shamiko, why not use official magisk.
I think your banking app will work fine without shamiko if it doesn't detect zygisks. Shamiko cannot completely hide zygisk.
I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.
mcichy10 said:
I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.
Click to expand...
Click to collapse
I have the same issue since today on Galaxy s21 Ultra!
I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.
mcichy10 said:
I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.
Click to expand...
Click to collapse
try using Shamiko together with Zygisk and without forcing the denylist
I tried this before with zero success
With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.
neelchauhan said:
With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.
Click to expand...
Click to collapse
yup, I did that. Didn't work for me.
I performed "Format Data", flashed latest MIUI for my device, installed Magisk, Hided Magisk, activated Zygisk, Forced deny list and it's working well.
i tried like 4 different ways and NONE work
Universal SafetyNet Fix (didnt work)zydisk (didnt work)
denylist (didnt work)
magiskhide proops config (didnt work)
i have a mi 9 with miui 13+android 12
EDIT: it just takes trial and error, had to try a couple of different devices and one that worked for me was mi 9 europe
I can pass safety net on magisk 25.2 . I don't install magisk hide props. I have few things installed and a modified Verison of universal safety fix and I am using zygisk.
Alot times I forget about messages on here . Telegram me if I don't get back to u on @Assassin4Hire
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.
yot2703 said:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.
Click to expand...
Click to collapse
I tried this workaround in my Samsung SM-G531H with Android 7.1 and I tested it with the previously mentioned YASNAC app, and the SafetyNet Attestation tests (Basic Integrity and CTS profile match) PASSED!
Now, I'm able to use my bank app (BBVA) Thanks.