How to change the boot logo on your MTCD/MTCE device - MTCD Software Development

I was always kinda annoyed by the not matching boot logo. After the loader I could change the logo to the car manufacturer but the first seconds still showed "On vehicle navigation system". After installing the Malasyk 8.0 ROM I recognized a different boot logo. So a change was possible. After some playing around with various ROM tools I was able to change the logo (sorry, I don't remember the exact steps). After switching to the HAL9k ROM, the changed logo was gone. The old method didn't work with HAL as the boot loader with the logo was part of the signed update.zip and changing the logo of course breaks the signature.
So I played round with dumping various partitions and check for the logo. There is a way to change it:
NOTE: The slightest mistake in one of the steps WILL brick your device!!!
1. Dump the bootloader partition
2. Find the logo in the dump
3. Replace the logo in the dump
4. Write the new bootloader parition
In general it is a good idea to connect to the device using adb on your PC as typing on the on-screen-keyboard is error prone. dd commands have to be executed as root.
1a. dd if=/dev/block/mmcblk2p4 of=/storage/ext_sd/mmcblk2p4.bin
Note: Depending on your ROM or device the partition might be different. So if you don't find the logo there, try other partitions. Also adapt the of argument. I wrote the file to the "Music" SD card.
1b. Write down the file size. In my case it was exactly 16MB.
2a. Search the dump file for the string "BM6". I used HxD and found it atoffset F800.
2b. Dump everything starting as this offset to a new file and name it with the extension BMP.
2c. Open it with your favorite viewer (I use IrfanView) and check if it is the correct logo.
2d. Check the resolution. In case of the HAL9k 3.1 ROM it should be 800x480x24, for Malasky it was 1024x600x24
2e. Save the file there to a different name.
2f. Check the new file size. In case of the HAL9k 3.1 ROM it should be 1152054 bytes
3a. Create a logo of your choice with exact the same resolution.
3b. Check the file size. It must be identical to the one of the dumped BMP
3c. Replace the data in the compete dump. Make sure, you use the correct offset and use replace, not insert.
3d. Save the new dump and compare the file size. It must not be changed!
4a. Copy the file back on the SD card
4b. Write it back: dd of=/dev/block/mmcblk2p4 if=/storage/ext_sd/mmcblk2p4.bin
Note: if and of is now switched!
4c. Reboot

Just did mine in Hal9k rom.Thank you
Sent from my iPad using Tapatalk

NOTE: The slightest mistake in one of the steps WILL brick your device!!!
Hi,
just a thought of safety..
is it not better that you change that -boot- logo for all cars so that "everybody" can choose his car logo, instead or to prevent that men would make some a mistake which wouldl brick his headunit?
https://www.google.com/search?q=and...KHQHTDu8QsAR6BAgEEAE&biw=1280&bih=726&dpr=1.5

Thanks for this!
In my case, it was mmcblk2p7.
At first, I had a black screen, but file size and resolution was correct.
Somehow, I managed to boot the device again and then I tried another picture and it worked.
I don't know the difference between my first and second try...but I'm lucky that my device isn't bricked.
Maybe we find a safer way for this...

rezi09 said:
Thanks for this!
In my case, it was mmcblk2p7.
At first, I had a black screen, but file size and resolution was correct.
Somehow, I managed to boot the device again and then I tried another picture and it worked.
I don't know the difference between my first and second try...but I'm lucky that my device isn't bricked.
Maybe we find a safer way for this...
Click to expand...
Click to collapse
Great example of New member joining, reading articles, giving it a go and reporting back.
Wonderful but rare.

marchnz said:
Great example of New member joining, reading articles, giving it a go and reporting back.
Wonderful but rare.
Click to expand...
Click to collapse
Well, I'm new since 2009
Thx...it's a great forum with great people!

Pls support

Related

[Guide]Installing Custom Splash Screens (Revised 10/1/11)(Works for all hboots)

*updated 2/2/2011*
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt. Also, HUGE thanks to Stoney 666 for giving me the software to convert images to .rgb565 and to CYBERxNUKE for creating it.
*Note*
all filenames in this process are case sensitive. Don't capitalize it if it's not capitalized and don't lower case it if it's not lowercase. Also, do not add extensions unless you're instructed to. Doing any of these can mess up the process.
**UPDATE 10/1/11**
Updated a working PC36IMG.zip (in the attachments in the bottom). The last one was corrupt and the Unrevoked website goes down sometimes.
**UPDATE 10/24/11**
Added up a pro tip for people who want to make their own Splash screens and not just make their own Splash PC36IMG.zip.
Okay, rewriting this process from scratch because, well it's easier that way.
PART 1 (if you downloaded a splash screen image from the Themes and Apps Section of the Evo forums in XDA, the proceed directly to PART 2).
1. Download the EVOSplash Zip from the attachments.
2. Open the howto.txt file inside for instructions on how to use it. With this program, you can convert a file into the required .rgb565 file.
3. Rename the converted .rgb565 file splash1.img
PART 2 (if you have your file all ready to go)
*note* if you have not done so, rename the splash picture to splash1.img
1. Go to this website: http://unrevoked.com/rootwiki/doku.php/public/forever
2. Download the original PC36IMG.zip file (it's close to the bottom)
3. Use a .zip editor (winzip, 7zip, etc) to open it.
*ehem* DO NOT EXTRACT, JUST OPEN
4. Replace the splash1.img in the zip with the one you have/just made. Save it.
5. Plug your phone in, connect to PC via disk drive.
6. Put the PC36IMG onto the root of your SD card (for newbies, that's the very first page of the SD card).
7. Reboot phone into bootloader (turn off, volume down + power)
8. The phone should recognize the zip and ask if you want to update. Select yes (I believe it's volume up for yes).
The zip will install and you're new splash screen should be there next time the phone reboots.
I hope this helps a lot and thanks to everyone who's read it and been patient. It took me a month to thread jumping before I found a process that worked with hboot 2.02 and 2.10 (I have 2.10). This is also the easiest way for people who are uncomfortable with adb and the command prompt.
Give me a thanks if it helped, I do this for free so I don't accept donations
**PRO TIP**
If you want it to fit the whole screen (or to make your own from scratch), use a photo or paint like program (Photoshop, etc). Make a new file that is 480 pixels wide and 800 pixels for height. Then re-size the picture you want to use in it (another tip: use a picture that is bigger than 480x800. If it's smaller, it'll get fuzzy and become lower quality) to fit the borders of the new file. Alternatively, you can make your own. Save as JPEG when you're done, then follow the instructions above.
Followed the process, it's not working for me. I don't get a prompt to update in hboot. PC36IMG.zip is on the root of my SD card. =/
EDIT: When I boot back into CM6 and look at the root of my SD card the .zip is gone...
EDIT2: Diagnosed and fixed, had to make the PC36IMG.zip rwx-rwx-rwx. Flashed just fine!
what about users with hboot 0.93.0000?
AbsolutZeroGI said:
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt.
Okay here we go. This process is to install custom splash screens without having to use the command prompt or fastboot. Users who have hboot 2.02 and 2.10 CANNOT use the command prompt anyway so this is the workaround for those people.
1. Download the PC36IMG.zip from the attachments.
2. Find the splash screen you want and rename it splash1.img (don't worry about any warnings about it not being usable, Android is smarter than Windows).
3. Open the .zip and delete the splash1.img that's already there and replace it with the one you downloaded.
4. Plug your phone in, select "disk drive".
5. Move the .zip file into the first page (or root page) of your sd card.
6. Remount sd card (not necessarily important, but recommended).
7. Power Down
8. Load into Hboot (volume down + power)
9. Hboot will recognize the .zip as an update and will ask if you want to install it, hit volume up to install.
10. Reboot and enjoy your new splash screen.
If this gets a sticky, so be it, if not, I am going to PM the OP of the sticky'd thread with all the splash screens and ask him if he'd put this guide in there.
I hope this helps some people, it sure helped me.
Click to expand...
Click to collapse
you forgot to mention that the image used for the splash needs to be in .rgb565 format before renaming it to splash1.img, and has to be saved as a 24bit rgb bmp or png file before converting to .rgb565.... use this to convert the images to .rgb565 View attachment EVOSplash.zip there is also a "how to" in the zip.
or to make your life easier, go here... http://forum.xda-developers.com/showthread.php?t=812572 and i'll make one for you...
Stoney 666 said:
you forgot to mention that the image used for the splash needs to be in .rgb565 format before renaming it to splash1.img, and has to be saved as a 24bit rgb bmp or png file before converting to .rgb565.... use this to convert the images to .rgb565 View attachment 481035 there is also a "how to" in the zip.
or to make your life easier, go here... http://forum.xda-developers.com/showthread.php?t=812572 and i'll make one for you...
Click to expand...
Click to collapse
Thanks, all the splash files i've downloaded so far have been in .rgb565 so far but this is definitely useful information, especially if people want to make their own.
meansixx said:
what about users with hboot 0.93.0000?
Click to expand...
Click to collapse
This is compatible with all hboots. It's just that people with the two newest ones can't use any other method (to my knowledge) except this one so I thought it was guide worthy. Most of the threads that have splash screens have alternate instructions.
*bump*
people still need this, I wish I could get it sticky'd
problem installing splash screen
I am having the same problem as above, I have read alot on this fourm and still cannot get a different splash screen up. Im looking to install the stock flash for the evo. I'm getting an error no image found please help.
Thanks...
I found
a flashable zip of the stock splash screen, and it worked, but I would still like to know how to do this. I wanted to put on the red evo skelton giving the finger.
pgagolfer said:
a flashable zip of the stock splash screen, and it worked, but I would still like to know how to do this. I wanted to put on the red evo skelton giving the finger.
Click to expand...
Click to collapse
When you add the image to the Evo, make sure it's in it's native resolution (my instructions only cover splash screens from this forum, which is 800x480).
For further info, read Stoney 666's post, that's how you do it if your image doesn't start in the right file type.
Thanks.
Got it to work, not sure how, i think i used a different PC36IMG file, or I took zip off the ending.
pgagolfer said:
Got it to work, not sure how, i think i used a different PC36IMG file, or I took zip off the ending.
Click to expand...
Click to collapse
Even if you take off the .zip it's still a zip so one way or the other it works I just uploaded the PC36IMG file I found on the Unrevoked website.
Glad you got it to work!
Ok, I'm not doing something right. I downloaded the PC36IMG.zip, opened it, replaced the file with the splash screen I wanted, and re-zipped the file. Put it on the root of my sd card, and started it in bootloader. First, it didn't prompt me to update, although when it checked the sd card for updates, I did note that it said "parsing PC36IMG.zip", but then returned to the menu. I tried flashing it from recovery as well and it didn't work.
From all the stuff I've read this seems to be the method that makes the most sense and is easiest. I've tried flashing it via ABD and a whole bunch of other stuff to no avail; my computer must not like my phone.
What am I doing wrong, I followed your steps...
EDIT: I rooted phone with unrevoked...don't know if that is why. I know that has been a roadblock with some of the other methods of changing the splash screen.
Any possible way to get this turned into a flashable zip file? Im not good with adb!
wizholt7 said:
Ok, I'm not doing something right. I downloaded the PC36IMG.zip, opened it, replaced the file with the splash screen I wanted, and re-zipped the file. Put it on the root of my sd card, and started it in bootloader. First, it didn't prompt me to update, although when it checked the sd card for updates, I did note that it said "parsing PC36IMG.zip", but then returned to the menu. I tried flashing it from recovery as well and it didn't work.
From all the stuff I've read this seems to be the method that makes the most sense and is easiest. I've tried flashing it via ABD and a whole bunch of other stuff to no avail; my computer must not like my phone.
What am I doing wrong, I followed your steps...
EDIT: I rooted phone with unrevoked...don't know if that is why. I know that has been a roadblock with some of the other methods of changing the splash screen.
Click to expand...
Click to collapse
For 1 you don't have to unzip and re-zip. Just replace the image that's already in the zip. I think a couple of people have had this problem before. I'd try again without re-zipping the package.
Also, if you didn't get the splash screen from this section of the forums (i.e. you're using your own or from a different phone in xda), go to post #4 (on the first page) and read stoney 666's post about converting the file to .rgb565 and then renaming it (not convert, rename) it to splash1.img (yes, with the file extension).
Basically, from where you are, here's what I'd do:
attempt to just replace the splash1.img file in the zip without unzipping and try again. Or, try downloading the original, untainted one here: http://unrevoked.com/rootwiki/doku.php/public/forever
and follow the steps over again.
if that doesn't work:
follow stoney 666's instructions and convert the image to .rgb565 format and then rename it to splash1.img.
That should do it.
I will also post that link in the OP and tell people to get the original instead of using mine as people have been having trouble with it.
luist4498 said:
Any possible way to get this turned into a flashable zip file? Im not good with adb!
Click to expand...
Click to collapse
I revised the instructions on the original post, it should work for you. It's not flashable in recovery, but it's flashable in bootloader which is just as good (don't need clockwork or ra recovery to do it).
I tried it again adding the file to the zip instead of unzipping, rezipping, and no dice. I'll download the PC36IMG file from unrevoke's website and see if that works.
EDIT: I just downloaded the one from unrevoked's website, and I noticed the image file it has in there by default is "splash1.img". The name of the file I am inserting is "evosplash1.rgb565". That is the correct file name, right?
Also, I just tried it with the file from unrevoked's website, still no luck. It just says "parsing PC36IMG" but doesn't do anything and returns to the bootloader options...
Ok, so I finally got it figured out, thanks to moseso. Apparently, it was because the name of the file was wrong. As I understood it, the file was to be named evosplash1.rgb565 . But I had to rename it to splash1.img . I guess it was a misunderstanding on my part, idk. But I got it now. Here is the link to the thread if anyone wants or needs it: http://forum.xda-developers.com/showthread.php?p=11113102#post11113102
wizholt7 said:
Ok, so I finally got it figured out, thanks to moseso. Apparently, it was because the name of the file was wrong. As I understood it, the file was to be named evosplash1.rgb565 . But I had to rename it to splash1.img . I guess it was a misunderstanding on my part, idk. But I got it now. Here is the link to the thread if anyone wants or needs it: http://forum.xda-developers.com/showthread.php?p=11113102#post11113102
Click to expand...
Click to collapse
It says in the OP to rename the file and always has.
Glad you got it figured out.
AbsolutZeroGI said:
*updated 2/2/2011*
First, props to silentstryder for putting up the process. I'm just giving it it's own thread for the newbies, users with the new hboots (2.02 and 2.10) and for people who just plain don't like command prompt. Also, HUGE thanks to Stoney 666 for providing the software to convert images to .rgb565.
*Note*
all filenames in this process are case sensitive. Don't capitalize it if it's not capitalized and don't lower case it if it's not lowercase. Also, do not add extensions unless you're instructed to. Doing any of these can mess up the process.
Okay, rewriting this process from scratch because, well it's easier that way.
PART 1 (if you downloaded a splash screen image from the Themes and Apps Section of the Evo forums in XDA, the proceed directly to PART 2).
1. Download the EVOSplash Zip from the attachments.
2. Open the howto.txt file inside for instructions on how to use it. With this program, you can convert a file into the required .rgb565 file.
3. Rename the converted .rgb565 file splash1.img
PART 2 (if you have your file all ready to go)
*note* if you have not done so, rename the splash picture to splash1.img
1. Go to this website: http://unrevoked.com/rootwiki/doku.php/public/forever
2. Download the original PC36IMG.zip file (it's close to the bottom)
3. Use a .zip editor (winzip, 7zip, etc) to open it.
*ehem* DO NOT EXTRACT, JUST OPEN
4. Replace the splash1.img in the zip with the one you have/just made. Save it.
5. Plug your phone in, connect to PC via disk drive.
6. Put the PC36IMG onto the root of your SD card (for newbies, that's the very first page of the SD card).
7. Reboot phone into bootloader (turn off, volume down + power)
8. The phone should recognize the zip and ask if you want to update. Select yes (I believe it's volume up for yes).
The zip will install and you're new splash screen should be there next time the phone reboots.
I hope this helps a lot and thanks to everyone who's read it and been patient. It took me a month to thread jumping before I found a process that worked with hboot 2.02 and 2.10 (I have 2.10). This is also the easiest way for people who are uncomfortable with adb and the command prompt.
Give me a thanks if it helped, I do this for free so I don't accept donations
Click to expand...
Click to collapse
maybe a really stupid question, as i can be known for those but i can be a worry wart. im using miui 1.8.5 on tiamat-evo 4.0.6 w/ sbc, and im just curious, is reflashing the stock pc36img.zip (after my file replacement, ofc) going to change ANYTHING else on my phone? been having a hell of a time keeping it running lately and i WANT to do this, but now im leery of EVERYTHING...

Splash screens.

I tried to use splash flasher to flash some screens but on boot the image is scrambled?
{LCD}Stelios said:
I tried to use splash flasher to flash some screens but on boot the image is scrambled?
Click to expand...
Click to collapse
Are you use a right 24 bit bmp format?
Tried ones that I had on my DHD.
Had the same problem; Here's a quick how to:
Make sure your image is sized as 540x960 (so you'll lose a bit off of the sides, since the aspect ratio is different vs. the usual 480x800 that many HTC devices have been).
Use the 2nd option of SplashFlasher 1.0 to convert the PNG you have to custom.img. Ignore the warning that says the file should be a certain resolution.
Take the custom.img file and copy it into your fastboot directory. Rename it to new_splash.img
do this:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
(credit to jbrew78 at http://forum.xda-developers.com/showthread.php?t=1171290)
You should be all set! For some reason, the splashing from splashflasher doesn't work with our devices, but it's converting tool is the easiest for me.
This is my first attempt at a how to, so please let me know if there's anything I could help clarify, or if it doesn't work/what step you get stuck on.
Hope it helps!
Cheers for that bud, yeah the tool is handy it is a shame that it doesn't work with the Sensation. Just need to find out what I have messed up with the bootanimation now.
I put a new one in and now I can't work out how to do it again lol?
And that was really easy to follow and helpful thanks.
i use this way and it works
http://forum.xda-developers.com/showthread.php?t=1194690

[Q] Getting .img from phone

Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
rhodesbauer said:
Hi folks.
I have an unusual smartphone from a Brazilian manufacturer, CCE, who have been bought for Lenovo.
This manufacturer are not exactly knowed for their support our product quality and I'm prety sure my device will not be updated or suported for any longer.
It's the SK504 and I want to try to customize the rom, build tunning apps (battery consumption sucks) and things like that. I have a good programming backgroung but not for mobile devices so I'm stepping on eggs for now.
The first thing I tried to do was get a backup from my actual rom so if I mess with something I shouldn't I would be able to come back to a working version through fastboot.
long story short, I managed to obtain through romdump 5 files; checksum.md5, config.gz, system.info.gz and system.tar
but, in the posts I been reading, it gives me the idea that I should get a boot.img, a recovery.img and a system.tar.gz
And with this I would be able to generate my own system.img through a different process.
Since I'm not being able to find what I did wrong, can anyone tell me if there are a different way to get those boot.img and recovery.img?
I tried the "adb backup -f boot.img boot" but it generates a 1kb .img file and I don't believe this is a valid boot.img.
Click to expand...
Click to collapse
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
qwertyu123 said:
Instead of making a backup, have you tried to find original restore image? Usually it is a an .IMG file.
Click to expand...
Click to collapse
I used Root Explorer to look for both, recovery.img and *.img.
No result.
try this http://forum.xda-developers.com/showthread.php?t=2450045

Alternative BOOT LOGOS for your 5X

Tired of looking at that honor 5X standard boot logo? Well here are 8 different ones I've made for you to chose from. This has been a bit of a challenge due to the different and occasionally strange 5X OS. I must thank @deadman96385 for pointing me in the right direction to where the 5X has it's boot logo stored.
Before using you must be aware that it is possible to soft brick your device, however I have changed my own boot logo 8 times using each one of the posted examples successfully.
At this point I must emphasise that I am not responsible for any ills that may befall your device, including soft and hard bricking through to Aliens landing, mating with your dog and then trashing all your devices.
It is not possible to upload .mbn files to XDA, therefore I have renamed the file extensions to .img, AS SOON AS YOU DOWNLOAD THE FILE rename the extension to .mbn
UPDATED 2/23/2016
I've had a request to give a guide for creating the oemlogo.mbn files to complement what I posted in respect of installing new boot logos. To keep it in logical order I have done a rewrite of the first guide and put in the new points at the appropriate places. If you are not bothered about making your own .mbn files but instead are just happy to use ones that I or anyone else post then you can just pick up at the appropriate point in the install part of the guide.
To create .mbn files for the honor 5X you will need the following..... (1) A graphics manipulation program - the one I use is the free "Paint.net" which can be downloaded from their web site at http://www.getpaint.net/index.html..... (2) You will also need a program which can remove the 54 byte header from .BMP files. Those of you proficient in code/scripting can probably do this with a good hex editor but I needed to find a program to do it for me. I use "bmp-header-remover.exe" from here http://karpolan.com/software/bmp-header-remover/ .... to be honest there is a lot of dispute and controversy on the Web about this type of program so I won't tell you to use it but for what I wanted it did the job.
When you get to the installation stage you will need on your 5X a File Manager and a Terminal Emulator.
OK let's get started ....
1) Firstly you have to find an image you want to use, this can be any of these .JPG, .PNG, or .BMP, personally I prefer to work with .JPG's. Bear in mind that the 5X default image size is 1080 x 1920 so if you start with a small image let's say 300 x 300, by the time it has been blown up to the full 5X size you are going to lose some definition and you will likely get an unwelcome degree of distortion.
2) Open the "Paint.net" program and click on the heading "Layers" then on the drop down menu click on "Import from File" then in the window that opens, navigate to where your image is and click on it to open it in "Paint.net". Don't be disturbed by the size or appearance.
3) Click on the heading "Image" then on the drop down menu click on "Resize". In the "Resize" window that opens enter the size of 1080 in the width box and 1920 in the height box. Then click "Ok". Your image will now be resized to the 5X parameters.
4) At this point you can use the "Paint.net" tools to adjust colors or add text and if you experiment you should be able to stretch or contract the image to how you want it. I make no apology for the fact that I am not giving a guide to the use of "Paint.net" here (their help page should answer any questions you have).
5) Now comes the juggling bit. In "Paint.net" click on the heading "Image", a drop down menu opens so click on the choice "Flip Vertical". Your image now takes what I think of as an "upside down and inside out" aspect, you'll see that it's upside down and in effect is a mirror image.
6) Now you need to save the file. Click on the heading "File" and from the drop down menu click on "SaveAs". Now it is important to save the image as a .BMP file irrespective of whether you started with a .JPG or .PNG or .BMP original. In the "SaveAs" box "Paint.net" tends to default as its own file format(.PDN) so change this by selecting .BMP. At this time you can leave the filename as it is or change it, it doesn't matter. Make certain that it is being saved to the folder location you want then click "Save". The next screen you get is the "SaveConfiguration" window, on the left hand side of this window you must click on "24-bit", leave everything else alone and click on "OK". Exit out of "Paint.net".
7) Now you need to run the program "bmp-header-remover.exe". A small window opens up and you will see two empty slots (to be honest you only have to read the screen and you will see what you have to do). In the top slot enter the path to your newly created .BMP file - In the bottom slot enter the path and name that you chose for your modified file. ***VERY IMPORTANT - YOU MUST GIVE THE FILE NAME AN .MBN EXTENSION*** So just to emphasize in the top slot you will have a .BMP file and in the bottom slot you will have an .MBN file. Click on the button "Remove BMP Header" and you have successfully created your .MBN file.
Now we move on to the "INSTALLATION" phase
8) Transfer the .MBN file to your device putting it in whichever folder of your SD Card you prefer. Use your File Manager to copy or Move the .MBN file to the Internal folder...../cust/hw/usa/logo..... If you want to keep the standard boot logo (as a safety precaution), rename it now or it will be overwritten. Rename your new .MBN file to oemlogo.mbn and change the permissions to match the original.
9) Come out of File Manager and open your Terminal Emulator. At the $ prompt change into superuser mode by typing su and pressing Return/Enter. You will then get the # prompt.Type load_oemlogo press Return/Enter and several lines of text will display, when this stops exit out of Terminal Emulator.
10) REBOOT and enjoy your new boot logo.
I have posted .jpg's so that you can see what you are getting.
Thought I would knock up another one. Very simple this one. All above instructions apply. Works on mine. JPG shows what it's like.
metpolds said:
Thought I would knock up another one. Very simple this one. All above instructions apply. Works on mine. JPG shows what it's like.
Click to expand...
Click to collapse
Can you write a guide on how to make these properly?
deadman96385 said:
Can you write a guide on how to make these properly?
Click to expand...
Click to collapse
Hey @deadman96385 thanks for your post. I have been making boot logos and boot animations for my varied Android devices since 2012 and believe me when I say I have never come up with such a complicated way of dealing with them as that which is used by Huawei in it's EMUI operating/themed system, I think you might agree with me. Looking at my above instructions (just to INSTALL the darned thing) I am amazed that so many downloads have been made without a squawk about the complicated proceedure compared with a "normal" device using a flashable zip in recovery. That by the way is my ultimate aim (flashable zips) but so far very little success with my Edify scripting.
However even if I was successfull that would not tackle the problem of constructing the ".mbn" file which I'm sure is the point you are making by posting your query. @Deadman it is one of the weirdest and complicated set of steps I have ever had to take in order to create a file which I could "flash/load/push". On initially thinking about posting my method I am a little reluctant because I don't want to lead a possible "noob" into soft/hard bricking his/her device because of me. However I appreciate your interest and if you think it would assist the thread's community then I will do so. A word of warning, it will take me a bit of time to try and write in logical understandable steps the way to go.
metpolds said:
Hey @deadman96385 thanks for your post.
Click to expand...
Click to collapse
@deadman96385 ... please see my edit to post#1 this effectively changes the playing field for the moment.
TO ALL READERS ..... This post can be ignored now later events have overtaken it.
@deadman96385 ... Don't know if this has anything to do with anything ... In twrp recovery in the "Mount" section I have a partition named "cust" with an empty check box beside it. It is not possible to chose "cust" , the check box will not accept a click. If I use any "Install type" function i.e. install a zip or install an image or wipe Dalvic & Cache, although the function is "Successful" , I also get written several lines in Red (Error) text i.e. "Failed to mount '/cust' (Invalid argument)"
It may seem a remote possibility but is there any chance that the mount "cust" has anything to with my missing folders?
THIS POST CAN NOW BE IGNORED ..... My system was screwed up by the B140 update.
metpolds said:
@deadman96385 ... Don't know if this has anything to do with anything ... In twrp recovery in the "Mount" section I have a partition named "cust" with an empty check box beside it. It is not possible to chose "cust" , the check box will not accept a click. If I use any "Install type" function i.e. install a zip or install an image or wipe Dalvic & Cache, although the function is "Successful" , I also get written several lines in Red (Error) text i.e. "Failed to mount '/cust' (Invalid argument)"
It may seem a remote possibility but is there any chance that the mount "cust" has anything to with my missing folders?
Click to expand...
Click to collapse
I have installed the B140 update and all the directories are still their and I can still see the oemlogo.mbn from ES file explorer
clsA said:
I have installed the B140 update and all the directories are still their and I can still see the oemlogo.mbn from ES file explorer
Click to expand...
Click to collapse
@clsA ... much appreciate your post, it just about confirms my suspicions that all the problems I'm having result from my installation of B140. Had tentatively decided that today I would restore one of my twrp backups taking me back to B130 then let it settle down before maybe trying B140 again. Just in the rare possibility that anyone else is having the same issues as me, when I found the folders missing I re-created them but on reboot they were deleted again.
deadman96385 said:
Can you write a guide on how to make these properly?
Click to expand...
Click to collapse
@deadman96385 ... Will give it a go this week. Can't give an estimated day to finish it. Having problems with my own system.
@deadman96385 ... All problems resolved. Will work on the guide @clsA ... Thankyou for all your assistance..
metpolds said:
@deadman96385 ... All problems resolved. Will work on the guide @clsA ... Thankyou for all your assistance..
Click to expand...
Click to collapse
@deadman96385 ... Post #1 amended. Guide now explains how to create .mbn files as well as installing them.
Skull splash screen
I made one, if anyone is interested I may post some more when I make them. Remember to rename .img file to .mbn and to follow the install guide posted here. I also suggest to make a nandroid beforehand. My thanks for it to @metpolds for the tutorial, and I apologize if I messed up the upload this is my first contribution to xda. If you like or use the file please hit thanks I need em right now.
wickedesires said:
I need em right now.
Click to expand...
Click to collapse
@wickedesires ... Do like your skull, I'll try it out for a while. Glad my original post was of some assistance. As for "Thanks" don't stop breathing awaiting them. If you add them up you will find that my original 8 logos have been downloaded 954 times and you can see that 5 different people gave a "Thanks" throughout the thread. It would seem that the new phone has attracted a new breed of poster.
metpolds said:
@wickedesires ... Do like your skull, I'll try it out for a while. Glad my original post was of some assistance. As for "Thanks" don't stop breathing awaiting them. If you add them up you will find that my original 8 logos have been downloaded 954 times and you can see that 5 different people gave a "Thanks" throughout the thread. It would seem that the new phone has attracted a new breed of poster.
Click to expand...
Click to collapse
I'm glad you like it, I've use xda for so long I'm glad to finally contribute to the community a little bit. About the thanks, yeah I've noticed that in a few other places in the 5x forums as well. It'll be nice to have the prerequisites out of the way. Again thanks for your tutorials, as soon as I find a video or something I like enough to put the work into I'm going to make a bootani also. I've been fooling around with the 2 that came stock and you're right Huawei made all of this much more complicated than it needed to be or has ever been on any other device I've owned.
Rgb skull splash screen
I made a red version of the skull splash screen to go with the new boot animation, for some reason when installed they render a different color than what I made on the PC so when trying to nail down red I got green and blue also that I will post. Since they render a different color I can't provide accurate thumbnails but they are the color in the file name. Remember to rename to oemlogo.mbn, put in the correct folder, change permissions, and load with terminal emulator as per the tutorial. I may take a break from making any more until I see about making them into flashable zips.
wickedesires said:
for some reason when installed they render a different color ............. I see about making them into flashable zips.
Click to expand...
Click to collapse
@wickedesires ... Congrats on the logos. Regarding the color change - I vaguely remember that in the early days of making logos for the moto G, I and others ran into a similar problem. This turned out to be a problem in the script used, the particular graphics program used by the script changed the colors. However if you are using the program "Paint.net" for your graphics manipulation then that probably isn't the problem.
As far as flashable zips go, since February when I posted my first logos for the 5X I have been working, fairly regularly, on trying to create flashables. I keep on running into errors which is particularly aggravating because I don't run into problems with creating them for the moto G or the moto X Pure. I think it's as we have both agreed - the problem lies in the difference between the 5X EMUI coding compared to genuine Android.
@metpolds I'm actually using gimp,but I'll give paint.net a look. If you break any ground on flashable zips let me know, I'll do the same.
View attachment oemlogo.bmpmy oemlogo
linux33it said:
View attachment 3715579my oemlogo
Click to expand...
Click to collapse
@linux33it ... Thanks for adding your logo to the thread.
I see that you have this well in hand but I thought you might find this interesting anyway -
https://github.com/fedotawa/flash_oemlogo_u9500?files=1
Looks like it would be easy to modify if this helps.
Could start by commenting out the final load step, changing the resolution, feeding it a PNG, and see if it produces the same oemlogo.mbn as the same PNG run through your procedure.
I mention this because some of us don't normally run Windows.
Edit - now that I think about it, I may be able to get the original bootsplash as a PNG and then compare with the original Huawei mbn. I think I'll do that and get back to you unless you beat me to it.

