After some trial and error, I have found the secret sauce which allows you to disable EdXposed's app list mode and still pass SafetyNet. This means I am one step closer to having a fully customized & still-secure phone (bootloader re-locking is probably going to happen in the coming weeks - stay tuned ). But what it also means is that I can write a post to share this new knowledge with all of you!
I am sure this advice will become dated soon enough. However, right now, there is still a way to have proper system-wide EdXposed without tripping SafetyNet.
After installing the latest Riru, run touch /data/adb/riru/enable_hide and reboot. This will enable "hidden" mode, which... does something with /proc that I don't care to understand. The point is that now it is much easier for EdXposed to hide its presence, since the hooking framework it's using is now doing so properly.
Then, install the latest canary version of EdXposed YAHFA. SandHook only passes SafetyNet when all modules are disabled, however... YAHFA passes SafetyNet regardless. YAHFA simply doesn't care. That means if you have your MagiskHide set up correctly, and you're not using a module like HiddenCore which intentionally ****s with the response signature, you will have fully passing SafetyNet with EdXposed. You will NOT have to enable app list mode to blacklist Google services. That means XPrivacyLua (and other modules too) will work on them. Just be careful not to use any modules which intentionally screw with SafetyNet
If you're willing to take the slight performance hit that comes with using YAHFA over SandHook, it may be something to try. The 7 Pro is a pretty fast phone, and the second or two of delay when starting up a launcher for the first time (for example) is much more acceptable compared to the 10 seconds or so of "Phone is starting..." you have to endure on competing phones, even without EdXposed.
the enable_hide option in the riru folder is not available on my phone.
Auel Yakubu said:
the enable_hide option in the riru folder is not available on my phone.
Click to expand...
Click to collapse
What do you mean it's not available?
LoganDark said:
What do you mean it's not available?
Click to expand...
Click to collapse
When i go into the /data/adb/riru/ folder on my phone then i don't see the enable_hide file inside it.
Auel Yakubu said:
When i go into the /data/adb/riru/ folder on my phone then i don't see the enable_hide file inside it.
Click to expand...
Click to collapse
Yes, you're supposed to make one. That's what enables hide.
The touch command creates a blank file
Would you kindly provide further explanation !
how to run that
touch /data/adb/riru/enable_hide
mahaseno said:
Would you kindly provide further explanation !
how to run that
touch /data/adb/riru/enable_hide
Click to expand...
Click to collapse
Download Termux, run su to enter a root shell, and then run that touch /data/adb/riru/enable_hide
i did that
and give me : not found!
mahaseno said:
i did that
and give me : not found!
Click to expand...
Click to collapse
Could you provide a screenshot please?
i'm not using canary version by the way
mahaseno said:
i'm not using canary version by the way
Click to expand...
Click to collapse
Oh whoops. Hide is only supported in the new version of Riru, the one that says "Riru" instead of "Riru - Core".
screenshot
mahaseno said:
screenshot
Click to expand...
Click to collapse
You forgot the space after touch.
LoganDark said:
Oh whoops. Hide is only supported in the new version of Riru, the one that says "Riru" instead of "Riru - Core".
Click to expand...
Click to collapse
i'm sorry
what do you mean?
this what i have installed
mahaseno said:
i'm sorry
what do you mean?
this what i have installed
Click to expand...
Click to collapse
You have to remove EdXposed and reinstall the latest canary version (YAHFA version). You have v4 which doesn't support your version of Riru
link please ?
aha you mean from inside edxposed ?
mahaseno said:
link please ?
Click to expand...
Click to collapse
There are no links.
Here's what you do:
Go into Magisk Manager and remove your EdXposed module.
Reboot.
Open EdXposed Manager, and wait a few seconds. A Canary tab should appear on the top.
Go to the Canary tab. At the top, there should be a drop-down with two options: SandHook and YAHFA. Choose YAHFA and press install.
You will be redirected to your web browser which will download a zip file. This is a Magisk module you must install from storage. (Technically, this is a link, but please do not post it here as the EdXposed Manager will know the latest version automatically.)
After all that, your EdXposed should be up to date.
OK bro i will try it now
hope it will work
my phone stuck after booting
i will remove this version from recovery
thx for help bro
Related
Resently BDS banking app(India) is updated.is there any modules to make that work...
Aniruddhlr said:
Resently BDS banking app(India) is updated.is there any modules to make that work...
Click to expand...
Click to collapse
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that
manor7777 said:
This isn't xposed, so probably not. As long as your passing safetynet and enabled magisk hide for that and rebooted, in theory you should be fine. The next thing you can try is force closing the app and in Magisk manager, tapping "hide magisk manager" but that's only a temporary fix, some apps now check to see if magisk is installed at all. This will fix that
Click to expand...
Click to collapse
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
Thank you.ill try and tell you results.
Aniruddhlr said:
Magisk is installed and passes safety net.
Still many banking apps detected root like BHIM.
And is there any way to hide custom ROM?
Click to expand...
Click to collapse
manor7777 said:
You can make a script to change the build information in the rom to release-keys instead of test-keys, some apps detect that. Also make sure you tick your banking app in Magisk hide settings. I believe there is a module so ewhere on the forum to do this, I will link it if I see it. Also you can try universal safetynet bypass module
Click to expand...
Click to collapse
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.
Didgeridoohan said:
MagiskHide already changes the prop to release-keys (and some other props). And since SafetyNet already passes there's no need for the Universal SafetyNet Fix module.
Only thing to do is to add the app to the Hide list (no module needed for that) and also hide the Magisk Manager (there's an option for that in the Manager settings). Also make sure to use the latest release (currently v14.6 beta) since there's often improvements being done.
It's also possible that the app detects things like Developer options and USB Debugging being enabled. That can't be hidden by Magisk, so try disabling those if they're enabled.
Click to expand...
Click to collapse
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.
It's saying runtime tampering.what does it mean?
Aniruddhlr said:
Yeah just now I saw that release keys in build prop.
I'm not on beta is it safe to install beta(magisk).
I'll try those debugging things.
Click to expand...
Click to collapse
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
Aniruddhlr said:
It's saying runtime tampering.what does it mean?
Click to expand...
Click to collapse
What is saying that?
https://i.imgur.com/e2rAlNI.png
Didgeridoohan said:
Beta is safe... The worst that can happen (that I've seen so far) is a bootloop that can be fixed by flashing a clean boot image or an earlier release (v14.5).
There might also be problems with the su database, but that should be fixed by uninstalling the app (from within the Manager, press Uninstall and choose Uninstall App) and reinstalling it.
It's worth it, since the Hide feature is much improved in v14.6.
---------- Post added at 12:21 ---------- Previous post was at 12:21 ----------
What is saying that?
Click to expand...
Click to collapse
I added a image.see
Aniruddhlr said:
I added a image.see
Click to expand...
Click to collapse
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.
Didgeridoohan said:
Hello again.
Yes, I saw the image... But, the only thing you could try is to update Magisk and use the improved hiding features.
There are a few issues with the latest stable v15.0. Many Samsung and Huawei users are experiencing bootloops and some users have had forced encryption issues. Don't think I've seen any issues mentioned for Xiaomi devices though... Just make sure to have a backup and the latest Magisk uninstaller zip available and you should be good to go.
If you're feeling unsure about updating, wait... The issues are under investigation.
Click to expand...
Click to collapse
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?
Aniruddhlr said:
Thanks for that warning.
I already updated to 15v and found forced encryption issue.
Does runtime tampering have anything to do with this root?
Click to expand...
Click to collapse
Have you gotten v15.0 up and running? If not you could try again and uncheck "Preserve forced encryption" in the Manager before updating, or if you're flashing from recovery you could run the following code in the recovery terminal first:
Code:
echo KEEPFORCEENCRYPT=false>>/data/.magisk
Runtime tampering is probably just DBS's way of saying your device is rooted.
After getting v15.0 running, add the app to the Hide list and hide the Manager (option in settings). You might also have to clear data for the DBS app.
Also make sure that MagiskHide is working by checking SafetyNet. If at least basic integrity passes we know it does. If it doesn't, toggle MagiskHide off and on in the Manager settings and try again.
Hi, I am also facing same issue. My device is Zuk Z2 and am on Dot-OS rom. Magisk passes SafetyNet, have enabled Magisk Hide but still this DBS bank app detects root.
I also tried after disabling Developer options. Same error. What extra can be done?
+1
I need access to this app too whilst rooted with Magisk
tomdot said:
+1
I need access to this app too whilst rooted with Magisk
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
DBS banking app finally works with Magisk 16.0 (with Magiskhide)
Mine can't work.. there no error code appearing when opening the app but the app hangs at "log in " and "register" page.. anyone can help please
I'm using ressurectiin remix on redmi note 5
tomdot said:
DBS banking app finally works with Magisk 16.0 (with Magiskhide)
Click to expand...
Click to collapse
yes it's work for me,
1st i check it in my hide list
and then i hide my magisk
if only i did my 1st choice it still give some warning and force close the app
thanks
Hi everyone,
I just rooted (my 1st root) my pixel 4 yesterday to activate the soli module as in my country it doesn't work otherwise.
Soli is now working, but some app (like Netflix) cannot be used even after installing the APK from some APK database.
After looking online I understood that this was because of the safetynet checks, which are both failed (ctsprofile and basicintegrity)
Unfortunatelly, I haven't found any thread to fix it except some old for older versions or mentioning TWRP which i didn't use.
I have only 3 modules installed: Riru Edxposed / Riru Core and MagiskHide props config (and the check of all google playservice addresses in the module)
Can someone help me on that?
Thanks !
Seems like Google started detecting EdXposed yesterday, but this can be worked around by adding some Google components to the EdXposed blacklist. Take a look on the EdXposed Github for details.
Didgeridoohan said:
Seems like Google started detecting EdXposed yesterday, but this can be worked around by adding some Google components to the EdXposed blacklist. Take a look on the EdXposed Github for details.
Click to expand...
Click to collapse
The check is now green for both, thanks
But i can't still use netflix (app will remain on the logo for ever).
I tried to rename the liboem file with a root explorer but the file is not present in the folder in system\lib\ or \lib64
frikadel said:
The check is now green for both, thanks
But i can't still use netflix (app will remain on the logo for ever).
I tried to rename the liboem file with a root explorer but the file is not present in the folder in system\lib\ or \lib64
Click to expand...
Click to collapse
Hi,
Coul you please tell me if you are on custom rom?
I am on custom and only way to pass is to use Props Module in Magisk. But the Props is not loading when Riru EdXposed is active.
Thank you,
amplatfus
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
SmilingPerson said:
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
Click to expand...
Click to collapse
Hi,
Tried. It is not working. Still searching.
Thanks!
amplatfus said:
Hi,
Tried. It is not working. Still searching.
Thanks!
Click to expand...
Click to collapse
Yep, I recently went from rooted stock to LineageOS 16 on my phone, and can no longer use Netflix. My rooted Android media boxes also run LOS and Netflix *does* work on them, so I am perplexed. I can run the (terrible) remote control app for my Toyota by simply hiding things in Magisk and adding it to the blacklist in EdXposed Manager, otherwise it will complain about the phone being rooted. That works, but Netflix does not.
I don't need Netflix on my daily driver telephone, so no loss, but it tells us that whatever Google is doing, it is beatable. I just don't see the common ground though, it almost seems like it is device dependant. Next time I install Netflix, I am going to face due north, chant the Canadian anthem, and touch my nose with my right index finger while clutching a rosary in my left hand. Maybe that will be the ticket.
Sent from my unknown using Tapatalk
SmilingPerson said:
I just posted this on Github, kinda curious if it helps with Google Pay. I had never heard of this module before:
Has anyone tried the Hidden Core module in EdXposed? It is passing SafetyNet for me without any blacklisting or switching modes, just install and reboot.
For posterity, I am running EdXposed YAHFA 0.4.5.1. EdXposed Manager 4.5.1 under Magisk v20.1 / Android Pie.
https://ibb.co/xLBxDDV
https://ibb.co/F6y1hcH
Click to expand...
Click to collapse
You're a great bro !! after having installed the module on EdXposed and restarted my redmi note 4x (mido) with EAX Os 6.7, both the ticks were of a magnificent green! many thanks! :victory::victory::victory:
公司业务-中国工商银行手机网站
m.icbc.com.cn
中国工商银行手机网站
m.icbc.com.cn
helpppp!
Edit: Solved. Install Magisk 24.x. Hide Magisk app. Enable zygisk. Add ICBC app to Deny list.
try zygote?
Make sure it is on deny list, clear storage and cache, then reboot.
already done...
wrecklesswun said:
try zygote?
Click to expand...
Click to collapse
how?
anyone???? help!!!
try zygisk (magisk canary) with the denylist enabled, if not try zygisk + shamiko (module).
ok it seems you need to use something bankrx to use it for now, i hope magisk can built-in support soon
optionalmgrr.la said:
公司业务-中国工商银行手机网站
m.icbc.com.cn
中国工商银行手机网站
m.icbc.com.cn
helpppp!
Click to expand...
Click to collapse
What's your problem with this app ? For me, on Android 9.0 Pie, after hiding this application in Magisk hide, the application works correctly
Spartacus500 said:
What's your problem with this app ? For me, on Android 9.0 Pie, after hiding this application in Magisk hide, the application works correctly
Click to expand...
Click to collapse
which version and where u d/l from?
mine was upgraded and then it stopped working
optionalmgrr.la said:
which version and where u d/l from?
mine was upgraded and then it stopped working
Click to expand...
Click to collapse
Version 7.0.1.2.0
hiding magisk works now ,thx!
lol i can't get pass face verification during login
optionalmgrr.la said:
hiding magisk works now ,thx!
Click to expand...
Click to collapse
It disappeared after last update... I had to restore my phone to have it back.
What's wrong?
i dunno, i upgraded to v24 then use the "rename" function in magisk (make the app something other than magisk) and then use zyogte hide and now the icbc bank app works
but i cannot get pass face verification
optionalmgrr.la said:
i dunno, i upgraded to v24 then use the "rename" function in magisk (make the app something other than magisk) and then use zyogte hide and now the icbc bank app works
but i cannot get pass face verification
Click to expand...
Click to collapse
Thanks for your answer. How can I use zygote hide?
just enable it in magisk
its zygisk btw, sorry for the wrong name
optionalmgrr.la said:
its zygisk btw, sorry for the wrong name
Click to expand...
Click to collapse
Upps... I have Magisk. Do I have to install Zygisk?
I've tried Shamiko + Universal SafetyNet Fix and ICBC still doesn't work on latest Magisk 24.1
misosofos said:
Upps... I have Magisk. Do I have to install Zygisk?
Click to expand...
Click to collapse
built in in magisk 24, just update magisk and goto settings
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
KaoDome said:
I just realized there was a new public Magisk release yesterday, v24, and reading through the changes I see there are two that kind of impact me: MagiskHide and the central module repository removals.
So far I had been using MagiskHide because of its ease of use, list apps, tick box, and that's it (I haven't encountered apps that detected Magisk or root status, although I know it's insufficient for some). For modules, for example, the one that moves user certs to the system store, I just searched directly from the Magisk app and it was all good as well.
But things change from now on with those things being deprecated and removed and because there isn't much to go about in the release notes I was wondering if someone could direct me to the way of doing things now.
- What's the most apt, prevalent, or recommended replacement for MagiskHide? From the release notes I gather its a module, but I'm clueless as to which one or whether there are more than one option.
- If searching for mods and directly installing them is not available through the app, is there anything like it? Or is it all manual now? I.e. look for a module around the net, download it, copy it / decompress it somewhere in the device and install it.
Thanks for everything!
Click to expand...
Click to collapse
[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
Here. First 5 post and you should know all you need
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Quantumrabbit said:
So, I read through that thread. It certainly solved a few issues for me. Like getting safety net, getting a repository, etc.
But it didn't have anything I see to replace magisk hide, even in the Fox Magisk Module Manager.
Do I just need to know other terminology now? Or is there something else I'm missing?
Click to expand...
Click to collapse
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.
Click to expand...
Click to collapse
Porpet said:
I don't get it, Magisk Hide is good for passing SafetyNet and you said you got it. Anyway, for SafetyNet you can use the Universal SafetyNet Fix module.
If you meant the hide list, there's now the Deny list. To quote:
Click to expand...
Click to collapse
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Quantumrabbit said:
Yes, it's for some banking apps, Concur, and others, none of which have any business checking for root, but all check for Magisk and such in other ways, and prevent usage.
If the deny list is how to do that now, I'll give that a go. Thank you
Click to expand...
Click to collapse
And where did you find the deny list?
fusk said:
And where did you find the deny list?
Click to expand...
Click to collapse
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
H
toolhas4degrees said:
Settings enforce deny list. You need to enable zygisk and reboot prior also in settings.
Also there is an add on module shamiko that has more hide features after you configure denylist
Click to expand...
Click to collapse
How to add modules shamiko & how to more hide features
Spartacus500 said:
H
How to add modules shamiko & how to more hide features
Click to expand...
Click to collapse
Shamiko is a flashable only need to slash magisk module. You can find it in the magisk alpha thread on telegram. You need to configure denylist first and reboot then turn off the enforce denylist toggle and flash the shamiko module.
If you are using lsposed download hide my applist xposed module and search how to use it if you want more coverage
Pm me if you want links
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Drakinite said:
I'm having a lot of trouble. Duo Mobile (a 2FA app) is still able to detect that I'm rooted. Here's what I've done:
1) Installed Magisk & Manager app version 24.1 (24100)
2) Enabled Zygisk (and rebooted of course)
3) Enabled Enforce DenyList
4) Added com.duosecurity.duomobile and ALL Google Play Services submodules to the DenyList
5) Installed Universal SafetyNet Fix v2.2.1 from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
6) Hidden the Magisk app
7) Completely uninstalled & reinstalled Duo Mobile (and verified that it's still on the DenyList
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
This is quite weird and definitely shows how different devices handle root detection. I a Samsung S10+ and just installed Magisk 24 with enforce DenyList earlier this week. Today I just installed Duo Mobile and it works fine. I do not have it in the DenyList, and Magisk is not hidden. I use a custom SafetyNet fix that was installed when I originally installed an AIO TWRP/Magisk/SafetyNet fix after unlocking my bootloader. I also fail SafetyNet checks.
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Drakinite said:
This is incredibly annoying, is there anything I'm doing wrong? Is there a way to verify that the SafetyNet Fix is working as expected? Magisk doesn't have a "Check SafetyNet" option on the app anymore.
Click to expand...
Click to collapse
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
danbest82 said:
Have you tried Shamiko? It didn't help me pass SafetyNet so I removed it.
Unfortunately I don't have any other fixes for you but you can check SafetyNet with apps from the play store, I use YASNAC and SafetyNet 'attest'.
What phone are you using?
Click to expand...
Click to collapse
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
anonymous-bot said:
There are SafetyNet checker apps you can download from the Play Store or F-Droid such as YASNAC.
Click to expand...
Click to collapse
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
Get VD Infos and use it to scan your files. You can find it on XDA.
Drakinite said:
I'm using a Oneplus 6. At your suggestion, I tried Shamiko, but so far it hasn't worked.
Click to expand...
Click to collapse
Hmm ok. Like I said shimako didn't work for me either. I'm not sure why Duo is still detecting root. For reference this is what is on my DenyList:
Drakinite said:
I tried Momo from the Magisk alpha telegram channel, and it's been helpful so far, but it's detecting Magisk/TWRP files and I don't know where they are located. Is there a way to find where these files it's detecting are? This might be what Duo is detecting.
When I run YASNAC, it passes the SafetyNet check.
Click to expand...
Click to collapse
YASNAC is the replacement for Momo it looks like since Momo is Riru based (https://github.com/canyie/Riru-MomoHider)
simplydat said:
Get VD Infos and use use to scan your files. You can find it in XDA
Click to expand...
Click to collapse
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Drakinite said:
Ok so this one is more helpful, but I'm not sure how to hide these that appeared. Any idea what ro.kernel.qemu.gles is? I looked through my list of installed apps and nothing like that showed up.
Should we switch to private messages to not spam the thread? Or perhaps staying in here can be helpful for those with the same problem?
Click to expand...
Click to collapse
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Drakinite said:
OMG WAIT, it finally worked! I don't know what changed, but Duo is now no longer detecting root. Gotta love when things magically start working when you don't know what changed.
Click to expand...
Click to collapse
Awesome. Hope it stays that way!
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
antivirtel said:
Hi,
I've switched to the new method with the DenyList & Shamiko (v0.5.0) on OnePlus 6 recently - Magisk (v24.3), however it doesn't seem to hide root from Google Pay. Can it still be a bug with Magisk, when it can't hide system apps? In the changelog of Shamiko it mentioned that it was fixed in Magisk "24102+", I'm not sure what version is this, but I imagine it's not released yet. If so, is there a way of installing this version early?
Thank you!
Click to expand...
Click to collapse
Version 24102 would be v24.102. So your Magisk 24.300 is newer.
I made a big mistake yesterday. I saw threads about the new Play Integrity API thing and download the Integrity API checker. At that time, the integrity API checker cannot pass MEETS_DEVICE_INTEGRITY but my YASNAC can pass CTS profile. So I installed the Displex mod of the universal safetynet fix. I saw that my DEVICE_INTEGRITY passed but after testing a bit I found that it's not very consistent. Then after checking out the original repo knowing that there will be a release about this fix soon, I Installed back v2.4.0. This is when everything goes wrong. My device can no longer pass CTS profile. I tried wiping storage of the GAPPS, install back the modded module, remove Magiskhide props config. It is still not working. I cannot use my GPay now. Please help me get my GPAY back. Thanks for all the help.
To clarify my current setup, I have the modded v2.3.1_MOD2.1 installed now and props config removed.
Also a small question, do I need to wait for the device to get certified to get the CTS profile match or it should immediately work if everything is right.
seanho12345 said:
To clarify my current setup, I have the modded v2.3.1_MOD2.1 installed now and props config removed.
Also a small question, do I need to wait for the device to get certified to get the CTS profile match or it should immediately work if everything is right.
Click to expand...
Click to collapse
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.
manjaroid said:
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.
Click to expand...
Click to collapse
Yeah I already have USNF 2.3.1_MOD2.1 installed. However, my question is that is the CTS profile a prerequisite for the device to get certified or it should first get certified then the CTS profile match will work.
Hi
Im having sort of same problem, untill today my phone passed everything, gpay worked and all good..
from nothing it started to fail, not passing CTS profile match, gpay doesnt work.
tried everything, reinstalled magisk, reinstalled the modules, tried 2.3.1 mod, tried 2.4.0. Nothing works.
best i've achieved, is passing safetynet once, but after 2-3 min, it doesnt pass anymore.
any ideas what to do now?
manjaroid said:
safetynet-fix 2.3.1-MOD_2.1 should get you back on track. It's a popular topic today for those of us caught off guard.
Waiting for Play Protect certification should work but clearing storage for Play Store and Play Services will speed it up.
Click to expand...
Click to collapse
I'm Play Store certified but I don't pass CTS profile match
I am not sure if anyone has the same problem as mine. I configured magisk denylist as picture attached which included "play store service". The restarted the phone, went back to the denylist "play store service" gone
tinhsoftware said:
I am not sure if anyone has the same problem as mine. I configured magisk denylist as picture attached which included "play store service". The restarted the phone, went back to the denylist "play store service" gone
Click to expand...
Click to collapse
If you mean Google Play Services, that's normal and intended behavior if using a USNF mod. It's "denied" in the background.
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
seanho12345 said:
Can confirm that the new 3.0 MOD from Displax works flawlessly. I just installed it and everything is working.
https://github.com/Displax/safetynet-fix/releases/download/v2.3.1-MOD_3.0/safetynet-fix-v2.3.1-MOD_3.0.zip
Click to expand...
Click to collapse
I you still have issues with Banking / Wallet app (even passing SN checks) then install Shamiko Module, disable Enforce Deny List and try. This module takes charge of DenyList hidding Zygisk itself and Zygisk modules.
good morning
after maby 20 hours of hiding the magic by Shamiko moldes
itis ok
and fine
I have a Google Pixel 7 with Magisk V25.2, Universal SafetyNetFix V2.4.0 and I still can't install some apps and some other are not even visible in the results.
I've tried with and without the deny list (clearing cache and storage of Google Play service/store/protect), but nothing.
I've spent the last 2 days banging my head on the wall looking for solution, but...nothing.
Do you guys know something that works?
andrea_x said:
Do you guys know something that works?
Click to expand...
Click to collapse
Yes, Canary builds 25206 (831a398b) or 25209 (2717feac) and patch accordingly. Plus the modified safetynet-fix module.
manjaroid said:
Yes, Canary builds 25206 (831a398b) or 25209 (2717feac) and patch accordingly. Plus the modified safetynet-fix module.
Click to expand...
Click to collapse
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!
andrea_x said:
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!
Click to expand...
Click to collapse
Browse the repo and download app-release.apk. On a PC click the <> symbol to the right. If you're navigating from a phone tap the Browse files button to locate the file. I suggest caution and go with 25206. Anything after it has problems except maybe 25209, which worked ok for me but not for everybody. Once Canary is installed avoid the update button.
First, uninstall your current Magisk and restore init_boot.img back to stock. The phone is unrooted at this point.
Whichever Magisk release you install next, patch init_boot.img with that release. The phone should be rooted at this point.
Then your modules and Magisk configuration.
The safetynet-fix module you want is named safetynet-fix-v2.4.0-MOD_1.2.zip.
andrea_x said:
Wait wait, I'm not familiar with that, how do I get the APK or if it's a Magisk module where do I get the .ZIP?
And what do you mean with "patch accordingly"?
Thanks a lot!
Click to expand...
Click to collapse
magisk-files/canary.json at master · topjohnwu/magisk-files
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
ziddey said:
magisk-files/canary.json at master · topjohnwu/magisk-files
Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Thanks for your help, but I've installed and the "CTS profile match" test stil fails. and I still can't install some apps.
manjaroid said:
Once Canary is installed avoid the update button.
Click to expand...
Click to collapse
Thanks a lot fr your detailed explanation, you're very kind!
Buuut...the update button is exactly where the install button is, how can I patch the init_boot.img?
Should I really go back to the original init_boot.img first?
andrea_x said:
Thanks a lot fr your detailed explanation, you're very kind!
Buuut...the update button is exactly where the install button is, how can I patch the init_boot.img?
Should I really go back to the original init_boot.img first?
Click to expand...
Click to collapse
I don't know what's up with the buttons. Install is needed to select your file to patch. And yes, when starting over it's usually best to clean patch the boot image with the Magisk release that's running, although not always. If you don't mind posting a screen shot of Magisk it might help get a better perspective.
manjaroid said:
I don't know what's up with the buttons. Install is needed to select your file to patch. And yes, when starting over it's usually best to clean patch the boot image with the Magisk release that's running, although not always. If you don't mind posting a screen shot of Magisk it might help get a better perspective.
Click to expand...
Click to collapse
Here it is the screenshot