yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
Killed accidentially by mistake complete CSA partition from SM-R830... GWA2.

Now trying to restore... "rebuild"...

Bad...

I have no Backup to compare...

Files + Folders inside SM-R760 for instance... as base info...

.mac.info
00000000.authtokcont
bluetooth
csc
ese
factory
imei
lost+found
nv
prov
prov_data
recovery
sensor
skpm_OTA_CSR_OCF_ECC_P256
skpm_sk.dat
skpm_supported_list
TEE
wd

bluetooth\.bd_addr
bluetooth\.local_irk
csc\csc-active-customer.inf
ese\sem_data
ese\ssp_data
factory\.ksb
factory\.nv_created
factory\.nv_ready
factory\battery_cisd_data
factory\battery_cycle
factory\battery_full_count
factory\batt_cable_count
factory\cal_date
factory\default_bt_state
factory\default_nfc_state
factory\default_wifi_state
factory\dfms_failhist
factory\earjack_count
factory\fdata
factory\hist_nv
factory\hwver
factory\nad_data
factory\test_nv
imei\.MSL_flag
imei\MSL_address.dat
imei\MSL_code.dat
imei\prodcode.dat
imei\serialno.dat
nv\nv.log
nv\nvdata.bin
nv\nvdata.bin.md5
prov\libdevkm.lock
prov_data\ccm
prov_data\dcm
prov_data\dev_root
prov_data\knox
prov_data\pfw_data
prov_data\sem
prov_data\skpm
prov_data\uaf
prov_data\ccm\ccm.dat
prov_data\dcm\dcm.dat
prov_data\dev_root\dev_root.dat
prov_data\dev_root\sym_key.dat
prov_data\knox\knox.dat
prov_data\pfw_data\.reset
prov_data\pfw_data\.sspay-service-stats.db
prov_data\pfw_data\.sspay-service-stats.db-journal
prov_data\sem\sem.dat
prov_data\skpm\skpm.dat
prov_data\uaf\uaf.dat
sensor\baro_cal_data
sensor\gyro_cal_data
TEE\00000000.authtokcont
wd\hostapd.log
wd\wd_log
wd\wifi_mf.log
wd\wpa_supplicant.log

GOOD... partition size 1:1 same in SM-R760 and SM-R830...

Now need to find minimal files + folders to get Stock Firmware to work.. :rolleyes:

Edit 1.

V1

I will take SM-R760 CSA as template... clean/erase all files and only these files content I can "rebuild"... by Copy & Paste:

.mac.info
bluetooth\.bd_addr

csc\csc-active-customer.inf

imei\prodcode.dat
imei\serialno.dat

Sidenote...

Combination Firmware work... SDB + WiFi Connection work tooo

Will see if Stock Firmware can boot with these 5 files in CSA... :o
[Samsung Gear S3] adfree:
Some tiny exercise with "event" of Hardware keys...

sh-3.2# /home/getevent -pl /dev/input/event0
add device 1: /dev/input/event0
name: "s2mpw01-power-keys"
events:
KEY (0001): KEY_POWER
input props:
<none>
sh-3.2# /home/getevent -pl /dev/input/event13
add device 1: /dev/input/event13
name: "gpio_keys"
events:
KEY (0001): KEY_BACK
input props:
<none>

Goal is to send event Command via SDB/ADB...

Need some time... long time ago and small brain... :D

Edit 1.

Because I am so slow with Copy and Paste... these 2 lines leads to Poweroff menu...

sh-3.2# /home/sendevent /dev/input/event0 1 116 1
sh-3.2# /home/sendevent /dev/input/event0 0 0 0

The funny part... same in 2014... I can capture events... but in HEX... and send require Dec :eek:

Google search results:

http://ktnr74.blogspot.com/2013/06/emulating-touchscreen-interaction-with.html

https://stackoverflow.com/questions...nd-fully-adb-shell-sendevent-device-type-code

https://stackoverflow.com/questions/26204766/simulating-combination-of-key-presses-from-adb-terminal
[Samsung Gear S3] adfree:
If I have time i will check Touch Input...

Here example with my big fat finger... tap short in the middle of screen...

