I TAKE NO RESPONSIBILITY FOR YOUR PHONE OR ANY DAMAGE INCURRED FROM APPLYING THIS. MODIFY AND FLASH AT YOUR OWN RISK
==Intro==
When I've unlocked my phone I faced with ugly warning window instead of moto logo I got used to. And desperately wanted to get rid of this disclaimer.
Searching the web I've got some tips about swizzled color channels and raw image format, but there was nothing 100% compatible with (or at least described for) our DROID MAXX\Ultra\mini.
In order to modify boot logo you have to prepare and binary logo file and flash it. I'm not sure if this file get checked on flash (most likely you can flash it even on locked phone). I appreciate if someone try to flash modified logo with locked bootloader just to confirm
First off all let me tell you shortly how this binary logo file looks like.
For our phones it's size is 2,625,328 bytes, at least on 4.4 and 4.2.2 ROMs. This file includes 3 images:
1) logo for the phone with locked bootloader
2) image with discharged battery which you can see when you start charging turned off phone
3) logo for the phone with UNlocked bootloader, and in original logo there is that ugly disclaimer
each image is raw color data 540x540 in BGR (not RGB) format. there are also some headers and tech data. Here are offsets for each of these 3 images (important):
1) 512 (locked bootloader image)
2) 875520 (charging battery)
3) 1750528 (unlocked bootloader image)
each image 874800 bytes long: 540 * 540 * 3 (3 color channels, 1 byte per channel, 3 per pixel)
BTW: Fun fact on 4.2.2 there was a string at the end of the first paragraph of disclaimer "-and all warranties are null and void". In 4.4 they got rid of this phrase =)) and words alignment become worse... =))
== tools ==
1) GIMP (free tool for graphics) (http://www.gimp.org/downloads/). I was on 2.8.10.
2) RawTEX plugin for GIMP (http://registry.gimp.org/node/57). Extract RAWTex.exe to "<GIMP FOLDER>\lib\gimp\2.0\plug-ins\"
3) Swiss File Knife (http://sourceforge.net/projects/swissfileknife/?source=dlp)
== preparation ==
1) Make a working folder
2) get original logo.bin file for your phone from sbf file for you phone from http://sbf.droid-developers.org/. It is named logo.bin in the archive, put it in our working folder.
2.1) Actually I'll post original binary logo file below, it is the same for all Maxx\Ultra\Mini as I wrote above.
3) extract Swiss File Knife to this folder (sfk170.exe in my case)
4) find\create\resize a 540x540 image for your logo =)
== step by step how to ==
1. Prepare binary image for injection
a) open regular 540x540 (bmp, png, gif, jpeg does not matter) image in GIMP
b) flip red and blue channels
i. go to Colors -> Components -> Channel Mixer ...
ii. for output channel red (by default already selected) set RED value from 100 to 0 AND BLUE from 0 to 100
iii. for output channel blue (now select in drop down) set BLUE value from 100 to 0 AND RED from 0 to 100
iv. OK to apply
c) export in binary format
i. File -> Export as...
ii. Select "All files", expand "Select File Type (by extention)", scroll to file type "Raw image data"
iii. select our working directory as a target dir, give it a name, lets say "mylogo.data"
iv. press export
v. in export settings select Save Type "Stanadrd (R, G ,B)" and Indexed Palete Type "R, G, B (normal)", these settings should be default, but I put them just in case
d) CHECK FILE SIZE of the image, it should be exactly 874800 bytes
2. Once you get a proper binary image, lets inject it into the motorola logo file
a) open command line in our folder and execute:
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 1750528
b) check the output it should be like this:
Code:
[simulating:]
copying 874800 bytes, from input offset 0 to 874800, to target offset 1750528
[add -yes to really copy data.]
c) if the output precisely the same as above lets commit these changes to out logo.bin by executing
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 1750528 -yes
d) Not necessary step! if you have unlocked bootloader, this step will affect only locked phones logo
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 512 -yes
3. your modified logo ai ready, check output filesize for logo.bin (2,625,328 bytes), cross your fingers and flash this logo to the phone:
rebbot to fastboot manually or make it with ADB:
Code:
adb reboot bootloader
flash the file:
Code:
fastboot flash logo logo.bin
reboot the phone and enjoy your stylish logo:
Code:
fastboot reboot
I'm also attaching my first custom logo which I made as a proof of concept.
== notes ==
1) same way you can replace batter logo, you know that offset =)
2) I'm aware of various logo creating tools and created logos like this
I should say that these logo files are not complete and substantially differ from our original logos, they have only one image encoded (no battery charging image, etc). It might be safe to use them, but I personally prefer to keep everything as much as possible to the original logo we have in our maxx\ultra\mini firmwares. May be I'll rool out my own tool soon to create logo files easily. It is up to you which logo to use.
Do not forget to share your work with others! =) Lets make a galley of nice boot images here for those who do not want to draw\convert\inject.
[Reserved for the best works]
Dragon31337 said:
I TAKE NO RESPONSIBILITY FOR YOUR PHONE OR ANY DAMAGE INCURRED FROM APPLYING THIS. MODIFY AND FLASH AT YOUR OWN RISK
==Intro==
When I've unlocked my phone I faced with ugly warning window instead of moto logo I got used to. And desperately wanted to get rid of this disclaimer.
Searching the web I've got some tips about swizzled color channels and raw image format, but there was nothing 100% compatible with (or at least described for) our DROID MAXX\Ultra\mini.
In order to modify boot logo you have to prepare and binary logo file and flash it. I'm not sure if this file get checked on flash (most likely you can flash it even on locked phone). I appreciate if someone try to flash modified logo with locked bootloader just to confirm
First off all let me tell you shortly how this binary logo file looks like.
For our phones it's size is 2,625,328 bytes, at least on 4.4 and 4.2.2 ROMs. This file includes 3 images:
1) logo for the phone with locked bootloader
2) image with discharged battery which you can see when you start charging turned off phone
3) logo for the phone with UNlocked bootloader, and in original logo there is that ugly disclaimer
each image is raw color data 540x540 in BGR (not RGB) format. there are also some headers and tech data. Here are offsets for each of these 3 images (important):
1) 512 (locked bootloader image)
2) 875520 (charging battery)
3) 1750528 (unlocked bootloader image)
each image 874800 bytes long: 540 * 540 * 3 (3 color channels, 1 byte per channel, 3 per pixel)
BTW: Fun fact on 4.2.2 there was a string at the end of the first paragraph of disclaimer "-and all warranties are null and void". In 4.4 they got rid of this phrase =)) and words alignment become worse... =))
== tools ==
1) GIMP (free tool for graphics) (http://www.gimp.org/downloads/). I was on 2.8.10.
2) RawTEX plugin for GIMP (http://registry.gimp.org/node/57). Extract RAWTex.exe to "<GIMP FOLDER>\lib\gimp\2.0\plug-ins\"
3) Swiss File Knife (http://sourceforge.net/projects/swissfileknife/?source=dlp)
== preparation ==
1) Make a working folder
2) get original logo.bin file for your phone from sbf file for you phone from http://sbf.droid-developers.org/. It is named logo.bin in the archive, put it in our working folder.
2.1) Actually I'll post original binary logo file below, it is the same for all Maxx\Ultra\Mini as I wrote above.
3) extract Swiss File Knife to this folder (sfk170.exe in my case)
4) find\create\resize a 540x540 image for your logo =)
== step by step how to ==
1. Prepare binary image for injection
a) open regular 540x540 (bmp, png, gif, jpeg does not matter) image in GIMP
b) flip red and blue channels
i. go to Colors -> Components -> Channel Mixer ...
ii. for output channel red (by default already selected) set RED value from 100 to 0 AND BLUE from 0 to 100
iii. for output channel blue (now select in drop down) set BLUE value from 100 to 0 AND RED from 0 to 100
iv. OK to apply
c) export in binary format
i. File -> Export as...
ii. Select "All files", expand "Select File Type (by extention)", scroll to file type "Raw image data"
iii. select our working directory as a target dir, give it a name, lets say "mylogo.data"
iv. press export
v. in export settings select Save Type "Stanadrd (R, G ,B)" and Indexed Palete Type "R, G, B (normal)", these settings should be default, but I put them just in case
d) CHECK FILE SIZE of the image, it should be exactly 874800 bytes
2. Once you get a proper binary image, lets inject it into the motorola logo file
a) open command line in our folder and execute:
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 1750528
b) check the output it should be like this:
Code:
[simulating:]
copying 874800 bytes, from input offset 0 to 874800, to target offset 1750528
[add -yes to really copy data.]
c) if the output precisely the same as above lets commit these changes to out logo.bin by executing
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 1750528 -yes
d) Not necessary step! if you have unlocked bootloader, this step will affect only locked phones logo
Code:
sfk170.exe partcopy mylogo.data -allfrom 0 logo.bin 512 -yes
3. your modified logo ai ready, check output filesize for logo.bin (2,625,328 bytes), cross your fingers and flash this logo to the phone:
rebbot to fastboot manually or make it with ADB:
Code:
adb reboot bootloader
flash the file:
Code:
fastboot flash logo logo.bin
reboot the phone and enjoy your stylish logo:
Code:
fastboot reboot
I'm also attaching my first custom logo which I made as a proof of concept.
== notes ==
1) same way you can replace batter logo, you know that offset =)
2) I'm aware of various logo creating tools and created logos like this
I should say that these logo files are not complete and substantially differ from our original logos, they have only one image encoded (no battery charging image, etc). It might be safe to use them, but I personally prefer to keep everything as much as possible to the original logo we have in our maxx\ultra\mini firmwares. May be I'll rool out my own tool soon to create logo files easily. It is up to you which logo to use.
Click to expand...
Click to collapse
From what i have read with locked bootloader you flash to clogo and use .bmp file. So it would be
fastboot flash clogo <filename.bmp>
Sent from my Dev Ed. Ultra
Clogo.bmp is for locked boot loader the op has an unlocked phone its logo.bin he is correct
---------- Post added at 02:42 PM ---------- Previous post was at 02:38 PM ----------
Dragon the xda logo when unzipped says its a data file not a bin file I am unable to flash it. I really like it and would like to try it out.
bigv5150 said:
Clogo.bmp is for locked boot loader the op has an unlocked phone its logo.bin he is correct
---------- Post added at 02:42 PM ---------- Previous post was at 02:38 PM ----------
Dragon the xda logo when unzipped says its a data file not a bin file I am unable to flash it. I really like it and would like to try it out.
Click to expand...
Click to collapse
The logo_fixed.bin and xda_logo.data are both the same filesize with the same header. You should just be able to change xda_logo.data to xda_logo.bin and flash it, and it will work.
@Dragon31337 Does your logo you created still cycle colors? or is it stuck on Orange like the one posted in the other thread?
Looks like there is no option for unlocked phones to use animated logos, at least I did not figured out it yet. By default unlocked phone read this non-animated image from logo file and display it. Actually someone already posted this note.
I've reuploaded xda_logo, now there is a bin file, so you should not rename it from .data to .bin before flashing.
Thanks for the upload I'm going to try it tonight.
That sucks the colors don't cycle when I changed the stock logo it got stuck on orange as well. I'm guessing that may be the first color in the cycle.
It did not stack, logo behavior is just different for locked and unlocked bootloaders. I'm still looking for opportunities to enable animated logo.
bigv5150 said:
Clogo.bmp is for locked boot loader the op has an unlocked phone its logo.bin he is correct
---------- Post added at 02:42 PM ---------- Previous post was at 02:38 PM ----------
Dragon the xda logo when unzipped says its a data file not a bin file I am unable to flash it. I really like it and would like to try it out.
Click to expand...
Click to collapse
Indeed. He asked in OP about someone trying it w locked bootloader. I was addressing that
Sent from my Dev Ed. Ultra
Here is something interesting I just got a refurbished maxx from Verizon in the mail ( don't ask its going back). Anyway when I turned it on the boot logo was orange same as yours. Here is the weird part everytime I boot up the phone its always the orange Motorola logo it never changes this phone is stock from the factory and it still never changes I don't get it
From what I've got reading forums there is a way to turn on animation and firmware supports that. It turns on animation by schedule and can be updated over internet by carrier\moto. By default it shows static logo, but once there is a schedule record and it hits current time it uses alternative logo which can be animated.
May be we should dig into that direction.
I just want my original color changing M back.
Sent from my unlocked consumer edition Motorola Droid Maxx xt1080m.
Awesome tutorial thanks
Related
I would like to request users to post all there boot images in a single thread for all other users. and i would also request a boot image that is the Gucci and FBI boot image modded for mytouch that is available in the dream forum, i can post them if you can't find coz with those images i can make a perfect boot ROM(special Hero) highly modded and highly cool if anybody can mod the images for my touch or just use the name magic. with that if done i can make a secure and cool hero ROM that will run as fast as cyanogen's and Good boot and graphics
This is updated with the latest tool. (Windows)
I included a zip with all files you may need at the bottom of the post.
1. Turn off your phone
2. Turn on the phone into bootloader (camera+power).
Make sure it say fastboot in the middle if not hit back and it should appear-
3. Make sure your device is found in device manger
If you don't see adb device up top in device manger find the yellow mark devices
Right Click, update driver, and point to the location of the USB Driver
(http://dl.google.com/android/android_usb_windows.zip)
4. Open and extract the below zip to your desktop
You should now have a custom and fastboot folder on your desktop
5. Open up a dos window (start>run>CMD)
6. Type cd desktop then cd fastboot
7. If you would not like to flash the sample images skip to step 9
8. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565
fastboot reboot
Part 2 Making your own images
9. Open up the "create" folder
10. Run CreateG1Splash.exe
11. Open up your image in the program and click convert
12. Go to the folder of your images and their you will find mysplash.rgb565
13. Place the mysplash.rgb565 into the fastboot folder
14. copy and paste the command line by line
fastboot flash splash1 mysplash.rgb565
fastboot flash splash2 mysplash.rgb565 (maybe the mytouch or magic spl does not have splash2 partition. dont panic if it gives any error. it cannot brick the phone)
fastboot reboot
i just copied it from the dream forum so credits to them
Here are the boot images to be edited
I finally found the images on my hard drive, so here they are. Can anybody replace G1 with mytouch
Right, so here's what I boot to =)
Andy and Astroboy my 2 favorite androids!
Nice! How do you change the boot screen?
Using fastboot
We can change the using fastboot and boot images tool, ican upload it if requested
Here's mine. I included the .jpg and the .rgb565 file for easy use, if anyone would want it.
if u can upload that it would be nice. i wanna try to mamke a nice boot screen. if u have some tutorial on how to make the glow also would be nice, sorry im still new to this as mytouch is my first android phone.
Here's one for ya
myBoot.zip has both a jpg and the raw565 file. Enjoy
edit: Also decided to add the original boot image that spawned this - myOriginalBoot.zip
edit: I finally got that peeing Andy working on this thing! framework-res.apk attached. You need to do the following:
Update your 32b phone to Cyanogen 4.1.2.1
Unzip framework-res.apk from the framework-apk.zip attachment
From a shell, run:
adb remount
adb push /path/to/framework-res.apk /system/framework/framework.apk
Now reboot your phone and enjoy your custom boot splash followed by the animation of Andy peeing on an apple that looks suspiciously familiar.
Note - I take no credit for the images you see here. I simply compiled them into boot screens for your enjoyment.
Here is mine... my first try at Adobe CS4 Fireworks... haha
Here is mine (for now)
Can anybody please change the names in these images
Charnsingh - Try these
I put these together in like 5 minutes, so if you want me to change something or if it's not quite perfect, let me know and I'm happy to correct.
Enjoy!
BTW - nice work on the Debian installer, got it running on my myTouch right now and I can't get over having LXDE on my phone
edit - I just noticed the FBI screen had Dream written on it, so you'll notice I made some adjustments to that graphic as well.
For the lxde just install vnc viewer from the market then start debian. After that go to vnc after sometime and input the values given and you Will be running lxde. Have any problem pm me. Thanks for the edit I will throw on a Gucci FBI Rom tomorrow. Just gimme your name and I will make a special one for you (with login and pass)
maybe i may just give the files coz i cant keep on updating each and every hero ROM, and people it will be universal, can be used on any hero ROM. I will create a one click file for windows and mac(you must have adb set up) and one for the phone. Files will be build.conf, the edited system files, the sound files, some image files and sim tracker app from market if you would like that. The editing will not affect the speed, i can also make a speedu script for hero as i have done for my phone which needs to be run every time you flash a hero ROM, just message me
flash troubles...
how long does it take to flash the new splash screen??? my cmd is sitting at sending 'splash1' <300kb>...
and not moving--- anyways i have another question..
there is HBOOT and FASTBOOT...
when im in FASTBOOT it says sending 'splash1' <300kb>... FAILED <remote: not allow>
when im in HBOOT it just sits at sending 'splash1' <300kb>...until i close or do something else to stop it... i let it sit for 20 min--- no way in hell should it take that long
It never takes more than a second for me...
ok so im not sure why i keep getting remote: not allow any help out there?
What SPL are you using? Search the forum for how to root your myTouch.
I have tried over and over to install the USB driver and it will not install. Im running Win7. Is this my issue and how can I get the driver to work so I can run FastBoot?
11ryan11 said:
ok so im not sure why i keep getting remote: not allow any help out there?
Click to expand...
Click to collapse
iWantDonut said:
What SPL are you using? Search the forum for how to root your myTouch.
Click to expand...
Click to collapse
+1 you need to root.
Hi everyone and thanks for your time. I will get straight to the point:
All these tests were made on G925V 5.1.1 , rooted with eng boot. (Look at my profile for my post on how to downgrade from 7.0 ,and all below, to 5.1.1 and for for root turorial)
-The samsung downgrade mechanism relies on a flag set in the different partitions to determine its version.
- The phone looks for the flag "SYSMAGIC X" where X is the version. (Starting from 0, meaning SYSMAGIC 0= version 1)
-The following partitions have the flag:
*BOTA0 <----gets its files from sboot.bin (bootloader first partition)
* BOTA1 <-------gets its files from cm.bin (bootloader second partition)
*BOOT <----- from boot.img
*CACHE <-----from cache.img
*RECOVERY <----from recovery.img
*SYSTEM <------from system.img
*sdb <---- which is the bootloader as a whole I believe, don't quote me in this, just a deduction.
All these files can be accessed through a full tar or by dumping them using dd if of.
Bota0, bota1, boot, system,recovery,cache..etc can be found in :
/dev/block/platform/15570000.ufs/by-name
Putting any of these in a hex editor, you will find the line "SYSMAGIC 3" (in my case for 5.1.1, binary version 4).
If you dump /dev/block/sda18 , edit with hex editor and edit the SYSMAGIC to one version lower. Save then dd back to sda18, reboot the phone and guess what?
SYSTEM REV. CHECK FAIL. DEVICE:3 BINARY:2.
All this is assumption but the line is there and it seems to pass every check and just assumes thats the version.
Hope someone can take it further. I unfortunately bricked my s6 writing the wrong partiton back over the bootloader...and well...bad bootloader....no more download mode.
Be careful, devs please help. Anyone with a device willing to use as a ginny pig, pm me.
dragoodwael said:
Hi everyone and thanks for your time. I will get straight to the point:
All these tests were made on G925V 5.1.1 , rooted with eng boot. (Look at my profile for my post on how to downgrade from 7.0 ,and all below, to 5.1.1 and for for root turorial)
-The samsung downgrade mechanism relies on a flag set in the different partitions to determine its version.
- The phone looks for the flag "SYSMAGIC X" where X is the version. (Starting from 0, meaning SYSMAGIC 0= version 1)
-The following partitions have the flag:
*BOTA0 <----gets its files from sboot.bin (bootloader first partition)
* BOTA1 <-------gets its files from cm.bin (bootloader second partition)
*BOOT <----- from boot.img
*CACHE <-----from cache.img
*RECOVERY <----from recovery.img
*SYSTEM <------from system.img
*sdb <---- which is the bootloader as a whole I believe, don't quote me in this, just a deduction.
All these files can be accessed through a full tar or by dumping them using dd if of.
Bota0, bota1, boot, system,recovery,cache..etc can be found in :
/dev/block/platform/15570000.ufs/by-name
Putting any of these in a hex editor, you will find the line "SYSMAGIC 3" (in my case for 5.1.1, binary version 4).
If you dump /dev/block/sda18 , edit with hex editor and edit the SYSMAGIC to one version lower. Save then dd back to sda18, reboot the phone and guess what?
SYSTEM REV. CHECK FAIL. DEVICE:3 BINARY:2.
All this is assumption but the line is there and it seems to pass every check and just assumes thats the version.
Hope someone can take it further. I unfortunately bricked my s6 writing the wrong partiton back over the bootloader...and well...bad bootloader....no more download mode.
Be careful, devs please help. Anyone with a device willing to use as a ginny pig, pm me.
Click to expand...
Click to collapse
That is great news. What else do you know of the magic bytes at the footer of the system image?
I'm going to look into this.
All of those partitions, probably even the cache partition with it's metadata file from the CSC, have points that have access to the private signing key burned into the Trust Zone firmware.
Hi, I followed your tut on downgrading my SM-G925V to 5.1.1 and also got root which was great, but I guess its pretty worthless as its only temporary til reboot, has there been any further progress on permanent root on the G925v? Great work btw all involved!
Note:
This is not bootanimation, this is the splash screen (the 'Coolpad' boot logo which is displayed when device is switched ON)
This is for Coolpad Cool1 Dual Snapdragon variants Only..
For other devices, please send me your splash.img so that I can create a tool for you too..
Requirements:
1. Rooted Coolpad Cool1 Dual (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Coolpad_Cool1_Dual_Splash_Maker.zip
2. Make sure you have 4 pictures (same or different) in 1080x1920 px resolution in PNG format.
(It seems Coolpad displays any 1 picture from the 4 pictures randomly while switching ON, so I think you'll have to use 4 pictures)
3. Now rename your 4 pictures as logo1.png, logo2.png, logo3.png, logo4.png & replace it inside "pics" folder of the extracted folder.
(Similarly you can replace other pictures in it carefully if you wish)
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Thanks to @Vikasspattel who provided the stock splash.img of Coolpad Cool 1 Dual ..
2. This is just a modified version of my tool here: [GUIDE] How to Change Boot Logo (Splash Screen) of LeEco Le 2 / Le S3
Hit the Thanks :good: button if it worked for you
You're welcome to share the splash images that you created
Thank You sir for reading my comment and helped by your quick effort ,
well i had no hope but thank you so much
hi
i installed custom recovery to cool 1 c 103
after it finished model number changed to 106
what i have to do?????
Note:
This is not bootanimation, this is the splash screen (the 'Huawei' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
Use this tool and instructions:
Huawei OEM_logo Changer
Note: Use a 1080x1920 pic, as .bmp file (in rgb565 format as specified in that post)
Old method:
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly 1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Steps to backup your oeminfo.img:
Open Terminal Emulator, type the following command to save your stock oeminfo.img to your Internal Storage:
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo_stock.img
Now, choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/oeminfo.img of=/dev/block/platform/hi_mci.0/by-name/oeminfo
c. To flash from Fastboot mode:
Code:
fastboot flash oeminfo oeminfo.img
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
2. @GokulNC (myself ) who wrote this script
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Doesn't work for me., same logo as before.
rebranded mine too
---------- Post added at 09:07 PM ---------- Previous post was at 09:05 PM ----------
https://imgur.com/a/XAup4
just made this btw, it's already in the right format.
GokulNC said:
TESTING:
@CrimsonBloodfang
1. Can you please check if this tool is working??
2. Please check if flashing the zip from custom recovery works.
3. Please attach your 'oeminfo' partition backup. I guess it might have the logo inside it (if the above procedure doesn't work)
4. Are there different variants of P8 Lite like P8lite 2017 , etc. ?
Click to expand...
Click to collapse
1. I am able to create a new "oemlogo.mbn" and a "flashable_logo.zip" through your tool but unfortunately the stock boot logo of Huawei still shows up in every reboot, after using the two files.
2. The zip file works in TWRP Recovery and was flashed without errors but the stock boot logo still shows upon reboot then after rebooting, I checked /product/etc/logo/ and the stock oemlogo.mbn was not replaced with the new one.
3. Here is the oeminfo.img backup, by using this command in a terminal emulator
Code:
su
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img
and this one is the raw file itself. I only used two out of three methods of backing up the oeminfo partition based from this thread because I was unsure as to where in TWRP Recovery should I find the backup for oeminfo partition since it only has the options Boot, Cache, Data, System and Vendor for backup. Maybe in the "Vendor" partition, but the backup size is 394 MB.
4. I'm not sure for the variants of Huawei P8 Lite, maybe only Huawei P8 Lite (2017) and the ones on the "download section" in this link? If you meant the Huawei P8 Lite (2017) variants, the ones I know are Huawei P8 Lite (2017) PRA-LX1, PRA-LX2, PRA-LX3, PRA-LA1 and PRA-TL00. I'm using the Huawei P8 Lite (2017) PRA-LX2.
I've also tried copy pasting the new oemlogo.mbn then changed it to the correct permissions (-rw-r--r--). I even tried renaming it to "oemlogo.mbn.bak" to see if there's any change but it seems that this file is not in control of the boot logo. We also have the boot warning logo too by the way, the one that is caused by unlocking the bootloader.
Here is my own logo.bmp boot logo, 1080x1920 resolution, edited through Gimp 2 and exported as .bmp file format.
Edit: Does anyone know where is the exact location for our boot logo files? I've also found the same oemlogo.mbn file on some folders in /product/hw_oem
@CrimsonBloodfang
The oeminfo.img file had the pictures as I guessed.
I have updated the OP with the new tool. Please check if it's working
Also, I think the files in the '/product/hw_oem/whatever' directory are created from the oemlogo partition while booting (not sure though).
So maybe using the old tool, setting the permissions for oemlogo.bin as -r--r--r-- might have worked (since write access is denied).
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Thanks! I will be testing it now.
GokulNC said:
@CrimsonBloodfang
Edit:
As specified in GSMArena website, is it true that P8 Lite (2017) is also called Huawei P9 Lite (2017), Huawei Honor 8 Lite, Huawei Nova Lite, Huawei GR3 (2017) ???
If yes, this tool MIGHT work for those devices too.
Click to expand...
Click to collapse
Yes, it is called with different names from different countries and they are more or less, just the same devices.
In the Philippines, this phone is called the Huawei GR3 (2017).
Edit:
Maybe the users need to backup their own "oeminfo.img" first before using the tool and can you add it on OP? They might use my device's oeminfo.img if they forgot to backup and it might change their device's region settings then their stock updates would be based from my country.
I haven't rebranded my phone, just went straight to LineageOS 14.1 so I'm not sure about the consequences of flashing other oeminfo.
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
@GokulNC
It also didn't work for me. I've tested it six or more times with both the Terminal Emulator and the TWRP Recovery flash method.
Edit:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder. Then flashed the six different files of oeminfo.img and flashable_logo.zip with Terminal Emulator and TWRP Recovery, but on every reboot, the boot logo is still at stock.
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
CrimsonBloodfang said:
The only locations left I can guess as to where the boot logo files for Huawei P8 Lite (2017) are maybe in the Boot partition or it's embedded in the Kernel.
Click to expand...
Click to collapse
Nope, I don't think so..
MIcHiJK said:
Is that working with all variants of the p8lite 2017? I rebranded mine to the Chinese Honor Version.
Click to expand...
Click to collapse
I'm not sure if the oeminfo partition is same across all the different firmwares.
I guess they all must be the same. If you can attach your stock 'oemlogo.img', I'll take a look at it.
CrimsonBloodfang said:
The logo file in "pics" folder of the tool has a logo.png and not anymore a logo.bmp, so I tried both file formats just in case. I've tried replacing it with logo.bmp, I've tried replacing it with logo.png and I've tried placing both logo.bmp and logo.png together on the "pics" folder.
Click to expand...
Click to collapse
My tool automatically converts everything to .bmp format, so it doesn't matter
Striike said:
still not working for me. Now it's just booting into eRecovery and the logo was changed to the original one
Click to expand...
Click to collapse
I'm not sure about the rebranded device. Can you please attach your 'oeminfo' file?
I'll check that out.
GokulNC said:
@CrimsonBloodfang
Actually there were many .bmp pics inside the oeminfo.img
I didn't look at that properly.
When I extracted them, I saw 2 bootlogo images.
So I've modified the tool to change them both.
Try the new tool that I've uploaded now and see if it's working
It should contain 2 files named logo1.png and logo2.png
Click to expand...
Click to collapse
Ok, I've flashed the flashable_logo.zip using the new tool and it seems to work. Boot logo is not anymore the stock one but instead, it's replaced by a "glitched image" with a color green background and two rectangles with colors pink and blue, not the boot logo I made. Boot warning sign is still there afterwards though.
It may be a wrong procedure on my part because I just placed my logo.bmp together with the logo1.png and logo2.png but I will continue tinkering and testing it or have a lower file sized image to see if I can finally get the desired boot logo.
---------- Post added at 11:04 PM ---------- Previous post was at 10:52 PM ----------
Also flashed my backup oeminfo.img through Terminal Emulator or TWRP Recovery and everything went back to normal.
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
CrimsonBloodfang said:
@GokulNC
Tested it many times, boot logo always end up with the "glitched image" as attached below.
This is not the original image. Just an edited image through Gimp 2, for reference.
Click to expand...
Click to collapse
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
GokulNC said:
Does this arise after changing the logo2.png (or logo2.bmp)??
Is that the same output no matter what the logo2 is?
I mean, even for the default one that I've placed in pics folder or what you replaced with, is the output the same weird image??
FYI, ensure there are only 2 images in the pics folder while creating the oemlogo.img, ie, logo1.<whatever_format> and logo2.<whatever_format>
Click to expand...
Click to collapse
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Lenovo' boot logo which is displayed when device is switched ON)
This is for Huawei P8 Lite 2017 Only.. (Resolution 1080x1920)
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Huawei P8 Lite 2017 (any ROM)
2. Optional:Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create boot logo:
1. Download & Extract this in computer: Huawei_P8_Lite_2017_Logo_Maker.zip
2. Make sure you have a picture in BMP format with resolution exactly1080x1920px. (Can be of any format)
3. Now rename your picture as logo.bmp & replace it inside "pics" folder of the extracted folder. (Or directly edit the 'logo.bmp' file)
4. Finally, run the 'CREATE_LOGO.bat' to create oeminfo.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash boot logo:
Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_logo.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the oeminfo.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
c. To flash from Fastboot mode:
Finally, Reboot and check if the bootlogo has changed!!
Note:
Incase something goes wrong or device doesn't bootup, just flash the stock oemlogo.img from custom recovery or fastboot.
Credits:
1. @CrimsonBloodfang who provided the stock oemlogo.img of P8 Lite 2017 (PRA-LX2)..
[email protected] (myself ) who wrote this script
Hit the Thanks:good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
Thanks bro
Very useful guide
CrimsonBloodfang said:
Yes, I've already tried different ways like replacing only the logo2.png or replace both images and also ensured there are two images in the pics folder.
I also tried using only the "default images" and did not replace anything in the pics folder, then flashed the newly created files and the resulting boot logo is still the glitched image.
Edit:
The image in this post is what the glitched image of the boot logo, actually looks like.
Click to expand...
Click to collapse
Hi, sorry for my late reply. Got stuck up with something lately.
I have attached a new tool, with little changes.
Please check if it's working.
If it doesn't, I'm not sure what else to do.
honorfan said:
Thanks bro
Very useful guide
Click to expand...
Click to collapse
Hi, did this work for you?
Thanks, I will be testing it later. I've also found out from another user that changing the boot logo using the tool, has stopped working in Nougat and Oreo.
Here is what he said, and this thread is also changing their Huawei device using the oeminfo partition.
Maybe you already know these?
@GokulNC
Tested it twice, it's still showing the glitched image.
My first attempt was replacing the logo2.png with another image as logo2.bmp. Flashed the files through TWRP Recovery, rebooted and the result is still the glitched image.
Second attempt was to not replace anything in the "pics" folder. Created the files, flashed them in TWRP Recovery, rebooted and the result is still the same.
I've been searching around xda forums for information about editing Huawei's oeminfo for its boot logo image and I noticed that their tutorials needs to follow a "specific RGB format" when editing the images to be used as a boot logo. (Bitmap file with color depth not less than 16 bit, supported color schemes: RGB555, RGB565, RGB888, RGB8888)
Although, I'm uncertain that this might be the cause of the problems and I haven't tried it yet.
- Follow any of the RGB formats to fix the problem.
I've only tried "RGB565" and "RGB888 with color depth of 24 bits".
On the other hand, seeing the "glitched image" as a boot logo, might just only be an indication of a corrupted oeminfo, when it's not properly recompiled or reconstructed?
Just to be sure, I'll place the links of the threads and posts, that I think might be useful for reference.
You might have already read these threads before.
- How To Change The Splash Screen or Boot Logo In Huawei Honor 7 at post #2
- Scroll down to Part VII - How To Change The Splash Screen
- Solution by Kostyan_nsk
- [HOW TO] Replace initial splash screen (logo) on Huawei P7
- [GUIDE] Changing boot splash image on the Huawei Y6
I will try changing the RGB formats for the image that I'll be editing, to see if it makes a difference.
I've been looking for a way to change my A2's splash screen for a while. Tried using tools available for other Mi devices such as GokulNC's Redmi Note 5 toolkit (https://forum.xda-developers.com/re...guide-how-to-change-boot-logo-splash-t3787820) and they worked for replacing the splash screen, but the fastboot image (Xiaomi bunny) was broken in the process, leaving fastboot mode only with a black screen. So I decided to take matters into my own hands and voilà, managed to change both splash images. In this guide I'll explain how.
Edit: since posting this I've made a simple cmd script for automatically generating the splash.img. For the old tutorial check out this post's edit history.
Prerequisites:
Mi A2 with unlocked bootloader
Windows machine with working fastboot executable
Tutorial:
Download a2 splash generator.zip from this post and extract it to its own folder
Replace the .bmp files with the desired images
1.bmp is the default splash logo that shows up when you boot your device
2.bmp is the image for fastboot mode
3.bmp can be left alone as its probably unused (the unlocked warning is now baked into the bootloader itself)
4.bmp is the splash logo with unlocked padlock. You probably should make it a duplicate of 1.bmp
Run generate_splash.cmd. It will make newsplash.img in the same folder
Put your phone in fastboot mode and run the command
Code:
fastboot flash splash newsplash.img
You may now reboot the phone and check the your all new splash and fastboot screens!
If it doesn't work, make sure the resolution of your BMPs is 1080x2160 and save them in Paint as 24 bit bitmap files. Then run generate_splash.cmd and flash the image again.
with this guide you can remove the message that the bootloader is unlocked?
Julio_MotoMod said:
with this guide you can remove the message that the bootloader is unlocked?
Click to expand...
Click to collapse
Na u can not. Unlocked bootloader message is shown from boot loader itself.
To anyone is using a UNIX or UNIX like OS, to generate the image just run
Code:
cat header.img 1.bmp empty.img 2.bmp 3.bmp 4.bmp empty.img > splash.img
Awesome! I was just looking for that. After swaping roms from MIUI to AO I lost my fastboot logo and it was only showing a black screen, Thanks!
In case someone wants to grab the original image files:
Code:
dd skip=16384 count=6998454 ibs=1 if=splash.img of=1.bmp
dd skip=7014840 count=6220854 ibs=1 if=splash.img of=2.bmp
dd skip=13235694 count=6998454 ibs=1 if=splash.img of=3.bmp
dd skip=20234148 count=6998454 ibs=1 if=splash.img of=4.bmp
The generated image matches with 10.0.2.0 stock's splash.img (MD5: EE57036E7626DA5DEFC276F428D7FBE9).
Files are attached.
EDIT: The unlocked bootloader warning is not stored in splash.img (run fastboot erase splash and see yourself), modifying this will not change that
I was waiting for this to create my own bootanimation. I want to share that with you guys if possible.
should i post a reply here or create an other thread(m not familiar with rules). Before this all i have done is explore xda
The bootanimation is of goku (complete UI) though!
@prokaryotic cell This tool break Xiaomi Bunny in the process
YouTube ban guy said:
@prokaryotic cell This tool break Xiaomi Bunny in the process
Click to expand...
Click to collapse
Delete 3.bmp and 4.bmp, run the tool, and it works. Even the stock splash, the one I backup from my device, break xiaomi bunny.
EDIT: lmao i know why mine wont work, because i do the steps incorrectly. you don't have to delete 3 and 4 bmp. but if this post helps you anyway then okay
ARNOB XENON said:
Na u can not. Unlocked bootloader message is shown from boot loader itself.
Click to expand...
Click to collapse
Do you know since when it changed this way? Is it possible to use an older bootloader to avoid the unlocked warning?
Embeeweezer said:
Do you know since when it changed this way? Is it possible to use an older bootloader to avoid the unlocked warning?
Click to expand...
Click to collapse
Yeah, it will be really amazing if someone can make a mod to "hide" the unlocked bootlader thing.
Hey op do you know how to do it for wayne?
fchrkbr said:
Hey op do you know how to do it for wayne?
Click to expand...
Click to collapse
Sooo after few hours playing with hex editor (and actually figuring how to read those hex), I figured out how to do it for 6x! Turns out the composition of the 6x splash is header+logo+fastboot+corrupt+logo-unlocked, rather different than a2 which has 2 bytes of empty file in between logos. Oh, AND for 6x it uses 1080x1920 24bit bmp instead of 1080x2160, idk why
I edited the generator script from op, you can download it below, and how to do it is exactly the same except it has to be 1080x1920 24bit bmp
If OP would take the file to the first page so it's easier to find, it'd be delightful
View attachment 6x_splash_generator.zip
I tried in mi6x(converted mia2) but even if I change 4 files with different images only 1.bmp shows in booting and fastboot is black
fchrkbr said:
Sooo after few hours playing with hex editor (and actually figuring how to read those hex), I figured out how to do it for 6x! Turns out the composition of the 6x splash is header+logo+fastboot+corrupt+logo-unlocked, rather different than a2 which has 2 bytes of empty file in between logos. Oh, AND for 6x it uses 1080x1920 24bit bmp instead of 1080x2160, idk why
I edited the generator script from op, you can download it below, and how to do it is exactly the same except it has to be 1080x1920 24bit bmp
If OP would take the file to the first page so it's easier to find, it'd be delightful
View attachment 4698907
Click to expand...
Click to collapse
Fastboot is broken. Stays black. Rest works.
ktlk21 said:
I tried in mi6x(converted mia2) but even if I change 4 files with different images only 1.bmp shows in booting and fastboot is black
Click to expand...
Click to collapse
Letzen said:
Fastboot is broken. Stays black. Rest works.
Click to expand...
Click to collapse
Huh, weird, you guys on relocked bootloader? I'm sure when it boots it shows 4.bmp, not 1.bmp. Or is your device native 6x (not a2 converted)? It works on my converted a2, but I'll look to it. Maybe it does need empty file.
fchrkbr said:
Huh, weird, you guys on relocked bootloader? I'm sure when it boots it shows 4.bmp, not 1.bmp. Or is your device native 6x (not a2 converted)? It works on my converted a2, but I'll look to it. Maybe it does need empty file.
Click to expand...
Click to collapse
Yes, it is native 6X.
DELETED
pretty awesome tool, thanks for making it. there is not way to replace too the boot animation?
prokaryotic cell said:
I've been looking for a way to change my A2's splash screen for a while. Tried using tools available for other Mi devices such as GokulNC's Redmi Note 5 toolkit (https://forum.xda-developers.com/re...guide-how-to-change-boot-logo-splash-t3787820) and they worked for replacing the splash screen, but the fastboot image (Xiaomi bunny) was broken in the process, leaving fastboot mode only with a black screen. So I decided to take matters into my own hands and voilà, managed to change both splash images. In this guide I'll explain how.
Edit: since posting this I've made a simple cmd script for automatically generating the splash.img. For the old tutorial check out this post's edit history.
Prerequisites:
Mi A2 with unlocked bootloader.
Click to expand...
Click to collapse
I have locked bootloader, and fastboot screen is black.What will i do?