Database Info

[How To] Flash Splash1 on EVO on Windows 7

[HOW TO] Changing the starting Splash Image EVO
Tools Used:
GIMP http://www.gimp.org/downloads/
fastboot http://okean.ath.cx/splash_editing/fastboot.exe
rgb2565.exe http://okean.ath.cx/splash_editing/rgb2565.exe
cygwin1.dll http://okean.ath.cx/splash_editing/cygwin1.dll
ImageMagic http://okean.ath.cx/splash_editing/ImageMagic.exe
Note: Mirrors to most of those can be found in the threads bellow section.
Help With Tutorial:
Thread I Started http://forum.xda-developers.com/showthread.php?p=6820690#post6820690
G1 Thread That I got most of this from. http://forum.xda-developers.com/showthread.php?t=456071
Thanks a lot to everyone.
----------------------------------------------------------------
Disclaimer.
My first tutorial, I am not responsible for any damages. I did this
by trial and error on my Evo Running Damage Control 3.0 by damageless with Radio Evo-1.39.00.05.31 (06/06/2010) by toastcfh. Fully rooted with engineering SPL via toastcfh method for fast boot access.
--------------------------------------------------------------------------
Step 1:
NAND Backup, Just in case always do this. YOu never know when this will save your phone.
Step 2:
Put the phone aside, and find a picture with a aspect ratio close to 800 height by 480 width, will work best. Open up GIMP with your image. Modify the photo to be 800 height by 480 height or scale it via Image Scale Image, You may hit the chain link on the right if the aspect ratio is not equal. Once the image is scaled, Go to Image -> Mode -> Indexed. Leave it at Generate optimum palette Maximun number of colors 256. Then in the layers, merge all all the layers if required and remove all alpha channels, if there are any. Save as a png, prefferable as splash.png as I will refer to it from this point.
Step 3:
Let us check to make sure we are on the right track, in Windows right click and go to properties than details and make sure width is 480 amd height is 800 and that Bit depth is 8.
Step 4:
Next we will use the ImageMagick software, if installed on windows correctly when you type in convert into cmd (Command Prompt) it will display tons of options. Well will go into the
directory where we saved splash.png and run this command in that folder
Code:
convert -depth [COLOR="SeaGreen"]8[/COLOR] [COLOR="Magenta"]splash.png[/COLOR] rgb:[COLOR="Orange"]splash.raw[/COLOR]
It should make a file called splash.raw right next to it.
Step 5:
Make sure that in the same area as splash.raw is, that you have cygwin1.dll and rgb2565 also and we will execute the following command
Code:
rgb2565.exe < [COLOR="Orange"]splash.raw[/COLOR] > [COLOR="Teal"]splash.raw565[/COLOR]
It should make a file called splash.raw565
WARNING: I know these files are size sensitive and I have had it come out to
exactly 750 KB (768,000 bytes) for size and 752 KB (770,048 bytes) size on disk each time. If someone who knows more about this can explain a significanse or what the size should be exactly i and everyone will appreceate it but for me it works with that size.
Step 6:
Get into fast-boot on your phone via turning it off, than turning on while holding power button, untill you get into the white screen with androids. Select fastboot, it should show fastboot usb. If you type the command
Code:
fastboot devices
it should show you your phone. Next type the following command
Code:
fastboot flash splash1 [COLOR="Teal"]splash.raw565[/COLOR]
It should print out some stuff about sending it and the speed it sent it at. Then finish up with fastboot reboot And you should see your new splash image. YAAAY.
I will include an attachment of a file from Digital Blasphemy that i used and all the files it made in the process.
Questions, Comments, Need Help Post Below.

Xyber3364 said:
Code:
fastboot flash splash1 [COLOR="Teal"]splash.raw565[/COLOR]
Click to expand...
Click to collapse
nice! thanks for putting this together! this should be the beginning of plenty sweet boot images!
new to the HTC fastboot methods ... any idea if there are any other methods of flashing splash1 from inside recovery or normal android? can the flash_image binary flash to splash1?

Ahh ive been looking for something like this for awhile now. Any chance you saved the original splash image? I was hoping to use it in the second bootanimation to make it a smooth switch.
Thanks!

Original
Mast3rpyr0 said:
Ahh ive been looking for something like this for awhile now. Any chance you saved the original splash image? I was hoping to use it in the second bootanimation to make it a smooth switch.
Thanks!
Click to expand...
Click to collapse
Forgot to include this, it is important
Original Hosted here http://okean.ath.cx/splash_editing/splash.nb0
right click and save as if it opens the file in your browser.
Code:
fastboot flash splash1 splash.nb0

Xyber3364 said:
Forgot to include this, it is important
Original Hosted here http://okean.ath.cx/splash_editing/splash.nb0
right click and save as if it opens the file in your browser.
Code:
fastboot flash splash1 splash.nb0
Click to expand...
Click to collapse
Aww its not an image? Is there any way to change it back into an image?

Best I know
joeykrim said:
nice! thanks for putting this together! this should be the beginning of plenty sweet boot images!
new to the HTC fastboot methods ... any idea if there are any other methods of flashing splash1 from inside recovery or normal android? can the flash_image binary flash to splash1?
Click to expand...
Click to collapse
Not sure is my answer.
If you are handy with linux and android,
http://elinux.org/Android_Fastboot
From the recovery you can find these partitions, what to do with them, at the moment I have no clue

Not Perfect BUT
Mast3rpyr0 said:
Aww its not an image? Is there any way to change it back into an image?
Click to expand...
Click to collapse
This is from the HTC BootAnimation, since i have no clue how to convert .n0 back to png, but this is close.
{
"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"
}