sh-3.2# /home/getevent -lt /dev/input/event1
[1586219076.109728] EV_KEY BTN_TOUCH DOWN
[1586219076.109728] EV_ABS ABS_MT_TRACKING_ID 00000038
[1586219076.109728] EV_ABS ABS_MT_POSITION_X 000000ba
[1586219076.109728] EV_ABS ABS_MT_POSITION_Y 000000b7
[1586219076.109728] EV_ABS ABS_MT_PRESSURE 00000022
[1586219076.109728] EV_ABS ABS_MT_TOUCH_MAJOR 0000000b
[1586219076.109728] EV_ABS ABS_MT_TOUCH_MINOR 0000000b
[1586219076.109728] EV_ABS ABS_MT_ORIENTATION 00000000
[1586219076.109728] EV_SYN SYN_REPORT 00000000
[1586219076.112772] EV_ABS ABS_MT_POSITION_Y 000000b5
[1586219076.112772] EV_SYN SYN_REPORT 00000000
[1586219076.128094] EV_ABS ABS_MT_POSITION_Y 000000b4
[1586219076.128094] EV_SYN SYN_REPORT 00000000
[1586219076.139020] EV_ABS ABS_MT_TOUCH_MAJOR 0000000c
[1586219076.139020] EV_ABS ABS_MT_TOUCH_MINOR 0000000c
[1586219076.139020] EV_SYN SYN_REPORT 00000000
[1586219076.149829] EV_ABS ABS_MT_POSITION_Y 000000b3
[1586219076.149829] EV_ABS ABS_MT_TOUCH_MAJOR 0000000b
[1586219076.149829] EV_ABS ABS_MT_TOUCH_MINOR 0000000b
[1586219076.149829] EV_SYN SYN_REPORT 00000000
[1586219076.171933] EV_KEY BTN_TOUCH UP
[1586219076.171933] EV_ABS ABS_MT_TRACKING_ID ffffffff
[1586219076.171933] EV_SYN SYN_REPORT 00000000

sh-3.2# /home/getevent -l /dev/input/event1
EV_KEY BTN_TOUCH DOWN
EV_ABS ABS_MT_TRACKING_ID 00000039
EV_ABS ABS_MT_POSITION_X 000000be
EV_ABS ABS_MT_POSITION_Y 000000a5
EV_ABS ABS_MT_PRESSURE 0000001c
EV_ABS ABS_MT_TOUCH_MAJOR 0000000a
EV_ABS ABS_MT_TOUCH_MINOR 0000000a
EV_ABS ABS_MT_ORIENTATION 0000003f
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_POSITION_X 000000bd
EV_ABS ABS_MT_PRESSURE 0000001d
EV_ABS ABS_MT_TOUCH_MAJOR 0000000b
EV_ABS ABS_MT_TOUCH_MINOR 0000000b
EV_ABS ABS_MT_ORIENTATION 0000002f
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_PRESSURE 0000001e
EV_ABS ABS_MT_ORIENTATION 00000023
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_PRESSURE 0000001f
EV_ABS ABS_MT_ORIENTATION 0000001a
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_ORIENTATION 00000013
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_ORIENTATION 0000000e
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_POSITION_Y 000000a4
EV_ABS ABS_MT_ORIENTATION 0000000a
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_POSITION_X 000000bb
EV_ABS ABS_MT_POSITION_Y 000000a2
EV_ABS ABS_MT_TOUCH_MAJOR 00000017
EV_ABS ABS_MT_TOUCH_MINOR 0000000e
EV_ABS ABS_MT_ORIENTATION 0000002f
EV_SYN SYN_REPORT 00000000
EV_KEY BTN_TOUCH UP
EV_ABS ABS_MT_TRACKING_ID ffffffff
EV_SYN SYN_REPORT 00000000

sh-3.2# /home/getevent -vp /dev/input/event1
0001 014a 00000001
0003 0039 0000003a
0003 0035 000000af
0003 0036 000000b4
0003 003a 00000024
0003 0030 0000000b
0003 0031 0000000b
0003 0034 00000000
0000 0000 00000000
0003 0030 0000000c
0003 0031 0000000c
0000 0000 00000000
0003 0035 000000ae
0003 0036 000000b3
0000 0000 00000000
0003 0035 000000ab
0003 003a 00000023
0003 0030 0000001a
0003 0031 0000000f
0003 0034 000000f3
0000 0000 00000000
0001 014a 00000000
0003 0039 ffffffff
0000 0000 00000000

Maybe somebody have better idea how to capture Dec Values... instead HEX...

Best Regards
[Samsung Gear S3] Mulky1108:
Hey all, just wondering if there has been a successful port to Wear OS from Tizen? Or whats the progress on it? Ive read through the thread but im only starting to learn to code so i dont really understand what is being said mostly:) thanks.
[Samsung Gear S3] tanisdlj:
First of all: thanks for the great job you are all doing in here guys!

