yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
Tested my self compiled Kernel dzImage... the Engineer Variant. :angel:

1.

SM-R760 boot proper as it seems. :cowboy: :cool: :good:

I have flashed before FT30 Combination Firmware CQL1...

2.

In Odin Mode I can see now also:

CURRENT BINARY: [B]CUSTOM[/B]

No idea because ENG or because not signed... :D :o

I will try now few tests... and later I will try if Download Wireless is hopefully alive...

Then I could upload my Kernel... as Example...

Best Regards

Edit 1.

Visible sideeffect... :rolleyes:

WARRANTY VOID [B][COLOR="Red"]1[/COLOR][/B] (0x0[COLOR="Red"][B]302[/B][/COLOR])

Edit 2.

C:\SDB>sdb shell
sh-3.2# whoami
root
sh-3.2# mount -o remount,rw /
mount: cannot remount /dev/root read-write, is write-protected
sh-3.2# dd if=/dev/mmcblk0rpmb of=/home/owner/media/Others/rpmb.bin
dd: reading `/dev/mmcblk0rpmb': Input/output error
0+0 records in
0+0 records out
0 bytes (0 B) copied, 0.00356646 s, 0.0 kB/s
sh-3.2# change-booting-mode.sh --update
Setting update mode for engineers
mount: cannot remount /dev/root read-write, is write-protected

Hmmm... still no idea about difference in Kernel Compiling between usr and eng...

:confused:

Edit 3.

sh-3.2# uname -r
3.18.14
sh-3.2# uname -a
Linux localhost 3.18.14 #1-Tizen SMP PREEMPT Tue Oct 23 00:10:03 CEST 2018 aarch64 GNU/Linux
sh-3.2# cat /proc/version
Linux version 3.18.14 (ubuntu64@ubuntu64) (gcc version 4.9.4 (Linaro GCC 4.9-2017.01) ) #1-Tizen SMP PREEMPT Tue Oct 23 00:10:03 CEST 2018

So it looks like my Eng Kernel is used... no Backup...

Short test... not fully...

Wireless Download start...

So later I can flash something else with netOdin...
[Samsung Gear S3] adfree:
Warranty Void/Knox crap is stored in mmcblk0boot0

Now need to find way to reset... :D

Best Regards
[Samsung Gear S3] soutieslak:
Very cool thread! I hope this development can lead to WearOS being ported to the galaxy watch! Tizen sucks! keep up the work guys!
[Samsung Gear S3] adfree:
In my older Backup of mmcblk0boot0

At Offset:

0x1FFC00

Warranty Void 0 (0x0000)

12003412000000000000000000000000534D2D523736300000000000000000000000000000000000

Now :o

Warranty Void 1 (0x0302)

12003412[COLOR="Red"][B]01[/B][/COLOR]00000000000000[COLOR="Red"][B]0A[/B][/COLOR]000000534D2D52373630000000000000000000000000[B][COLOR="Red"]EE0203[/COLOR][/B]0000

Best Regards
[Samsung Gear S3] adfree:
sh-3.2# dd if=/home/owner/media/Others/mmcblk0boot0.bin of=/dev/mmcblk0boot0
[COLOR="Red"]dd: writing to `/dev/mmcblk0boot0': Operation not permitted[/COLOR]
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0111522 s, 0.0 kB/s
sh-3.2# closed

Attempt 1. :D

Attempt 2.

Old trick... from GT-I9300 times... seems not work fully... :o

sh-3.2# echo 0 > /sys/block/mmcblk0boot0/force_ro
sh-3.2# dd if=/home/owner/media/Others/mmcblk0boot0.bin of=/dev/mmcblk0boot0
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.483718 s, 8.7 MB/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.212908 s, 19.7 MB/s

Best Regards

Edit 1.

