yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S3] adfree:
sh-3.2# pitread
2018-09-01 08:55:46 [I] wd_pit_init: 0x22
2018-09-01 08:55:46 [I] wd_pit_init: Magic: 0x12349876
2018-09-01 08:55:46 [I] wd_pit_init: Count: 18
2018-09-01 08:55:46 [I] Magic: 0x12349876, Model: LSI7270, Count: 18

2018-09-01 08:55:46 [I] 00 [80] BOOTLOADER sboot.bin 0x0 + 0x1000 0 + 2097152
2018-09-01 08:55:46 [I] 01 [70] PIT 0x22 + 0x10 17408 + 8192
2018-09-01 08:55:46 [I] 02 [71] MD5HDR md5.img 0x32 + 0x1fce 25600 + 4168704
2018-09-01 08:55:46 [I] 03 [01] TUP 0x2000 + 0x10000 4194304 + 33554432
2018-09-01 08:55:46 [I] 04 [02] CSA csa.img 0x12000 + 0x4000 37748736 + 8388608
2018-09-01 08:55:46 [I] 05 [03] CPNVCORE cpnvcore.img 0x16000 + 0x1000 46137344 + 2097152
2018-09-01 08:55:46 [I] 06 [04] RAMDISK2 ramdisk-recovery.img 0x17000 + 0xa000 48234496 + 20971520
2018-09-01 08:55:46 [I] 07 [05] RAMDISK1 ramdisk.img 0x21000 + 0x4000 69206016 + 8388608
2018-09-01 08:55:46 [I] 08 [06] PARAM param.bin 0x25000 + 0x4000 77594624 + 8388608
2018-09-01 08:55:46 [I] 09 [07] CM cm.bin 0x29000 + 0x1800 85983232 + 3145728
2018-09-01 08:55:46 [I] 10 [08] BOOT dzImage 0x2a800 + 0x8000 89128960 + 16777216
2018-09-01 08:55:46 [I] 11 [09] RECOVERY dzImage-recovery 0x32800 + 0x8000 105906176 + 16777216
2018-09-01 08:55:46 [I] 12 [10] MODULE modules.img 0x3a800 + 0x8000 122683392 + 16777216
2018-09-01 08:55:46 [I] 13 [11] CSC csc.img 0x42800 + 0x5f000 139460608 + 199229440
2018-09-01 08:55:46 [I] 14 [12] SYSTEM-DATA system-data.img 0xa1800 + 0x4f000 338690048 + 165675008
2018-09-01 08:55:46 [I] 15 [13] USER user.img 0xf0800 + 0x3c9800 504365056 + 2033188864
2018-09-01 08:55:46 [I] 16 [14] ROOTFS rootfs.img 0x4ba000 + 0x28d000 2537553920 + 1369440256
2018-09-01 08:55:46 [I] 17 [15] STEADY - 0x747000 + 0x200 3906994176 + 262144
crashed [1535759746] processname=pitread, pid=2991, tid=2991, signal=11[sys-assert] can't find symtab
Segmentation fault (core dumped)

Maybe usefull... in combination with mmcdump Command...

I am using for 160 MB dump from start address of eMMC:

mmcdump 0x0 0x50000 160MBdump.bin

For investigation I can open this Image with WinHex... and ectract partitions...

I will later add screenshots... and add few infos...

Best Regards

Edit 1.

sh-3.2# mmcdump 0x0 0x50000 160MBdump.bin
blkstart: 0x0 (0), blksize: 0x50000 (167772160)
Out: /opt/usr/media/mmcdump/160MBdump.bin
[Samsung Gear S3] adfree:
sh-3.2# cat /proc/partitions
major minor #blocks name

7 0 13888 loop0
7 1 320 loop1
254 0 285988 zram0
179 0 3817472 mmcblk0
179 1 32768 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 20480 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 3072 mmcblk0p7
259 0 16384 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 16384 mmcblk0p10
259 3 194560 mmcblk0p11
259 4 161792 mmcblk0p12
259 5 1985536 mmcblk0p13
259 6 1337344 mmcblk0p14
259 7 256 mmcblk0p15
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1280000 dm-0

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.00241558 s, 0.0 kB/s

