yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S2] SavageMind1:
Tizen Vs AW

I like the idea of AW on the GS2 if is ported well. I love my GS2 but Int to use it like my Garmin Fortrex GPS. I want the option to read lat/long, MGRS, or UTM. The built in accelerometers and compass could be utilized for inertial navigation giving the GPS a break and improving battery life and accuracy. So far everything I have found is hot garbage and mostly related to fitness or road navigation instead of cross country navigation. Since there is such a Tizen resistance for development my only recourse is to pray for AW.
[Samsung Gear S2] valsivief:
Thank you very much for updating this thread after a while , and you get it at the end ,

can you make the process clearly to remove the reactivation lock plz , i was so confuse coz i don't know too much in Kaizen

Thanks in advance
[Samsung Gear S2] adfree:
Better write me PM... Private Mail...

NO money required...

But I can not give public details to prevent trouble... :angel:

Best Regards
[Samsung Gear S2] adfree:
After long wait for dotNet Milestone... with Tizen 4 support... :( :o

I am back to commercial 2.3 Firmware... :D

Today played around with FOTA stuff...

Few things failed... to Fake Gear S3 to get FOTA package... :o

But now I am on ;

R732XXU2EQD1

I have flashed floating around EPK5 Firmware and downloaded the 20 MB FOTA package...

Btw... really funny...

If you unzip the 20 MB... you will find 15 MB ramdisk-recovery.img inside...

But this file seems not in update progress... imho... :D

BOOTLOADER	sboot.bin	FULL_IMG	0	0
ROOTFS	delta.rootfs	DELTA_FS	0	0
CSC	delta.csc	DELTA_FS	0	0
BOOT	delta.boot	DELTA_IMG	0	0
MODULE	delta.module	DELTA_IMG	0	0
RAMDISK2	delta.ramdisk2	EXTRA	0	0
RECOVERY	delta.recovery	EXTRA	0	0

So maybe they blow up the file size... so it looks more mighty update... :D :D :D :rolleyes:

Instead 5 MB...

Now I will check if I can flash back to Combination Firmware AOJ2... or mighty Rollback Prevention will punish me...

To replace sboot.bin in update.zip failed...

Will try later something similar...

Best Regards

Edit 1.

Puh... it work. :cool:

Combination Firmware AOJ2 without problem flashed via USB cable and Odin (still no idea if different if I would use Download Wireless Mode)... and Bootloader downgrade success:

bootloader.ver=R732XXE2BOJ2
[Samsung Gear S2] adfree:
:D

Update package from EPK5 to EQC1 has same size...

20 MB

:D :D

And also contains 15 MB ramdisk-recovery.img...

So imho EPK5 have minor differences between EQC1 or EQD1... :rolleyes:

Best Regards
[Samsung Gear S2] adfree:
Strange... no idea how or why...

But today I have realized I can flash modified Firmwarefiles with Odin...

Instead my older method...

https://xdaforums.com/showpost.php?p=72124639&postcount=121

:confused:

No idea if this is result of removing Reactivation Lock "complete"...

Or by luck... :D

Maybe my stupid Flash attempts with Tizen 3 and 4 and stupid tests with testmode Commands unlock something...

:confused: :confused:

I will upload my rooted BOKK Firmware...

Maybe someone can confirm...

WARNING!

Only tested via soldered wires...

It seems difference between Flashing via "Odin WiFi" and "Odin USB"...

Upload need some time... if finished I will add Link... later...

Best Regards

Edit 1.

It seems Reactivation Lock OFF is enough... to have less Security check in Odin.

ROOTed BOKK Firmware for SM-R732

https://www.file-upload.net/download-12576528/BOKK_rooted_NEWversion_smR732_June2017_v1.zip.html

OWN RISK!

Seems Reactivation Lock need to be OFF

Only tested with soldered wires to have USB connection...

RISK to disable Download wireless... if Reactiation Lock is ON
[Samsung Gear S2] Electronicbrain:
Actually, the first gear ran modified Android, and you could sideload apps to it.
[Samsung Gear S2] adfree:
ROOT done with rooted Firmware... via FOTA... :D :rolleyes:

Base was my rooted BOKK Firmware...

Catched update.zip for:

R732XXU2DPFB/R732OXA2DPFB

Steps...

1.

update.zip from Gear Manager app is TAR file... so rename...

delta.tar
delta.ua

delta.ua can be take from update.zip or in theory standard delta.ua is used...

2.

I have copied these 2 files into:

/opt/usr/media/Others

Because with USB cable easy...

MTP ;)

