yashsingh1/xdaforums huggingface dataset:
[Magisk] wugga3:
I'm not any expert ... But... OnePlus 7T on OOS12 (latest) and official magisk stable 25.2 (not hidden) with enforce denylist with Yes bank on deny list gets me past the root detection error I got before adding into deny list in magisk.... So may be force stop Yes bank then clear data/cache... ? Worked for me to get to the registration screen without error. I don't have/use lsposed so I'm unable to assist with that matter. Clear data and retry?

EDIT: to add that my device is OEM unlocked...

And.. universal safetynet fix v2.3.2 mod 2.1 kdragOn mod by displax

Unable totake screenshots of bank app due to sensitive information on registration screen...

And I don't use Yes....
[Magisk] pndwal:
My device:

Xiaomi RN8T stock A11 MIUI

Magisk Canary 25209

Latest Shamiko public release (for proper root hiding]

[LSPosed Hide My AppList, but not needed for this app]

This app is detecting OEM unlocking when enabled in Developer options (even if enabled with developer options disabled)... With the above setup I get:

With OEM unlocking disabled:

... It's not detecting USB debugging or Developer Options itself...

I have disabled OEM unlocking on my device and rebooted and all is fine... While I believe this is normally safe with the

important exception

of Magisk use with relocked bootloader (ie. with custom keys set to allow relocking with custom mods incl. Magisk etc), I'm not certain of this... Others may like to verify the safety of disabling OEM unlocking with normal (unlocked device) Magisk use...

The App can be used by disabling OEM unlocking before a reboot however, so you can always enable it again before a reboot...

Hope this fixes your issue! 👍 PW
[Magisk] asripath:
Accessibility service(not granted to the app) and

VPN (Netguard) also seem to trigger it's sensitivity
[Magisk] asripath:
Have you tried using the app

In parallel space/shelter/insular/island ?
[Magisk] pndwal:
... Guess those are additional issues on your device with your setup (and your solutions may help if the member uses similar settings)...

However the member specifically said:

... OEM unlock triggers the "device appears to be rooted" Security Alert notice...

The Security Alert notices you show concern different issues... PW
[Magisk] asripath:
True...

"Is there a way to find which app is the reason for the root detection"

Don't use yes Bank...

was just helping out in diagnosing the issue.

Rooted with delta and magisk hide...

Don't get OEM unlock error

(maybe it doesn't trigger on delta).

Btw the user did not upload any screenshots

Of his detections...

would help more in identifying the issue
[Magisk] zgfg:
If I correctly understand your screenshots, for Accessibility and VPN you have options to Close the app or Skip (and continue to use)?

I had a similar case with one MDM - it found Accessibility and warned but let me continue

Btw, Ruru also warns about Accessibility (screenshot)

It will be stupid if banking and similar apps prohibit the use of regular Google features like Accessibility (users with disabilities) and VPN (users may need for their work)
[Magisk] pndwal:
Yeah, I removed the ref. to 'app' in quoting this above as it seems app detection isn't triggered 'root found' Alert... OEM unlocking enabled is... The question simply assumes it would be an app but that's a red herring; the app in question starts without even using HMA...

I don't either... But only because I prefer No Bank... 😁

And there may be further issues...

Maybe...

Is OEM unlocking already disabled in Developer Options?

Also, what USNF version are you using?...

Can you check /data/adb/modules/safetynet-fix/service.sh to see if the lines highlighted (at the end) here:

https://github.com/kdrag0n/safetyne...e9b5d57eb43446f4954/magisk/service.sh#L57-L60

exist?...

That OEM unlock prop change in USNF was proposed and finally rejected by @kdrag0n and removed from @Displax patch set (later merged in official USNF)...

It may still exist in older or forked USNF builds, and may also have been added in other hide-solution mods...

mmm... But said 'root' detected, so seems it's per my 'Alert' screenshot... PW
[Magisk] asripath:
Don't use USNF...on custom ROM crdroid... it's inbuilt

OEM unlocking option not available in developer settings and *#*#7378423*#*# doesn't work...away from a computer so cannot check through fastboot at the moment

getprop sys.oem_unlock_allowed

0

User never mentioned what error he/she was getting in relation to app failure to work...you got OEM unlock alert and me accessibility and vpn
[Magisk] pndwal:
Ah... Custom ROM...

Just checked my Mi Pad 4 with LineageOS Developer options, and OEM unlocking is disabled; I haven't done that... Seems disabled by default...

That would explain it on CRDroid too since it's based on LineageOS (although strange OEM unlocking doesn't appear in CRDroid Developer options)...

