Database Info

trying to unveil logo.png mysteries

Hi all
Well, it's probably stupid to want to change the boot logo but ... it's awfull and I want to understand. I know it's risky too ...
The facts:
- First, I identified how to save the file from photoshop to have the same binary file : Export for device with options transparency & no metadata & no color profile. Saving the original logo.png this way give the same one (binaries are exactly the same). Saving the file the standard way give different binary file.
- it's a 32bits png ( I think 24 bits colors+8bits transparency), in the header appears "Photoshop Image ready" so it was made with photoshop ...
- Then I tried to flash a simple logo.png (modded from original) with a size lower than 4kb like the orginal. Just puting the logo.png in a tar file and flashing as one package with Odin.
- At boot, the original black&white logo appeared ... hhhmmm, strange ! There was no warning message in Odin.
- Then I tried to flash a colored logo of 6Kb, a 100% transparent one lower than 1Kb, and ... same thing ... the original samsung logo appeared !
- I just made an image of /dev/block/bml3 (see attached) with dd command. The partition size for logo.png is 512Kb, so in theorry we can make a nice boot logo ...
- If you edit the attached file, you will see 2 strange things : GT-I8315HG01L phone model appears in the header (this information is not in logo.png), and the logo.png file appears twice in the partition !
?????????
Anybody wants to make the quest ?
it would be good to see if other people have the same partition structure, then just type:
dd if=/dev/block/bml3 of=/cache/bml3.bin bs=1
then pull it to your computer and have a look.

Ok now. You actually flashed bootloaders so many times just to check??

dhirend_6d said:
Ok now. You actually flashed bootloaders so many times just to check??
Click to expand...
Click to collapse
he actually flashed logo.png and not the bootloaders...

dharamg3 said:
he actually flashed logo.png and not the bootloaders...
Click to expand...
Click to collapse
The logo.png only comes into play when flashed with bootloaders I suppose. Correct me if am wrong.

dharamg3 said:
he actually flashed logo.png and not the bootloaders...
Click to expand...
Click to collapse
exactly !
When XXJPS appears it was an oportunity to test that so I flashed the whole package (with bootloaders and with my modded logo.png).
After that I only flashed logo.png.

sambastrakan said:
exactly !
When XXJPS appears it was an oportunity to test that so I flashed the whole package (with bootloaders and with my modded logo.png).
After that I only flashed logo.png.
Click to expand...
Click to collapse
you tried pushing logo.png in the bml partition?
P.S. which software did you use to check the .bin partion..?

dhirend_6d said:
The logo.png only comes into play when flashed with bootloaders I suppose. Correct me if am wrong.
Click to expand...
Click to collapse
I thought that too but this was my first try and ... nothing ...

dharamg3 said:
you tried pushing logo.png in the bml partition?
P.S. which software did you use to check the .bin partion..?
Click to expand...
Click to collapse
No ... I'm a little bit afraid to make that ...
and there is a header in the bml3 partition (which comes from where ???) so it's not easy to push the png at the right place ....

dharamg3 said:
P.S. which software did you use to check the .bin partion..?
Click to expand...
Click to collapse
Just open the .bin file in notepad++

sambastrakan said:
Just open the .bin file in notepad++
Click to expand...
Click to collapse
Ok...i'll take a look at it tomorrow morning...
Sent from my GT-I5800 using XDA App

Maybe a develloper have forgot a .png that's all !
Next mysteries !?
Okay i know where is the exit --> []
Envoyé depuis mon Samsung I5801

Darius_AWS said:
Maybe a develloper have forgot a .png that's all !
Next mysteries !?
Okay i know where is the exit --> []
Envoyé depuis mon Samsung I5801
Click to expand...
Click to collapse
this is not the main point ...
if you know why when flashing a new logo.png the old one stays please explain ...
typical french sarcasm ?

Yes more or less ;D

@Sambastrakan
The CM7 port for galaxy 5 has a modified bootlogo
It displays "android" on the screen, no samsung logo
Look into it Maybe you will know what to change..

Rapier07 said:
@Sambastrakan
The CM7 port for galaxy 5 has a modified bootlogo
It displays "android" on the screen, no samsung logo
Look into it Maybe you will know what to change..
Click to expand...
Click to collapse
I beleive the png is displayed by the s3c framebuffer driver, builtin the kernel.
The image has to be converted in a special format : look this repo to get the tool : https://github.com/morfic/Samsung-logo
G5 devs have activated the framebuffer console, I guess. That's why you can read "android" on the screen at boot up.
It's possible to activate the framebuffer console in the g3 kernel.

