yashsingh1/xdaforums huggingface dataset:
[Magisk] coolhandz:
I have no idea. Just got an SPay update today and now it is not working. I've uninstalled all Magisk modules, but it still is not working.
[Magisk] wy1d:
Exactly same for me. I'm on Pixel 2 XL.
[Magisk] coolhandz:
I'm on the Pixel XL. Are you using a custom rom or are you stock w/ magisk?
[Magisk] wy1d:
Stock with Magisk and stock recovery, stock kernel. Just the patched boot.
[Magisk] coolhandz:
Then it's safe to say that it is detecting Magisk. I'm on a custom ROM. Maybe go through and start hiding it from other system apps? Ugh. Samsung can be suck crap-heads sometimes.
[Magisk] wy1d:
I did the hide Magisk Manager setting and that didn't work. I'm not sure what else it can be detecting. I tried revoking storage rights to see if it was looking for the presence of a certain file or folder but it immediately requested them again and doesn't launch if it's doesn't have storage rights.

I'm surprised Magisk Hide wouldn't hide other things from the apps listed.

---------- Post added at 04:51 PM ---------- Previous post was at 03:57 PM ----------

Hey! It's working now. I did the hide Magisk Manager and then rebooted.
[Magisk] MrBrady:
Can you outline the steps you took to get it working? I hid Magisk Manager and rebooted, but Samsung Pay is still throwing a security error.
[Magisk] Xgztylm:
Amy luck for a s8+? I got a gear s2
[Magisk] coolhandz:
Are you talking "hide Magisk Manager" in settings? I try that and it fails.
[Magisk] ugvpkn:
I am also having trouble with Samsung Pay after it upgraded to version 1.6.x on a Nexus 6P. I have Magisk 15.3, everything Samsung is hidden in Magisk Hide, did the 'hide magisk manager' also. Looks like Magisk Hide needs an upgrade !!
[Magisk] Didgeridoohan:
And for that to even be a consideration, one of you guys are going to have to figure out what it is that triggers Samsung Pay...
[Magisk] coolhandz:
Checking out the LogCat, but to TBH i am code illiterate.
[Magisk] wy1d:
I am completely stock (Pixel 2 XL) except for Magisk with patched boot. I have all Samsung apps hidden via Magisk Hide. I'm on Magisk 15.3 and Magisk Manager 5.5.5. I did hide Magisk Manager in settings. I don't have busy box installed anywhere.
[Magisk] MrBrady:
I'm willing to diagnose. Any idea where to start?

Already posted a logcat in the Magisk Discussions thread.
[Magisk] Didgeridoohan:
I know, I saw it. It's absolutely massive though... Can you try to capture only the part where the pay app triggers?
[Magisk] MrBrady:
Maybe that's the difference. Are you saying you patched the stock kernel through the Magisk app? I have just been flashing Magisk through TWRP. Maybe the patching is slightly different.
[Magisk] wy1d:
That's right. I have stock recovery, no TWRP.
[Magisk] coolhandz:
Here it's something that might work better.
[Magisk] MrBrady:
Here's the portion where I see Samsung Pay popping up a lot:

https://pastebin.com/7ZekyQ8m
[Magisk] MrBrady:
Just saw a new log that's on the root of my SD card from Samsung. Clearly is detecting Magisk. Maybe this provides better info?
[Magisk] MrBrady:
Just tried going back to stock kernel, dtbo and recovery and patching through Magisk. Samsung Pay still throws an error for me.
[Magisk] wy1d:
Hide Magisk Manager also?
[Magisk] MrBrady:
Yes. It had a random name (still called Magisk in front-end).
[Magisk] Didgeridoohan:
There's this in both your logs:

SAMSUNGPAY.GEAR.SpayBaseActivity: AppShield AlertPopup: exit - SECURITY_THREATS_DETECTED_ROOTED

Doesn't say much...