Same question than Mulky above. Is there any "user-friendly" status page or something that you can check eventually?

A 70 pages thread full of misc & tech info is not really usable to know how's the actual status of this project :).

Do we have (or could we create something) where we can check that quickly?

Thanks!
[Samsung Gear S3] adfree:
[MENTION=10736085]Mulky1108[/MENTION]

Special VIP post for you:

https://xdaforums.com/showpost.php?p=81922995&postcount=850

;)

[MENTION=4508633]tanisdlj[/MENTION]

https://xdaforums.com/showpost.php?p=81922995&postcount=850

I love your words quickly. :cool:

Please you can port Android for us quickly.

With all this helping hands here...

[MENTION=9350973]All[/MENTION]

Still need somebody who compile the AKI stuff... not only the Kernel...

And maybe somebody found meawhile the commercial Firmware or have Firmware updates for study...

Best Regards
[Samsung Gear S3] nirodg:
I confirm the combiner FW for the Frontier works. As well I've already build the kernel for the Exynox 7270. I'll keep digging into this
[Samsung Gear S3] adfree:
[MENTION=5753826]nirodg[/MENTION]

This sounds interesting... can you please explain more?

I am not sure what you mean with combiner FW... :o

Frontier means SM-R760 or LTE Variant? Liek SM-R765A

You mean you build the AKI Source?

From this Korean Android Model?

Thanx in advance.

Best Regards
[Samsung Gear S3] nirodg:
Hello there [MENTION=1030585]adfree[/MENTION]

1. By combiner FW I meant the combination firmware [R760XXU2BQC2] - it was a typo, my mistake. I also own a Frontier SM-R760.

I've used sdb to connect to it and switch to root successfully.

2. Related to building the kernel, I was checking on https://opensource.samsung.com and downloaded sources to all projects (utilities, commands) and as well on GitHub, where I found an interesting repo - it seems pretty good, so I decided to fork it and try to work on building it. https://github.com/nirodg/AW-exynos7270-kernel/tree/tizen

After a few attempts I managed to build it successfully - despite the fact of a few warnings. As well I've documented additional workaround to build it

https://github.com/nirodg/AW-exynos7270-kernel/blob/tizen/fixes.md

Now, my goals are the following:

1. Try to run the kernel using qemu - Right now I'm getting "no text/graphic" which makes me think the kernel crashes even before it can start, I think I have badly configured the needed arguments.

2. Build any of the projects (https://opensource.samsung.com) and try to install it - to make sure the sources are compatible with the device.

Now some off-topic, have you managed to run any Tizen Emulator? One way of testing my built kernel was by using the Tizen Emulator and replacing the kernel. Now, with original settings in my case it's stuck on "Booting Kernel"

And here some useful links I've seen while digging

https://github.com/tizenorg/platform.kernel.linux-exynos/tree/accepted/tizen_wearable and can be found as well under https://git.tizen.org/cgit/profile/wearable/platform/kernel/linux-3.18-exynos7270/

https://source.tizen.org/ko/release/tizen-4.0-m2

https://wiki.tizen.org/Tizen_ARM64_Development

https://wiki.tizen.org/ARM

https://lists.tizen.org/pipermail/dev/2015-January/005971.html

https://developer.tizen.org/forums/...l-dzimage-open-source-code-gear-s3-gear-sport
[Samsung Gear S3] adfree:
Index of /prerelease/tizen/unified/tizen-unified_20200504.1/tizen-unified_20200504.1.20200507.005157/images/standard/wearable-wayland-armv7l-tw2/

../
MD5SUMS 06-May-2020 16:35 483
SHA1SUMS 06-May-2020 16:35 523
SHA256SUMS 06-May-2020 16:35 643
manifest.json 06-May-2020 16:35 694
tizen-unified_20200504.1.20200507.005157_wearab..> 06-May-2020 16:35 25430
tizen-unified_20200504.1.20200507.005157_wearab..> 06-May-2020 16:35 410782
tizen-unified_20200504.1.20200507.005157_wearab..> 06-May-2020 16:35 100551
tizen-unified_20200504.1.20200507.005157_wearab..> 06-May-2020 16:34 497857552
tizen-unified_20200504.1.20200507.005157_wearab..> 06-May-2020 16:35 2480

Uuuuuhuu... Tizen 6... on 6. May... :D

I will check if I can "install"...

Best Regards
[Samsung Gear S3] adfree:
Short tested... Tizen 6 on SM-R760 possible...

tizen-unified_20200504.1.20200507.005157_wearable-wayland-armv7l-[B]tw2[/B].tar.gz

I have removed 2 files to prevent killing WiFi Download Mode...

dzImage-recovery
ramdisk-recovery.img

Runs...

Amazing... looks like 3 4 5 5.5 :rolleyes:

Will later try again to check under the hood... and make few Screenshots...

Need to add again WiFi Driver into rootfs.img... otherwise no BT no WiFi...

Only as info...

Best Regards
[Samsung Gear S3] nirodg:
Good news [MENTION=1030585]adfree[/MENTION] - keep us updated on that script. Perhaps making a git repo for it? :)

