Samsung Pay and Magisk

[hkbladelawhk]

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.

 

[davekaz]

Same. Then this droidx program protecting pay app

Sent from my SM-N910V using XDA-Developers Legacy app

 

[candiesdoodle]

Try the universal safteynet net module

 

[grymkmb]

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

 

[hkbladelawhk]

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

I'm on an LG

 

[sevenday4]

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.

 

[vooks]

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

 

[hkbladelawhk]

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

 

[alexbelgium]

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.

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)

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.

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.

 

[Iradj]

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

 

[hkbladelawhk]

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

Booo!

 

[Schuan]

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

 

[filjusz]

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

This is possible by disabling safetynet check at boot level before compiling the kernel

 

[gghose]

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

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.

 

[Yeti47]

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.

Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.

 

[dcbii]

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.

 

[menkent]

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 menkent33@gmail.com. Thank you so much. Bye.

 

[dcbii]

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.

 

[jknaggs]

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

 

[schmaltzy]

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.

Root explorer won't let me remove it from xbin. How exactly did you do it?


Sent from my iPad using Tapatalk