This one's interesting and is probably a big clue. I wonder what it is they're detecting... Let's see if some more knowledgeable people can chime in.
[Magisk] coolhandz:
I saw that when i was going through. Not sure how to figure out what triggers it though....
[Magisk] wy1d:
I don't see that line in my log. Oddly tapatalk won't let me post it.
[Magisk] MrBrady:
Good news is we can roll back to a previous version of SPay and it works fine. Unfortunately current version of SPay needs to be uninstalled first which means you have to set the credit cards again.

https://www.apkmirror.com/apk/samsu...g-pay-for-gear-1-5-6306-android-apk-download/
[Magisk] coolhandz:
I went this route, but is there a way to stop the update other than clicking 'later?' Just want to find something more permanent until we can figure this thing out and i don't want to have to worry each time it pops up.
[Magisk] MrBrady:
Not that I'm aware of. Just need to click "later" until a solution is found.
[Magisk] daddylonglegs:
I can't install this. It just says "App not installed" when I try to run the APK. Is there something special I have to do? I even tried uninstalling Samsung Gear entirely and I still get that error.
[Magisk] MrBrady:
Hm, I'm not sure. I've only seen that error if you don't uninstall the new version first.
[Magisk] daddylonglegs:
I don't see any option to uninstall Samsung Pay anywhere though?
[Magisk] MrBrady:
Go to Settings > Apps > All Apps
[Magisk] wy1d:
Oddly, the error started popping up again today. I was able to use Samsung Pay on my Gear S3 without problem at two different vendors - one swipe, one tap - but got the error when I tried to check my rewards. I haven't changed anything or rebooted so not sure why.
[Magisk] ReyStunner:
I was getting ready to create a new thread warning not to update the new samsung pay apps on the Gear S3. Did it on my classic and was unable to use SPay. Rollbacked to the previous version on APKMirror and it worked. Only downside is you have to factory reset your watch but I have all my data backed up to the cloud so No biggie. Like someone said before, you have to re-add your card which can be a pain for the banks that require you to call them to verify.

Right now ive unchecked the big 3 main Gear Apps from auto updating on the phone (Accessories, Gear, Gear Plugin). Hopefully with the next update it can hide root for gear again.
[Magisk] Orka82:
I uninstalled Samsung Pay (Gear plug-in) and installed the older version from APK-mirror. The only settings that got reset was the stuff for Samsung Pay. Just reconfigured and now it's working again. Guess this workaround will work untill they force the update.
[Magisk] atrix4nag:
which version of the app i should download?
[Magisk] wy1d:
Weird stuff. I noticed that my watch was no longer connected to my phone. Opened the Samsung Gear app and noticed that data had been wiped/reset. My watch still has all the previous settings but the app on my phone has been reset. I don't see that a new version was downloaded from the playstore in months so no idea how this happened over night. Is it possible there's a timebomb built into the app that if it detects magisk that after some period it will just wipe the app data?
[Magisk] farbeyondoverkill:
It shouldn't do that... I've been using magisk with my gear s2 for the past couple months and haven't had any issues. The only time my watch was reset is when I told it to whenever I would do a clean flash to get my notification sync working again.

Try adding every Samsung related app to Magisk hide. I also managed to get the Samsung pay plugin working by installing the APK from before (I believe version 1.5.6 or something), adding to Magisk hide, rebooting, then running Samsung pay from the gear app. You'll have to ignore the update prompt to keep yourself on the old version until either Magisk gets updated or the Samsung Pay app somehow doesn't detect Magisk anymore but that doesn't seem likely.

Maybe the dev for Magisk should be notified? Cause I also got the log on the root of my storage and right when I open it up it's littered with prompts about Magisk so the plugin is obviously aware of Magisk despite having Magisk hide enabled.
[Magisk] Didgeridoohan:
It's known. Can't say if there's anything to do about it though.
[Magisk] MrBrady:
PSA the new Magisk beta fixes SP for me (Pixel 2 XL) https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Magisk] farbeyondoverkill:
Are you using the latest version of the plugin with Magisk 15.4?
[Magisk] Kamkor82:
I can confirm using 15.4 on a Moto G5 plus with the latest version of the plug-in and Samsung pay fully up-to-date I'm no longer being blocked.