sh-3.2# dd if=/dev/dm-0 of=/home/owner/media/Others/dm0.bin
2560000+0 records in
2560000+0 records out
1310720000 bytes (1.3 GB) copied, 94.3551 s, 13.9 MB/s
sh-3.2# dd if=/dev/loop0 of=/home/owner/media/Others/loop0.bin
640+0 records in
640+0 records out
327680 bytes (328 kB) copied, 0.0265223 s, 12.4 MB/s
sh-3.2# dd if=/dev/loop1 of=/home/owner/media/Others/loop1.bin
27776+0 records in
27776+0 records out
14221312 bytes (14 MB) copied, 0.651573 s, 21.8 MB/s
sh-3.2# dd if=/dev/zram0 of=/home/owner/media/Others/zram0.bin
571976+0 records in
571976+0 records out
292851712 bytes (293 MB) copied, 11.4966 s, 25.5 MB/s

Since Tizen 3 I see dm-o ?

1300 MB...

:confused:

Will check if this is rootfs.img again...

:confused: :confused:
[Samsung Gear S3] adfree:
Yep.

dm-0 is rootfs.img without dm-verity... :D

Btw...

So I could use text string dm-verity to find end of rootfs.img... instead Offset..

https://xdaforums.com/showpost.php?p=76696355&postcount=548

I am at the moment at FT30 CRB1...

But battery Charging still s u x x X... :mad:

Also downgrade seems not fix this s h i ... how they broke battery management since Tizen 3.

I saw this f. not charging to 100 % also in BQC2...

:confused: :confused: :mad:

But this happens not to me... as I can remember BEFORE this Tizen 3 shi... :cyclops:

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

http://opensource.samsung.com/

No idea why and wheen...

But Samsung uploaded Source Code of CQL1... Tizen 3... :cyclops:

Only as info.

As we have so many Kernel DeveloperS... :D :o :( :crying:

Best Regards
[Samsung Gear S3] abumaha:
second link error
[Samsung Gear S3] adfree:
[MENTION=4378052]abumaha[/MENTION]

Thanx for info.

I hae tried... and got short Error 550 on first file...

After second attempt success... I have downloaded successfully.

So maybe temporary problem...

Please try again.

Best Regards
[Samsung Gear S3] abumaha:
still get error 410
[Samsung Gear S3] Leon_only_one:
Hello, I am sorry to ask this, because probably somebody already ask this, but is they some instructions on how to do this on SM-R760, with links on what I need to download (because I am new to this). Step by step would be perfect. If somebody could help :)

Sorry wrong thred, ignore this
[Samsung Gear S3] adfree:
https://www.sciencedirect.com/science/article/pii/S1742287618300409

Found interesting article param related...

Index	Name	Example setting
0	REBOOT_MODE	0
1	SWITCH_SEL	3
2	DEBUG_LEVEL	18505
3	SUD_MODE	0
4	DN_ERROR	0
5	CHECKSUM	3
6	ODIN_DOWNLOAD	1
7	SALES_CODE	0
8	SECURITY_MODE	1526595585
9	NORMAL_BOOT	0
10	CP_DEBUG_LEVEL	22015
11	USERBOOT_MODE	0
12	DIAG_MODE	0
13	CHARGING_MODE	48
14	INT_RSVD14	0
15	LCD_RES	1
16	CMDLINE	console = ram loglevel = 4
17	BARCODE_INFO	(null)
18	KEEP_LOG	(null)

.

.

.

Name	Value
REBOOT_MODE_NONE	0
REBOOT_MODE_DOWNLOAD	1
REBOOT_MODE_UPLOAD	2
REBOOT_MODE_CHARGING	3
REBOOT_MODE_RECOVERY	4
REBOOT_MODE_FOTA	5
REBOOT_MODE_FOTA_BL	6
REBOOT_MODE_SECURE	7
REBOOT_MODE_FWUP	9
REBOOT_MODE_EM_FUSE	10

Best Regards

Edit 1.

Found in CQL1 Tizen 3 Source Code...

