yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
Reason for spend time about Knox counter... Warranty Void 0 (0x0000)...

I still have no idea if my Custom Kernel or something else changed the Value... :o

:confused:

At the moment "nobody" else confirmed it is safe... to play with unsigned dzImages...

Here I will add my results:

https://xdaforums.com/showpost.php?p=78514927&postcount=680

Need some time to test few older Kernels etc...

eFuses protection...

Maybe... No idea... data displayed in Odin screen is maybe spread over whole eMMC...

On my Screenshot in prior post... I have exact 5 Bytes different... near Offset 0x1FFC00

BUT 0 - 0x1FFC00 is sboot.bin Bootloader and this area can be written from SM-R760... internally...

So IMHO whole mmcblk0boot0 can not be One Time Programming area...

Need to make Batch file *.bat... for easier test...

V1

sdb root on
sdb push mmcblk0boot0.bin /home/owner/media/Music/
sdb shell echo 0 > /sys/block/mmcblk0boot0/force_ro
sdb shell dd if=/home/owner/media/Music/mmcblk0boot0.bin of=/dev/mmcblk0boot0
sdb shell dd if=/dev/mmcblk0boot0 of=/home/owner/media/Others/mmcblk0boot0check.bin
sdb pull /home/owner/media/Others/mmcblk0boot0check.bin

Later more... need to check few things...

Best Regards
[Samsung Gear S3] adfree:
Tiny success...

With this old Tizen 3 Image I was able to write mmcblk0boot0 with dd Command. :cool: :good:

tizen-wearable_20170403.2.20170404.044936_wearable-wayland-armv7l-tw2.tar.gz

Now my ODIN MODE screen shows:

WARRANTY VOID: [B][COLOR="Red"]1[/COLOR][/B] ([COLOR="Green"][B]0x0000[/B][/COLOR])

Before it was:

WARRANTY VOID: [B][COLOR="Red"]1[/COLOR][/B] (0x[COLOR="Red"][B]0302[/B][/COLOR])

Perfect Value looks like this:

WARRANTY VOID: [B][COLOR="Green"]0[/COLOR][/B] ([COLOR="Green"][B]0x0000[/B][/COLOR])

It looks like to me...

From these 5 Bytes...

I have "control" with dd Command over 2 Bytes...

1 Byte seems write protected... maybe... Efuse... MAYBE... maybe 2 Bytes...

1 other Byte seems controlled by something else...

:confused:

00 if Knox 0
08 in my bad Knox dump...
02 now

Okidoki, I am far from Reset complete Knox crap...

BUT... I have write access to mmcblk0boot0 with dd Command. :cool: ;)

So in theory I could maybe downgrade Bootloader...

to Software Revsion 1...

We are at the moment at Software Revision 2... for SM-R760...

Attached are my dumps from mmcblk0boot0...

Best Regards
[Samsung Gear S3] gingerdude:
I'm sure I read somewhere that a Knox trip is irreversible as it's a hardware trip.

I could be wrong tho.
[Samsung Gear S3] aleksander002:
Yeah, it is. Samsungs before Knox used custom flash counter which was a self-iterating counter every time you flashed an unsigned image. Now it's both. If I understood it correctly, adfree just cleaned that counter but the real deal is efuse that wasn't really bypassed yet.

Anyway, I don't care about Knox as Spay is not available in my country anyway. Great job with Tizen 5 [MENTION=1030585]adfree[/MENTION].
[Samsung Gear S3] adfree:
IMHO according to Log files...

initialize_ddi_data: usable! (0:0x0), warranty [B]reason[/B] : (0x0000)

So for me this looks like internal Codes... why Warranty Bit is 0x1...

As "additional" info...

Here Log taken from SM-R765A ATT...

