Develop Bugs

Galaxy Watch and Lineage OS

Hi,
I have Samsung S9 phone (Exynos version) with official Lineage OS 17 installed. Also I have Magisk (package renamed, Magisk Hide is active) as root control app.
Recently I've bought Galaxy Watch (not 2 or 3), installed Wearable, changed system props to be able to run it (as described here: https://forum.xda-developers.com/ga...earable-app-rooted-phone-help-t3838503/page10) and everything works OK, except inability to pay with watch.
When I run Samsung Pay from Wearable app, it tells about unauthorized modifications and exit.
I've found this interesting log, named com.samsung.android.samsungpay.gear.log in the root of internal storage.
In this log (which is XML) I see a section "detections", and there I see next stuff:
<Detection>
Date Time Source Policy Summary Current Warning Ver Name Description
2020-08-15 09:14:31 [7107] 52355100 00004000 00004000 00004000 5.3.0 (ROOTED ) com.topjohnwu.magisk
2020-08-15 09:19:06 [7107] 52355100 00004000 00004000 00004000 5.3.0 (ROOTED ) com.topjohnwu.magisk
</Detection>
I've double-checked, in Magisk I hide it from this Samsung app.
So, my question is - why it still able to detect magisk? And what I can do to be able to pay with watch?

Thank you for pointing this file out. Exactly what I was looking for.
Mine, too, says Magisk is found.
I still can't get the Samsung Wear App to work, but good to get confirmation what it is detecting, Magisk in this case.
I was getting this error on LineageOS even before Magisk. I specifically installed Magisk to see if that hide feature would help.
Now at least I can go back to plain LineageOS without Magisk and see what it says.
Thanks.

DulacLancelot said:
Thank you for pointing this file out. Exactly what I was looking for.
Mine, too, says Magisk is found.
I still can't get the Samsung Wear App to work, but good to get confirmation what it is detecting, Magisk in this case.
I was getting this error on LineageOS even before Magisk. I specifically installed Magisk to see if that hide feature would help.
Now at least I can go back to plain LineageOS without Magisk and see what it says.
Thanks.
Click to expand...
Click to collapse
Eh. I uninstalled Magisk. And the LineageOS root functionality is disabled. Wear Samsung Pay still detects root, and flags it multiples times as "MAGISK-11" or "MAGISK-2" or "framework".

Samsung Pay will never work on rooted devices. It's related to knox services.

w41ru5 said:
Samsung Pay will never work on rooted devices. It's related to knox services.
Click to expand...
Click to collapse
Wrong. I've had Samsung pay working on my watch with rooted pixel 3a xl

And i have it on my rooted Pixel 2 XL....
Install Magisk
Enable MagiskHide
MagiskHide all Samsung apps
Rename Magisk Manager
Do this before opening Samsung Pay

[SM-T970/Others??] Passing SafetyNet 😈

I'm about to become your favorite person ever, everyone! ​​I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.​
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1

Thanks for sharing!

Thanks so much for this post. I'm a recent proud owner of a Tab S7 T870, after almost 5 years using the Tab S2 T813 (R.I.P.).
Even being a bit rusty rooting, had no problems unlocking bootloader and rooting with Magisk. The only thing really bugging me was the Safetynet message popping in RED
After following your post and handy links I'm in heaven with the message now popping in BLUE. How magical, I can even install Netflix now... crazy!

Here is something latest you to know. Today safetynet failed kn my rooted Tab S7. I searched and found solution.
I have flashed kdragon safetynet fix version 2.0.0 test2.
Removed edxposed breaks safetynet now
Install lsposed doesnt break safetynet
Installed magisk hide prop module but no changes done in it
Magisk hide is on
Thats how i fixed it today on Tab S7 T875 running android 11 latest firmware. Because previiously without kdragon safety net and with only magisk hide everything but not from today onwards

Question Rooting or not ?

Hey Guys I'm thinking if I should root my op9pro or not ? What type of magisk modules you use after rooting that can help me get something which I can't without root ?

Here's some XDA Rooting food for thought:
Best apps for rooted Android devices in 2023
Here are some of the best root apps for you to try on your rooted Android device to unlock new features or just increase your productivity!
www.xda-developers.com

AdAway alone is worth it IMO. Using it over a VPN sucks.

why do you open another thread to ask a similar question?
Best Magisk Modules for OOS 12
I have recently rooted my phone. Can anyone please recommend some good modules as i am new to rooting. So far i am able to tweak google dialer to enable call screening and call recording. Call hold and direct my call do not activate. Any other...
forum.xda-developers.com
What Magisk modules are you using?
Hey all moving up from my OP 7 pro to the OP 9 pro. What are all the magisk modules everyone is using on the OP 9 pro.? 1.Anything to force full screen mode on all apps? The settings for full screen apps dont include all the apps im using as...
forum.xda-developers.com

[q] Gpay on lineage 19.1

Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!

Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.

deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?

HW898 said:
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
Click to expand...
Click to collapse
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case

