Editing boot logo (initlogo.rle)

[broodplank1337]

Hi,

As some of you know it's possible to change the bootlogo in boot.img, named initlogo.rle. I've made a new bootlogo and converted it to rle. I tried these methods:

1. Make in photoshop > save as raw > convert with "to565" to initlogo.rle > hang at samsung logo
2. Open background in paint.net > save as RGB565 file (with plugin) > convert with "to565" to initlogo.rle > hang at samsung logo

method used to convert raw to rle

$ tools_cygwin/to565 -rle < logo/initlogo.raw > logo/initlogo.rle

method used to repack the img

$ tools_cygwin/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk-new.gz -o target_img/boot.img --base "cat unpack/boot.img-base"

I actually also tried to NOT change the logo and leave all the files intact, then repacked it. This also got me a corrupted boot.img file which means that the packing method probably isn't correct.

If someone knows the right way could you please change the initlogo.rle from boot.img provided in the zip with the one in the zip (attached: boot.img, initlogo.png, initlogo.raw, initlogo.rgb565, logo2.psd)

If this is working correctly for me i completely remove/disable the boot animation for faster boot

I would greatly appreciate it if someone wants to make it (and tell me what i did wrong)

edit: the actual bootlogo

 

[GuestK00338]

I would also like to know this!

Please keep us posted if you get it right!

good luck!

Sent from my GT-I9000 using Tapatalk

 

[broodplank1337]

I would also like to know this!

Please keep us posted if you get it right!

good luck!

Sent from my GT-I9000 using Tapatalk

Ok I will

 

[erdemsaid]

thanks too much dude. i search this

 

[broodplank1337]

thanks too much dude. i search this

If you don't get a bootloop when trying it, would you please download my attached file and replace the initlogo.rle file then repack?

 

[Mich2027]

Great idea, i was searching a way to totally get rid of the boot animation, will keep an eye on this one...
Thanks

 

[broodplank1337]

If anyone knows how to fix it please reply... threads like this one get lost in the Q&A section very quick.

 

[FlorisNL]

Is it working yet?

Sent from my GT-i9001 @ LionROM

 

[x1123]

Hi,

As some of you know it's possible to change the bootlogo in boot.img, named initlogo.rle. I've made a new bootlogo and converted it to rle. I tried these methods:

1. Make in photoshop > save as raw > convert with "to565" to initlogo.rle > hang at samsung logo
2. Open background in paint.net > save as RGB565 file (with plugin) > convert with "to565" to initlogo.rle > hang at samsung logo

method used to convert raw to rle

$ tools_cygwin/to565 -rle < logo/initlogo.raw > logo/initlogo.rle

method used to repack the img

$ tools_cygwin/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk-new.gz -o target_img/boot.img --base "cat unpack/boot.img-base"

I actually also tried to NOT change the logo and leave all the files intact, then repacked it. This also got me a corrupted boot.img file which means that the packing method probably isn't correct.

If someone knows the right way could you please change the initlogo.rle from boot.img provided in the zip with the one in the zip (attached: boot.img, initlogo.png, initlogo.raw, initlogo.rgb565, logo2.psd)

If this is working correctly for me i completely remove/disable the boot animation for faster boot

I would greatly appreciate it if someone wants to make it (and tell me what i did wrong)

edit: the actual bootlogo

I downloaded you rar file, checked and looklike all file ok I dont have this i9000 .. I thinks this is galaxy S. Unpack your boot.img

$unpack-bootimg.pl boot.img

we will have additional 3 files boot.img-kernel.gz boot.img-ramdisk.cpio.g and Folder boot.img-ramdisk. Well in this folder boot.img-ramdisk I presumed all went well. Take out initlogo.rle in the ramdisk folder and change with yours (?) from unrared folder
create new ramdisk >

$mkbootfs boot.img-ramdisk | gzip > bootimg-ramdisk [ENTER]

Now we have kernel.gz and gziped ramdisk (with new initlogo.rle file) ... repack into boot image flashable via fastboot >

$mkbootimg --kernel boot.img-kernel.gz --ramdisk bootimg-ramdisk --pagesize 4096 --cmdline "console=ttyFIQ0,115200 init=/init no_console_suspend" --base 0x32000000 -o samgalaxysxda.img

samgalaxysxda.img is flashable via fastboot in this post or download HERE

$sudo fastboot flash boot samgalaxysxda.img

if something wrong I thing you can modify the command during create boot image

mkbootimg --kernel boot.img-kernel.gz --ramdisk bootimg-ramdisk --pagesize 4096 [B][COLOR="Red"]--board aries[/COLOR][/B] --cmdline "console=ttyFIQ0,115200 init=/init no_console_suspend" --base 0x32000000 -o samgalaxysxda-1.img

I tried to split your boot image to know the parameter

$split_bootimg.pl boot.img

OUTPUT FILE FOR OUR INFO

Page size: 4096 (0x00001000)
Kernel size: 3632644 (0x00376e04)
Ramdisk size: 650135 (0x0009eb97)
Second size: 0 (0x00000000)
Board name: 
Command line: 
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
...

usually Command line (kernel command line) is very important. I toke cmdline from cm7 tree using galaxysmtd .. this probably I choose wrong device

Just test and post here the result

 

[wintel_mac]

9000 and 9001 work different when it comes to the kernel. And their hardware is significantly different. I don't know if even fastboot works, have never tried it.