yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ChitownWingMan:
Works perfectly

Works simply and perfectly on T-Mobile SGH-T999 w/UVLJ4 firmware (ICS 4.0.4)

Just follow the instructions and everything works perfectly.

If you are resizing an image try to crop it to the same 720x1280 ratio (16:9 or 0.5625).

That means crop your image where the width is 0.5625 times the height.

For example if the height of your image is 3260 pixels make the width 1,833 (0.5625 x 3260) wide.

This will yield an image that fills the screen with the least amount of distortion.

Thank you button clicked.
[Verizon Samsung Galaxy S III] con247:
Thanks for the resolution tip. Please feel free to post any of the splashes you make for others to enjoy!
[Verizon Samsung Galaxy S III] ChitownWingMan:
I really don't think anyone would be interested in my wife in her wedding dress holding her flowers :).

I am a photographer so maybe I will make up a few just for fun.

I guess the next step would be a splash screen rotator that would sequence through several screens.

I have seriously thought of writing a program to create boot and shutdown animations that does just that.

Thank you for your excellent work
[Verizon Samsung Galaxy S III] norbarb:
I make lot of them here : http://xdaforums.com/showthread.php?t=1951551 and trying add one a day.
[Verizon Samsung Galaxy S III] Ghostfreak NB:
Hey OP can you lend me some help in making this work on Sony Xperia Neo V??

Nice work :thumbup:

Ty in advance for any help
[Verizon Samsung Galaxy S III] ChitownWingMan:
Important note

Please note. The image must be 720 pixels wide (referenced to the 720 pixels width of the display regardless of the orientation of the splash image)

I don't know if this is a conversion issue or an issue with the splash screen display firmware but if the image is less than 720 pixels wide the image will appear to "tear".

For those technical minded out there it appears that either the converter or the firmware writes (or displays) 720 pixels per row regardless of how many are in the original image. Hence the tearing effect.

I did not try to see what would happen if an image had more than 720 pixels per row.

It appears that height is not important.

My suggestion is to use the following procedure to create your image (regardless of the size and type or your original)

1. Download PNGtoFlashableSplash.zip to your computer

2. Decompress PNGtoFlashableSplash to a directory (folder) on your local drive

3. Crop your image to 16:9 ratio

4. Using a constrained (fixed) ratio resize your image to 720 x 1280

5. Save the resultant image as a .png

6. Copy this image to PNGtoConvert\initlogo.png in the directory (folder) used in step 2

7. Run the PNG-2-RLE.bath file from the directory (folder) used in step 2 (note this must be run from the directory [folder] used in step 2. The batch script will not find the png file if you don't.)

8. Copy the flashthisfile.zip file from the directory (folder) created in step 2 to your phone

9. Reboot to your favorite recovery utility (TWRP or CWM)

10. In the recovery utility install flashthisimage.zip

11. Reboot and Voila your new splash image is installed

For the curious and detail minded:

Host OS: Windows 7 32-Bit

Photo Editor: Adobe Photoshop CS5

Phone: T-Mobile Galaxy S III SGH-T999

Firmware: T999UVLJ4 (Stock Pimped)

Recovery: ClockWorkMod Touch 6.0.1.2
[Verizon Samsung Galaxy S III] con247:
Probably not for the wedding pic lol. An "animated" splash would require kernel changes because the stock splash implementation is a static image. Kernel changes would be impossible to do to an existing kernel.

Sweet!

If you can prove to me your splash screen is stored in your boot image as a .RLE or other image file that is editable maybe. Otherwise, nope.

Basically if one follows my recommendation in the OP to use a 720x1280 PNG there shouldn't be any issues.
[Verizon Samsung Galaxy S III] ChitownWingMan:
Very true.

The problem is converting a non-16:9 aspect ratio image to 16:9 format without too much distortion of the original image. Very few cameras have a true 16:9 aspect ratio as their native format. Most cameras are somewhere between aspect ratios of 3:2 (35 mm film is 24mm x 36mm) and 4:3 (the Sony "four thirds" system for example). 16:9 is almost panoramic in the photo world though it is the standard in video and cinema.

If the image being used is not 16:9 just resizing it to 16:9 will distort it. Doing a constrained (maintaining the aspect ratio of the original image) re-size will rarely produce a true 720 x 1280 image because the original image was not 16:9.

The only way to insure that the resultant image is the correct size (720 x 1280) is to crop it to the 16:9 aspect ratio first and then re-size it to 720 x 1280 afterwards.

That is all I was trying to point out.

I rewrote your instructions to stress the need for the correct aspect ratio prior to re-sizing.

The conversion program I used for my HD2 in days of old was passed in the height and width of the input and the output files so tearing wouldn't happen. Missing pixels in the incoming image rows were written to black and extra pixels in the incoming image rows were skipped.

By passing in both sets of parameters a reasonably generic conversion program can be written. This of course assumes that different roms use the same splash file format. Writing a truly universal program would be a logistical and support nightmare.

Any way I was just trying to help people to make better and easier use of your program.

I hope I may have helped somebody with this.

That's the problem with being an old school engineer/programmer we need to tweak everything :)

And for the animated screens, I was referring to the existing Android startup and shutdown animations not creating an animated splash screen. I agree that would require a firmware change :)