deathblade said:
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
Click to expand...
Click to collapse
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!

HW898 said:
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
Click to expand...
Click to collapse
I just remembered, the unofficial is setup to pass safteynet out the box, but more maybe needed for Gpay to work. Once you flash it try it out, if you run into issues I can provide what I did to get Gpay working

deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?

HW898 said:
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
Click to expand...
Click to collapse
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working

deathblade said:
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
Click to expand...
Click to collapse
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread

HW898 said:
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
Click to expand...
Click to collapse
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue

deathblade said:
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
Click to expand...
Click to collapse
I see... I will try installing the official one without magisk as I won't want to meddle with rooting stuff for now, will get back with results asap!

deathblade said:
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Click to expand...
Click to collapse
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?

HW898 said:
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
Click to expand...
Click to collapse
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them

deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
Aite thanks for the help mate! just installed but apparently, i couldn't find gapps despite sideloading it.. might have to reinstall again

Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse

HW898 said:
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
Click to expand...
Click to collapse
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you

deathblade said:
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
Click to expand...
Click to collapse
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho

HW898 said:
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
Click to expand...
Click to collapse
You install the pixelify module? Also can you explain how it's not working?

deathblade said:
You install the pixelify module? Also can you explain how it's not working?
Click to expand...
Click to collapse
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs

HW898 said:
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
Click to expand...
Click to collapse
This is the pixelify module I installed then removed, you can give it a try.
GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
Magisk module to enables pixel exclusive features and ui - GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
github.com

Themes / Apps / Mods Samsung Health on Rooted Android 12

Samsung Health on Rooted Android 12​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its pretty clear that Samsung has disabled its Samsung Health services in Tripped Knox Devices and Rooted devices. Till Android Version 11 there's a solution to overcome this via changing the ro.config.tima line in Build.prop file. but after Android 12 Update, there is no ro.config.tima line in Latest Build.prop files. Even if we try to copy the ro.config.tima line, the device gets into boot loop sequence. The only way to run Samsung Health app in Tripped and rooted devices is to install a Patched Samsung Health App. Modifying the integrity of the app will allow us to run the app in tripped devices. The patched app can also be synced to Samsung Account in order to retrieve and save your Data on the Cloud.​
PASSWORD = hibiscus
Refer this article to read in brief​

Download now

rc chanu said:
Download now
Click to expand...
Click to collapse
This sounds promising as I've been keeping my app on 6.19.5.017 to avoid tripping the security on the new versions, but what's the password for the zip file?

Mr_Death1996 said:
This sounds promising as I've been keeping my app on 6.19.5.017 to avoid tripping the security on the new versions, but what's the password for the zip file?
Click to expand...
Click to collapse
sheesh! forgot to mention passkey. its updated above. pls check

HIBISCUS said:
sheesh! forgot to mention passkey. its updated above. pls check
Click to expand...
Click to collapse
The app seems to work well and sync to the servers, but it doesn't connect directly to my watch anymore. The "Show on phone" button just errors out too?

Why not use a magisk module instead of patched Samsung Health app
that makes latest Samsung Health app work 100 percent and get regular updates as well ?
I use this magisk module on my A13 Rooted Note20 Ultra N986B and Samsung Health latest version works perfect and i am also getting latest updates of it as well.
PS . I also have Watch4classic and Watch5 pro connected to my phone.
link
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com

kingwicked said:
Why not use a magisk module instead of patched Samsung Health app
that makes latest Samsung Health app work 100 percent and get regular updates as well ?
I use this magisk module on my A13 Rooted Note20 Ultra N986B and Samsung Health latest version works perfect and i am also getting latest updates of it as well.
PS . I also have Watch4classic and Watch5 pro connected to my phone.
link
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
Click to expand...
Click to collapse
That's brilliant, I hadn't seen it before. My Watch 5 seems to be working again perfectly on the latest health app once that module is installed.

