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
Is there a module to bypass/cloak a tripped Knox & root access to enable use of Pay?
I'm thinking of something like Root Cloak (When it worked with Snapchat) - except working and for the new Nougat Xposed. I'm using the Galaxy S5+ on a Resurrection Remix rom.
You could say "Well why not just use Root Cloak?" but the module says that it only supports 5.x.x & 6.x.x., whereas I am on 7.1.1. Thank you for any help
Note: My KNOX is tripped and there is no reset. I'm hoping that there is a module that will cloak this and/or at least fool Android Pay to work on my phone.
No.
Sent from this galaxy
Hi guys,
I would like to enable fingerprint login on my banking app but cannot get the prompt to show up to register a finger for the life of me.
I have rooted my device with Magisk and tripped knox e-fuse, also have installed xposed; removed Samsung Pass from my phone totally, it was in the /data/app/com.samsung.android.samsungpass*/ folder, which I just deleted. All references of samsung pass have been removed from my lockscreen and security settings. Anything I'm messing?
I followed this thread: https://forum.xda-developers.com/general/rooting-roms/samsung-pass-knox-tripped-devices-t3687977 though I had nothing in the /system/* of my phone relating to pass.
Thanks
I got a custom ROM and it tripped KNOX, I got bored of the custom ROM and went back to stock android, not realising I had tripped my KNOX somehow. After finding this out due to secure folder not working and my banking app (barclays) sh**** itself on me I decided to root it since I had nothing to lose. I use Magisk and for a while the barclays app worked, until it didn't, and I haven't been able to get it to work anymore.
I've tried:
- Hiding the app
- Changing my android ID with both apps and the adb shell
- Reinstalling and trying all of the above
I need help as it's crucial for me to get this app to work again, I haven't had it for a couple of months but now that I have an actual income i need it.
And if I can't get it to work, are there any banking apps that support barclays?
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
With google coming up with increasingly stricter policies of what deems a device safe and rise of hardware attestation for safetynet, does the note 10 face these issues, or do the payment/banking apps work fine?
I have a Samsung A51 and once my device was rooted the Samsung Pass application will not allow me to record and use any security passwords or biometric security. The application gives me a message stating that because my device is rooted I can no longer use Samsung Pass. However, I am still able to use passwords and biometrics on my bank accounts application.
Last year, I changed the firmware of the LG V35 ThinQ I had and Google Pay would not work for me.
if it comes rooted yes , you will have to hide the root otherwise wont work
Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.
TechV said:
Everything works fine for me. I'm using a custom rom and I'm rooted. Play store shows my device is certified, and it passes safetynet on magisk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Same here
mite_jan said:
if it comes rooted yes , you will have to hide the root otherwise wont work
Click to expand...
Click to collapse
What is the best way to hide the root?
To hide root, enable magisk hide, and change the magisk manager to something else, like mgsk. I enable gpay in magisk hide, and even changed magisk manager to mgsk (You can use any name, but remember the name you change to), and I'm now able to access gpay. Works everytime.