Here is my update, locally compiled the linaro/android ranchu kernel - the one mentioned in one of the oficial tizen docs.

And a good one, I could directly get logged in as root

For booting I only need 2 things, kernel and rootfs.

1. The kernel was locally compiled,

2. The rootfs was extracted from the R760XXU2BQC5_R760OXA2BQC5 and converted to qcow2 - [MENTION=1030585]adfree[/MENTION], one of your combined FWs.

qemu-img convert -O qcow2 rootfs.img rootfs.qcow2

Here's link to the kernel - I bet with a little of 'Google's magic" you can find it

git clone ssh://{yourid}@review.tizen.org:29418/platform/kernel/linux-arm64.git -b ranchu_kernel

At this point, I think I could literally mess with the kernel as much as I can before doing anything on the real device - am I wrong?
[Samsung Gear S3] Qwibbert:
[MENTION=5753826]nirodg[/MENTION]

Thanks for your nice work!

As of now, I'm trying to get your forked kernel to successfully compile on my machine(Arch).
[Samsung Gear S3] adfree:
[MENTION=5753826]nirodg[/MENTION]

Thank you. :cool:

I was NEVER able to use QEMU... :o

Maybe somebody can help me...

I am Ubuntu user...

At the moment limited time to fight against Ubuntu and my low brain...

Best Regards
[Samsung Gear S3] nirodg:
With the forked Kernel for the Exynos I still have issues to boot - while compiling I get some compilation warning and the compiler takes them as error. So I've compiled successfully ignoring the errors, but I guess I have to try again.

[MENTION=1030585]adfree[/MENTION]

To boot the Kernel - remember to convert to qcow2

qemu-system-aarch64 -m 1024 -cpu cortex-a57 -machine virt -nographic \
-kernel Image \
-append 'root=/dev/vda rw console=ttyAMA0 panic=10 init=/bin/sh CONFIG_DRM=y CONFIG_DRM_VIRTIO_GPU=y' \
-device virtio-gpu-pci \
-device virtio-blk-device,drive=image \
-drive if=none,id=image,file='/media/dorin/data/projects/gear-s3/roms/R760XXU2BQC5_R760OXA2BQC5/AP_R760XXU2BQC5_usr/rootfs.qcow2' \

If you remove the

init=/bin/sh

then the kernel will try to boot the tizen-boot.sh, and and some point will get stuck - still need to do research

To boot the ramdisk-recovery - remember to convert to qcow2

qemu-system-aarch64 -m 1024 -cpu cortex-a57 -machine virt -nographic \
-kernel Image \
-append 'root=/dev/vda rw console=ttyAMA0 panic=10 boot_mode=1 boot_mode 1' \
-device virtio-blk-device,drive=image \
-drive if=none,id=image,file='/media/dorin/data/projects/gear-s3/roms/R760XXU2BQC5_R760OXA2BQC5/AP_R760XXU2BQC5_usr/ramdisk-recovery.qcow2'

When booting the qemu stops due to a missing ENV, I've tried to append it but nothing.

You entered into /sbin/init on initrd
root=/dev/vda rw console=ttyAMA0 panic=10 boot_mode=1 boot_mode 1 BOOT_MODE=1 BOOT_MODE 1
BOOT_MODE was NOT defined!!
Do reboot!!
Reboot
Rebooting.
[Samsung Gear S3] adfree:
[MENTION=5753826]nirodg[/MENTION]

I have to "fix" few brain problems... before I will spend time "again" with Linux QEMU...

Sorry. :o

Meanwhile I have managed to have Wifi in Tizen 6...

D:\SDB\sdb4212>sdb capability
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:6.0
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

Now will check if the good old Capture Commands work.. to get Screenshots...

Edit 1.

