Changing your motorola "M" boot logo tutorial

[fish1552]

Actually, Moto Droid is 100% correct. You only need to flash CG42 if you only want to replace the bootloader image. Flashing anything else (much less everything else) is completely unnecessary.

I just figured it was one of those times where it just seemed like it was too easy to be true. But that's good to know. Saves a heck of a lot of time and recovery.

So what do you do just recompile the SBF with only the cg42 file in it?

You should be able to click the remove button for each of the other files in SBFCodec to just remove them.
I'm gonna try it as soon as I fix my problem where my phone won't reboot into either recovery mode. Makes it just a bit more difficult to change these. LOL

[fish1552]

Ok, just tried flashing only the CG42 file and I'm still showing the same boot logo I had before. It gave me the same FAILED message I always get flashing them, but for some reason nothing changed. This was for the Android Peeing On Apple (name changed to pass censor) image posted by FastKatt.

I'm going to play around with it a few more times and see if maybe it wasn't the image. The file size was way off what I normally get when editing them and usually I can get to the "ff" near the end of the SBF and delete everything else. This time I had to dig a few bits into that to get the file size right. Maybe I'll try it using one of the older files first.

[FastKatt]

FWIW, my file was still a jpg
I started to work with it, till I found the 2nd write-up & the possibility of a shorter way

[fish1552]

FWIW, my file was still a jpg
I started to work with it, till I found the 2nd write-up & the possibility of a shorter way

Oh, I converted everything to a bmp-24 file. Just that some of the numbers weren't coming up the same in more than just the image file. I'm going to keep trying and see what I can figure out.

On another note, I had another suggestion to keep the RDL3 part of the sbf in there as well. I'm going to try that and see what happens...

[MotoCache1]

FWIW, my file was still a jpg
I started to work with it, till I found the 2nd write-up & the possibility of a shorter way

Oh, I converted everything to a bmp-24 file. Just that some of the numbers weren't coming up the same in more than just the image file. I'm going to keep trying and see what I can figure out.

On another note, I had another suggestion to keep the RDL3 part of the sbf in there as well. I'm going to try that and see what happens...

It's probably easiest and safest if you start with one of the "bootloader image only" SBF's in my topic and just replace CG42 in that. Yes, you need to have the right RAM downloader in your SBF for it to work (which in this case is RDL3, but it's not always RDL3). Not everything in the SBF is a CG that gets written to the phone. Some of the files are code used in the flashing process, and others are data that defines the CG's, etc. It is much safer to start with an SBF that is made by someone who completely understands the internals, and then just replace a CG, than to take things out and add them in by trial and error. That's why I created the SBF's in that topic -- to give the community a properly built, regression tested, "bootloader image only" SBF to modify and work with. I also have an SBF in there to put your boot image back to stock (without overwriting anything else).

Also, if you want to avoid getting "failed" at the end, be sure to check out steps 8, 9, and 10 of my SBF flashing guide. You won't get "pass", ever, if you don't do those steps.

Hope this helps.

[Jharmon12]

ok i tried downloading the boot screen only sbf and doing my own custom boot logo with it. I have tried several times and got critical errors with it. when i flashed the stock logo back to it it fixed it. So thinking that it was my smg file i stuck in in the full restore sbf and it worked. What did i do wrong? I have done several boot logos before and would like to get this to work for me. One time i went to reprogram my phone after flashing one and verizon wouldnt reactivate my phone so i had to go all day with out it. Could it be that i was modifying the stock sbf and not one that was already modded? attached is the sbf file i was using

[MotoCache1]

ok i tried downloading the boot screen only sbf and doing my own custom boot logo with it. I have tried several times and got critical errors with it. when i flashed the stock logo back to it it fixed it. So thinking that it was my smg file i stuck in in the full restore sbf and it worked. What did i do wrong? I have done several boot logos before and would like to get this to work for me. One time i went to reprogram my phone after flashing one and verizon wouldnt reactivate my phone so i had to go all day with out it. Could it be that i was modifying the stock sbf and not one that was already modded? attached is the sbf file i was using

Grabbing and taking a look...

[MotoCache1]

ok i tried downloading the boot screen only sbf and doing my own custom boot logo with it. I have tried several times and got critical errors with it. when i flashed the stock logo back to it it fixed it. So thinking that it was my smg file i stuck in in the full restore sbf and it worked. What did i do wrong? I have done several boot logos before and would like to get this to work for me. One time i went to reprogram my phone after flashing one and verizon wouldnt reactivate my phone so i had to go all day with out it. Could it be that i was modifying the stock sbf and not one that was already modded? attached is the sbf file i was using

Grabbing and taking a look...

OK, I disassembled your SBF, and looked at your CG42 file. It's the right length and has the 64 byte pad at the end which is that should have mattered. I recompiled the SBF and then compared them. Mine and yours are not the same. There should be minor differences due to the embedded date stamp being different, but I can't say for sure if all the differences are right or not. I'm going to flash on my recompiled one first, and then yours and see how it goes. Back with you soon.

[MotoCache1]

OK, I disassembled your SBF, and looked at your CG42 file. It's the right length and has the 64 byte pad at the end which is that should have mattered. I recompiled the SBF and then compared them. Mine and yours are not the same. There should be minor differences due to the embedded date stamp being different, but I can't say for sure if all the differences are right or not. I'm going to flash on my recompiled one first, and then yours and see how it goes. Back with you soon.

Hahaha - that's awesome. I love your Monster logo. Personally I'm a Moster Low Carb (blue logo) fan, but still. OK, that was my recompile of your exploded SBF (which obviously went fine). Now let me try to flash your original SBF and see what happens.

[MotoCache1]

OK, I disassembled your SBF, and looked at your CG42 file. It's the right length and has the 64 byte pad at the end which is that should have mattered. I recompiled the SBF and then compared them. Mine and yours are not the same. There should be minor differences due to the embedded date stamp being different, but I can't say for sure if all the differences are right or not. I'm going to flash on my recompiled one first, and then yours and see how it goes. Back with you soon.

Hahaha - that's awesome. I love your Monster logo. Personally I'm a Moster Low Carb (blue logo) fan, but still. OK, that was my recompile of your exploded SBF (which obviously went fine). Now let me try to flash your original SBF and see what happens.

Yah - no go. What tool are you using to compile your SBF? Whatever it is it's not recalculating the checksum value on your CG42 (the one you're replacing). When I was looking at your SBF in the hex editor I was pretty sure the that some of the byte pairs that differed were the checksums. Your SBF has a checksum of 0x7C87 for CG42, but the correct checksum is 0x18BB. Some tools you have to manually fix the checksums in the file yourself with a hex editor by using the error output in RSD Lite as a guide. If you can give me a link to download whatever tool you're using (if I don't already have it somewhere) I can check it out and let you know. In the meantime, here's your file rebuilt in a working state.

I'm getting ready to head to bed (after 2am here), but I'll check the topic in the a.m. to find out what tool you're using and get back to you.