The changelog of 15.4 shows that they made magisk hide better looks like it may have worked its persisted across reboots.
[Magisk] gghose:
Same here! 15.4 with the Busybox Magisk Module and Magisk Hide on a Moto g5+ works.
[Magisk] Didgeridoohan:
The socket obfuscation in the new beta is pretty much a direct result of this thread, so it's nice to hear that it works. :good:
[Magisk] MrBrady:
Yes, Samsung Pay 1.6
[Magisk] arjuna_:
I'm still getting access denied despite updating to Magisk 15.4, hiding Samsung Pay, and deleting BusyBox.

I was using the version just prior to this one flawlessly and updated to see if it worked. Anything more I have to do? I have a rooted Exynos S8+ on Oreo.

Thanks
[Magisk] Didgeridoohan:
I believe the other users in this thread are using non-Samsung devices. If you have a Samsung device, Samsung Pay probably also checks if KNOX has been triggered, and that can't be hidden.

Pure guesswork on my part though, since I don't do Samsung...
[Magisk] arjuna_:
That could be the case but that would be a new change then as Samsung Pay on the Gear never previously was totally blocked on rooted phones even the Knox was tripped.

I'm still hopeful that it could work but right now will probably just roll back again
[Magisk] Didgeridoohan:
They did update the app to detect Magisk, so it's perfectly possible they added Knox detection as well...
[Magisk] farbeyondoverkill:
Oh wow I had no idea, great to see that we're getting noticed and getting results! ? I'll report back later once I update Magisk and the SP plugin
[Magisk] Didgeridoohan:
Of course things get noticed... :)

There's a lot of noise in the forums, but this is a community, and fixing things like this is usually a community effort. :highfive:
[Magisk] Orka82:
Still getting blocked on my OnePlus 3 with Magisk 16.0. What have I missed?
[Magisk] dimon222:
Click "Hide magisk manager" in options, then turn on again Samsung Pay in magiskhide.
[Magisk] Orka82:
Same thing :crying:
[Magisk] farbeyondoverkill:
Everything is working fine on my OP5 with Magisk 16. Make sure you hide Gear S Plugin and every Samsung related app in Magisk Hide. If that doesn't work then either Samsung patched the Gear Plugin again or Magisk 16 broke something in Magisk hide that won't let samsung pay work with root.
[Magisk] Orka82:
All Samsung apps checked.

No Magisk modules.

Had to go back to the earlier version again.
[Magisk] biggdevon:
I'm using SM-N920T, running Khongloi's S8 final and Magisk v16. Was able to register my device and can access the app but most of the content says I'm offline. I can get through the majority of the way through the process of adding a card but it gives the same message, of being offline.
[Magisk] LinoX:
Magisk itself installs a copy of busybox in /data/adb/magisk...

I think you can't remove it if you want magisk to work....
[Magisk] Didgeridoohan:
Yes, it does. And it's essential for the functions of Magisk.

But, that internal busybox is not exposed to the rest of your system (unless you've got some module or similar that foolishly exposes it), and since it's in /data/adb, no non-root processes can detect it. It's not an issue.
[Magisk] LinoX:
I still think there is something else.

The only app which passes safetynet, actually, is magisk manager itself.

Even with magisk hide active, the play store itself gives "not certified" no matter if magisk hide is enabled and working...and that is somewhat weird, no?

Another (banking) app finds root (while with earlier versions of magisk and magiskhide it used to work)..

I wonder if it's just me but... does your play store give you "certified" in the status?
[Magisk] Didgeridoohan:
My Play Store doesn't show the certified status anymore, but I can install Netflix and other apps that are known to use it. Try clearing the Play Store data and reboot. More on that:

https://www.didgeridoohan.com/magis...and_other_apps_wont_install_or_doesnt_show_up

About banking apps:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] MrBrady:
To get the certified status back, hide the Play Store in MagiskHide and wipe data on Play Store. Reboot for good measure, the open Play Store, accept the agreement and check the status after a few minutes. It SHOULD say certified, assuming you're passing Safety net.
[Magisk] Didgeridoohan:
Thanks, but if you'd checked the link in the post you quoted, you'd have seen that you're just echoing information...