No, but mentioned 'root detection', not 'an enabled accessibility permission' or 'connection to a VPN network' detected...

And I got 'device rooted' alert, not 'OEM unlock' alert:

However I guess we can assume nothing since we know very little about device / setup...

If on custom LineageOS or CRDroid (or other custom ROM) the member may simply be equating 'root' detection with those other issues, who knows... The member may be wrongly reporting and you may be right. 🙃 PW
[Magisk] Spartacus500:
What is it that detects me in the Ruru app 🤔
[Magisk] pndwal:
This is 'hidden space'...

In MIUI it seems it may be triggered by either Dual app space or Second space which work differently...

It's easy enough to see and remove both of these data directories from /data/media if they've been created, but the Ruru detection persists for me even when these are absent... Perhaps MIUI has another even better 'hidden space' secretly stashed somewhere... Anyone know? 😬 PW
[Magisk] hotland:
when i tried uninstalling supersu in my oneplusone it says uninstall failed.
[Magisk] CrazyCypher:
You should write in SuperSU thread, not here in Magisk General Support :)

---------- Post added at 03:52 PM ---------- Previous post was at 03:47 PM ----------

Anyone knows what part of Magisk is causing failed SafetyNet? Maybe we could try temporary renaming files/folders like what Root Switch is doing for Superuser files?
[Magisk] hotland:
alright my fault sorry thanks anyway
[Magisk] jascolli:
Good idea. Hopefully someone smarter than me reads this.
[Magisk] Alxoom33:
At this point, if you want to pass Safety Net you need to fully uninstall Magisk. Only use SUhide, Root Switch and Xsetprop.
[Magisk] NovaViper:
I am having issues installing Magisk (I have the manager installed too) for the systemless Xposed.. Everytime now I install it, it ends up causing bootloops and the only way to fix it is to flash a new ROM.. I'm using the Mostly Stock ROM (its not Stock though), my phone is an Samsung S6 edge (SM-G925P) running Android 6.0.1. I am also using the latest SuperSU (Systemless mode)

The Boot file is here
[Magisk] Ashtrix:
The revamped UI has masterswitche(s) for all modes. Yes I did, But it wont :rolleyes:
[Magisk] Kany3:
Thanks im able to play pokemon go !!!!

I got a note 5 (SM-N920T) i flash supersu, 86.2 exposed systemless , and then suhide v.55
[Magisk] lkikl:
Hi all.