sh-3.2# cd /sys
sh-3.2# ls
bbd bcm-dhd block bus class dev devices firmware fs kernel module power
sh-3.2# cd block
sh-3.2# ls
dm-0 loop0 loop1 loop2 loop3 mmcblk0 mmcblk0boot0 mmcblk0boot1 mmcblk0rpmb ram0 ram1 zram0
sh-3.2# cd mmcblkboot0
sh: cd: mmcblkboot0: No such file or directory
sh-3.2# ls -a1l
total 0
drwxr-xr-x 2 root root 0 Nov 3 15:36 .
dr-xr-xr-x 14 root root 0 Nov 3 15:36 ..
lrwxrwxrwx 1 root root 0 Nov 3 15:43 dm-0 -> ../devices/virtual/block/dm-0
lrwxrwxrwx 1 root root 0 Nov 3 15:43 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx 1 root root 0 Nov 3 15:43 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx 1 root root 0 Nov 3 15:43 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx 1 root root 0 Nov 3 15:43 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx 1 root root 0 Nov 3 15:36 mmcblk0 -> ../devices/13540000.dwmmc0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
lrwxrwxrwx 1 root root 0 Nov 3 15:43 mmcblk0boot0 -> ../devices/13540000.dwmmc0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0boot0
lrwxrwxrwx 1 root root 0 Nov 3 15:43 mmcblk0boot1 -> ../devices/13540000.dwmmc0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0boot1
lrwxrwxrwx 1 root root 0 Nov 3 15:43 mmcblk0rpmb -> ../devices/13540000.dwmmc0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0rpmb
lrwxrwxrwx 1 root root 0 Nov 3 15:43 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx 1 root root 0 Nov 3 15:43 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx 1 root root 0 Nov 3 15:36 zram0 -> ../devices/virtual/block/zram0
[Samsung Gear S3] adfree:
Memo to me... Kernel related...

sh-3.2# /home/developer/dtbtool --help
DTB combiner:
dtbTool [options] -o <output file> <input DTB path>
options:
--output-file/-o output file
--dtc-path/-p path to dtc
--page-size/-s page size in bytes
--verbose/-v verbose
--help/-h this help screen
sh-3.2# /home/developer/mkdzimage --help
usage: /home/developer/mkdzimage [-okda]
-o output filename
-k kernel filename
-d device tree filename
-a atags address

Best Regards
[Samsung Gear S3] RICARDOIO:
Estoy muy perdido...tengo un s3 frontier de emiratos arabes y se actualizo y perdio todos los sensores... en el sat no pueden arreglarlo en garantia pues no les sale la numeracion y para colmo ni en la web donde se compro ni en samsung se hacen responsables de nada... estoy asi rom R760NDAAXSG original de las pegatinas
[Samsung Gear S3] wolfcat90:
I dont want HW1 hahah

I love the G3 appearance, it looks elegant for me.
[Samsung Gear S3] Connor McSwaggins:
Has any progress been made on this? I recently got a gear s3 and love it to death, but tizen is limited and my lg g watch before this makes me wish I still had it instead, android wear was just way better at voice commands and had more apps, even compared to now vs what, 4 years ago or so when the g watch was released? Im really interested in this and if anyone can help catch me up through this thread that would be much appreciated! :D
[Samsung Gear S3] nuclearwaste:
Request/Question

Will it be possible to port AW apps to Tizen? I ask because I didn't research yet the architectures (sorry).

I never tried AW, but I don't dislike Tizen. All I wanted was to install Google Fit on Gear S3. (edit: I understand this can be quite hard, and maybe app specific due to hardware interactions)

I'm tech educated but I lack experience, where should I start to contribute?
[Samsung Gear S3] adfree:
Memo to me...

because still unsolved... unfinished...

Btw.

Thanks for soooooo much help...

dtbtool s h it and mkdzimage crap seems known also in Adnroid world... hey "surprice"... :rolleyes:

https://github.com/xiaolu/mkbootimg_tools

Still I have only found files running on my SM-R760... not on my 64 bit Ubuntu blabla 16 crap s hi t...

