yashsingh1/xdaforums huggingface dataset:
[Magisk] vukis:
Thanks but using

su -c chmod 000 /proc/net/unix or 440 from termux didn't work.

Even this banking app uses something different or it fails when cannot read. I think it's first. As it throws different error "root detected" when detecting root and another error message when hidden in magisk, without hiding Magisk manager "root management apps detected"
[Magisk] Didgeridoohan:
Could be something about your ROM and/or setup rather than something to do with Magisk, judging from the message in your screenshot.
[Magisk] vukis:
It's completely stock OnePlus 7 pro except twrp and Magisk with two modules (call recorder and YouTube vanced . Few months ago I had error complaining about unlocked bootloader on OnePlus 6t for same app. Maybe this detection is similar? Maybe same like Netflix with it's Widevine L1 :(
[Magisk] Didgeridoohan:
When does it trigger, and is it the version found in the Play Store?
[Magisk] vukis:
It's other version swedbank 2019 Lietuva beta. But it's already taken from play store, as it will be interchanged with the version you refered to. Meaning that currently available version (you referring) will have an big update till 31th of July.

Anyway it triggers only after login. So not possible to test for you. Can I help somehow with diagnosing this case and using my login?
[Magisk] Didgeridoohan:
Logcat or strace showing what actually happens when it triggers might be the only way. Or it could maybe be possible to decompile the apk.
[Magisk] Ingan121:
Could you check if RootbeerFresh passes with Magisk Hide and the UDS workaround? I guess it's a issue with BusyBox, as some manufacturers includes BB on stock ROM, which cannot be hidden with Magisk Hide. (And according to Rootbeer's readme, OnePlus does it.)
[Magisk] vukis:
swedbank V2 apk 8.8 mb from titanium backup

https://saugykla.telia.lt/Shares/Home.aspx?ShareID=670dae49-b803-4ad5-a1bb-61d93d53746c

Logcat 1.0 MB shared till tomorrow. Captured part after loging in and going through welcome screen until fingerprint recognition fails due to "Modified firmware (ROM) configuration was detected"

https://saugykla.telia.lt/Shares/Home.aspx?ShareID=a2d69f8f-e744-4f1c-a0f7-3f7b545bc583

Rootbeer after UDS workaround passes:
[Magisk] Einaras123:
I have Xiaomi mi mix3 on miui 10

Swedbank Lithuania worked well untill I enabled "OEM unlocking" setting in developer options. Since then Swedbank gave me modified firmware error

Keep in mind that i did not unlock or root the phone. I just enabled oem unlocking feature that *allows* me to unlock phone. And that triggered app protection.
[Magisk] vukis:
Version from the play store just got updated and now it's detects unlocked bootloader... Possible to hide that?
[Magisk] vonDubenshire:
Sounds like they're as smart as Netflix.
[Magisk] Didgeridoohan:
MagiskHide should be able to hide that, but from recent reports it seems like something might have changed on A/B devices...

Could you run this command in a terminal emulator and return with the output (the bootprops.txt file):

su -c getprop | grep boot > /sdcard/bootprops.txt
[Magisk] vukis:
Attached
[Magisk] Didgeridoohan:
Awesome!

Now try this command and then open the app again:

su -c resetprop vendor.boot.verifiedbootstate green

If that doesn't change anything, place this in a file in /data/adb/service.d, give it execution permission and reboot (and if that doesn't work move the file to /data/adb/pos-fs-data.d, make sure it has execution permission and reboot):

#!/system/bin/sh
resetprop vendor.boot.verifiedbootstate green

If that still doesn't do anything I'll take a look at the props again...

Edit: I changed the script, since I messed it up the first time.
[Magisk] vukis:
Error on execution

/system/bin/sh: resetprop: not found
[Magisk] Didgeridoohan:
That makes no sense of you have Magisk installed... What happens if you run the command

magisk

You could try using the absolute path:

su -c /data/adb/magisk/magisk resetprop vendor.boot.verifiedbootstate green
[Magisk] vukis:
Magisk returnedNo command 'magisk' found, did you mean:Command 'magick' from package 'imagemagick'

But absolute path worked. Verified, that property has changed by executing su -c getprop | grep boot > /sdcard/bootprops2.txt

Then cleared banking app data and tried my luck... This didn't work

Created changeverifiedbootstate.sh with this text:

#!/system/bin/sh
/data/adb/magisk/magisk resetprop vendor.boot.verifiedbootstate green

Put this file in /data/adb/service.d gave x permissions and restarted.

