Moto X Boot Logos

[Globalrebel]

Worked like a charm. unlocked bootloader message is gone

 

[Bill Idol]

Tell me where it can be found and I'll give it a shot.



I attached what I believe is the correct bootanimation.zip which is found in /data/local/moodle

Edit: found out how to find and back up the purple boot logo. Looks like this. Uploaded to imgur so everyone can see it and also to dropbox so you don't have to rename it. It's a 4mb bmp.

https://www.dropbox.com/s/r17e78p82r9ron2/clogo.bmp

Thanks brudda

Sent from my XT1060 using Xparent Cyan Tapatalk 2

 

[clebaomotoqueiro]

Thanks brudda

Sent from my XT1060 using Xparent Cyan Tapatalk 2

someone has logo.bin this purple image?
to flash the moto x Christmas theme.
sorry english google translator.
thank you

 

[caanda45]

I too would like a logo.bin of the purple image....that would be great.

 

[MaKTaiL]

No love for this thread

 

[carock]

Attached purple motorola logo bin file, as requested.
It doesn't include the "motorola a google company", but it does include the empty battery logo in the bin.

 

[MaKTaiL]

Attached purple motorola logo bin file, as requested.
It doesn't include the "motorola a google company", but it does include the empty battery logo in the bin.

Thank you very much! :good:

 

[bgdc]

Attached purple motorola logo bin file, as requested.
It doesn't include the "motorola a google company", but it does include the empty battery logo in the bin.

Thanks. Now i need to find a way to nuke that animation when I reboot my phone. Moodles...moodles...off to kill the moodles.

 

[cannondale0815]

I tried everything and i couldn't find a way to open it in GIMP, it just refused to open the .bin or .raw extensions!

You have to change the file extension to ".data" for GIMP to correctly identify it as a RAW image. This worked for me. I also figured out that the dimension is 540 x 1620 (for the three-image logo type with the battery image), and the Palette Type is "B, G, R, X".

But I still have issues with the correct offset.

 

[KidJoe]

Attached purple motorola logo bin file, as requested.
It doesn't include the "motorola a google company", but it does include the empty battery logo in the bin.

Thank you!

Can you share how you replaced the individual image?

I would love to change the warning message to the jeweled logo in the OP (the box art).

 

[carock]

Thanks. Now i need to find a way to nuke that animation when I reboot my phone. Moodles...moodles...off to kill the moodles.

\data\local\moodle\bootanimation.zip
If you rename the file (e.g. bootanimation.zip.bak), you should only see the boot logo during startup. At least that's what happened when I tried to replace it with an incorrectly formatted bootanimation

You have to change the file extension to ".data" for GIMP to correctly identify it as a RAW image. This worked for me. I also figured out that the dimension is 540 x 1620 (for the three-image logo type with the battery image), and the Palette Type is "B, G, R, X".

But I still have issues with the correct offset.

Thank you!

Can you share how you replaced the individual image?

I would love to change the warning message to the jeweled logo in the OP (the box art).

All the info is in the file header:
logo_boot
starts at 0x200, is 0xD5930 bytes
logo_battery
starts at 0xD5C00, is 0xD5930 bytes
logo_unlocked
starts at 0x1AB600, is 0xD5930 bytes

If you do the math, that leaves a buffer between the logos of 0xD0 bytes.
As for the image formats. They are all 540x540 and BGR-24bit, except logo_boot is RGB-24bit.

What I did, was remove the logo_unlocked (everything after 0x1AB600), and append my own image.
I used ffmpeg to convert a 540x540 bmp to the correct format:

ffmpeg -i logo.bmp -f rawvideo -s 540x540 -pix_fmt bgr24 logo.raw

 

[cannondale0815]

All the info is in the file header:
logo_boot
starts at 0x200, is 0xD5930 bytes
logo_battery
starts at 0xD5C00, is 0xD5930 bytes
logo_unlocked
starts at 0x1AB600, is 0xD5930 bytes

If you do the math, that leaves a buffer between the logos of 0xD0 bytes.
As for the image formats. They are all 540x540 and BGR-24bit, except logo_boot is RGB-24bit.

What I did, was remove the logo_unlocked (everything after 0x1AB600), and append my own image.
I used ffmpeg to convert a 540x540 bmp to the correct format:

ffmpeg -i logo.bmp -f rawvideo -s 540x540 -pix_fmt bgr24 logo.raw

Carock, this is hugely useful, you clearly know your stuff. I am honestly a bit of a rookie when it comes to image manipulation. What's the best way to accomplish cutting off the last image before apending the new one?

