yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
[MENTION=8195733]artem5[/MENTION]

Caution... THEORY not tested maybe totally wrong...

If you look at this Picture... for SM-R720...

https://xdaforums.com/showpost.php?p=70836447&postcount=110

I have seen this Picture somewhere else "rotated"...

So maybe for SM-R760 and SM-R770:

POGO400 -> [COLOR="Red"][B]RED[/B][/COLOR]	+5V
POGO401 -> WHITE	Data-
POGO402 -> [COLOR="Green"][B]GREEN[/B][/COLOR]	Data+
POGO403 -> [B]BLACK[/B]	GND
POGO404 - no wire

Only idea/dream... NOT tested nor any evidence that could be true...

Be carefully not to damage Hardware.

Best Regards
[Samsung Gear S3] artem5:
no, POGO404=Ground 100%
[Samsung Gear S3] adfree:
Maybe then this?

POGO400 - no wire
POGO401 -> RED	+5V
POGO402 -> WHITE	Data-
POGO403 -> GREEN	Data+
POGO404 -> BLACK	GND

:confused:

Meanwhile I've created Thread here...

http://forum.gsmhosting.com/vbb/f878/gear-s3-sm-r760-sm-r770-usb-pinout-2213125/

Maybe in 2017 somebody find and post the correct Pinout.

Best Regards
[Samsung Gear S3] Zeal415:
This is pretty cool, looking forward to seeing the results down the road. Just picked up the S3 Classic, and never had a smart watch prior. Is Android wear that much better? I'd love to see Tizen based Roms, that enable the use of Wear apps, so I could actually remove Samsungs "email" "Schedule" and put on Google Calender and stuff like that. Kinda annoyed that Samsung thought that using 3 apps and syncing would be better than just using googles.
[Samsung Gear S3] coromd:
They can't use Google's apps because the Gear S3 runs Tizen, which is incompatible with Android apps.
[Samsung Gear S3] 10urshin:
What [MENTION=6773561]Zeal415[/MENTION] ask is just porting the application framework of android instead of porting whole Android Platform, which is actually possible but way too much work since software architectures of the two platforms are very different.
[Samsung Gear S3] adfree:
Bootloader Version check...

Any idea how to do it?

In easy way?

https://xdaforums.com/showpost.php?p=71794678&postcount=6

No idea if Gear S3 allow Code like this:

*#9900#

This spit out Log...

Maybe this is good idea to know...

Looks like sboot.bin Bootloader not allow Downgrade...

And Combination files set back sboot.bin... to older Version...

Not possible with "stock firmware"...

At the moment again only theory...

Best Regards

---------- Post added at 05:09 AM ---------- Previous post was at 04:28 AM ----------

This Code should also work on Gear S3...

*#9900#

We can find Bootloader Version and other infos here:

==== Boot arguments ([B]/proc/cmdline[/B])

According to this... Command for SDB is:

cat /proc/cmdline

Bootloader Version looks like this:

bootloader.ver...

Best Regards
[Samsung Gear S3] n0_yi:
and I'm still here wondering if anyone can enable Samsung Pay on my Korea version of Gear S3 ...

you guys are awesome~!
[Samsung Gear S3] BlackKnight23:
Following
[Samsung Gear S3] lsutiger216:
I hope you succeed
[Samsung Gear S3] oaid:
Yep, I failed too, at first, then saw the "tpk" in the example usage pkgcmd shows.

Not sure if due to disabling S-Health and Music, but battery drain overnight went from 2.5%/h to 1.9%/h.