Checked getprop. State was green. Cleared banking app data and tried once again. Still same error.

Moved changeverifiedbootstate.sh file to /data/adb/pos-fs-data.d restarted, verified that state still changed to green, cleared banking app data and still same error.

Tried restarting without changeverifiedbootstate.sh file in those directories and verified that state is orange.
[Magisk] Didgeridoohan:
That none of the magisk commands are working on your device is weird... That's also something that might have to be looked into.

But, that the prop change didn't work just means it's also looking for something else. I'll take another look at your props shortly.

---------- Post added at 19:35 ---------- Previous post was at 19:25 ----------

[MENTION=2553561]vukis[/MENTION] Another couple of thoughts:

As well as changing the prop, also try disabling OEM unlock. Just for good measure you could also try disabling USB debugging and Developer options as well.

And could you provide another props list, but this time without su, since regular apps won't have access to those props anyway. I'd also like more than just boot props:

getprop > /sdcard/propslist.txt
[Magisk] vukis:
Disabled USB debugging and dev options. Still same outcome.

For bootloader lockinging I would need full data wipe? Would it also wipe internal sdcard?

Maybe Magisk commands does not work because Magisk manager is hidden?

Attached newest props as per request

Thanks for all!
[Magisk] Didgeridoohan:
Thank you.

I did not mean that you should lock the bootloader (that would indeed wipe your device), just try disabling the OEM Unlocking option under Developer Options. But when I think about it again, that might not be possible once you've unlocked the bootloader...

The magisk command has nothing to do with the Magisk Manager. The magisk binary in /data/adb/magisk should be mounted to /sbin, and all the applets (like resetprop) should be symlinked there as well.
[Magisk] vukis:
You nailed it! It was just that "OEM unlock" toggle. Developer options could stay on. And nk props changes is needed.

Thank you! Brilliant ideas!

Should I care about Magisk symlink?
[Magisk] Didgeridoohan:
So the app works just fine now?

About the symlinks, I'm not sure. It's strange that you can't call the applets or even the main Magisk binary. What Magisk version are you using, and could you post your Magisk log?
[Magisk] vukis:
Yep app works without any problems now. Once again thank you!

Magisk is 19.3. I can see the logs but save icon does not do anything. It's not a big issue for me :)
[Magisk] Didgeridoohan:
I guess as long as things seems to be working for you everything's good... :good:

Thank you for indulging my queries and helping me finding new information to add to my root hiding guide.

---------- Post added at 21:38 ---------- Previous post was at 20:43 ----------

Here's a worrisome post about disabling OEM Unlocking:

https://xdaforums.com/apps/magisk/m...systemless-t3432382/post79911991#post79911991

It's not certain that's the case on your OP7P, but you could do a test and try flashing TWRP through fastboot. If that works with OEM Unlock disabled we know that it's not a general Android thing.

Keep in mind though that it's not entirely risk free, so please make sure to have a backup and don't do anything that you don't feel comfortable with just because some random dude on the interweb says so...

I can probably test this myself in a near future, but until then (or if anyone knowledgeable chimes in with new info), and if you feel uncomfortable testing this yourself, it'd probably be safest if you keep the option enabled.
[Magisk] Ingan121:
Termux I guess.
[Magisk] vukis:
As that post says if flashing twrp fail it can fail to boot and launch recovery. In that case backup would not help? Maybe flashing other partition would be safer? System or vendor? Or it's related to recovery partition?

Why is it safer to leave that option if I don't flash roms or partitions. Does ota then twrp +Magisk after ota count as flashing partitions via fastboot? In such case I would need to remember unchecking that box every ota..

I don't want to enable that option, as I do like contactless payments by touching my phone. Is there a chance for Magisk to spoof this option to apps which are in root hiding list?

Yes, termux.
[Magisk] Didgeridoohan:
Of course... I've long since stopped using Termux because of stupid stuff like that and keep forgetting about it. Thank you.

A backup of any important data always helps, even if the device becomes unusable. That does entail keeping the backup off the device though (something I take for granted but I sometimes forget that others might not)... But, since you always can fastboot boot TWRP you're pretty safe.

And talking about TWRP, you can't test with the recovery partition as you have a A/B device. Forgot about that little detail... Testing with a Magisk patched boot image is likely the safest way to go.

I've since had an opportunity to test this on one of my devices, a pretty old Nexus 6 (I don't have access to a computer for another 2-3 weeks and I don't have a USB OTG cable that fits any other device than my OnePlus 3T, so the Nexus it is). No issues there, I can fastboot flash with an unlocked bootloader and OEM Unlocking disabled. It's a pretty old device though, and stuff might have changed.