On my older Ubuntu installation where Z3 Kernel proper compiled...

Anyway...

Want to find working sh it ...

v1.

http://nyx.skku.ac.kr/wp-content/uploads/2016/03/Lecture3_연장.pdf

system-tools-0.0.1-1.1.i586.rpm

Attached and unziped to CPIO crap...

v2... no idea from where...

https://github.com/ne0z/tizen_system_tools

Will check on my Ubuntu and report...

No idea if Gear S3 require newer version...

Best Regards

Edit 1.

v1 and v2 1:1 same...

Edit 2.

No idea if newer Version required... but v4 with 64 bit + Source... added...

Found here:

http://download.tizen.org/snapshots...ages/x86_64/system-tools-0.0.1-1.2.x86_64.rpm

http://download.tizen.org/snapshots...ages/x86_64/system-tools-0.0.1-1.2.x86_64.rpm

http://download.tizen.org/snapshots...wayland/source/system-tools-0.0.1-1.2.src.rpm

system-tools-0.0.1-1.2.x86_64.rpm
system-tools-0.0.1-1.2.src.rpm
[Samsung Gear S3] adfree:
SYSMAP System.map
OBJCOPY arch/arm64/boot/Image
DTB combiner:
Input directory: 'arch/arm64/boot/dts/'
Output file: 'arch/arm64/boot/merged-dtb'
Found file: exynos7270-tizen_solis-r08.dtb ...
chipset: 0x7270, platform: 8, rev: 0
Found file: exynos7270-tizen_solis-r05.dtb ...
chipset: 0x7270, platform: 5, rev: 0
Found file: exynos7270-tizen_solis-r06.dtb ...
chipset: 0x7270, platform: 6, rev: 0
Found file: exynos7270-tizen_solis-r11.dtb ...
chipset: 0x7270, platform: 11, rev: 0
Found file: exynos7270-tizen_solis-r03.dtb ...
chipset: 0x7270, platform: 3, rev: 0
Found file: exynos7270-tizen_solis-r04.dtb ...
chipset: 0x7270, platform: 4, rev: 0
Found file: exynos7270-tizen_solis-r10.dtb ...
chipset: 0x7270, platform: 10, rev: 0
Found file: exynos7270-tizen_solis-r13.dtb ...
chipset: 0x7270, platform: 13, rev: 0
Found file: exynos7270-tizen_solis-r09.dtb ...
chipset: 0x7270, platform: 9, rev: 0
Found file: exynos7270-tizen_solis-r12.dtb ...
chipset: 0x7270, platform: 12, rev: 0
Found file: exynos7270-tizen_solis-r07.dtb ...
chipset: 0x7270, platform: 7, rev: 0
=> Found 11 unique DTB(s)
Start EXYNOS magic, version DTB...
Generating master DTB...
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r03.dtb' - 77824 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r04.dtb' - 77824 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r05.dtb' - 79872 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r06.dtb' - 79872 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r07.dtb' - 81920 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r08.dtb' - 79872 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r09.dtb' - 81920 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r10.dtb' - 81920 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r11.dtb' - 81920 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r12.dtb' - 81920 bytes)
(writing 'arch/arm64/boot/dts/exynos7270-tizen_solis-r13.dtb' - 81920 bytes)
Total wrote 888832 bytes
completed
out_name[arch/arm64/boot/dzImage]
kern_name[arch/arm64/boot/Image]
dt_name[arch/arm64/boot/merged-dtb]

Seems the reason was really I have only found the 32 bit files...

Now with 64 bit Version more success...

Need to check if valid...

Best Regards
[Samsung Gear S3] DQEight:
Maybe we can contact the folks who've ported android wear in the past to Samsung watches? Whoever did the gear 2 and Gear S( curved) ports?
[Samsung Gear S3] adfree:
[MENTION=5317855]DQEight[/MENTION]

Feel free to contact them.