3.

Then via SDB Tool... fire up few Commands:

sh-3.2# cd /opt/usr/media/Others
sh-3.2# cp *.* /opt/usr/data/fota
sh-3.2# fota_local_test.sh
Setting fota update mode
Rebooting with argument 'fota'.

Maybe I will upload this FOTA package as "example"...

First Feeling...

R732XXU2DPFB is nice... not so hard secured like EPK5 as it seems.

Need more time for tests...

Best Regards

Edit 1.

https://www.file-upload.net/download-12579715/FOTA_smR732_BOKK_2_DPFB.zip.html

FOTA package added...
[Samsung Gear S2] adfree:
Puh... :angel:

I was now able to fix my long time problem with Limitation of ROOT... in Tizen 2.4 Mobile...

https://xdaforums.com/showpost.php?p=72854079&postcount=460

I hope this knowledge helps to remove Restriction in Gear S2 too...

In EPK5 is for instance su Binary not enough...

Example...

sh-3.2# dd if=/opt/usr/media/Others/csc.img of=/dev/mmcblk0p10
dd: opening `/dev/mmcblk0p10': [COLOR="Red"]Permission denied[/COLOR]
sh-3.2# reboot download
Failed to write reboot param to /run/systemd/reboot-param: [COLOR="Red"]Permission denied[/COLOR]

This happens not in Firmware Version before EPK5... Tested in:

BOKK - FULL ODIN package
DPFB - only as FOTA package

So since EPK5 stronger Security...

Best Regards
[Samsung Gear S2] adfree:
Project for next few days...

Custom FOTA package (Delta file)...

Reduce to only sboot.bin Bootloader

delta.ua
sboot.bin
update.cfg

Edit of update.cfg

BOOTLOADER	sboot.bin	FULL_IMG	0	0

At the moment theory only...

But we have progress for Gear S3 Bootloader Downgrade project... :cool:

Best Regards
[Samsung Gear S2] tids2k:
in delta files everyfile is signed inside.
[Samsung Gear S2] adfree:
Every file is not really problem...

I have forgotten it is signed... the whole TAR package...

You can find at end of file the Certs...

Anyway...

I have to test...

Maybe Signature check not enabled in FOTA local test... in SM-R732...

We have to find difference between theory and reality... :D :o

Best Regards
[Samsung Gear S2] boswelja:
Did you ever get it working?
[Samsung Gear S2] adfree:
Seems Samsung changed something to unified Cr.p... :rolleyes:

So I can not use this cr.p anymore...

Tested and NOT work anymore

tizen-unified_20170620.1.20170626.113904_wearable-wayland-armv7l-tw1.tar.gz
tizen-unified_20170704.3.20170705.132525_wearable-wayland-armv7l-tw1.tar.gz
tizen-unified_20170707.1.20170707.092054_wearable-wayland-armv7l-tw1.tar.gz

I had some trouble as I have destroyed my csa.img ... :rolleyes: :o

But I was able after many hours... to write BT address and SN back...

Otherwise if this happens, Gear Sx is nearly unuseable...

But I am 99,9 % sure this is not my CSA accident... they changed something...

1.

My old tested TAR Firmware Images for Tizen 4 still work...

2.

This is not first time...

I can remember after we had some success with RD-PQ... to run Tizen 3...

3.

Now new dotNet Preview 4 is downloadable...

https://developer.tizen.org/development/tizen-.net-preview/introduction

As it seems... they have no really interest to add Wearable support...

So Tizen 4 is not really interesting for me. :D

Same for Tizen 3... :D :D

Nothing really "amazing" inside... only security cr.p...

Best Regards

Edit 1.

Tested older Version from June...

tizen-unified_20170620.1.20170626.113904_wearable-wayland-armv7l-tw1.tar.gz

So they removed SM-R732 supported few weeks ago... :cyclops:
[Samsung Gear S2] adfree:
Tested short if Signature is checked of FOTA package... if I perform manually FOTA local test

sh-3.2# fota_local_test.sh
Setting fota update mode
Rebooting with argument 'fota'.

Strange... via Code from Misc. menu not possible... never realized before... as I have ever used shell script *.sh

/bin/cp: accessing `/opt/usr/data/fota/delta.ua': Permission denied
/bin/cp: accessing `/opt/usr/data/fota/delta.tar': Permission denied
Setting fota update mode
>> /opt/data/recovery does not exist. create one
/bin/mkdir: cannot create directory `/opt/data/recovery': File exists
/usr/bin/fota_local_test.sh: line 44: /opt/data/recovery/DELTA.PATH: Permission denied
Failed to write reboot param to /run/systemd/reboot-param: Permission denied