Thanks again for creating a very easy process...
[Verizon Samsung Galaxy S III] Green Ranger:
Wow this is very neat. Thanks for sharing this. Gotta try this when I get home tonight.
[Verizon Samsung Galaxy S III] nerys71:
any chance of a version for the US Note II ? (and the US S2 running jelly bean)

as for using non ratio images this is pretty easy.

non ratio images are almost always "too wide" so here is how you "get it" right without distortion.

open a blank black PNG that is already 720x1280

RESIZE your desired image to 1280 tall (keep aspect ratio) select all copy

now goto your 720x1280 PNG and paste.

your image is larger than the canvas your pasting to so you can "move it" side to side as you see fit till it "fits" and "looks right" without exposing an edge.

Flatten the image and save.
[Verizon Samsung Galaxy S III] con247:
Nope
[Verizon Samsung Galaxy S III] nerys71:
do you know why? a simple nope is insanely unsatisfying :) hehe
[Verizon Samsung Galaxy S III] con247:
Things that use the exynos have the splash embedded in the kernel so it can't be changed without recompiling the kernel

Sent from d2_vzw
[Verizon Samsung Galaxy S III] fcon:
Hey, great work! This is what I love about android. As a UofM alum I was very pleased to see this tool come from a fellow maize and blue fan. Would it be possible to link the block m you created already? I have been looking online for a suitable candidate and I can't find one. I want to tease my apple toting roomate with what I can do with my phone and I figure a block m splash screen on reboot is a good start!

Thanks!
[Verizon Samsung Galaxy S III] con247:
I attached it to this post. Glad there is another Wolverine here.
[Verizon Samsung Galaxy S III] alquimista:
*Nix Version

I think all you would need to do this in linux is:

Download the zip in the OP

Make sure ImageMagick installed (should be in most linux distros, you need it for the "convert" command)

Download the tools zip from [TOOL][LINUX]PNG to RLE conversion scripts - make your own splash screen!

install 7zip command from where you can find it (depends on your linux distro)

Delete all the binaries in con247's /bin folder and replace them with the binaries from "splashtools". Then re-write the batch scripts so they work in linux.

Should work. I'll give it a whirl and post what I find.

OP - Can I post a modified version of your zip that works in linux?

TA,

ALQI
[Verizon Samsung Galaxy S III] alquimista:
I am taking NO CREDIT for anything whatsoever with this tool. I just did a litle mashup for Linux and Mac people. So here goes...

I made a *Nix version of con247's adapted tool.