Any help or progress is welcome.

Leider werde ich wohl auch weiterhin als Alleinunterhalter hier rumgeistern...

Best Regards

P.S.:

My second compiled Eng Kernel (based on CQL1 Source) is also working in my SM-R760...

So I can confirm 2 possible ways... to have valid dzImage...

A.

With sripts... additional manually way...

./scripts/exynos_dtbtool.sh -o arch/arm64/boot/merged-dtb -p scripts/dtc/ -v arch/arm64/boot/dts/
./scripts/exynos_mkdzimage.sh -o arch/arm64/boot/dzImage -k arch/arm64/boot/Image -d arch/arm64/boot/merged-dtb

B.

With Binaries... for instance 64 bit variant... here mkdzimage and dtbtool inside:

system-tools-0.0.1-1.2.x86_64.rpm

So damn script can run fully from start to end... :rolleyes:

Without additional interaction... :rolleyes: :rolleyes:

./release_obs.sh usr tizen_solis

or

./release_obs.sh eng tizen_solis
[Samsung Gear S3] adfree:
https://www.file-upload.net/downloa...originalSource4Tizen_smR600andSMr760.zip.html

Can somebody help me to compile this Linaro Toolchain/Compiler from SM-R760/SM-R600 source?

Thanx in advance.

Meanwhile I will try to manage to compile SM-R800 source..

SM-R800 ARH3 shows:

gcc version 6.2.1 20161213 (Linaro GCC Snapshot 6.2-2016.12

Will try first attempt with this Version:

https://releases.linaro.org/components/toolchain/binaries/6.2-2016.11/aarch64-linux-gnu/

Maybe with this Command...

./release.sh galileo large

Best Regards
[Samsung Gear S3] yariksychov:
Hi [MENTION=1030585]adfree[/MENTION],

First of all, thanks for your help with the Galaxy watch earlier this week, much appreciated.

It's obvious that this thread is the most popular on gear S3 forum with more than 200k views and tons of passive readers. It also seems like you're the only one who pulls this tremendously difficult mission to get through the source code of tizen.

Is there a chance we could help as a community? I'm sure there's tons of people who would like to participate in one way or another.

Thanks
[Samsung Gear S3] adfree:
Summary Kernel build related...

http://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/aarch64-linux-gnu/

gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz

Source	successfully build	tested on device
Tizen 3
R760XXU2CQL1	SM-R760_Opensource.zip	yes	on my SM-R760

Tizen 2.3
R765KOU1APJG,
R765AUCU1APJ8,
R765TUVU1APJ9,
R760XXU1APJF,
R770XXU1APJF	SM-R765_Opensource.zip	yes	no, because Rollback Prevention...

Tizen 3
R600XXU1AQI6	SM-R600_Opensource.zip	yes	no, I have no device

Tizen 3
R600XXU1AQK4	SM-R600_Opensource.zip	yes	no, I have no device

User and Engineer Kernel...

SM-R760 (SM-R770)

./release_obs.sh usr tizen_solis
./release_obs.sh eng tizen_solis

SM-R600

./release_obs.sh usr tizen_pop
./release_obs.sh eng tizen_pop

Tested on 64 bit Ubuntu... 16.04 LTS

64 bit version of dtbtool and mkdzimage files can be found in:

https://xdaforums.com/showpost.php?p=78236313&postcount=656

Original filename

system-tools-0.0.1-1.2.x86_64.rpm

But I have extract from rpm... to cpio to ...

v4_FU.zip :D

I have simple copied with sudo Command...

Best Regards
[Samsung Gear S3] Patrice05:
Hi,

the install.bat included in the windows version is nearly empty, only an "echo off" command, I suppose there is somethink missing ;)
[Samsung Gear S3] adfree:
:confused:

Sorry, no idea... what where?

I have no idea which files from where you could mean? :o

Best Regards
[Samsung Gear S3] jeebspawnshop:
Details for 165.213.148.120