Now battery stats show that Settings eats up the battery :(

Too bad there's no log like logcat in Tizen.
[Samsung Gear S3] adfree:
You could log with SDB...

sdb dlog [<filter_spec>] - view device log

With *#9900# you can set Debug Level to Middle...

"Debug enable"

Also in this menu is possible to dump some logs...

Best Regards
[Samsung Gear S3] adfree:
Password...

Seems in

/etc/shadow

root:$1$ullGurt1$6fSVvZKgePjjycNVanGxl0:17505:0:99999:7:::

owner:$6$6fB.gmp3kruX/h6t$NpqyrcATZMyDlaAbi9bc7AORXawaAR6E3AVqMz24mI89U8d/YiW/fo.lHL5J3m62.gKyQoB1NMsnpm1zjOLIU0:17505:0:99999:7:::

guest:$1$HEDSlOU7$pjDkaXEVENb8g7duwYOQ/0:17505:0:99999:7:::

$1$ seems MD5

$6$ seems SHA-512...

Hmmmmmmmmmmmmmmmmmm... :D

So ROOT and GUEST have maybe weak Hash...

Later more...

Best Regards

Edit 1.

ROOT MD5 seems:

E9F495BD92A078F8E3C9C3556A71B197

GUEST MD5 seems:

A630E469711510D6FC83B76EC18390FF

Edit 2.

https://www.unix.com/security/174566-cracking-complex-passwords-etc-shadow.html

Tiny exercise...

It is base64... So MD5 is:

?

Oh... seems bad example... I cannot decrypt base64...

Memo to me...

Anyway... windows MD5 is:

0F4137ED1502B5045D6083AA258B5C42

Edit 3.

Harhar... few seconds...

https://crackstation.net/

Only windows MD5 without salt...

Edit 4.

for study...

https://hashcat.net/wiki/doku.php?id=example_hashes

https://cryptii.com/base64-to-hex
[Samsung Gear S3] adfree:
First attempt with hashcat on my Windows Notebook...

D:\hashcat>hashcat64.exe -a 3 -m 500 rootpasswordv1.txt --force
hashcat (v4.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) HD Graphics 4000, 438/1752 MB allocatable, 16MCU
* Device #2: Intel(R) Core(TM) i3-3217U CPU @ 1.80GHz, skipped.

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
* Brute-Force

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastically reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

clBuildProgram(): CL_BUILD_PROGRAM_FAILURE

fcl build 1 succeeded.
fcl build 2 succeeded.
Error: out of memory.

* Device #1: Kernel ./OpenCL/m00500.cl build failed - proceeding without this device.

Started: Fri Jul 13 03:21:30 2018
Stopped: Fri Jul 13 03:23:12 2018

Puhhhhh...

:confused:

Will check later other Computer... :o

Best Regards
[Samsung Gear S3] adfree:
SMACK...

D:\sdb>sdb root on
Switched to 'root' account mode

D:\sdb>sdb shell
sh-3.2# grep smackfs /proc/filesystems
nodev smackfs
sh-3.2# exit
exit

D:\sdb>sdb root off
Switched to 'sdk user' account mode

D:\sdb>sdb shell
sh-3.2$ grep smackfs /proc/filesystems
nodev smackfs
sh-3.2$ ls -Z
User::Home apps_rw User::App::Shared data User::App::Shared media User::App::Shared share
sh-3.2$ chsmack
./data access="User::App::Shared" transmute="TRUE"
./.pki access="User::Home"
./apps_rw access="User::Home" transmute="TRUE"
./.config access="User::App::Shared" transmute="TRUE"
./media access="User::App::Shared" transmute="TRUE"
./.cache access="User::App::Shared" transmute="TRUE"
./share access="User::App::Shared" transmute="TRUE"
./.applications access="User::Home" transmute="TRUE"
sh-3.2$ id -Z
User::Shell
sh-3.2$ ps -Z
LABEL PID TTY TIME CMD
User::Shell 2970 pts/0 00:00:00 sh
User::Shell 2988 pts/0 00:00:00 ps

https://wiki.tizen.org/Security:Smack

My Goal is to disable SMACK...

Best Regards
[Samsung Gear S3] Underwater Ogre:
Hi, my lovely wife bought me a S3 classic. When she gave it to me we were no where near phone reception and I proceeded to wear it. Unfortunately when I got back home and tried to pair it with my Doogee S60 work phone the Doogee is not compatible with Samsung Gear app. I love the watch and the S60 is the only phone that has handle the abuse I put phones through at work. Question is..... Am I better to root the phone and make it compatible? If that's even possible? Or does this thread provide the answers I'm looking for? I'm not into programming so the jargon flies a bit over my head. Any help appreciated.

O
[Samsung Gear S3] jeebspawnshop:
This is the wrong thread for that sort of discussion.

But you should be able to install the Gear Plugin app from the Play Store and pair the watch through that.

If not, then it's unlikely root will help you much.
[Samsung Gear S3] LukeJC3MP:
I do not know if this method will work for you, but this is what my problem was and how i got it solved:

When i tried to pair it with my s7 on lineage os 15.1, the gear app claimed that my firmware was modified, so i could not use the app. After some searching around i found a reddit page, with one answer suggesting to edit the build.prop. So i changed some text in there, using the app "BuildProp Editor", and i got it to work by changing the following texts to make the app think the device is a pixel 2:

ro.build.product: walleye

ro.product.brand: google

ro.product.device: walleye

ro.product.manufacturer: google

ro.product.model: Pixel 2

ro.product.name: walleye

I also installed magisk and got the safetynet test fully passed to my surprise. The gear app itself could be downloaded from the playstore, the gear s plugin and samsung accessory service were downloaded from apkmirror.
[Samsung Gear S3] Underwater Ogre:
Awesome, now I just have to find someone who can do what you just described. Or if your in Melbourne, I've got a slab of quality beer for you to do it.

Thanks again,

O
[Samsung Gear S3] tids2k:
[MENTION=1030585]adfree[/MENTION] SMack can be disabled by adding kernel parameter security=none
[Samsung Gear S3] adfree:
[MENTION=1722345]tids2k[/MENTION]

The question is how... or where...

:confused:

I know at the moment only this:

cat /proc/cmdline

But where are these text strings stored?

:confused:

Best Regards
[Samsung Gear S3] jeebspawnshop:
From my weak understanding of all this stuff, the kernel parameter must be set at build time - the kernel must be compiled with that flag.
[Samsung Gear S3] adfree:
[MENTION=823156]jeebspawnshop[/MENTION]

https://wiki.tizen.org/Security:Smack

I will check how we can test option 1...

Btw...

This info is from 2015...

Best Regards
[Samsung Gear S3] adfree:
setenv CMDLINE
console=ttySAC%d,115200 loglevel=7

setenv CMDLINE
console=ram loglevel=4

This can be found in Bootloader sboot.bin...

But we know sboot.bin is not hackable...

Taken from FT30 Combination sboot.bin... is Engineer Version...

If we check with SDB Tool:

sh-3.2# [B]cat /proc/cmdline[/B]
console=ram loglevel=4 bootmode=ramdisk root=/dev/ram0 rw boot_ver=FT30_R760XXU2CQL1 hw_rev=13 sec_debug.enable=1 sec_debug.enable_user=0 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_checksum=0
tizenboot.serialno=4100c74261d4a3bd tizenboot.log=0x46200000,0x200000,0x0,0x2b47 tizenboot.boottime=1922ms tizenboot.sales_code=default warrantybit=0 lcdtype=0x404025 cordon=c5a22bb5eae3d1e92f80f968ef
f27748 connie=SM-R760_OPEN_EUR_e5b0891922b931e19215e3ba5431d957 ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M

We can see:

console=ram loglevel=4

If we investigate inside Firmware files... we can find:

console=ram
loglevel=4

Inside param.bin...

param.bin is not signed...

So first test to modify Kernel Command Line... is to edit param.bin

Easiest IMHO to test 1 Byte change...

loglevel=[B]7[/B]

To see if env settings come from param.bin... or elsewhere...

Best Regards
[Samsung Gear S3] adfree:
Second result... because first attempt failed...

sh-3.2# cat /proc/cmdline
console=ram loglevel=[B][COLOR="Red"]7[/COLOR][/B] bootmode=ramdisk root=/dev/ram0 rw boot_ver=FT30_R760XXU2CQL1 hw_rev=13 sec_debug.enable=1 sec_debug.enable_user=0 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_checksum=0
tizenboot.serialno=4100c74261d4a3bd tizenboot.log=0x46200000,0x200000,0x10c544,0x10ef7c tizenboot.boottime=1908ms tizenboot.sales_code=default warrantybit=0 lcdtype=0x404025 cordon=4927f6800800a4da5c3
93495cc74666b connie=SM-R760_OPEN_EUR_949c501782ea1dcffd0483d746300f7b ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M

Flashing param with netOdin seems have no effect...

But the good old dd method work... as it seems.

Tested on FT30 Combination Firmware:

CQL1

Dump partition p6

dd if=/dev/mmcblk0p6 of=/home/owner/media/Others/mmcblk0p6.bin

After modification... I can write back:

dd if=/home/owner/media/Others/paramtest_v1.bin of=/dev/mmcblk0p6

So 1 Byte change possible...

Next attempt is to add Command line:

security=none

Best Regards

Edit 1.

No luck yet...

Gear S3 hangs at Logo...

Also after Recovery...

Need to fix this...

Edit 2.

Fixed...

Created with working dump od partition p6 param.bin TAR and flashed via netOdin... SM-R760 alive again.

Puhhhh...
[Samsung Gear S3] adfree:
sh-3.2# cat /proc/cmdline
console=ram loglevel=4 bootmode=ramdisk root=/dev/ram0 rw boot_ver=FT30_R760XXU2CQL1 hw_rev=13 sec_debug.enable=1 sec_debug.enable_user=1 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_checksum=0
tizenboot.serialno=4100c74261d4a3bd tizenboot.log=0x46200000,0x200000,0x65605,0x68211 tizenboot.boottime=2462ms tizenboot.sales_code=default warrantybit=0 lcdtype=0x404025 cordon=26dac7d61c27eb92c7c94
c2c64e25ae6 connie=SM-R760_OPEN_EUR_9c1fa57a04893bd740a598432614be29 ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M

:D

sec_debug.enable=1

This Debug Level MIddle

Now I have set to high:

sec_debug.enable_user=1

But I have to find the effect... :o

Best Regards
[Samsung Gear S3] all_moon2001:
hi there

i see it's so difficult root or install android wear in gear s3

i have opinion

i hope you can develop app like "" OpenMobile ACL " to help every one to install app from google play

and thank you
[Samsung Gear S3] adfree:
Tiny progress with Kernel Command Line stuff...

1.

Few hints inside Source Code from SM-R600 for Tizen 3...

I have not checked Gear S3 sources...

2.

Back to my beloved BQC2 FTMA Combination Firmware... :D

2.1...

Generally it is possible to add to param.bin...

But sideeffects... :rolleyes:

CQL1 hangs in Logo...

BQC2 is very slow and many things crashes... like this:

W-Home has closed unexpectly.

I can not connect with SDB... WiFi crashes too... :rolleyes: :rolleyes:

3.

With good old Logfile Code:

*#9900#

I can see it is possible...

[ 1.848] [EFUSE] RB count: device(0x2), binary(0x2)
[ 1.853] [OTP] SW LOCK Success
[ 1.856] DDI value :0x00000000
[ 1.859] check_rustproof [1,0] Off
[ 1.862] cmdline: console=ram loglevel=7 [B]security=none [/B]bootmode=ramdisk root=/dev/ram0 rw boot_ver=R760XXE2BQC4 hw_rev=13 sec_debug.enable=0 sec_debug.enable_user=0 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_checksum=0 tizenboot.serialno=4100c74261d4a3bd tizenboot.log=0x46200000,0x200000,0x0,0x299f tizenboot.boottime=1859ms tizenboot.sales_code=default warrantybit=0 lcdtype=0x404025 cordon=6cc736d1016773411cca094c0cfcc986 connie=SM-R760_OPEN_EUR_7a78b3292cac71a16bb43c9f45cc47d8 ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M
[ 1.914] [GSIM] boot,normal: 1

[MENTION=9322734]all_moon2001[/MENTION]

Gear S3 is like Z1 (SM-Z130H)...

Low RAM... low eMMC...

Best Regards
[Samsung Gear S3] akrambek321:
what should i do next

Hi im in the installing part and i didn't know what is the path for the tpk in the guid that you posted...what is the path for gear s3

---------- Post added at 12:32 AM ---------- Previous post was at 12:31 AM ----------

Hi im in the installing part and i didn't know what is the path for the tpk in the guid that you posted...what is the path for gear s3

---------- Post added at 12:33 AM ---------- Previous post was at 12:32 AM ----------

Hi im in the installing part and i didn't know what is the path for the tpk in the guid that you posted...what is the path for gear s3

---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------

Hi im in the installing part and i didn't know what is the path for the tpk in the guid that you posted...what is the path for gear s3
[Samsung Gear S3] adfree:
Memo to me...

If I search for bootmode= inside Firmware files...

I can find in sboot.bin

NORMAL bootmode=ramdisk
CHARGING systemd.unit=charging-mode.target
SILENT bootmode=silent bootmode=recovery
FOTA bootmode=fota
RW-UPDATE bootmode=fus_rw
W-DOWNLOAD bootmode=wireless-download
W-UPLOAD bootmode=wireless-upload TUP

Best Regards

Edit 1.

[Unit]
Description=Charging Battery Animation
Before=xorg.service
ConditionKernelCommandLine=|!bootmode=charging-mode.target

[Service]
Type=oneshot
SmackProcessLabel=charging-animation
EnvironmentFile=/run/tizen-mobile-env
ExecStart=/usr/bin/charging-animation

[Install]
WantedBy=charging-mode.target

[Unit]
Description=Silent Boot Animation
After=wm_ready.service boot-animation.service
Before=tizen-system.target
ConditionPathExists=!/tmp/restart
ConditionKernelCommandLine=|bootmode=silent

[Service]
Type=oneshot
ExecStart=/usr/bin/vconftool set -t int memory/boot_animation/finished 1 -f
ExecStart=/bin/sleep 3
User=app
Group=app
SmackProcessLabel=boot-animation

[Install]
WantedBy=tizen-system.target
[Samsung Gear S3] adfree:
https://www.kernel.org/doc/Documentation/mmc/mmc-dev-parts.txt

Hmmmmmmmmmmmmmmmmmm.......

Maybe something like this for rootfs.img partition...

Only as info...

Be carefully!

Best Regards
[Samsung Gear S3] adfree:
:confused:

sh-3.2# mount -o remount, rw /
mount: you must specify the filesystem type

Later more...

I am at BQC2...

Best Regards

Edit 1.

sh-3.2# file -sL /dev/mmc*
/dev/mmcblk0: x86 boot sector; partition 1: ID=0xee, starthead 0, startsector 1, 7634943 sectors, extended partition table (last)\011, code offset 0x0
/dev/mmcblk0boot0: data
/dev/mmcblk0boot1: data
/dev/mmcblk0p1: data
/dev/mmcblk0p10: Linux rev 1.0 ext4 filesystem data (extents)
/dev/mmcblk0p11: Linux rev 1.0 ext4 filesystem data (extents)
/dev/mmcblk0p12: Linux rev 1.0 ext4 filesystem data (needs journal recovery) (extents) (large files)
/dev/mmcblk0p13: Linux rev 1.0 ext4 filesystem data (needs journal recovery) (extents) (large files)
/dev/mmcblk0p14: Linux rev 1.0 ext4 filesystem data (extents) (large files)
/dev/mmcblk0p15: data
/dev/mmcblk0p2: Linux rev 1.0 ext4 filesystem data (needs journal recovery) (extents)
/dev/mmcblk0p3: data
/dev/mmcblk0p4: Linux rev 1.0 ext2 filesystem data (mounted or unclean) (extents)
/dev/mmcblk0p5: Linux rev 1.0 ext2 filesystem data (mounted or unclean) (extents)
/dev/mmcblk0p6: POSIX tar archive (GNU)
/dev/mmcblk0p7: data
/dev/mmcblk0p8: data
/dev/mmcblk0p9: data
/dev/mmcblk0rpmb: ERROR: cannot read `/dev/mmcblk0rpmb' (Input/output error)
[Samsung Gear S3] adfree:
Short tested with BQC2 FTMA...

sh-3.2# cat /proc/cmdline
console=ram loglevel=4 [COLOR="Red"][B]bootmode=fota[/B][/COLOR] bootmode=ramdisk root=/dev/ram0 rw boot_ver=R760XXE2BQC4 hw_rev=13 sec_debug.enable=1 sec_debug.enable_user=0 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_ch
ecksum=0 tizenboot.serialno=4100c74261d4a3bd tizenboot.log=0x46200000,0x200000,0x8c18c,0x8e9f2 tizenboot.boottime=1866ms tizenboot.sales_code=default warrantybit=0 lcdtype=0x404025 cordon=6d9bb9c6a14a
96529ba2d3e41dcda23c connie=SM-R760_OPEN_EUR_5291d66acc9cb900da5856debcc677cf ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M

Added in param...

No effect...

So I have to check from where bootmode=ramdisk ...

:confused:

Best Regards

Edit 1.

Uuupsi...

This killed my Download Wireless... I hope I can dd correct param partition...

Edit 2.

Puhh... DL Wireless restored...

sh-3.2# dd if=/opt/usr/media/paramtest_v2.bin of=/dev/mmcblk0p6
16384+0 records in
16384+0 records out
8388608 bytes (8.4 MB) copied, 1.21974 s, 6.9 MB/s
[Samsung Gear S3] bnickolas97:
Samsung is selling this device on their parts website go to samsung parts . com and search with this model # GH81-11888A

Remember to remove the space before the .com and before the .aspx :cool::cool:
[Samsung Gear S3] adfree:
[MENTION=9351105]bnickolas97[/MENTION]

:confused:

You mean the Anyway JIG ?

https://www.tvserviceparts.com/GH81-11888A.html

:confused:

Best Regards
[Samsung Gear S3] bnickolas97:
Yes, Exactly, however it does appear to be available to the public directly from Samsung, I have ordered one myself and it is literally a fraction of the price.. I am 'new' to XDA as a member in the forums, but I've been following this thread for a very long time silently. Saw a mention about the Anyway JIG and thought I'd mention the fact that it is cheaper directly from the manufacturer. It may not work for this project, but could be useful in other project.
[Samsung Gear S3] adfree:
bash-3.2# /home/owner/test1 -o remount,rw /
test1: cannot remount /dev/root read-write, is write-protected
bash-3.2# ls -1al
total 76
drwxr-x--- 10 owner system_share 4096 Aug 26 11:09 .
drwxr-xr-x 5 root root 4096 Dec 5 2017 ..
drwxr-x--- 6 owner system_share 4096 Dec 5 2017 .applications
drwxrwxr-x 5 owner users 4096 Aug 22 14:00 .cache
drwxrwxr-x 4 owner users 4096 Aug 22 14:00 .config
drwxr-xr-x 3 owner users 4096 Dec 5 2017 .pki
drwxr-x--- 77 owner system_share 4096 Aug 23 06:15 apps_rw
drwxrwxr-x 6 owner users 4096 Aug 22 14:00 data
drwxrws--- 12 root priv_mediastorage 4096 Aug 24 11:32 media
drwxrwxr-x 7 owner users 4096 Aug 22 14:00 share
-rwxrwxrwx 1 root root 33784 Aug 26 11:09 test1

FT30 CQL1...

Found folder from where I can execute Binaries...

https://developer.tizen.org/ko/foru...-test-binary-using-sdb-possible?langswitch=ko

Long time ago... but failed to understand fully...

:o

:o

In Tizen 3 seems this folder usefull:

/home/owner

Will do somw tests...

Best Regards
[Samsung Gear S3] adfree:
I have seen this only few days ago... :o :rolleyes:

But is since BQC2... maybe earlier in Combination Firmware...

sh-3.2$ su
Password:
bash-3.2# mmcdump 0x0 0x40000 newdump.bin
blkstart: 0x0 (0), blksize: 0x40000 (134217728)
Out: /opt/usr/media/mmcdump/newdump.bin

[B][COLOR="Red"]mmcerase
mmcwrite[/COLOR][/B]

Not tested... dangerous to kill device!

Only as info.

Best Regards
[Samsung Gear S3] tids2k:
[MENTION=1030585]adfree[/MENTION] may be mmcwrite | more ?
[Samsung Gear S3] adfree:
Usage: mmcwrite {start_block} {file_name}

No problem to find correct Command... but at the moment no concrete idea... what to write. :D :o

Best Regards
[Samsung Gear S3] TheUndertaker21:
oh people still trying to port android wear? that's crazy

if they can keep samsung pay that would be nuts
[Samsung Gear S3] MatHunter:
Help

I try this command vconftool get -t string db/csc/salescode

and it says this

sh: /usr/bin/vconftool: Permission denied

What im doing wrong?

Thank you.
[Samsung Gear S3] adfree:
[MENTION=5066342]MatHunter[/MENTION]

Tizen 3 differ to Tizen 2.3...

cat /csa/csc/csc-active-customer.inf

and

cat /csa/imei/prodcode.dat

Best Regards