PREREQUISITES:

Your OS muse be some *Nix variant.

ImageMagick must be installed for your OS

p7zip must be installed for your OS

Build/Download/Find rgb2565 and 5652rgb for your OS

The rgb2565 and 5652rgb binaries are built from:

to565.c

from565.c

To build the binaries yourself you should probably already have android source on your machine (NOT THE SDK, the source as described on source.android.com HERE). Or if you know what you are doin just follow the instructions in the Android.mk and .c files themselves. I supplied both ".c" files and their Android.mk files in /bin/OS/_MAY_NEED_TO_COMPILE_ for anyone who wants em.

Once you have the zip downloaded from this post, and have read the prerequisites. Unzip the file to your home folder. Open up a terminal. CD to the unzipped folder. Run setup.sh, or just chmod +x all the scripts and binaries. I built Mac versions of the binaries, 5652rgb and rgb2565, and left them in the /bin folder, so this will work for Mac out of the box. For other *Nix based distros, try copying 5652rgb and rgb2565 from /bin/OS/Linux to /bin. It doesn't really matter if you overwrite the Mac binaries, they will only work on darwin_x86_64 anyway.

Now that everything is setup, put a 720x1280 PNG in /PNGtoConvert and rename it "initlogo.png". Then open a terminal and cd to $HOME/PNGtoFlashableSplash_Nix. Then run png-to-rle.sh and wait for the magic to happen!!

Let me know if it works!! Or if you can't understand what I just wrote, PM me, cause i'm too pissed to type at the moment.

TA,

ALQI
[Verizon Samsung Galaxy S III] alquimista:
I looked around and there are some tools to do this on devices that have the .rle built into the kernel.

Like KernelTools by ChampionshipSwimmer

You will probably have to tweak alot of stuff in there to make it more specific to the Note2, but it looks like fairly simple stuff. I'd make it myself, but I don't have a Note2 and don't know much about the device.

Ok, time to get back to working on me own tools and stop messing about in other blokes threads.

TA,

ALQI
[Verizon Samsung Galaxy S III] vdub2pt0:
Is there any way to fun the batch file from the phone? My computer is down at the moment.
[Verizon Samsung Galaxy S III] nerys71:
now that would be cool. screencap/image load app on the phone right to the zip file all on the phone. but the user base would be so extraordinarily limited it will likely never happen :)
[Verizon Samsung Galaxy S III] Stranger_84:
quick question ... if i wanted to change the image to a different oneis it possible to just flash a new image or do i have to delete the old one first?
[Verizon Samsung Galaxy S III] alquimista:
No need to delete the old .rle from the phone. You can delete the old zip just to keep confusion down.
[Verizon Samsung Galaxy S III] nwre:
Just wanted to ask if anyone has tried it on Bell's (Canada) S3?

Probably just the same with the AT&T version like with everything else... just wanted to make sure. Thanks
[Verizon Samsung Galaxy S III] con247:
It will work with any S4 based GS3. Have fun!
[Verizon Samsung Galaxy S III] DroidSensei:
Hi everyone,

I'm Italian and I have a Galaxy S3 with ROM stock (rooted with CF - root 6.4). I tried to create and install a new splash screen and to install the android1splash.zip (with original screen), but I obtain the following error in both cases:

CWM-based Recovery v5.5.0.4 :: CF-v1.5

--Installing: /emmc/android1splash.zip

Finding update package...

Opening update package...

Installing update...

assert failed: getprop("ro.product.device") == "d2vzw" || getprop("ro.build.product") == "d2vzw" || getprop("ro.product.device") == "d2spr" || getprop("ro.build.product") == "d2spr" || getprop("ro.product.device") == "d2att" || getprop("ro.build.product")

E:Error in /emmc/android1splash.zip

(Status 7)

Installation aborted

Could this error depends from galaxy S3?