I have simple unpack delta.tar.... then repack... so Signature/Certs gone...

Successfully updated from BOKK to DPFB... with "custom" Delta file...

Maybe next attempt with replaced sboot.bin ...

Best Regards
[Samsung Gear S2] adfree:
Tested now "custom" Delta package/FOTA file...

Inside this TAR file now only 3 file:

sboot.bin
delta.ua
update.cfg

sboot.bin taken from EPK5 Firmware...

update.cfg modified... looks now like this:

BOOTLOADER	sboot.bin	FULL_IMG	0	0

Result is now EPK5 Bootloader is flashed in this way...

Check:

sh-3.2# cat /proc/cmdline

console=ram loglevel=4 root=/dev/ram0 rw initrd=0x42000000,8M bootmode=ramdisk pwron.reason=ap:swrst,pmic:pwron sec_debug.enable=0 sec_debug.enable_user=0 sec_watchdog.sec_pet=5 se
c_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 lcdtype=402015 oops=panic pmic_info=83 sysscope=0xee000000 cordon=8d1e8a70bcc48b8b94d406ccd4497814 warrantybit=1 serialno
=4100ed7b5567828b tizenboot.sec_atd.tty=/dev/ttySAC1 tizenboot.emmc_checksum=3 tizenboot.odin=1 bootloader.ver=R732XXU2EPK5 bootloader.fb=0x48000000 bootloader.log=0x114a@0x46187bd

Will now prepare second TAR... with older sboot.bin to check downgrade...

Later more...

Best Regards

Edit 1.

For me it work... :cool:

Tested with my rooted BOKK Firmware.

sh-3.2# cat /proc/cmdline

console=ram loglevel=4 root=/dev/ram0 rw initrd=0x42000000,8M bootmode=ramdisk pwron.reason=ap:swrst,pmic:pwron sec_debug.enable=0 sec_debug.enable_user=0 sec_watchdog.sec_pet=5 s
ec_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 lcdtype=402015 oops=panic pmic_info=83 sysscope=0xee000000 cordon=67c48571afc43c04feb5edafbc5aabc3 warrantybit=1 serialn
o=4100ed7b5567828b tizenboot.sec_atd.tty=/dev/ttySAC1 tizenboot.emmc_checksum=3 tizenboot.odin=1 bootloader.ver=R732XXE2BOJ2 bootloader.fb=0x48000000 bootloader.log=0x1745@0x4605c3
3b bootloader.elapsed=2687

No tested yet, but IMHO... this should run also from Combination Firmware...

Edit 2.

I made tests with 2 files.. ever:

delta.tar
delta.ua

delta.ua is taken from delta.tar...

No idea if any differences... if only delta.tar is used...

I can copy these 2 files via MTP... as still soldered wires/USB connected...

Then with help of SDB:

sh-3.2# cd /opt/usr/media/Others
sh-3.2# cp *.* /opt/usr/data/fota
sh-3.2# fota_local_test.sh
Setting fota update mode
Rebooting with argument 'fota'.
[Samsung Gear S2] adfree:
<model model_name="SM-V700" pet_name="Gear"/>
<model model_name="SM-R380" pet_name="Gear 2"/>
<model model_name="SM-R381" pet_name="Gear 2 Neo"/>
<model model_name="SM-R710" pet_name="Gear 2 Solo"/>
<model model_name="SM-R750" pet_name="Gear S"/>
<model model_name="GT-V770" pet_name="Gear S"/>
<model model_name="SM-R750A" pet_name="Gear S"/>
<model model_name="SM-R750P" pet_name="Gear S"/>
<model model_name="SM-R750T" pet_name="Gear S"/>
<model model_name="SM-R750V" pet_name="Gear S"/>
<model model_name="SM-R750B" pet_name="Gear S"/>
<model model_name="SM-R750L" pet_name="Gear S"/>
<model model_name="SM-R750W" pet_name="Gear S"/>
<model model_name="SM-R750D" pet_name="Gear S"/>
<model model_name="SM-R750R4" pet_name="Gear S"/>
<model model_name="SM-R750J" pet_name="Gear S"/>
<model model_name="SM-R730" pet_name="Gear S2"/>
<model model_name="SM-R730A" pet_name="Gear S2"/>
<model model_name="SM-R730P" pet_name="Gear S2"/>
<model model_name="SM-R730V" pet_name="Gear S2"/>
<model model_name="SM-R730T" pet_name="Gear S2"/>
<model model_name="SM-R730S" pet_name="Gear S2"/>
<model model_name="SM-Q430" pet_name="Gear S2"/>
<model model_name="SM-Q540" pet_name="Gear S2"/>
<model model_name="SM-Q540S" pet_name="Gear S2"/>
<model model_name="SM-Q540A" pet_name="Gear S2"/>
<model model_name="SM-Q540P" pet_name="Gear S2"/>
<model model_name="SM-Q540V" pet_name="Gear S2"/>
<model model_name="SM-Q540T" pet_name="Gear S2"/>
<model model_name="SM-R720X" pet_name="Gear S2"/>
<model model_name="SM-R732" pet_name="Gear S2"/>
<model model_name="SM-R732X" pet_name="Gear S2"/>
<model model_name="SM-R720" pet_name="Gear S2"/>