[Guide] Change Xiaomi MIX 2S (polaris) boot logo

Sagit Logo Generator for Xiaomi MIX 2S
Thanks @wangchuanyes for test! https://github.com/moonheart/sagit-logo-gen/issues/1
First download this File View attachment sagit-logo-gen-MIX2S.zip
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM .
Source: https://github.com/moonheart/sagit-logo-gen/tree/MIX2S
Thanks @huhu2207 for advice (binwalker).
Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?
thiefxhunter said:
Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?
Click to expand...
Click to collapse
up
thiefxhunter said:
Nice tool !!!!! Awesome
Do we have limit about size(in mb) or size (in pixels) ?
Click to expand...
Click to collapse
Yes. You should keep the original image height and width, and color depth. If you see file size reduced after saving, it's okay as long as you do not change pixels and color depth.
I recall, for example, 01.bmp extracted is around 20M but after you save it it's just around 5M. Feel safe, it's correct.
The newly generated logo binary file should be 19.5M, according to my memory. I don't have that file on hand now.
And if you broke it, you'll end up with a strange bootloader UI (with volume keys to select different modes), but don't worry, just flash a correct logo.bin and you'll make it running again.
EraserKing said:
Yes. You should keep the original image height and width, and color depth. If you see file size reduced after saving, it's okay as long as you do not change pixels and color depth.
I recall, for example, 01.bmp extracted is around 20M but after you save it it's just around 5M. Feel safe, it's correct.
The newly generated logo binary file should be 19.5M, according to my memory. I don't have that file on hand now.
And if you broke it, you'll end up with a strange bootloader UI (with volume keys to select different modes), but don't worry, just flash a correct logo.bin and you'll make it running again.
Click to expand...
Click to collapse
Alright , thank you again for that awesome explanation . Have a nice week !
Anyone has a "Mix" logo just like the boot animation?
Hi , i don't know why
But whenever i flash the logo.img created by your program.(even when using images you provided)
It always booted into a weird bootloader interface.
i'm on miui 9.6 china.
Wonder if anything has to do with this?
Can you help fix it?
Thanks!!!
Hello,
I will use this to remove the "unlocked" message at boot.
It's possible to simply copy 01.bmp to 03.bmp then recompile the image? (I ask due to size of 01.bmp is higher than 03.bmp)
Thanks
bartito said:
Hello,
I will use this to remove the "unlocked" message at boot.
It's possible to simply copy 01.bmp to 03.bmp then recompile the image? (I ask due to size of 01.bmp is higher than 03.bmp)
Thanks
Click to expand...
Click to collapse
I'd like to do that as well, "unlocked" seems so damn wrong to be displayed
evronetwork said:
I'd like to do that as well, "unlocked" seems so damn wrong to be displayed
Click to expand...
Click to collapse
I've created this Mix2s image (https://mega.nz/#!51UDyQoT!3b9sL2j4dNDW8WUNck39xVfNNuClqED2rZGw7kU5ZQs) using the files from OP to remove the "unlocked" message on boot splash.
You can use it if you want...
bartito said:
I've created this Mix2s image (https://mega.nz/#!51UDyQoT!3b9sL2j4dNDW8WUNck39xVfNNuClqED2rZGw7kU5ZQs) using the files from OP to remove the "unlocked" message on boot splash.
You can use it if you want...
Click to expand...
Click to collapse
Ready to use file? hmm
So it's just "fastboot flash logo xiaomi_mix2s_logo_image_removing_unlocked_message.img"
How safe is this? did you use the very same file?
Of course, I have used the same file that I've uploaded to my mega and is working fine. You can use it or generate using the op generator, but in any case I'm not responsible if you brick your device, blah, blah, blah...
evronetwork said:
Ready to use file? hmm
So it's just "fastboot flash logo xiaomi_mix2s_logo_image_removing_unlocked_message.img"
How safe is this? did you use the very same file?
Click to expand...
Click to collapse
Nice, ill put my contact information to make it harder to sell if it gets stolen or lost
Any chance this can be updated for the new format? New logo won't overwrite the bootloader splash.
xumixu said:
Nice, ill put my contact information to make it harder to sell if it gets stolen or lost
Click to expand...
Click to collapse
Great idea, so:
Fastboot, boot image etc ...with details, orange fox(instead of twrp) with pin locked and rom locked displaying personal info
This won't be an easy sale if stolen(hopefully not)

Categories

Resources