Thank you in advance.
[Verizon Samsung Galaxy S III] alquimista:
What version of the S3 do you have? I would assume the I9300 international version. If so, this tool will not work. You would need an I9300 boot.img and a set of code to create an update.zip specifically for your version of the SGS3.

HTH

ALQI
[Verizon Samsung Galaxy S III] DroidSensei:
Hi alchimista, you're right. I have the international version.

Can I make something to create an update.zip for my version?

Eventually where I could find information to create the right version of flashable zip?

Thank you!

:)
[Verizon Samsung Galaxy S III] con247:
Please read the thread. It says NA variants only in the OP. i9300 support will NEVER happen due to the way Samsung stores the splash image on the device. A kernel developer can add their own splash, but it cannot be changed without making a whole new kernel each time. The zip failing was for your protection. It would likely have bricked the device had that check not been in there. Please in the future do not flash things outside of the i9300 section.
[Verizon Samsung Galaxy S III] DroidSensei:
Hi con247,

thank you for your suggestion. Unfortunately I'm a beginner, so I'm not very good with root management. :o

I will be very careful and I'll take your advice!!

Thanks a lot :D
[Verizon Samsung Galaxy S III] raymond26170:
JB 4.2

What needs to be done to get this to work with the latest 4.2 jelly? I have tried to get it to work on ATT S3 running Task650's latest AOKP. Thanks!
[Verizon Samsung Galaxy S III] con247:
Send me the boot.img from the rom and ill look at it next week when I get home from vacation.
[Verizon Samsung Galaxy S III] JLow0214:
First off just want to say love your splash maker. I recently jumped to 4.2 and I know it doesn't work with it but now I can't even get the stock splash back unless I flash a previous version. Even after I get it back by flashing an older ROM when I flash the 4.2 ROM still no splash. Anyone got any ideas on how to fix that?

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] dragon1357:
I tried this, it compiled and flashed successfully, but my boot image stayed the same. I am on vzw galaxy s 3 jellybeans rom, with lean kernel from imoseyan. It has that pink boot image, so I was tempted to try something new :P
[Verizon Samsung Galaxy S III] Archangel:
Unfortunately until imo takes the pink coloring out of the kernel whatever you flash will be pink. Trust me I tried and everything turns pink.
[Verizon Samsung Galaxy S III] dragon1357:
HMM, interesting, what if you flashed a the image with green text, does that still make the text pink? Or will it combine colors? And if so, why does the black background not get combined?
[Verizon Samsung Galaxy S III] Archangel:
Yeah I tried that,,,I used GIMP to change the text color to blue on the stock splash and it was still pink lol
[Verizon Samsung Galaxy S III] Jugger naut:
Posted some Splash Screens here : http://xdaforums.com/showthread.php?t=2096148

More to come

Thanks again con247
[Verizon Samsung Galaxy S III] Galaen:
I'm not trying to be pushy. I'm sure you have a million other things going on. But, have you had any luck with 4.2?

Sent from my AT&T GS3
[Verizon Samsung Galaxy S III] JLow0214:
I been wondering same thing just did t want to ask lol

Sent from my SCH-I535 using Xparent ICS Tapatalk 2
[Verizon Samsung Galaxy S III] AldehydeGFX:
This is really cool, I'm going to give it a try once I make a suitable Logo. Thanks for this :)

Ok, so I made this for myself and it worked just fine, thanks again!
[Verizon Samsung Galaxy S III] ywalker:
I found this tool last night and have made some fantastic splash screens for my phone. Thanks for sharing.
[Verizon Samsung Galaxy S III] azbobs:
Very nice thx!

:thumbup:

cOming frOm my

smOking sOOmth

Synergy r443

---------- Post added at 11:14 AM ---------- Previous post was at 11:10 AM ----------

Nice this for sharing

:cool:

cOming frOm my

smOking sOOmth

Synergy r443
[Verizon Samsung Galaxy S III] cordell12:
bump 4 use on AOSP/CM

