Tell me your device type and Android version, provide me a screenshot or video of where it happened and how, a logcat is appreciated, these details will help me re-create the environment and try to get the issue you have so I can trace it and fix it...~~~ Tizen - Active2 & Watch3 - How to install SHM MOD - Tutorial - XDA - Dante63 ~~~
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted devices. This doesnt mean its a universal "fix" and works on every device every time, so ymmv....
Disclaimer: The changes made by this module may have ramifications/consequences beyond what you may be using it for (Samsung Health). I have tested it for several days and havent found any personally, but this doesnt mean they dont exist. You use this at your own risk
This module:
looks for /vendor/build.prop
if found, it copies the ro.security.keystore.keytype line (in case not everyone has the same keytypes in the line - i hate using static files, i write modules to use whats on each device) to a new system.prop file in the modules folder
removes sakv2 from the line in system.prop (it will remove sakv2 from the line (hopefully) wherever it exists, beginning, end or middle)
I had planned to test this new "fix" for a while before releasing the module to stop people from manually editing the existing file, as using magisk is preferable as its easily reversible, but once i saw posts on XDA about it, i figured id release this now
As mentioned above, there may be side effects to this "fix", ymmv
Note: You still need to make sure you have Samsung Health added to Magisk's Deny List, ideally with Shamiko installed (if using Shamiko dont forget to disable Enforce Deny List)
Thanks to @adfree for providing me SHM 1.1.0.181, SHM watch 1.1.0037 and SHM watch 1.1.0039...
Thanks to @vadu71 for providing me the updated version of SHM 183...
Big thanks to member @l0nax for the great catch of finding the device detection and lowering age restriction found in here...
Thanks to @jmdomini as despite BP was hidden and inaccessible, he was able to use the BP by calling the activity through a third-party app which tells me that the restrictions were only view related and not functionality, his findings helped me dig in the right place and fix SHM...
Thanks to @warpjavier for sharing his thread https://xdaforums.com/t/working-bp-tpk-for-non-samsung-phones.4184729/
I have followed his steps and generated unsigned TPKs, you just need to sign it...
After signing it with Tizen studio, you either push it sdb or you can use the TPK installer which you decompile, place the tpk in assets and compile it again...
Thanks for this Guide by @xxstd (download 1 to 3, don't use 4 or 5, use mine and proceed with the rest) for how to sign TPKs
Thanks to Mr. @m2carbine as on the journey of trying to make this work, thanks to him I found the root cause why BP failed to install...
According to Samsung, The Samsung Health Monitor app requires a Galaxy Watch Active2 or Galaxy Watch3 and later models, alongside having Android version 7.0 and above...
SHM has device detection, country restriction and spoof location detection, the following countries were listed in the country restriction checking, I believe if you live in those countries, SHM should Work, otherwise, it wouldn't, SHM checks your GeoLocation, Sim Card, and Device CSC (if no sim or location provided)
List of Country Codes Alpha-2:
SHM will work only if the following is not detected on your Samsung Device:
~~~ Don't forget to ~~~
Don't forget to smash the THANKS
PS. if you are super happy and want to thank me, It is highly appreciated if you'd consider supporting me through myPatreon Pagemonthly or one time throughPayPal ...You can also support me through Google Play by installing: