[DEV][TOOL] kernel.sin and FTF creator (v1.0)

1. windows
2. may be Java installed

• Xperia X10 ONLY

1. place the compiled kernel zImage & compressed ramdisk (cpio.gz) in the same folder as these files
2. rename zImage to "image" (without quotes)
3. rename compressed ramdisk to "ramdisk" (without quotes)
4. edit the BUILD-IT.bat file and modify the following entries:
   
   Code:

   echo branding: DooMKernel-v06-BootManager-v1.4 >>  manifest.mf
   echo Created-By: DooMLoRD >>  manifest.mf
   echo version: 2.3.3 >>  manifest.mf
   ren kernel.jar X10_2.3.3_DooMKernel-v06-BootManager-v1.4.ftf

   to whatever you want, as this is what will be displayed in FlashTool FTF window
5. once you are done editing that file save it
6. now double click on BUILD-IT.bat to launch kernel.sin & FTF build process
7. at end you will get a FTF which can be flashed via FlashTool

adrianom said:

DoomLord,

Very nice...

In theory this method work to all sin files (partition), right? I only need to have the partition attributes, right?

You know how to get the attributes for all partition?

Click to expand...

Click to collapse

jonusc said:

How is the Bin2Elf and Bin2Sin different to mkbootimg? I ask because mkbootimg gives us some more options that we don't have with the tools by the_laser e.g. specifying the kernel commandline.

EDIT: Basically I want to learn more about the differences between boot.img and kernel.sin, I've crawled XDA for days but I don't think I can piece it all together. From what I understand boot.img is for fastboot/bootloader phones which the X10 isn't, though I am trying to figure out how to convert a boot.img to kernel.sin while retaining the command-line.

Boot.img seems to have only minor differences, the header starts with ANDROID and some other text such as the kernel command-line but I can't find any plain text in kernel.sin or loader.sin so I'm not sure where I can inject/remove some bytes to make the boot.img work with flashtool. Apart from the header the only other difference is random machine code two-thirds or so down, my guess is that's were the init.rd has been strapped on the end of the kernel.

Anyway, I tried flashing a boot.img in flashtool which I built based on the way custombootimg.mk does, but the flashtool freezes when it gets to kernel, I know that's probably silly but I hope there is some more material on the web or buried in XDA about the work you and the_laser have done that I could read up on.

Click to expand...

Click to collapse