IP:	165.213.148.120

Decimal:	2782237816

Hostname:	165.213.148.120

ASN:	6619

ISP:	SamsungSDS

Organization:	SamsungSDS

Services:	None detected

Assignment:	Static IP

Continent:	Asia

Country:	Republic of Korea kr flag

Latitude:	37.5112 (37° 30′ 40.32″ N)

Longitude:	126.9741 (126° 58′ 26.76″ E)

:eek:
[Samsung Gear S3] highaltitude:
What's the current status? Are things still getting ironed out? Stable rooted rom yet? Is there a way to back up in order to restore to fully functional stock?
[Samsung Gear S3] adfree:
Still I wish I would understand the Qemu s h... to use exact the same Toolchain...

Memo to me...

https://wiki.tizen.org/OSDev/qemu-accel

...

Meanwhile I am trying to compile few other Tizen Retail Kernel... for some """exercise"""...

Best Regards

Edit 1.

More Links about "magic" Qemu:

https://wiki.tizen.org/Tizen_ARM64_Development

https://download.tizen.org/releases..._64/succeeded/qemu-accel-aarch64.buildlog.txt

https://wiki.tizen.org/Tizen_4.0_GBS_Local_Fullbuild_Guide_for_TM1

:cyclops:

If I see this... my tiny Windows Fanboy Brain explode... :eek:
[Samsung Gear S3] adfree:
Because it is so f boring... and my SM-R760 allready dripped Knox...

Warranty Void Value is...

I will try what happens with Tizen 5 Image from here:

https://download.tizen.org/prerelea.../images/standard/wearable-wayland-armv7l-tw2/

tizen-5.0-unified_20181218.2.20181221.015253_wearable-wayland-armv7l-tw2.tar.gz

More as my SM-R760 will explode... :D

I will post result...

Best Regards

P.S.:

I did something simila rlong time ago with my SM-R732... with Tizen 3 and 4...

And lost WiFi...

But was able to find the missing parts.

Please not try without USB cable...
[Samsung Gear S3] adfree:
Tizen 5 "work" on my SM-R760...

WiFi, BT and Download Wireless is deactivated... like I know since RD-PQ... SM-R732... :rolleyes:

https://xdaforums.com/showpost.php?p=72480651&postcount=165

Hints for missing WiFi files:

https://xdaforums.com/showpost.php?p=72567943&postcount=173

I need to make USB connection... to fix my tiny problems...: D :o :rolleyes:

Meanwhile I have realized... :rolleyes:

Tizen 5.5 in Unified folder...

:rolleyes: :rolleyes:

https://download.tizen.org/prerelea.../images/standard/wearable-wayland-armv7l-tw2/

https://download.tizen.org/prerelea.../images/standard/wearable-wayland-armv7l-tw3/

If I fix my SM-R760... I can flash magic Tizen 5.5... :rolleyes:

I will check what is inside tw3... maybe this is Galaxy Watch series SM-R8...

Best Regards

Edit 1.

:confused:

Sorry, wrong conclusion...

<model-config version="5.5" model="tw3">
<platform>
<key name="tizen.org/system/model_name" type="string">TW3</key>
<key name="tizen.org/system/platform.name" type="string">Tizen</key>
<key name="tizen.org/feature/platform.version" type="string">5.5</key>
<key name="tizen.org/system/platform.processor" type="string">[B]exynos7270[/B]</key>

tw3 is also Exynos 7270... maybe they are doing fun for SM-R600 too :confused: :confused:

About my SM-R760...

Battery Charging seems work... if booting complete... so I can reach 100 %...

short tried before in power off mode... nothing moved... I saw only the Flash symbol...

I was on Combination Firmware FT30 CQL1 before I flashed Tizen 5...
[Samsung Gear S3] adfree:
:rolleyes:

I am back at this tiny problem...

https://xdaforums.com/showpost.php?p=76558349&postcount=64

