Thanks bro is there any way i can brick this watch?
Bro can i get indian firmware link my friend flashed stock CSC again in his watch 3, i also want to flash it in my watch 4 (wifi)
There is a big chance samsung will reject bricked Watch saying it was abused and they will need proof of how it bricked...
Ok i will visit service centre and will check what they will tell me
You probably were slow to allow / grant access from your PC.
adb disconnect <IP:port> adb connect <IP:port>
adb kill-server adb connect <ip:port>
It's called soft color + on facer but since facer battery drain, I decided to recreate the watchface, you can find it on Playstore, look for geminiman watchfaces case, install the app and find the face from there
If you're talking about the shm mod companion, just set check updates to never...Thank you very much for this adapted app version @Dante63 ! It works very well.
As another user had asked before, I was wondering if it would be possible to allow/enable toggling on/off the background activity of the Wear OS app. I understand that you said it uses around 1% of battery but I think toggling background off could help save battery. I hope it's possible to implement this.
SH BP sync, as in Samsung Health BP sync, thus, Samsung Health app, don't mix between Samsung Health and Samsung Health Monitor, two different apps...Hello, trying to go through the instructions and have tried searching the thread, but have gotten stuck on enabling "set features" within the Samsung Health Monitor app. I've been tapping on the version # for a while now (I included a screenshot and circled where I'm tapping), but nothing pops up. I've tried installing the companion app and had it successfully Enable SetFeatures. I've also tried force stopping app, clearing cache, and restarting phone, but I can never get "set features" to show up. Not sure what I'm doing wrong?
I'm using a Pixel 6 Pro running 13.
First I want to say to article authors, thank you for your efforts to publish an article on this, but please do not copy and paste into your article as content may change and please provide link to the thread so people can get help and ask questions...
Ok, now let's begin:
- Tizen SHM MOD and WearOS SHM MOD...?
The watch4 original SHM can't communicate with the phone MOD, and it's not possible to completly remove the original SHM from the watch4, so I had to create WearOS MOD and rename the previous MOD to Tizen MOD...
- Do I need root...?
No root is required...
- Does this void my warranty?
No it does not void the warrenty or trip the know or damage the watch or the phone...
- OTA effect on MOD & MOD effects on OTA.
No Effects, the MOD is independant...
- Do I need to install both phone and watch MODs?
Yes, you need both, keep in mind, the apk with word phone is for phone and the watch4 is for the watch...
- Where is the IP Address?
You can find it inside the developer options after you enable the ADB Wi-Fi, it takes time though, alternativly, you can go to connections -> wifi -> the wifi you are connected to -> scroll down and you'll find your IP...
- Can I do this from my phone?
Yes, you can use Bugjeager if you don't like to type commands or Remote ADB Shell if you want to type the commands...
- How do I update?
Just install it again and it will update, whether you install the phone app or the watch app...
- Do I need Samsung Health MOD, is there even such thing...?
There is no Samsung Health MOD, Samsung Health is a core application, modding it will break many services, using official Samsung Health works fine...
Now here is an update of mine if the above does not work and Galaxy Wearables keeps disconnecting from the watch4
Initially it was Huawei devices but this solution works for other devices as well...
This fix is done by Reddit u/Relative_Comparison2 & u/MelodicMaintenance
You need Galaxy Wearables & Watch4 Plugin installed, now do the following steps:
- Download Samsung Health.
- start Samsung health then go to accessories and search for your watch (scan).
- Samsung Health will call Galaxy Wearables to set up the connection and a normal setup is performed.
It was Explained that you need to have the following apps installed:
Galaxy Wearable & Watch 4 plug-in
Give all permissions to Galaxy Wearables and the Watch4 plugin by going app info, scroll down, permission and grant all...
Now Clear the data of the following applications:
The phone will start acting up, that's normal, so restart your phone to allow system app to rebuild itself, when the phone starts, do not configure your google account yet, first try connecting to the Watch4 again through Samsung Health and it should work, after that you can do whatever you want for google...
- Google Play Services
- Google Play Framework
- Google Play Store
- HwWifiproBqeService (For Huawei devices only, skip if you are not Huawei)
One last note, disable any battery optimization, some phones have aggressive optimization, they will kill background services, this will stop the watch4 from pairing, if you can't disable it, then whitelist galaxy wearble and the watch4 plugin!
Samsung Health Security PropsRemoves "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
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
- 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)
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)
pm disable-user --user 0 com.samsung.android.shealthmonitorand exiting the shell and disconnecting... instructions updated...