As mentioned above I can't currently confirm it, but on my OP3T I don't even have an OEM Unlocking option on the ROM I currently use and the sys.oem_unlock_allowed is set to 0 by default (it's disabled). I have been messing with fastboot more than once on this device as well, so I'm pretty confident that I have been using fastboot flash with the option disabled and the bootloader unlocked.
[Magisk] vukis:
What are you using as terminal emulator?

Did a backup via twrp.

Downloaded 9.5.8-GM21BA-OnePlus7ProOxygen_21.E.12_OTA_012_all_1906160800_03f237d1-FASTBOOT.zip. Took boot.img to phone and patched via magisk.

Took magisk_patched.img back to pc.

Restarted to bootloader and executed fastboot flash boot_a magisk_patched.img fastboot flash boot_b magisk_patched.img

Restarted. Root persisted. Tested recovery, and it was stock instead of previous TWRP as expected.

All done with OEM unlocking set to OFF.

By the way OEM unlocking description is "Allow the bootloader to be unlocked". I wounder what kind of description Huaweis have.
[Magisk] Didgeridoohan:
Keeping it simple:

https://play.google.com/store/apps/details?id=jackpal.androidterm

Nice to hear things work. I'm going to have to add a warning to my guide though, for those with the not so friendly devices... Thanks again for testing things.
[Magisk] h_maharaj:
I also have that problem with termux. The problem is that termux does not include /sbin in PATH. Solution is to open the file /data/data/com.termux/files/usr/bin/su and add /sbin to PATH. Commands like resetprop and magiskhide will now work.
[Magisk] The Transporter:
I updated magisk to canary, I took some screenshots.

It's still not working.
[Magisk] Didgeridoohan:
You see that first red check in Rootbeer? You haven't hidden the Magisk Manager... Go to the Manager settings and repackage it with a random name.
[Magisk] DingoTM:
Solved

'canary release' helps me :

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
[Magisk] CryptMan:
Hi,

I have also a Banking App which stopped working after an update of the banking app.

It crashes right after the start but sometimes redirects to an error page in the browser saying that "modified devices" are not supported.

My device is an Axon 7 with unofficial Lineage OS 16, with "MagiskHide Props Config" and Device Simulation I was able to pass SafetyNet Basic and CTS but the Banking App still does not start.

I startet playing around with "MagiskHide Props Config" and set some properties. But nothings helped with the Banking app.

But what I noticed is that some apps still are able to read the non modified values for build flags or device information even if I add them manually to "MagiskHide Props Config".

Then I tried to decompile the Banking App so see if I'm able to find the redirect or maybe some properties they are checking for but also no luck.

Anybody some more ideas?

Many thanks in advance.
[Magisk] Didgeridoohan:
I managed to test the app and like pretty much every single test lately I had no issues hiding root

Android Pie, Magisk v19.4 (19307) Canary release with hidden Manager and the app on the Hide list.

More root hiding details here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

I'm rather curious about your report about MagiskHide Props Config though. I'm the creator of that module and I would really appreciate if you could pop over to the module thread and continue there:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

If you could post there with all the details of what you've done and the results, together with the module logs, I would be very thankful.
[Magisk] CryptMan:
I think I found out whats going on.

First, CPU-Z reads the property "ro.build.display.id" which was not manipulated.

Second, my Banking App checks for UDS/STAT (RootbeerFresh pointed me that way).

On my test device with Magist 19.4 (Canary) it works ... but not on my "production device", anyway I found the cause.

May thanks
[Magisk] Realkeyjoyfree:
What the summary of this?

Is magisk be detect

So we have to downgrade to 17 version

Or we upgrade to 19.4 becoz the problem is solved
[Magisk] Tr4sHCr4fT:
German Fidor Bank App now also detects Magisk (Zenfone Z)
[Magisk] Didgeridoohan:
You sure? Have you tried everything that's been discussed in the thread and from the guide that's been linked a few times. This one:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Tr4sHCr4fT:
Yes

* Stock FW

* Magisk v19.3

* Core Only Mode / no modules

* Manager repackaged

* App put in Magisk Hide

* no files/folders of Magisk in /sdcard

* UDS fix applied

No problem with other bank apps or GPay...
[Magisk] Didgeridoohan:
You mean this app, right:

https://play.google.com/store/apps/details?id=com.fidor.fsw

If so, I have no issues hiding root from it... Custom Pie ROM, Magisk Canary 19307 (with hidden Manager, of course), app on the Hide list, lots of modules and lots of Magisk files on the device.
[Magisk] Manut38:
So, I'm at the exact same position right now.

Any other app works but my banking app (Fidor) detects root.

Oneplus 5T

OxygenOS Beta 33, all stock firmware

Magisk Canary 19307

And all the other things mentioned above.

The only thing I haven't tried is toggling the "OEM unlocking" switch back to off, because I don't really know how it will behave when I do that.

Can someone tell me if I can simply toggle it back without consequences?

And what could I be missing?

I'm surprised that it works for Didgeridoohan, I really thought this app is just too strong for us :D
[Magisk] Didgeridoohan:
I do have OEM Unlocking set to off (I have an OP3T, by the way)... Shouldn't be an issue on devices closer to stock Android (unless it's an old, old Android version).
[Magisk] MeZen81:
Any help guys
[Magisk] Tr4sHCr4fT:
I'm stuck on 6.0.1 forever, is this 'old-old'? (/proc leak)
[Magisk] Didgeridoohan:
Old enough for proper root hiding to be impossible.
[Magisk] Gimmly:
Try the newest Canary Magisk, IT works for me
[Magisk] mrsus01:
Not working on Canary Magisk, Hide the Manager and using Magisk Hide.
[Magisk] Gimmly:
Works for me... Use Canary, repack Manager and Check magisk hide. Stable get detected by Fidor...
[Magisk] Nemorensis32:
Hello,