Can someone help me ? Why i cannot show the Root Toggle in Magisk Manager? I open the Magisk Manager only was showing 3 components is OK (Installed Magisk v8", "Latest version of Magisk installed" & "Latest version of Magisk Manager Installed") . I confirmed granted root access right in phh SuperUser.
[Magisk] Didgeridoohan:
I just don't get it. People must be following some outdated guides and not bothering to read up for themselves... :crying:

Anyway... There is no root toggle in Magisk (anymore) and, as far as I know, currently no method to circumvent Safety Net with Magisk. I'm sure you can find some answers in the Pokemon thread.
[Magisk] lkikl:
Thanks for ans me. i just want to use android pay instead of Pokemon.:(

Sorry for my outdated information.
[Magisk] poulopoulosa:
It seems that people who care about passing safety net are by majority those obsessed with PoGo. I don't mean to underestimate anyone, but most of them just care about having the "hack" omitting any details, even the donation button. :)
[Magisk] NovaViper:
Anyone know why my phone keeps bootlooping?
[Magisk] Kany3:
I got a question about Xsetprop ? How do I get it for my note 5 T-Mobile ? And thanks
[Magisk] Alxoom33:
Best way is to do a Google search for a dl link and detailed installation instructions.
[Magisk] Kany3:
Thanks will give that a try
[Magisk] Alxoom33:
You may want to look in the Suhide v. 0.55 thread. I provided some instructions there, but you may find more detailed instructions from others. Good luck!
[Magisk] tormie:
I need a rooted phone only to apply changes to the hosts file via adaway. So I solved the situation flashing SU, adaway, remove su by its app and it's done. I flash an upgraded ROM once in a month so It's not a big deal.
[Magisk] shawkes:
Not 100% sure on this but I don't think the systemless xposed in Magisk is compatible with Samsung stock based roms.
[Magisk] NovaViper:
It did work before but for some reason now, it keeps on bricking my phone.. I have Mostly Stock as my ROM (I try Renegade but I loose mobile data connectivity after flashing it)
[Magisk] pndwal:
Yeah, funny 'skip' seems grayed out though...

FWIW, even after enabling Accessibility options and getting this Ruru result:

I still couldn't get the app to produce that alert even after clearing data!... Didn't log in though; may occur after that I guess... PW
[Magisk] Robbo.5000:
Apologies if a solution is already buried in the thread. I've tried a basic search of the thread but couldn't find anything specific.

I'm on the latest stable build of Magisk and have been for a long time. I've got everything set up fine and all financial apps working. However my main banking app detects the Magisk app, even after 'hiding', and has done for about 18 months. At the time this started happening others reported the same thing from other banks. The solution has been to freeze the Magisk app, then unfreeze when needed.

I'm just about to upgrade to LOS 20, so decided on a clean install. As I'm about to configure Magisk again, I decided to check if there is now a better solution to apps that can detect the hidden Magisk app. Would be nice if the Magisk app could remain active and undetected.
[Magisk] wugga3:
Strange cause I was also OEM unlocked and got past the device rooted error so wonder what the difference is between the two?
[Magisk] pndwal:
Not sure what you mean... Do you mean bootloader is unlocked, or you have OEM unlocking enabled in Developer options?... I needed to disable that...

If you can't see that in Developer options please say what ROM you use... Guessing it would be a custom one in that case... PW
[Magisk] zgfg:
No warning or error whatsoever (Magisk Delta, Zygisk and SuList, App data isolation and Reset sensitive props - with Developer options, OEM Unlocking, USB Debugging and Accessibility enabled)

Cannot proceed (not having the account)
[Magisk] pndwal:
Please name the app... PW
[Magisk] Robbo.5000:
It's com.krungsri.kma. Though I don't believe it's particularly relevant.
[Magisk] pndwal:
No?...

My device:

Xiaomi RN8T stock A11 MIUI,

Magisk Canary 25209,

Latest Shamiko public release (for proper root hiding),

LSPosed Hide My AppList module configured to hide all apps associated with root,

OEM unlocking disabled,

USB debugging disabled,

Developer options disabled...

Guessing you need Hide My Applist... 🤠 PW
[Magisk] shoey63:
Of course it's relevant. Different banking apps use different detection techniques and require different approaches to bypassing them.

If you are lucky, someone here will work it out for you by installing it themselves and figuring out the correct method.

Edit: as @pndwal has just done as I was typing 😃
[Magisk] pndwal:
That's interesting...

What does getprop sys.oem_unlock_allowed return? PW
[Magisk] zgfg:
Zero (like not enabled)

I think, it's due to Reset sensitive props module
[Magisk] wugga3:
Stock Oxygen OS latest stable (OnePlus 7T)

Official Magisk stable v25.2

Universal safetynet fix 2.3.1-MOD2.1 kdragOn mod by displax

Enforce denylist

Put Yes bank into denylist and got past the root detection (after Yes app data cleared)

Nothin else to see here other than I couldn't take screenshots of the Yes app due to the sensitive/private personal information. (LOL).
[Magisk] Robbo.5000:
I'd already stated previously that the app is detecting the 'hidden' Magisk app. I already knew very specifically what detection technique the app was catching me out on. If I freeze the Magisk app the banking app works. So everything else I'd done within Magisk was working. I didn't need, nor ask for someone to work it out for me. I just asked specifically what is a better solution than freezing the Magisk app, when an app detects the Magisk app is installed, even after it's been hidden.

It sounds like the better solution I need is Hide My Applist.
[Magisk] Robbo.5000:
Ok thanks, I'll investigate Hide My Applist.
[Magisk] zgfg:
Yeah, without HMA your banking app KMA complains something on the Web, with HMA it opens (screenshot)

Unlike @pndwal (he uses HMA with the Blacklist template), I use HMA in the Whitelist mode (no templates), as on the screenshot
[Magisk] Robbo.5000:
Am I right I assuming?

Blacklist mode = hide apps blacklisted from every other app that asks for an applist

Whitelist mode = do not give an applist (or give an empty applist) to any app in the Whitelist
[Magisk] zgfg:
Whitelist (I don't have a template) as on my screenshot

Blacklist, with Blacklist template, as described in the HMA Guide thread (actually, it's OP post #1 now points to the HMA Guide on GitHub)
[Magisk] Robbo.5000:
Ok thanks and thanks to @pndwal also. I've installed it and got it configured. Everything's working fine and no more freezing and unfreezing apps.
[Magisk] Spartacus500:
OEM Unlocked and OEM Locked on Samsung S7 9.0 nothing helps for Yes bank, it seems to detect invalid certificate 🤔
[Magisk] WoKoschekk:
No, I said same as you. As long as no patched boot.img is active, the contents of /data/adb/ are not mounted.
[Magisk] WoKoschekk:
Did you install a certificate some time ago? Open settings menu and type "certificate" in the searchbar. You should see an overview of your installed certificates.

Are you using an adblock app or sth else with VPN?
[Magisk] kullurumanoj:
So, disabling the oem unlocking worked for me. Will that the be an issue if I reboot my device?

Installing safetynet sensitive prop module worked for me. Thanks all for the help!
[Magisk] Spartacus500:
I didn't install any certificates, adblock for Samsung without VPN 🤷
[Magisk] J.Michael:
I believe that is wrong: "/data/adb" isn't mounted, it just is.

If you believe that "/data/adb" is mounted, then from where do you believe it is mounted?
[Magisk] pndwal:
Magisk Magic Mask (overlay) works when "module files are magic mounted".

https://topjohnwu.github.io/Magisk/details.html#post-fs-data 😉

Modules are mounted as /system overlays to function... Specifically module directories as

system <--- This folder will be mounted if skip_mount does not exist

https://topjohnwu.github.io/Magisk/guides.html#magisk-modules

Other files are mounted too:

https://topjohnwu.github.io/Magisk/details.html#paths-in-magisk-tmpfs-directory

So if content in /data/adb is not mounted, Magisk (Mask) is not working...

Use

Magisk --path to print Magisk tmpfs mount path

Incidentally, much refactoring of Magisk mount is being done ATM... We recently got:

Refactor magic mount to support overlayfs

and other commits will ensure better module compatibility incl. proper ability to systemlessly remove directories etc...

🤠PW
[Magisk] pndwal:
Some systems (ROMs) may sanitize this location much as they do with/system files at boot time, but most do not AFAIK...

/data/adb content is generally preserved even with stock boot.img loaded, and many of us rely on this for module and configuration survival... Booting a stock boot.img will generally not result in an empty /data/adb folder... 🙃 PW
[Magisk] dcarvil:
~ $ mount | grep adb

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

/dev/block/dm-0 on /apex/com.android.adbd type ext4 (ro,relatime,seclabel)

/dev/Zcr/.magisk/block/system_root on /system/bin/badblocks type ext4 (ro,relatime,seclabel)

~ $
[Magisk] pndwal:
So that would explain it anyway... Something is forcing sys.oem_unlock_allowed = 0 regardless of Developer option setting...

On my device I get sys.oem_unlock_allowed = 1 as soon as OEM unlocking is enabled in Developer options...

As I mentioned, this forced prop was considered for USNF but rejected due to producing misleading Developer option state:

https://github.com/kdrag0n/safetynet-fix/pull/240#issuecomment-1368867689

@huskydg originally cautioned against this, but some module may be doing that, what he suggested here

https://github.com/kdrag0n/safetynet-fix/pull/240#issuecomment-1368497042

or other...

One instance where such a misleading Developer option state could be disastrous is if a user (especially Pixel or OnePlus) re-locks bootloader with custom mods and custom keys, eg using avbroot script w/ Magisk... Whether mislead by false Developer options or not, you know of this case where a member recently hardbricked Pixel 6 Pro with no known way to recover:

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-88327781

😶 PW
[Magisk] zgfg:
Magisk Delta with SuList, no need to prepare anything before testing

Finding only ReVanced YT (module) - first screenshot, second with RV disabled

Edit: Download from Magikisune
[Magisk] m0han:
Magisk Delta with Riru. Nothing found.
[Magisk] Mrbally123:
I use Magisk to hide the rooted status for an app, on my samsung a21s, after the process my sim card shows emergency calls only
[Magisk] Spartacus500:
MemoryDetector is the app ?
[Magisk] zgfg:
sus.apk, download from TG channel as on the screenshot in my quoted post #55033

Actually, the same apk on GitHub:

GitHub - HuskyDG/Sample_Detector: ???

??? Contribute to HuskyDG/Sample_Detector development by creating an account on GitHub.

github.com
[Magisk] pndwal:
Stock Android?... Did you flash all 4 binaries w/ Odin?... Did you transfer files using ADB pull (not MTP)?... PW
[Magisk] Spartacus500:
For Magisk stable 🤷
[Magisk] J.Michael:
Is there any way to test whether it can really make an emergency call without actually making an emergency call?

Did you add the name of the app to a list, like Hide List, Deny List,...? Are you using HMA? Did you add the app to HMA's list?

What I am really working towards is, did you maybe add other, especially system, apps to a list? You probably shouldn't.
[Magisk] pndwal:
To me, "the process" is not clear... I assumed this meant installing Magisk to hide the rooted status, and you hiding the rooted status itself... Some clarification from the member would certainly help... PW
[Magisk] ephemunch:
Thanks. So no need to run this command.

I have a Pixel 6A.

adb shell ls -l /dev/block/by-name shows me that it has vbmeta_a AND vbmeta_b partition.

Would be this right?

fastboot flash boot_ab magisk_patched-[random_strings].img

OR

fastboot flash boot magisk_patched-[random_strings].img

XDA tutorial here (https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-google-pixel-6a/) write fastboot flash boot magisk_patched-[random_strings].img

Don't know what is right and what is wrong now.
[Magisk] pndwal:
The latter method should always work (flashes current slot)... You shouldn't ever need the former option AFAIK (so it's not even mentioned in Installation Instruction page).

Flashing to inactive slot is only really used to preserve Magisk through an OTA and for devices supporting this a user flashes OTA and immediately uses inbuilt Magisk function (go to Magisk app → Install → Install to Inactive Slot) to install Magisk to the updated slot before any reboot (which swaps active slot) per:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#devices-with-ab-partitions

Nb. Install to Inactive Slot preservation method is broken some for late Pixel 6 series updates and for Pixel 7 series (and likely other devices by now) apparently due to new update engine partition digest checks marking installation w/ Magisk as corrupted before it will boot... It seems Magisk can still overcome this (overwrite accepted digest calculations) with some device/update combinations so users may be able to use this feature... Mileage is inconsistent but most are finding usually fails ATM it seems...

👀 PW
[Magisk] ephemunch:
Thanks. So like the XDA-Instruction page said I need reflash bootloader and reroot Magisk/ Pixel 6A after every OTA of LineageOS 20/ Stock-ROM?
[Magisk] Lughnasadh:
Not completely broken as I explained here. More like hit or miss.
[Magisk] pndwal:
Not sure what you mean here... If you mean unlock, then no... That's a one time thing unless you/your flashing software relocks it...

Late LOS should preserve Magisk when updating from booted system as it supports addon.d v2 survival script.. Nb. this is a different Magisk preservation feature, maintained in Magisk by @osm0sis, only for custom ROMs...

You could try OTA preserve Magisk method if you're game (some still have success) but this no longer works consistently as mentioned above...

Most find they need to return images to stock, take OTA and reboot to new slot, then do initial root again as root was lost...

🤠 PW
[Magisk] pndwal:
Ah yes... It's the Alzheimer's you see...

I've edited my posts above... Thanks!

Pinging @ephemunch...

Alzheimers Magisk modders chant:

"What do we want? Better Magisk hiding!.... When do we want it........

Wait... when do we want what?..."

😃 PW
[Magisk] docluv01:
Hey guys, have the latest magisk canary build sis systemless hosts enabled. i updated to the new adaway apk and I cant get past the syncing screen "Failed to sync". any suggestions? Some say its an issue with the latest magisk?
[Magisk] zgfg:
Unfortunately, it's kind of a trap and nobody reads in advance but later asks for help when in trouble

There are numerous posts during the last weeks that support for systemless modules (incl. Systemless hosts) is broken in Canary v25210, and the posts with instructions how to download and roll back (to avoid repeating the whole story)
[Magisk] docluv01:
my apologies, I will search
[Magisk] PieKnu:
Hello there,

my danish authority app "MitID" is stating that it is detecting a root.

Because of that I removed everything already 3 months ago and all was fine.

Now today, I had to face that MitID for some reason was stating I'm rooted.

Applist Detector which I still had installed, now for some reason states, that some "Sundry API from Magisk could be found"

Anyone here who has a suggestion what that means and how I perhaps am able to fix that?

Already thanks in advance

Regards

Pierre
[Magisk] zgfg:
Screenshot tells that Applist Detector finds com.topjohnwu.magisk

- that is the Magisk app (you have to hide it by HMA)

However, no guarantee that it's the same what your MitID is complaining about (MitID maybe looks for something totally different, and/or you hid Magisk app from MitID but not from Applist Detector, etc)

Make sure you pass Basic and Device Integrity by Play Integrity API (that's not SafetyNet) and that MitID is in DenyList
[Magisk] PieKnu:
Hey there, thanks for your reply.

Yea, but the weird thing is, that magisk app isn't installed anymore. and com.topjohnwu.magisk isn't being detected anywhere else.

The phone is unrootet.

and yea, MitID is prone to detect other things that might be the issue.

though the “PM Sundry API” was the only suspicious thing that came in my mind, hehe