kingwicked said:
Why not use a magisk module instead of patched Samsung Health app
Click to expand...
Click to collapse
Because you have people like me, who have tripped/removed knox so s-health errors out (it technically works in the background but you can't use the app).
Their DRM/lock-in often works in bizarre and schizophrenic ways: s-health-monitor, for BP/ECG worked immediately just by installing the vanilla apk, go figure...

b0rked said:
Because you have people like me, who have tripped/removed knox so s-health errors out (it technically works in the background but you can't use the app).
Their DRM/lock-in often works in bizarre and schizophrenic ways: s-health-monitor, for BP/ECG worked immediately just by installing the vanilla apk, go figure...
Click to expand...
Click to collapse
I have rooted N20, bootloader unlocked and Knox is tripped. SAMSUNG health latest and Samsung health monitor both working perfect after installing this magisk module. see the screenshots of the latest version health and accesories connected and everything synced .
I gave you a 100 percent working method that allows Latest Samsung Health to sync and work perfectly. Where as patched version method doesnt allow Samsung Health app to be updated from Google Playstore.
So Go figure yourself. Perhaps it was better not to share a solution with people like you who instead of being happy. Make sarcastic remarks.

kingwicked said:
I gave you a 100 percent working method that allows Latest Samsung Health to sync and work perfectly. Where as patched version method doesnt allow Samsung Health app to be updated from Google Playstore.
So Go figure yourself. Perhaps it was better not to share a solution with people like you who instead of being happy. Make sarcastic remarks.
Click to expand...
Click to collapse
Where's the sarcasm?
I've already tried the magisk module: IT DID NOT WORK FOR ME, this did.
I've prob removed something you haven't.

b0rked said:
Where's the sarcasm?
I've already tried the magisk module: IT DID NOT WORK FOR ME, this did.
I've prob removed something you haven't.
Click to expand...
Click to collapse
OK. Perhaps you may have Samsung Health ticked in Denylist. Since this is a magisk module it will NOT work in that case.
See my screenshot , I have not ticked Samsung Health in denylist. And i have used hide the magisk app option in magisk app.b. Here is the xda link of the developer of this magisk module
Post in thread '[Guide] How to use latest S-Health on devices with Knox tripped (0x1)'
[Guide] How to use latest S-Health on devices with Knox tripped (0x1)
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped. This guide will show you how to get the latest version of S-Health to run without this block Rooted Devices This method requires...
forum.xda-developers.com

It wasn't on denylist: I'm missing some bloody knox related crap, hence the module WILL NOT WORK on my damn phone.
I'm probably going to return this damn watch... My old fitbits and amazfits battery lasted 3 times longer and i didn't have to get around retarded software to get basic stuff to work

b0rked said:
It wasn't on denylist: I'm missing some bloody knox related crap, hence the module WILL NOT WORK on my damn phone.
I'm probably going to return this damn watch... My old fitbits and amazfits battery lasted 3 times longer and i didn't have to get around retarded software to get basic stuff to work
Click to expand...
Click to collapse
same even im now using noise watch instead of sam watch

kingwicked said:
OK. Perhaps you may have Samsung Health ticked in Denylist. Since this is a magisk module it will NOT work in that case.
See my screenshot , I have not ticked Samsung Health in denylist. And i have used hide the magisk app option in magisk app.b. Here is the xda link of the developer of this magisk module
Post in thread '[Guide] How to use latest S-Health on devices with Knox tripped (0x1)'
[Guide] How to use latest S-Health on devices with Knox tripped (0x1)
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped. This guide will show you how to get the latest version of S-Health to run without this block Rooted Devices This method requires...
forum.xda-developers.com
Click to expand...
Click to collapse
Do you mind posting the magic module. The module developer left XDA in anger and didn't say where the new repo for his module is.

yerrag said:
Do you mind posting the magic module. The module developer left XDA in anger and didn't say where the new repo for his module is.
Click to expand...
Click to collapse
send me a pm. i can share with you but i will not post here in forum because the developer left xda and doesnot want to post it here.

You can just use this:
GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted Galaxy device.
LSPosed module to get Samsung apps/features working again in your rooted Galaxy device. - GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted G...
github.com
It's better than removing sakv2 from vendor/build.prop in vendor because doing this will break Samsung's Find My Mobile functionality (and possibly other security related features).
Also patches a few Knox features like Secure Folder.

OK, so I've found nuked repository, but I was able to check prior commits, which gave me enough to do the modification myself. I do not use Find my phone from samsung, so I am good. sHealth works. I removed it only from /vendor/build.prop file, not elsewhere
Running Android 13 on Galaxy S20+ and Galaxy S22, both rooted with Magisk 25, stock kernel. S Health has to be in DenyList as well

ShaDisNX255 said:
You can just use this:
GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted Galaxy device.
LSPosed module to get Samsung apps/features working again in your rooted Galaxy device. - GitHub - BlackMesa123/KnoxPatch: LSPosed module to get Samsung apps/features working again in your rooted G...
github.com
It's better than removing sakv2 from vendor/build.prop in vendor because doing this will break Samsung's Find My Mobile functionality (and possibly other security related features).
Also patches a few Knox features like Secure Folder.
Click to expand...
Click to collapse
As for Secure Folder, Samsung's Find My phone....those KNOX related apps are useless without KNOX either way. But Samsung Health can work with KNOX tripped, as KNOX is used only as a failsafe. Samsung Health doesn't use KNOX for anything else. Given that the phone is already rooted and KNOX tripped, I am not interested in either Secure Folder or any other KNOX related app. Hell, I nearly wiped original set of apps already (uninstalled from user's context anyway), replacing all apps like dialer, contacts, clock, calculator, messages...nearly everything - by apps from Google. So, removing this keyword from one file, when it impacts only KNOX dependent stuff (I do not use anyway), was no hard decision at all. For which I would like to thank to kingwicked for giving enough hints to find my own way through ;-)
​

[deleted]

Many thanks for this.