#define REBOOT_MODE_PREFIX 0x12345670
#define REBOOT_MODE_NONE 0x0
#define REBOOT_MODE_DOWNLOAD 0x1
#define REBOOT_MODE_UPLOAD 0x2
#define REBOOT_MODE_CHARGING 0x3
#define REBOOT_MODE_RECOVERY 0x4
#define REBOOT_MODE_FOTA 0x5
#define REBOOT_MODE_FOTA_BL 0x6 /* update bootloader */
#define REBOOT_MODE_SECURE 0x7 /* image secure check fail */
#define REBOOT_MODE_NORMAL 0x8 /* Normal reboot */
#define REBOOT_MODE_FWUP 0x9 /* emergency firmware update */
#define REBOOT_MODE_SILENT 0xA /* silent reboot */
#define REBOOT_MODE_WDOWNLOAD 0xB /* wireless-download */
#define REBOOT_MODE_WUPLOAD 0xC /* wireless-upload */
#define REBOOT_MODE_WDOWNLOAD_UPDATE 0xD /* wireless-download update binary */

#define REBOOT_MODE_POW_PREFIX 0xaec80000 /*poweroff watch prefix*/
#define REBOOT_MODE_FACTORY_COMMAND 0x12345611
#define REBOOT_MODE_WDOWNLOAD_RW_UPDATE 0x12345612

#define REBOOT_SET_PREFIX 0xabc00000
#define REBOOT_SET_SALES_CODE 0x000a0000
#define REBOOT_SET_LCD_RES 0x000b0000
#define REBOOT_SET_DEBUG 0x000d0000
#define REBOOT_SET_SWSEL 0x000e0000
#define REBOOT_SET_SUD 0x000f0000

#define REBOOT_SALES_CODE_BASE_PHYS (0x40000000)
#define REBOOT_SALES_CODE_MAGIC_ADDR (phys_to_virt(REBOOT_SALES_CODE_BASE_PHYS))
#define REBOOT_SALES_CODE_ADDR (phys_to_virt(REBOOT_SALES_CODE_BASE_PHYS+4))

