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
Related
Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I tested to make sure that magisk hide is working properly on my device. https://play.google.com/store/apps/details?id=com.revolut.revolut&hl=en_GB. This app does not have fingerprint login enabled without magisk hide. Hence when I turn off magisk hide, you can't use fingerprint to login into the app. When I turn it back on, fingerprint login works. Also my bank app works.
Here is the problem. https://play.google.com/store/apps/details?id=com.starlingbank.android&hl=en_GB. This app does not seem to run even when magisk hide is on. Here's the kicker, even though magiskhide has been toggled and confirmed working, upon opening this app it will show the usual "device not secure/rooted" message. After this it somehow disable magiskhide as my revolut app no longer prompts for fingerprint and my bank app stops working.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
UDPATE: I did some stuff from https://forum.xda-developers.com/apps/magisk/how-to-bypass-lloyds-root-detection-t3837206, the adaway host list. Added MagiskHide Props Config. I also set tasker to toggle magiskhide whenever I turn on my screen. Seems to work more consistently for now
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
lambstone said:
Details: Huawei P20 Pro running 9.0. Magisk Manager v7 (latest), Magisk v18.2 (latest canary) original package name. Safety net passed.
I have to go back into magisk and retoggle magisk hide for it to work again. (However the starling bank app still fails the root check)
I'm really really frustrated now and will appreciate any help.
Click to expand...
Click to collapse
If Magisk Hide Of Magisk 18.x Is Working Intermittently (Which Means Also The Device Will Not Pass The SafetyNet Sometimes), Try To Use The Module Of Microsoft Intune Company Portal Hider Which Includes Also The Functionality Of Re-Enabling Magisk Hide Every 5 Min. For Magisk 18.x From This Thread https://forum.xda-developers.com/apps/magisk/module-microsoft-intune-company-portal-t3780451. Awaiting Your Feedback.
Dreamer(3MF) said:
The Functionality Of Re-Enabling Magisk Hide Every 5 Min
Click to expand...
Click to collapse
Doesn't this cause battery drain?
akxak said:
Check the Magisk main thread and Github, there is a known problem with Magisk Hide in the 18.x. I went back to 17.x which work for me without any problems.
Click to expand...
Click to collapse
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Simone_ASR said:
Hi, some questions. Do I have to install also the Manager v6.10 to install Magisk v17.3? Or can I leave the last Manager? Then, I uninstall Magisk from the app and them I flash the v17.3 from (temporary) TWRP, is it correct?
Click to expand...
Click to collapse
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
akxak said:
The latest Magisk Manager dropped support for Magisk 17 or older, you need the matching Manager..
Click to expand...
Click to collapse
Thank you so much for your fast reply!
In the exact same situation as OP P20 Pro (maybe except im on LOS 16)
Magisk seems to be working fine passing safteynet and Root Beet finding nothing but yet the Starling Bank app and the Arriva Ticket app both figure out my phone is rooted after a while and lock out.
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
gkornaks said:
Had exact problem with Starling app with magisk hide and app on hide list. Turned out to be a direct build.prop modification so after resetprop -p all good now.
Click to expand...
Click to collapse
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
republicj said:
Can you expand on this a bit?
I've downloaded Magiskhide props config, and what do I have to do now?
For me, starling always works for couple of days and then it locks me out via the root screen.
Click to expand...
Click to collapse
I modified a build.prop directly before magisk install so compromised the system partition. I've used resetprop to mask it. Like you I'm occasionally getting root warning as well and have to re-authorise so magisk hide in 18.1 not perfect as mentioned a lot in a forum.
Hi,
it seams that the problem is still there. I have to retoggle Magisk Hide at every reboot of the phone.
Is there any workaround or any ETA on the fix?
Thank you.
No one?
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Didgeridoohan said:
Never ask for ETAs...
https://github.com/topjohnwu/Magisk/issues/1654
Click to expand...
Click to collapse
Ok, I'm sorry about that , I just needed a confirmation that the problem was still there. Thank you for the reply!
Yes it's till here. I cannot login to Arriva bus app with Magisk 20.1.
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
If you can pass SafetyNet (cts profile) try to hide :
Magisk Manager with a random name (mandatory) ... and "Your banking app" must be hidden too along with Google Services of course !
There are currently several ways of detecting Magisk that MagiskHide can't circumvent.
If the app isn't using one of those (if it is you'll just have to wait for a possible update to Magisk), you can find some tips and tricks here:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Magisk cannot hide:
Other known root apps (see "Detecting apps requiring root"). (Shouldn't be a problem since even with a renamed manager and magisk unflashed it still works.)
Remnants of previous root method, including any root management apps (a good way to remove most remnants of root is osm0sis unSU script). (Magisk is unflashed and app immediately works.)
Unlocked bootloader (see Unlocked bootloader). (Magisk is unflashed and bootloader unlocked, app still works. I also tried custom rom and the stock rom.)
A tripped Samsung Knox counter. (Not a samsung phone.)
Xposed (deactivate it or uninstall). It doesn't matter if it's systemless, Magisk can't hide it. (Never used.)
EdXposed. Detection of EdXposed can sometimes be worked around with newer release of EdXposed and/or features like the EdXposed Manager blacklist. (Never used.)
USB/ADB Debugging (disable under Developer options in Android settings). (Magisk unflashed and debugging on, app works.)
Developer options. (Magisk unflashed and developer options is on, app works.)
Some Magisk modules - Depending on what the module does, it may not be able to be hidden by MagiskHide. (Tried core only mode which should disable all modules, still don't work.)
Some modifications to /system. Make sure to use Magisk modules... (I'm not sure what this means :c)
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
IcY~ said:
From that list it looks like it's something from Magisk itself that's tripping the detection :/
Im going bald from this.
Click to expand...
Click to collapse
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Didgeridoohan said:
If you've tested and confirmed everything else, it is very likely that the app is using a detection method that Magisk currently can't hide from.
Solution? Wait for @topjohnwu to possibly update Magisk/MagiskHide (alternatively, don't install Magisk). When? Whenever he feels like it...
Click to expand...
Click to collapse
https://github.com/topjohnwu/Magisk/issues/2406
Looks like someone posted a potential fix. Will wait for it to reach the master branch!
Have you find the workaround? I am using the same app and face same problem. This app last update gives headache
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
@kubis111
i'm happy for you, but please...this isn't your thread so do not OOT, OP problem isn't solving yet
---------- Post added at 11:46 AM ---------- Previous post was at 11:03 AM ----------
Tomek0000 said:
I am hidding root and edxposed using Island and installing intune inside the sandbox. Maybe the same will be with bank apps.
Click to expand...
Click to collapse
can you share the apps link?
Any updates on this banking app? I've tried many TaiChi Magisk, Sudohide and Zuper module but no success.
ctsProfile all green, Rootbeer Fresh all green.
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Heatexplorer said:
citi app also detected my rooted device( Mi 8 Pro) after update , even hide the App ..useless....
Click to expand...
Click to collapse
Had the same problem. Updated magisk manager and fixed it (even before updating my modules).
Anyone lucky on it? What about BBVA Spain app?
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Have you found a solution? With latest Permata and Magisk (23) the banking app still does not work...
timofonic said:
Anyone lucky on it? What about BBVA Spain app?
Click to expand...
Click to collapse
For me work
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Found a solution, but can't publish yet. Excuse me
Spartacus500 said:
Found a solution, but can't publish yet. Excuse me
Click to expand...
Click to collapse
Why?
hallo dare said:
Why?
Click to expand...
Click to collapse
So I ran the test quickly and it turns out that it works, for those who are interested, I will provide a solution, but a little later.
I managed to make it work,
Spartacus500 said:
For me work
Click to expand...
Click to collapse
Spartacus500 said:
For me work
Click to expand...
Click to collapse
No idea how. I'm worried about that Knox logo these days, but we'll..
Thanks!
IcY~ said:
My banking app (PermataMobile X) is detecting root with Safetynet passed and Magisk Manager hidden. I asked some other people to install and see if they can pass the root detection to no avail.
I've tried some little things to narrow down the culprit like:
1. Installed Magisk Manager without flashing the magisk 20.4 zip file (unrooted). Detected as root. Uninstalling the manager immediately allows bank app to work.
2. Flashed Magisk 20.4 without installing Magisk Manager. Detected as root, obviously.
3. Went back to previous versions of Magisk and Magisk Manager. Still detected as root.
Anyone can give any tips on what else I can try to do?
Click to expand...
Click to collapse
Sorry to be just now, but to the point of solution to this,
1. Install the disable services app and disable a process called "S17"
2. Done
Hi
I have a problem in the clubhouse app that login not complete on any rooted device ... no problem on Non Root devices
I hide magisk app add clubhouse to magisk hide and EDExposed blacklist but still not working.
also, the same issue is in Mcdonald's app.
any idea how to solve these issues
Note: My Bank app works after adding it to magisk hide and hide magisk app, which means i did it right.
thanks
anyone help me please
Have you tried removing the Magisk app? That's a popular way of detecting Magisk, even with a repackaged app. It's practically impossible to completely hide it on anything below Android 11, and even then it's necessary for the app to target A11 for full hiding to work (which won't happen until Google enforces that, maybe later this year).
Of course, Xposed/EdXposed/LSPosed tools can probably be used to hide the app fully...
Didgeridoohan said:
Have you tried removing the Magisk app? That's a popular way of detecting Magisk, even with a repackaged app. It's practically impossible to completely hide it on anything below Android 11, and even then it's necessary for the app to target A11 for full hiding to work (which won't happen until Google enforces that, maybe later this year).
Of course, Xposed/EdXposed/LSPosed tools can probably be used to hide the app fully...
Click to expand...
Click to collapse
thanks for your reply
if i removed magisk .. everything that use root will stop and i don't want that
also can you please tell me how to hide the app fully using EDXposed
I did not say "remove Magisk"... I said "remove the Magisk app". Just uninstall the app and try and see if Clubhouse still triggers. If it works we know it's looking for the app and you'll have to either freeze/uninstall the Magisk app when using Clubhouse and then reinstall it again afterwards, or use one of the available isolation methods. I've got a few of those mentioned here, but I'm sure you can find more if you search (it's been covered a lot):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Isolation_apps
zamlkawy said:
Hi
I have a problem in the clubhouse app that login not complete on any rooted device ... no problem on Non Root devices
I hide magisk app add clubhouse to magisk hide and EDExposed blacklist but still not working.
also, the same issue is in Mcdonald's app.
any idea how to solve these issues
Note: My Bank app works after adding it to magisk hide and hide magisk app, which means i did it right.
thanks
Click to expand...
Click to collapse
for Mcdonald's try this
[MOD][XPOSED][4.1+] McRoot (McDonalds Global App)
McRoot McDonalds Global App security fix Remove checks of: root unacceptable apps unacceptable device properties (developer options etc) Note: The app requests SafetyNet pass! Use Magisk+Riru+Riru-Unshare etc Install notes: install apk...
forum.xda-developers.com
Hi. I also have Magisk installed on my device. I uninstalled Magisk app, tried logging into clubhouse again, but still the issue persists.
After receiving the missed call while trying to sign in, I get the notification, 'There was an error please try again'
Clearing the clubhouse app data, uninstalling and reinstalling the app again hasn't helped at all. I get the same issue.
I have Magisk 23.0 installed on my Oneplus5T running Android 10.
For context I have "treble_arm64_bvS-userdebug 11 RQ3A.211001.001 eng.crossg.20211108.032335 test-keys" LineageOS custom rom with magisk and safetynet granted (thanks to riru module)
But my banking app got recently updated https://play.google.com/store/apps/details?id=com.cm_prod.bad and now refuses to let me connect because "For security reasons this application does'nt support emulators anymore"
This app has MagiskHide applied otherwise it detects root and refuses to let me connect
I know MagiskHide is discontinued but is there a Magisk module or a tweak that could resolve my issue ?
Thanks in advance for any help
Try install IsLand and add app that detect Magisk into IsLand, also hide magisk app by repacking magisk with random package
Dawnowl444 said:
For context I have "treble_arm64_bvS-userdebug 11 RQ3A.211001.001 eng.crossg.20211108.032335 test-keys" LineageOS custom rom with magisk and safetynet granted (thanks to riru module)
But my banking app got recently updated https://play.google.com/store/apps/details?id=com.cm_prod.bad and now refuses to let me connect because "For security reasons this application does'nt support emulators anymore"
This app has MagiskHide applied otherwise it detects root and refuses to let me connect
I know MagiskHide is discontinued but is there a Magisk module or a tweak that could resolve my issue ?
Thanks in advance for any help
Click to expand...
Click to collapse
https://github.com/kdrag0n/safetynet-fix make sure you use the one for magisk hide not zygisk.
Also make sure that magisk manager is hidden ex in magisk manager settings hide magisk rename. Also make sure gms(play services), play store, and your banking app is hidden
toolhas4degrees said:
https://github.com/kdrag0n/safetynet-fix make sure you use the one for magisk hide not zygisk.
Also make sure that magisk manager is hidden ex in magisk manager settings hide magisk rename. Also make sure gms(play services), play store, and your banking app is hidden
Click to expand...
Click to collapse
There are more and more app now can detect magisk stub apk (random package). Your tutorial is old and already have a post about how to do this ))
Well thanks for your responses and yes I have already have already rename Magisk with random id, I have universal safety net fix with riru, and MagiskHide enabled with my banking app (otherwise it detects root as is). And tough that all of this was enough (I do pass safetynet for now) but seems that it is not for my banking app...
@huskydg.11455139 I installed IsLand but I was a bit too much surprised with all the professional profil tweaking that it was doing without my consent... I kinda panic and uninstall the all thing...
But :
- I don't get in what way this will hide the fact that my banking app detect Magisk as an emulator
- When an app is "professionalised" what does it do and what does happen to my saves ?
- I do need MagiskHide to hide root otherwise my banking app detects it either way, can I do that while having IsLand enabled ?
Dawnowl444 said:
Well thanks for your responses and yes I have already have already rename Magisk with random id, I have universal safety net fix with riru, and MagiskHide enabled with my banking app (otherwise it detects root as is). And tough that all of this was enough (I do pass safetynet for now) but seems that it is not for my banking app...
@huskydg.11455139 I installed IsLand but I was a bit too much surprised with all the professional profil tweaking that it was doing without my consent... I kinda panic and uninstall the all thing...
But :
- I don't get in what way this will hide the fact that my banking app detect Magisk as an emulator
- When an app is "professionalised" what does it do and what does happen to my saves ?
- I do need MagiskHide to hide root otherwise my banking app detects it either way, can I do that while having IsLand enabled ?
Click to expand...
Click to collapse
IsLand is second space, any app in IsLand cannot collect anything in Primary space, prevent it collects app list and scan these apk to detect random package magisk app
You can apply MagiskHide / MagiskDenyList for any app in IsLand
I used this to bypass Techcombank, PUBG NEW STATE which can even detect random package magisk app (stub.apk) without freezing Magisk app
Or Hide your list app by using Xposed module: Hide My List App, because now more and more app can detect magisk even it has random package.
With combo (MagiskHide)+(Random Package Magisk app)
huskydg said:
IsLand is second space, any app in IsLand cannot collect anything in Primary space, prevent it collects app list and scan these apk to detect random package magisk app
You can apply MagiskHide / MagiskDenyList for any app in IsLand
I used this to bypass Techcombank, PUBG NEW STATE which can even detect random package magisk app (stub.apk) without freezing Magisk app
Or Hide your list app by using Xposed module: Hide My List App, because now more and more app can detect magisk even it has random package.
With combo (MagiskHide)+(Random Package Magisk app)
Click to expand...
Click to collapse
Well I did just now tried IsLand and my banking app still detects that my phone is considered as an emulator.
But the thing is MagiskHide and random package repacking do work as long as hiding root is concerned, otherwise by banking app do warn me that it detects root. But I wonder if in that process MagiskHide use some technics that are ones of an emulator in the process and my banking app do detects that...
Dawnowl444 said:
Well I did just now tried IsLand and my banking app still detects that my phone is considered as an emulator.
But the thing is MagiskHide and random package repacking do work as long as hiding root is concerned, otherwise by banking app do warn me that it detects root. But I wonder if in that process MagiskHide use some technics that are ones of an emulator in the process and my banking app do detects that...
Click to expand...
Click to collapse
Are you using Custom ROM?
huskydg said:
Are you using Custom ROM?
Click to expand...
Click to collapse
Well yes I'm using AndyYan's Lineage OS (Android 11) rom thanks to phh experimentation from the Treble Project.
This could could be a thing but I'ts weird that my banking app is warning me about emulator and not custom rom (instead of WhatsApp that clearly says that it detects custom rom).
I'm just speculating at this point but I have my bootloader unlock and the phh/AndyYan rom is userdebug. I think the unlock bootloader is spoofed by safetynet fix but I don't know if the userdebug variant can be detect and can be sign of an emulator...
Dawnowl444 said:
Well yes I'm using AndyYan's Lineage OS (Android 11) rom thanks to phh experimentation from the Treble Project.
This could could be a thing but I'ts weird that my banking app is warning me about emulator and not custom rom (instead of WhatsApp that clearly says that it detects custom rom).
I'm just speculating at this point but I have my bootloader unlock and the phh/AndyYan rom is userdebug. I think the unlock bootloader is spoofed by safetynet fix but I don't know if the userdebug variant can be detect and can be sign of an emulator...
Click to expand...
Click to collapse
So that's why, most Custom ROM has broken rules, do you know? Also app can easily detect if you are running Custom ROM
huskydg said:
So that's why, most Custom ROM has broken rules, do you know? Also app can easily detect if you are running Custom ROM
Click to expand...
Click to collapse
Welp same here but it just bug me that my app detects "emulator" and not custom rom... But it's could be some nonsens from by banking app after all...
And weird think that I need to disable MagiskHide, that is still usefull to me, for Momo checking.
So then I should try to spoof my build id and other stuff that can say that I have custom rom?
Dawnowl444 said:
Welp same here but it just bug me that my app detects "emulator" and not custom rom... But it's could be some nonsens from by banking app after all...
And weird think that I need to disable MagiskHide, that is still usefull to me, for Momo checking.
So then I should try to spoof my build id and other stuff that can say that I have custom rom?
Click to expand...
Click to collapse
Maybe they can mark custom ROM as emulator just to make you fear (sometime they said they found something but not that thing). who know?
Try restore to stock rom (no root) and check
huskydg said:
Maybe they can mark custom ROM as emulator just to make you fear (sometime they said they found something but not that thing). who know?
Try restore to stock rom (no root) and check
Click to expand...
Click to collapse
Yeah sometimes they say stuff because they found root or "insecurity" but the app says something completely different.
I will loose all my data if I restore stock rom plus it's a Chinese bloated rom, so I won't do that. I do really like Lineage OS so I will stay out there. But yeah it will most definitively work with stock rom not rooted that's obvious (well I say that but I still have TWRP and unlock bootloader)
huskydg said:
There are more and more app now can detect magisk stub apk (random package). Your tutorial is old and already have a post about how to do this ))
Click to expand...
Click to collapse
If you are using xposed, you can use dev opts hide and hide my applist modules to hide anything you want. I was going with the simplest answer to see if all the first checks were in place.
toolhas4degrees said:
If you are using xposed, you can use dev opts hide and hide my applist modules to hide anything you want. I was going with the simplest answer to see if all the first checks were in place.
And wasn't tutorial was a question
Click to expand...
Click to collapse
Not all apps you can apply the same way
huskydg said:
Not all apps you can apply the same way
Click to expand...
Click to collapse
Actually you can if they are more invasive you will need more hiding than magisk hide can give you. Which are the lsposed method example of what I said also lua module can do some of it also depends which module you prefer. I use hide my applist and dev opts
Go search lsposed and how to use hide my applist
toolhas4degrees said:
Actually you can if they are more invasive you will need more hiding than magisk hide can give you. Which are the lsposed method example of what I said also lua module can do some of it also depends which module you prefer. I use hide my applist and dev opts
Go search lsposed and how to use hide my applist
Click to expand...
Click to collapse
You think I don't know this , don't you?
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
toolhas4degrees said:
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
Click to expand...
Click to collapse
What's the question I am asking?
toolhas4degrees said:
If you do you wouldn't be here asking.
Maybe you should try using them correctly and clearing data and cache of the app.
Click to expand...
Click to collapse
Maybe you misunderstand what i am taking?
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.