com.samsung.b2-setup-wizard

This seems the annoy... auto select thingie...

Strange... in Gear S3 few more but not gear S3... :confused:

Later more...

I am trying to play with Command:

launch_app
[Samsung Gear S2] adfree:
sh-3.2# screen_recorder --help
It's a console application
screen_recorder: invalid option -- '-'
usage: screen_recorder -f <format> -c <capture> -o <width>,<height> -p <fps> -b <bitrate> -t <filepath> -m <mode>
ex: screen_recorder -f RGB4 -c 1 -o 240,400 -p 30 -b 1000000 -t screen-recording -m 0
-f format [RGB4,SN12]
-c capture [1:Still, 2:Stream]
-o output size[w,h]
-p fps [30,60]
-b bitrate [Max 2000000 - 2Mbps]
-t filepath [screen-recording]
-m mode [0-RECORD, 1-PREVIEW]
-? help
error:3

Oh, cool...

It was not in BOKK Firmware...

But in DPFB... :good:

Need to find good parameter...

Best Regards

Edit 1.

sh-3.2# screen_recorder -f RGB4 -c 1 -o 360,360 -p 30 -b 1000000 -t Video -m 0
It's a console application
++ capture = Still
++ format = RGB4
++ output size(width,height) = 360,360
++ fps = 30
++ bitrate = 1000000
++ filepath = Video
========================================
XvGrabPort success : 78
========================================
open drm device : /dev/dri/card0
Open drm device : /dev/dri/card0
DRI2 GET BUffer Time:0
BO_IMPORT Time:0
Output file path (/tmp/Video.mp4)
starting run, recreate the timer
XSync Time = 1
PutStill time = 0
XvPutStill - 0
Processed frame = 0
DUMPING. data->in_width : 360, data->in_height : 360, Time:9
Pixmap_dump time = 10
Total Time Taken = 11
XSync Time = 5
PutStill time = 0

No idea why... stored in tmp folder...

Will check result...

Edit 2.

Hmmm, tiny problems...

On my SM-Z130H easy...

sh-3.2# screen_recorder -f RGB4 -c 1 -o 480,800 -p 30 -b 2000000 -t screen-recording -m 0
^Cfinish

(screen_recorder:2541): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object->refcount > 0' failed

MP4 is easy playable... stored in:

/op/usr/media/...

I can use Ctrl + C to stop capture... and MP4 is not corrupted...

On my SM-R732 I was not able to take valid MP4...

Will try other Binaries... from other Firmware... like EPK5... and will check also SM-R760 file...

I need Video Capture... on Gear...

Edit 3.

screen_recorder MD5 from DPFB

A0A42B3B9E3E8A6611CB1EDC23CBA900

EPK5

AD68A8AD31FDAEB606055F43C9C16753
[Samsung Gear S2] adfree:
Hmmmm...

After several hours of stupid experiments... :rolleyes:

I can capture Video of my Gear S2 (SM-R732)...

Highest Quality Setting:

screen_recorder -f RGB4 -c 1 -o 360,360 -p 30 -b 2000000 -t screen-recording -m 0

Phenomenon(s) :rolleyes:

1.

Compared with SM-Z130H...

I can not choose file path...

... and I can not capture more then 1 Video... as -t only work as file name...

:confused:

So all captured Videos goes to:

/tmp

2.

Compared with SM-Z130H...

Result Video have "special" Format...

