[Samsung Galaxy Express GT-I8730 Guides, News, & Di] jjchico:
CM + samsung zImage

Hi!

I have done some tests using samsung's zImage with the CM build from [MENTION=5093942]KINGbabasula[/MENTION] with no luck.

Background:

* I have use the samsung boot.img generated by CWM backup. I have extracted the samsung's zImage from there.

* I have used the "abootimg" package included in Ubuntu and other Linux distributions to manipulate the boot.img.

* When I say "samsung logo" I mean the very first "Samsung Galaxy Express I8730" logo.

These are the results:

* samsung kernel + cm initrd:

- samsung logo for a few seconds, followed by screen corruption: the screen starts to draw light grey lines and goes slowly to white. I reboot manually after a few more seconds.

- same result using the CWM backup zImage and zImage provided by [MENTION=5246389]aureljared[/MENTION] in this thread.

When generating the boot.img with abootimg you need to use a bootimg.cfg. I mostly used the .cfg generating when extracting the samsung boot.img. The CM .cfg will give an error when used with the samsung kernel. I also tried a simple .cfg only including command line but no kernel/initrd addresses. In this case, after booting, the phone stays at the samsung logo forever. See details at the end of the post.

* whole samsung boot.img as saved by CWM backup:

- samsung logo, stays there forever.

* CM kernel + samsung initrd: same as CM kernel + CM initrd (original CM build)

Conclusions: the samsung kernel seems to do something: instead of rebooting is causes screen corruption and who knows what else... May be it is a problem with the kernel/initrd addresses in the boot.img config file. I am not familiar with these parameters. Any help is wellcome.

Configuration details:

===============

Original Samsung boot.img

====================

$ cat samsung/bootimg.cfg

bootsize = 0xa00000

pagesize = 0x800

kerneladdr = 0x80208000

ramdiskaddr = 0x82200000

secondaddr = 0x81100000

tagsaddr = 0x80200100

name =

cmdline = console=null androidboot.hardware=qcom user_debug=31

$ abootimg -i samsung/boot.img

Android Boot Image Info:

* file name = samsung/boot.img

* image size = 10485760 bytes (10.00 MB)

page size = 2048 bytes

* Boot Name = ""

* kernel size = 6171016 bytes (5.89 MB)

ramdisk size = 355676 bytes (0.34 MB)

* load addresses:

kernel: 0x80208000

ramdisk: 0x82200000

tags: 0x80200100

* cmdline = console=null androidboot.hardware=qcom user_debug=31

* id = 0xa1fb2a75 0xc942ae30 0xada0d3d2 0x3146d7a4 0xbe949ab0 0x00000000 0x00000000 0x00000000

CM [MENTION=5093942]KINGbabasula[/MENTION] build

$ cat cm-10.2/bootimg.cfg

bootsize = 0x409000

pagesize = 0x800

kerneladdr = 0x80208000

ramdiskaddr = 0x82208000

secondaddr = 0x81100000

tagsaddr = 0x80200100

name =

cmdline = console=null androidboot.hardware=qcom user_debug=31

$ abootimg -i boot.img

Android Boot Image Info:

* file name = boot.img

* image size = 4231168 bytes (4.04 MB)

page size = 2048 bytes

* Boot Name = ""

* kernel size = 3766448 bytes (3.59 MB)

ramdisk size = 459727 bytes (0.44 MB)

* load addresses:

kernel: 0x80208000

ramdisk: 0x82208000

tags: 0x80200100

* cmdline = console=null androidboot.hardware=qcom user_debug=31

* id = 0x3cb1305f 0x0724ec57 0x3d516aa2 0xd71ea721 0x7af8fea3 0x00000000 0x00000000 0x00000000

Simple configuration

===============

$ cat bootimg.cfg

cmdline = console=null androidboot.hardware=qcom user_debug=31

$ abootimg -i boot.img

Android Boot Image Info:

* file name = boot.img

* image size = 6635520 bytes (6.33 MB)

page size = 2048 bytes

* Boot Name = ""

* kernel size = 6171016 bytes (5.89 MB)

ramdisk size = 459727 bytes (0.44 MB)

* load addresses:

kernel: 0x00000000

ramdisk: 0x00000000

tags: 0x00000000

* cmdline = console=null androidboot.hardware=qcom user_debug=31

* id = 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000

(see that load addresses are all zero in this case)