Database Develop

Samsung Pay and Magisk

Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.

Same. Then this droidx program protecting pay app
Sent from my SM-N910V using XDA-Developers Legacy app

Try the universal safteynet net module

Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.

grymkmb said:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
Click to expand...
Click to collapse
I'm on an LG

I've got the same issue with galaxy tab 3
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.

Same problem here; Magisk works but Samsung pay won't work

Even tried freezing magisk. Though still no go must be detecting something.

hkbladelawhk said:
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
Click to expand...
Click to collapse
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.
If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)
sevenday4 said:
I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner.
Click to expand...
Click to collapse
Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.

There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Booo!

someone please made an apps that can hide or fake the Knox status.

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
This is possible by disabling safetynet check at boot level before compiling the kernel

Iradj said:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
Click to expand...
Click to collapse
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.

gghose said:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
Click to expand...
Click to collapse
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.

Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.

Magisk hide 14
Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in [email protected]. Thank you so much. Bye.

Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.

Spot on fella, just got it working on OP5 with lineage ROM.

dcbii said:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
Click to expand...
Click to collapse
Root explorer won't let me remove it from xbin. How exactly did you do it?
Sent from my iPad using Tapatalk

Kernal or ROM that hides KNOX Trip?

Hello,
I rooted and installed a custom ROM on my Note 9 a couple of months ago and yesterday I was getting annoyed not being able to use apps like Android Pay, Samsung Pay and Banking apps, So I decided to use Odin to flash the stock ROM back and set OEM Unlock to OFF. To my Horror, I found out the hard way about what a KNOX Trip was. I have no idea how I missed all the warnings on every ROM post about tripping it and not being able to change it back. I can now use my Banking apps, Android Pay and play Fortnite however, Because of the Knox being tripped I can no longer use Samsung Health and Samsung Pay
My Question is is there a way to just install a custom kernel or ROM that tricks apps like Samsung Pay and Samsung Health into working again without installing root and having modifications hidden so I can use my Banking apps and play games??
Any Help is very much appreciated!

After a bit more searching the forums and Google I now understand that no matter what I do I can't get Samsung pay to work which is fine. However any help on the rest is still appreciated! ?

You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query

bober10113 said:
You should go read some more as you also missed the part where tou can use magisk hide. but it wont get back spay.
Just use the forum sarch feature as if you were google searching ie:
magisk shealth
magisk hide
magisk google pay
magisk android pay
magisk insert what ever query
Click to expand...
Click to collapse
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.

VortexHD said:
I did use Magisk Hide to hide root from apps but some apps could still detect the custom rom was installed.
Click to expand...
Click to collapse
so for example you went to magisk hide menu and selected your banking app and it didnt work?

bober10113 said:
so for example you went to magisk hide menu and selected your banking app and it didnt work?
Click to expand...
Click to collapse
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.

VortexHD said:
Yes i selected my banking app along with google pay and all its services and Samsung pay with its services and none of them worked.
This also doesn't work for pokemon go and fortnite.
Click to expand...
Click to collapse
how about safety net status, is it passing?

bober10113 said:
how about safety net status, is it passing?
Click to expand...
Click to collapse
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.

VortexHD said:
Yes Everytime. I'm about to flash TWRP and only install a custom kernal with no root.
Click to expand...
Click to collapse
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.

bober10113 said:
try endurance. but besure ure rom base matches kernel ramdisk or u won't be able to get past lock screen. so do a full twrp backup in case
or just try dr ketan. usualy best all round working rom.
Click to expand...
Click to collapse
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?

VortexHD said:
I have installed a custom rom without root access and my banking app and games work perfectly however Google pay is detecting the unlocked bootloader. Anyway to hide this with out rooting the phone?
Click to expand...
Click to collapse
for google pay, some actualy revert to an older version. just search the forums. for me magisk hide works great with my banking app. and for games, im not much of a gamer so i realy dknt know. but again you should try with dr. ketan rom just in case it works. just choose to flash kernel and magisk during setup.( do a clean install so factory wipe in twrp before flashing his rom)

Well i decided to just use Stock Rom and lock the bootloader so at least most of my apps then work. I installed a modified apk of Samsung Health but it doesn't contain the heart rate monitor but I suppose that's fine and I just have to accept that Samsung Pay will never work again

Where can i get the old version of Google pay which works with unlocked bootloader?
Sent from my SM-N960F using Tapatalk

S heath can work on a rooted device with a simple change to the build prop , but secure folder and spay remain a dud

Safetynet bypass

So did anyone tried bypassing safetynet while on rooted custom rom?

Sure,with magisk module called MagiskHide Props Config.