I am not able to play with my Win 7 Computer... only with my GT-I9300 and installed VLC app...

Attached is Example...

Maybe I am toooo stupid to find correct Codec or Tool...

I have started with DIVX... and installed latest...

A.

My Avira creates Alarm if DIVX Installer starts... :rolleyes: :rolleyes:

B.

DIVX crashes if I try to play this recorded Video... :rolleyes: :rolleyes: :rolleyes: :mad:

I have only short looked into first few Bytes... it looks like "Header" is strange... of this MP4...

Best Regards
[Samsung Gear S2] DinckelMan:
Getting this on an unrooted SM-R760

sh-3.2$ screen_recorder -f RGB4 -c 1 -o 360,360 -p 30 -b 1000000 -t Video -m 0
It's a console application
++ capture = Still
++ format = RGB4
++ output size(width,height) = 360,360
++ fps = 30
++ bitrate = 1000000
++ filepath = Video
========================================
XvGrabPort success : 78
========================================
Unable to open a DRM device
DRI2 GET BUffer Time:0
[Error] : fail to get buffers
crashed [1501082795] processname=screen_recorder, pid=12116, tid=12116, signal=11Segmentation fault07
[Samsung Gear S2] pRo_lama:
I don't have any problem to play this video.

BSPlayer + K-Lite Codec pack
[Samsung Gear S2] adfree:
No idea why or how...

I can not capture more then 30 seconds... :rolleyes:

Attached are 2 Videos...

part 1 is only 16 seconds... and have moved as much as I can... :D

part 2 is 21 seconds... last scene is same Pic...

"New" method for now... as only file name instead file path is possible... and screen_record stops self...

screen_recorder -f RGB4 -c 1 -o 360,360 -p 30 -b 2000000 -m 0 -t video

I moved -t parameter to the end... :D

So I can easily change filename... to add 1 more Video...

