This is a program that I wrote to decode and re-encode the OnePlus 5T "logo.bin" file. Please read below so you can better understand this type of encoding being used:
What Is A Raw Image?
A raw image, whether it be a file or an image in memory, is simply pixel data. There is no extra information like width, height, name, end of line... Absolutely nothing, just pixel data. If you have an image that is raw and the resolution is 1080x1920 and you are using a typical RGB24 or BGR24 (like the ones used here), then your exact filesize or size in memory will be 1080x1920x3! We use 3 here because there is one byte for the R or red component, one for the G (green), and one for the B(blue).
What Is A Run Length Encoded Image?
A run length image encoding uses a count ;usually a single byte (char), 2 bytes (short int), or 4 bytes (long int); and then the pixel components. So instead of writing out 300 bytes of '0's to make a line of 100 black pixels. Black is RGB(0,0,0). You could encode this as 100, 0, 0, 0. And only use 4 bytes of data to get the exact same image as the 300 byte raw image. All the run length encoding I've found, except the Motorola style which is a little different, use a run length encoding that is pixel-oriented like this.
Now I've found this new one and it is a byte-oriented run length encoding. This is for runs of bytes, not pixels. You may think, well whats the big deal? When you add a little area of color, you increase the run length encoded image in you logo.bin immensely! You use 6 bytes per pixel if there aren't any runs of color data. If you had an image that was a 1080x1920 black image with a 25 pixel horizontal line in the middle. The encoder would be doing runs of black data efficiently until it reached the red area.
.....0 255 0 255 0 255 0 255 0 255 0 133 /// we've reached the top left corner of the red line /// 13 1 30 1 255 1 // << that was just one red pixel!! in bgr color order (13, 30, 255) <<// And it keeps going through the rest of the red pixels on that line using 6 bytes per pixel, which is the opposite of compression. Before reaching the red line the encoding was decoding to 255 zeros over and over, until finally 133 zeros. 255 zeros is 85 black pixels stored in just 2 bytes!
This type of encoding is ONLY good for grey scale images. It is not good with color, but it still will handle color of course. In grey scale, the Red, Blue, and Green data components are always the same values. All the way from black (0,0,0) to white (255, 255, 255); including every shade of grey in between>>>(1,1,1) (2,2,2) (3,3,3)....(243, 243, 243) (254, 254, 254)<<<
One other difference in this method of run length encoding is that the color byte is before the count, which is backwards from all of the other methods.
The attachment contains the executable that was compiled using mingw32 on a 64 bit Windows 10 PC. The PNG library that I used is LodePng, the source is in the download.
Big thanks to @RajGopi for sharing his logo.bin with me and requesting this mod, and testing it as well!:good:
To use the OnePlus 5T Logo Injector:
Decode your logo.bin:
Code:
OP5tLogo -i logo.bin -d
All the PNG 's will be extracted from logo.bin. Edit the PNG(s) that you want to change...
Note:
Your original "logo.bin" file is never changed, it is just read. If the file you try to load isn't a logo.bin file, or a different style, then the program will tell you and exit.
Inject the image(s) back in to the logo.bin:
Code:
OP5tLogo -i logo.bin -j fhd_oppo fhd_at
To list whats in your logo file:
Code:
OP5tLogo -i logo.bin -l
For a more detailed list:
Code:
OP5tLogo -i logo.bin -L
If the colors are messed up use the "-s" switch while decoding.
Code:
OP5tLogo -i logo.bin -d -s
If you had to use the "-s" switch to decode properly, you'll have to use it to inject also:
Code:
OP5tLogo -i logo.bin -j image_name -s
Note:
You can put as many names after "-j" as you want, and it's not case sensitive. You also don't have to put the whole name. If you just put "-j fhd" every image in the logo.bin that starts with "fhd" will be injected. There has to be a PNG with the name in the directory though
The size of your modified.logo.bin will displayed along with the original size, if everything went good. The 'splash' partition is 16 MB on the OnePlus 5T. If you use too much color on too many of the images you will easily go over 16 MB. The program will tell you and delete the "modified.logo.bin" that was created. If for some strange reason you would like to keep it, use the "-B" flag on the command.
The last step is to flash the modified logo file via fastboot with the command
Code:
fastboot flash LOGO modified.logo.bin
Use this at your own risk.
Always make backups.
Always.
Glad to see your work here.
Been waiting for this.
Merry Christmas
RajGopi said:
Glad to see your work here.
Been waiting for this.
Merry Christmas
Click to expand...
Click to collapse
Merry Christmas to you too. Thank you for being humble, understanding, patient, polite, and more than likely an upstanding individual in your realm.
Cool, thanks for this!
thank u so much, i was trying to figure out how to do it with the OP3/T/5 and could not figure it out, it just crashed.
Bradl79 said:
thank u so much, i was trying to figure out how to do it with the OP3/T/5 and could not figure it out, it just crashed.
Click to expand...
Click to collapse
- Extract the .exe
- Right click while holding 'shift' in the same folder where the .exe is located and 'open command window' here
- Place logo.bin in the same folder
- Run the commands from OP
makers_mark said:
Flash the "modified.logo.bin" file through fastboot.
Click to expand...
Click to collapse
Please forgive my ignorance. I think I got everything done properly. I just don't know what you mean by the above statement.
Normally, if I flash a new recovery in fastboot, I use the phrase fastboot flash recovery xxxx.img
What phrase do I use to flash the new logo.bin file?
Thanks,
Peter
P.S. Where on my OP5T is the original logo.bin file located?
P.P.S. I believe I found my logo.bin file; however, it appears I made some kind of mistake and now I simply have a black splash screen, and nothing I do gets the default splash screen back, including Nandroid restore. It always remains black. Does anyone have an original OP5T logo.bin file they can give me to download? Also, the file I found is called LOGO, not logo.bin. It's in the following directory:
/dev/block/bootdevice/by-name/
P.P.S. I also believe I found the right command in fastboot. Is this the command to flash the logo.bin file:
fastboot flash LOGO logo.bin ???
PeterGuru said:
Please forgive my ignorance. I think I got everything done properly. I just don't know what you mean by the above statement.
Normally, if I flash a new recovery in fastboot, I use the phrase fastboot flash recovery xxxx.img
What phrase do I use to flash the new logo.bin file?
Thanks,
Peter
P.S. Where on my OP5T is the original logo.bin file located?
P.P.S. I believe I found my logo.bin file; however, it appears I made some kind of mistake and now I simply have a black splash screen, and nothing I do gets the default splash screen back, including Nandroid restore. It always remains black. Does anyone have an original OP5T logo.bin file they can give me to download? Also, the file I found is called LOGO, not logo.bin. It's in the following directory:
/dev/block/bootdevice/by-name/
P.P.S. I also believe I found the right command in fastboot. Is this the command to flash the logo.bin file:
fastboot flash LOGO logo.bin ???
Click to expand...
Click to collapse
Try this one, flash in recovery just like any flashable zip
Let me know if you still want stock logo
Yes, fastboot flash LOGO logo.bin
PeterGuru said:
Please forgive my ignorance. I think I got everything done properly. I just don't know what you mean by the above statement.
Normally, if I flash a new recovery in fastboot, I use the phrase fastboot flash recovery xxxx.img
What phrase do I use to flash the new logo.bin file?
Thanks,
Peter
P.S. Where on my OP5T is the original logo.bin file located?
P.P.S. I believe I found my logo.bin file; however, it appears I made some kind of mistake and now I simply have a black splash screen, and nothing I do gets the default splash screen back, including Nandroid restore. It always remains black. Does anyone have an original OP5T logo.bin file they can give me to download? Also, the file I found is called LOGO, not logo.bin. It's in the following directory:
/dev/block/bootdevice/by-name/
P.P.S. I also believe I found the right command in fastboot. Is this the command to flash the logo.bin file:
fastboot flash LOGO logo.bin ???
Click to expand...
Click to collapse
Thanks for the question, but 49 out of 50 times I do not have the device that I am working with. When you use fastboot program, you flash `x` partition with `y` file.
It doesn't matter what `y` is, but `x` is the name of the particular partition that is case sensitive. You can rename `y` whatever you want. It is hard to find partition dumps or names, so I can not worry about what the actual partition name is for a particular device. I could of asked @RajGopi when he tested, but I did not. With nearing 9 million people on XDA, I will gladly let people do their own research or what not before flashing anything for unsaid reasons which others will understand unsaid. In the past I have guided people to this thread. But thank you for wanting more clarification on the actual command with fastboot, I will include it in the post since this program is made specifically for the OP5t.
RajGopi said:
Try this one, flash in recovery just like any flashable zip
Let me know if you still want stock logo
Yes, fastboot flash LOGO logo.bin
Click to expand...
Click to collapse
Worked perfectly. Thank you.
Peter
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
makers_mark said:
Thanks for the question, but 49 out of 50 times I do not have the device that I am working with. When you use fastboot program, you flash `x` partition with `y` file.
It doesn't matter what `y` is, but `x` is the name of the particular partition that is case sensitive. You can rename `y` whatever you want. It is hard to find partition dumps or names, so I can not worry about what the actual partition name is for a particular device. I could of asked @RajGopi when he tested, but I did not. With nearing 9 million people on XDA, I will gladly let people do their own research or what not before flashing anything for unsaid reasons which others will understand unsaid. In the past I have guided people to this thread. But thank you for wanting more clarification on the actual command with fastboot, I will include it in the post since this program is made specifically for the OP5t.
Click to expand...
Click to collapse
Thank you for the detailed reply. I appreciate all your hard work. Have a great day.
Peter
RajGopi said:
Try this one, flash in recovery just like any flashable zip
Let me know if you still want stock logo
Yes, fastboot flash LOGO logo.bin
Click to expand...
Click to collapse
Argh! While your zip file worked perfectly, I'm now trying to modify the PNG file. I got everything done correctly (I think), but when I flash it, I still have your logo, not mine. Obviously there's something I'm doing wrong. Is there anything special about the PNG file? When I copy the modified logo.bin file back to the ZIP file, do I use standard compression or no compression?
Any ideas?
Peter
P.S. I'm trying to get the following PNG file as my Splash Boot image. If someone could create a flashable zip, that would be great, but I still would like to know what I did wrong. I want to learn how to do it, as I did with my OnePlus5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PeterGuru said:
Argh! While your zip file worked perfectly, I'm now trying to modify the PNG file. I got everything done correctly (I think), but when I flash it, I still have your logo, not mine. Obviously there's something I'm doing wrong. Is there anything special about the PNG file? When I copy the modified logo.bin file back to the ZIP file, do I use standard compression or no compression?
Any ideas?
Peter
P.S. I'm trying to get the following PNG file as my Splash Boot image. If someone could create a flashable zip, that would be great, but I still would like to know what I did wrong. I want to learn how to do it, as I did with my OnePlus5.
Click to expand...
Click to collapse
I hope you are renaming the output file to logo.bin and replacing it in the zip
- Check for image resolution
- Normal/standard compression will do fine
RajGopi said:
I hope you are renaming the output file to logo.bin and replacing it in the zip
- Check for image resolution
- Normal/standard compression will do fine
Click to expand...
Click to collapse
Yes, I renamed it to logo.bin, and I tried both normal/standard compression and no compression, but it's not working. Your splash continues to display.
What about the image itself? Must it be 256 colour gammut? I'm also assuming that it has to be a PNG file.
Peter
P.S. I even tried flashing the new zip AND by the fastboot method: fastboot flash LOGO logo.bin
PeterGuru said:
Yes, I renamed it to logo.bin, and I tried both normal/standard compression and no compression, but it's not working. Your splash continues to display.
What about the image itself? Must it be 256 colour gammut? I'm also assuming that it has to be a PNG file.
Peter
P.S. I even tried flashing the new zip AND by the fastboot method: fastboot flash LOGO logo.bin
Click to expand...
Click to collapse
I'll give you flashable zip tomorrow with the image you provided.
Yes, it must be a PNG
RajGopi said:
I'll give you flashable zip tomorrow with the image you provided.
Yes, it must be a PNG
Click to expand...
Click to collapse
Thank you. In the meantime, I'm going to try and figure out what's going wrong. I simply can't let this go. I have to solve the problem.
Regards,
Peter
P.S. I figured it out. I had to modify the encoding command to make it all work.
Was using: OP5tLogo -i logo.bin -j fhd_oppo fhd_at
Changed to: OP5tLogo -i logo.bin -j fhd_plus_oppo fhd_plus_at
Now everything is working perfectly. Thank you for your assistance.
Hi, I'm interested in doing this, but I never edited my bootlogo, any help on how to get the logo.bin from my phone?
Syzew said:
Hi, I'm interested in doing this, but I never edited my bootlogo, any help on how to get the logo.bin from my phone?
Click to expand...
Click to collapse
Have a look here, https://forum.xda-developers.com/oneplus-5/themes/guide-customize-oem-bootlogo-logo-img-t3704393
scoobyjenkins said:
Have a look here, https://forum.xda-developers.com/oneplus-5/themes/guide-customize-oem-bootlogo-logo-img-t3704393
Click to expand...
Click to collapse
OP3TInject crashes whenever I try to convert my logo.img, guess something's wrong with my pc.
Syzew said:
OP3TInject crashes whenever I try to convert my logo.img, guess something's wrong with my pc.
Click to expand...
Click to collapse
Sorry, I meant there's instructions there on how to extract your logo.bin, use the tool from here to extract and inject images with your dumpling logo.bin
Syzew said:
OP3TInject crashes whenever I try to convert my logo.img, guess something's wrong with my pc.
Click to expand...
Click to collapse
I'm preparing a detailed Guide on how to prepare and implement a custom boot splash. I should have it ready for download within the hour.
Peter
---------- Post added at 03:27 PM ---------- Previous post was at 02:46 PM ----------
Okay, as mentioned in my previous post, below is a detailed Guide on how to create your own custom boot splash for the OnePlus5T.
Download the PDF file here: https://www.dropbox.com/s/t45ld1abip5orhv/OnePlus5T Custom Boot Splash.pdf?dl=1
Regards,
Peter
Related
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for extra (extra thanks..)
(may U?)
does this work on hboot 1.14?
byliu88 said:
does this work on hboot 1.14?
Click to expand...
Click to collapse
double that?
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Elloco305 said:
Will this remove the HTC red warning at the very bottom??
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
invasion2 said:
Nothing removes that except SOFF.
Sent from my HTC One S running ViperOneS!
Click to expand...
Click to collapse
Don't scream at me Bro!
I figured that much though just thought I'd ask. Lol
Sent from my HTC One S using Tapatalk 2
Hmm think I might try this tomorrow to see if it works on 1.14.
---------- Post added at 03:07 AM ---------- Previous post was at 02:38 AM ----------
Changed my mind lol but unpacking the boot.img is not working.
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
byliu88 said:
Darn... no luck for hboot 1.14 I see. Updating was such a bad decision.
Click to expand...
Click to collapse
nelikp is have a go doing it because he says the image I did didn't convert right.
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
syntropic said:
I have a Nandroid of the axiom build (an awesome sense ROM popular here a few months ago before the devs fell under the SG3 spell) which I had been using on my phone until about a week ago, and for whatever reason this ROM, which has custom boot animation, has a splash screen without the red overlay text. I don't know why.. But if anyone wants to look at it, let me know. Because a pristine splash screen without S-Off is possible. I would think you could look at the partitions for the splash and maybe figure out if there is something different.
Just thought I would offer. I am trying to get up to speed on building ROMs, but am not quite there yet, otherwise I would examine it.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
v3n3 said:
As far as I know we can't flash those partitions without the need of S-OFF or using adb to push those partitions manually.
So it should be not possible flashing those from recovery, same reason we can't flash the kernel in it.
Gesendet von meinem HTC One S
Click to expand...
Click to collapse
There is another way here but need to be 1.09 lower Hboot for it to work. I think this boot.img mod just dont work for us and nelikp never got back to me.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
How did you fixed that error?
alexeius said:
How did you fixed that error?
Click to expand...
Click to collapse
When you install Cygwin you be asked if you like to install plug-ins or something like that, when it does that search for cpio and select to install all and do the same for perl.
Darknites said:
I fixed that but all I get is a bootloop and nothing has changed. Here the boot.img I did, don't if anybody wants to try it on a lower Hboot or can see if I did it wrong. Boot.img is from aokp_ville_experimental_Nov-01-12.
Click to expand...
Click to collapse
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
essentialmindz said:
I had the same problems. I followed your guide step by step and encountered boot loop without the change. Im on Hboot 1.09.0000. I realy wanted to get this image as my kernel logo -=*( woah is me...
Click to expand...
Click to collapse
I got same thing so give up. Boot you in luck with that Hboot you can use this thread here to do what you want to.
Hi there XDA! I have a really big question/problem. I want to theme Clockworkmod Recovery with custom pictures/icons/themes and such. So far I installed Ubuntu VM, decompiled the Recovery Image into Kernel and Ramdisk, replaced the pre-loaded icons with my custom icons to the ramdisk. Finally, I recompiled it into a new recovery image!
However, since this program is designed for device boot images, Im still curious, can this be used for recovery images? I haven't editing anything within the kernel, just opened the ramdisk, replaced the /res/images with my own and did abootimg --create newcwm.img.
EDIT : All I know is that in the boot.cfg the boot parameter size has to be exact fit or hardbrick.
so I have attached the 2 files that shows the recovery image data/config of both of them.
Don't worry its just 2 txt files. Inside the other archive has the flash ready images. BOTH OF THEM. Also includes the already decompiled ramdisk and kernel to take a look at. In addition the bootimg.cfg is also in. It has everything you need to know
So, heres the question. If I decide to flash it to mmcblk0p21 which is the verified recovery partition for the GT-i9505, (Info on the partition informations/mount points below
http://forum.xda-developers.com/showthread.php?t=2342841
Then, hopefuly the flash to the recovery partition shouldn't hardbrick my device. Am I right? Or missing something.
I will attach both my image and the cwm recovery Image I decompiled. Please if you can tell me if theres something that has to be fixed to prevent me getting a $700 paperweight.
Note: The layout might be confusing inside the Archive, just please bear with me and just take your time. I can wait
PRESS ME TO DOWNLOAD
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Mi A1 Only (Snapdragon Variants)..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Mi A1 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
FOR NEW FIRMWARES FOR WHICH THIS TOOL DOESN'T WORK, TRY THIS NEW TOOL here:
https://forum.xda-developers.com/mi-a1/themes/tool-tissot-splash-maker-mod-5-pngs-t3799701/
Also, try these if that didn't work:
https://forum.xda-developers.com/showpost.php?p=76713069&postcount=42
https://forum.xda-developers.com/mi...change-boot-logo-splash-t3681033/post75978168
(I don't know if it works; an user seems to have successfully used it to create splash.img for new bootloader)
I never had the latest splash.img from the latest firmware, so I can't create a proper unless someone sends me
For older firmwares, proceed below:
STEPS to create splash.img:
1. Download & Extract this: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Was searching for this thanks.
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
ravinder0003 said:
@GokulNC
I created splash with your demo logo image... Result: Same boot logo showing when booting
I created splash with Google and iphone pngs taken from rn4 thread... Result: Same boot logo showing when booting
So not working for me
Click to expand...
Click to collapse
rameshurfrnd1 said:
@GokulNC
Splash not working bro in ma1
it create splash image and i flash via fastboot but not working
Kindly look into it asap
Click to expand...
Click to collapse
Please send your stock splash.img and logo.img
I'll check what the problem is..
GokulNC said:
Please send your stock splash.img and logo.img
I'll check what the problem is..
Click to expand...
Click to collapse
Attached splash.img of stock and logo.img not available check enclosed screenshot
Hey, @GokulNC please add options like change bootloader image, charging animations etc, and give a proper way to unpack or extract decompile splash.img file.
Will this also change the 'your device bootloader has been unlocked' thingy?
Say goodbye to white
If there's enough interest I'll make a matching boot animation (Oreo flavor)
Tested and working through flashing via twrp on latest Oreo OTA
Tested and working through flashing via twrp on latest Nougat OTA
If you find yourself stuck in a twrp bootloop - look at the slot you are in
If in A choose reboot - than select slot B - then boot to system to get out of it
any way to remove bootloader unlock warning in mi a1?
need to find out how to remove or change to black
pedrazadixon said:
any way to remove bootloader unlock warning in mi a1?
Click to expand...
Click to collapse
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Stoutpuppy GFX said:
There's already a couple of us looking into to this but so far no luck
I've combed through system dumps even and nothing to be found
If anyone knows where this screen is located please let us know
Click to expand...
Click to collapse
@Stoutpuppy GFX, I was reading an earlier reply of yours on this thread, did you flash the splash.img in TWRP instead of fastboot flashing it?
Any luck on anyone getting this message removed?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text. Has anyone unlocked their bootloader and used this Splash Maker and had it work?
fastboot erase splash works, then we get a black screen and Tux... LOL
I've always considered a Splash image what you see on a bootup, running this command removes this message, but the Fastboot image is also removed in the Mi A1.
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
DoR3M3 said:
Any luck on this?
I tried the splash maker, didn't do anything, instead of a white background screen with the text, anytime I made a splash image and installed it, the screen was then black with the bootloader unlocked text.
Removing the splash image does work, then we get a black screen and Tux... LOL
It would be nice to not erase the splash and someone comes up with a fix for this?
Please let us know...
Thanks
Click to expand...
Click to collapse
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
And I just flashed the splash screen through adb commands (fastboot splash splash.img) don't use brackets
but unfortunately if you have to leave your device in an unlocked state - all it will do is change the splash screen
to black with message saying your phone can't be checked bla bla - followed by that white unlocked screen shown in previous post
Stoutpuppy GFX said:
No luck so far - but I read somewhere the some pixel & nexus devices have the same problem with no solution either
I'm hoping these screens will disappear once we get an official ROM for our device - fingers crossed I hate white screens
Click to expand...
Click to collapse
@Stoutpuppy GFX
WOW fast reply, LOL...
Please look back and read over, I edited my previous reply...
Thanks
Any news about the splash solution for the tissot? Thanks.
PS: the problem seems to be the new splash format comes with the new bootloader.. Does anybody got luck to guess the format?
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
robby_tan said:
Since this tool is based on redmi note 4's tool and the redmi note 4 ones already have splash maker for newer firmware in that thread, can I use that for Mi A1 too?
Click to expand...
Click to collapse
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Xiaomi Mi A1 Only (Snapdragon Variants)..
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Mi A1 (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Mi_A1_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x1920 or lower.
Note:
Mi A1 logo has a fixed size of 100kB allocated for splash image frame buffer, so only very light-weight pictures can be used.
It's recommended to use picture with 3 or 2 colors only, like Black & White pictures.
So you'll have to try many pictures till you get a successful one.
3. Now rename your picture as logo.png or logo.jpg according to its format & replace it inside "pics" folder of the extracted folder.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
Note:
You'll get an error like "PICTURE IS LARGE IN SIZE" if it's not possible to create a logo with that picture.
In that case, try any one of these below:
a. Try compressPNG.com to reduce no. of colors in PNG picture.
Upload your picture, click Settings, reduce number of colors to 2, Apply & download it & try again.
b. Reduce the picture resolution.
For example, this picture:View attachment 4073256 can be edited to something like this: View attachment 4073257
(Hope you understand what I say)
c. Try some other picture.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
1. Based on my original tool for Redmi Note 4
2. @OtrovX who provided the stock splash.img of Mi A1.
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
Click to expand...
Click to collapse
thanks
novic_dev said:
The new format for RN4 is:
python bin/logo_gen.py pics/logo.png 100864
mv output.img temp/logo.img
python bin/logo_gen.py pics/fastboot.png 613888
mv output.img temp/fastboot.img
python bin/logo_gen.py pics/logo.png 101888
mv output.img temp/logo2.img
cat bin/header.img temp/logo.img temp/fastboot.img temp/logo2.img bin/destroy.img > output/splash.img
rm output\*.raw
So, I'll test it today for Tissot
Click to expand...
Click to collapse
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
Click to expand...
Click to collapse
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
novic_dev said:
Guys!!!! This format is correct!!! Have just successfully tested! :victory::victory::victory:
---------- Post added at 01:26 PM ---------- Previous post was at 01:11 PM ----------
Just use the correct scripts I've prepared: http://anikos.su/tissot_splash_scripts_new_novicdev.zip
PS:
SPLASH - is a so-called "structured" raw image of the splash device partition.
Each bootloader parses the splash partition as a set of images created in some different media formats and sizes.
So, the new updated bootloader of Tissot is now parses the splash as a set of 4 (four) parts: "header - image - fastboot image - image 2".
Click to expand...
Click to collapse
what's header image? The 5 second "device can'tbe checked" warning?
Note:
This is not bootanimation, this is the splash screen (the boot logo which is displayed when device is switched ON)
This is for Razer Phone Only.. (codename: cheryl)
(For other devices, please send me your splash.img so that I can create a tool for you too..)
Requirements:
1. Rooted Razer Phone (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this in computer: Razer_Phone_Cheryl_Splash_Maker.zip
2. Make sure you have a picture with resolution 1440x2560px.
Now rename your picture as logo.png or logo.jpg (according to its format) & replace it inside "pics" folder of the extracted folder.
3. Finally, run the 'CREATE_LOGO.bat' to create splash.img and flashable zip file, which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
Now, Choose any one easy method:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@game_guy who provided the stock splash.img of Razer Phone (cheryl)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Splash screen is different from boot animation. The one which appears before boot animation
Oops sorry, brain fart.
I guess I wasn't paying attention all that well.
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
eoghan2t7 said:
I would guess the splash screen is reading the bootloader state from somewhere so if that's the case disabling it or at least hiding the message might be possible since the image can be changed
Click to expand...
Click to collapse
Nope, the splash screen is just a BMP picture (in RGB24 format) with an empty 16kB header before the picture.
You could see that in the batch file's code.
linuxct said:
@GokulNC, does this also disable the Qualcomm verified boot/5 seconds to boot message? And if not, is there any possibility to do so?
Click to expand...
Click to collapse
The warning message actually is from the bootloader itself.
Most probably, it will be present in the 'aboot' partition, but it's not as easy as changing splash screen.
The same issue was also present in Nextbit Robin. (a company acquired by Razer)
Because, the bootloader is just a raw file when dumped, which needs to be checked using hex editor or whatever tool to see if it has an image and find its offset and patch the image accordingly, or even, it might be possible to find the location of where the amount of warning time is present and make it 0.
But the problem is, since it's a raw dump and the bootloader is the code that brings up the kernel, it's highly possible that if we do something wrong, the device might be hard-bricked (even fastboot mode is from bootloader). Also, today's bootloaders might even be signed, so patching the bootloader for warning picture might not necessarily work since the device won't be able to verify the integrity of bootloader partition after its contents change.
So, if there's a tool with which you can flash and recover a hard-bricked phone, and if you're willing to test the modified bootloaders that I create, send me the bootloader partition dump. I'll take a look at it
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
linuxct said:
@GokulNC, thanks for your highly detailed explanation, but I'm not taking the risk of having an 800 USD brick :)
Click to expand...
Click to collapse
Lol I remember doing stuff with my Droid RAZR and Bionic for dhacker back in the day. It was worth it in the end, but took time for the recover from hard brick processes to come about.
RUNNERX said:
You can just change the boot animation.zip located in system /media and set permissions to rw-r-r.
Here I renamed the original to stk-bootanimation.zip then added what I wanted.
Click to expand...
Click to collapse
Hi, can you please upload and share the default bootanimation here? I have deleted mine and would like to get it back.
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
GokulNC said:
Note:
This is not bootanimation, this is the splash screen (the 'Mi' boot logo which is displayed when device is switched ON)
This is for Redmi Note 5 Pro (whyred) Only.
For Redmi Note 5 (vince), click here.
For other devices, please send me your splash.img so that I can create a tool for you too.
Requirements:
1. Rooted Xiaomi Redmi Note 5 Pro (whyred) (any ROM)
2. Optional: Terminal Emulator app or Custom Recovery or atleast working fastboot in computer
3. You're proceeding at your own risk.
STEPS to create splash.img:
1. Download & Extract this: Redmi_Note_5_Pro_Splash_Maker.zip
2. Make sure you have a picture with resolution 1080x2160 or 1080x1920.
3. Now replace your pictures on logo.png inside "pics" folder of the extracted folder.
(Similarly you can change other pictures too)
Note: You can put any picture format, but the names have to be 'logo', 'fastboot', etc.
4. Finally, run the 'CREATE_LOGO.bat' to create splash.img , which you can find inside the "output" folder after completion.
STEPS to flash splash.img:
Optional: To backup your original splash.img:
Code:
dd if=/dev/block/bootdevice/by-name/splash of=/sdcard/splash.img
(Not necessary though.. You may get it from the stock firmware itself.)
First of all, make sure fastboot is setup in your computer & working just in-case something gets ducked up
Now, Choose any one easy method to install:
a. To flash from recovery:
Transfer the flashable_splash.zip to your device and flash from TWRP or CWM or Philz or any other custom recovery.
b. To flash from Terminal Emulator:
Transfer the splash.img to your device's Internal Storage, Open Terminal Emulator & enter the following to flash it:
Code:
su
dd if=/sdcard/splash.img of=/dev/block/bootdevice/by-name/splash
c. To flash from Fastboot mode:
Code:
fastboot flash splash splash.img
Note:
Incase something goes wrong or device doesn't bootup, flash the stock splash.img from custom recovery or fastboot.
Credits:
@[email protected] who provided the stock splash.img of Redmi Note 5 Pro (whynce)
Hit the Thanks :good: button if it worked for you
You're welcome to post the splash images that you created..
FOR MEDIATEK VARIANTS:
For MTK devices, you might have a different partition for that called 'logo'.
Browse in /dev directory to find out where that is present.
After you have found out, dump the logo.bin file by:
Code:
dd if=/<the_directory_where_logo_is_present>/logo of=/sdcard/logo.bin
Now you can edit the logo.bin using this tool:
Changing Boot Logo (logo.bin) - LOGO BUILDER Program
After editing, you can reflash it by:
Code:
dd if=/sdcard/logo.bin of=/<the_directory_where_logo_is_present>/logo
If you did this successfully, please share the details of how you did it so that it will be helpful for others..
Or if that tool doesn't work, send me your logo.bin or splash.img, I'll check it..
Click to expand...
Click to collapse
You are awesome , genius , superb , intelligent , brilliant , excellent , superb:good::good::good::good:
thank You Sooooooo MUCH
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
kqixs said:
How to solve black bars on head and foot side...if background is white....intried picture of res 1080×2160 and the get compressed vertically and on trying with res 1080×1920 it seems fine but just those black bars on both side look weird...
Click to expand...
Click to collapse
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
GokulNC said:
Eventhough your device resolution is 1080x2160, the developers of this device have used 1080x1920 splash screens.
So I just extracted it and created the tool. That's the reason why if you use an image with non-black background, you see the remaining pixels black.
If I modify the tool to work for 1080x2160, I'm afraid it will affect the fastboot picture (since the bootloader would have hardcoded the locations for each image and changing resolution will change splash size and location of other files).
You may try it yourself by editing the batch file and set 'resolution=1080x2160' in the script.
Also, I may work around this problem if you can test the following:
Replace all the word containing 'rgb24' with 'rgb565' in the script and tell me if the splash.img still works.
Click to expand...
Click to collapse
The reason wasbunderstood, but i couldn't find the solution...i didn't know much about programming (to edit .bat file) i tried to search it a bit but couldn't succeed so i just used another image for boot logo....
Thnx for you help though....?
Please make a flashable Google pixel logo and boot animation for Redmi note 5 pro
Google G icon splash screen for whyred.
splash.img
raw files
Wow. Thanks its so easy.
This is the flashable zip of my splash screen.
If anyone find it useful.
Thanks for making this guide and sharing this tool, I love it!
I have an issue though, I tried making some 1080x2160/18:9 splash screens but they got vertically squished down into 1080x1920/16:9 , is this meant to happen?
As a workaround I changed my images to 1080x1920/16:9 and made the background pitch black so there wouldn't be black bars at top and bottom.
I'm a loser who loves watching Twitch livestreams, so in lack of creativity I just made these my Splash screens
KuldeepShivankar said:
This is the flashable zip of my splash screen.
If anyone find it useful.
Click to expand...
Click to collapse
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
sharmasrb said:
Could you please edit and correct the spelling to Wonder Woman. It says Women currently.. Image looks amazing
Click to expand...
Click to collapse
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Can I request this picture for splash image, as my computer is broken..
Thank you
This is a test splash screen...
KuldeepShivankar said:
Haha.. I realised that mistake so i deleted that splash image and now using it without "powered by wonder woman" written on it. And i don't have my laptop near me so can't edit it.So I can only give you my current splash image file. Do you want it? Let me know.
Click to expand...
Click to collapse
Okay, i want it
@GokulNC I tried to edit the script and make the resolution 1080*2160 because I wanted a white splash without the black bars, and then resized all 3 images to the same resolution, and then made a splash and flashed it. Worked but instead of these images it shows a complete black screen.
You know why?
Rishi2906 said:
@GokulNC I tried to edit the script and make the resolution 1080*2160 [...] Instead of these images it shows a complete black screen.
Click to expand...
Click to collapse
The routine that displays the images is very simple, and just looks for them at certain offsets within the splash partition. When you change the dimensions, file sizes change as well, and the following images are no longer at the offsets they're expected to be, so they can't be found, and nothing is displayed.
If the BMP images are exactly 6,220,854 bytes each, they can just be concatenated together; smaller ones could possibly work with some padding in between them but if you want a larger resolution, the resulting bitmaps would be too large in size.
One way to make the files small enough to fit within their spaces so that the following ones could still start at the right offsets would be to reduce color depth. (Another way would be to find the code that displays the images and edit the offsets it looks for but this isn't trivial). But in the end, the routine might still not be designed to display anything else than 24-bit, 1080x1920 px anyway.
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Jerry981028 said:
Google G icon splash screen for whyred.
splash.img
raw files
Click to expand...
Click to collapse
Is it flash able zip via twrp
irfan.shikarpuri said:
Is it flash able zip cis twrp
---------- Post added at 05:32 PM ---------- Previous post was at 05:21 PM ----------
Is it flash able zip via twrp
Click to expand...
Click to collapse
No.
What is the maximum logo size that I have to make? thanks before
What is the maximum logo size that I have to make? thanks before