I don't know if you misunderstood me... I didn't say that my Play Store status is "uncertified", just that it doesn't show the status. Big difference...
[Magisk] MrBrady:
When you open the menu in Play Store, do you see an option for "Play Protect"? I've noticed after clearing data in the PS, it doesn't even have a listing for status. It takes a little time for it to show up, but I wonder if enabling Play Protect and telling it to scan the apps would fix that?
[Magisk] Didgeridoohan:
I haven't cleared my Play Store data for months and months... :laugh: I also always have Play Store protect enabled and it regularly scans for harmful apps.

I'm not having any issues with Play Store certification... :D
[Magisk] gsmsource:
any new information about this topic?
[Magisk] MrBrady:
Working fine for me on Pixel 2 XL
[Magisk] gsmsource:
I assume it is different for non samsung phones. It seems that Samsung is detecting custom recovery or the magisk patched boot image because if I remove magisk and flash original firmware, spay will work again.
[Magisk] mariol66:
I rooted my Essential Phone last night, and received Access denied when trying to setup SPay. I had to flash an original image to get it to work. Patched image from Magisk was detected. Again, this was on a non-Samsung device.
[Magisk] Orka82:
I had to reset data for the Samsung Pay Gear Plugin and now it won't let me setup pay without updating the app. The updated app detects Magisk somehow so the downgrade option is gone. Running 16.3 on OnePlus 3. So, guess it's good bye for now.
[Magisk] Orka82:
It does not detect Magisk(?). Used the uninstaller for Magisk and dirty flashed original rom (factory recovery and boot image). Still same fail with Samsung Pay. Does it detect the unlocked bootloader?
[Magisk] Soooperstar:
Works for me with latest magisk update
[Magisk] Orka82:
What version? I can't use 16.4 because the 64-bit problem.

With 16.3, it does not work for me.
[Magisk] Soooperstar:
I'm using 16.4 yes
[Magisk] Orka82:
I think I tried the unofficial 16.4 with no luck. Will try again when the working official version comes.

It worked when I used the older version of Samsung pay but now it's forcing me to update before I can set up the app.
[Magisk] Soooperstar:
Yea that happened to me and I updated both Samsung pay and beta magisk and works fine for me
[Magisk] coolhandz:
I see you're using the Pixel XL like me. I'm currently on the latest version of Resurrection Remix and Magisk 16. Are you saying that with the Official Magisk Beta 16.4 and the newest version of SPay, it is working? How did you get it to work? Did you just update Magisk first, then update SPay?
[Magisk] Soooperstar:
Yes otherwise it will detect modifications and then you have to clear data and setup Samsung pay again
[Magisk] :
gear s3

samsung galaxy s8+ rooted renovation rom

magisk 16.3 -or- magisk 16.4 + safetynet pass

deleted busybox in /system/xbin or /system/bin

won't work anymore with updated samsung pay gear plug-in (as of May 2018). I can see samsung has enabled "Rewards" on new samsung pay gear plug-in which is vert interesting *if I can use it*.

used to work with older version of samsung pay gear plug-in (can add credit cards and successfully made payments with my gear s3)

