Droid 1 custom bootloader logos to replace Motorola logo

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
"Moto Droid" (a member here) approached me with a very good question about replacing the bootloader image in a Droid 1. This is not the "boot animation" image (which is the pulsing red "eye" on a stock phone), but is the white Motorola "M" logo that displays when you first boot the phone (while the bootloader is loading and handing off).

According to the information the member had (from a guide on this site), historically the procedure to replace the bootloader image was to modify a "full flash" SBF and replace the logo (as the logo is in a code group of its own). His question was "wouldn't it make more sense to just flash the single CG with the logo rather than the whole thing?" Of course he's right -- it is silly to blow away the entire phone just to replace your bootloader logo.

Since I have several Droid 1's running different bootloaders and different versions of the OS, I offered to prepare a "bootloader image only" SBF, regression test it, and release it. This way, those that would like to make a custom bootloader image SBF have a safe base to work from that will only replace the bootloader image, leave the rest of the phone undisturbed, and therefore be safe for any OS version on a Droid 1.

It should be noted that the bootloader image is a 480 x 182 BMP file that only contains what appears in the center band of the screen. The areas above and below that band are filled in automatically.

The original bootloader logo (package link in case you want to go back to stock at some point) looks like this:

attachment.php



I prepared two custom ones using two DroidForums.net logos. I think they are both cool, but right now the second one is the one I have on my daily use phone.


The first custom one I made (package link) uses this image, by TParker76:

attachment.php



The second custom one I made (package link) uses this image by Dandroid and Johndroid:

attachment.php



I know I'm a dork, but I really think it's cool to see something custom so early in the boot process.

To flash these packages onto your Droid 1, grab the zip from one of the three links above, unzip it (I zip them for file integrity purposes -- these are not update.zip type files, so you do need to unzip them), and then use my SBF flashing guide to apply the package to your phone.

Before flashing an SBF to your phone it's a good idea to do a fresh Nandroid backup just in case. If you don't know what that is, you can find it with "search" on these forums.

Please note: The subject and purpose of this topic is the SBF packages contained herein. There are other topics on the forum that discuss how to make your own custom bootloader image and those topics are the appropriate place to support that activity. I do not wish or intend to support that process here in Droid Labs.

Enjoy!