Loading DTB at 0x48000000 (0x14000)
Loading Ramdisk from 0x21000 (8388608 byte)
[EFUSE] RB count: device(0x2), binary(0x2)
[OTP] SW LOCK Success
DDI value :0x00000000
check_rustproof [1,0] Off
cmdline: console=ram loglevel=4 bootmode=ramdisk root=/dev/ram0 rw boot_ver=R765AUCU2CQL1 hw_rev=13 sec_debug.enable=1 sec_debug.enable_user=1 tizenboot.sec_atd.tty=/dev/ttySAC2 tizenboot.emmc_checksum=3 tizenboot.serialno=4100182159ed1527 tizenboot.log=0x46200000,0x200000,0x0,0x2051 tizenboot.boottime=2571ms tizenboot.sales_code=default [B]warrantybit=0[/B] lcdtype=0x404025 cordon=064193556ace99444f1f03140ce6ed7c connie=SM-R765A_ATT_NA_54a10811354a2c8a98c93c02db116201 ess_setup=0x46000000 sec_last_kmsg=0x200000@0x45e00000 sec_tima_log=0x200000@0x47c00000 pmic_info=11 mem=768M

warrantybit=0

Here for instance other Value... so IMHO other reason...

https://xdaforums.com/showpost.php?p=73607036&postcount=1

Oh... I see Warranty void still 0... so in such case I could correct the other Values... :D

(0x030a)

https://support.samsungknox.com/hc/...-a-Knox-Warranty-Bit-and-how-is-it-triggered-

If this is really true...

So I killed my Knox crap with flashing unsigned Kernel... dzImage... :rolleyes: :rolleyes:

I am back at FT30 Combination Firmware CQL1... and will flash again my self compiled Kernel...

Maybe then maybe again written this crap...

0x0302

:confused:

Best Regards
[Samsung Gear S3] adfree:
This is my plan for adding WiFi into Development Tizen 3 4 5 5.5 ...

Will later test with Tizen 5.5

Missing files taken from CQL1 FT30 Combination Firmware... and attached here...

Theory plan for Batch file. :D

sdb root on
sdb shell mount -o remount,rw /
sdb push wlan_v1.zip /home/owner/media/Music/
sdb shell cp /home/owner/media/Music/wlan_v1.zip /
sdb shell unzip /wlan_v1.zip
sdb shell chmod +x /usr/bin/wlan.sh
sdb shell chmod +x /usr/bin/wifi-loader
sdb shell /usr/bin/wlan.sh start

I hope I have all missing files... :o

Will test my theory later...

This needs mandatory USB cable... to perform Batch files and insert missing files...

I have never tested if enough to add files to rootfs.img... :o

Best Regards
[Samsung Gear S3] adfree:
I can now use WiFi in Tizen 5.5... :cool: :good:

Files are correct from wlan_v1.zip... :good:

but again my Batch File is not perfect... :rolleyes:

No idea if because I have used my beloved old SDB 2.2.60...

So Zip inflating to somewhere else... :o

:confused:

Need to search where exactly...

:confused: :confused:

So steps 1 by 1... in sdb shell... :o

With SDB 4.1.3...

[B]sdb capability[/B]
secure_protocol:disabled
intershell_support:enabled
filesync_support:pushpull
usbproto_support:enabled
sockproto_support:enabled
syncwinsz_support:enabled
sdbd_rootperm:disabled
rootonoff_support:enabled
encryption_support:disabled
zone_support:disabled
multiuser_support:enabled
cpu_arch:armv7
sdk_toolpath:/home/owner/share/tmp/sdk_tools
profile_name:wearable
vendor_name:Tizen
can_launch:unknown
device_name:Tizen
platform_version:5.5
product_version:unknown
sdbd_version:2.2.31
sdbd_plugin_version:unknown
sdbd_cap_version:1.0
log_enable:disabled
log_path:/home/owner/share/sdbdlog
appcmd_support:enabled
appid2pid_support:enabled
pkgcmd_debugmode:enabled
netcoredbg_support:enabled

Best Regards

Edit 1.

sh-3.2# find / -name wlan.sh
/usr/bin/wlan.sh
[COLOR="Red"][B]/root/[/B][/COLOR]usr/bin/wlan.sh

Found the Error from my Batch File... Zip is extracted to folder root...