https://xdaforums.com/showpost.php?p=76633219&postcount=70

My """construction""" is not very stable to do long time tests... I am scared also to flash full firmware...

I have to hold cable in 1 hand and in the other the SM-R760... :eek:

So I will try to find more stable solution... so I have my hands free...

Need to prepare few things...

1.

Tizen 5 Test Firmware contains:

dzImage
dzImage-recovery
ramdisk.img
ramdisk-recovery.img
rootfs.img
system-data.img
user.img

7 files...

So maybe I will create """Emergency Rescue Repair""" TAR... with less files to have again working:

Download wireless

To minimize risk to kill device if full firmware flash fail... Bootloader PIT etc...

Hmmmm...

First attempt could be 1 file:

ramdisk-recovery.img

If fail because Kernel not compatible... then second attempt could be:

dzImage-recovery
ramdisk-recovery.img

Btw...

Somebody realized that 2 Kernels are similar... except RSA Signature at end of file...

dzImage
dzImage-recovery

Best Regards
[Samsung Gear S3] yariksychov:
Let us know if you need anything
[Samsung Gear S3] adfree:
My repair attempt v1.. with ramdisk-recovery.img only...

Result later...

Edit 1.

:cool: :good:

Success.

Then I was able to use again netOdin to flash full FT30 CQL1.

So Download wireless worked again. :good:

Conclusion (theory)

If I remove for my next Flash attempt ramdisk-recovery.img from Tizen 5.5 package...

tizen-unified_20181218.2.20181221.023957_wearable-wayland-armv7l-tw2.tar.gz

-

ramdisk-recovery.img

Then in theory my Download wireless/netOdin should be still alive...

I will test my theory. :D

Soon... (this year 2018... in few minutes...)

For SDB Tool and other action I need more time...

I have with few screws and some tiny parts bigger POGO Connector... and shielded against my fat wet fingers... to prevent short circuit...

But damn... to hold SM-R760 and press POGO inside watch... AND then hold under same pressure without destroy hardware... :eek: :o

ANNNNND then move Cursor to start Odin... :cyclops:

So I was very lucky to hold only few seconds. :cowboy:

Edit 2.

Tizen 5.5 runs on my SM-R760 :cool: :good:

But no real visible "magic" for normal user...

No apps no WiFi etc...

Download wireless seems to work... not fully tested... but I can activate...
[Samsung Gear S3] adfree:
With few more screws... older parts and old Board...

I was able to make fixture for my POGO connection... it is still far away from perfect...

But I was able to hold in 1 hand... and so I can type with the other hand. :D

Instead hold with both hands.

1.

I am still using my SDB 2.2.60. :D :cool: :good:

2.

Short I saw MTP is installed + activated...

So I see folders in Windows Explorer :good: :good:

This can later help to transfer files... without SDB...

3.

Now I need collection of Commands to try...

As I use other Notebook... with Windows Vista and without Internet... :rolleyes:

My Todo list...

A
Screenshots

B
Check if remount work for rootfs.img

C
Check if I have access to 1 more partition... ;)

D
investigate if I can reset Warranty Void... :D

For A I hope this still work:

https://xdaforums.com/showpost.php?p=72553023&postcount=171

enlightenment_info -dump_topvwins /opt/usr/home/owner/media/Images

B

https://xdaforums.com/showpost.php?p=77358044&postcount=611

sh-3.2# [B]mount -o remount,rw /[/B]
mount: cannot remount /dev/root read-write, is write-protected

C

cat /proc/partitions

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

D

last, because dangerous to kill my SM-R760... :o

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

Backup... then in other direction... write...

Best Regards
[Samsung Gear S3] adfree:
MTP works fine...

So I can copy files via Windows Explorer. :good:

Screenshot seems different...

sh-3.2# [B]enlightenment_info -dump_screen[/B] /home/owner/media/Images
make dump: /tmp/dump_screen.png

It ignores my path... I know this from somewhere... :rolleyes:

I can also not change filename... :rolleyes: :rolleyes:

So it is again not sooo easy to make screenshots... as cp from /tmp needed... otherwise file will be overwritten

No idea how long I need to find better solution... :o

Attached are 3 Screenshots.

Task A is done...

B...

remount seems to work.

Short tested with mkdir in /bin folder with success

:cool: :good:

C.

Fail...

Like I know from all other Tizen Variants for SM-R760...

D.

Not tried yet...

Best Regards

Edit 1.

For Screenshots I can use this:

sdb shell enlightenment_info -dump_screen -p /home/owner/media/Images/ -n 1.png

So I have attached few more screenshots...

Edit 2.

In screenshot visible Editor... but if I select it I can see only Error... no idea for what this App is...

:confused:
[Samsung Gear S3] ChangeToTower:
Nice work, great progress! Keep that going :)
[Samsung Gear S3] adfree:
Found via Google search for:

enlightenment_info dump_screen

https://build.tizen.org/package/vie...expand=1&rev=dc3d4c0204234e246cc4f08f0c060ced

Aha... seems my fault as Windows Fanboy...

Parameter -p and -n seems possible for path and filename... will test... soon.

Best Regards
[Samsung Gear S3] adfree:
Maybe soon I am drunken enough to test Knox Reset... :D

To have again:

Warranty Void 0 (0x0000)

Theory looks like this...

sh-3.2# echo 0 > /sys/block/mmcblk0boot0/force_ro
sh-3.2# dd if=/opt/usr/media/Music/mmcblk0boot0.bin of=/dev/mmcblk0boot0
8192+0 records in
8192+0 records out
4194304 bytes (4.2 MB) copied, 0.456286 s, 9.2 MB/s

Output is from older attempts with my SM-R760... with Retail and Combination Firmwares...

With no effect... :o

Maybe more luck with Development Images for Tizen 3 or 4 or 5 or 5.5... :angel:

I have Backup (dd dump) from mmcblk0boot0. where Knox is not dripped...

If my SM-R760 will survive...

I will try to integrate WiFi in Tizen 5.5...

Best Regards

Edit 1.

No luck with Tizen 5.5...

So I have checked my HDDs for older Images... maybe more luck with Tizen 3 from 2017...

Image/Filename	Tested with my SM-R760	KNOX RESET possible?

Tizen 3
tizen-wearable_20170403.2.20170404.044936_wearable-wayland-armv7l-tw2.tar.gz	Yes work

Tizen 3
tizen-wearable_20170413.1_wearable-wayland-armv7l-tw2.tar.gz

Tizen 4
tizen-unified_20170830.2.20170901.191411_wearable-wayland-armv7l-tw2.tar.gz

Tizen 4
tizen-4.0-unified_20171228.1.20171229.060354_wearable-wayland-armv7l-tw2.tar.gz

Tizen 5
tizen-5.0-unified_20181218.2.20181221.015253_wearable-wayland-armv7l-tw2.tar.gz	Yes work

Tizen 5.5
tizen-unified_20181218.2.20181221.023957_wearable-wayland-armv7l-tw2.tar.gz	Yes work	Tested, [COLOR="Red"][B]NO[/B][/COLOR]

NO means with "my" Commands... maybe obsolete in newer Exynos...

Maybe I need to Google for Triangle away "compatibility list...

https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&hl=de

Hmmmmmm... seems from 2014...

Hmmmmmmmmmmmmmm...

I can see posts about Efuse blabla...

But why I can not write to mmcblk0boot0?

I mean SM-R760 can write to this partition... first few Bytes are sboot.bin Bootloader...

So it is not write protected at all...

Edit 2.

I have flashed successfully old Tizen 3 Dev Image... need some time to check my Knox theory...
[Samsung Gear S3] RohanKalra97:
OMG we are so close

Thank you [MENTION=1030585]adfree[/MENTION] for doing this <3