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

Search This thread

DreckSoft

Senior Member
Oct 6, 2012
52
7
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
 
Last edited:

rezi09

Member
Dec 20, 2009
5
2
Vienna
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...
 
  • Like
Reactions: marchnz

marchnz

Senior Member
Nov 26, 2012
6,000
1,290
NZ
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...
Great example of New member joining, reading articles, giving it a go and reporting back.

Wonderful but rare.
 
  • Like
Reactions: rezi09

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    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
    1
    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...
    1
    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...
    Great example of New member joining, reading articles, giving it a go and reporting back.

    Wonderful but rare.
    1
    Great example of New member joining, reading articles, giving it a go and reporting back.

    Wonderful but rare.
    Well, I'm new since 2009 🤣
    Thx...it's a great forum with great people!
    1