cp /tmp/*.mp4 /opt/usr/media/Video

Then I copy result(s) to Video folder...

reboot

:rolleyes:

No idea why...

But I can not see immediatly after cp Command... and I have NO idea have to refresh MTP... so I reboot via Command...

:rolleyes: :rolleyes:

Reboot autodelete MP4 from /tmp folder...

So not forget to backup...

----------------

Video(s) show the Misc menu...

Which I can enter in all Firmware Versions... most of them rooted... :D

In Combination Firmware easy via Input like *#1234#... simple:

*#6472#

In my rooted Retail Versions via SDB and Command:

testmode *#6472#

Also few other ways possible...

Maybe I will check again how to do this with non rooted Gear...

Best Regards
[Samsung Gear S2] DinckelMan:
*#6472# is not recognized as a command on an unrooted R760
[Samsung Gear S2] adfree:
*#6472# is not recognized as a command on an unrooted R760

I know, this is blocked/disabled... :o

I also know few methods to bypass... but nearly all required manipulation/modification of Firmware... and this is at the moment for Gear S3 NOT possible... yet.. :o :o

Can you please check, if this makes any difference to enter this Code after doing this?

https://xdaforums.com/showpost.php?p=71819880&postcount=65

Thanx in advance.

Best Regards
[Samsung Gear S2] DinckelMan:
That's what I did :) doesn't respond to the code at all. I have an idea that I wanna try but it'll have to wait until tomorrow
[Samsung Gear S2] adfree:
I have now EQC1 Firmware for playing around. :cool:

Thank you very much.

If somebody need, here it is for region OXA:

https://www.file-upload.net/download-12636189/EQC1_OXA_smR732.zip.html

Now I can play little bit with non rooted Firmware. :D

This should work with SDB without ROOT...

sh-3.2$ vconftool get -t string db/csc/salescode
[B]db/csc/salescode, value = DBT (string)[/B]

DBT is my German Sales Code...

sh-3.2$ vconftool get -t string db/csc/bincode
[B]db/csc/bincode, value = OXA (string)[/B]

Gear S2 have OXA and OXX region Firmware... different countries/languages supported...

Best Regards
[Samsung Gear S2] chediak:
Sorry, I'm not a developer but I'm very interested in running android wear on S2. Can someone please tell me how is going this thread? Thank you so much.

Enviado de meu MI MIX usando Tapatalk
[Samsung Gear S2] DinckelMan:
Sorry to disappoint, but there's nothing you can install on the watch yet. Adfree has been doing most of the work trying to figure out how to downgrade the firmware on the watch so we are able to flash custom stuff on it, but so far nothing is available to an normal user
[Samsung Gear S2] adfree:
Somebody have SM-R730 Service Manual and can share please.

Thanx in advance.

Best Regards

Edit 1.

Reason is to identify Pinout for USB connection...

https://xdaforums.com/showpost.php?p=73359677&postcount=3
[Samsung Gear S2] adfree:
First attempt to modify ramdisk-recovery.img...

Easist idea was... edit IP address of Download/Upload...

Simple text search leads to...

192.168.49.20

etc\wifi\dhcpd.conf

This work for me... :cool:

But I have tried first with Combination Firmware...

I will do some tests... maybe I understand how Upload Wireless work...

Best Regards

Edit 1.

Seems I can extract this image like rootfs.img with good old:

ext2explore.exe

:good:

Will check if I can add/remove/replace files... like I mount rootfs.img :cowboy:
[Samsung Gear S2] adfree:
Little time table for my little brain...

WoW... """amazing"""... between EQC1 and EQH1 are 5 months Development time...

Respect... from this 18 MB FOTA are only 2 MB difference in rootfs.img

ramdisk-recovery.img... 15 MB... if I unpack and compare... this looks 1:1 like in EQC1...

:confused: :confused:

Why Samsung doing this kind of jo.e?

SM-R732	Month	2015/O	2016/P	2017/Q
A-01	January
B	Feb
C-03	March	E[B]Q[/B]C1
D	April
E-05	May
F	June
G-07	July
H	Aug	E[B]Q[/B]H1
I-09	Sep
J	Oct	A[B]O[/B]J3
K-11	Nov	B[B]O[/B]KK	E[B]P[/B]K5
L	Dec

:rolleyes:

Best Regards
[Samsung Gear S2] xcpion:
Hi, I would like the Combination firmware.

I live in Australia, and I downgraded to the R732XXU2AOJ3 firmware as my watch kept prompting me to upgrade the firmware but after downloading and installing, it always failed to update. So I thought if I could flash it with that R732XXU2AOJ3 firmware that my issues would be solved. It did to an extent, I was able to upgrade to the latest firmware from there using the Gear manager app.

However I believe that original firmware was not specific to my country of sale (Australia) and so Samsung Pay does not appear on the watch nor does it appear in the Gear manager app (I can't install it on my phone- S8), but not within the Gear app nor on the watch.

So I'm hoping if I find the correct firmware that applies to my country that it would solve the problem . I do believe Australia is one of those countries where Samsung Pay is active.

Let me know if the combination firmware you have would help?

Kind Regards,

Jeremy
[Samsung Gear S2] adfree:
[MENTION=4353111]xcpion[/MENTION]

SM-R732 have 2 Firmware packages for multiple countries/CSC/Sales Code...

OXX

and

OXA

OXA package contains for instance:

SER -- Russia
DBT - Germany
XAR - US

Samsung Pay is inside Security obscurity crap and only enabled for few "countries"...

Country means not where your position is... Country means what your device have stored... :D :D

To find out, what your device have stored as active CSC... aka Sales Code...

"Easiest" way is to check with SDB Tool and Command:

https://xdaforums.com/showpost.php?p=73253129&postcount=205

vconftool get -t string db/csc/salescode

Output looks like this:

sh-3.2$ vconftool get -t string db/csc/salescode
db/csc/salescode, value = DBT (string)

To enable Samsung Pay... is NOT easy...

Because Security CRAP in chain...

This is f. Knox Security stuff...

I was able with Retail M. app to enable SPay... but it seems dangerous to CSA partition... :eek:

I have Retail M app only from Gear S3... so maybe this is the reason...

Maybe more luck with Gear S3... but here it fails with handset update to Android Spay part... :D :silly: :rolleyes:

Maybe I upload Video... maybe then more clear...

Only as hint.

Best Regards

P.S.:

About Combination Firmware... if you need... PM me...

I mean send Private Mail...
[Samsung Gear S2] adfree:
Splay...

Attached Video is from Gear S3... no idea if full safe enable possible...

On my SM-R732 this leads to maybe bigger problems,,,

Here I saw short the Credit Card Pictures... but then something with Security Violation or Manipulation or something in this Direction...

And I had Boot problems... :o

Seems this App write something to CSA or affect CSA partition.... So Knox Security is involved...

This could lead to heavy problems... which are not easy to fix...

This time I was able to fix this problem by flashing full Firmware with Odin... :cyclops:

Only as info...

Best Regards