Samsung Pay Watch plug in

[mio-19]

Device name:

S21 ultra;Watch5

Device model number:

SM-G9880;SM-R910

OS version:

Android13 OneUI5.1

Software info:

G9880ZCU5EWH6

Magisk/KernelSU version:

26.3

Hook framework app:

1.9.1

KnoxPatch version:

0.6.1 Enhancer 0.4

Steps to reproduce:

I enabled the xposed module for recommend apps and watch plug in. My watch was "bootloader unlocked" by accessing the hidden menu for wifi Odin and etc. (OEM Unlock in developer settings is disabled and gray. I found an article in xda claimed that this "bl unlock" does nothing to real bootloader status and knox)

Expected behaviour:

-

Actual behaviour:

It was stuck on the loading screen last week. Today I got an message saying that my device contains unapproved modification and it disappeared before I got a chance to screenshot. I tried it again and got an gray "start" button after the loading circle.

Logs:

magisk_log_2023-09-16T23.47.05.log LSPosed_2023-09-16T23_47_20.014695.zip

[salvogiangri]

A friend of mine (@paulowesll) actually confirmed me the Pay Watch plug-in works fine in his Galaxy M52, he also has a Galaxy Watch 5. Please share some logs so I can take a look at what's going on in your end.

I enabled the xposed module for recommend apps and watch plug in.

You only need to enable the apps marked as "Recommended" in the module settings, the module will ignore all the apps that are selected but aren't marked as "Recommended" as there's nothing to hook there. For Watch apps you only need the Enhancer module. Make sure you also didn't add any Samsung app in the Magisk DenyList.

My watch was "bootloader unlocked" by accessing the hidden menu for wifi Odin and etc. (OEM Unlock in developer settings is disabled and gray. I found an article in xda claimed that this "bl unlock" does nothing to real bootloader status and knox)

Samsung bootloader lock value nowadays is stored in two places: the persistent block and the device's RPMB. The actual value used to check whether or not the device can boot custom binaries is the RPMB one, which you can change by going in the bootloader lock/unlock menu in Download mode. The persistent block value is only used to hide/show the bootloader lock/unlock menu in Download mode, it can be set in the phone's Developer Options and it's greyed out when the bootloader is fully unlocked (OEM Lock: OFF (U))

[mio-19]

I am having the Shamiko module in my phone so Magisk DenyList performs differently. Today I removed all Samsung app in DenyList and rebooted the phone.

The device containing modification message poped out again.

I sent xposed and magisk logs to your email in commit history.

[mio-19]

Samsung bootloader lock value nowadays is stored in two places: the persistent block and the device's RPMB. The actual value used to check whether or not the device can boot custom binaries is the RPMB one, which you can change by going in the bootloader lock/unlock menu in Download mode. The persistent block value is only used to hide/show the bootloader lock/unlock menu in Download mode, it can be set in the phone's Developer Options and it's greyed out when the bootloader is fully unlocked (OEM Lock: OFF (U))

Thanks for the explanation! Does the unlocked bootloader in Galaxy Watch affect knox functionalities? In this case I will sent the Galaxy Watch to Samsung after-sales service for a new motherboard (I flashed my Watch with US Firmware for Google Play. Apparently the after-sales service here doesn't have China Firmware and they will resolve firmware issues such as the firmware being us firmware by replacing the motherboard for free.)

I was adding quotes to "unlocked bootloader" because wifi odin doesn't accepted boot image patched by magisk or any modified ones. The only method to root Galaxy Watch seems to require opening the device phisically. The article I came across on xda claimed that knox status is not affected if no modified partition is installed

[salvogiangri]

I sent xposed and magisk logs to your email in commit history.

Thank you, I've added them in your issue but unfortunately the LSPosed logs zip is damaged and doesn't contains all the verbose system logs I need:

➜  Scaricati 7z x -oout LSPosed_2023-09-16T23_47_20.014695.zip

7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=it_IT.UTF-8,Utf16=on,HugeFiles=on,64 bits,16 CPUs Intel(R) Core(TM) i9-9900KF CPU @ 3.60GHz (906EC),ASM,AES-NI)

Scanning the drive for archives:
1 file, 5722168 bytes (5589 KiB)

Extracting archive: LSPosed_2023-09-16T23_47_20.014695.zip

ERRORS:
Unexpected end of archive

--
Path = LSPosed_2023-09-16T23_47_20.014695.zip
Type = zip
ERRORS:
Unexpected end of archive
Physical Size = 5722168

Archives with Errors: 1

Open Errors: 1

Send a new one when you can.

[salvogiangri]

Thanks for the explanation! Does the unlocked bootloader in Galaxy Watch affect knox functionalities? In this case I will sent the Galaxy Watch to Samsung after-sales service for a new motherboard (I flashed my Watch with US Firmware for Google Play. Apparently the after-sales service here doesn't have China Firmware and they will resolve firmware issues such as the firmware being us firmware by replacing the motherboard for free.)

Sorry, I didn't understood you did also unlock your watch bootloader, infact the BL unlock procedure I explained is the one in Samsung Mobile devices (phones/tablets). Unfortunately I don't have any experience with Samsung Wearables both because I never owned one (Only a Gear S3 with Tizen) and lack of any full firmware dump. Would be great if you could do some tests by locking the bootloader in your watch to see if any change is noticeable, as KnoxPatch & its Enhancer module will only take care of the apps/services running in the phone.

[mio-19]

LSPosed_2023-09-17T13_45_16.309769.zip LSPosed_2023-09-17T13_45_05.247963.zip magisk_log_2023-09-17T13.44.54.log magisk_log_2023-09-17T13.44.51.log

I locked the bootloader of my watch. This time I was able to proceed one step futher

[mio-19]

Last time this message only appeared once. Today I got the message when setting up Samsung Pay on the watch for the second time.

[salvogiangri]

Is this the Samsung Pay app you're trying to set up? https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-pay-watch-plug-in/samsung-pay-watch-plug-in-5-0-36-20006-release/

[mio-19]

Is this the Samsung Pay app you're trying to set up? https://www.apkmirror.com/apk/samsung-electronics-co-ltd/samsung-pay-watch-plug-in/samsung-pay-watch-plug-in-5-0-36-20006-release/

Yes, I installed it from Google Play and the version number is 5.0.36.20006

[mio-19]

Everything worked fine since I disabled the Firefds Kit module and removed non recommended apps from KnosPatch's LSPosed scope