Here is my root status. There are so many problems that I don't know where to start!

I use KTB Bank which is a Thai bank and the app turns to "restrained mode". The problem is that I don't live there anymore and I need access to the account.

I removed Lucky Patcher that I used to disable intruding privacy modules of some apps.

Please, what to do?

Edit :

- Politeness ?

- More accuracy
[Magisk] Nemorensis32:
No answer?? ??
[Magisk] Tr4sHCr4fT:
I'll wait for 19.4
[Magisk] geek85:
I have the exact same error on a Honor 9 (STF-L09)

on Android 7.0 with Magisk Canary 19.4-736729f5
[Magisk] knives of ice:
I'm using the latest canary build on the Q beta for OnePlus 7 Pro

I get the following errors even after magisk hide

- won't work because magiskmanger is insalled - even after going into settings and choosing to hide magisk manager it is still detected. i get the following error:

Please disable MagiskManager (topjohwu) then try again

- detects root, magisk hide not working.

any help or ideas?
[Magisk] knives of ice:
sorry, but is Emulator an app you get in the play store? i'm not sure what that is

4- use my andriod tools beta and disabled usage and activity monitor service for the apk ( the bank apk )

i tried this in the app. i'm really not sure what i should disable. i'll post a screenshot of what is listed until the activity tab
[Magisk] raiffeisen_hu:
I'm trying to bypass root check of my banking app (com.guidance.android.apps.raiffeisen.banklet) but since they've implemented a mobile token functionality I just can't get it to work. Other banking apps work fine.

I have frozen all root related apps (AdAway) except Titanium Backup , updated Magisk to the canary build, hid Magisk Manager, enabled MagiskHide, installed MagiskHide Props config, selected Xiaomi Mi A1 9.0.0 as my fingerprint, enabled advanced hide, implemented the UDS fix, removed Vanced and reinstalled YouTube (according to the logcat apparently there was a check for that) and I have even decompiled the apk to see what's going on. Between each step I've force stopped the app and deleted the data. When I disabled a module, I've restarted the whole system

During the check of the decompiled code I could determine that it uses Vasco's Digipass technology and logcat revealed that the app tries to access another Vasco product on the system. Also when there was no data connection, an error message popped up saying the service is not available. First I thought this was from the banking app's core but actually this was a Vasco error message. I have a feeling that maybe they have a list of banned devices, so if the root check fails once there is no way to be authenticated.

At this point I'm kind of out of options, so if there's anything I've missed, I'd be glad to try that.

I've collected and uploaded a bunch of logs here: ufile.io/zc22crpa

My phone is a Xiaomi Mi A1 with the latest LineageOS 16.0. RootbeerFresh returns all checks as passed.
[Magisk] Didgeridoohan:
Does the app trigger before or after the prompt to enter id and password? When I tested I had no issues getting to the password prompt, but of course I could not go any further.
[Magisk] belidzs:
Deleted
[Magisk] Didgeridoohan:
[MENTION=10114432]raiffeisen_hu[/MENTION]

So... If the app triggers it's root detection at start, and before you even get to the password screen for the mobile token, the fact that I can get all the way to the password input without issue likely means that it's perfectly possible to hide root from the app. Could be something to do with specific device setups, which is sometimes really hard to troubleshoot...