No idea why or how to fix this to make better Batch file... :o
[Samsung Gear S3] adfree:
sh-3.2# dd if=/dev/mmcblk0rpmb of=/home/owner/media/Others/mmcblk0rpmb.bin
dd: reading `/dev/mmcblk0rpmb': Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00212669 s, 0.0 kB/s
sh-3.2# dd if=/dev/mmcblk0boot0 of=/home/owner/media/Others/mmcblk0boot0.bin
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.215114 s, 19.5 MB/s
sh-3.2# dd if=/dev/mmcblk0p14 of=/home/owner/media/Others/mmcblk0p14rootfs.bin
2674688+0 records in
2674688+0 records out
1369440256 bytes (1.4 GB) copied, 93.9293 s, 14.6 MB/s

sdb pull /home/owner/media/Others .\2
pulled mmcblk0rpmb.bin 100% 0 B 0KB/s
pulled mmcblk0p14rootfs.bin 100% 1306MB 2573KB/s
pulled mmcblk0boot0.bin 100% 4096KB 2938KB/s
3 file(s) pulled. 0 file(s) skipped.
/home/owner/media/Others 3114KB/s (1373634560 bytes in 430.757s)

I have dumped my changed rootfs.img with dd Command... and pulled over WiFi to my PC...

Need now time for few tests... to check if this will work...

Plan:

1.

Flash Combination Firmware FT30 CQL1 with netOdin.

2.

Flash my modified Tizen 5.5 with netOdin.

I hope this could work... to have WiFi...

First test with recovery from Reboot menu... WiFi worked...

No USB cable required...

But I have to be sure. :o

Then I can upload my result.

Meanwhile few Screenshots...

8 GB... maybe Error... but maybe hopefully next devices from Samsung will have more eMMC

Watch Faces... :D :o

I thought internal Watch Faces are somewhere else... but here they are in /usr/apps

I can find them by name...

Best Regards
[Samsung Gear S3] adfree:
I am uploading my result...

Need some time.

Need somebody who is willing to test. :angel:

BUT be carefully.

1.

RISK to brick your device... :o

2.

RISK to tripp Knox ... so Warranty Void is gone.

So also bye bye Samsung Pay... if out of luck...

See example:

https://xdaforums.com/showpost.php?p=73607036&postcount=1

3.

RISK to loose WiFi... so maybe netOdin will not work...

4.

OWN risk!

Please don't kill me if something goes wrong...

5.

Lower your expectation...

Tizen 5.5 is only in Development status...

No amazing apps or Watch Faces installed...

6.

Charging of Battery is possible...

But... with less "Animations"... like % progress circle etc...

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

Important Notes...

A.

Tested by me with SM-R760... :cool:

(((((((((in theory also runs on other Gear S3... UNTESTED))))

B.

Deactivate Reactivation Lock... to prevent """funny""" sideefects...

NO joke!

With custom stuff MANDATORY to deactivate Reactivation Lock...

Otherwise full Knox crap like prevent boot... netOdin could be deactivated...

C.

Tested with Combination Firmware FT30... CQL1 and CRB1 Tizen 3 Firmware.

So first step is to flash Combination Firmware... for instance CQL1 from here:

https://xdaforums.com/gear-s3/development/rom-samsung-gear-s3-sm-r760-t3746522

D.

After Combination Firmware... next round with netOdin.

netOdin is here:

https://xdaforums.com/showpost.php?p=73503787&postcount=150

Link to example/DEMO Tizen 5.5 Firmware will follow... if upload ready.

Best Regards

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

WARNING!

OWN RISK!

Tizen 5.5 with working WiFi... tested only with SM-R760:

https://www.file-upload.net/download-13456119/tizen55_DEMO_custom_Wifi_work_v1.zip.html

BEFORE trying.

Read carefully again:

https://xdaforums.com/showpost.php?p=78582106&postcount=690

If question(s).

Ask BEFORE you try...

To prevent worst case scenario...

Please not forget to check in Odin Mode.

Warranty Void

and important:

REACTIVATION LOCK: OFF

If Combination Firmware allready flashed.

Please I need Photo... to compare EFUSE infos...

Thanx in advance.

Best Regards
[Samsung Gear S3] adfree:
Found my old Photo... where Knox untouched...

WARRANTY VOID: [COLOR="Green"][B]0 (0x0000)[/B][/COLOR]

Here also EFUSE infos different...

Second Photo after my attempt to fix Knox...

So I was only able to "reset" Value inside brackets...

(0x0000)

https://xdaforums.com/showpost.php?p=78530937&postcount=683

Best Regards
[Samsung Gear S3] RohanKalra97:
When you reset the value were you on tizen 5.5 or on stock?
[Samsung Gear S3] adfree:
Look here:

https://xdaforums.com/showpost.php?p=78530937&postcount=683

Older Tizen 3 Firmware...

tizen-wearable_20170403.2.20170404.044936_wearable-wayland-armv7l-tw2.tar.gz

No idea if also possible with other Firmware...

But I am 100 % sure this is not possible with Stock Firmware... as you need minimum ROOT access to write to this partition:

mmcblk0boot0

And as you can see.

I was not able yet to reset Warranty Void 1... only the reason info... :o

I could do few experiments with Tizen 5.5 and check if can do similar things, like in this old Tizen 3 Firmware...

Best Regards
[Samsung Gear S3] adfree:
:D :o :silly: :eek:

I was able to write whole mmcblk0boot0...

But stupid me tried sboot of Software Version 1... :rolleyes:

Result is...

Black screen...

With USB cable I see request for driver Exynos7570...

:rolleyes: :rolleyes:

Puh... so I need some time to restore Bootloader... the hard way...

Before I typed Command:

reboot download

I have pulled dump of written data...

So it seems this time also Warranty Void 1 was erased...

Best Regards

Edit 1.

After some "Google search"...

A

Seems I can use drivers from SM-R380/SM-R381...

(14-34) SM-R380 R381 Boot Recovery Guide_rev2 0.pdf

I was able to install the 32 bit drivers in my Windows Vista 32 bit...

B

Multidownloader-32bit.exe start and detect "something"...

C

Puuuuuuhhhhh... now the harder part... :rolleyes:

Seems I have to create own cfg... :o

Maybe I can use as template... from G900H...

; BL1
DNW_STORE e5420 fwbl1 10 1000 "IMAGES\bl1"
; BL2
DNW_STORE e5420 fwbl1 10 5000 "IMAGES\bl2.bin"
; S-BOOT
DNW_STORE e5420 fwbl1 10 5000 "IMAGES\s-boot.bin"
; TZ
DNW_STORE e5420 fwbl1 10 5000 "IMAGES\tz.img"

These files can be found in older Firmware in system-data.img in /var/tmp or something like this...

Or I can "create" something...

Because only in Software Revision 1 Firmwares found...

APK3 for instance... :eek: :rolleyes:

Edit 2.

Found via Google...

https://xdaforums.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865

http://forum.gsmhosting.com/vbb/f200/sm-g920f-boot-repair-exynos-7420-device-2198973/

Edit 3.

Maybe my mistake was... to forget cm.bin :rolleyes:

Anway...

Attached is APK3 Bootfiles in Original... this hopefully help me later with sboot from BQC2...
[Samsung Gear S3] adfree:
Tiny progress...

A

I have changed template for CFG...

B

[COM17]Transfer Done : C:\2019\myBOOTrepair\bootrepairSMr760_v1\IMAGES\bl1	2019_01_04-16_41_38
[COM17]Wait Re-Connect AP USB Device	2019_01_04-16_41_69
[COM17]Please Run Re-Enumeration Sequence on AP	2019_01_04-16_41_69

Now I am here...

I have to add few files... only short tested with 3...

I have ignored EL3_MON...

; S Project

; must keep order of binary list

; BL1
DNW_STORE e5250 fwbl1 200 20 "IMAGES\bl1"
;DNW_WAIT
; BL2
;DNW_STORE e5250 el3_mon 2000 20 novi_2.bin

; u-boot
; Wait Re-Enumeration

DNW_WAIT

DNW_STORE e5250 bl2 2000 20 "IMAGES\bl2.bin"

;DNW_WAIT
DNW_STORE e5250 bootloader 20000 20 "IMAGES\s-boot.bin"

;DNW_WAIT
;DNW_STORE e5250 tzsw 20000 20 4pt.img

C

Memo to me...

Seems realy important to hold Power Button...

Best Regards
[Samsung Gear S3] adfree:
Before I have killed my SM-R760 with APK3 sboot...

I know I have flashed Combination Firmware BQC2...

So I need to "extract" files...

Minimum for test...

BL1
BL2

Later more...

Best Regards

Edit 1.

I am out of luck... :o :(

Found in old SM-R765T AQA6 Firmware Software Revision 2 files... from system-data.img

Edit 2.

With help of "Original Files"... I have extracted from BQC2 sboot.bin

Help for search	size ca.
bl1	0	-	2000	8 KB
e3mon	2000	-	F0000000	120 KB
bl2	20000	-	01000014	64 KB
s-boot	36000	01000014	836 KB
s-boot end search for	VERSION_-+J0
tz	107000	-	1E0000	512 KB

Edit 3.

Found something funny... during my search for Bootloader parts... in SM-R765F Combination Firmware...
[Samsung Gear S3] adfree:
Puuuuuuuuuuuuuhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh... :D :cowboy:

Seems I have reanimated my SM-R760...

After finding this Thread:

https://xdaforums.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461

He simplified the Config... :good: :good:

DNW_STORE e7420 fwbl1 5 20 bl1
DNW_STORE e7420 el3_mon 5 0 el3.bin.signed
DNW_WAIT
DNW_STORE e7420 bl2 5 20 bl2.bin.signed
DNW_STORE e7420 bootloader 5 0 u-boot.bin.signed
DNW_WAIT

So it was easier to read...

I did few stupid Edits...

Now I need Vodka because I thought I will never manage it... :eek:

Battery was really down... now I need few minutes for full charge...

Then I can post my edited Config and steps...

I can tell I only needed 3 files... because damn bl1 ever restarted...

And no need to hold any key...

Very simple... if you have correct files and Tools... :angel:

Best Regards

Edit 1.

[COM17]Write thread Start##################	2019_01_08-03_35_531
[COM17]Transfer Done : C:\2019\myBOOTrepair\bootrepairSMr760_v1\IMAGES\el3mon.bin	2019_01_08-03_35_696
[COM17]Wait Re-Connect AP USB Device	2019_01_08-03_35_712
[COM17]Please Run Re-Enumeration Sequence on AP	2019_01_08-03_35_712
[COM17]Transfer Done : C:\2019\myBOOTrepair\bootrepairSMr760_v1\IMAGES\bl2.bin	2019_01_08-03_35_739
[COM17]Transfer Done : C:\2019\myBOOTrepair\bootrepairSMr760_v1\IMAGES\s-boot.bin	2019_01_08-03_35_943
[COM17]Write thread Exit##################	2019_01_08-03_35_943

This is Log like in Screenshot...

In Screenshot hopefully visible I have also Odin opened... BEFORE I connected my watch... I have only selected BL... instead all files... for faster Boot Restore...

It was NOT important to press any Key...

I have only connect to my POGO... then checked with open eyes if Odin find Port... :D

Later I will upload my files...

Need some cleaning...
[Samsung Gear S3] Longpre:
Any updates on porting wear OS to Gear S3?
[Samsung Gear S3] adfree:
;DNW_STORE e7570 fwbl1 5 20 bl1.bin
DNW_STORE e7570 el3_mon 5 0 el3mon.bin
DNW_WAIT
DNW_STORE e7570 bl2 5 20 bl2.bin
DNW_STORE e7570 bootloader 5 0 s-boot.bin
;DNW_WAIT

Attached are the files... how I was able to repair my SM-R760 in "Exynos" Mode...

Files extracted from BQC2 FTMA Combination Firmware sboot.bin:

R760XX[B]E[/B]2BQC4

This is Engineer Bootloader...

No idea if generally could work... or I have luck because exact this Bootloader was on my SM-R760... before I have killed with stupid tests... :D :o

Best Regards
[Samsung Gear S3] adfree:
Tiny exercise to install RPM into Tizen 5.5...

sdb root on
Switched to 'root' account mode

sdb push hash-signer-0.0.2-3.1.armv7l.rpm /tmp
WARNING: Your data are to be sent over an unencrypted connection and could be read by others.
pushed hash-signer-0.0.2-3.1.armv7l.rpm 100% 18KB 0KB/s
1 file(s) pushed. 0 file(s) skipped.
hash-signer-0.0.2-3.1.armv7l.rpm 154KB/s (19136 bytes in 0.121s)

sdb shell mount -o remount, rw /

sdb shell rpm -Uvh --force /tmp/hash-signer-0.0.2-3.1.armv7l.rpm
error: Failed dependencies:
xmlstarlet is needed by hash-signer-0.0.2-3.1.armv7l

Aha... interesting...

sdb shell rpm -Uvh --force /tmp/xmlstarlet-1.4.1-3.1.armv7l.rpm
Preparing... ################################# [100%]
Updating / installing...
1:xmlstarlet-1.4.1-3.1 ################################# [100%]

sdb shell rpm -Uvh --force /tmp/hash-signer-0.0.2-3.1.armv7l.rpm
Preparing... ################################# [100%]
No manifest in this package. Creating default one
Updating / installing...
1:hash-signer-0.0.2-3.1 ################################# [100%]

Best Regards

Edit 1

sdb shell rpm -Uvh --force /tmp/dotnet-build-tools-2.1.502-8.1.armv7l.rpm
error: Failed dependencies:
corefx-managed-ref is needed by dotnet-build-tools-2.1.502-8.1.armv7l

Edit 2.

sdb shell rpm -Uvh --force /tmp/corefx-managed-ref-2.1.4-3.10.noarch.rpm
Preparing... ################################# [100%]
Updating / installing...
1:corefx-managed-ref-2.1.4-3.10 ################################# [100%]

sdb shell rpm -Uvh --force /tmp/dotnet-build-tools-2.1.502-8.1.armv7l.rpm
Preparing... ################################# [100%]
No manifest in this package. Creating default one
Updating / installing...
1:dotnet-build-tools-2.1.502-8.1 ################################# [100%]

But rootfs.img is not big enough... dotNet is huge and reqired 81 MB more fee space...

So I have deleted:

locale-archive 83 Mb nig file... no idea for what... :D

sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 929M 312M 75% /
devtmpfs 291M 4.0K 291M 1% /dev
/dev/mmcblk0p12 139M 45M 91M 33% /opt
/dev/mmcblk0p14 1.3G 929M 312M 75% /
/dev/mmcblk0p10 15M 132K 15M 1% /usr/lib/modules
tmpfs 303M 16K 303M 1% /dev/shm
tmpfs 303M 1.8M 301M 1% /run
tmpfs 303M 0 303M 0% /sys/fs/cgroup
tmpfs 303M 133M 170M 44% /tmp
/dev/mmcblk0p2 6.8M 2.5M 3.8M 40% /csa
/dev/mmcblk0p13 1.9G 23M 1.9G 2% /opt/usr
tmpfs 61M 40K 61M 1% /run/user/5001
/dev/mmcblk0p13 1.9G 23M 1.9G 2% /opt/usr/home/owner/media
[B]sh-3.2# rm /usr/lib/locale/locale-archive[/B]

Now need little bit time to find correct Command line... for build dotNet... :o

Edit 3.

sh-3.2# dotnet-build -?
/usr/bin/dotnet-build: illegal option -- ?
usage:
/usr/bin/dotnet-build restore <project> [-s <source>] ...
/usr/bin/dotnet-build build <project> [-c <configuration>] ...
/usr/bin/dotnet-build pack <project> [-c <configuration>] [-v <version>] ...
/usr/bin/dotnet-build install <project> [-t <type>]
sh-3.2# dotnet --help
/usr/bin/dotnet: line 9: /usr/share/dotnet-build-tools/cli/dotnet: cannot execute binary file

Edit 4.

dotNet samples I can download from here:

https://github.com/Samsung/xamarin-forms-samples
[Samsung Gear S3] speedme:
although I barely understand what you are doing, I do have to admire your persistance in trying to port Android Wear on the Gear S3.

Keep up the good work [MENTION=1030585]adfree[/MENTION], I know a lot of us really appreciate it (but don''t say it that often)
[Samsung Gear S3] gingerdude:
I sold the watch ages ago and got the galaxy watch but I love the determination of adfree and follow the thread as I I'd love to see him succeed.
[Samsung Gear S3] saif.dmaster:
Would love to see you succeed. Go [MENTION=1030585]adfree[/MENTION] ?
[Samsung Gear S3] yariksychov:
Go [MENTION=1030585]adfree[/MENTION]!

Thread has over 230k views, we need more people involved into this
[Samsung Gear S3] mcwups1:
Read an article that stated you could put Wear OS on the Gear S3 Frontier smartwatch, and it took me here, however, I don't see any way to actually DO IT.

Is this real, or just a work in progress?
[Samsung Gear S3] primod808:
Yes it's a work in progress stay tuned.
[Samsung Gear S3] yariksychov:
/Off topic

I actually think it's a marketing article.. found a discounted open watch in Best buy and was somewhat in a rush. Didn't have lots of time to think so just googled wear os on frontier and found the mentioned article. It had references to xda so figured it must be true.. never was. Had Galaxy watch before (42mm) but returned it after two weeks, couldn't stand the battery life on the small watch. Ended up getting frontier and actually grew to love it.

After all, sounds like the marketing trick worked :laugh:

N.B. got an update this morning: tizen 4.0.0.2 has arrived! Software version R760XXU2DSA1!

Pretty stoked to see Samsung taking care of more/less dated watch. Probably last update before new Galaxy sport rolls out.
[Samsung Gear S3] Qwibbert:
Yeah, I just read about the update. Although I haven't got it yet, I'm super happy that they actually did it!!!!:laugh:
[Samsung Gear S3] pizza_pablo:
Same here.

My hopes were UP and then down...

https://www.i4u.com/2017/04/122106/here-samsung-gear-s3-running-android-wear
[Samsung Gear S3] matezz992:
progress?

Any progress? I'm looking forward to android wear on gear s3
[Samsung Gear S3] adfree:
SM-R500 Firmware leaked...

Same Exynos 9110 like Galaxy Watches...

Tizen 4.0.0.[B]3[/B]

Spotify.tpk is inside CSC... NaverMap.wgt

I can sideload these TPKs on my SM-R760... for tests... :D

Best Regards
[Samsung Gear S3] deadman96385:
In case others want the firmware, I have uploaded it here https://androidfilehost.com/?fid=11410963190603915888
[Samsung Gear S3] matezz992:
Tizen is bull****. I can Android Wear.
[Samsung Gear S3] failsafe65:
Is there any chance that this could apply to the Galaxy Watch? And if Android Wear doesn't work, is there still a way to root it?
[Samsung Gear S3] adfree:
In theory yes... not tested yet.

I have root access in Tizen 2.3 and Tizen 3 Stock Firmware...

At the moment I am waiting only for FT40 for my SM-R760... for tests with Tizen 4... :rolleyes:

NO idea how much Security is increased in Tizen 4 nor in SM-R8 devices...

A

You need to know exact Model Name... to have Combination Firmware...

Galaxy Watch is again dozen of devices... :rolleyes: :eek:

Best """support""" for SM-R800 and SM-R810...

B.

If Combination Firmware is available... "only" modification of rootfs.img

Best Regards
[Samsung Gear S3] Void_Dragon07:
I don't get it what is the advantage of rooting a smartwatch?
[Samsung Gear S3] RohanKalra97:
Installing Apps not available on galaxy Apps

Custom Themes, Launchers etc.
[Samsung Gear S3] Void_Dragon07:
Holy **** seriously? But isnt tizen a whole different os do standard android apk probably dont run on it how do we find these apps themes launchers honest to god had no clue it was possible to sideload apps and stuff on tizen