Not close enough for what I was hoping to do :/ Oh well, ill keep looking.

Mast3rpyr0 said:
Not close enough for what I was hoping to do :/ Oh well, ill keep looking.
Click to expand...
Click to collapse
Here you go, in BMP format.

ortizdupri said:
Here you go, in BMP format.
Click to expand...
Click to collapse
Ahh yess i love you! haha. Il have a bootanimation out later utilizing it
Might I ask how you were able to acquire it?

Xyber3364 said:
Not sure is my answer.
If you are handy with linux and android,
http://elinux.org/Android_Fastboot
From the recovery you can find these partitions, what to do with them, at the moment I have no clue
Click to expand...
Click to collapse
this is perfect! the information is not for our phone specifically but it helps to understand the fastboot and phone interaction plus basic partition structure! of course, it raises more questions for me, but they're at least advanced a step which is definitely progress! thanks!!

Mast3rpyr0 said:
Ahh yess i love you! haha. Il have a bootanimation out later utilizing it
Might I ask how you were able to acquire it?
Click to expand...
Click to collapse
Through a pain in the ass. And lots of Google. And what not.
Basically grabbed the splash1.nb0 file from toast's RUU file, renamed it to splash1.nb, and used this tool: http://forum.xda-developers.com/showthread.php?t=405118 to convert the splash1.nb to splash1.bmp. My goal is the same as yours - utilize a bootanimation with that as the starting image to jump off from. Luckily, I hope I have helped people out.
(Interesting note from the splash screen, the background isn't pure white, but is a shade of gray, one that continues on to the Sprint bootanimation background.)

ortizdupri said:
Through a pain in the ass. And lots of Google. And what not.
Basically grabbed the splash1.nb0 file from toast's RUU file, renamed it to splash1.nb, and used this tool: http://forum.xda-developers.com/showthread.php?t=405118 to convert the splash1.nb to splash1.bmp. My goal is the same as yours - utilize a bootanimation with that as the starting image to jump off from. Luckily, I hope I have helped people out.
(Interesting note from the splash screen, the background isn't pure white, but is a shade of gray, one that continues on to the Sprint bootanimation background.)
Click to expand...
Click to collapse
So you are telling me, that that program easily turns and bmp to a nb also.... that one can than flash? that makes life easier

Xyber3364 said:
So you are telling me, that that program easily turns and bmp to a nb also.... that one can than flash? that makes life easier
Click to expand...
Click to collapse
Yeah, not sure how well it works on the conversion back to NB, but it might be easier than some of the other methods I've read.

I will let someone else test that out .

Here's a clean and simple one I threw together today for those of us who are rooted.

I like it. What I would like to see is some combo's splash1 -> bootanimation -> background to make it look as smooth as possible.

here is a quick visual program i made.
I used the code for the G1 splash made by Koush.
open up image
preview how it will look
convert to raw file with correct filesize.
it auto resizes to dimension on the longest side.
then just fastboot flash to phone.
I might add a nb0 to bmp/jpg/png
--Included
Executable
Orginal Splash Screen
fastboot

Xyber3364 said:
I like it. What I would like to see is some combo's splash1 -> bootanimation -> background to make it look as smooth as possible.
Click to expand...
Click to collapse
I tried doing that on a bootanimation (as far as splash1 connecting in terms of design), unfortunately, splash1 cuts to a black screen before booting into the animation. I believe it's something like a quarter or half a second of black screen before the animation starts, nothing dramatic, but enough to be noticeable so it is not a smooth transition.

Little something I threw together.
And a link to the file if you want to use it. Feel free to ask questions and use freely.
http://www.wikiupload.com/c8Kn5mTz

[WINDOWS] {05/22} WET_ANDY * a UNIVERSAL splash screen converter and flashing tool

Meet Wet Andy, a UNIVERSAL splash screen tool.
{
"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"
}
Yes, you heard right, this is a tool that can take any standard image (jpg, png, bmp), convert it to the exact screen size of your device, and flash it to your device.
Custom splash screens have never been easier! It will work with API7 through API15 without issue (on the 8 different devices I tested). This is a self-contained package, no installers, and can be used from a flash drive with no additional downloads required. All the tools are right there!
STEPS:
1. Connect your Device and enable USB Debugging. Start the "Wet Andy" program by clicking it.
2. Hit the "TEST ADB" button, it will tell you if your device is connected. (output can be seen as ADBTEST.txt in the folder)
3. Hit "PICK" and you must pick an image file that is JPG, BMP, or PNG using the file chooser.
4. Hit "CONVERT", you will not see the progress on screen, but when you see your image, display.txt, and splash.img in the program folder it has worked!
* This program auto converts the image to the size of your screen, so you can use any image. If your phone does not display its screen size in the props, the default is 480x800
5. Close the program. (ffmpeg has something weord where it keeps going, but don't worry as it WORKED.
6. Restart the program and "TEST ADB"
7. Once you see it is connected, hit "Install"
* The phone will freeze, then reboot into the bootloader. From there, it will do the install.
* Once you see the screen go blank and the program show "Installing", it has installed and is rebooting
* You will see the new image as it boots!
TO REUSE AND FLASH ANOTHER IMAGE TO THE SPLASH, DELETE THE SPLASH.IMG !!!!
DOWNLOAD: http://dl.dropbox.com/u/58849669/WetAndy.windows.zip
Say THANKS and/or DONATE if you like the program!!!
NOTICE: BY USING THIS PROGRAM, YOU AGREE TO THE RIGHTS AND PRIVILAGES OF GOOGLE AND THEIR SDK TOOLS

Good
Sent from my GT-I9100 using xda premium

Very cool. Thanks
**EDIT** Works fantastic on my evo 3D. thanks again.

^^OP
This works for all phones?
My boot.img contains logo in form of rle
That is initlogo.rle
Then?
What if I want splash screen in form of initlogo.rle?

This is not your boot.img, this is the system splash which is before your kernel and such. Messing with your Boot.img is a different matter.
Works on all devices that use the splash standard set forth by Android.
This is not a boot animation. This is just an image at startup.
Requires Root, shell, and fastboot access. SGS2 users need to be running AOSP packages that use the base system standards.

What?
I have Micromax A70 and we have first boot logo inside the kernel i.e zimage and second bootlogo is from boot.img which is initlogo.rel
We dont have any splash partition to flash splash.img via fastboot
So this is not for our device?

This is unfortunately, not going to rip your boot image, replace the image and zip it all up again. Kernel code requires that you compile your own after doing the conversion.
I can make a converter and compiler for kernel code that puts your image in there with links to the source code.
They basically made those areas blank and put no beginning splash. What you are seeing with the kernel start and boot start is not a splash image. Your images are built into your running code, so not your boot splash.
Running as the zImage and uImage pieces is not true native Android code and does not really adhere to the base code standard. They basically put a micro layer between the OS and the hardcoded chip firmware. They run it as a standard OS.

Great tool, do you know if this works on the Toro Galaxy Nexus?

Just try it. There is literally no harm that can come from this program. If you have no splash ability on your devices, well can't help you there just yet.
Its just using fastboot to flash the splash image. The fancier bits are in the device recognition with display specs and file conversion.
For the SGS2 users and those whose boot images are in the kernel, I can make a image converter that automatically compiles the kernel, then pushes it and flashes the new kernel. I can also add some fuctionality for rle image conversion for some of the more odd implementations.
Tell me if you want it. I can do it. Not that hard.

How long does it take for a file to be converted? It has said file loaded for a while and seems to stay there?
Ok never mind I restarted it duh LOL and it seemed to install but the splash screen is the same, will try again

Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...

You got it Bill!
Hopefully this takes the guess work out.
Its really a GREAT way to insure your device has another layer of safety because you can make an image that has your name and personal contact information that the person who finds it can you to get a hold of you. Also, regardless of if someone manages to boot into recovery mode and completely wipe your data or flash a new image, they CAN'T wipe this. That is unless they are a very diligent thief and find this tool!

Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
billbowers said:
Open the folder that contains the program. When it is finished, you will see a new file called splash.img. Then, close wet Andy, and restart it. And select install. Bada bing Bada boom...
Click to expand...
Click to collapse

Strange.. Mine took about 10 seconds...max

You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
camblue said:
Thats just the thing how long do you have to wait for the file to convert? I left my device connected for roughly 30 mins and all I saw was a text file created, no splash.img??
Click to expand...
Click to collapse

Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Childofthehorn said:
You have to PICK a file for it to convert. You must pick, then convert. It only works on PNG, JPG, and BMP file formats for the pictures. PICK loads the file into the program and then hit CONVERT. I would double check that your device is connected. If you are also only seeing display.txt and NOT the splash.img or a copy of the picture you are converting and flashing, you did not hit the PICK option first. That or your internal windows tools are super-broke.
Also check that ffmpeg isnt running rampant on your processes.
There just isn't a good reason why its worked for everyone else and your computer is having issues, unless something is wrong.
Please outline exactly what you are doing and seeing.
Click to expand...
Click to collapse

camblue said:
Ok I connect my device to my computer and just to be sure I check my ADB connection by running a command prompt and typing adb devices and my devices shows up. Then I back out of that and go into the wet andy program and test the ADB connection and it says device connected! Then I pick a picture of my car (dont judge me its a corvette LOL) it is a jpg file and it says file loaded! Then I hit convert and it just sits there and does nothing? I have tried several other pics and nothing happens after I hit convert?
Click to expand...
Click to collapse
After that, you should see your img file in the folder for the program.
Close Wet Andy, restart it, check your adb connection, and Then run INSTALL.
It will install and reboot your device!

[APP][LOGO] Moto X/G/E boot logo command line tool

Here is a small command line tool to manage boot logo on motorola phones with unlocked bootloader on Jelly Bean, Kitkat and Lollipop.
With this tool you can mainly create your own custom boot logo and/or remove warning message.
You can also list, extract, replace, remove image from a boot logo file or create a new one from scratch.
The tool can accept a large variety of image format, but prefer using a non-destructive format like BMP or PNG.
Images are exported as PNG.
Code:
[B]Usage:[/B]
mlogo <logo_filename> command [arguments]
[B]Commands:[/B]
mlogo <logo_filename> list
list logo contents
mlogo <logo_filename> extractall
extract logo contents
mlogo <logo_filename> create
create a new empty logo
mlogo <logo_filename> append <name> <image_filename>
append image to an existing logo
mlogo <logo_filename> replace <name> <image_filename>
replace image in an existing logo
mlogo <logo_filename> remove <name>
remove image in an existing logo
mlogo <logo_filename> extract <name>
extract image from an existing logo
Create a custom logo on Kitkat/Lollipop (android 4.4.x/android 5.x):
Your image can have any size less or equal to your phone's native which is:
Moto X 2014: 1080x1920
Moto X 2013: 720x1280
Moto G (2013/2014): 720x1280
Moto E: 540x960
If your image resolution is less than phone's native:
Changes are done by the phone not by this tool
- it will be centered vertically and horizontally
- the background color not covered by your image will be the same as the top-left pixel of your image.
List the content of your current logo:
mlogo logo.bin list
Replace the image you want to change with yours:
Start logo on unlocked bootloader:
mlogo logo.bin replace logo_unlocked mylogo.png
Empty battery logo:
mlogo logo.bin replace logo_battery mylogo.png
Low power logo (moto E):
mlogo logo.bin replace logo_lowpower mylogo.png
Unplug logo (moto E):
mlogo logo.bin replace logo_unplug mylogo.png
Create a custom logo on Jelly Bean (android less than 4.4):
Same as above but your image must have a size of 540x540
Use 'mlogo (old format)'
Thanks to:
Carock, for explanations on boot logo RLE image encoding.
Changes:
- v1.01 change errorlevels behavior,
return errorlevel 0 on succes and errorlevel 1 on error.
- v1.02 correct an error when there is no padding,
bug found by caitsith2 in this post.
Downloads:
Kitkat/Lollipop (Windows)
Windows version for new logo format (android 4.4.x/android 5.x)
mlogo v1.02.zip SHA-1:
6C63079E15993915A778B53259FD960D09A33687
Kitkat/Lollipop (Linux)
Linux version for new logo format (android 4.4.x/android 5.x)
mlogo-linux v1.02.tar.gz SHA-1:
91A2773F16E47691A171F4A84E741C0E3C471725
Jelly Bean (Windows)
Windows version for old logo format (android less than 4.4)
mlogo (old format) v1.02.zip SHA-1:
7BA3689CE35FCD1CE27E6690703D05A599473962
Jelly Bean (Linux)
Linux version for old logo format (android less than 4.4)
mlogo-linux (old format) v1.02.tar.gz SHA-1:
8F2A520C0C4733F20B8D2A78BA6B9229AF2CC5E0

This tool appears to be dealing only with Logo.bin... and not CLOGO... so you might want to clarify this is for unlocked bootloaders only.
Does this tool resize any images that are larger than 1280x720? And does it take into account needing a solid border around the edges if there isn't one?

Yes the tool only manage logo.bin container and don't care of image size or number.
KidJoe said:
And does it take into account needing a solid border around the edges if there isn't one?
Click to expand...
Click to collapse
Are you sure for the solid border around the edges ?
I generate random noise image and it display without problem.

marmottepoilue said:
Yes the tool only manage logo.bin container and don't care of image size or number.
Are you sure for the solid border around the edges ?
I generate random noise image and it display without problem.
Click to expand...
Click to collapse
Yup. I am very sure.. See -> http://forum.xda-developers.com/showpost.php?p=49179887&postcount=150
and more recently a specific example with walk through and samples -> http://forum.xda-developers.com/showpost.php?p=53712454&postcount=408
And over sized images (greater than 1280x720) will also cause issues, at least when replacing the unlocked bootloader warning message.

KidJoe said:
and more recently a specific example with walk through and samples -> http://forum.xda-developers.com/showpost.php?p=53712454&postcount=408
Click to expand...
Click to collapse
I make the test on moto G (android 4.4.4) with IMAG0434.bmp (legoland toy story without border) from your post and it works.
I think the carock's script you used has issues.

marmottepoilue said:
I make the test on moto G (android 4.4.4) with IMAG0434.bmp (legoland toy story without border) from your post and it works.
I think the carock's script you used has issues.
Click to expand...
Click to collapse
Ok. I just took the logo.bin from the Verizon 4.4.2 rom, placed it in the folder with your tool. Added IMAG0434.bmp to the folder, then ran the following... mlogo logo.bin replace logo_unlocked imag0434.bmp
I then used mfastboot to flash the resulting logo.bin. It does work. So is it an issue in Carock's script itself? or FFMPEG which he is using?
Btw, doing the same using an oversized image (i.e. greater than 1280x720) with your tool does result in a scrambled screen when booting, but at least it boots and doesn't get hung.
Doing a mlogo logo-chrimbus.bmp.bin extract logo_unlocked (from a previously created logo.bin I made using carock's script) works. I get the proper 1280x720 png image.
Are there any conditions to changing the battery graphic?

KidJoe said:
Are there any conditions to changing the battery graphic?
Click to expand...
Click to collapse
I've not tested but it should be the same.
If you want to automatically reduce images greater than phone resolution you can use XnView nConvert:
nconvert.exe -ratio -rtype lanczos -rflag decr -resize 720 1280 image.png
I also updated my first post to explain how images with resolution lesser than phone's are managed.

Is this tool also available for Linux OS??

@TheStrix
You can try this (Compiled and tested on ubuntu)
Edit: moved to first post

marmottepoilue said:
@TheStrix
You can try this
Click to expand...
Click to collapse
How to execute that file??
I can see only oe file in the zip folder!
Please tell the steps

@TheStrix
It works exactly the same as the windows version.
Unzip, untar to the folder of your choice (with read/write access)
Copy your logo.bin alongside
Open a terminal and navigate to the folder
Then execute the command of your choice, for example:
./mlogo logo.bin extractall

marmottepoilue said:
@TheStrix
It works exactly the same as the windows version.
Unzip, untar to the folder of your choice (with read/write access)
Copy your logo.bin alongside
Open a terminal and navigate to the folder
Then execute the command of your choice, for example:
./mlogo logo.bin extractall
Click to expand...
Click to collapse
Its woking mate! Thank you!
Here's mine!
{
"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"
}

GUI
Hey Guys, I have made a simple GUI in java for this tool for replacing boot logo, This will make it user friendly and the process is much easier.
you can download it from link below screenshots:
you just need to keep this tool and downloaded file in same folder as shown in screenshots below.
Download Link

any way use on Razr HD ?

s27moto said:
any way use on Razr HD ?
Click to expand...
Click to collapse
I believe the logo.bin is a different format

One thing worth noting for a Moto G, and maybe the other phones, is that the logo partition max size, and therefore, the max size of logo.bin, is 4MiB. This means you could get by with only one complex 1280x720 logo. (worst case about 3MiB).
This means if you wish to do a complex normal logo, and a complex 0-3% battery logo, you will want to make sure the combined size of the 2, does not cause logo.bin to exceed 4MiB.

s27moto said:
any way use on Razr HD ?
Click to expand...
Click to collapse
I just release 'mlogo (old format)' to manage logo on phones without android 4.4.x like Razr HD (XT925).
You can download it in the first post.

I think I found a bug in your tool for the android 4.4.x logo.bin creator.
What I was trying to do, was make sure the moto g/x/e could find logo_boot, in the event that it needed to, but actually have it pretty well removed. Seems if the exact size of the compressed data happens to line up on a 512 byte boundary, the program errors when you try to append any additional data onto logo.bin If said file is replacing something in logo.bin, then the error completely destroys logo.bin
One way you can reproduce this bug, is to create an empty one color 100x100 bmp file, and feed that as one of the inputs. As long as the RLE compressed image size is not a multiple of 512, then the program will correctly work.
The main reason of wanting logo_boot to be as small as possible, while still existing, is to give as much space as possible within the 4MB max size of logo.bin for logo_battery and logo_unlocked.

Thanks OP for the tool. I appreciate the Linux support as well.

@caitsith2
Thank you for your feedback.
I make a version 1.02 that correct the bug you found.

[APP][4.4+][BACON][MATERIAL][ROOT] Bootlogo Viewer: view and flash bootlogo

*** Disclaimer ***
I have tested and tested and tested on MY OWN device and it works. If you don't have any skills or you want to make your own bootlogo safely use the versione for PC/Mac at this link: http://forum.xda-developers.com/oneplus-one/themes-apps/mod-customize-ones-bootlogo-t2857153
Introduction
This application helps you to view, create and flash your own bootlogo directly from your Oneplus One. This project is a "son" of the main one. Is a "transposed" version for Android into APP.
Before you start you need to install root functionality on your Oneplus One. To know more http://www.xda-develo...xda-developer-tv/
Screen
https://www.dropbox.com/s/nbotwdca4265i25/Screenshot_2014-12-16-18-53-44.png?dl=1
https://www.dropbox.com/s/ly0fpadb0ws4255/Screenshot_2014-12-16-18-53-48.png?dl=1
https://www.dropbox.com/s/juewkkadt2xlo9g/Screenshot_2014-12-16-18-53-59.png?dl=1
Installation instructions
Enable "Settings -> Security -> Unkown sources"
Download and install apk
Download from Google Play Store
[QRCODE]https://www.dropbox.com/s/rsa5661oknore2s/BootlogoViewer-v2.0.apk?dl=1[/QRCODE]
Download APK
Mirror 1
Mirror 2
Changelog
Code:
Current changelog: 16/12/2014
[new] Material design
[new] Export created theme (you can backup your original logo before flash a new one)
[new] SplashScreen added. It loads the internal logo automatically.
[replaced] The image must be the same size of the logo.
Older changelogs:
Code:
v1.1 changelog: 07/12/2014
[new] Added support to flash a pre-formatted zip file (read FAQ to learn how to create one)
[new] Fixed some minor bugs
v1.0 changelog: 13/10/2014
[note] First release.
[new] View images in LOGO partition
[new] Replace images in LOGO partition
[new] Flash new LOGO
FAQ
Empty
Click to expand...
Click to collapse
Thanks To/Credits
Original post for Oneplus Boot logo mod here
XDA:DevDB Information
Bootlogo Viewer, App for all devices (see above for details)
Contributors
MarchriusDennis
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2014-12-16
Current Beta Version: 1.0
Beta Release Date: 2014-10-13
Created 2014-10-13
Last Updated 2015-01-26

FAQ
1. How can I install it?
1. Go to Settings->Security->Unknown Sources and enable it. Then download and install the apk.
2. How can I change single image manually?
1. Select the image to change.
2. Long press on it and select a PNG image.
3. Push the "Send" button on top of the toolbar.
N.B. Select an image that is not smaller than the size shown in top of image view. It will resized if the size is different. So if the image is bigger 4x the image will be blurry or pixeled. You can also take a picture from camera and insert in but keep in mind the size.
3. I'm too lazy. How can I flash a themed zip??
1. Download (You don't say!?!?) the zip theme and store on the phone.
2. In app, select "Import from a Zip" and select the zip file.
3. Check if there are all preferred images and flash it!
4. How can I create a "theme" package zip?
2. You need a zip manager (on Mac OS X the default decompression utility is fine).
Create a info.xml file like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<author>Marchrius</author>
<version>1.0</version>
<date>07/12/2014</date>
Then you can add this keys (one or all):
this is the entire logo.bin and can be the original one to flash
Code:
<binary>file.bin</binary>
this is the bootlogo file image in png format and 1080x1919 resolution.
Code:
<bootlogo>file1.png</bootlogo>
this is the secondlogo file image in png format and 536x60 resolution.
Code:
<secondlogo>file2.png</secondlogo>
this is the thirdlogo file image in png format and 300x1020 resolution.
Code:
<thirdlogo>file3.png</thirdlogo>
this is the fastboot logo file image in png format and 350x313 resolution.
Code:
<fastboot>file4.png</fastboot>
this is the lowbattery logo file image in png format and 645x1074 resolution.
Code:
<lowbattery>file5.png</lowbattery>
this is the sixth logo file image in png format and 392x66 resolution
Code:
<sixthlogo>file6.png</sixthlogo>
this is the seventh logo file image in png format and 487x69 resolution.
Code:
<seventhlogo>file7.png</seventhlogo>
If you add the <binary> other won't be inserted. So, if you want to post a original LOGO binary use this key.
Then create the zip file without subdirectories or other and post it. Then donwload on the phone ad flash!

Reserved

Nice thread, finally made one!
One problem.... Still shows this error.
{
"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"
}
Sent from my OnePlus One using Tapatalk VIP

nicholaschum said:
Nice thread, finally made one!
One problem.... Still shows this error.
http://tapatalk.imageshack.com/v2/14/10/13/7e53f3bee026551c32787710eb7910ae.jpg
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Ok. Now must be ok. If not please post the log cat and grep "System info"

MarchriusDennis said:
Ok. Now must be ok. If not please post the log cat and grep "System info"
Click to expand...
Click to collapse
Just updated and it works. Good job finding all those icons in the LOGO partition.
Just wondering, with this application are you meant to be able to change all logos?
Can we also get some text instructions on how to use it in the OP (for others)? I know the video's there but sometimes people prefer text instructions! Thanks!

nicholaschum said:
Just updated and it works. Good job finding all those icons in the LOGO partition.
Just wondering, with this application are you meant to be able to change all logos?
Click to expand...
Click to collapse
Yes, you can change all the logos. I tested only the bootlogo, fastboot and low battery. I don't know how to reach other logos. But, teorically, all the functions are global.
For now, you MUST use and image that fit the logo (eg. for Bootlogo you need an image of 1080x1919) or the image is cut.

MarchriusDennis said:
Yes, you can change all the logos. I tested only the bootlogo, fastboot and low battery. I don't know how to reach other logos. But, teorically, all the functions are global.
For now, you MUST use and image that fit the logo (eg. for Bootlogo you need an image of 1080x1919) or the image is cut.
Click to expand...
Click to collapse
Check my sig, I released a series of my boot logos with my boot animations, included is the bootlogo and the fastboot logos.
I would still like to use the original tool for the computer to distribute my work though, but this is a handy tool.
Sent from my OnePlus One using Tapatalk VIP
---------- Post added at 02:41 PM ---------- Previous post was at 02:33 PM ----------
MarchriusDennis said:
for Bootlogo you need an image of 1080x1919
Click to expand...
Click to collapse
1920x1080 works. 1919 is a really odd dimension value.
Sent from my OnePlus One using Tapatalk VIP

nicholaschum said:
Check my sig, I released a series of my boot logos with my boot animations, included is the bootlogo and the fastboot logos.
I would still like to use the original tool for the computer to distribute my work though, but this is a handy tool.
Sent from my OnePlus One using Tapatalk VIP
---------- Post added at 02:41 PM ---------- Previous post was at 02:33 PM ----------
1920x1080 works. 1919 is a really odd dimension value.
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Yep but the system of the OPO want an image of 1080x1919. So the program cut the image before write it.
I pulled a request to update the program of chillstep1998 on github. He should accept the pull request.

Suggestions to add:
Backup original logo.bin
Restore from original logo.bin

It seems like this app can change even more images then the desktop version chillstep made. Great job!
Quick question. Is it possible to reverse the process and upload the stock images in case we want to make minor changes to those? I think the bootlogo and fastboot are floating around but I have yet to see the low battery and others. Thanks.

qureyoon said:
Suggestions to add:
Backup original logo.bin
Restore from original logo.bin
Click to expand...
Click to collapse
Smasher816 said:
It seems like this app can change even more images then the desktop version chillstep made. Great job!
Quick question. Is it possible to reverse the process and upload the stock images in case we want to make minor changes to those? I think the bootlogo and fastboot are floating around but I have yet to see the low battery and others. Thanks.
Click to expand...
Click to collapse
More functions added! Check it out!
Added support for a themed zip file or an original zip file to flash.

Any help with bootlogo
Create a info.xml file like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<author>Marchrius</author>
<version>1.0</version>
<date>07/12/2014</date>
Then you can add this keys (one or all):
this is the entire logo.bin and can be the original one to flash
Code:
<binary>file.bin</binary>
this is the bootlogo file image in png format and 1080x1919 resolution.
Code:
<bootlogo>file1.png</bootlogo>
Hi,
I am not sure what to put in the xml file if i only want to change the bootlogo.
Am i correct to enter the next line?
<bootlogo>file1.png</bootlogo>
Or is the name for the bootlogo a random name. Will someone point me in the right direction
Thanx

Updated version 2.0 to material design and Navigation Drawer! Check it out!
mart56 said:
Create a info.xml file like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<author>Marchrius</author>
<version>1.0</version>
<date>07/12/2014</date>
Then you can add this keys (one or all):
this is the entire logo.bin and can be the original one to flash
Code:
<binary>file.bin</binary>
this is the bootlogo file image in png format and 1080x1919 resolution.
Code:
<bootlogo>file1.png</bootlogo>
Hi,
I am not sure what to put in the xml file if i only want to change the bootlogo.
Am i correct to enter the next line?
<bootlogo>file1.png</bootlogo>
Or is the name for the bootlogo a random name. Will someone point me in the right direction
Thanx
Click to expand...
Click to collapse
If you want to change only the bootlogo you must insert the line
Code:
<bootlogo>file1.png</bootlogo>
where file1.png is the name of your file. So, if you have a file named myCoolBootlogo.png the xml file must look like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<author>Marchrius</author>
<version>1.0</version>
<date>07/12/2014</date>
<bootlogo>myCoolBootlogo.png</bootlogo>

V 2. 0
Hi receive parsing error when trying to install v2. 0.. I think the APK is not complete

mart56 said:
Hi receive parsing error when trying to install v2. 0.. I think the APK is not complete
Click to expand...
Click to collapse
Do not use external downloader. Download it with web browser (Chrome is ok)

bootviewer
Hi dude,
Downloaded through chrome but the parsing error is still there.

mart56 said:
Hi dude,
Downloaded through chrome but the parsing error is still there.
Click to expand...
Click to collapse
Try the mirror link. I don't know, it works for me ok both chrome and firefox

MarchriusDennis said:
Try the mirror link. I don't know, it works for me ok both chrome and firefox
Click to expand...
Click to collapse
Sorry Marchrius,
I tried everything from my Oneplus
downloaded from chrome and firefox to my desktop and put it on my OPO still the error
Checked if the box unknown sources was ticked
I have a size of 1,84 mb
Its a pitty i can't use your apk because i like making bootlogo's and changing them on the fly is ever so nice
greetz

mart56 said:
Sorry Marchrius,
I tried everything from my Oneplus
downloaded from chrome and firefox to my desktop and put it on my OPO still the error
Checked if the box unknown sources was ticked
I have a size of 1,84 mb
Its a pitty i can't use your apk because i like making bootlogo's and changing them on the fly is ever so nice
greetz
Click to expand...
Click to collapse
This is the md5sum c0991233222478cb9cf1f91fa42997c5. Can you check yours?

[GUIDE/ODIN/FW/BL] SM-P610 USA/XAR WIFI ONLY: Stock Firmwares + Modded BL WarningText

THIS IS YOUR FIRST WARNING (WILL BE REITERATED PLENTY OF TIMES!) IN BIG RED BOLD LETTERS - THESE FILES ARE FROM/FOR THE USA ("XAR") REGION, SM-P610 WIFI MODEL ONLY!
(with the exception of the Odin utility, as well as possibly the modified boot splash screen, which may work on other variants, though untested and done solely at your own risk - read all the notes!!)​
I already went through the work, so I figured I would share these files for those who also own the same exact tablet. Again, it's for the USA/XAR region Samsung Galaxy Tab S6 Lite WiFi Model ONLY - "SM-P610" / "gta4xlwifi". LTE model is a different variant; do NOT flash the stock firmware files to that device! Also, sorry, I will not support or answer questions for other variants (other than what I will mention in this OP). Downloading firmwares for other variants will be a huge PITA, and I don't have / pay for any "premium" accounts which would allow me to quickly download the huge firmware files. I'm only sharing these I'm posting because I already took the time to acquire and archive them for personal usage, and might as well share them for those who own the same device / variant.
Use these files at your own risk, and only flash if you know what you're doing!! I'm not responsible for any problems user may incur from usage of these files, the usual warnings apply, etc. This device is just a backup / playaround device for me, and so it doesn't get daily usage out of me, nor will I likely be very active on this subforum (sorry! just being honest). Also, I immediately installed LOS on my device anyway, so I don't run stock ROM myself and therefore won't be sharing pre-patched Magisk boot images either. Sorry to those who are used to that from me =)
So anyway... what's in this post?
Odin3 v3.14.4 (version I've been using on this device, and working perfectly fine as of this initial posting)
Stock firmware zips for USA/"XAR" Region SM-P610, WiFi Only
Modified BL file (Odin-flashable), to remove the warning boot text
Odin3 v3.14.4:
I posted this in another thread, but figured I would also link to it here so it's easy to find in one place. This worked perfectly fine for me to root / install TWRP / flash BL files, etc.
Download Link: https://www.androidfilehost.com/?fid=10763459528675582443
Stock Firmware Files:
USA/XAR WIFI ONLY! October 2020 Update - Firmware Version P610XXU2BTJ5
Download Link: https://www.androidfilehost.com/?fid=10763459528675592742
USA/XAR WIFI ONLY! September 2020 Update - Firmware Version P610XXU2BTI3
Download Link: https://www.androidfilehost.com/?fid=10763459528675592159
Firmware files for other variants, see this post. Follow the links, use the resources, consider the context for other variants: https://forum.xda-developers.com/showpost.php?p=83083249&postcount=2
Modified [BL-slot] Odin-Flashable File To Remove Warning Splash Screen Text:
My Thoughts On This...After unlocking the bootloader and flashing non-stock images, we all know we end up with that annoying, ugly splash screen screaming that the device is modified. Most of us modifying our devices understand the security implications involved, and ironically choose to modify our devices to increase security in other ways. Yet, these warning splash screens, in the unfortunate event of possible theft, may very well end up being the reason a more tech-savvy thief is able to break into the device, or find someone who can. So, thanks to users' posts Awesomeslayerg's hint and blascogm's guide, I quickly came up with an Odin-flashable file to change the splash screen, as seen below:
(if the pic doesn't show, probably the imgur link I used is dead, but I also attached it to this post)
{
"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"
}
I know some people may be thinking "why not just remove the PRESS POWER KEY TO CONTINUE line completely and have it stay at the normal boot screen seamlessly the whole time", and the reason I decided not to do this is because it generally wouldn't make the average person suspect the device is modified, and it's still good for us to know that it's at the boot stage where we can hit the power key to skip the ~10 second timeout. It's exactly the same image, so it's still very seamless and stock-like. I even took the time to center the power key text exactly, by the pixel, from left to right and from top bottom relative to the knox and android logos.. ; )
And if it really bothers you that much, follow the guide I linked above and do it yourself. =)
I should also mention that, for our devices, the .bin.lz4 file that needs to be decrypted is actually "up_param.bin.lz4" and not "param.bin.lz4" as suggested in the guide, as it's for a different device. You will need the lz4 utility (check Awesomeslayerg's thread, or google lz4 github) to decrypt the lz4 file to a regular bin file, and then you can extract and/or replace the .jpg files using an archiver program (I recommend 7-zip for this).
The hash checksums for every single file/jpg in each up_param.bin were identical between the September and October firmwares. Therefore, at least as of this posting, the same modified Odin-flashable file will work on either firmware version, and likely future versions until they make any significant changes. I did test this myself too btw. Also, if you look at the structure and contents of the up_param.bin file for yourself, you'll see that they are simply .jpg files containing the screens, backgrounds, and text you're all familiar with when going into bootloader / download mode. Assuming they follow the same file naming structure, I suspect you can probably flash this to other variants, although it will change the text language to English (assuming they localize the bootloader / download mode text per every region; I have no idea about this as I only own US variants). To see what I'm talking about, here's a quick screenshot (better resolution pic, and just in case imgur link dies, also attached to this post):
Now that I (hopefully) tricked you into reading this entire section so that you now have some basic understanding of how it works before proceeding to flashing the warning text removal mod, here are the instructions / link for install:
- Download the .tar file provided below.
- Boot device into Download mode.
- Place .tar file into bootloader [BL] slot in Odin and flash.
Download Link: https://www.androidfilehost.com/?fid=10763459528675592179
To revert back to stock splash screen with warning text, for whatever reason:
Pull the stock up_param.bin.lz4 from the stock firmware file (from the BL****.md5 file within the firmware zip).
- Convert it to up_param.bin uzing lz4 utility.
- Add up_param.bin to an archive as .tar file, uncompressed (recommend using 7-zip).
- Flash the .tar file, which should contain only the stock decrypted up_param.bin file, in Download mode using Odin in the BL slot.
I uploaded my custom jpg's, as well as the stock untouched jpg's, for those that are curious or want to edit them further. Feel free to snag them here: https://www.androidfilehost.com/?w=files&flid=320350
* As we can see, we're only modifying the .jpg files provided by up_param.bin, so it's a relatively harmless process (unlike modifying aboot files in the old days of HTC devices, which if done improperly could literally result in an unrecoverable brick). But even so, please only flash if you know what you're doing and can recover from any potential mistakes or errors.

Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609

And another

Hi,
Thanks for these resources. I'm actually not at these steps yet. I'm having trouble gaining access to the OEM Bootloader Unlock option in developer options. Here are things I've tried already based on what I researched before my attempt.
Android 10 is the current OS installed after unboxing.
1. Disable Automatic Date and time
2. Select a date more than 7 days prior to current date of attempt.
3. Under Settings > About Phone > Software Information. Select/Tap Build Number 7-8 times to unlock Developer Option.
4. Disable Auto Update System (Apply Updates When Device Restarts) - *This was somehow already disabled the first time I entered Developer options*
5. Under Software Updates > Disable Automatic Updates -*This was also already disabled on unboxing and it says Automatically download updates over Wifi. It does not say Automatic Updates*
6. Reboot device and return to Developer Options after booting to OS.
7. The OEM Bootloader Unlock option should appear greyed out at this point. Toggle it to unlock bootloader with consideration that it will wipe the device data.
These are the steps I've found and tried with no success in gaining access to the Bootloader unlock option. I am also certain that my device is the international model SM-P610 with Exynos chipset and Mali-G72 GPU. Something else to note, I did uncheck many default options tied to improving privacy on the device before attempting the steps to gain access to the bootloader unlock option. I do not know if that would make a difference. If you recognize anything wrong with the steps I've tried already, please let me know where I'm going wrong or where I can find the correct way to unlock the bootloader. I've been posting in other threads, but nobody seems to be replying to me. Any help will be appreciated.

Hi
I've flashed your modded file on my PHN (Netherlands), no problems at all working ootb!

Hi. I used blascogm's guide for my P615 with latest firmware for SEC UI 3.1and all are OK! Thanks for all.
Add. I add link . Flash via Odin(BL).
https://androidfilehost.com/?fid=14943124697586347282

i5lee8bit said:
Not sure if there were any changes since the September / October 2020 firmwares, but here's a new one directly modified from the March 2021 (Android 11) firmware base:
NEWEST DOWNLOAD, BASED ON 2021-03 FIRMWARE:
https://www.androidfilehost.com/?fid=14943124697586346609
Click to expand...
Click to collapse
I flashed ths when I'm running lineageos 18.1 annd this is the only mod that worked for me

Thanks for posting your images and linking to the guide, worked perfectly and the images just fit to the pixel <3

Confirmed working as of March 2022. Device is running base P610XXU2DUL9. Thanks for the hard work.

can you make one for SM-P613 model plz?