Hello.
I'm trying to customize the Boeffla Kernel (I9305 port) with a custom splash screen.
I've worked out that I need to use a initlogo.rle file at the root of the ramdisk, however I can't get the image to display properly.
I've atached two images, the first image is what the splash screen is supposed to look like, the second image is a photo of my phone showing how the image turns out.
Any assistance would be greatly appreciated
That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution
CNexus said:
That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution
Click to expand...
Click to collapse
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)
djb77 said:
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)
Click to expand...
Click to collapse
What are you using to convert the image to an RLE file?
I'm using the app from this thread here
The only thing I can guess is maybe this app might not be the right one
Still having trouble with it.
I don't want to give up on this, even if it takes me a while. I'm sure it can't be that complicated
BUMP
Any help at all? I'm still stuck with the same issues
Questions:
Is there a initlogo.rle there that you're trying to replace ?
If yes, can you provide both rle files?
There is no file I'm replacing just inserting it. The res is 720 x 1280
Sent from my GT-I9305 using XDA Premium HD app
Can you attach the initlogo.rle that you created?
You can use the same image in the OP
Sent from my GT-I9305 using XDA Premium HD app
That's a PNG, i need the RLE you used to create that double image error.
daedric said:
That's a PNG, i need the RLE you used to create that double image error.
Click to expand...
Click to collapse
Here you go...I had to zip it because the forums don't like RLE images
I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?
daedric said:
I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?
Click to expand...
Click to collapse
Using a PNG to RLE converter that I found on XDA. I dare say that somehting was encoded bad for this to happen.
If I knew exactly how it was to be encoded (or had the right encoder) I would be right hopefully.
It's just that I would probably want to create more splashes in the future, and even though I'd be grateful if this file was fixed, I'd also like to know how to make them properly in future
Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711
daedric said:
Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711
Click to expand...
Click to collapse
Still seem to be having the same issues.
Is it possible since there was no initlogo.rle there that it isn't properly supported by the kernel?
I know that it does show something when I put one there, but maybe there's something that needs adding to show it properly.
I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image
daedric said:
I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image
Click to expand...
Click to collapse
So it might not support that format at all by stock. It's weird how it does read that file though.
djb77 said:
So it might not support that format at all by stock. It's weird how it does read that file though.
Click to expand...
Click to collapse
You should pm DerTeufel1980. He's managed to accomplish adding a splash screen to his kernel for the Note II.
Related
I found something in the forums, but oly cabbed dialers which eat almost 5MB storage, so I simply edited the dialer pics in windows folder.
Just copy them into windows folder and accept overwriting, you will gain 1 MB of free storage, thanks to lnando84 for images compression.
I still need to edit some files , but at the moment the dialer is as in images below
If my memory is correct sir, you can find the missing images in the phcanImages.dll file.
Hope this can helps you.
I don't know how to manage .dll files.
I red some tutorials but at this moment I have no time to make practice, if someone could kindly extract the images and post them here, I could edit them and repost to rebuild the .dll
you can use a app called "Resource Hacker" to extract the bmp-file from your dll. after editing this image, just import it using Resource Hacker and save your new file. after that you'll have to singn your new dll (just search xdadev for signing dll-files).
Here in attachment you can find your needed files.
And to be useful to you I have extract all .bmb files from the specific .dll file.
Hope this helps you.
thanks, lot of things inside.. I've just made a try with the button that was missing, it's difficult to identify the gray frame..
in the rar file there are 2 pics (both in bmp and png cause I don't know which is the better format) .
Bitmap_11/png11 is from phcanImages2.dll , Bitmap_12/png12 is from phcanImages.dll.
Need to rebuild the dll files and test if I'm on the right way
thanks to kurt-willems I made a test, edited images above are ok, just have a matter of file size.
Now I need to rebuild the dll files without increase their size
here the dll files I rebuilt, I need help to check them cause I'm not able to sign them.
if I replace the stock files with those unsigned I lose storage (seems the OS have memory of the original files somewhere) and have a weird displaying of dialer bottom bar.
EDIT: if you're going to test this post dll on the phone , make first a sistem backup cause, once installed , overwriting them with the stock one will not give you back free storage .
jjollyroger said:
I found something in the forums, but oly cabbed dialers which eat almost 5MB storage, so I simply edited the dialer pics in windows folder.
Just copy them into windows folder and accept overwriting, you will lose only few KB of storage.
I still need to edit some files but I'm not able to find them (see pics with arrow- no need the green button but the gray frame) if someone knows please tell me name\location of those files
Click to expand...
Click to collapse
Hi jjolly,
do you also have a screenshot of the incoming call screen?? If that's also black, you convinced me to change to your method instead of .cab file installation.
regards, Kuzibri
kuzibri said:
do you also have a screenshot of the incoming call screen?? If that's also black, you convinced me to change to your method instead of .cab file installation.
Click to expand...
Click to collapse
unforunately no, I firstly have to learn manage dll files to complete the black buttons, and the incoming call screen is quiet complicated for me.. i made an attempt some time ago: there are 2 or 3 bmp image that are overlayed to create that background, and there is the caller name text that has to be changed from black to white and I don't have any idea where it is
at this moment you can use files in post #1 and have black keyboard+back button as in image without sacrifice free storage.
jjollyroger said:
unforunately no, I firstly have to learn manage dll files to complete the black buttons, and the incoming call screen is quiet complicated for me.. i made an attempt some time ago: there are 2 or 3 bmp image that are overlayed to create that background, and there is the caller name text that has to be changed from black to white and I don't have any idea where it is
at this moment you can use files in post #1 and have black keyboard+back button as in image without sacrifice free storage.
Click to expand...
Click to collapse
Thanks for your answer. Maybe just wait what Sir Sternas is going to send you today? Is that an option?
regards, Kuzibri
kuzibri said:
Thanks for your answer. Maybe just wait what Sir Sternas is going to send you today? Is that an option?
regards, Kuzibri
Click to expand...
Click to collapse
Will be waiting, eagerly, for Sir Sternas's answer.
Black keypad would look awesome on our HD2
As for Sir. Kuzibri, thanks a million for being around, as I mentioned the most responsive member on .... maybe the whole web ...
Thanks for always being there friend.
adazamim said:
Will be waiting, eagerly, for Sir Sternas's answer.
Black keypad would look awesome on our HD2
As for Sir. Kuzibri, thanks a million for being around, as I mentioned the most responsive member on .... maybe the whole web ...
Thanks for always being there friend.
Click to expand...
Click to collapse
Dear Adazamim,
thanks very much for your support. I will try and do my best to stick around and keep on helping members, but you give me too much honour!!
kind regards, Kuzibri
So.. no one out there can help ,please?
need to correctly rebuild and sign that dll files (possibly not cabbing them) using post's 6 edited images.
jjollyroger said:
So.. no one out there can help ,please?
need to correctly rebuild and sign that dll files (possibly not cabbing them) using post's 6 edited images.
Click to expand...
Click to collapse
+1 I really need a correct black on black dialer skin,
I, found another one though,
But never liked that only the buttons are black
The background stays as is !!!! check this thread,
a zip file is attached to the bottom of it for developers.
Would be nice if you could amend it to be a black on black
http://forum.xda-developers.com/showthread.php?t=746452
adazamim said:
check this thread,
a zip file is attached to the bottom of it for developers.
http://forum.xda-developers.com/showthread.php?t=746452
Click to expand...
Click to collapse
the attached files are part of those of my post #1 (I put 7 files in the rar file, he did 4).
It is the stock dialer ,he only inverted the names (the screenshots are "photoshopped" cause bottom bar\buttons are still gray) , I did something more cause I edited the dialer frame and the Back button
jjollyroger said:
the attached files are the same as in my post #1 stock one.
he only inverted the names (the screenshots are "photoshopped" cause bottom bar\buttons are still gray) , I did something more cause I edited the dialer frame and the Back button
Click to expand...
Click to collapse
I beg your bardon, I am no developer but a humble user.
I just wanted to help,
BTW: I have posted on Artemis thread that we had no replies in here.
this is my post.
http://forum.xda-developers.com/showthread.php?t=612580&page=3385
post no: #33849
sorry again I wasn't of much help
jjollyroger said:
So.. no one out there can help ,please?
need to correctly rebuild and sign that dll files (possibly not cabbing them) using post's 6 edited images.
Click to expand...
Click to collapse
I'll try lending a helping hand. I downloaded the zip from post #6 and noticed there are only 2 different images in there. Are these the only 2 you'd like to change within the .dll? In order for me to do that I'll need you to go into your windows folder, copy "phcanImages.dll" out of there and attach it for me.
adazamim said:
sorry again I wasn't of much help
Click to expand...
Click to collapse
no matter
lnando84 said:
I downloaded the zip from post #6 and noticed there are only 2 different images in there. Are these the only 2 you'd like to change within the .dll?
Click to expand...
Click to collapse
yes, thanks a lot.
before editing other images I need to know if its possible to rebuild them in the dll file without losing storage
with that 2 images the dialer will result as in post #7 (it has been cabbed by user kurt-willems but eats 5 MB of storage.
lnando84 said:
In order for me to do that I'll need you to go into your windows folder, copy "phcanImages.dll" out of there and attach it for me.
Click to expand...
Click to collapse
ok, here they are
jjollyroger said:
no matter
yes, thanks a lot.
before editing other images I need to know if its possible to rebuild them in the dll file without losing storage
with that 2 images the dialer will result as in post #7 (it has been cabbed by user kurt-willems but eats 5 MB of storage.
ok, here they are
Click to expand...
Click to collapse
No problem, I swapped out the 2 images you provided with the original one's from the dll's. I see what you mean about the storage because they did increase in size with just switching 1 image in each when there are about 20 bmps in each dll. Here are the one's i edited so u can see the difference.
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.
Hello guys! I have in my hand a chinese "FG8" cellphone which has an "HTC" Launcher. I dont see any posts about it, so I will share.
QsHtcLauncher.apk
https://sites.google.com/site/ernestovillarreal/home/QsHtcLauncher.apk?attredirects=0&d=1
QsWidgetHTCClock.apk
https://sites.google.com/site/ernestovillarreal/home/QsWidgetHtcClock.apk?attredirects=0&d=1
I can't install them on my Dell Streak, but, hey, you can try it.
The ODEX files are on: test.neto.mx
Don't work on my sgs2
So yeah.. it installs. but nothing more...
this want low resolution display (320x240 or 400x240 or 480x320 ) so low end / mid end devices
This is weird, I've tried in my cell phone too without success... Do you think we need any special file???
it's possible, somethings like framework.res or other device's specific files
is ther anyway to know? I can get those files
netomx said:
The ODEX files are on: test.neto.mx
Click to expand...
Click to collapse
so where is it? i mean the odex file
edited: my bad, found it. thanks
Can you upload all apks&odex and framework files?
Ill get the phone tonight and will try to make a system image.
Here is a dump of the system and data partition. Symlinks may not work ;-)
http://www.multiupload.com/SSWKLFWPEW
ThauExodus said:
Here is a dump of the system and data partition. Symlinks may not work ;-)
http://www.multiupload.com/SSWKLFWPEW
Click to expand...
Click to collapse
How did you manage that? I was looking how to dump the partitions without success!
I found an update archive and unpacked it
ThauExodus said:
I found an update archive and unpacked it
Click to expand...
Click to collapse
I have just founded them too.. but I dont seem to locate any frameworks... it is weird :S
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.
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)