Hi,
If you have a Galaxy Watch without Samsung Pay enabled, is it enough to change the CSC with SDB (in my case to Australia) to enable it, or do you need to flash an Australian firmware as well?
Also, can you manage Samsung Pay on the watch with a non-Samsung android phone, like Huawei P20 (e.g configure payment cards)?
Thanks
Biermann said:
Hi,
If you have a Galaxy Watch without Samsung Pay enabled, is it enough to change the CSC with SDB (in my case to Australia) to enable it, or do you need to flash an Australian firmware as well?
Also, can you manage Samsung Pay on the watch with a non-Samsung android phone, like Huawei P20 (e.g configure payment cards)?
Thanks
Click to expand...
Click to collapse
I don't know the answer to the first question but I'm using SPay in the S3F and OnePlus 6T with out any issue. It's the only way to get MST payment without buying a SS phone.
Sent from my ONEPLUS A6013 using Tapatalk
Biermann said:
Hi,
If you have a Galaxy Watch without Samsung Pay enabled, is it enough to change the CSC with SDB (in my case to Australia) to enable it, or do you need to flash an Australian firmware as well?
Also, can you manage Samsung Pay on the watch with a non-Samsung android phone, like Huawei P20 (e.g configure payment cards)?
Thanks
Click to expand...
Click to collapse
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
I tried to follow your procedure but I`m getting always a "failed to connect" message between PC and watch
peter7 said:
I tried to follow your procedure but I`m getting always a "failed to connect" message between PC and watch
Click to expand...
Click to collapse
The fix is to go into C:\Users\{USER}\.tizen and ether delete that folder or delete the items in it. This changes your key to a new one which make the watch prompt you to accept the new key.
Make sure hidden files are shown in windows Explorer, if this thing doesn't work, then instal the tizen studio, and that will bring the .tizen folder in tha above-mentioned location, and then you can delete that folder
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Hi thanks - on my PC is no tizen folder ?
Tizen studio ? I uderstand I have to install it on my PC ? Which version - any link?
Ok - now I`m a step further...I`m connected
launch_app csc-manager.csc-pre-configuration - when I say enter I will get "either wrong written or could not befound"
How can I know which region my watch is set on? I'm from Mexico and I can not use samsung pay, the model of my watch is SM-R800. Regards
ca_guri01 said:
I have a Samsung galaxy watch 42mm and Nokia 7 Plus, i live in India, since i got the watch there is no option of Samsung pay in Galaxy wear app. I manually installed latest Samsung pay plugin ( https://www.apkmirror.com/apk/samsu...n/samsung-pay-watch-plug-in-1-7-5906-release/ ) , and changed the region to Australia and after that when i paired the watch again with galaxy wear app Samsung pay is showing in it, and i then followed the instructions in the app to set it up.
I followed the below instructions samsung pay works on my nokia 7 plus.
You do NOT need root.
But this is how you do it.
1. So first, download SDBstarterKidv1 from the following link please:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
WARNING: This will reset your watch, so make sure you back it up so you can restore it later.
2. Next make sure your watch is set up as follows:
- Debugging Mode turned ON
- Connect watch to WiFi and get its IP address (To find the IP address on Galaxy Watch: Settings > Connections > Wifi > Wifi Networks > [your network] > Scroll down to IP address)
3. Next, from SDBstarterKidv1 double click on 'install.bat' (it will not install, it just flashes a window, but this step is required)
4. From the subfolder data\tools double click on 'sdb.exe' (it will not install, it just flashes a window, but this step is required too)
After noting IP address of the Galaxy Watch, Launch ‘Ansicon.exe’ from sdb_2.2.60_windows-64\data\tools (this thing will open a command prompt window, and all the action is done here)
5. Type: sdb connect [IP of Galaxy Watch]
6. Look at Galaxy Watch, it will prompt you to accept a message
7. If you try the sdb connect [IP address] again, it will say "already connected". This means we are connected and good to continue.
8. Type: sdb shell and Enter
9. Copy Paste: launch_app csc-manager.csc-pre-configuration and Enter
So this lets you change the region of the watch. Now for me I changed mine to Austrailia. The code for Austrailia is XSA
Once the watch is reset, pair it back up with your phone.
10. Once pared with your phone you will need to:
- Turn on developer mode again
- Turn on debugging mode
- Turn off the watch and turn it back on again.
- You may need to wait a few minutes.
11. Once you have done this, you can open the Samsung Galaxy Wearable app and go to settings. When you scroll down you should see samsung pay.
If you dont see pay, hold down the back button (Top right button) on the watch till samsung pay opens up and follow the instuctions to set it up. But initially the Samsung pay app is not recognising my compatible Indian Debit and Credit card and not allowing me to add, i thought this might be that i had changed the region to Australia, but i tried again after an hour and then to my surprise i am able to add all my 4 cards to Samsung pay app , and it is working also, i tried a payment at NFC enabled terminal and payment works flawlessly
Enjoy your new watch with Samsung Pay enabled.
Click to expand...
Click to collapse
BUT how about my carrier T Mobile ...will he still work ...because now my phone is saying we are no longer in Germany no now we are in for example Switzerland
AIKON1989 said:
How can I know which region my watch is set on? I'm from Mexico and I can not use samsung pay, the model of my watch is SM-R800. Regards
Click to expand...
Click to collapse
When you do the step 9, it will show the installed csc on your watch, and then you can scroll up or down and select your desired region csc
Sent from my [device_name] using XDA-Developers Legacy app
Great now I switched from Germany to Swiss BUT they do not accept german cards .....................
Any other country which will accept german cards ????
Thanks for your help i am almost Finished but I'm getting the answer despite my card is confirmed by the bank from Samsung pay App confirm your card
Hello . Curve cards now support Samsung pay. Do you think that is a way to get working Samsung pay in not supported country? On galaxy watch LTE?
tomaspavelka18 said:
Hello . Curve cards now support Samsung pay. Do you think that is a way to get working Samsung pay in not supported country? On galaxy watch LTE?
Click to expand...
Click to collapse
Mine is also LTE and it seems we are out of luck. I use Samsung Pay on my phone but it seems I will not be able to change the CSC region cause it is a US LTE model.
If any wiz here know a way, let us know!
So curve will not work?
---------- Post added at 08:35 AM ---------- Previous post was at 08:22 AM ----------
You can definitely change the region on your watch but if the watch will accept curve ?
I think that Curve is win for people which there bank doesn't not support Samsung pay. So they get curve card (where they add there cards) and curve card add to Samsung pay.
Another case is that someone is in country what does not support Samsung pay. So there is a way that you change the CSC region and add curve card. That should work also.
Worst case is if you have LTE model of your watch, there is ( I think) no way to change CSC region and work with cellular data normally.
I hope that I am wrong about the last one and someone correct me and show me way how to get SP working in not supported country and still use my tariff from local operator.
I'm in Germany and changed via csc the region of my watch. My phone Tarif is German. I think you are right.
I tried to combine several cards with sp but without success. So I assume that curve will work either.
Well today I was curious and I change csc on my galaxy watch LTE with working esim (tmobile). From TZM (Czech tmobile) to AUT( Switzerland)
Before I did backup of watch. After change of CSC -> Samsung Pay shows up. I expected that. What I did not expect was that after restoring my backup the esim setup will work like before and it is.
I tried add some cards to Samsung pay but no succes. My bank doesn't support that.
Now I'm waiting for my curve card. It should work with SP.
tomaspavelka18 said:
Well today I was curious and I change csc on my galaxy watch LTE with working esim (tmobile). From TZM (Czech tmobile) to AUT( Switzerland)
Before I did backup of watch. After change of CSC -> Samsung Pay shows up. I expected that. What I did not expect was that after restoring my backup the esim setup will work like before and it is.
I tried add some cards to Samsung pay but no succes. My bank doesn't support that.
Now I'm waiting for my curve card. It should work with SP.
Click to expand...
Click to collapse
I have an LTE version from US but the ZTO code fro Brazil does not show. Was that a similar case as yours? If so, how was the process? I know my bank accept Samsung Pay here, since I use it on my phone already.Let me know.
Cheers,
After step 9 watch showed me lots of CSC, AUT included. I followed instructions from page 1.
Hi fellas
I got it finally to work, after updating to Android Pie
Time to share how I did it and be aware, I did not test this again in different ways, so there are some uncertainties, I will incorporate them into the places where they belong, so I recommend to first read this guide before doing it, so you are aware of what it requires, what the "risks" are and what restrictions I found so far.
Risks:
No guarantee it works for your devices. I already know from my own testing, it does not work on Android 8.X.
No guarantee this won't damage your phone or something, but that said, I am using this since over 1 year now, no adverse effect or anything
Untested if updating of the watch or Tab S4 breaks this - but in my case, I was on the newest version of Android, Tizen, and the needed apps already. That said, sofar updating the watch is not breaking this, after 1 year and several updates.
This is faking the phone's identity to a Galaxy Note 9, this leads to some side effects, ie. in my case the navigations button are stuck on the bottom, pin keypad is only usable horizontally, etc. BUT this is only for the procedure, you can revert after pairing, etc. and it worked ever since for me, even updating the watch software was no problem whatsoever - updating the watch software (the apps on it) you need to do temporary this trick again
Specs of my devices:
Samsung Galaxy Tab S4 LTE (SM-T835)
Android 9.0 - ROOT IS REQUIRED and this will void the warranty of your Galaxy Tab S4, as it is breaking Knox and this is not undoable (afaik)!
Here the exact Android version I use - which is meant for my provider (Swisscom), so please use your appropriate provider version! Only posting if someone is wondering (installed via Odin)
Here the guide which I used to root it (I have also some suggestions that should make it more clear)
Samsung Galaxy Watch LTE 46 mm (SM-R805F)
Tizen 4.0.0.1 (R805FXXU1DSB2/R805FOXA1DSB2/R805FXXU1DSB2 - according to Galaxy Wearable)
IIRC with this new guide you can activate the eSIM normally, in case it does not work:
Activate the eSIM with a known compatible device [but it must have the physical sim card your eSIM is connected to, insert before pairing up ofc.], ie. Galaxy S9, Galaxy S20, Galaxy Note 9 and then connect it with the guide below
Things you need to get this working:
Root (see above)
[Probably] Magisk Module so that Bluetooth connection is not forgotten: "libsecure_storage companion for rooted Samsung devices" (by ianmacd)
Build Prop Editor app (I used this one), hence the root
Galaxy Wearable app (tested on version 2.2.24.19031361) - If you download it at the beginning you can find it on the Play Store, otherwise you can find it on apkmirror as well
A file explorer with root capabilities
How to install:
At this point I strongly recommend installing ianmacds "libsecure_storage companion for rooted Samsung devices" in the Magisk Manager app! Otherwise, the tablet will forget the Bluetooth connections! Do not restart as we need to do this in a few moments anyways
Install the Galaxy Wearable app from the Play Store
Open your Build Prop Editor
Change the following stuff to fake your Tab S4 identity (mine is SM-T835, yours might be different) to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model than the Note 9, as well, I haven't tested it though)
ro.build.characteristics=tablet to ro.build.characteristics=phone
ro.config.tima=1 to ro.config.tima=0 (this is to get Samsung Health app to work, I know this app is refusing to work on rooted phones, maybe other Samsung apps are also affected?)
Save the changes (in the app I suggested there is a save symbol top right) and restart the tablet (to apply)
Yes some of the UI is a bit weird, do not worry, we will revert to the correct identity at the end and everything should be back to normal
Launch the Galaxy Wearable app
Close the app again
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
!!! This might have to be redone if the Galaxy Wearable app is updated !!!
Start the Galaxy Wearable app again
Press "Connect to new phone" on your Galaxy Watch (or if it is brand new, then you should be also in the screen it asks to pair up with a new device) - beware: This "resets" your Galaxy Watch (except eSim info), so I suggest to back it up beforehand if you can
In the main menu of the Galaxy Wearable app, you should now see the Galaxy Watch, then click on it
Now it should pair up without any problems and set up properly (at least for me it did work all 4 times )
As said, if the mobile network setup fails, you need to setup the eSim beforehand with a known compatible device, as written somewhere above
You can restore a backup from here if you chose to, though you still have to setup some of the stuff again - I tried it without and it still worked without problems
If you have an eSim, check your watch if you have a mobile data connection (go to settings > mobile network > put it on ALWAYS ON just for that test)
Afterwards if you want to use it as a standalone outside your Bluetooth tablet range, I suggest AUTO or ALWAYS ON (beware ALWAYS ON eats a lot of battery, your watch might hold only 12h+ hours) and set in the Galaxy Wearable under "Account and backup", "Remote Connection" to on (which requires the tablet to have a data connection of its own)
Now I suggest to install & update all the necessary apps, see the guide below!
How to update watch apps or install watch apps:
Open your Build Prop Editor [you can skip these first 3 points if you are coming from first install part from above]
Change the following stuff to fake your Tab S4 (mine is SM-T835, yours might be different) identity to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app, I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model than the Note 9, as well, I haven't tested it though)
ro.build.characteristics=tablet to ro.build.characteristics=phone (this is essential, otherwise, we would need to change some XML file as well)
Save and restart the device
[Resume here if you are coming from the install part above] Open Galaxy Wearable
Open Galaxy Store
Open the 3 lines on the top left, go to Updates and then use the Watch tab
After you have done all the watch app updates & installs
Open your Build Prop Editor
ro.product.model=SM-T835 [SM-T835 is my tablet, yours might be different]
ro.build.characteristics=phone
Save and restart and all should be working as before
Enjoy your fully functional Galaxy Watch with your Galaxy Tab S4!
In case you are FORCED to do an update to the Galaxy Wearable app (it is not recommended to auto-update):
Update like any other app
If everything still works, you don't have to do the following points:
If suddenly it says your device is not compatible or something:
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Save
Start the Galaxy Wearable app again and it should work again
Tested features that work:
Restarting the tablet (on my very first try this triggered some kind of in-app update, but it just repaired and it still works as usual), never had that again later (I repaired/reset the watch several times for testing)
Backup & Restore incl.
Connecting to a Samsung Account (never tested without though, but I see no reason it shouldn't work)
Remote connection (both LTE and Wifi) incl.
Notifications (specifically tested with Gmail and SMS) (both remote and over Bluetooth) and
Calling something (both remote and over Bluetooth)
Automatic Bluetooth reconnect
Widget/App installation & uninstallation (tested with Spotify remote control)
Adding a music track to the watch via Galaxy Wearable and play it
Samsung Health (partially tested, specifically heart rate works)
Calling from the watch, receiving calls to the watch, as standalone or in Tablet range (all 4 are working) (I recommend a Bluetooth headset)
Things that don't work:
Updating / Installing Galaxy Watch apps without doing the guide above
[Sometimes] rules.xml needs to be rechecked after a Galaxy Wearable app [see guide above]
Have fuuuuuuuuuuuun
neuer31 said:
Hi fellas
I got it finally to work, after updating to Android Pie
Time to share how I did it and be aware, I did not test this again in different ways, so there are some uncertainties, I will incorporate them into the places where they belong, so I recommend to first read this guide before doing it, so you are aware of what it requires, what the "risks" are and what restrictions I found so far.
Risks:
No guarantee it works for your devices. I already know from my own testing, it does not work on Android 8.X.
I haven't tested it longterm, so no idea if it will still work in 1 month or if your phone / watch breaks down or Samsung blocks it.
Untested if updating of the watch or Tab S4 breaks this - but in my case I was on newest version of Android, Tizen and the needed apps already.
This is faking the phone's identity to a Galaxy Note 9, this leads to some sideeffects, ie. in my case the navigations button are stuck on the bottom, pin keypad is only usable horizontally, etc.
Specs of my devices:
Samsung Galaxy Tab S4 LTE (SM-T835)
Android 9.0 - ROOT IS REQUIRED and this will void the warranty of your Galaxy Tab S4, as it is breaking Knox and this is not undoable (afaik)!
Here the exact Android version I use - which is meant for my provider (Swisscom), so please use your appropriate provider version! Only posting if someone is wondering (installed via Odin)
Here the guide which I used to root it (I have also some suggestions that should make it more clear)
Samsung Galaxy Watch LTE 46 mm (SM-R805F)
Tizen 4.0.0.1 (R805FXXU1DSB2/R805FOXA1DSB2/R805FXXU1DSB2 - according to Galaxy Wearable)
eSim preactivated on a "compatible" phone (iirc. Galaxy S9) - even doing "Connect to new phone", the watch keeps your eSim info - I could not setup mobile network with this one, but with this "trick" it still works
I tested both, setting it up new and using a backup both work in my case
Things you need to get this working:
Root (see above)
Build Prop Editor app (I used this one), hence the root
Galaxy Wearable app (tested on version 2.2.24.19031361) - If you download it at the beginning you can find it on the Play Store, otherwise you can find it on apkmirror aswell
How to install:
Install the Galaxy Wearable app from the Play Store (or do it later but then you need the .apk)
Open your Build Prop Editor
Change the following stuff to fake your Tab S4 identity to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model, than the Note 9, aswell, I haven't tested it though)
ro.build.characteristics=phone to ro.build.characteristics=phone (this is essential, otherwise we would need to change some xml file aswell)
ro.config.tima=1 to ro.config.tima=0 (this is to get Samsung Health app to work, I know this app is refusing to work on rooted phones, maybe other Samsung apps are also affected?)
Save the changes (in the app I suggested there is a save symbol top right) and restart the tablet (to apply)
Press "Connect to new phone" on your Galaxy Watch (or if it is brand new, then you should be also in the screen it asks to pair up with a new device) - beware: This "resets" your Galaxy Watch (except eSim), so I suggest to back it up beforehand if you can
If you haven't already: Install the Galaxy Wearable app, but now you need to do with the .apk, you won't find it on the Play Store anymore (I wonder why)
Launch the Galaxy Wearable app
In the main menu of the Galaxy Wearable app, you should now see the Galaxy Watch, then click on it
Now it should pair up without any problems and setup properly (at least for me it did work all 4 times )
As said, the mobile network setup will fail, but it will still work if you setup the eSim beforehand, as written somewhere above
You can restore a backup from here if you chose to, though you still have to setup some of the stuff again - I tried it without and it still worked without problems
If you have an eSim, check your watch if you have connection (go to settings > mobile network > put it on ALWAYS ON just for that test
Afterwards if you want to use it as a standalone outside your Bluetooth tablet range, I suggest AUTO or ALWAYS ON (though ALWAYS ON eats a lot of battery) and set in the Galaxy Wearable under "Account and backup", "Remote Connection" to on
Tested features that work:
Restarting the tablet (on my very first try this triggered some kind of in app update, but it just repaired and it still works as usual), never had that again later (I repaired/resetted the watch several times for testing)
Backup & Restore incl.
Connecting to a Samsung Account (never tested without though, but I see no reason it shouldn't work)
Remote connection (both LTE and Wifi) incl.
Notifications (specifically tested with Gmail and SMS) (both remote and over bluetooth) and
Calling something (both remote and over bluetooth)
Automatic bluetooth reconnect
Widget/App installation & uninstallation (tested with Spotify remote control)
Adding a music track to the watch via Galaxy Wearable and play it
Samsung Health (partially tested, specifically heart rate works)
Untested:
Someone calling me, possibly do tomorrow (once with bluetooth, once without)
Splitscreen on the Tab S4
Things that don't work:
Samsung Dex disappeared for me from the widget bar on the Tab S4 (see in P.s. for a possible fix)
[Possibly] Setting up a new eSim in the Galaxy Wearable app (untested because I didn't want to risk it - if it doesn't work, use workaround by setting it up on another device, then unpair and the eSim profile will be kept)
P.s. !!!
I put back the old model in the prop editor, SM-T835 and it is still working (after a restart of the Tab S4), so maybe it is not needed?
In a further attempt I also edited rules.xml under data/data/com.samsung.android.app.watchmanager/files (you need root for that or someone who is capable to modify the app so that rules.xml is by default with the following changes) and changed all supportTablet="false" to supportTablet="true" between <group name="Gear S4"> and the next </group> and still seems to be working! Maybe, just maybe, a modified .apk could do this without any root necessary, though I had it rooted and tried by only modifying these rules.xml and it didn't work for me. Idk, I am too inexperienced in such things and have no idea of .apk coding.
As for now I keep running with these last changes and set Galaxy Wearable to never update in Play Store. These last changes also fix the Dex and other visual issues, so thats that.
Click to expand...
Click to collapse
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
jazol said:
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
Click to expand...
Click to collapse
That is exactly the problem I had with Android 8, it got stuck at pairing.
Sorry I am not into rooting, I just have enough knowledge to root my own device.
Shouldn't it be compatible on stock?
neuer31 said:
That is exactly the problem I had with Android 8, it got stuck at pairing.
Sorry I am not into rooting, I just have enough knowledge to root my own device.
Shouldn't it be compatible on stock?
Click to expand...
Click to collapse
Yes, it is compatible with stock but the last official Samsung update for S7 is Oreo. If I want to use Pie I need to install a custom rom and that is when the connectivity problems arise. Anyway, thanks for your time...
Wysłane z mojego SM-G930F przy użyciu Tapatalka
jazol said:
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
Click to expand...
Click to collapse
When it is stuck in pairing, try going to Bluetooth setting and manually click on connect button for watch, and come back again on app, may be this will help you, because it helps me when i was stuck on pairing mode
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
When it is stuck in pairing, try going to Bluetooth setting and manually click on connect button for watch, and come back again on app, may be this will help you, because it helps me when i was stuck on pairing mode
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks ca_guri01. I'll try it tomorrow.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
jazol said:
Thanks ca_guri01. I'll try it tomorrow.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
Click to expand...
Click to collapse
If you find any solution pls tell me [emoji53]
Sent from my SM-N935F using Tapatalk
fearbit said:
If you find any solution pls tell me [emoji53]
Sent from my SM-N935F using Tapatalk
Click to expand...
Click to collapse
Ok but no luck so far...
jazol said:
Ok but no luck so far...
Click to expand...
Click to collapse
Still looking?? Which rom have you installed?
Στάλθηκε από το SM-N935F μου χρησιμοποιώντας Tapatalk
fearbit said:
Still looking?? Which rom have you installed?
Στάλθηκε από το SM-N935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I gave it up for the time being. Got back to [TeamExyKings][G930/G935_F/FD][8.0][S9 Port][06-May-2019][v22]LightROM...
So 8 month after I made this guide, this is still working
No issues whatsoever, did multiple watch updates and updates of the app and with a trick even running Samsung Health app
I hope all of you that did this have a similiar good experience
You Sir are a Life Saver!
I had Tab S4 was using as my phone. As it was hard to carry it around I bought the watch. But did not work with S4 but you saved the day!
Thank you.
After editing rules.xml Samsung wear resets and no devices are shown.
Please help
neuer31 said:
So 8 month after I made this guide, this is still working
No issues whatsoever, did multiple watch updates and updates of the app and with a trick even running Samsung Health app
I hope all of you that did this have a similiar good experience
Click to expand...
Click to collapse
Hi, I have a galaxy Tab A (2017 model) and recently bought a Galaxy Watch D346. My tablet shows the watch in bluetooth available devices but can't connect and the samsung wearable app also cant find the watch. Can you please help me with this?
1. I updated the guide with 1 more strongly recommended install, a Magisk module by ianmacd, allowing the rooted Tab S4 to remember Bluetooth connections. It is called: "libsecure_storage companion for rooted Samsung devices"
2. The newest versions of the Samsung Galaxy Wearable app might require an additional modification, which I also implemented in the original post. You have to do it only if it suddenly says that your device is not compatible anymore.
Close the Galaxy Wearable app
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Save
Start the Galaxy Wearable app again and it should be working again
Ashish3640 said:
After editing rules.xml Samsung wear resets and no devices are shown.
Please help
Click to expand...
Click to collapse
Are you using icanmads Magisk Module "libsecure_storage companion for rooted Samsung devices"?
Did you follow the guide?
I assume you did edited rules.xml doing this:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Zen_K said:
Hi, I have a galaxy Tab A (2017 model) and recently bought a Galaxy Watch D346. My tablet shows the watch in bluetooth available devices but can't connect and the samsung wearable app also cant find the watch. Can you please help me with this?
Click to expand...
Click to collapse
Did you root your device?
If yes, are you using icanmads Magisk Module "libsecure_storage companion for rooted Samsung devices"?
Did you follow the guide?
Hi neuer31, thanks for sharing, I am trying to get galaxy watch3 to connect with Tab S4, I have follow all the steps, in rules.xml in Gear S4 and Watch 3, I change all false to true. Watch 3 show up on wearable, goes through pin numbers authentication and start pairing a minute then shows
Can't open Galaxy wearable
Your version of Android isn't compatible . Check for software update for your phone and try again.
What should I try next ? Thanks
More info,
SM-T835
Android version 10
Baseband version T835XXU4CTI4
Galaxy Wearable 2.2.34.20091461 , I try to load older version but was force to upgraded to this version, I checked rules.xml to be all "true" for Gear s4 and Watch 3
I don't know how to root or tinker a device, scared to screw. Can you help modify the files for Galaxy Tab S2 8.0 please? Or would you be able to share your apks here, so I can try it out on my device??
Hi neuer31, I downgraded to android 9, and got the watch 3 connect to tab s4, I been playing with it for a wk now, so far so good, thanks a lot
I have a Galaxy Watch SM-R800 and the Galaxy Wearables app installed on my S10+ but couldn't pair my watch with my phone. Both my phone and watch were bought in India, but I use them here in Italy cause I live here.
I used this watch for many days with no problem at all and then one day I upgraded my phone to One UI 2 (beta) and I encountered this bug with security module, which locked me out from entering the phone even though I was entering the correct Pin or passcode.
After that I rolled back my phone to Android 9 (stable) version.
So my assumption is that the procedure that I followed to upgrade my phone to One UI 2 might have caused this issue with my watch.
Firstly I created a Samsung account with my email which by default is Italian cause of location, but I had to sign up for the beta program using an India account. No beta testing in Italy.
As suggested on XDA forums by someone I had to delete my Italian Samsung account and create Indian account with same email if I want to enroll for the beta program, which I did.
So I didn't use the watch for few days and later when I tried to pair it with my phone it says, "Couldn't Pair your watch" (Try Again/ Cancel)
I'm using the same email Id for Signing In to finish the setup of pairing with which I initially setup both the Phone and watch. It sometimes says I am using a different account from the one I used earlier to setup. I'm definitely sure that I never used any other account of mine or a friend. (No others)
I need your help if someone has a solution for this situation.
Thanks,
Akhil Bellam.
akhilbellam said:
I have a Galaxy Watch SM-R800 and the Galaxy Wearables app installed on my S10+ but couldn't pair my watch with my phone. Both my phone and watch were bought in India, but I use them here in Italy cause I live here.
I used this watch for many days with no problem at all and then one day I upgraded my phone to One UI 2 (beta) and I encountered this bug with security module, which locked me out from entering the phone even though I was entering the correct Pin or passcode.
After that I rolled back my phone to Android 9 (stable) version.
So my assumption is that the procedure that I followed to upgrade my phone to One UI 2 might have caused this issue with my watch.
Firstly I created a Samsung account with my email which by default is Italian cause of location, but I had to sign up for the beta program using an India account. No beta testing in Italy.
As suggested on XDA forums by someone I had to delete my Italian Samsung account and create Indian account with same email if I want to enroll for the beta program, which I did.
So I didn't use the watch for few days and later when I tried to pair it with my phone it says, "Couldn't Pair your watch" (Try Again/ Cancel)
I'm using the same email Id for Signing In to finish the setup of pairing with which I initially setup both the Phone and watch. It sometimes says I am using a different account from the one I used earlier to setup. I'm definitely sure that I never used any other account of mine or a friend. (No others)
I need your help if someone has a solution for this situation.
Thanks,
Akhil Bellam.
Click to expand...
Click to collapse
Hello. did you tried to reinitialise the watch?
The watch is locked (reactivation lock (not other security lock)) by original samsung account used when it was locked. You MUST NOT DELETE this account UNTIL the watch was UNLOCKED. If you delete the original account you will (never) not able to unlock the watch. (or use hack (paid) method))
I can help u have to use netodin and install combination file and then u have to remove reactivation lock and then install official firmware. Indeed a long and complicated process. Msg me on whatsapp 923107671256
Iron_UV said:
Hello. did you tried to reinitialise the watch?
Click to expand...
Click to collapse
It doesn't work if you try anything else other than flashing it.
By the way I fixed my watch finally.
I had to use the firmware and other combination files, but I couldn't find them anywhere on the web.
And then finally I found this video on Youtube showing how to remove that re-activation lock on Gear S3. youtube . com/watch?v=Afx3RWWFSfg&t=1s
and I contacted the guy on Facebook.
He redirected me to his website, where I paid him a little money $15 and he provided me with the necessary files to do the task.
https: // electrovo.com/
akhilbellam said:
It doesn't work if you try anything else other than flashing it.
By the way I fixed my watch finally.
I had to use the firmware and other combination files, but I couldn't find them anywhere on the web.
And then finally I found this video on Youtube showing how to remove that re-activation lock on Gear S3. youtube . com/watch?v=Afx3RWWFSfg&t=1s
and I contacted the guy on Facebook.
He redirected me to his website, where I paid him a little money $15 and he provided me with the necessary files to do the task.
https: // electrovo.com/
Click to expand...
Click to collapse
hi bro i have same watch R800 wich is samsung account lock. can you plz share your file with me ?
For Those who are facing problem on the galaxy watch SM-R800 i finally found the solution to by pass the Samsung Account it's a little long method but working fine
Hi!
I was wondering if anyone managed to setup Samsung Pay on their galaxy watch active 2 while their phone is rooted.
I can't setup SPay on my watch since it requires setting it up on my galaxy s10+ phone which is rooted.
Maybe any bypass or any other suggestion?
Thank you!
Neeham said:
Hi!
I was wondering if anyone managed to setup Samsung Pay on their galaxy watch active 2 while their phone is rooted.
I can't setup SPay on my watch since it requires setting it up on my galaxy s10+ phone which is rooted.
Maybe any bypass or any other suggestion?
Thank you!
Click to expand...
Click to collapse
Unfortunately, Knox kills the ability to setup Samsung pay on the watch. Pity because I was considering the Galaxy Note 20 or Galaxy Note S10+ as my next phone due to processor specs.
Once Knox is tripped, one cannot go back (though there is anecdotal discussion on some Samsung devices that people have had Knox reset to 0x0 after being tripped).
Sorry I could not be of more help.
Cheers,
B.D.
Hi guys !
I want to change the region to my active 1 to USA ? Is there Any chances To Change the region In watch active 1. And there is lots of stuff on watch active 2 not for watch active 1.
My Watch Model No. is
SM-R500
Tizen Version - 5.5.0.1
One UI watch Version- 2.0
Software Version- R500XXU1FUD1
Any Links as well as process required too please do Help in this . I seriously want to use Samsung Pay in watch active 1. And anybody have youtube link for watch active 1 change region please do share it.
Thanks
Works fine on my rooted Pixel 2 XL
I decided after my Note 4 finally died to exit the Samsung family and get on with life, they were making it just too hard to do anything if your are a tinkerer....
Neeham said:
Hi!
I was wondering if anyone managed to setup Samsung Pay on their galaxy watch active 2 while their phone is rooted.
I can't setup SPay on my watch since it requires setting it up on my galaxy s10+ phone which is rooted.
Maybe any bypass or any other suggestion?
Thank you!
Click to expand...
Click to collapse
I was able to get it to work on mine. Uninstall the Samsung pay plugin on your phone then reinstall it and use the magisk hide option in magisk to hide it from the 2 plugins I have in my screenshot. Close the magisk manager app and then try it. You have to be fast at signing in and adding a card. If it pops up with the error saying that your device is modified just close the Samsung pay app and open it again and keep going. If it keeps going you might have to block more of the plugins for the Samsung plugin in the magisk manager hide option.
Once you get it running, to keep it working across ROM's, if youre in the habit of flashing different ROM's, and want to keep your Samsung Pay working across flashes, along with the connection to the watch (without having to reset it), heres how i do it:
Keeping Watch Connection And Samsung Pay Across ROMs
This is currently how i keep my Galaxy Active 2 working - connected and Samsung Pay working - across ROM flashes without having to reset it every time, because resetting sucks Please note: At time of writing theres no known way to keep BP...
forum.xda-developers.com
The basic part is to set the same Android ID as when you first got it working....