Have you tried the solutions I gathered on the thread?@Dante63 While signing the TPKs i got error and unable to sign it. Could you please tell me how can i fix this.
View attachment 5277211
Sorry, I was unclear before, I did both things accordingly, but it's not working.
I was watching your video and follow all steps, now i read XDA thread and found solution to it. First i got error and successfully able to create TPKs. I follow every step and after creating apk, it gives me an error, failed to install app.
Did you grab the signed tpk from install me folder? Because I have a feeling you grabbed the same ones you put inside sign me folder... basically, you tried to install unsigned TPKsI was watching your video and follow all steps, now i read XDA thread and found solution to it. First i got error and successfully able to create TPKs. I follow every step and after creating apk, it gives me an error, failed to install app.
Install the latest Samsung Health if your version is not the same as the one in the Google drive, repeat the steps of enabling the features and turning on the developer mode on and DEV...Sorry, I was unclear before, I did both things accordingly, but it's not working.
I grab tpk from install me and put it is asset folder one by one after decompile and compile again.Did you grab the signed tpk from install me folder? Because I have a feeling you grabbed the same ones you put inside sign me folder... basically, you tried to install unsigned TPKs
The generated certificates have your DUID?I grab tpk from install me and put it is asset folder one by one after decompile and compile again.
Yes you are right.The generated certificates have your DUID?
If yes, I suggest you remake the certificates again because it should work...
Here is the scenario, if you install the apk, you should get notified about installing unknown apps to your watch and you hit allow or deny unless you have in Galaxy wearable allow installing from unknown sources...
If you see phone logo with arrow in notification bar after installing the apk, that means the phone is sending the tpk, if you don't see it, you have an issue with Samsung accessory service, communication issues between phone and watch...
If the installation fails, the apk will also be uninstalled, this could be because you installed original tpk (throws error because it's already installed and probably newer version) or bad tpk (unsigned or bad signature)...
From my understanding, you're at the bad tpk situation, so I want to confirm,
you grabbed unsigned_SBP.tpk
You created the 10 certificate files with your DUID, you copied them to cert folder of fit2installer and you placed the tpk inside sign me, you ran the sign me, entered the correct password and made sure no error was mentioned (if there is 1 error, you will have files inside install me but unsigned) then you copied the tpk from install me and used the tpk installer to push it?
Did I miss anything?
Tried the Samsung Health from your Google Drive. After updating both features were already enabled, still no sync. Do i have to do a full reinstall? I don't want to loose all my health data...Install the latest Samsung Health if your version is not the same as the one in the Google drive, repeat the steps of enabling the features and turning on the developer mode on and DEV...
Sign me showed no errors, and in certificate manager it showed DUID of your watch?Yes you are right.
I connect my watch > Generate new certificates > grab unsigned tpks > put certificates into cert > unsigned into sign me and click sign > grab signed tpk from install me > decompile app > put signed tpk into asset > recompile and sign it for both apk.
After everthing i push apks to my phone and install it, it gives me error.
Sync on Samsung Health will store all health data to the cloud, even if you accidentally cleared the data or needed to uninstall SH, you can restorethe health data all of it, now Force stop and clear the cache of SH, run SHM, hit sync once just to make sure the service is running, now run SH, it should sync BP but honestly I'm not sure if it would sync the old BP from SHM so try recording a new BP and see if that trigger the sync...Tried the Samsung Health from your Google Drive. After updating both features were already enabled, still no sync. Do i have to do a full reinstall? I don't want to loose all my health data...
I recreate certificates and grab fresh copy of Fit2Installer.Sign me showed no errors, and in certificate manager it showed DUID of your watch?
If yes, I suggest you to recreate the certificates and save the old ones somewhere else, if that didn't solve it...
Grab a new copy of Fit2Installer and unsigned tpk and try to sign them...
Keep an eye for any errors...
it is recommended to reboot watch and phone if you still didn't do those...
All I can say, you have a bad tpk or original tpk, these are the only times you get error for failed to install on the watch
No success messages, it can't find the required files to sign the tpk, you can watch on the YouTube video @ 20:15, after I input the password it loads the profiles and applies them and shows success messages...I recreate certificates and grab fresh copy of Fit2Installer.
This is the output.
View attachment 5277371
Yes, I already see. I don't know why it is not getting profile for signing?No success messages, it can't find the required files to sign the tpk, you can watch on the YouTube video @ 20:15, after I input the password it loads the profiles and applies them and shows success messages...
Your tpk was never signed...
Double check the solution for your java "main" problem, you might have used the wrong solution?Yes, I already see. I don't know why it is not getting profile for signing?
I checked it and it is same as it mentioned in OP. It is main problem for some eclipse utils error and as it mentioned in post, replace actual tizen sdk version and ide files with default Fit2Installer have.Double check the solution for your java "main" problem, you might have used the wrong solution?
Replacing files will cause issue of where to read, since it's not finding your profile aka certificates, it's looking for the files in a different place instead of Fit2Installer, have you tried PATH environment approach Or perhaps Googled the java error exception?I checked it and it is same as it mentioned in OP. It is main problem for some eclipse utils error and as it mentioned in post, replace actual tizen sdk version and ide files with default Fit2Installer have.
Did you try copying the files from the Tizen folder to the Tizen folder inside Fit2Installer and then delete the profile.xml in the Fit2Installer folder then try to sign the apk. It should go through.Replacing files will cause issue of where to read, since it's not finding your profile aka certificates, it's looking for the files in a different place instead of Fit2Installer, have you tried PATH environment approach Or perhaps Googled the java error exception?
Where did i find this xml file?Did you try copying the files from the Tizen folder to the Tizen folder inside Fit2Installer and then delete the profile.xml in the Fit2Installer folder then try to sign the apk. It should go through.
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...- Run_me.bat Java "main" errors and JDK15.
Open CMD and type 'Java --version', if it doesn't say Java 15, then you will struggle with such error, uninstall any JDK and reinstall JDK 15, run the command again, you should see Java 15...- Connecting to the watch isn't working.
Firewall, antivirus, defender, anything that filters the internet can block the connection of the watch, so make sure to disable all internet security, if it doesn't connect yet, reboot the pc and the watch and try again...
Please use the Knox Patch Module:
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
This module:
looks for /vendor/build.propif 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 folderremoves 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 the following members for sharing their solutions about the Java "main" exception error solution: @FckSamsung, @little_blaine, @uoY_redruM and @gogega ...
BIG THANKS TO @evildog1 for the APK Easy Tool and @LeJay for the Fit2Installer that I found on his Thread...
Thanks to @caravana for sharing version 175, found at Samsung Health Monitor - 1.1.0.175.mod4.Caravana and on XDA Samsung Health Monitor v1.1.0.167 by @JonGarrett is how I found the link...
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...
Here is what I observed on phone SHM 1.2.4.003:
GUI:
- assets has country code IN - india with both BP and ECG documents, this is a clear indicator of support...
- plenty of permissions removed, this will probably solve the issue of SHM being flagged by TotalVirus (I already checked, this apk is safe)...
- Diagnostic added (might be for Samsung Members aka Samsung devices only)
- backup service updated (this might be backup and restore logic activated)
- Samsung India address added...
- I can see Sleep duration strings, not sure what this is, I will know when I look at the code...
CODE:
- CSCUtil confirms India got ECG and BP but not IHRN...
- I can confirm sleep layout and sleep tracking added but I do not see it being used anywhere nor even called - I can confirm sleep is not active from the manifest, probably future implementation...