Hi,
After setting up my new Gear Sport I was very disappointed to find that the Samsung Pay app was missing. From what I can tell it should be pre-installed and ready to go. I believe this is because I have purchased a Korean model and activated it in the UK - the first thing it did was update the software, so I think it has taken an international firmware version which doesn't include the Pay app, because the Pay app is region specific? Is there a way to update the software to the correct UK version?
Device info:
Gear Sport SM-R600NZKAKOO (Korean model number)
Tizen 3.0.0.1
Software version R600XXU1AQJS
[edit]
After a quick look at the S3 forums I see some people had similar issues and some were able to flash the ROM with the country version they needed:
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-classic-sm-r770-t3526747
I guess I'll have to wait until the UK ROM for the Sport is available to download somewhere...
Gear Sport SM-R600NZKAKOO (Korean model number)
Click to expand...
Click to collapse
Where do you have this info?
From the Box?
Or is in SM-R600 possible to check this in About device info or via Code?
I have no SM-R600 to check self.
Maybe we have now all incredients... to do something similar on SM-R600...
Like few users did with SM-R760 or SM-R770...
Best Regards
adfree said:
Where do you have this info?
From the Box?
Click to expand...
Click to collapse
Yes it is on the side of the box. In the device information the model is listed simply as SM-R600. I believe the additional letters after specify the colour and the region.
I hoped they made it easier to check if Product Code on Box match written Software data in Gear...
Still for normal end user not visible without using Tools...
SM-R600NZKAKOO
UK Sales Code/CSC is IMHO:
Code:
BTU
Last 3 letter... of Product Code.
On Gear S3 Forum...
Few users changed successfully to Sales Code USA:
Code:
XAR
And Gear S3 started to work with Samsung Pay... in:
India
For instance...
------------------------------------------------------------------------------------------
Code for identify of written/active CSC... Sales Code seems different in Tizen 3
Code:
vconftool get -t string db/csc/salescode
This Command worked on Tizen 2.3... but now Permission...
Strange... now CSA folder readable...
So maybe someone with SM-R600 could check if this work with SDB.
Code:
cat /csa/csc/csc-active-customer.inf
and/or just for fun
Code:
cat /csa/imei/prodcode.dat
-------------------------
These Codes only to find out, what is set/written on device
Best Regards
adfree said:
I hoped they made it easier to check if Product Code on Box match written Software data in Gear...
Still for normal end user not visible without using Tools...
SM-R600NZKAKOO
UK Sales Code/CSC is IMHO:
Code:
BTU
Last 3 letter... of Product Code.
On Gear S3 Forum...
Few users changed successfully to Sales Code USA:
Code:
XAR
And Gear S3 started to work with Samsung Pay... in:
India
For instance...
------------------------------------------------------------------------------------------
Code for identify of written/active CSC... Sales Code seems different in Tizen 3
Code:
vconftool get -t string db/csc/salescode
This Command worked on Tizen 2.3... but now Permission...
Strange... now CSA folder readable...
So maybe someone with SM-R600 could check if this work with SDB.
Code:
cat /csa/csc/csc-active-customer.inf
and/or just for fun
Code:
cat /csa/imei/prodcode.dat
-------------------------
These Codes only to find out, what is set/written on device
Best Regards
Click to expand...
Click to collapse
sh-3.2$ cat /csa/csc/csc-active-customer.inf
SEK
sh-3.2$ cat /csa/imei/prodcode.dat
SM-R600NZBASEK
sh-3.2$
anybody managed to solve the issue? having the same problem with the same Korean watch
We have meanwhile 2 Combination Firmware...
https://forum.xda-developers.com/gear-sport/help/sm-r600-firmware-odin-repair-study-t3688495/page3
Code:
COMBINATION-FT30_R600XXU1[B]AQI6[/B].tar.md5
AQI6 seems no luck to change CSC...
Code:
COMBINATION-FT30_R600XXU1AQL1.tar.md5
I got no feedback... no idea if same result...
Code:
COMBINATION-FT30_R600XXU1AQI4.tar.md5
Also no idea, but this is not yet for free available... only on paid sites..
Best Regards
Only as info. Working solution now also for SM-R600 possible:
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
And few posts later... with SDBTool:
Code:
launch_app csc-manager.csc-pre-configuration
SDB + infos how to connect are here:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Best Regards
Many thanks!! I ran the code and managed to change my configuration to UK region (BTU) and reset the device which installed Samsung Pay!
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
A few details as I am very much a novice - others may find useful (edited to add more info):
SDB = Software Development Bridge - it comes with the Tizen development studio. It's an executable that lives in the tizen tools folder and you run using a cmd shell (if on windows)
First I had to install Java SE development kit 8 (8u162 for windows - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)
Then I had to add a new windows environment variable called JAVA_HOME which points to the Java install directory (C:\Program Files\Java\jdk1.8.0_162) and reboot before Tizen studio would install
I installed Tizen studio - https://developer.tizen.org/
Now I could run the sdb executable on windows command line from the Tizen install folder
To get the Gear sport to connect to sdb I had to enable debug mode on the gear, disconnect it from my phone, connect to the wifi and run the connect command
Here's all the code I ran in the cmd shell:
Code:
cd "C:\tizen-studio\tools"
sdb connect <[I]gear ip address[/I]>
sdb shell
launch_app csc-manager.csc-pre-configuration
Then the region selection popped up on the Gear screen.
Thanks again! :good:
No ZIP for canada
davesing33 said:
Many thanks!! I ran the code and managed to change my configuration to UK region (BTU) and reset the device which installed Samsung Pay!
https://forum.xda-developers.com/showpost.php?p=76007649&postcount=41
A few details as I am very much a novice - others may find useful (edited to add more info):
SDB = Software Development Bridge - it comes with the Tizen development studio. It's an executable that lives in the tizen tools folder and you run using a cmd shell (if on windows)
First I had to install Java SE development kit 8 (8u162 for windows - http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html)
Then I had to add a new windows environment variable called JAVA_HOME which points to the Java install directory (C:\Program Files\Java\jdk1.8.0_162) and reboot before Tizen studio would install
I installed Tizen studio - https://developer.tizen.org/
Now I could run the sdb executable on windows command line from the Tizen install folder
To get the Gear sport to connect to sdb I had to enable debug mode on the gear, disconnect it from my phone, connect to the wifi and run the connect command
Here's all the code I ran in the cmd shell:
Code:
cd "C:\tizen-studio\tools"
sdb connect <[I]gear ip address[/I]>
sdb shell
launch_app csc-manager.csc-pre-configuration
Then the region selection popped up on the Gear screen.
Thanks again! :good:
Click to expand...
Click to collapse
Thank you very much, that worked like charm ! However, there is just one problem now. When I try to add my VISA card, it wants me to enter the ZIP code (5 digit US code) and I apparently live in canada and have an alphanumeric code. Is there a workaround ?
Rammy_sd said:
Thank you very much, that worked like charm ! However, there is just one problem now. When I try to add my VISA card, it wants me to enter the ZIP code (5 digit US code) and I apparently live in canada and have an alphanumeric code. Is there a workaround ?
Click to expand...
Click to collapse
Yes, there is... Only use the numbers of your postal code and add 2 zeros at the end. For example V6T 1Z4 would be 61400.
Happy to see this is working for others!
Cheers
i get a failed to connect to remote target message. ... any ideas?
any ideas?
Click to expand...
Click to collapse
If you mean SDB...
Then maybe check this:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
If not help...
Then maybe helpfull if you post screenshot... or Copy & Paste of text output...
I mean you see an Error message?
Can you Copy & Paste it...
Best Regards
Related
Hello all,
Please find attached the recovery and the ramdisk from the firmware.
I have no language knowledge ( C+, Java ) and hence cant help with getting a root.
Could someone please look at the files and help us achieve a root.
Thanks.
Ramdisk : http://www21.zippyshare.com/v/YI1WNBKI/file.html
Recovery: http://www21.zippyshare.com/v/VffwNEbb/file.html
Anyone here with rooting skills ?
tids2k said:
Anyone here with rooting skills ?
Click to expand...
Click to collapse
not too sure why sdb sdk command "sdb root on" exist if it's always permission denied haha, but i might have something little tricky to get root acces, still on it tought
Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.
Jhfreeze said:
Root would be awesome. Maybe @cipherswitch can give us some pointers as his Gear S root thread is well put together.
Click to expand...
Click to collapse
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.
tids2k said:
We need to do a insert exploit with a method like Magisk as rooting will trigger will Knox fuse and then Samsung pay will become unusable. Also there is actually an app that checks whether the device has been rooted or not in the watch itself. My suggestion would be to pack a binary with su.apk and then making an Odin flashable package, but then I'm not sure if it will proceed as the signature validation will fail.
Click to expand...
Click to collapse
Im fairly sure it will beacuse its not digitally signed by Sammy.
cipherswitch said:
I actually just picked up an S3 Frontier last week. I haven't really looked into it and and I'm not 100% sure what rooting will do to Samsung Pay but it's worth taking a look at.
Click to expand...
Click to collapse
i got access via sdb sheel to few sbin command like "pivot_root" and "switch_root" if this could help..
and i was able to use initrd scripts
Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards
adfree said:
Stupid question.
No idea if allready Gear S3 is rooted...
I was able to successfully root Tizen handsets with same method and same 1 file:
SM-Z130H
SM-Z300H
SM-Z300F
SM-Z200F
Procedure...
Copy file su into bin folder...
Easiest way... modify rootfs.img... then flash result with Odin.
Ehm... not tested with any Gear... but...
Maybe check this special Factory Firmware... aka Combination.
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
Extract rootfs.img ...
You will see su in bin folder:
/bin/su
In theory you could try now to use this su file... and inject in other rootfs.img... then flash.
Own risk!
Only as info.
I am to lazy to buy Gear S3 to check my theory...
Best Regards
Click to expand...
Click to collapse
Too bad root checker will spot that su binary and blow warranty void fuse than farewell spay
Too bad root checker will spot that su binary and...
Click to expand...
Click to collapse
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards
adfree said:
Root Checker on Z-Mobiles only disable access to FOTA Server...
Not really deep investigation... but an app could check Root... maybe not Bootlaoder...
Something like this...
com.samsung.rootdetection-syspopup ...
Maybe to remove the "App" which checks if su is present or not...
No idea how much Security inside Gear S3... but maybe if you compare difference between Combination "FTMA" Firmware... and normal...
Otherwise you would also loose warranty blabla with this file?
https://forum.xda-developers.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3550225
No idea yet. Only theory...
Best Regards
Click to expand...
Click to collapse
With official firmwares you can't loose warranty. As you mentioned this was an internal build with most of the apps scrapped.
I treid to mount the storage but getting write protection error. Trying to compile TWRP and test but unable to do so. @cipherswitch @DevALT. Some screenshots
I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R760
For Kernel related study... Source Code is available...
I was only to lazy to download...
But in theory also here in repos...
1 RPM is inside with su...
Will check after Download... "soon"...
Best Regards
Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards
adfree said:
I could create rootfs.img with su inside...
su file I would take from combination file...
Code:
COMBINATION-FTMA_R760XXU1APK3.tar.md5
rootfs.img I have at the moment only from this Firmware:
Code:
R760XXU1APK7_R760OXA1APK7.zip
And I have NO Gear Watch to test self.
So I "need" tester with balls and SM-R760 who is able to flash with Odin...
OWN risk!
I could do it and upload...
But to prevent waste my time...
I will try to "explain" first...
Before I was able to root my SM-Z130H...
I have used rooted GT-I9300 to create my modified rootfs.img...
Extracting files from rootfs.img under Windows was easy with Windows Tools...
But creation of valid rootfs.img is better to do with Linux...
Need few minutes to upload extracted su file... and to post few Commands for SDB... or ADB ...
Best Regards
Edit 1.
su added...
Taken from Combination Firmware...
MD5
Code:
B784CC4DBBC86EFCC308D239D1235CE0
Now this file "must" inject into folder bin in rootfs.img
Edit 2.
Here is example how I would do it with my rooted Tizen SM-Z130H... with Batch file... few Commands for SDB:
Code:
sdb root on
sdb push su /opt/usr/media/Others
sdb shell mount -t ext4 -o loop,rw /opt/usr/media/Others/rootfs.img /opt/usr/media/Others/2
sdb shell cp /opt/usr/media/Others/su /opt/usr/media/Others/2/bin
sdb shell cd /opt/usr/media/Others/2
sdb shell sync
pause
sdb shell cd /
sdb shell umount /opt/usr/media/Others/2
rootfs.img I would copy manually to folder Others...
For rooted Android device... replace sdb with adb... and few path changes...
Click to expand...
Click to collapse
gonna try that but i'll compile myself, not that I don't trust you but if it breaks my gear s3 i want to be the one who brick it
and also for weird reason sdb root on dosen't want to work on windows (will try on Linux tomorrow, work till very late :'( )
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
adfree said:
Downloaded...
SM-R765_Opensource.zip
Extracted:
SM-R765_repos.tar.gz
Unpack:
coreutils-6.9.rpm
Bingo... su Binary is inside.
But still problem...
I don't know how to install RPM without ROOT access.
I can only install RPM if allready device is rooted...
So I only know this way to inject su into rootfs.img and create then valid TAR file to use with Odin...
Simple Copy and Paste solution.
Best Regards
Click to expand...
Click to collapse
as i said upthere sdb root on command won't work on my windows and your solution seems to be the one will try everything tomorrow on my Linux pc will give an update right after
Code:
sdb root on
This is only possible, if you have allready su in bin folder:
Code:
/bin/su
For better understanding you could install Tizen Studio for instance...
https://developer.tizen.org/development/tizen-studio/download
It is possible to use SDB with Emulator...
Also Wearable Image available...
So you don't need to buy Tizen Mobile or other real device to test...
Simple study Image in Emulator...
You can delete su from Image and then play again with command:
Code:
sdb root on
simple curiosity did you use RPM based distro to create your rootfs.img, if not witch distro are you using?
Click to expand...
Click to collapse
I am Windows Fan Boy...
So first time... before my SM-Z130H was rooted. I've created rootfs.img with GT-I9300 (Android handset)...
Since my SM-Z130H is rooted... I am using this device.
I've never tried to create rootfs.img with Computer... with handset it was easier for me.
Maybe I find my old post with GT-I9300... to check my ADB Commands... because path could be different...
Best Regards
Edit 1.
2 years ago... I found "inspiration" by Gear Watch Thread...
https://forum.xda-developers.com/showpost.php?p=59457357&postcount=95
Then I did something like this:
https://forum.xda-developers.com/showpost.php?p=59478150&postcount=97
Important is for Odin... TAR file...
I can remember not all Windows TAR Packer were valid...
So I am using since over 2 years only IZArc Tool.
Also important... use only rootfs.img from Firmware which is on your device...
Not mix Firmware parts from different versions... to prevent funny sideeffects.
Best Regards
sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l
DevALT said:
sorry for late update i couldn't test anything today no free time for me until wednesday but sure will I test everything there :l
Click to expand...
Click to collapse
No panic.
For few things I have spend many months... years.
And I understand Gear S3 is at the moment very expensive "test" device...
I can wait. :angel:
Maybe someone have halfdead Gear S3... with brroken display or Water Damage or something similar...
Best Regards
670 MB for download... for study...
Code:
AP_R600XXU1AQI8_usr.tar
BL_R600XXU1AQI8_usr.tar
CSC_OXA_R600OXA1AQI8_usr.tar
Download Link for OXA region... contains all CSC for SM-R600:
https://www.file-upload.net/download-12796748/R600XXU1AQI8_OXA.zip.html
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Still missing, maybe somebody can share the LDU XXX Version.
Thanx in advance.
Code:
COMBINATION-FT30_R600XXU1AQI4.tar
COMBINATION-FT30_R600XXU1AQI6.tar
LDU Live Demo Unit XXX
Code:
AP_R600[B][COLOR="Red"]X[/COLOR][/B]XXU1AQI6_usr.tar
BL_R600[COLOR="Red"][B]X[/B][/COLOR]XXU1AQI6_usr.tar
CSC_OXA_R600[B][COLOR="Red"]X[/COLOR][/B]OXA1AQI6_usr.tar
Best Regrds
What is tizen version
What is tizen version
Click to expand...
Click to collapse
In theory something with Tizen 3...
At the moment I am not 100 % sure if:
Code:
3.0.0.0
Maybe more something like this:
Code:
3.0.0.1
Best Regards
SM-R600 Bootloader...
R600XXU1AQI8
Code:
sboot.bin
cm.bin
Please ask before you try something "amazing"... and your Gear is dead...
OWN RISK!
For study... and maybe repair...
Best Regards
Meanhwile I have SM-R600 Firmware for study.. Thanx. :angel:
Next problem.
Old methods not work to unpack...
7zip nor ext4 unpacker work...
So they used something "new"...
Code:
nad_fw.bin
nad_refer.bin
In BL package... this 2 for me unknown files inside...
Maybe with some Google search I can find some usefull info...
Short XDA search...
https://forum.xda-developers.com/sitesearch.php?q=nad_fw.bin
https://forum.xda-developers.com/sitesearch.php?q=nad_refer.bin
Maybe this can lead to compatible Unpacker/Extractor...
Best Regards
For extraction I will try this... as other attempts failed...
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-extract-img-to-dump-t3673863
Will report if success...
Best Regards
Edit 1.
Attempt 1 fail...
SVAImgUnpack.exe ramdisk.img
Code:
SVAImgUnpack - Unpacker img to ext4. Version 2.1 from 30.04.2013
----------------------------------------------------------------
Source file: ramdisk.img (file size = 7.340.304 bytes)
Destination file: ramdisk.ext4.img
Unpacking ...
Header error: source file has wrong format! Program terminated.
Unpacking successfully done!
Press any key ...
Edit 2.
I can mount *.img files in Tizen Studio...
Emulator with Tizen 3 Mobile... as I need SD card feature... otherwise not enough space to mount and tar 1200 MB
Then simple "copy & paste"... with SDB
First I have waste my time with Wearable Image T3... and spent hours to realize that SD card option is not possible here...
No success with any "converter" Tools at the moment...
New idea is to mount in Tizen 3 Emulator... need some time for Copy & Paste...
Later more...
Meanwhile if sombody want take an look:
https://www.file-upload.net/download-12781791/CSC_OXA_R600OXA1AQI8_usr.tar.md5.zip.html
Only CSC + PIT inside...
I am toooo lazy to upload now... and it seems nobody else want R600 Firmware.
Best Regards
Code:
R600XXU1AQJ5
Seems updated to this Version...
Somebody knows the Changelog...
I am not able to find something similar like this...
http://doc.samsungmobile.com/SM-R760/CHC/doc.html
Not for XAR nor for DBT or other Sales Code...
Maybe depend on big or small letters... like here
http://doc.samsungmobile.com/sm-g930f/dbt/doc.html
Or Samsung work like this...
Ehne mehne mu und Du kriegst halt nix...
Best Regards
Oh, magic.
After 5 years of Development from Tizen 3.0 we reach:
Tizen 3.0.0.1
http://doc.samsungmobile.com/SM-R600/CHC/doc.html
Code:
R600XXU1AQJ5
Best Regards
P.S:
I have added Link in first post for Odin package...
Only as hint...
I downloaded COMBINATION-FT30_R600XXU1AQI6.tar.rar from some kind of free site, so 100% is not sure if this is really it. I will be grateful if anyone will check - https://www.dropbox.com/s/z6nvlob4f3ixoft/COMBINATION-FT30_R600XXU1AQI6.tar.rar?dl=0
Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-R600
SM-R600 Source for study available. :good:
Best Regards
I have extracted Combination Firmware in this way...
Still with help of Tizen Studio... Tizen 3 Mobile Emulator...
"Beta" Batch...
Code:
sdb root on
sdb push t3.tar /opt/media/SDCardC
sdb shell cd /opt/media/SDCardC
sdb shell tar -xvf t3.tar
sdb shell mkdir csc
sdb shell mkdir user
sdb shell mkdir ramdisk
sdb shell mkdir ramdisk-recovery
sdb shell mkdir system-data
sdb shell mkdir rootfs
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/csc
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/user
sdb shell mount -t ext4 -o loop,rw ramdisk.img /opt/media/SDCardC/ramdisk
sdb shell mount -t ext4 -o loop,rw ramdisk-recovery.img /opt/media/SDCardC/ramdisk-recovery
sdb shell mount -t ext4 -o loop,rw system-data.img /opt/media/SDCardC/system-data
sdb shell mount -t ext4 -o loop,rw user.img /opt/media/SDCardC/rootfs
tar -cvf r600v1.tar rootfs
tar -cvf r600v2.tar csc
tar -cvf r600v3.tar user
tar -cvf r600v4.tar ramdisk
tar -cvf r600v5.tar ramdisk-recovery
tar -cvf r600v6.tar system-data
rm t3.tar
sdb pull *.tar
Maybe someone find other Tool or method to extract Tizen 3 Firmware...
Best Regards
Woooah, seems I was drunken with my "Beta" Batch file... for extracting *.img
Few really bad "mistakes"...
I made it few times now with line by line...
As my batch not work proper..
Meanhwile SM-R600 got new update:
Code:
R600XXU1AQK4/R600OXA1AQK4
At the moment I can again not find up2date Changelog...
Best Regards
Code:
COMBINATION-FT30_R600XXU1[B]AQL1[/B].tar.md5
Meanwhile new Combination Firmware floating around...
Only as info.
Best Regards
adfree said:
Code:
COMBINATION-FT30_R600XXU1AQI6.tar.md5
:good:
Thanx for sharing.
I can not try self... as no SM-R600... but first look looks good.
Related to my first mistake with SM-R732... where I have first flashed the Live Demo Unit Firmware...
2 XX in Filename is correct for Retail device
3 XXX means "danger", because for LDU
Also no Rollback Prevention problem at the moment visible...
Code:
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI6
R600XXU[COLOR="Green"][B]1[/B][/COLOR]AQI8
Both Firmware packages in same Software Revision. :good: :good:
So in theory...
We need only 1 brave tester.
I need some time to extract all files...
To check if Codes etc. maybe same or changed...
Best Regards
Click to expand...
Click to collapse
I HAVE the live demo version. Can I Flash regular version of tizen onto live demo unit with any of the zip files in this forum? I'm very familiar with flashing via odin, i just can't tell if any of these will work on my unit?
Thanks for all the work @adfree! I have the Canadian SM-R600 (R600XXU1AQK4) and was wondering if you have had any success yet changing the CSC? I saw you played an active part in accomplishing that on the S3.
I'm by no means proficient in programming, but quite familiar with rooting, sdb, odin, etc. Let me know if I can help.
Cheers!
@detjoe
I have no SM-R600 for own tests...
1 user told me via PM he tried COMBINATION-FT30_R600XXU1AQI6.tar.md5 long time ago.
With no success in changing CSC...
He wrote...
Flashing no problem... Combination Firmware work... Code is same...
But after Reboot old CSC is back...
I have only idea it is maybe related to Product Code...
Maybe security increased... or maybe only no luck.. or maybe error in Combination Firmware...
Meanwhile also CQL1 as Combination Firmware "available":
Code:
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQI4.tar.md5[/COLOR]
[COLOR="Green"][B]COMBINATION-FT30_R600XXU1AQI6.tar.md5[/B][/COLOR]
[COLOR="Red"]COMBINATION-FT30_R600XXU1AQL1.tar.md5[/COLOR]
Green means we have for free download... :good: and tested by 1 user
Red is only on paid sites...
Maybe with other Combination Firmware more luck...
Maybe if somebody is willing to test...
Own risk!
Best Regards
Edit 1.
SDB Tool is for instance here... with tiny Instruction how to connect via WiFi...
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards
Hoping this works....
adfree said:
@mmafighter077
I wrote you PM...
No idea if you allready tried?
Best Regards
Click to expand...
Click to collapse
I'm hoping you guys get this to work.....I have a German version of the watch, but need it to be set for the US. I had the same issues as reported above with it swapping back to the original CSC.
Any update on this for you guys?
I have put tpk file on the device but when I click to install it (as android) appears : Error occurred: No matched application found.
How Can I solve it?
It's important to install it directly from gear sport and not using a pc software.
Thank you
Sofia
No idea what you trying to achieve...
But...
1.
You are familiar with SDB or ADB Tool?
Code:
[B]sdb install [/B]blahblaTPKorblablaWGT.blabla
2.
Because you can enter device over WiFi from ADB Android APK...
So you could try to fire up few Commands...
Look here:
https://forum.xda-developers.com/showpost.php?p=75833894&postcount=7
I have success with this nice APK:
https://play.google.com/store/apps/details?id=com.cgutman.androidremotedebugger
So in theory... no PC... but you need ADB on Phone...
Sorry, we have no Developers... which creates something usefull for free...
In theory it is not Rocket Science to create Installer APK on Phone...
Best Regards
@sofiaxxx
You tried?
I am too lazy to check it...
As I am using PC... and "sdb install"...
https://developer.tizen.org/ko/foru...t/how-install-tpk-within-device?langswitch=ko
Something like this could work:
Code:
/usr/bin/pkgcmd -q -i -t tpk -p <tpk file name>
Best Regards
Use the directions from the thread below with the correct combination firmware for your watch to change the region on your phone. (Allowed me to finally get samsung pay to work in the USA).
Follow these directions https://forum.xda-developers.com/gea...ar-to-t3718236], but find a combination firmware and a stock firmware for your device.
For the SM-R720 I got it from here:
https://addrom.com/combination-rom-s...ar-s2-sm-r720/
and I used stock firmware R720OXA2EQH1 since it had a XAR folder in this location: CSC_OXA_R720OXA2EQH1_usr.tar.md5\csc.img\preconfig \
(CPC5 and AOJ3 did not have it or I didnt see it)
and now samsung pay shows up.
mickeyx323 said:
Hi, can anyone that lives in the US tell me what firmware they have on their R720 wifi only model and if spay works on your watch.. Samsung is no help. They cant even tell me which version im suppose to have on my watch. Ive been trying to get spay to work on my watch for the past year.
Click to expand...
Click to collapse
I got a carrier version not wifi only but pay works on it and its the latest firm out drc1 on a r730a
Sorry i couldnt help more
You can change CSC/Sales Code to XAR... this is the US Sales Code...
Then you can play with Samsung Pay on:
Code:
SM-R720
SM-R732
SM-R760
SM-R770
SM-R600
Tested and confirmed by many users...
Step 1.
Is to connect with Tool SDB...
Best Regards
adfree said:
You can change CSC/Sales Code to XAR... this is the US Sales Code...
Then you can play with Samsung Pay on:
Code:
SM-R720
SM-R732
SM-R760
SM-R770
SM-R600
Tested and confirmed by many users...
Step 1.
Is to connect with Tool SDB...
Best Regards
Click to expand...
Click to collapse
Where might I find help on how to do this?
TIA
You need SDB... to connect over WiFi...
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Step 1.
Connect to correct IP....
use my Link to find out how...
SDB is similar to ADB from Android world...
Step 2.
Code:
sdb shell
Then you can use this Command:
Code:
launch_app csc-manager.csc-pre-configuration
Select XAR
Best Regards
adfree said:
You can change CSC/Sales Code to XAR... this is the US Sales Code...
Then you can play with Samsung Pay on:
Code:
SM-R720
SM-R732
SM-R760
SM-R770
SM-R600
Tested and confirmed by many users...
Step 1.
Is to connect with Tool SDB...
Best Regards
Click to expand...
Click to collapse
As I am still quite new to this device, Is one to possibly benefit From changing the csc on these and use on other carriers I I got a R730a I thought it was a 20 but I guess I was wrong
adfree said:
You can change CSC/Sales Code to XAR... this is the US Sales Code...
Then you can play with Samsung Pay on:
Code:
SM-R720
SM-R732
SM-R760
SM-R770
SM-R600
Tested and confirmed by many users...
Step 1.
Is to connect with Tool SDB...
Best Regards
Click to expand...
Click to collapse
This is what I'm trying to do what file on s3 do you launch I tried csc.manager.csc-pre-configuration and launch fails everytime. There has to be something missing ugh
Dmkarkutt said:
This is what I'm trying to do what file on s3 do you launch I tried csc.manager.csc-pre-configuration and launch fails everytime. There has to be something missing ugh
Click to expand...
Click to collapse
Hey guys I had the same issue you guys had so I gave up on that idea and did it this way.
Follow these directions https://forum.xda-developers.com/gear-s3/how-to/succesfully-changed-csc-to-xar-to-t3718236], but find a combination firmware and a stock firmware for your device.
For the SM-R720 I got it from here:
https://addrom.com/combination-rom-samsung-gear-s2-sm-r720/
and I used stock firmware R720OXA2EQH1 since it had a XAR folder in this location: CSC_OXA_R720OXA2EQH1_usr.tar.md5\csc.img\preconfig\
(CPC5 and AOJ3 did not have it or I didnt see it)
and now samsung pay shows up. Man finally! I have been trying for so long with samsung and they couldn't even tell me what firmware I was suppose to have. And it all happened because they flashed the wrong firmware on my watch when i sent it in for a band replacement.
Good luck, Hopefully it works for you
Oh and if you get a kernal panic after flashing the combination firmware dont freak out. I waited a bit, but then just decided to hold the power key until it restarted.
mickeyx323 said:
Hey guys I had the same issue you guys had so I gave up on that idea and did it this way.
Follow these directions https://forum.xda-developers.com/gear-s3/how-to/succesfully-changed-csc-to-xar-to-t3718236], but find a combination firmware and a stock firmware for your device.
For the SM-R720 I got it from here:
https://addrom.com/combination-rom-samsung-gear-s2-sm-r720/
and I used stock firmware R720OXA2EQH1 since it had a XAR folder in this location (CPC5 and AOJ3 did not have it or I didnt see it):
CSC_OXA_R720OXA2EQH1_usr.tar.md5\csc.img\preconfig\
and now samsung pay shows up. Man finally! I have been trying for so long with samsung and they couldn't even tell me what firmware I was suppose to have. And it all happened because they flashed the wrong firmware on my watch when i sent it in for a band replacement.
Good luck, Hopefully it works for you
Oh and if you get a kernal panic after flashing the combination firmware dont freak out. I waited a bit, but then just decided to hold the power key until it restarted.
Click to expand...
Click to collapse
This is what I was trying to do as I had done it this way on s3 just couldn't find s2 combination file. I'll look thank you so much, really appreciate the help
Short tested with EQJ2... not work:
Code:
sh-3.2$ launch_app csc-manager.csc-pre-configuration
... launch failed
sh-3.2$ launch_app csc-manager.csc-verifier
... launch failed
sh-3.2$
So this trick not work anymore on these newerGear S2 Firmware:
Code:
[COLOR="Red"][B]EQJ2
FRC1[/B][/COLOR]
Will check later older Version... since when S.msung removed this...
Best Regards
adfree said:
Short tested with EQJ2... not work:
Code:
sh-3.2$ launch_app csc-manager.csc-pre-configuration
... launch failed
sh-3.2$ launch_app csc-manager.csc-verifier
... launch failed
sh-3.2$
So this trick not work anymore on these newerGear S2 Firmware:
Code:
[COLOR="Red"][B]EQJ2
FRC1[/B][/COLOR]
Will check later older Version... since when S.msung removed this...
Best Regards
Click to expand...
Click to collapse
Follow the directions from the link I posted, thats the only way it worked for me. I couldn't get it to work via command line
Sorry, my fault...
Seems not working for SM-R720 nor SM-R732...
Tested with Firmware Version BOKK... and my rooted BOKK
Code:
sh-3.2$ launch_app csc-manager.csc-verifier
... launch failed
sh-3.2$ launch_app csc-manager.csc-pre-configuration
... launch failed
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# launch_app csc-manager.csc-pre-configuration
... launch failed
sh-3.2# launch_app csc-manager.csc-verifier
... launch failed
Strange... I was successfully with 1 of these SM-R730 devices... so I thought it is also working on R720 and R732...
Best Regards
adfree said:
Sorry, my fault...
Seems not working for SM-R720 nor SM-R732...
Tested with Firmware Version BOKK... and my rooted BOKK
Code:
sh-3.2$ launch_app csc-manager.csc-verifier
... launch failed
sh-3.2$ launch_app csc-manager.csc-pre-configuration
... launch failed
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# launch_app csc-manager.csc-pre-configuration
... launch failed
sh-3.2# launch_app csc-manager.csc-verifier
... launch failed
Strange... I was successfully with 1 of these SM-R730 devices... so I thought it is also working on R720 and R732...
Best Regards
Click to expand...
Click to collapse
So can these things actually be rooted. I haven't even looked yet as I just figured it was a no
So can these things actually be rooted. I haven't even looked yet as I just figured it was a no
Click to expand...
Click to collapse
With few limitations...
SM-R720 and SM-R732 "tested"...
I have only SM-R732, but SM-R720 is same...
And most success with older Firmware...
As Sa.sung only increase Security...
And my rooting method is simple...
Inject su Binary into rootfs.img...
Code:
/bin/su
So most working features in Firmware Version BOKK... with this simple Rooting method...
If I remember correct, EPK5 and EQC1 tested... but less success and more restrictions...
So I gave up to check EQJ2 or FRC1...
Never tested Qualcomm devices like SM-R730 and so on...
Nobody requested...
Best Regards
mickeyx323 said:
Use the directions from the thread below with the correct combination firmware for your watch to change the region on your phone. (Allowed me to finally get samsung pay to work in the USA).
Follow these directions https://forum.xda-developers.com/gea...ar-to-t3718236], but find a combination firmware and a stock firmware for your device.
For the SM-R720 I got it from here:
https://addrom.com/combination-rom-s...ar-s2-sm-r720/
and I used stock firmware R720OXA2EQH1 since it had a XAR folder in this location: CSC_OXA_R720OXA2EQH1_usr.tar.md5\csc.img\preconfig \
(CPC5 and AOJ3 did not have it or I didnt see it)
and now samsung pay shows up.
Click to expand...
Click to collapse
Where did you get R720OXA2EQH1 file? I searched in the xda forum but there's none, when Google it, the only place found wants $ to download the file
I really want to use Samsung pay on the S2 in Canada eh!
Thanks.
macv36 said:
Where did you get R720OXA2EQH1 file? I searched in the xda forum but there's none, when Google it, the only place found wants $ to download the file
I really want to use Samsung pay on the S2 in Canada eh!
Thanks.
Click to expand...
Click to collapse
Now worries, I followed the instructions a little scared using the firmware on this forum: R720XXU2EQH1 and when finished, got OTA update :good:.
Thanks a lot man!
Galaxy Watch SM-R800
Galaxy watch is registered with Samsung pay Hongkong.
Please help me to change region to Australia.
thanks
adfree said:
Sorry, my fault...
Seems not working for SM-R720 nor SM-R732...
Tested with Firmware Version BOKK... and my rooted BOKK
Code:
sh-3.2$ launch_app csc-manager.csc-verifier
... launch failed
sh-3.2$ launch_app csc-manager.csc-pre-configuration
... launch failed
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# launch_app csc-manager.csc-pre-configuration
... launch failed
sh-3.2# launch_app csc-manager.csc-verifier
... launch failed
Strange... I was successfully with 1 of these SM-R730 devices... so I thought it is also working on R720 and R732...
Best Regards
Click to expand...
Click to collapse
nep123 said:
Galaxy watch is registered with Samsung pay Hongkong.
Please help me to change region to Australia.
thanks
Click to expand...
Click to collapse
This is the wrong thread for that. This is for American firmware I would assume by the title
csc reset
adfree said:
You need SDB... to connect over WiFi...
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Step 1.
Connect to correct IP....
use my Link to find out how...
SDB is similar to ADB from Android world...
Step 2.
Code:
sdb shell
Then you can use this Command:
Code:
launch_app csc-manager.csc-pre-configuration
Select XAR
Best Regards
Click to expand...
Click to collapse
This code does´t work for me.
I receive a message:
Launch failed
My watch is a SM-r720
Any idea?
I have R-720 and get the same message:
Launch failed
Any progress, anyone?
--- EDITED
After about a week trying, I finnaly solved the firmware and samsung pay problem!!!!!
It's may first resolution post..I will tray to do as the forum rules asks....
from the post: https://forum.xda-developers.com/smartwatch/gear-s2/samsung-pay-gear-s2-t3816505
"Hello Everyone. I have some awesome news for anyone who wants to activate samsung pay on ANY gear s3 classic (SM-R770). I have successfully changed my CSC to XAR (which is the csc for USA)
DISCLAIMER: this is a detailed account of what i did and it worked for me. USE AT YOUR OWN RISK.
Ok so first i want to say thanks to @BiggPharma , @xedamen , @Honestly Annoying , and @adfree as i used guides produced by each of them to do this.
What youll need:
Netodin3
files for current firmware. I got mine from @xedamen post:
https://forum.xda-developers.com/gea...-r770-t3646789
Then I got the post at - https://forum.xda-developers.com/smartwatch/gear-s2/samsung-pay-gear-s2-t3816505
to get the firmwares
Hi There!
Samsung Pay works fine now!!!!
I did it on my Gear S2 Classic R720.
Seems to be a compatible work around for any Gear S2 and Gear S3.
Important: Use stock and combination firmware for your specific model number.
Look for it here in XDA.
Post Original for S3 (Instructions which a followed and worked for me)
https://forum.xda-developers.com/gea...ar-to-t3718236
For Gear S2 R720
Combination firmware
https://drive.google.com/file/d/1sP-...ysc226THS/view
Stock Firmware
https://forum.xda-developers.com/gea...-r732-t3684789
My gear s2 got two or tree more updates ota, and is still fine.
The gear app on your phone will "self-update", and eventually you show the samsung pay option.
My credit card from Brazil was validate to use. Just didn't linked with my local account. It's like a separated samsung account (cuz now the gear s2 is linked with the samsung awards from usa, i bet tis just some region incompatibility)
Nothing here is my credit! Well, those last 4 phrases at least and the post, haha
(and back to de first post for the instructions)
shout out to @BiggPharma for the guide that relates to SM-R760
INSTRUCTIONS:
----------------
1. Check reactivation lock is off
- On your phone, go to Samsung Gear App
- Go to Setttings Tab, choose "Find my Gear"
- Make sure Reactivation Lock is off
2. Connect your watch to your PC
- Hold down the home/power button until you see the "rebooting" screen
- Release the home/power button then quickly press it three times to bring up the boot menu
- Quick press the home/power button to cycle through the menu to "Download (wireless)"
- Long press the home/button to confirm the menu selection
- The phone will then go into WPS mode
- Double press the home/power button to change to AP mode
- On your PC, enable WiFi and connect to the access point on you watch.
NOTE: Until you successfully connect to NetOdin, your watch may display red text stating "Connection Timeout" - this is OK
- Open up NetOdin. You should now be connected to your watch (you should see the IP in the NetOdin window and "Connected to xx.xx.xx.xx" on your watch face.
NOTE: I had to disable Windows Defender public firewall temporarily for NetOdin to work properly
3. Flash combination firmware
- Load the unzipped .tar.md5 file into the "AP" box of NetOdin, wait for it to finish checking then click "Start". This should take about 10 minutes to complete after clicking "Start".
NOTE: I reccomend unchecking auto-reboot in the NetOdin3 program so it doesnt restart after flashing.
4. Flash CSC file from stock firmware
- Load the unzipped CSC_xxx.tar.md5 file into the "CSC" box of NetOdin, wait for it to finish checking then click "Start". This should take about 1-2 minutes to complete after clicking "Start".
5. Factory reset
- In your Gear, go to Settings > Gear Info > Reset Gear > Confirm
NOTE: BiggPharma got a warning at this stage that Reactivation Lock was on. Don't know why they got this message as they had definitely turned it off in step 1. They ignored it (no guts, no glory!) and was fine. Your mileage may vary. I however did not have this happen
6. Set CSC code
- In the Gear, go to the Tizen Keystring app
NOTE: screenshots of what your interface will look like: https://forum.xda-developers.com/sho...5&postcount=13
- Type in the following code exactly: *#272*719434266344#
- You will be taken to a list of CSC codes that you can scroll through. Find the code you want to change to and select it. I used "XAR" for US so that i could use samsung pay.
7. Reflash complete current stock ROM
- Load the unzipped CSC_xxx.tar.md5 file into the "CSC" box of NetOdin, wait for it to finish checking.
- Load the unzipped AP_xxx.tar.md5 file into the "AP" box of NetOdin, wait for it to finish checking.
- Load the unzipped BL_xxx.tar.md5 file into the "BL" box of NetOdin, wait for it to finish checking.
- Click "Start". This should take about 15 minutes to complete after clicking "OK".
You are done!
i also should mention after i put the current stock firmware it got a FOTA update to R770XXU2BQH1.
ALSO shoutout to @adfree for being so awesome and helping xedamen which enabled me to do all this. he also pmed me and replyed to my comments with some useful info.
To everyone who helped me thanks a billion. you made my birthday (today) AMAZING. "
in resume
1 - NetOdin 3
2 - Combination firmware at https://drive.google.com/file/d/1sP-...ysc226THS/view and Stock Firmware at https://forum.xda-developers.com/gea...-r732-t3684789
3 - follow the instructions with those files
4 - put XAR (even I am in brazil, it works! (the ZTO doesn't)
5 - Updte to the last version with the Galaxy Werable
6 - Done!!!
DISCLAIMERThis method is not tested fully and do not attempt to try this if you care about updates and support. This might potentially lock you out of updates. This could lock you out in the CSC Permanently!
Requirement1. Any watch 4 with LTE. Currently there is no known method for changing CSC on BT variant until a way is found to open the CSC change menu.
2. Make sure to back up your watch settings before continuing. This will factory reset your watch
3. Patience and time to set up watch again from scratch
Possible issues/Unconfirmed possibilities
This guide might only work in regions where Samsung pay works on phones but is restricted on watches. Might not work in regions where S-pay doesn't exist at all.
While I do not think changing CSC voids warranty, I cannot be held responsible for any loss/issues arising because of this guide.
You will start receiving updates for the new CSC (or no updates if the model isnt sold in that region). This might also mean your network capabilities, carrier support might be affected.
This guide might work on a non-samsung phone too. If you try and it works, please report it.
GUIDE
Open dialer and enter below code to bring up CSC menu
Code:
*#272*IMEI#
Spoiler: Lazy way if you have adb
adb shell input text *#272*IMEI#
Now match any CSC from the list to known CSC from post #2. No match? Do not worry. Go to Post #3 to find a CSC that could work for you.
Select the CSC and tap install. This will reboot and reset the watch.
Get past the initial setup and see if you have Samsung pay installed.
Spoiler: If Samsung Pay is not found
If not, you need to execute this in ADB after enabling developer options along with ADB Debugging and Debug over WiFi enabled.
Code:
adb shell pm install-existing com.samsung.android.samsungpay.gear
Once you have samsung pay installed, the app would open but you cannot add card yet until you install SPay wear plugin.
Head over to here, download and install the app on phone.
Once installed you can open samsung pay again on watch and continue adding your cards via phone by following the on-screen instructions.
Report the CSC you used so it could be added to the list of working CSC.
Instruction on Using ADBI do not wish to repeat the same guide. Dante63 has made an excellent guide on ADB as part of his SHM mod here. Search for "~~~ ADB Text Instructions ~~~" in his thread and follow the instructions.
CSC known to support Samsung Pay:
MEA - Middle East
SER - Unknown, Disables Bixby
SKZ - Unknown
XFA - Unknown
Click to expand...
Click to collapse
Please help me identify the region for CSC mentioned unknown.
If none of the above CSC is in your list of installed CSC, follow the below guide to choose one.
You need ADB and developer options enabled which you can set up from the guide here written by Dante63. Search for "~~~ ADB Text Instructions ~~~" in his thread and follow the instructions.
Little Background:Samsung Pay app is included in the firmware but is blacklisted in regions where it is not supported by Samsung. Find if you have the app using below code. If the result is non-empty, you are good to go.
Code:
adb shell "ls /system/app | grep 'SamsungPayForGear'"
Guide:All below commands are executed on pc via cmd/terminal with watch connected via adb over wifi.
Jump into watch's adb shell
Code:
adb shell
cd into target directory for convenience
Code:
cd /prism/etc/carriers
List all available CSC that could be selected
Code:
ls
Now, is the essential part. /System/app contains SPay but how does it know the app isnt allowed to be used? The key is a filed called "enforceskippingpackages.txt" inside each CSC folder.
What we are about to do is, take all the folder names from step 3, traverse them and read "enforceskippingpackages.txt" to find which one doesn't skip SPay.
For each CSC name, repeat the below command replacing <CSC> with the 3 letter folder name.
Code:
cat <CSC>/enforceskippingpackages.txt | grep -q SamsungPayForGear.apk && echo "Unsuitable CSC" || echo "Suitable CSC"
Look for the outputs which reads "Suitable CSC". That's what you will select in step 2 of the guide.
is there variant restriction? U model vs B model?
CSC is global?
mind sharing your gw4 model?
This thread is going to blow up.
Brilliant find
If only someone is able to find a way for BT as well before mine gets delivered in October.
jemfalor said:
is there variant restriction? U model vs B model?
Click to expand...
Click to collapse
I don't think its restricted by variant but you can follow post 3 to confirm.
jemfalor said:
mind sharing your gw4 model?
Click to expand...
Click to collapse
SM-R885F - GW4 classic 42mm LTE.
SS3300 said:
If only someone is able to find a way for BT.
Click to expand...
Click to collapse
I'm sure its about time. I do not have much time but anybody who knows about intents could come up with a quick way to start the CSC chooser activity may be. The package is
Code:
com.samsung.sec.android.application.csc
There's a way to find out activity name:
adb shell dumpsys window | find "mCurrentFocus"
but it needs your help, my watch is BT version
When I try "cat <CSC>/enforcekeeping packages.txt", the phrase "Adbd cannot run as route in production builds" appears. Is there a way to solve this?
im live korea and my watch have (KTC KTO LUC LUO SKC SKO) CSC CODE
vijai2011 said:
위의 CSC가 설치된 CSC 목록에 없으면 아래 가이드에 따라 하나를 선택하십시오.
Dante63이 작성한 여기 가이드에서 설정할 수 있는 ADB 및 개발자 옵션이 활성화 되어 있어야 합니다. 스레드에서 " ~~~ ADB 텍스트 지침 ~~~ "을 검색 하고 지침을 따르십시오.
작은 배경:Samsung Pay 앱은 펌웨어에 포함되어 있지만 Samsung에서 지원하지 않는 지역에서는 블랙리스트에 있습니다. 아래 코드를 사용하여 앱이 있는지 확인하십시오. 결과가 비어 있지 않으면 진행해도 됩니다.
[코드]adb 쉘 "ls /system/app | grep 'SamsungPayForGear'"[/코드]
가이드:아래의 모든 명령은 cmd/터미널을 통해 pc에서 실행되며, 시계는 wifi를 통해 adb를 통해 연결됩니다.
시계의 adb 셸로 이동
[코드]adb 셸[/코드]
편의를 위해 대상 디렉토리로 cd
Code:
cd /prism/etc/carriers
선택할 수 있는 사용 가능한 모든 CSC 나열
Code:
ls
이제 필수적인 부분입니다. /System/app에 SPay가 포함되어 있지만 앱 사용이 허용되지 않는다는 것을 어떻게 알 수 있습니까? 키는 각 CSC 폴더 안에 "enforceskippingpackages.txt"라는 파일입니다.
우리가 하려는 것은 3단계에서 모든 폴더 이름을 가져와서 탐색하고 "enforceskippingpackages.txt"를 읽고 SPay를 건너뛰지 않은 폴더를 찾는 것입니다.
각 CSC 이름에 대해 <CSC>를 3자로 된 폴더 이름으로 바꿔 아래 명령을 반복합니다.
[코드]cat <CSC>/enforceskippingpackages.txt | grep -q SamsungPayForGear.apk && echo "부적합한 CSC" || echo "적합한 CSC"[/코드]
"Suitable CSC" 라는 출력을 찾습니다 . 이것이 가이드의 2단계에서 선택하게 될 것입니다.
Click to expand...
Click to collapse
"cat <CSC>/enforcekeeping packages.txt" "Adbd는 빌딩에서 올 수 없다"고 말할 수 있습니다. 이 방법을 사용할 수 있습니까?
im live korea and my watch have (KTC KTO LUC LUO SKC SKO) CSC CODE
vijai2011 said:
Hello,
Got Samsung Pay to work on my GW4 classic LTE today.
Requirement1. Any watch 4 with LTE.
Click to expand...
Click to collapse
GW4 44mm LTE with DBT salescode... no reaction to *#272IME#. Neither with direct input, nor with ADB input.
bamserl said:
GW4 44mm LTE with DBT salescode... no reaction to *#272IME#. Neither with direct input, nor with ADB input.
Click to expand...
Click to collapse
what's your watch model?
jemfalor said:
what's your watch model?
Click to expand...
Click to collapse
SM-R875FZSADBT
bamserl said:
SM-R875FZSADBT
Click to expand...
Click to collapse
replace IMEI with your imei
*#272*IMEI#
jemfalor said:
replace IMEI with your imei
*#272*IMEI#
Click to expand...
Click to collapse
i did, and as i said before... it doesn't work. i just wanted to inform that this doesn't work on all GW4 LTE models - like this code didn't work on all galaxy phones.
bamserl said:
i did, and as i said before... it doesn't work. i just wanted to inform that this doesn't work on all GW4 LTE models - like this code didn't work on all galaxy phones.
Click to expand...
Click to collapse
any chance you hv updated your watch?
share your build number
Do we have to install the SHM from Dante in order to be able to do this? There's nothing happen when I use *#272*IMEI#.
My build number is R865FXXU1BUH9
I tried the following:
1. turn off bluetooth so it disconnect from the phone.
2. run it again.
error message: connection problem or invalid MMI code.
Any help please?
jemfalor said:
any chance you hv updated your watch?
share your build number
Click to expand...
Click to collapse
i have updated to the latest available build.
AP/CP: R875FXXU1BUH9
CSC: R875FOXA1BUH9
jemfalor said:
any chance you hv updated your watch?
share your build number
Click to expand...
Click to collapse
I encountered the same problem, and I am pretty sure that the code I entered is correct, and I found csc.apk in /system, which shows that it exists, but the watch does not work after entering the code
about me：
AP: R875FXXU1BUH9
CP: R875FXXU1BUH9
CSC: R875FOLB1BUH9
Model :SM-R875F
SM-R875FZGATGY