Thanks
-J

 

[lxadoz104]

Nice work on the mlogoblk!

 

[carock]

Carock, this is hugely useful, you clearly know your stuff. I am honestly a bit of a rookie when it comes to image manipulation. What's the best way to accomplish cutting off the last image before apending the new one?

Thanks
-J

I would suggest using a hex editor. If you're using windows, you can try a program called Frhed. It has an option under the edit menu to delete a section by offset and size. And you can also insert a file, under the file menu, wherever you place the cursor. I attached the bin file with the logo_unlocked already removed for use/reference.

Cheers.

 

[darkgodz]

anyone able to take a request for making a few of the custom images with the battery info?

thought i'd add, im on 4.4, unlocked but not rooted.

 

[carock]

Got bored and decided to decipher the compressed 4.4 logo bin.

The header is the same format as the old logo bin, but the image data is compressed using an odd algorithm.

There is a header for each image now too. Each starts with 0x4d6f746f52756e (MotoRun in hex), followed by 0x00, followed by 2bytes for the horizontal resolution, and 2bytes for the vertical resolution. Such as, 0x4d6f746f52756e0002d00500 would be for a 720x1280 image.
Basically, each chunk of the image is preceded by a 0x8 or 0x0, followed by a 12bit number.
For 0x8, the number that follows signifies how many times to repeat the next 3bytes as RGB (or BGR) pixels. With a maximum number of repetitions being the horizontal resolution. For instance, 0x82D0FFFFFF would be 720 white pixels.
For 0x0, the number that follows signifies how many 24bit(3byte) pixels will follow. For instance, 0x0002FFFFFF000000 would be 1 white pixel followed by 1 black pixel.
And that's basically it. With one extra rule, that you cant repeat 2 of the same color pixels using 0x8. Such that 0x8002FFFFFF wouldn't occur. It would instead be 0x0002FFFFFFFFFFFF.

I've tested this with a script to decompress the images, and I've also compressed other images with this method. Both work fine.

anyone able to take a request for making a few of the custom images with the battery info?

thought i'd add, im on 4.4, unlocked but not rooted.

attached (tested & worked for me)

 

[Smukec]

good work

 

[darkgodz]

Got bored and decided to decipher the compressed 4.4 logo bin.

The header is the same format as the old logo bin, but the image data is compressed using an odd algorithm.

There is a header for each image now too. Each starts with 0x4d6f746f52756e (MotoRun in hex), followed by 0x00, followed by 2bytes for the horizontal resolution, and 2bytes for the vertical resolution. Such as, 0x4d6f746f52756e0002d00500 would be for a 720x1280 image.
Basically, each chunk of the image is preceded by a 0x8 or 0x0, followed by a 12bit number.
For 0x8, the number that follows signifies how many times to repeat the next 3bytes as RGB (or BGR) pixels. With a maximum number of repetitions being the horizontal resolution. For instance, 0x82D0FFFFFF would be 720 white pixels.
For 0x0, the number that follows signifies how many 24bit(3byte) pixels will follow. For instance, 0x0002FFFFFF000000 would be 1 white pixel followed by 1 black pixel.
And that's basically it. With one extra rule, that you cant repeat 2 of the same color pixels using 0x8. Such that 0x8002FFFFFF wouldn't occur. It would instead be 0x0002FFFFFFFFFFFF.

I've tested this with a script to decompress the images, and I've also compressed other images with this method. Both work fine.



attached (tested & worked for me)

:victory: :highfive:

 

[KidJoe]

I've tested this with a script to decompress the images, and I've also compressed other images with this method. Both work fine.

Script? Can you share?

Or write up a process for us to make our own logo.bin for kitkat?

 

[carock]

Script? Can you share?

Or write up a process for us to make our own logo.bin for kitkat?

I cleaned up my scripts and made them more universal and friendly. Rough scripting, so it might not be perfect (or very efficient).
File attached.

This was made for windows. You'll need to install perl and ffmpeg and add them to your path for this to work properly. If you're running linux, I'm sure you can figure out how to adjust it.

Once you've done that, simply place your 720x1280 image in the folder and run the compress.bat. You'll be prompted to enter the image name. I'd recommend a lossless format, but any image file should work.
This will output a logo.bin that should work fine. It will also output a file called logo-moto.raw, which is the raw compressed file. I did this in case you want to run my decompress bat file on it and check if it outputs the correct image.

Hope this helps.
Oh, and of course, I'm not responsible if anyone damages their phone/pc from using this