[Android Q&A, Help & Troubleshooting] V3ctorX:
try

http://k.japko.eu/boot-img-manipulation.html

or

Okay, first off, let me tell you I'm not at all familiar with your device...so, instead of specifically answering your questions (which would be dangerous/irresponsible of me to have you do something for which I cannot be sure of or vouch since I don't have experience with your device), I'll try to give you some general information (it does seem like you have a good grasp of many of the concepts for getting where you want to go, so maybe I can just fill-in some gaps :)).

1. Regarding renaming initlogo.rle to initlogo.rle.old: I'm not sure that doing that will change the splash screen or break something when it goes to look for the initlogo.rle file (a special image file). As you've probably researched, these files are a bit odd and are not just simple image files we're all used to dealing with. I've never successfully been able to create a new initlogo.rle file on my previous attempts a few years back.

2. When you re-pack a bootable image file (boot.img or recovery.img), you need:

- re-pack the updated ramdisk to a new ramdisk.gz file

- rebuild the .img file using mkbootimg utility, specifying the kernel file and the updated ramdisk.gz file

- it's might also be important / necessary to specify the base boot address using the --base <address> parameters when issuing the mkbootimg command where <address> is the base boot address of your device; your bootable image split/unpacking utility should tell you what it sees that the base address is; here is the information I saw when I unpacked the boot.img file that you supplied in your first post:​

ScaryAlien@LV-426 ~/boot-img-split-tools/ameen

$ ../split_boot.pl boot.img

Page size: 2048 (0x00000800)

Kernel size: 9600396 (0x00927d8c)

Ramdisk size: 1313051 (0x0014091b)

Second size: 0 (0x00000000)

Board name:

Command line: 'console=ttyS0,115200 rw init=/init loglevel=5'

Base address: (0x40000000)

Writing boot/boot.img-kernel ... complete.

Writing boot/boot.img-ramdisk.cpio.gz ... complete.

Unpacking ramdisk... complete.

ScaryAlien@LV-426 ~/boot-img-split-tools/ameen​

- not having properly set the base boot address might explain why your device didn't boot

- not properly re-packing the ramdisk might explain why your device didn't boot

- not properly rebuilding the bootable image (using the mkbootimg utility)​

3. I kind of understand what you were trying to do by changing the the .md5 file...I'm guessing that you calculated a new MD5 sum of the new boot.img file thinking that would help CWM restore it; that probably doesn't matter unless you've got the MD5/checksum verification enabled; asking/using CWM to restore / install your boot.img is an interesting and non-traditional way of doing that :)

4. Is the CWM custom recovery specifically built for your device? I did a quick search for it and couldn't find anything. You do indeed need a custom recovery that is built specifically for your device and it's hardware & partition / filesystem layouts and sizes. Just want to make sure that you were aware of that...using the "wrong" custom recovery might be "problematic" (bad).

Edit: I think I might have found which one you used? http://xdaforums.com/showthread.php?t=2189640

5. If you had previously booted into custom recovery on your "broken" device, you still should be able to re-flash or re-launch the custom recovery in the same way that you originally did, yes? The boot and recovery partitions should be separate--so, if you only messed with the boot partition, then you should be okay--unless you've got an incompatible custom recovery that overwrote important things (like your recovery partition...).

I hope that helps...I know I didn't touch on all of your questions...that's probably enough for this post and for what follow-up questions you might have ;) :p.

Cheers!

source

http://androidforums.com/threads/help-with-boot-img.963358/