http://review.cyanogenmod.org/#/c/34911/ nice work invisiblek for the kernel commits (and a TON more!)

thanks for the mod con247
[Verizon Samsung Galaxy S III] theabnormalone:
So I followed the instructions in the OP to the T. I am using Ktoonz latest kernel and when the splas screen comes up its not a solid picture. It looks like the image is overlaid on itself repeatedly. Any help?
[Verizon Samsung Galaxy S III] calebsb:
If the image isn't exactly the right size it will do weird stuff. Happened to me once. That could be it. I thought mine was right but looking at PNG properties of the image it told me it was a little off

*
[Verizon Samsung Galaxy S III] shazo85:
I saw this posted in the Sprint forums for the S3. I figure with the OP saying to come here it will be a better chance in getting help than to post in the Sprint one. I'm using MOAR 5.01 with Freeza's Optimized Kernel. I have downloaded the zip file and converted the jpg file I had to a PNG file then used the zip file to convert it to use as a splash screen. I used a site to convert to the PNG and a 720 pxl x 1280 pxl. I took the zip file that was made with the splash screen converter and renamed it from "flashthisinrecover.zip" to Jelly_Bean.zip so I knew what it was from the others. After I flash this my phone reboots twice and uses what ever the last image was.
[Verizon Samsung Galaxy S III] spitfire143:
Did you wipe out cahce a davlik? That did the trick for me
[Verizon Samsung Galaxy S III] moparfreak426:
Will this is t!

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] RBarnett09:
If I'm running an AOSP ROM, does this splash image tool still work?
[Verizon Samsung Galaxy S III] Hayzie:
I thought I posted in this thread already a while back? Anyways, thank you for this tool. Love it and it makes my phone complete. :fingers-crossed:
[Verizon Samsung Galaxy S III] KonradIC13:
Is it normal

Is it normal that conversion can take up to 10 minutes and even more?

It takes a lot of time and im not sure if its supposed to be that way, or something is wrong and im just wasting my time.

This is the rle i want to convert is from 800x480 tablet device (attached to post)

The file in RAW-Images is 200mb and still rising and its on STEP 1: Converting to RAW format for like 10 minutes already.

///After an hour or so the RAW image (not even finished one) grew to 1GB, im not going to waste time. Some please tell me if he/she managed to convert stock RLE initlogo to a PNG file, and how long it took?
[Verizon Samsung Galaxy S III] bigpappags3:
This is made for the US version of the gs3 so that may be the reason that it's taking so long. It should only take a minute maybe 2 at most.

I'm not sure if all rles are created the same so with you trying to use that of a tablet may be ur problem. Try making a png to rle 720x1280 and then taking the rle from that and run the rle to png. That will test it and insure it is working properly. Both should only take 1 to 2 mins.
[Verizon Samsung Galaxy S III] KonradIC13:
Thanks, i just tried playing with stock image that is in zip and its working fast as lighting, i think the problem may be that the RLE file created from the Samsun logo that is in zip is only 7kb and RAW is like 3 mb while the logo in my tabled has 1.5MB RLE so the RAW would be like over 1GB? something like that, so thats why it takes soooooo long.

So i managed to convert mine custom png file to rle, but im not trying to flash it because i assume thath flashthisimage.zip will only work wih specific device Samsung Galxy SIII?
[Verizon Samsung Galaxy S III] bigpappags3:
Correct. ..it's only for samsung galaxy s3
[Verizon Samsung Galaxy S III] EindhovenOne:
Worked perfectly on JellyBeans ROM!
[Verizon Samsung Galaxy S III] nerys71:
any chance for some Note 3 loving? snapdragon processor in the us not exoynos :)
[Verizon Samsung Galaxy S III] Tsumi:
Tried to flash the stock splash screen, didn't work. T-mobile SGH-T999 using MOAR and ktoonsez kt747 kernel. It keeps showing ktoon's splash screen.
[Verizon Samsung Galaxy S III] tyler.frost92:
having the same issue with the ktoonsz kernel
[Verizon Samsung Galaxy S III] tyler.frost92:
So I realized i had been naming the file "initlogo.png" when the file type was already a png. Changed the name of the file to just "initlogo", made a new zip and copied it to the phone, wiped cache and dalvik and everything is fine now.

