Database Develop

Magisk Banking apps not working

I was using the Xposed framework today and every app kept crashing so disabled Xposed framework and related modules.
However, afterwards my banking apps stopped working.
These apps are logging me off because they detect my phone has been jailbroken.
The app in question is Lloyds banking app (UK)
I have Magisk 16.0 on a Samsung S8 G950F with renovate ice 7.2 installed
Everything was working before
When I tap on safety net check i get all success
In Magisk hide the apps I want to hide the status of are checked (lloyds being one)
I uninstalled, cleared cache of the app, restart the phone and installed the app again, then before starting it up I checked the option in Magisk hide and then opened the app. However it didn't work.
Any idea what I am missing?
Thank you

http://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

Tried those options already
Hide Magisk manager but didn't work

I would uninstall the banking app or delete it's memory completely. The app might have stored the root status and a phone usually does not unroot anymore.
Unfortunately the banks do not see that the owner of a rooted phone usually works more on keeping his phone safe and free of ads.

I'm going to try that again but doubt it will work as I have tried it already. Maybe there's something residual left that can't be removed even after cleaning the data. I see a lot of apps folder in my file manager from apps that I deleted ages ago.

LLoyds bank
went to bank info and cleared cache and data
Uninstalled app
went to file manager and removed residual files folders
installed clean master and did a cache junk file clean up
restart phone in recovery and cleared cache and dalvic cache
rebooted phone and installed lloyds banking app
opened magisk manager before opening lloyds and ticked lloyds app in magisk hide
opened app and inputted login information
same error: your device appears to be jailbroken etc

Have you tried with Magisk v16.7 (MagiskHide has been improved since v16.0)?
Have you tried repackaging the Manager?
Have you tested if the app is detecting Magisk in the Manager name?
Have you tried grabbing a logcat, to see if it's possible to figure out what's happening?
Etc...
In other words: All of the things that are found in the link I gave you earlier.

is your kernel set to permissive? ive noticed if i set kernel to enforcing then my banking app works with magisk hide. im with santander uk

dead0 said:
is your kernel set to permissive? ive noticed if i set kernel to enforcing then my banking app works with magisk hide. im with santander uk
Click to expand...
Click to collapse
That is interesting. MagiskHide should be able to hide a permissive SELinux. I wonder why it doesn't seem to work...

Didgeridoohan said:
That is interesting. MagiskHide should be able to hide a permissive SELinux. I wonder why it doesn't seem to work...
Click to expand...
Click to collapse
it is strange... seems on latest builds of banking apps, they are somehow still detecting if kernel is permissive or enforcing.

cpu2007 said:
I was using the Xposed framework today and every app kept crashing so disabled Xposed framework and related modules.
However, afterwards my banking apps stopped working.
These apps are logging me off because they detect my phone has been jailbroken.
The app in question is Lloyds banking app (UK)
I have Magisk 16.0 on a Samsung S8 G950F with renovate ice 7.2 installed
Everything was working before
When I tap on safety net check i get all success
In Magisk hide the apps I want to hide the status of are checked (lloyds being one)
I uninstalled, cleared cache of the app, restart the phone and installed the app again, then before starting it up I checked the option in Magisk hide and then opened the app. However it didn't work.
Any idea what I am missing?
Thank you
Click to expand...
Click to collapse
If it's anything like Barclays's App, once it detects a rooted phpne, that's it - you're stuffed, as the App sends the phone's identity to Barclays's blacklist. The only way out is a reflash, which will give the phone a new identity.
.

DaystromLIVR said:
If it's anything like Barclays's App, once it detects a rooted phpne, that's it - you're stuffed, as the App sends the phone's identity to Barclays's blacklist. The only way out is a reflash, which will give the phone a new identity.
.
Click to expand...
Click to collapse
To follow-up, it appears that Barclays doesn't use SafetyNet, but something called libShield (??!).
Whenever Barclays detects root on one of my phones, I have to reflash it to stock, thus giving it a new identity.
I have to follow this sequence, in order to prevent tripping:
Reflash the device to stock
Make sure you get Magisk installed BEFORE re-installing the banking app.
Once you've installed the banking app, DO NOT RUN IT yet.
Make sure MagiskHide is ticked for that banking app (and any related apps, like Pingit).
Do the 'randomise Magisk\'s package name' thing.
Set the Superuser thing to 'deny' by default (Barclays seems to trip if it detects that a user is pressing DENY, by the longer time taken).
Reboot
Make sure everything is working
Then, start the app, and begin the reregistration process.

It's happened on me to. On Bank Mandiri App. On other Bank running normaly. The issues happened after upgrade into Magisk 17.1
On Magisk 16.x it's Work without any issue.
Any clues what going on and how to fix it?

repackaging the Manage with a random name is the trick,i did it and its works

