Sorry, I forgot to mention that my phone runs MIUI 12.5.1, android 11. Xiaomi mi 9 see. I'll try to disable Lucky Patcher. Thanks.
Banking app (Starling) detecting Magisk
- Thread starter makeyourself
- Start date
-
- Tags
- magisk root detection
Then I'm not sure to be honest. You are on Android 11, which is probably relatively uncommon these days. So at a wild guess, it could be something to do with that.
I see you use Shamiko, at one point Shamiko was tripping Starling. This was fixed but it's worth disabling it to see if that makes a difference for you.
And finally, you can try disabling Zygisk (Play Integrity will fail). If the Starling countdown goes away (or it lets you login), you can enable Zygisk again and the countdown will probably have reset.
If none of that works, then aside from trying an unofficial Magisk fork I'm stumped lol
I have miui as well, Xiaomi eu, haven't gotten it to work even after trying every setup shown here.
I think this may be @VetalM84's issue then because I just tried it on an old device I have with Xiaomi.eu MIUI and yeah it won't work for me either.
I've disabled root, as a result, Staling worked but Gpay didn't. I've installed root again and Gpay works, Starling does not 
And I cannot bypass Starling's notification screen even if I have 14 days left
My device has [meets_basic_integrity and meets_device_integrity]
And I cannot bypass Starling's notification screen even if I have 14 days left
My device has [meets_basic_integrity and meets_device_integrity]
Hi @snake-4 to let you know:
this module helped to hide LineageOS for another app I have that detects custom ROM! I've checked its code: nice work!
There is also this other older one:
https://github.com/Magisk-Modules-Alt-Repo/ezme-nodebug
This one seems to be also changing some props that you don't.
It will be interesting to kind of mix both, add the props that the other dev has found to yours and then have a v1.1 of yours.
And then publish it as a new thread/tool on XDA Magisk section! (Module to hide LineageOS/custom ROMs in general if properly adapted).
There is currently nothing like that!
Thanks!
I somehow managed to get it working on Lineage OS 21 (razer phone)
I upgraded from Stable to Canary (Magisk)
Ive hidden Magisk
have Zygisk enabled
and enforcing denylist
and am using the following modules (not sure if all are needed)
Play Integrity fix v16.9
playcurl v10.7
Shamiko v1.1 (Turned off)
Starling Bypass 1.0 (Turned off)
Systemless hosts v1.0
Zygisk - LSPosed v1.9.2
Zygisk Assistant v2.1.2
I am also using the adaway with blocking the attached
hope this helps anyone using this
p.s. Too a while to get working hope this helps
edit. I have turned off a few and still working
I upgraded from Stable to Canary (Magisk)
Ive hidden Magisk
have Zygisk enabled
and enforcing denylist
and am using the following modules (not sure if all are needed)
Play Integrity fix v16.9
playcurl v10.7
Shamiko v1.1 (Turned off)
Starling Bypass 1.0 (Turned off)
Systemless hosts v1.0
Zygisk - LSPosed v1.9.2
Zygisk Assistant v2.1.2
I am also using the adaway with blocking the attached
hope this helps anyone using this
p.s. Too a while to get working hope this helps
edit. I have turned off a few and still working
Last edited:
Question.
Can do the same (Magisk Module) for remove or hide a permission from AndroidManifest.xml ?
I have a app who detect a other 'app' and say to uninstall.
Hi @snake-4 check this thread on some concerns about props changing/delete and folders/files that may give traces of a custom ROM/LineageOS. Maybe you can help with your knowledge, thanks!
resetprop (deletion) detection
Hi Some apps check props for indications of custom ROM (eg "lineageos", "userdebug", "test-keys"). As such it can be useful to hide these properties. I've been experimenting with some modules that do just that and generally they do two things...
xdaforums.com
TS won't stop apps detecting root, it's useful for apps that are looking for a locked bootloader or requiring strong integrity.
It just started working for me again, I'm not sure what it is but the app has a new design overhaul.
I'm running KSU with
PIF 17.2
Playcurl 10.7
Zygisk next
Zygisk lsposed
HMA not installed.
I'm running KSU with
PIF 17.2
Playcurl 10.7
Zygisk next
Zygisk lsposed
HMA not installed.
Last edited:
Nekromantik
Senior Member
Starling works on P9 Pro XL using Canary and Zygisk Assitant. Make sure starling is in DentList and dont force Denylist
The issue with starling detection of root is with Lsposed Jingmatrix. Not sure how to hide Lsposed from starling.
Hello snake-4,
I tried this on LOS 21 on OnePlus 6, but Momo and Securify both still detect Custom ROM.
BTW, I'm passing STRONG integrity and Google Play settings -> About showing device is certified.
Using:
TrickyStore with unrevoked keybox.xml
PIF
Zygisk-Assistant
Shamiko
But Microsoft "Intune Company Portal" still detecting root, despite being on the deny list (and enforce deny list is off).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
I have found some banking apps are calling an external site and somehow they are detecting reporting back root. I had an issue with Halifax and Starling before.
Starling for me tripped over the last few days, and I used pcap droid to trace what hosts it was calling during app start up.
I found that when i blocked the following address:-
firebaseremoteconfig.googleapis.com
it all worked OK.
Try it if you use Adaway or a DNS provider and add this to your blacklist7- KSU or APatch
- Zygisk Next (v4-0.9.1.1 also works if you want a FOSS setup)
- Zygisk Assistant (v2.1.1)
- Reset LOS Props (attached)
The setup above will work without HMA. I haven't investigated why Magisk doesn't work yet.5If this helps anyone here i made a Magisk module to bypass the root check screen.
https://github.com/corndoghh/Starling-Bypass/5Guys, I know what happen. Starling detect resetprop utility, if you set any prop using that Starling will detect it. Hopefully I used magiskboot and modify cmdline to patch ro.boot.verifiedbootstate and ro.boot.flash.locked.
(I'm using stock Indo rom for vayu with modified super.img and now boot.img).
Now I lost root, I will root again and I will see.
After my research I have discovered that it detects Starling:
- Detect any Zygisk including Magisk Delta and Magisk Alpha, Shamiko doesn't help.
- Detect resetprop utility, any module using this Magisk tool will be detected.
- Detect su binary.
- It does NOT check Play Integrity neither SafetyNet, you can fail Device integrity (CTS profile) and app can work.
- It does NOT check sensitive properties (like ro.boot.verifiedbootstate and ro.boot.flash.locked).
- It does NOT check patched images (as someone said earlier).3
