[Ornate TrueSmart] :
Hi martinbogo1

Thanks for your very accurate Developer Reply.

Exaclty you are absolute Right!

Not that i know.

What i can tell and know is that we are able to Compile and create with the Delivered tools and the Sources a Boot Loader Image that can be Flashed to the Watch Phone.

To create such a Boot Loader Image you need to download the Sources from Github

https://github.com/LinuXperia/mt6572_x201

do a Clean up with

./mk ipro72_we_jb3 clean

and start Compiling the BootLoader Image with

./mk ipro72_we_jb3 n lk

The BootLoader Image that contain the Kernel together with the Initram Filesystem can be found after a successful Build in the following Directory

/out/target/product/ipro72_we_jb3

After this Like every MediaTek Image the Kernel can be extracted from the Image by using Tools like

unpack-MT65xx.pl

This will give you then this self compiled BootLoader Kernel here

http://ubuntuone.com/4NYWAdKDM3daeEFf7SugOU

A simple Compare of the ARM Machine Code with the Original MediaTek Build Kernel here

http://ubuntuone.com/1A2RRSPhGh2kMLsx80UtQh

will reveal that several Memory Access Addresses are different also that for some strange Reason the Android Header Part is Missing.

As a Example by Using the HexBinary Viewer vbindiff to Compare both Kernels we get for the Original Build Kernel this here

0000 0000: 41 4E 44 52 4F 49 44 21 08 AE 3C 00 00 80 00 10 ANDROID! ..<.....
0000 0010: 6E C4 09 00 00 00 00 11 00 00 00 00 00 00 F0 10 n....... ........
0000 0020: 00 01 00 10 00 08 00 00 00 00 00 00 00 00 00 00 ........ ........
0000 0030: 32 30 31 33 31 30 32 38 2E 31 38 30 35 31 30 00 20131028 .180510.

0000 0800: 88 16 88 58 08 AC 3C 00 4B 45 52 4E 45 4C 00 00 ...X..<. KERNEL..
0000 0810: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0000 0820: 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF ........ ........
0000 0830: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ........ ........

and for the Self Compiled Kernel this here

0000 0000: 88 16 88 58 08 AC 3C 00 4B 45 52 4E 45 4C 00 00 ...X..<. KERNEL..
0000 0010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
0000 0020: 00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF ........ ........

So yes you are absolute right!

We need to Port a Kernel from a another Device that has the same SoC but different Drivers to the Omate Truesmart without having any Technical Specs or really hardware Knowledge about the Hardware.

That is why i am also thinking that Reverse Engineering aka Disassembling the Original Kernel Builds can help us get further.

kuronosan has allready started with importing non existing Drivers to the Kernel to his Kernel Source Tree as can be seen i am not sure however if this Drivers are really the Ones that we original need.

https://github.com/kuronosan/mt6572_x201/commit/e0db624c174c71529612750470ac4ba1357376d1

If anybody is willing to Dissasamble the Kernel Firmware here are the Files.

Original Builded MediaTek Bootloader Kernel

http://ubuntuone.com/1A2RRSPhGh2kMLsx80UtQh

Original Builded MediaTek Android Linux Kernel

http://ubuntuone.com/6d1BLOYwqZlrnEkIlCZYHS

Self compiled BootLoader Kernel

http://ubuntuone.com/4NYWAdKDM3daeEFf7SugOU

If you want me to do something for you like making a research on the just received Omate Truesmart Developer Edition Watch Phone

please write exactly what need to be done step by step.

I am very busy and dont have lot of time to loose.

Thanks in advance.

Greetings Aran.