In my case (RaiPay in Romania) I did all things except reflashing and it did not work.
Logcat: https://gist.github.com/eusebiu/8110ef85b1d4093c557b32a101fac299

eusebium said:
In my case (RaiPay in Romania) I did all things except reflashing and it did not work.
Logcat: https://gist.github.com/eusebiu/8110ef85b1d4093c557b32a101fac299
Click to expand...
Click to collapse
Hi, I also have RaiPay (Czech rep.), please try to change SELinux to "enforcing" with this module, it works for me:
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042

PlagueCz said:
Hi, I also have RaiPay (Czech rep.), please try to change SELinux to "enforcing" with this module, it works for me:
https://forum.xda-developers.com/apps/magisk/module-magisk-selinux-manager-t3760042
Click to expand...
Click to collapse
Hey! Thanks for replying! In my case it was already set to "enforcing". I tried changing it using KA-Mod from enforcing to permissive and back but still same result.

eusebium said:
Hey! Thanks for replying! In my case it was already set to "enforcing". I tried changing it using KA-Mod from enforcing to permissive and back but still same result.
Click to expand...
Click to collapse
Hi, sry I didn't reply, too busy.
Please try following Magisk modules:
Busybox for Android NDK
Magisk SELinux Manager (set to enforcing)
MagiskHide Props Config
SafetyPatch
SQLite for ARM aarch64
Modules can be found in Magisk "Downloads" tab (except SELinux manager).
I have these modules installed and my RaiPay works, in combination with enforcing SELinux. I think both our RaiPay apps are very similar if not the same.

PlagueCz said:
Hi, sry I didn't reply, too busy.
Please try following Magisk modules:
Busybox for Android NDK
Magisk SELinux Manager (set to enforcing)
MagiskHide Props Config
SafetyPatch
SQLite for ARM aarch64
Modules can be found in Magisk "Downloads" tab (except SELinux manager).
I have these modules installed and my RaiPay works, in combination with enforcing SELinux. I think both our RaiPay apps are very similar if not the same.
Click to expand...
Click to collapse
Thanks for answering! I think the SafetyPatch was not correctly installed as I get an error message at boot (something with Android has an internal system error. Contact the manufacturer) => not working...

eusebium said:
Thanks for answering! I think the SafetyPatch was not correctly installed as I get an error message at boot (something with Android has an internal system error. Contact the manufacturer) => not working...
Click to expand...
Click to collapse
Yes, I get the same message, is your RaiPay working? And have you tried RaiPay without Magisk installed on your device?

[Help] Magisk hide works only when retoggled

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.

SafetyNet checks (CTS and basic) both failing - LOS16 w/ microG

Hi, can someone please help? I can't get SafetyNet check to pass in Magisk Manager, not even basicIntegrity.
I have tried everything here:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
... and here (in addition to digging around XDA forums)
https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Specific troubleshooting steps taken, each step taken with TWO device restarts after:
1) Magisk Manager is hidden (via Magisk Hide in the Manager)
2) I am only using Magisk modules i.e. no BusyBox, xposed, etc.
3) After having issues I tried disabling all Magisk modules and rebooting twice
4) I tried the osm0sis unSU script, I flashed it in TWRP then deleted Dalvik/cache and rebooted twice, only Magisk was found
5) Developer options/USB debugging are both disabled
6) I froze in Titanium Backup any app needing root then hid Titanium Backup in Magisk (do I need to fully uninstall Titanium Backup and/or other apps with root?)
7) I tested magiskHide with a root checker app - it works, the root checker reports successful root then I hide the root checker with MagiskHide and when re-checking root then fails as expected.
8) I tried to reset fingerprint props but I reverted the settings back when this didn't help. Does anyone have any more info about this please? Unfortunately I already altered the props on my OPO and I don't have stock Cyanogen ROM available to me (it's spyware anyway!!)
A few related question please:
1) I don't need to use Systemizer plugin anymore, correct? As MagiskHide can handle this now? Or do I?
2) I tried a few SafetyNet fixes/modules but none worked... should I try more i.e. PetNoire's SafetyNet Spoofer? https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680/page5
Unfortunately I am not sure that I can attach a logcat output file as I am brand-new to XDA and have <10 posts.
Thank you all so much!

ertrink3n said:
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Click to expand...
Click to collapse
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.

Didgeridoohan said:
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.
Click to expand...
Click to collapse
Micro G can't pass safety net no more cause the Droid helper hasn't been updated....
([emoji3590]09-09-18[emoji3590])

Thank you for the confirmation @PoochyX, that's what I thought, but since I don't use or keep track of MicroG I wasn't sure.
@ertrink3n That's your answer.

Banking app detects root on multiple devices.

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

MagiskHide detected as an Android Emulator in banking app

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?