Changing boot splash on Kit Kat

rlmesq · Jan 5, 2014

Q: Is there a way to change the boot splash image (Moto dual core logo) when running Omni 4.4.2?

I had used the Team EOS Boot Splash image to change the double-M logo to the Jelly Bean logo. After running BigPart and upgrading to Kit Kat, I'd like to restore to stock, but the EOS displays an error message saying it's only compatible with the Xoom.

UPDATE: I've tried the methods on the two threads below, with no luck.

http://xdaforums.com/showthread.php?t=2123586

http://xdaforums.com/showthread.php?p=20664147

sigfridov · Jan 11, 2014

OmniROM bootsplash replacement

rlmesq said:
Q: Is there a way to change the boot splash image (Moto dual core logo) when running Omni 4.4.2?

I had used the Team EOS Boot Splash image to change the double-M logo to the Jelly Bean logo. After running BigPart and upgrading to Kit Kat, I'd like to restore to stock, but the EOS displays an error message saying it's only compatible with the Xoom.

UPDATE: I've tried the methods on the two threads below, with no luck.

http://xdaforums.com/showthread.php?t=2123586

http://xdaforums.com/showthread.php?p=20664147

Try this:
http://xdaforums.com/attachment.php?attachmentid=2487982&d=1388603369
This is V3 of a contribution from AIEsC, which You can see here:
http://xdaforums.com/showthread.php?t=2580256&page=26
Basically it will delete old phone related apps, as well as will install your requested Motorola logo.
Good luck! And thanks me if it is useful for you.

rlmesq · Jan 11, 2014

sigfridov said:
Basically it will delete old phone related apps, as well as will install your requested Motorola logo.
Good luck! And thanks me if it is useful for you.

Thanks for the suggestion.

One quick question... does this actually replace the splash screen (the static Double-M logo)?

It appears the file installs a Moto Heatbeat boot animation, but I don't see anything in the .zip package that would change the splash screen.

sigfridov · Jan 11, 2014

rlmesq said:
Thanks for the suggestion.

One quick question... does this actually replace the splash screen (the static Double-M logo)?

It appears the file installs a Moto Heatbeat boot animation, but I don't see anything in the .zip package that would change the splash screen.

For OmniROM you will see the pictures as you said, later the Omni logo show some lines moving out from left to right, then Omni logo keep moving just its eyes, so the zip of the link will set the first Moto logo same as Omni ROM, but will change to a Moto Logo with circles moving from inside to out until boot process finish.
Is it what are you looking for?
Let me know...

rlmesq · Jan 11, 2014

Thanks, but this zip package doesn't change the initial double-m splash screen. It only changes the boot animation (Omni logo) that follows it.

If the double-m logo was there in the first place, you'll still have it after flashing this... but I had replaced the splash screen with a different logo, and am trying to change that.

rlmesq · Jan 13, 2014

I found a solution:

1. Booted into recovery.
2. Backed up current ROM (CM11), data & boot.
3. Wiped data, system & cache.
4. Flashed EOS4 (v. 195)
5. Flashed the BigPart boot zip file (I was too lazy to replace boot.img in the ROM zip.)
6. Flashed Xoom gapps.
7. Booted to Jellybean
8. Installed Team EOS splash screen app.
9. Ran app, selected "return to stock," and it said flashing was successful.
10. Rebooted to recovery, made a backup entitled "Boot Image Changer" in case I want to use it again, and restored the earlier backup of CM11.
11. Rebooted again to see the Double-M instead of a Jellybean jar for the first time in a year.

sigfridov · Jan 14, 2014

rlmesq said:
I found a solution:

1. Booted into recovery.
2. Backed up current ROM (CM11), data & boot.
3. Wiped data, system & cache.
4. Flashed EOS4 (v. 195)
5. Flashed the BigPart boot zip file (I was too lazy to replace boot.img in the ROM zip.)
6. Flashed Xoom gapps.
7. Booted to Jellybean
8. Installed Team EOS splash screen app.
9. Ran app, selected "return to stock," and it said flashing was successful.
10. Rebooted to recovery, made a backup entitled "Boot Image Changer" in case I want to use it again, and restored the earlier backup of CM11.
11. Rebooted again to see the Double-M instead of a Jellybean jar for the first time in a year.

I see.
The new Logo, what kind of image have to be in order it be able to be installed (flashed)?
Could ypu show what picture did you setup?
Nice job...

rlmesq · Jan 14, 2014

sigfridov said:
The new Logo, what kind of image have to be in order it be able to be installed (flashed)?
Could ypu show what picture did you setup?
Nice job...

I think you can use most image formats, but I've reinstalled my CM11 backup so I can't open the program to check. I used a jpg.

You can crop the image from within the program. I'm not sure of the dimensions, but it's in portrait orientation, not landscape.

I just flashed back to the stock double-M "Dual Core" logo. That's contained in the program, so you don't have to hunt it down.

This is the image I had before... the Jellybean logo.

[Image] http://androidmuscle.com/wp-content/uploads/2013/02/android-jelly-bean-4.2.2.jpg[/image]

rlmesq · Jan 28, 2014

UPDATE: The EOS boot image app now recognizes my Xoom running CM11. Weird.

Topics

Topics

Changing boot splash on Kit Kat

rlmesq

Senior Member

sigfridov

Senior Member

rlmesq

Senior Member

sigfridov

Senior Member

rlmesq

Senior Member

rlmesq

Senior Member

sigfridov

Senior Member

rlmesq

Senior Member

rlmesq

Senior Member

Similar threads

New posts