[INFO] Modding boot logo

[nodramachicks]

i'm thinking this should be easier? anyone try it? or is there an EASIER method?

http://my.opera.com/eakrin/blog/index.dml/tag/A1200

How to modify BootImage (HelloMoto picture when phone power on)

Wednesday, 22. August 2007, 06:36:05
Motorola, A1200, CG39, ROKR E6 ...
Pack/Unpack BootImage Perl scripts for Motorla EZX Phones.
by eakrin @ MotorolaFans.com (eakrin@gmail.com) from Imahottyguy's how to.

License : Distribute and use for free and personal use only. do not use for commercial.

Boot Image is a first image that appear before splash animation display when power on phone. It is a GIF 89a image encoded to smg file. pack/unpackBootImage.pl is perl scripts that use to packing and unpacking gif image from and into smg file.

Requirements.
1. Perl Interpreter from ActivePerl

How to unpack bootimage.smg to gif image.
1. rename cg file to bootimage.smg
2. put pack/unpackBootImage.pl into the same folder as bootimage.smg.
3. double click on unpackBootImage.pl to extract smg file.
4. 2 files should apprear in bootimage folder. bootimage.gif and cgversion.txt bootimage.gif is a gif image file. cgversion.txt is a text file that indicated version of your cg.

How to pack gif image to bootimage.smg
1. check in bootimage folder that It have bootimage.gif and cgversion.txt.
2. double click on packBootImage.pl
3. new bootimage cg file should be in new_bootimage.smg.

PS. you can get bootimage.smg from firmware by use sbf codec extract cg39 from E6 and A1200 f/w.

cheer!
eakrin

[tmr]

...
How to modify BootImage (HelloMoto picture when phone power on)
...
cheer!
eakrin

There's nothing new and easy in this method, it's just the same old system warmed up a bit. (look at date of topic start)

...
or is there an EASIER method?

That's can be easier than a just direct write? unlock, erase, dd, lock, that's all!

[tmr]

Hi digitalD. I should explain what wrong with your mtd11.
This is strange, but seems that your "dd" compiled with non default block size (512)(I use mkezx dd). As I see, image writen to the wrong position (!0x800, 2048 bytes). To prevent this mistake you should use "bs" option, eg. bs=512 seek=4 or seek=2048 bs=1 or something like this.

[digitalD]

hey tmr.. thanks for looking into the issue...

please consider me as a total noob in the linux world.. and i really dont have much experience in hex editing too...

it would be really nice of you to gimme a step wise guide to what i should be doing ..

i really appreciate your help.

[norman_s]

you are saying easily, but doing complexly.

[MSmiles]

Instructions

- create[download,convert,etc.] new image: GIF89 240x320 8pbb
- extract CG39 from SBF
- goto 0x800
- replace original image from 0x800 to sizeof(new_image)
- repack SBF and reflash phone

Sorry in advance: practicing freedom of speech.
Posts like these with such vague instructions make me want to break something beautiful. Grrr.

I wish people would take the time to enumerate all the things needed in order for a specific task to be accomplished along with the instructions. Not just something half-a****

Sigh...

[tmr]

norman_s, this is complexly if you don't understand what you do. Actually, this operation last less than ten seconds, like file copying.

MSmiles, try to read next messages, I write step by step guide for win and mac users.

[starkrav]

tmr had previously provided an easy and direct way to modify the boot logo on the A1200. Now apparently he is offering to write detailed instructions so everyone can use it. I personally want to thank him for his insight, I've tried his method (as a non-expert) and it worked. However, we DID just recently discover one very important detail when modifying the boot logo with his direct flash method:
The size of the image file in bytes is just as important as the size of the image in resolution.

We discovered this when changing the boot logo to an image that was "larger" in byte size than previous images we had tried. What happened was that the image was written correctly, that is, it was placed exactly in the frame of the A1200 screen but the bottom 20% of the image was truncated and appeared black.

tmr this morning solved this problem by downsizing the image (in bytes, not dimension) and re-installing it. I don't know yet what the limit is in byte size using this method but the image we used was originally 34k in size (and was truncated) and tmr downsized it by reducing the color map to a size of 19k. The image is still 240 x 320 resolution but 15k smaller in byte size and no longer is truncated.

By the way, tmr is translating everything back and forth, English is NOT his language which to me is quite amazing actually. Thanks again tmr.