static void sec_reboot(char str, const char *cmd)
{

in file sec_reboot.c
[Samsung Gear S3] adfree:
:confused:

Hmmm... need time to test...

I have forgotten my Ubuntu Password... :D :rolleyes:

In SM-R8xx Source I found 4 files...

release.sh
release_obs.sh

obs blabla is also since first Source inside ... I mean first Gear S3 Source...

#!/bin/bash
#
JOBS=`grep -c processor /proc/cpuinfo`
let JOBS=${JOBS}*2
JOBS="-j${JOBS}"
ARM=arm64
BOOT_PATH="arch/${ARM}/boot"
IMAGE="Image"
DZIMAGE="dzImage"

CHIPSET=exynos7270
RELEASE=${1}
MODEL=${2}
CARRIER=${3}
REGION=${4}
OPERATOR=${5}
SHOWCASE=${6}
VARIANT="${MODEL}"

if [ "${CARRIER}" != "" ]; then
VARIANT="${VARIANT}_${CARRIER}"
fi
if [ "${REGION}" != "" ]; then
VARIANT="${VARIANT}_${REGION}"
fi
if [ "${OPERATOR}" != "" ]; then
VARIANT="${VARIANT}_${OPERATOR}"
fi

if [ "${VARIANT}" == "${MODEL}" ]; then
echo "base_def : ${MODEL}_defconfig , Release : ${RELEASE}"
else
echo "base_def : ${MODEL}_defconfig , variant_def : ${VARIANT}_defconfig, Release : ${RELEASE}"
fi

if [ "${RELEASE}" = "usr" ]; then
echo "Now disable CONFIG_TIZEN_SEC_KERNEL_ENG for ${MODEL}_defconfig"

sed -i 's/CONFIG_TIZEN_SEC_KERNEL_ENG=y/\# CONFIG_TIZEN_SEC_KERNEL_ENG is not set/g' arch/${ARM}/configs/${MODEL}_defconfig
if [ "$?" != "0" ]; then
echo "Failed to disable CONFIG_TIZEN_SEC_KERNEL_ENG feature"
exit 1
fi

echo "Now disable CONFIG_DYNAMIC_DEBUG for ${MODEL}_defconfig"

sed -i 's/CONFIG_DYNAMIC_DEBUG=y/\# CONFIG_DYNAMIC_DEBUG is not set/g' arch/${ARM}/configs/${MODEL}_defconfig
if [ "$?" != "0" ]; then
echo "Failed to disable CONFIG_DYNAMIC_DEBUG feature"
exit 1
fi
fi

if [ "${SHOWCASE}" = "ifa" ]; then
echo "Now enable Showcase config for ${MODEL}_defconfig"

sed -i 's/\# CONFIG_IFA_DEMO is not set/CONFIG_IFA_DEMO=y/g' arch/${ARM}/configs/${MODEL}_defconfig
if [ "$?" != "0" ]; then
echo "Failed to enable CONFIG_IFA_DEMO feature"
exit 1
fi
fi

if [ "${VARIANT}" == "${MODEL}" ]; then
make ARCH=${ARM} ${MODEL}_defconfig
else
make ARCH=${ARM} ${MODEL}_defconfig VARIANT_DEFCONFIG=${VARIANT}_defconfig
fi

if [ "$?" != "0" ]; then
echo "Failed to make defconfig :"${ARCH}
exit 1
fi

rm ${BOOT_PATH}/dts/*.dtb -f

make ${JOBS} ARCH=${ARM} ${IMAGE}
if [ "$?" != "0" ]; then
echo "Failed to make "${IMAGE}
exit 1
fi

DTC_PATH="scripts/dtc/"

dtbtool -o ${BOOT_PATH}/merged-dtb -p ${DTC_PATH} -v ${BOOT_PATH}/dts/
if [ "$?" != "0" ]; then
echo "Failed to make merged-dtb"
exit 1
fi

mkdzimage -o ${BOOT_PATH}/${DZIMAGE} -k ${BOOT_PATH}/${IMAGE} -d ${BOOT_PATH}/merged-dtb
if [ "$?" != "0" ]; then
echo "Failed to make mkdzImage"
exit 1
fi

:silly:

Only as info...

Need time to check if this leads to something...

Best Regards
[Samsung Gear S3] adfree:
memo to me... Kernel related...

Tizen 2.3 later...

BQC2 FTMA--gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.02.2015.2.slp

Tizen 3...

SM-R760

CQK2 FT30-----gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)
CQK3----------gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)
CQL1----------gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)
CQL1 FT30-----gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)
CQL2 FT30-----gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)
CRB1 FT30-----gcc version 4.9.2 20151028 (prerelease) (Tizen/Linaro)

SM-R600 because same Chip...

https://gethypoxic.com/blogs/technical/samsung-gear-sport-teardown

SM-Z300F
Z300FXXU1BPI4
gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.02.2019.18.slp

SM-R360
gcc version 4.6 (Linaro GCC 4.6-2013.05

SM-R732
R732XXU2EQJ2
gcc version 4.6 (Linaro GCC 4.6-2013.05

Tizen 4 or 5 ?? Unified cr.p
tizen-unified_20180724.3.20180725.233100_wearable-wayland-armv7l-tw2.tar
gcc version 6.2.1 20161213 (Tizen/Linaro GCC 6.2.1 2016.12

Edit 1.

At the moment I am using this Version to compile self...

gcc version 4.9.4 (Linaro GCC 4.9-2017.01

Edit 2.

SM-R800 ARH3

gcc version 6.2.1 20161213 (Linaro GCC Snapshot 6.2-2016.12

Edit 3.

tw2
(gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.06)

TM1 dzImage
(gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.06)

SM-Z200F
(gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.02.2015.6.slp)

BQC5 SM-R760
(gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.02.2015.2.slp)

SM-Z400F
(gcc version 4.9.2 (Tizen/Linaro GCC 4.9.2 2015.06)

Edit 4.

SM-Z130H older... Tizen 2.3...

gcc version 4.6.4 (Linaro GCC 4.6-2013.05

Edit 5.

TW2 Tizen 5

gcc version 6.2.1 20161213 (Tizen/Linaro GCC 6.2.1 2016.12)

TW2 Tizen 5.5

gcc version 6.2.1 20161213 (Tizen/Linaro GCC 6.2.1 2016.12)
[Samsung Gear S3] adfree:
I have limited time at the moment... :o

But "we" have progress Kernel related. :D :good: :cool:

To compile Tizen 3 Kernel from CQL1 Source Code...

This GCC Toolchain seems to work:

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

I mean Tizen Source Code from here...

http://opensource.samsung.com/reception.do

./release_obs.sh usr tizen_solis

This build User Kernel (dzImage) for SM-R760...

Also possible to create Engineer Kernel... no idea yet about the Pro and Contra... :o

./release_obs.sh eng tizen_solis

Maybe few infos missing...

But...

1.

Result is unsigned Kernel.

Tested on SM-R760 and working. :cowboy: :cool:

BUT...

2.

You need mandatory Engineer sboot.bin Bootloader...

For instance from Combination Firmware CQL1

Otherwise to risk tripp Knox... Warranty Void crap...

<ID:0/072> Added!!
<ID:0/072> Odin engine v(ID:3.1301)..
<ID:0/072> File analysis..
<ID:0/072> Total Binary size: 14 M
<ID:0/072> SetupConnection..
<ID:0/072> Initialzation..
<ID:0/072> Get PIT for mapping..
<ID:0/072> Firmware update start..
<ID:0/072> NAND Write Start!!
<ID:0/072> SingleDownload.
<ID:0/072> dzImage
<ID:0/072> FAIL! (Auth)
<ID:0/072>
<ID:0/072> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Reason is easy... no Signature from RSA2048 crap.

Anyway.

This is big big step forward. :cyclops:

Thank you very much for infos and trying. ;)

Best Regards
[Samsung Gear S3] bnickolas97:
SM-R765A: GH98-40543A (Has POGO Connections)

SM-R765T: GH98-40543A (Has POGO Connections)

SM-R765V: GH98-40543A (Has POGO Connections)

Hope this helps. Also [MENTION=1030585]adfree[/MENTION] Please PM me. I have some very interesting photos of my R765A and I would like to see how they can benefit the project! :D:D:D

---------- Post added at 06:13 AM ---------- Previous post was at 06:09 AM ----------

SM-R765A: GH98-40543A (Has POGO Connections)

SM-R765T: GH98-40543A (Has POGO Connections)

SM-R765V: GH98-40543A (Has POGO Connections)

Hope this helps. Also [MENTION=1030585]adfree[/MENTION] Please PM me. I have some very interesting photos of my R765A and I would like to see how they can benefit the project! :D:D:D
[Samsung Gear S3] adfree:
Linux arrrrrrrgGGGGGGGGGGGGGGGGGGGGGgggHHHHHHHHHHHhh

http://nyx.skku.ac.kr/wp-content/uploads/2014/11/Tizen-porting-on-Odroid-U3.pdf

I will edit f&%ing makefile...

Edit 1.

According to hte info from PDF...

I have edit my make file...

1 major difference... we play with arm64...

Now Computer doing something...
[Samsung Gear S3] adfree:
LD drivers/video/fbdev/core/built-in.o
CC drivers/video/fbdev/exynos/decon_7570/decon_core.o
CC drivers/video/fbdev/exynos/decon_7570/decon-int_drv.o
CC drivers/video/fbdev/exynos/decon_7570/decon_helper.o
CC drivers/video/fbdev/exynos/decon_7570/decon_reg_7570.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w1x01_mipi_lcd.o
LD drivers/video/fbdev/exynos/decon_7570/dsim.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w1x01_lcd_ctrl.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w1x01_dimming.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w2x01_mipi_lcd.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w2x01_lcd_ctrl.o
CC drivers/video/fbdev/exynos/decon_7570/panels/s6e36w2x01_dimming.o
LD drivers/video/fbdev/exynos/decon_7570/decon.o
LD drivers/video/fbdev/exynos/decon_7570/panels/built-in.o
LD drivers/video/fbdev/exynos/decon_7570/built-in.o
LD drivers/video/fbdev/exynos/built-in.o
LD drivers/video/fbdev/built-in.o
LD drivers/video/built-in.o
LD drivers/built-in.o
LINK vmlinux
LD vmlinux.o
MODPOST vmlinux.o
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
KSYM .tmp_kallsyms1.o
KSYM .tmp_kallsyms2.o
LD vmlinux
SORTEX vmlinux
SYSMAP System.map
OBJCOPY arch/arm64/boot/Image
[B][COLOR="Red"]./release_obs.sh: Zeile 86: dtbtool: Befehl nicht gefunden
Failed to make merged-dtb[/COLOR][/B]

First success...

I have now zImage...

The other problem I will fix with other script folder...

I was told to that I can finish manually the final step to dzImage...

Best Regards
[Samsung Gear S3] adfree:
./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

Seems this is my missing part...

https://github.com/DrBrunkov/AW-exynos7270-kernel/commit/9add08441cdf140928549768e7bf5ef37a23ed4c

Best Regards
[Samsung Gear S3] adfree:
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_dtbtool.sh -o arch/arm64/boot/merged-dtb -p scripts/dtc/ -v arch/arm64/boot/dts/
DTB input path is 'arch/arm64/boot/dts'
output path is 'arch/arm64/boot', output file is 'merged-dtb'
page size is '2048'
*HEADER 16[B]
| PAD: 2032[B]
## OUT: merged-dtb size: 2048[B]; 2[KB]
arch/arm64/boot/merged-dtb (size: 2KB) is created.

step forward... :rolleyes:

ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_mkdzimage.sh -o arch/arm64/boot/dzImage -k arch/arm64/boot/Image -d arch/arm64/boot/merged-dtb
*HEADER 28[B]
| PAD: 2020[B]
*Image 14340624[B]
| PAD: 1520[B]
*merged-dtb 2048[B]
| PAD: 0[B]
## OUT: dzImage size: 14346240[B]; 14010[KB]

Edit 1.

F *U* :mad:
[Samsung Gear S3] adfree:
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ chmod a+x ./scripts/exynos_dtbtool.sh
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ chmod a+x ./scripts/exynos_mkdzimage.sh
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_dtbtool.sh -o arch/arm64/boot/merged-dtb -p scripts/dtc/ -v arch/arm64/boot/dts/
DTB input path is 'arch/arm64/boot/dts'
output path is 'arch/arm64/boot', output file is 'merged-dtb'
page size is '2048'
*HEADER 236[B]
| PAD: 1812[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r08.dtb 79755[B]
| PAD: 117[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r05.dtb 79511[B]
| PAD: 361[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r06.dtb 79743[B]
| PAD: 129[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r11.dtb 80635[B]
| PAD: 1285[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r03.dtb 77418[B]
| PAD: 406[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r04.dtb 77735[B]
| PAD: 89[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r10.dtb 80886[B]
| PAD: 1034[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r13.dtb 80811[B]
| PAD: 1109[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r09.dtb 80411[B]
| PAD: 1509[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r12.dtb 80811[B]
| PAD: 1109[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r07.dtb 79887[B]
| PAD: 2033[B]
## OUT: merged-dtb size: 888832[B]; 868[KB]
arch/arm64/boot/merged-dtb (size: 868KB) is created.
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_mkdzimage.sh -o arch/arm64/boot/dzImage -k arch/arm64/boot/Image -d arch/arm64/boot/merged-dtb
*HEADER 28[B]
| PAD: 2020[B]
*Image 14340624[B]
| PAD: 1520[B]
*merged-dtb 888832[B]
| PAD: 0[B]
## OUT: dzImage size: 15233024[B]; 14876[KB]

Maybe I have this time more luck...

Best Regards

Edit 1.

Added my result"s"...

Image is file 1

Build with Command:

./release_obs.sh usr tizen_solis

After some copy and paste action... I am simple copy folder script...

File 2 is merged-dtb, after command:

./scripts/exynos_dtbtool.sh -o arch/arm64/boot/merged-dtb -p scripts/dtc/ -v arch/arm64/boot/dts/

Now with last Command... file 1 + file 2 is merged... to final dzImage

./scripts/exynos_mkdzimage.sh -o arch/arm64/boot/dzImage -k arch/arm64/boot/Image -d arch/arm64/boot/merged-dtb

Additonal steps:

https://github.com/DrBrunkov/AW-exynos7270-kernel/commit/9add08441cdf140928549768e7bf5ef37a23ed4c

chmod a+x ./scripts/exynos_dtbtool.sh
chmod a+x ./scripts/exynos_mkdzimage.sh

Best Regards
[Samsung Gear S3] Ruuu:
Hey guys sorry to ask but is the development still going on or we can go ahead and flash the port on our gear S3?
[Samsung Gear S3] adfree:
No idea... maybe you expect toooooooo much magic... :D

Look at this post:

https://xdaforums.com/showpost.php?p=71755928&postcount=22

Now we can... better "we" could...

eventually:

1. Build a working custom TIZEN kernel

2. Build an Android kernel that boots up

3. Port over TWRP/enable ADB through recovery

4. Start working on Android Wear

:D :rolleyes:

Please remember """Porting""" is not so easy like Farting. :D

Best Regards
[Samsung Gear S3] adfree:
Memo to me...

For RPM install under Ubuntu... I need other Linux crap... :rolleyes:

sudo apt-get install alien

.

.

.

alien -i system-tools-0.0.1-1.1.i586.rpm

ubuntu64@ubuntu64:~/Downloads$ alien -i system-tools-0.0.1-1.1.i586.rpm
Must run as root to convert to deb format (or you may use fakeroot).

ubuntu64@ubuntu64:~/Downloads$ sudo alien -i system-tools-0.0.1-1.1.i586.rpm
system-tools-0.0.1-1.1.i586.rpm is for architecture i386 ; the package cannot be built on this system

:rolleyes:
[Samsung Gear S3] kisuak:
Any luck with porting?
[Samsung Gear S3] Dark Messiah:
Really? Please, just read the last posts...

Short answer: no
[Samsung Gear S3] adfree:
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./release_obs.sh eng tizen_solis
base_def : tizen_solis_defconfig , Release : eng
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
drivers/motor/Kconfig:1:warning: config symbol defined without type
arch/arm64/configs/tizen_solis_defconfig:2660:warning: override: reassigning to symbol SEC_DEBUG_LAST_KMSG
KCONFIG_VARIANT((null))
.
.
.

ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ chmod a+x ./scripts/exynos_dtbtool.shubuntu64@ubuntu64:~/Dokumente/2018/1/1$ chmod a+x ./scripts/exynos_mkdzimage.shubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_dtbtool.sh -o arch/arm64/boot/merged-dtb -p scripts/dtc/ -v arch/arm64/boot/dts/
DTB input path is 'arch/arm64/boot/dts'
output path is 'arch/arm64/boot', output file is 'merged-dtb'
page size is '2048'
*HEADER 236[B]
| PAD: 1812[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r08.dtb 79755[B]
| PAD: 117[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r05.dtb 79511[B]
| PAD: 361[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r06.dtb 79743[B]
| PAD: 129[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r11.dtb 80635[B]
| PAD: 1285[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r03.dtb 77418[B]
| PAD: 406[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r04.dtb 77735[B]
| PAD: 89[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r10.dtb 80886[B]
| PAD: 1034[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r13.dtb 80811[B]
| PAD: 1109[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r09.dtb 80411[B]
| PAD: 1509[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r12.dtb 80811[B]
| PAD: 1109[B]
*arch/arm64/boot/dts/exynos7270-tizen_solis-r07.dtb 79887[B]
| PAD: 2033[B]
## OUT: merged-dtb size: 888832[B]; 868[KB]
arch/arm64/boot/merged-dtb (size: 868KB) is created.
ubuntu64@ubuntu64:~/Dokumente/2018/1/1$ ./scripts/exynos_mkdzimage.sh -o arch/arm64/boot/dzImage -k arch/arm64/boot/Image -d arch/arm64/boot/merged-dtb
*HEADER 28[B]
| PAD: 2020[B]
*Image 14933280[B]
| PAD: 736[B]
*merged-dtb 888832[B]
| PAD: 0[B]
## OUT: dzImage size: 15824896[B]; 15454[KB]

This time I have compiled the "Engineer Variant" of CQL1 Kernel... no idea whats the difference... no idea if Eng Kernel in Combination firmware...

Maybe I have time this week to flash to my SM-R760...

Best Regards