As usual, everything I've got is collected here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] raiffeisen_hu:
Thanks for trying to help. Your otherwise excellent guide unfortunately didn't help me this time, so it seems like I'm stuck with this problem. Thanks again
[Magisk] seemebreakthis:
... add another app to the list. "UBS Access" com.ubs.swidK2Y.android. Mine got updated on Sep 7, since then it has been detecting root. Tried some of the methods mentioned here to no avail... :(
[Magisk] TheFerhatKing:
Can anyone test the Commerbank Banking App https://play.google.com/store/apps/details?id=de.commerzbanking.mobil&hl=de ? I did everything possible from here https://www.didgeridoohan.com/magisk/MagiskHide# but the App closes even before I can write my login.
[Magisk] Didgeridoohan:
Tested and as long as it's on the Hide list it won't crash at the login screen.

Edit: Android Pie, Magisk Canary (19308), hidden Manager (233).
[Magisk] TheFerhatKing:
So you could stay in the app without a crash? Its on the list but still crashes for me..
[Magisk] Didgeridoohan:
Yes. Stayed on the login screen for several minutes without issue. With the app off the Hide list it would crash within seconds...

Take a look in the guide again, there might be something you've missed.
[Magisk] TheFerhatKing:
I don't get it.. Using a S7 edge (Android Pie, Note 8 ROM) with latest hidden Magisk Canary, SafetyNet passes both, even got GPay working. Searching the issue for hours now.. The app does not work wihout beeing in the list and with beeing in the list. You got some apps installed like Titanium Backup for example?

Edit: Even no luck with Magisk Core only.
[Magisk] Didgeridoohan:
Lots of root apps, like TiBu... Could be the ROM, could be KNOX (if you're really unlucky), etc. It's impossible for me to say exactly what it could be.
[Magisk] Tr4sHCr4fT:
switch to comdirect ;)
[Magisk] seemebreakthis:
Just tried the latest canary Magisk build. Doesn't work for this "UBS Access" app, although there is one other bank app that now works with canary build installed (the HSBC HK app).

Fingers crossed real experts out there will give this a crack. Thank you !!
[Magisk] Tr4sHCr4fT:
I've had to install it today too, for PSD2.

Instacrash without in Hide, but worked stable after hiding. Magisk 19.3 Core on x86 Marshmallow 6.0.1

Looks for me like one of the simple-to-bypass checks, not a tough one like Yomo or Fidor use.
[Magisk] TheFerhatKing:
Which root apps you got installed? I don't get it why it doesn't work with mine.. something other than magisk causes this because it's not the fault of magisk, Google Pay works perfect.

Gesendet von meinem SM-N950F mit Tapatalk
[Magisk] Tr4sHCr4fT:
Link2SD, AdAway, Titanium Backup.
[Magisk] TheFerhatKing:
Strange, slowly I start believing that it really could be Knox.. I don't think so that the cause is one of my apps, I freezed them with Titanium and even tried uninstalling some of them. No luck, even with removed sd card.

Annoying..

Gesendet von meinem SM-N950F mit Tapatalk
[Magisk] kozseb:
Guys, just change the name magisk manager.
[Magisk] Tr4sHCr4fT:
I've now also tried latest canary, still no luck.

As a last resort, reflashed stock.

But it still instacrashes on start, redirecting to the 'modified' web page.

Looks like it just doesn't like my particular phone then...
[Magisk] BlazeGarden:
Did have the problem with a Dutch banking app (ASN) with magisk hide already selected for the specific app. After repackaging magisk manager with a random name and toggle magisk hide off / on under settings. it started working without detecting root. Running magisk 19300 and manager 734. This will probably also work for the SNS banking app because the detection mechanisms seems to be looking for magisk manager name.
[Magisk] seemebreakthis:
Latest canary stable build (19403):

UBS Access App - working

HSBC Canada - not working, root detected, but the app itself merely gives you a warning and lets you comtinue
[Magisk] Fil76:
Anyone can help me with nexi pay ?

Tried also with magisk canary but no luck

Edit:toggled Hide on / off solved
[Magisk] FernanZ:
After being unable to have the Magisk Hide menu to hide apps, I completely uninstalled Magisk using the Canary Magisk Uninstaller (valid to uninstall any version of Magisk), and then installed Canary Magisk Manager and then Magisk from the Manager.

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

Now I have the Hide menu and CiC and Starling apps work on my Xiaomi Mi 8.