Edited to add: I went ahead and made a very simple (I'm a coder guy, not a graphics guy) boot animation file to go along with the last bootloader image above. If your web browser supports animated PNG files, you can click here to see what it looks like. The idea was that if you had the "These are the Droids you are looking for" bootloader image, the phone would start with that static picture, and then when the bootloader had fully transitioned into Android booting, and the boot animation takes over, it would start with the same image, and then seamlessly continue with the flashing lights. Someone who is good with graphics certainly could come up with a cooler implementation of this -- a neat 480 x 182 static bootloader image that then transitions smoothly into a cool boot animation. If you want to try the my boot animation, just grab this file and copy it to /data/local/bootanimation.zip on your phone ("adb push MC1_TATDYLF_Boot_Animation.zip /data/local/bootanimation.zip"). If that command doesn't make any sense, Google or search here for instructions on installing and using ADB. If you want to go back to stock, just delete the file from your phone and your phone will go back to using /system/media/bootanmiation.zip.
 
Last edited:

Moto Droid

New Member
Joined
May 24, 2010
Messages
15
Reaction score
0
"it is silly to blow away the entire phone just to replace your bootloader logo."
Thanks MotoCache1, this makes much more sense. That's whole reason I didn't want to do it the other way was flashing a whole sbf for a logo I will see only for a second or 2.
 
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
Good to hear we don't have to go back-and-forth for this
Hi FastKatt. I made a followup post in the other topic where you all are discussing making your own custom bootloader image SBF's. It sounds like you were trying to slice and dice your own SBF out of a full-flash. It's much safer to grab one of the ones above and then just replace CG42 in it. There's more in there than just the code groups. The SBF's above have been tested with numerous Android versions and bootloaders on various Droid 1's and should be perfect to use "as is" or to put your own image in. If you don't really understand what every file inside an SBF is you're playing with fire when you start deleting and changing things.
 

DF Smod

Silver Member
Joined
Apr 23, 2010
Messages
11,341
Reaction score
88
And the Lab is underway...as always thanks for the quick and easy approach to doing things that you bring to the table
 
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
OK, I'm not really a graphics guy at all -- I'm functional with image editing software, but don't really have any artistic skills at all. That said, I added a little "Edited to add" section at the bottom of the OP with a boot animation file that I made to go along with the 3rd SBF bootloader image. It looks just like the bootloader image but then adds in some animation so you seamlessly transition from bootloader image, into animation, to the OS being up. I'm hoping it will inspire the more graphically inclined folks to make a neat, static, 480x182 image to use as the bootloader image, which then transitions into a series of images (which can be up to 480x720 -- using the full screen instead of just the middle like the bootloader image does) that will be the boot animation.
 

fish1552

Premium Member
Premium Member
Rescue Squad
Joined
Mar 16, 2010
Messages
662
Reaction score
31
Location
Savannah area of Coastal Georgia, USA
Current Phone Model
S23 Ultra
Twitter
fish1552
So I'm wondering...and that often is dangerous. :)

It seems like you have a pretty decent grasp on the sbf files and such. I noticed in step 9 of the flashing sbf tut you mentioned:
On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter.
Do you know enough to dig into it and maybe include "SW Update Complete. Press UP on your D-pad"? Might help, IDK.

And people keep wondering on these other threads/forums why people don't want to give up their Droid1! I love changing EVERYTHING on this to truly make it MY take on Droid!
 
Last edited:

fish1552

Premium Member
Premium Member
Rescue Squad
Joined
Mar 16, 2010
Messages
662
Reaction score
31
Location
Savannah area of Coastal Georgia, USA
Current Phone Model
S23 Ultra
Twitter
fish1552
OK, I'm not really a graphics guy at all -- I'm functional with image editing software, but don't really have any artistic skills at all. That said, I added a little "Edited to add" section at the bottom of the OP with a boot animation file that I made to go along with the 3rd SBF bootloader image. It looks just like the bootloader image but then adds in some animation so you seamlessly transition from bootloader image, into animation, to the OS being up. I'm hoping it will inspire the more graphically inclined folks to make a neat, static, 480x182 image to use as the bootloader image, which then transitions into a series of images (which can be up to 480x720 -- using the full screen instead of just the middle like the bootloader image does) that will be the boot animation.

Weird, I've been trying to do that exact thing. I just keep getting either the first part or the second part working tough. Following the steps in the various tuts but something still isn't sitting right. :/
 
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
So I'm wondering...and that often is dangerous. :)

It seems like you have a pretty decent grasp on the sbf files and such. I noticed in step 9 of the flashing sbf tut you mentioned:
On your phone the screen will change to "SW Update Complete" (unless the message has been changed by the person who built the SBF) and your phone will reboot shortly thereafter.
Do you know enough to dig into it and maybe include "SW Update Complete. Press UP on your D-pad"? Might help, IDK.

And people keep wondering on these other threads/forums why people don't want to give up their Droid1! I love changing EVERYTHING on this to truly make it MY take on Droid!
Great question and idea. Changing the various messages that are displayed during flashing is actually pretty easy. The catch is that you have to keep the format of the message the same (number of letters per line, number of lines) as the original message.

Currently, the last message you see after a good flash, just before the phone boots is two lines:
Code:
SW Update
Complete
So that's 9 characters on the first line and 8 characters on the second.

The best message I could come up with that fits that pattern is:
Code:
Hold DPad
 up NOW
It goes by really fast, so I'm not really sure if there is much advantage, but I like the idea. When I make my next SBF perhaps I'll have that in there. It's a pretty big pain to go and re-generate the existing SBF's, redo all the links, update all the guides to the new links, etc., so I don't know that I'll go back and redo them, but going forward it would be a clever touch.

Thanks for the suggestion!
 
Last edited:
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
OK, I'm not really a graphics guy at all -- I'm functional with image editing software, but don't really have any artistic skills at all. That said, I added a little "Edited to add" section at the bottom of the OP with a boot animation file that I made to go along with the 3rd SBF bootloader image. It looks just like the bootloader image but then adds in some animation so you seamlessly transition from bootloader image, into animation, to the OS being up. I'm hoping it will inspire the more graphically inclined folks to make a neat, static, 480x182 image to use as the bootloader image, which then transitions into a series of images (which can be up to 480x720 -- using the full screen instead of just the middle like the bootloader image does) that will be the boot animation.

Weird, I've been trying to do that exact thing. I just keep getting either the first part or the second part working tough. Following the steps in the various tuts but something still isn't sitting right. :/

I'll PM you my email address and you can zip up your images and shoot them to me and I'll give it a whack and send you back some files...
 

jlutz555

Member
Joined
Feb 10, 2010
Messages
238
Reaction score
0
so have we figured out exactly what determines the overall background color yet?
 
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
so have we figured out exactly what determines the overall background color yet?
On which part? On the the bootloader image it seems like it is probably picking up the color of one of the edges of the image because the original Motorola one has black edges and the top and bottom fills in black. Both of mine have white backgrounds, but due to some clipped text (in the original image I grabbed off the forum) the bottom edge isn't 100% white (there is some gray), so I'm thinking perhaps something along the lines of sample all the pixels in the top and bottom line of the image and whatever color is most common is what it uses? Just a guess. It could be deduced with enough experimentation.
 

fish1552

Premium Member
Premium Member
Rescue Squad
Joined
Mar 16, 2010
Messages
662
Reaction score
31
Location
Savannah area of Coastal Georgia, USA
Current Phone Model
S23 Ultra
Twitter
fish1552
From the other thread, I was able to determine that the top left corner isn't where the color comes from. I used the image attached in one of the logos, and the color for the background was olive green. And the top right and bottom left corners have that color as do random edges. All the rest of mine were solid backgrounds and showed up as you would expect.
I think tparker was having problems with one of his that looked like it was all black, but had a white background.

I clear it up, I may have to create a logo with different colors around the outside edges and see what shows up.
 
OP
MotoCache1

MotoCache1

Chief Droid Scientist
Joined
Jun 30, 2010
Messages
530
Reaction score
1
From the other thread, I was able to determine that the top left corner isn't where the color comes from. I used the image attached in one of the logos, and the color for the background was olive green. And the top right and bottom left corners have that color as do random edges. All the rest of mine were solid backgrounds and showed up as you would expect.
I think tparker was having problems with one of his that looked like it was all black, but had a white background.

I clear it up, I may have to create a logo with different colors around the outside edges and see what shows up.
Now I feel compelled to replace it 1000 times if I have to to find out what pixel or pixels it looks at to decide the fill color for the top and bottom. Fortunately, if I'm starting from a clean boot of my PC with all the USB ports 100% happy the SBF takes like 15 seconds from hitting the start button until I have "PASS". Just need to prep up like 10 SBF's and start hammering some flashes on. But I need to eat dinner first. And hopefully I'll get back and you'll have posted the answer. ;)
 
Top