marcellusbe said:
I beleive the png is displayed by the s3c framebuffer driver, builtin the kernel.
The image has to be converted in a special format : look this repo to get the tool : https://github.com/morfic/Samsung-logo
G5 devs have activated the framebuffer console, I guess. That's why you can read "android" on the screen at boot up.
It's possible to activate the framebuffer console in the g3 kernel.
Click to expand...
Click to collapse
Would that possess any risk to the bootloader?

marcellusbe said:
I beleive the png is displayed by the s3c framebuffer driver, builtin the kernel.
The image has to be converted in a special format : look this repo to get the tool : https://github.com/morfic/Samsung-logo
G5 devs have activated the framebuffer console, I guess. That's why you can read "android" on the screen at boot up.
It's possible to activate the framebuffer console in the g3 kernel.
Click to expand...
Click to collapse
Thanks for that ! will have a look ...
The image is converted yes, the binary code in bml3 is totaly different from the png. Samsung makes things complicated when it could be easyer ...
It's possible to flash a modded logo on the GT-I5700, something have changed on i5800.
But this doesn't explain why a modded logo is ignored during flash !

Rapier07 said:
Would that possess any risk to the bootloader?
Click to expand...
Click to collapse
No, but you have to recompile kernel.
If you look in the kernel source, video/s3cfb.c :
Code:
#if defined(CONFIG_FB_S3C_LMS300)||defined(CONFIG_FB_S3C_S6D04D1)
#include "android_logo_rgb16.h"
#endif
The image is in the rgb16 format ... The morfic's tool should be modified to convert the image in rgb16.
It's also possible that the booloader show the samsung's logo ... Why ? I tried one time to activate framebuffer console and I could see the samsung's logo while kernel was loading.
sambastrakan said:
Thanks for that ! will have a look ...
The image is converted yes, the binary code in bml3 is totaly different from the png. Samsung makes things complicated when it could be easyer ...
It's possible to flash a modded logo on the GT-I5700, something have changed on i5800.
But this doesn't explain why a modded logo is ignored during flash !
Click to expand...
Click to collapse
I don't know if bml3 is really used ... maybe you waste your time.
It seems that the image is in the kernel itself ... so you have to compile your own kernel with the new image converted by morfic's tool.

marcellusbe said:
It's also possible that the booloader show the samsung's logo ...
Click to expand...
Click to collapse
I think it's more like that. The logo appears quickly, perhaps before the end of kernel boot.
marcellusbe said:
I don't know if bml3 is really used ... maybe you waste your time.
Click to expand...
Click to collapse
I believe you're right !!!

sambastrakan said:
I think it's more like that. The logo appears quickly, perhaps before the end of kernel boot.
Click to expand...
Click to collapse
5801 users knows that flashing bootloader changes the bootlogo..
But if the kernel is able to show a bootlogo then you could put your own bootlogo right after samsung's one.

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

Custom Boot / splash screen creator for HTC Mega

Boot / splash screen is the image that appears when you turning on your device.
1. Select 240 x 320 bmp image
2. Run nbimg.exe with parameter -F yourfile.bmp
3. The program creates new file named yourfile.nb
4. Copy yourfile.nb in NBHUtil directory
5. Run NBHUtil.exe, Select target device - Touch2, For Splash - select yourfile.nb, Build NBH!
6. Copy the created file yourfile.nbh to Radio RomUpdateUtility directory
7. Run ROMUpdateUtility.exe and flash your device
PLEASE NOTE! BACKUP YOUR DATA FIRST, BECAUSE IT IS POSSIBLE TO CAUSE HARD RESET!
Using NBHUtil.exe you can also add your custom splash screen to your fav. ROM.

Could you post pictures of your splash screen on your phone or screnshot of the software please?

psgarsenal said:
Could you post pictures of your splash screen on your phone or screnshot of the software please?
Click to expand...
Click to collapse
Here you are a screen shot, but really can´t understand why you need it. There are a lot of threads about the splash screen also i´m using well know tools.

I just wanted to saw which screen you were talking about.
Send from my Xperia play

Run nbimg.exe with parameter -F yourfile.bmp
Click to expand...
Click to collapse
How? On computer or telephone?

codesign9 said:
How? On computer or telephone?
Click to expand...
Click to collapse
you have to cook the splash .nbh on your pc

works fine
it works fine thank you

I was talking of the phone 's screen
Send from my Xperia play

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.

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

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