anyone has solution please? : (
[Magisk] arjuna_:
Samsung Pay gear app updated again and once again can't use it. Now the language is "Unauthorized changes were made to your phone."

Oh well all my cards are already loaded in my Gear S3 and if I ever want to use Samsung Rewards I'll just downgrade.
[Magisk] :
Same here, couldn't use Samsung pay gear plugin with any Magisk version after the latest update.
[Magisk] WTF_666:
similarly
[Magisk] coolhandz:
I went ahead and uninstalled 1.6.8906 and reinstalled 1.6.7406 from APK Mirror. I'm using Magisk 16.4 Beta, but it won't hide from the latest SPay version as far as I can tell. For now it is working and I fully expect it to update on its' own at some point so I just keep the APK in my download so I can reinstall it on the go.
[Magisk] Orka82:
Yea. Downgraded to samsung-pay-for-gear-1-6-7406-release from apkmirror. Uninstall old one, install the even older one and add it back to Magisk hide. Skip the pending update. Some update regarding GDPR, who cares? Just press later. Strange stuff. The latest update does not work, the one before works, the one before that does not and before that works. Every other one. ;)
[Magisk] Phreaker47:
I have a Gear S2 watch and up until an update installed today, Magisk Hide on the Samsung Pay gear plugin was always working. Now I get a prompt telling me I need to occasionally verify my identity, and then on the phone I am getting the system modification detection error. Anybody know of a solution to this? I'm on Magisk 16.4 on a Moto G5+. Double checked all gear apps/plugins are added to MH.

Edit... ah, I was just late getting that update. Downgrading to version 7406 worked for me too. Had to re-add the cards though... so i hope i can just keep this version for a while.
[Magisk] Orka82:
It will start to force us to install the GDPR-update later.

Tried some stuff today. The latest version does not work.

It does create a log file on internal storage with this

<Detection>
Date Time Source Policy Summary Current Warning Ver Name Description
2018-06-29 03:02:11 [6042] 52355100 00004000 00004000 00004000 4.4.4 (ROOTED ) MAGISK
2018-06-29 03:02:12 [6043] 52355100 00006000 00002000 4.4.4 (ROOTABLE ) MAGISK
2018-06-29 03:02:12 [6041] 52355100 02006000 02000000 02000000 4.4.4 (RSH ) MAGISK
2018-06-29 03:02:15 [6042] 52355100 00004000 00004000 00004000 4.4.4 (ROOTED ) MAGISK
2018-06-29 03:02:15 [6043] 52355100 00006000 00002000 4.4.4 (ROOTABLE ) MAGISK
2018-06-29 03:02:15 [6041] 52355100 02006000 02000000 02000000 4.4.4 (RSH ) MAGISK
2018-06-29 03:03:27 [6042] 52355100 00004000 00004000 00004000 4.4.4 (ROOTED ) MAGISK
2018-06-29 03:03:27 [6043] 52355100 00006000 00002000 4.4.4 (ROOTABLE ) MAGISK
2018-06-29 03:03:27 [6041] 52355100 02006000 02000000 02000000 4.4.4 (RSH ) MAGISK
</Detection>

Seems to be looking for Magisk. When using the version before I can get it to trig by removing the Samsung pay gear Plugin from the MagiskHide list but nothing about Magisk in the log, just the stuff about detecting su so it seems like they have added something to detect Magisk specifically in later versions.
[Magisk] Didgeridoohan:
[MENTION=1171044]Orka82[/MENTION] Care to post that log file, or is that the entirety of it?
[Magisk] vampyyri1123:
What I found to work for me, granted tedious as it is, was to have a copy of both a stock boot.img file along with a magisk patched_boot.img stored on my ext_sd and when I want to use android pay (or Pokemon go) I just flash back my stock boot.img in TWRP and vice versa if I want root capabilities.

Now if there is an app that can automate that process it could be a temporary work around until the creator works out the kinks.

Hope this works for some people.
[Magisk] Soooperstar:
I haven't taken the latest update but has anyone tried the latest update? Magisk 16.6
[Magisk] wiggmpk:
I just installed Magisk 16.6 from the beta channel. Using the Pixel XL and Gear 3 Frontier with the Samsung Gear App (all Samsung related apps added to Magisk Hide) still get the Access Denied, Unauthorized changes were made blah blah
[Magisk] Orka82:
It detects Magisk specifically. Look at the log-file Samsung Pay creates in root of storage when you get that access denied crap...

With MagiskHide disabled for S Pay, it detects root (SU) AND Magisk. It's all in the logs. ;)
[Magisk] Soooperstar:
This module is said to work for some persistent apps
[Magisk] Orka82:
For me, it works if not using the latest update of the Samsung Pay Gear plugin. The detection was added between version 1.6.7406 and 1.6.8906.