Good old Capture command work... Screenshot possible because swipe not work...

D:\SDB\sdb4212>sdb shell enlightenment_info -dump_screen -p /home/owner/media/Images/ -n 1.png
make dump: /home/owner/media/Images/1.png

No idea why... but Bezel at the moment not work correct in main menu...

:confused:

Edit 2.

Now trying to dump whole 4 GB eMMC direct to PC...

sdb shell dd if=/dev/mmcblk0>fullDumpeMMC_4GB.bin

Have to wait...

Edit 3.

Also not work proper... but it never worked for me. All devices all Firmwares... all Computers

But this seems now possible again:

dd if=/dev/mmcblk0 | /home/toybox-aarch64 netcat 123.123.123.23 1234

:good:

Have to wait... for final check if dumped data valid...

Edit 4.

Dumped result looks good. Seems usefull. :cool: :good:

Tested few other things...

But not really success nor very excited... :o

So I have very fast flashed commercial Firmware... :angel:
[Samsung Gear S3] nirodg:
I'm just dumping now the mmc, so far I've got ~400MB locally

The mmc I'm dumping has the combined FW- If I succeed I will try to reflash to original FW and try to dump it via the Download (Wifi) mode

And I was thinking.. The Tizen emulator uses the qemu for emulating the system itself. Perhaps my approach (the qemu command and having running the custom kernel) was a kind of reinventing-the-well-thing. I will try to have the Wearable Tizen 4.0 emulator running and then try to replace its kernel with the one I've compiled. - It made me think.. how the authors of TWRP tested before flasing to real device?... And then I found this https://twrp.me/twrp/androidemulator.html
[Samsung Gear S3] adfree:
./sdb shell "su --c 'dd if=/dev/mmcblk0'" > fullDumpeMMC.bin

:good: :cool:

Please check if dump is valid...

I have the problem with this way...

Additional 2 Bytes are written before EVERY 0A :rolleyes:

this is what added... in all my Windows machines...

0D0D

I was not able to find if SDB or Windows or me the reason for this. :D

About Emulator...

I ever thought this is not ARM Kernel... I thought special X86 stuff...

So I have not much time investigated...

I lost to much time in the beginning of Tizen, as I thought I can run native Tizen TPKs on Emulator... :D

Later realized the only X86 Code runs... :rolleyes: :o

Only Widgets (WGT) can be copied from real device and test on Tizen Emulator... because """HTML"""...

Best Regards
[Samsung Gear S3] nirodg:
[MENTION=1030585]adfree[/MENTION], dumping the emmc was successful, https://gist.github.com/nirodg/f149dc0a271d1d1c504b7f070d94c9a7

I've used binwalk to have a look at the .bin file
[Samsung Gear S3] adfree:
:cool: :good:

Thank you for feedback.

I will try next days to check my SM-R760 with Linux Ubuntu and SDB...

Failed only with Windows Computers... XP... Vista... Win7

Because my alternate solution not work in Tizen 3 and 4... seems by f.&%ing Security.

https://xdaforums.com/showpost.php?p=81872965&postcount=848

Btw...

Dumped with Tizen 2.3 Firmware or Tizen 4 like EFS2?

Thanx in advance.

Best Regards
[Samsung Gear S3] nirodg:
I would recommend you to have a small Ubuntu partition :)

The dumped emmc contains Tizen 2.3 - basically is the combined FW I've used to get root access.

Today I will re-flash to original FW and try to dump it via Download Wifi mode. - and in the meantime I'm setting up my env to build the WearOS https://android.googlesource.com/platform/manifest/+/refs/heads/android-wear-5.0.0_r1