-CALIBAN666- said:
Sure,with magisk module called MagiskHide Props Config.
Click to expand...
Click to collapse
i got play store to show my device is certified, but still out of three one banking application was able to detect that my phone is rooted, any ideas? but not a big deal they allowed it to work, just curious.

MagiskHide, and much the same if you use Xposed. Then clear storage/cache of those apps and try again. Hopefully you'll get it sorted.

I installed it after that, after certified and having device verified.
Still thank you.
Btw I installed another microfinance bank app and that won't work, I can work using dialer codes, since that bank and my carrier are same, but would love to use app instead of dialing code

Looking for some tips - Unable to get these two Belgium apps working with Magisk

Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Edit 1: After installing Universal Safetynet fix (https://github.com/kdrag0n/safetynet-fix), payconiq works, but not Keytrade.

Easiest way is to use a good browser like Brave to login to the bank's website bypassing the app.
I consider banking apps to be trash apps and never load them. The more needless apps you load, the greater the security risk.
Apps I sometimes use but don't like their behavior I package block when not in use and/or firewall block.
Rather than fight it, bypass it...

blackhawk said:
I consider banking apps to be trash apps and never load them.
Click to expand...
Click to collapse
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.

Ramihyn said:
Not helpful, because thanks to EU rules many banks simply and mandatorily require their app as the second authentication factor - especially when you don't want to use their "real" banking app and use the oldfashioned web interface instead.
Click to expand...
Click to collapse
That sucks... so much for easy fixes

The Transporter said:
Hi,
I live in Belgium and it's been years that I'm using Cyanogen, then now Lineage. Recently, I made a bargain and bought 2 Google Pixel 4a, one for me and one for my girlfriend.
I installed Lineage on both of them, and I have to say that it's the best Android experience I had so far. We both love our device. It's small, powerful enough, camera pictures are amazing.
However, we are unable to get any banking apps working. We would like to use 2 applications:
1. Payconiq: https://play.google.com/store/apps/details?id=mobi.inthepocket.bcmc.bancontact&hl=en&gl=US
2. Keytrade: https://play.google.com/store/apps/details?id=be.keytradebank.phone&hl=en&gl=US
I succeeded to get Payconiq working on my phone, using Magisk 23 and Magisk hide. So far so good.
Since this morning, Magisk has been updated to 24.1, Magisk hide is gone and I have to use Magisk Zygisk... And Payconiq doesn't work anymore.
Regarding the second app "Keytrade", it never worked, with any version of Magisk. I don't know what they did in their app, but it seems that they were able to find a way to detect if a phone has a custom rom pretty nicely.
Maybe this is something that the author of Magisk should be aware of? Maybe I'm doing something wrong?
Do you have any piece of advice for me? I don't want to be forced to re-install the official rom, I still want to use Lineage and have those apps working.
Thanks!
Click to expand...
Click to collapse
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com

Austinredstoner said:
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Click to expand...
Click to collapse
Safetyfix passes on the phone... I don't know how the Keytrade app is doing to detect root on the phone.

blackhawk said:
That sucks... so much for easy fixes
Click to expand...
Click to collapse
So true Unfortunately, that seems the way to go in Europe considering banking. If you want it online instead of running to the bank clerk all the time, you're stuck with at least some authentication app. Things get only worse when there's no classical webinterface at all and you're bound to use a complete banking app instead (there are some neobanks doing so already).
The Transporter said:
I don't know how the Keytrade app is doing to detect root on the phone.
Click to expand...
Click to collapse
They simply recognize Magisk app in some way. I've read in some other threads here that a probable solution is to use the app called "Ice Box" to hide the Magisk app by freezing it. Might be worth a try for you.

Another way if you have zygisk enabled. Go to config denylist select play store play services gms you need to hit menu system apps first. And you apps you wish to hide. Then search magisk alpha telegram channel. Download shamiko module. Reboot your phone with enforce denylist selected. After reboot turn the enforce denylist toggle off and flash the shamiko module and reboot. If your app still does not work and you are using lsposed zygisk. You can download hide my applist Xposed module and further hide your app.
Pm me if you want to links to all as they are not supposed to be posted on xda

Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app

Awaces said:
Have you managed to fix this?
I'm in the same boat.
My bank app 'keytrade bank' keeps detecting that I've rooted my device. This is what I tried
- I installed Magisk
- Installed module Shamiko
- Installed SafetyNet Fix v2.2.1
- Enabled Zygisk
- Configured DenyList
- Hide Magisk app
Click to expand...
Click to collapse
You have to disable Enforce DenyList in Magisk.

Question How do I hide root from certain apps?

Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
After force deny list did you've deleted caches of google play and google services and reboot? check also google play store inside settings if certified, if certified then it should work for your app too.

Maybe try installing Universal SafetyNet Fix?
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
And some applications can be extra finicky. LIke for me, Google Pay always takes its time to get persuaded about not being rooted. Also there might be other components either of this app or for system apps that might need hiding. I would generally try following guides for making banking apps work.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
I'm not familiar with that app, but I know that some apps also check for the presence of the Magisk Manager app. If you've already tried Zygisk and the deny list, then another thing to do would be to hide the Magisk app. It the Magisk Manager, go to Settings > Hide Magisk app.

What worked for me is installing Insular ( from Fdroid) and then clone the App that complains about root to the work environment.

I just downloaded musescore and installed it. It hasn't detected root on my phone. I use Shamiko to hide root. Get Fox's magisk module manager from fdroid. Then use it to install Shamiko. Make sure you turn off Enforce Denylist in magisk so Shamiko can enforce the deny list. Hide the magisk app using the feature in magisk. It works for me.

YayJohn said:
Hey, I rooted my phone just yesterday, and today I went to musescore just to see that they for whatever reason don't allow rooted phones to use their app?
So I tried enabling zygisk, DenyList, and I added musescore to the denylist and restarted my phone, but somehow musescore still knows that I'm rooted.
Is it possible that vbmeta is somehow related? if so then what file exactly am I supposed to flash as vbmeta (I use custom ROM).
If not, then what can I do to hide root from the app?
Click to expand...
Click to collapse
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.

BigChungus321 said:
Oh yes I can't seem to open musescore too even with safety net pass. But it is because I am using MicroG. I tried it on my other phone with Play Services and it works fine with hidden root (shamiko and magisk disabled) and safety net pass.
Click to expand...
Click to collapse
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.

IrishJames said:
I use MicroG as well. I can load the app and use it, I just can't subscribe because it requires GSF to make payment.
Click to expand...
Click to collapse
You can open it right? But can you select and open a random piano piece or something like that. For me, the piece loads up then detects something (root, safety net idk) then just tells me I can't for root reasons. I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece. It does load the main menu for me too on MicroG+patch playstore but can't open the contents.

It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
BigChungus321 said:
I tried using shamiko too and all the root hiding methods I know and I still couldn't open a piece.
Click to expand...
Click to collapse
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?

POTENTIAL FIX: So in new versions of magisk, the developer decided to remove magiskhide. Turns out that having magiskhide turned on makes musescore actually be able to function. I tested this on my samsung s7 edge (didn't want to brick my Xiaomi phone by accident just yet and it worked. However I labelled this 'POTENTIAL' as downgrading magisk isin't really a plausible fix and could still be considered a workaround.

RoboNinjaR said:
It's been roughly a month. Has anyone found a fix for this issue yet? There was discussion about the issue here where a dev 'fixed' the app for someone with a rooted phone. However I cant tell what the dev did because all his messages are deleted, for all I know he could of shared an apk or something, guess I'll never know. I've decided to try to get in contact with one of the people whose issue managed to get fixed, although I don't know if he'll ever respond. Apparently in the forum, he told the dev that he assumed the block was intentional. Maybe this could hint us towards a fix because maybe the block doesn't target rooted users?
If thats the case then perhaps the app isin't checking for root? Theres no way musescore has more sophisticated anti-root software than some banking apps out there. Perhaps it's detecting the os that the user uses instead? I can confirm this because my samsung s7 edge with the same lineage os version as my Xiaomi doesn't want to play any scores either. This issue also happens to people who have no custom rom or even no root, it has to do with the os that you use rather than being an issue with root.
So what, did I type 2 paragraphs on a one month old forum just to rant? No. I will find the issue (well, I already found the reason in the text above), and I will try to fix it, not by making any workarounds such as cloning the app but getting the app to reliably work on a rooted / custom rom phone.
EDIT: Maybe using something to spoof the OS to make apps think it's a different OS?
Click to expand...
Click to collapse
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.

BigChungus321 said:
Its not opening for me because I'm using MicroG. Like banking apps, MuseScore checks for specific Play Services version. Since microg uses idk android4.4 play services, it will fail to load any Banking Apps or apps of the same kind that uses that check regardless of root 'cause that version's too old and a potential for security. For the OS check, I guess it does check it too. I tried on two emulators and both failed to load a piece as well (might be because of safetynet cuz emulators can't pass it). There are xposed and magisk modules that can spoof OS and even prevent the app from seeing user installed apps. I haven't tried that method because I switched ROM now and got MuseScore working fine even without hiding root.
Click to expand...
Click to collapse
Weird. I have microG and I managed to get musescore working without switching roms. All I did was use safety net fix, enabled zygisk and added it to the deny list. Tried it before and it didn't work, probably because I didn't install safetynet fix. Who knows, maybe it's related to what type of GApps you install. I guess this issue is fixed for now.