link: https://drive.google.com/file/d/0B9y7AUvoDRPGOHRiTXV4dnNlNlE/edit?usp=sharing
[Verizon Samsung Galaxy S III] fffft:
Does anyone know if this script is compatible with a US S4 under 4.3 OTA?

The comment above in the OP suggests that it might be.. but that was posted before the 4.3 OTA update.

I'm getting an assert error when I try flashing it to a US S4:

assert failed: getprop ("ro.product.device") ==

E:Error executing updater binary in zip 'external_sd/flashthisimage.zip'

.
[Verizon Samsung Galaxy S III] bigpappags3:
Not trying to be a total a$$, but...lol u r kinda answering your own question.

http://i.imgur.com/qrByUGN.jpg
[Verizon Samsung Galaxy S III] fffft:
No problem, it'd be hard to take anyone who punctuates a sentence with lol seriously even if your reply wasn't specious. For the benefit of anyone else finding this thread later, the OP apparently meant S3 CPU and made a typo.

However we can update the S4 bootloader logo by decompiling boot.img with a tool like ROM kitchen. The logo is formatted as an RLE file. Provided the bootloader isn't locked, you can convert your same resolution png image to RLE and recompile. The S4 kernel is located at /dev/block/mmcblk0p20

.

.
[Verizon Samsung Galaxy S III] deskjet390:
Pretty sure he is talking about the Qualcomm Snapdragon S4 processors located inside our U.S.A. d2 variants. As apposed to the Samsung Exynos 4 of the international variants
[Verizon Samsung Galaxy S III] jimwick:
.......... hahahahaha, you got corrected on a forum for sentence structure by a guy whose name is the same sound I make in the bathroom every morning, hahahahaha........ Next time just tell him its the Flux capacitor that fell out of aliment ......
[Verizon Samsung Galaxy S III] jsin95:
GS3 AT&T (i747) variant here. I am using a custom AOSP kernel and CM based ROM. I kind of messed up...

I used the convertor with a 720x1280 png image. I then flashed it onto my phone with the newest TWRP to replace a previous custom kernel's boot logo. Now my phone is an infinite boot loop, with only the Samsung word flashing. The phone will not go into recovery but download mode works. What should I do?

Edit:

Well, if anyone has the same problem as me this helped me get back into recovery. Still don't know where this will take me....

I restored my original kernel (so glad I backed it up) and my phone finally booted in! However, the boot logo didn't change when I tried patching it again.

Edit 2:

Stock kernel allows me to change the boot logo; so does BMS. Now I know this isn't compatible with dkp kernel :)

Edit 3:

installed dkp over BMS while I had my custom boot logo. It worked. I don't understand anymore.
[Verizon Samsung Galaxy S III] :
Soooo.. Is it safe to use this tool with the i747m variant (default CM 11 rom and kernel) or not??
[Verizon Samsung Galaxy S III] rjm12rjm12:
Thanks for this, I was ready to try something new.
[Verizon Samsung Galaxy S III] :
It works flawlessly with i747m variant (default CM 11 rom and kernel). Thanks!!
[Verizon Samsung Galaxy S III] Heavy Metal:
Will it work on the S5? AT&T?

SAMSUNG-SM-G900A, with 128gb SD & Rooted.
[Verizon Samsung Galaxy S III] RockRatt:
I would not try it. I tried making a version for my ATT S4 the first week I got it and I softbricked it bad enough that it needed JTAG to fix it.

Sent fron I337 Red BadAss Themed ShoStock 7.0