We'll keep you updated.
[Samsung Gear S3] Qwibbert:
It looks like the Tizen emulator only supports x86_64 booting :(
[Samsung Gear S3] adfree:
Requested by User...

Original ESF2 Tizen 4 Firmware for SM-R760:

https://www.file-upload.net/download-14076365/R760XXU2ESF2.7z.html

Best Regards
[Samsung Gear S3] LollosoSi:
I'm probably about to say something extremely stupid but... has anyone tried asking them directly for a port? (for newer devices too?) maybe setting up a petition or something like that? This could save everyone a ton of work and I wouldn't exclude it without even trying...
[Samsung Gear S3] Qwibbert:
That would be same as asking Apple to make Android available for their iPhones...

And why would they? There are a lot of people very satisfied with Tizen, which is not me:rolleyes:.

And if Sammy would make Wear OS an option they would be admitting that Tizen was hot garbage after all IMHO.
[Samsung Gear S3] adfree:
Trying to root FTD4 Firmware...

At the moment I have only dumped files via RDX...

Later more...

Best Regards
[Samsung Gear S3] adfree:
Oh my God... spend so many time with dump with netcat... and failed in Tizen 3 4... included FTD4 Tizen 4.0.0.7

:rolleyes:

Tried many things...

Eng Kernel... nope

Tizen 6 Kernel runs but nope... still f&ing Permission denied...

Flashed Ramdisk from SM-R500.. as I know here user was able... runs... but nope Permission denied...

Btw... Seems Samsung really unified...

I can use Ramdisk from Combination Firmware from SM-R500 in my SM-R760...

Also su...

Back to netcat... :rolleyes:

IP4 is blocked...

I have converted my IP4 into IP6 with this Online Tool...

www.ultratools.com/tools/ipv4toipv6

Now will wait for final result of dumping whole 4GB eMMC to my PC over WiFi... :cyclops:

Best Regards
[Samsung Gear S3] Longpre:
I understand gear s3 by Verizon can be rooted now which means I can flash custom ROM now right? Can I get links for step by step?
[Samsung Gear S3] adfree:
Somebody with an idea how to remove ROOT and/or Knox check?

:confused:

Goal is to start Samsung Pay on my SM-R760... with Knox 1...

Also my SM-R732 was only with Knox 1...

So I ever thought this is Root detection... :D :o :rolleyes:

Will do some Logging... maybe I can identify apps involved...

Best Regards

Edit 1

Found something in Log...

W/[B]SSPAY[/B]_UI_SVC_COMMON( 3971): payuisvc_pai.c: payuisvc_pai_perform_app_reset(804) > [36mreason [[COLOR="Red"][B]device_warranty_broken[/B][/COLOR]] [0m
[Samsung Gear S3] nirodg:
I would recommend you start reading the thread, took me about a week. By ROM there is just modified FW with root access and very veeeeeeeeeery limited usage of it - forget about sync with the phone.

Glad to see progrese mate! Unfortunately this days I'm quite busy but still finding 5 minutes to check the XDA thread.

Listen, AFAIK the WearOS is not that open-sourced, so it would be hard to get our hands on. But, what about other OEMs using the WearOS, perhaps hard to achieve, but using some oficial FW from some OEM, tons of modifications and modified kernel...

Or.. what about AsteroidOS ?
[Samsung Gear S3] adfree:
[MENTION=5753826]nirodg[/MENTION]

I thought AKI Watch could be the "Holy Grail"...

https://xdaforums.com/showpost.php?p=79816730&postcount=773

IMHO compiled Kernel and U-Boot allready inside this package...

NOT tested nor self compiled nor I have the Platform files nor PIT nor AKI Firmware nor anything else from this AKI Watch...

Nor anyone else compiled the AKI Source nor... :D

Maybe in 2020 or 2021 somebody can increase our knowledge about AKI...

Not found Firmware nor AKI users nor ...

It is Korean only product for Kids...

Anyway...

Source files looks IMHO good... and as it seems also way described to get the Platform Files...

Best Regards
[Samsung Gear S3] adfree:
[MENTION=9657115]Longpre[/MENTION]

Sorry for long time silence...:o

Can you please flash this RAMDISK from SM-R500 to your SM-R765V:

https://xdaforums.com/showpost.php?p=81799723&postcount=15

This RAMDISK work with my SM-R760... FTD4 Firmware...

If you have questions... ask here... and better before mistake.

Best Regards
[Samsung Gear S3] Olafius83:
how does that install and work on Ubuntu 12.04

how does that install and work on Ubuntu 12.04
[Samsung Gear S3] adfree:
[MENTION=10858017]Olafius83[/MENTION]

How we can help you?

:confused:

Can you give more details what you wish to achieve?

Best Regards
[Samsung Gear S3] Olafius83:
Changing my region on Galaxy watch

Sorry , actually replied to an earlier post from you count #330 . I deleted the qoute and so the reference went down the drain entirely.

Anyhow, I wanted to change the region on my galaxy watch. I have a Computer with Ubuntu so I downloaded SDBStarter 2.2.60. And tried to follow the instructions. (which were for windows)

I cant get the sdb Installed properly i guess. What doesn't help is, that I am not an Ubuntu specialist at all. Its just the system I have access to .

How is the procedure for Ubuntu?

I need some help there.

Thanks for reading