[APP] Motorola Boot Logo Maker (source code included) (Version 2.4)

Here is my full gui tool for creating boot logo files, for a number of Motorola Devices.

You get a preview of the picture, exactly how it would look on your device.

Features
Open Existing Logo.bin files
Open Existing Flashable zip files
Create logo.bin files
Create Flashable zip files
Export images from Logo.bin / Flashable zips.

Instructions
To use, you just double click on the treeview entries, select your picture, and repeat that process for all of the files that would be in logo.bin You then go to File / Save, and then save either as a .bin file, for flashing using fastboot, or as a Flashable zip file, for flashing using TWRP or CWM. In general, boot_logo is used on a factory locked device, and as a result, you probably should clear that one, as you would be wasting your space. logo_battery is your 0-3% indicator when the battery is run dry, and you plug it in to charge. logo_unlock is the actual boot screen logo you see on unlocked devices.

You can also open existing logo.bin files, wither from zip files, or directly, in order to modify them. Custom mode is for the advanced users, or for cases where a new Motorola device is released, where its logo.bin contains files that are not known. This tool auto-detects whether the file is the pre-kitkit format or not, and pictures that are larger than screen resolution, or in the case of pre-kitkat format, 540x540 is automatically scaled down. Upscaling options are provided, but centering the image is the default selection.

Bugs
None that I am aware of. If any are found, report them.


Limitations
The tool will not create any logo.bin files that are greater than 4MiB. This is a device limitation, specifically the logo flash partition is exactly 4MiB in size on all the known devices that I specifically support with this tool. As such, you may have to downscale or reduce the bpp formats of your images, to get them all to fit within the 4MiB. (Moto X Play has 6MiB, and Moto X Style has 8MiB).

Version History
Version 2.4 - Released Oct 21, 2015 - Download

• All 3 Moto G listings merged into one listing, due to screen size and logo.bin size being the same across ALL 3 of them.
• Updated the Moto E listing, with the 2nd gen, (no seperate listing due to both generations having same screen size, and same logo.bin max size.)

Older versions:


XDA:DevDB Information
[APP] Motorola Boot Logo Maker, App for the Moto G

Contributors
caitsith2
Source Code: https://github.com/CaitSith2/MotoBootLogoMaker


Version Information
Status: Stable
Current Stable Version: 2.4
Stable Release Date: 2015-10-21

Created 2014-09-17
Last Updated 2015-10-21

rpcll said:

Is "logo_battery" the one that appears when the phone is at 0%?

And when does the "logo_unlocked" screen appear?

Click to expand...

Click to collapse

logo_battery is indeed your phone at 0% image. logo_unlock is typically the image you should replace, as that as the one that contains the unlock warning screen.

metpolds said:

@caitsith2 ..... The comments I made in post #3 were made when I had run your App to see what it looked like but had not used it to try and make a boot logo. I have to say that the GUI interface is attractive and that made me comment as I did. When I used your App it failed to make a single logo, each time leaving me with just a "white" illuminated screen before the bootanimation started.

Click to expand...

Click to collapse

For this, bit, you may have missed that you should be replacing logo_unlocked, as that is the logo your phone is going to show, if you did indeed unlocked it.

If you could help me out, upload one or two of your unsuccessful zips, and I will have a look.

metpolds said:

Looking at the files associated with your App, I see that you have used (word for word) two files (1) update-binary and (2) updater-script which have been associated with other scripts dating back to 2013 but you have not kept the same file structure i.e. ..... META-INF>com>google>android..... and it's in the folder "android" that files (1) & (2) above appear. Is it possible that you have missed this?

Click to expand...

Click to collapse

Actually, the program creates the directory structure in the zip file itself. Just open up the zips created. You will see that the zip contains
META-INF>com>google>android>updater-script
META-INF>com>google>android>update-binary
logo.bin

All of which are part of a normal flashable zip file.

metpolds said:

I haven't tried flashing with "fastboot" - I prefer to flash through Recovery and I think the majority of noobs prefer that easier method so maybe you could check your scripting. I used 12 different images all of which have been used to successfully create Boot Logos so maybe you could check

Click to expand...

Click to collapse

rpcll said:

I was able to create a new bootlogo from scratch, but wasn't able to open any logos from this thread (http://xdaforums.com/showthread.php?t=2686441) to edit them.

Click to expand...

Click to collapse

Okay, I had a look at the contents of some of them, and was not aware of a third logo.bin format, which is just a raw 540x540x24bpp image.

Guess I will have to specifically add support for that format. You should be able to edit the logos that look like they fill the entire screen in the mean time, as that requires using the "kitkat" formatted logo.bin format.

Delgado666 said:

And when does the "logo_boot" screen appear?

When I boot my phone i see logo_unlocked screen

Click to expand...

Click to collapse

logo_boot is strictly for boot-loader locked phones, while logo_unlocked is strictly for boot-loader unlocked phones.

metpolds said:

@caitsith2
I endorse what I said originally, the GUI is elegant and a pleasant and effective advance on the cmd line scripts that most of us have been using, in consequence I have "rated" the thread. Please take the following comments as suggestions NOT as criticism. I think you will find that 90% of the thread users have unlocked their bootloaders and you could consider changing the tree "titles" to more clearly indicate which is which ..... alternatively ..... you could add a couple of lines to the instructions to clear up any misunderstanding.

I take heed of your comments regarding the two META-INF scripts and apologise for not researching deeper.

I think this thread deserves more publicity and will do what I can in this respect.

Click to expand...

Click to collapse

And now, you no longer have to worry about those META-INF files, as I have now embedded them into the program,

And the tree now shows a tool-tip as to the purpose of the items, when you hover the mouse over the item.

The next version will be built with the Ionic.Zip.dll zip library built into the program, so that the program can truly stand alone.

Yeah, additional awareness would be good, as this should work with any motorola phone that has a flashable boot logo.

Phones that are Moto E and later, will likely have logo_boot, logo_unlocked, logo_battery, logo_lowpower, and logo_unplug.

Moto X/Moto G/Droid Ultra has logo_boot, logo_unlocked, logo_battery.

Motorola phones released mid-late 2012 have just logo_boot and logo_unlocked. Motorola phones released early 2012 (Droid 4) and earlier, have just the raw 540x540 logo. Although those phones only have 1MiB partitions, it will never be exceeded on those devices.

Version 1.5 released. Check OP for details.

Version 1.6 released. Fixed a fairly major bug.

UncolourTV said:

Excelent! i will change my bootlogo once a week with this!

Do you plan to make custom boot animations possible with this on a future update? Or this is just for the logos?

Anyway, thank you for efforts on this :good:

Click to expand...

Click to collapse

This is just for the boot logos and anything that Motorola decides to store in the boot logo partition.