https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-pay-for-gear/
[Magisk] Soooperstar:
Mine works fine for some reason using
[Magisk] MrBrady:
Anyone try the lastest SPay Gear plugin with today's 16.7 Magisk release?
[Magisk] coolhandz:
I'm on 16.6 beta and SPay update still not working. I've downloaded MagiskHide Props module and ran the general hide utility without success. Will try to add a finger print since Pixel XL 8.1.0 OPM4 is not listed as being supported. I've searched that thread without success for a solution but Sooperstar's post gives me hope.
[Magisk] Didgeridoohan:
[MENTION=3890857]coolhandz[/MENTION] I saw your post in the MagiskHide Props Config thread. Answering here as well...

I have a bunch of logs from [MENTION=1171044]Orka82[/MENTION] as well, and when Magisk development goes into a more stable phase I'm gonna see about figuring things out with [MENTION=4470081]topjohnwu[/MENTION].

Meanwhile, this is the thread for you guys to try figuring out what it is that is triggering Pay.
[Magisk] MrBrady:
I see Samsung released an updated Pay Gear Plugin 1.7.3006.

Anyone tried it yet? Does it work with Android 9? Magisk?
[Magisk] TheUndertaker21:
Can't get this to work on pie pixel XL 2

It kept being dectecting it.

Hope someone finds a way .

It worked on 8.1 and my s9+

---------- Post added at 11:53 PM ---------- Previous post was at 11:27 PM ----------

That version won't work on pixel worked on s9+ rooted
[Magisk] MrBrady:
Magisk 17 was just released. Anyone brave enough to try with the latest Samsung Pay?

I've been stuck on SP 1.5 and Samsung is starting to heavily push the upgrade to the point I am unable to have the SP app open for more than a few seconds without a mandatory upgrade notice.
[Magisk] GiSS88:
Can't speak for the full app, but the gear plugin was still no good for me. It still works on the old version for me, but who knows how long that will last. Between this and Pokemon Go I've been tempted to unroot.
[Magisk] dimon222:
Same thing, even with new magisk same story sadly
[Magisk] TheUndertaker21:
Yeah we can hide it anymore magisk probably need to update or catch up
[Magisk] Phreaker47:
Yeah, not working now with my new Galaxy Watch... now the old plugin version that worked up until yesterday on my S2 can't be stopped from auto-updating anymore.
[Magisk] ATP-Flo:
I also preordered the Galaxy Watch.

Is there any way to use mobile payment??

Google Pay? Samsung Pay? (rooted)

HELP
[Magisk] TheUndertaker21:
probably not right now

magisk hide isn't working with it anymore

so maybe some dev can have a look at it
[Magisk] TheUndertaker21:
anyone still trying to detect what is causing the detection?

seems like magisk needs to be updated to watch up to spay
[Magisk] Didgeridoohan:
[MENTION=2438439]rockingondrums[/MENTION] Have you tried the current Canary build? It has an update that randomizes the Magisk service name. It's possible that Samsung was detecting that.
[Magisk] MrBrady:
Does it randomize when selecting to hide Magisk itself?

Hiding Magisk Manager on Canary biods still not fixing the issue.
[Magisk] Didgeridoohan:
Thank you for testing... It's not something to do with MagiskHide per se, it's all done in the background.
[Magisk] rockingondrums:
I thought MagiskHide function already did that? I did already use the Magisk repackage function and it hasn't worked on the versions I've tried it with.
[Magisk] Didgeridoohan:
That's something different. With that function you're randomizing the Magisk Manager's package name. I'm talking about a new function that randomizes Magisk's service name. Two different things.

From a previous report it doesn't seem like it's what Samsung Pay is looking for though...
[Magisk] TheUndertaker21:
it's seeing Magisk itself now.

so hide doesn't work anymore.

i think we might be screwed

wish new york would adapt NFC fast, i would just get another watch and be done with this