yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kimchi0400:
Just an FYI - the batch script for eclair has a little problem where it tries to write the logo_ATNT.jpg to the /sdcard directory, which isn't allowed (error saying cannot write, location is a directory). So to fix it, I edited the batch script and added a / to the erroneous line to point it to the /sdcard/ location, which allowed the batch to complete properly.

AND TO ALL YOU GUYS COMPLAINING ABOUT STILL HAVING THE AT&T SECOND SCREEN:

It's been said many times that the second screen you see is the KERNEL screen. Once a custom kernel with a different screen has been released, you'll be able to replace it with whichever logo is used by the kernel.
[Captivate Android Development] Peaster111:
Thanks... You have one punk very happy... LOL. ;-)
[Captivate Android Development] connexion2005:
Fail on my part of writing "eclair" instead of "froyo". I changed it and as mentioned it doesn't work as 2.2+ uses /mnt/sdcard for the location versus the older Android OS using just /sdcard.

Also, the AT&T screen is the KERNEL screen and not related to this. Ask DG to toss in something custom on his CogKernels... :)
[Captivate Android Development] paracutin:
I have the same setup (Serendipity 7) and I am having the same problem.

I am using the package from the 1st post. There is never an error generated by the bootscreen installer with the exception of logo.jpg already existing on the sd card or busybox already installed. Every time I reboot it is a scrambled image. Also, read somewhere to load the param file with Odin then use Root Explorer to move logo.jpg to mnt/.lfs after making permissions RW. That doesn't work for me either. Root Explorer FCs every time when trying to access mnt/.lfs.

HELP please!
[Captivate Android Development] spartan062984:
Yo Josh!

Sent you a PM. Don't know if you got it or not, just making sure.
[Captivate Android Development] irishvandal:
if you guys are on S7 and want to change out the FIRST boot-screen(jpg image) just go to the S7 Thread post 3 and look for MobileTechVideos_BootReplacer.zip.

DL the zip and place on the PC

Open zip inside a fresh folder

Open txt file and follow directions

This will only change the FIRST boot-screen, however, you CAN use YOUR OWN custom 480x800 jpg. just make sure you rename it, WHAT? yep, logo.jpg and place it in the installation folder unzipped a minute ago.

The SECOND boot-screen is the kernel boot

The THIRD boot-screen is the bootanimation(animated boot-screen) which on GB 2.3.3+ are located at system/media/ and is now named sanim.zip.

Remember that, the bootanimation.zip is NOW named "sanim.zip"

You can keep as many bootani in the media folder itself, just rename them to whatever will help you remember the file itself and of course make it a back-up file. so it would follow

- sanim.zip(default samsung boot) is getting replaced by bootanimation.zip(lets say it is a flaming skull) in system/media/sanim.zip

- rename original sanim.zip to samsung.sanim.zip.bak

- paste bootanimation.zip in system/media

- rename bootanimation.zip to sanim.zip

- reboot and you should have a 99% shot of having a custom animation boot-screen

- TIP - when you replace the second sanim.zip, name it something like flame.skull.sanim.zip.bak and keep it in system/media folder

There are three total boots during start-up and i believe only one qmg shutdown image.

Before anyone asks or pm me,

i DO NOT know how to make a sanim.zip pack as of yet.

i DO NOT know how to change the shutdown boot as of yet, i know it has to deal with some kind of qmg file i believe. and not many are looking to hack/crack this method yet.

i DO NOT know how to install sound for either as of yet.

i DO NOT know how to change the start-up boot time for the third boot(sanim.zip).

I DO know it is in the kernel side.

I DO know that S7 4.1 kernel has extended this time for the third boot/sanim.zip.

I hope this helps others as I have done quite a bit of research/Google/pm and only wish to share what has been confirmed to work. I have had success with Serendipty 7 kernel and ROM, APEX 7.2 ROM and TALON kernel using these methods.

Just give a thanks if it does help, plz.

EDIT - DarkCore kernel bootanimation file name is bootanimation.zip inside the system/media folder.

Talon kernel 0.4.2+ bootanimation file name is sanim.zip inside the system/media folder.

I will try to get back to this post and clean it up soon as I have learned a little bit about the procedures a little more form the original posting. Right now i am dealing with a Bootloader logo jpg issue and still trying to track down some type of real answer as to why this app/program in the first post will not jive together with the ATT KF1 BL. I have been holding a garbage screen for two days now as I am leery to keep flashing back my KF1 BL over and over in fear of brick my Cappy somehow, fingers crossed nobody has to go thru that.
[Captivate Android Development] nybmx:
Just wanted to verify that following these steps worked perfect on Continuum V6 RC1 w/ KF1 AT&T bootloaders.
[Captivate Android Development] VFO:
I did this with Continuum but I am getting constant Forced Upload and Kernel Panic screens on boot. It shows the new boot screen then Kernel boot screen and then boot animation then shows the unlock screen for about 2 seconds then goes into kernel panic. When I revert the boot screen change this issue goes away. I have succesfully done this mod with Froyo a couple of times with no issue but now when running Continuum V6 with KF1 Bootloaders I am having this issue. Can anyone offer some suggestions?
[Captivate Android Development] t3chn0s1s:
Hey, just so you know Root Explorer force closes for me EVERYTIME I try to access my mnt/.lfs folder too. Try using another file explorer program like ES or File Expert to move a file and rename it to logo.jpg. That is the ONLY way I was able to change my boot screen. Hope this works for you.
[Captivate Android Development] t3chn0s1s:
Trying to change boot screen again...

Ok, this is kinda funny. I am running Serendipity 7. Knowing that the mnt/.lfs folder houses the boot screen logo.jpg file I decided to just rename the .jpg file I wanted to be my boot screen & moved it into that folder using File Expert (the FIRST TIME, since Root Explorer kept FC'ing when trying to access the mnt/.lfs folder and it worked fine.) So, I decided I wanted to change my boot screen (AGAIN) to something else now & File Expert, nor ES Explorer, nor SD Maid Pro or ANY OTHER root file mgmt app will NOT let me change file names or delete files out of this particular folder (mnt/.lfs). I keep getting an 'operation failed' type of error message. Does anyone know WHY? And, YES I am mounting the file system as READ-WRITE. HELP?
[Captivate Android Development] mikehe:
can i remove the kernel boot file if so what am i looking for.
[Captivate Android Development] b0uncyfr0:
I cant boot. Im running Miui with KF1 bootloaders. I run the I897 package and the param.lfs is installed but when it reboots its always going to recovery and not booting into Miui. Its supposed to go to recovery one more time after flashing but mine keeps going into recovery. Ive tried at least five times now and still same.

Is there something else i need to do?
[Captivate Android Development] studacris:
this is for the I9000 gb bootloaders. for kf1 boots use the package for I897 bootscreen replacement http://xdaforums.com/showthread.php?t=944353
[Captivate Android Development] goderaj:
First off thank YOU very much for this!

I have followed these directions to the Tee and it won't work for me. It pushes my logo file to the sd card but not into the lfs folder.

I am running a stock Gingerbread. After I ran Odin it deleted the Logo_ATNT.jpg from the lfs folder and created a lfs folder which I cannot enter inside the original lfs folder. My animation has not changed of course. What am I doing wrong?

Also...is there a way to figure out exactly which bootloader I am running...figured I'd ask that here since I am posting?
[Captivate Android Development] goderaj:
Update: I finally was able to move the Logo_ATNT.jpg to the lfs folder using File expert. It shows up in File expert as the image I want, yet in Dual File manager it shows up as the AT&T image I am trying to replace. Now, when I restart my phone the image I want to use as my boot image shows up first, then comes the AT&T image I want to be gone. Any explanations?
[Captivate Android Development] geokilla:
Does this work with Captivate bootloaders?
[Captivate Android Development] studacris:
No, use the old package for the froyo boots...
[Captivate Android Development] metalfangs:
yudodis

I'm having the same issue as a few others, however some other weird things as well. Like a few others, after running the batch script and rebooting I was still left with the jumbled screen. After reading the thread I went ahead and loaded odin up again flashed the params and manually moved the logo.jpg to the lfs folder with file expert and rebooted, (root explorer fc's) yet I still get a jumbled screen! :( Any idea what the issue here is? I'm currently running Apex 9.2 with DarkCore kernel using the Gingerbread boot fix package from the OP and one of the provided images.

Edit: Tried again with another image and same result.
[Captivate Android Development] studacris:
What bootloaders?

If you have at&t boots the logo is called logo_ATNT which would be why it doesn't work...so if that is the case read my post above yours, otherwise I've never has an issue.
[Captivate Android Development] metalfangs:
Ah yes that must have been the issue then. I will give it another go later on and post results thanks for the info.

Edit: Manually edited the batch for the logo_ATNT.jpg and everything worked. Thanks again.
[Captivate Android Development] TRusselo:
POST 4 updated for clairity!

sorry it took so long!

http://xdaforums.com/showthread.php?p=13519860#post13519860
[Captivate Android Development] jonnyg1097:
So its the same video to follow just different files to download?
[Captivate Android Development] TRusselo:
yes. same process.

READ THE READ ME FILES~

i9000 bootloaders final jpg is called logo.jpg

i897 bootloaders final jpg is called logo_ATNT.jpg

always read the read me files!

have fun!
[Captivate Android Development] t3chn0s1s:
I'm assuming you mean I897 -- you keep saying I987 and the readme says I987.

Edit: Guess you meant the Tab. My bad.
[Captivate Android Development] fuloplori:
Thx guys, worked great on KF1 :) Thought I'd share some pics that I've used

Cheers
[Captivate Android Development] IDoMy0wnRacing:
Thanks for sharing, looks great.
[Captivate Android Development] geokilla:
It's i896/897, not i987 ;)
[Captivate Android Development] t3chn0s1s:
I kinda thought so but wasn't sure if he meant the Galaxy Tab.

Sent from an Apex powered SGH-I897
[Captivate Android Development] turbosocks:
mega props for this!!! worked so great on my Epic 4G.

figured id share my custom screen also..

i can do the same screen with any color glow and without my 'dark droid designs' tag, remove the gun and match arm to the regular android arm, etc. ( i made a 3D model of the droid)
[Captivate Android Development] IDoMy0wnRacing:
Nice work
[Captivate Android Development] TRusselo:
Post 4 updated with i896 Rogers Gingerbread bootloader fix.!by me~
[Captivate Android Development] nickm50:
Tried this tonight. Worked perfectly!
[Captivate Android Development] anishz:
I am on uckk4 stock deodexed and all. I followed all instructions but now i get the custom image followed by at&t screen and then the bootanimation. i am using the samurai kernel, is this at&t screen the kernel image or what?
[Captivate Android Development] TRusselo:
yes the second image is the kernel screen. that is in the kernel. we need source to modify that.
[Captivate Android Development] 4-2ndtwin:
Just wanted to report that I had success with this using a .jpg that is 320 KB in size. The Read me had suggested under 100 KB, but mine worked fine. Just sayin...And thanks again for this.

.
[Captivate Android Development] TRusselo:
good to know. thanks.
[Captivate Android Development] GGGETTER:
guy hi and thanks for the info,i'm a newbie doing different thing to the phone growing every day.this what i'm getting when trying to install the boot screen.....

i read the read me and follow the step can someone tell me what i'm doing wrong...thanks

model # SGH I897

2.3.3

I9000TUBJV6

KERNAL 2.6.35.7-I9000TUBJV6-CL264642

thanks for any help.....
[Captivate Android Development] RichMD:
Did you flash the param.lfs that does not include the logo file? It looks like you didn't which is why it is saying the file exists.
[Captivate Android Development] GGGETTER:
RichMD thanks for your reply,i just did it using root explorer.......:)

yes that was the first thing i did...

i9000_gb_param_LFS with O but it didn't work for me
[Captivate Android Development] RichMD:
Does "I just did it using root explorer..." mean you copied/moved the desired logo to that directory so you are all set? I remember successfully copying a logo file via root explorer one time (on froyo I think) after the "empty" param.lfs had been flashed.
[Captivate Android Development] TRusselo:
Yes. Note: capitals matter
[Captivate Android Development] GGGETTER:
yes i copy/paste it there......
[Captivate Android Development] J0ESK0:
nevermind.. looks like i have to rename it logo_ATNT.jpg was using the wrong guide.
[Captivate Android Development] Graysonh:
Just tried the i896 package on my cappy on KK4. No dice.. garbled screen here.

Anyone have or did have the same issue?
[Captivate Android Development] TRusselo:
Read the instructions on post 4. it depends which boot loaders you have not what phone you have
[Captivate Android Development] Graysonh:
Sorry I forgot to mention I had already tried the i897 ones and got the same result.

Any other ideas? Thanks for the reply!
[Captivate Android Development] J0ESK0:
This really should be in the OP. Would have saved me a lot of time today had I seen this 4th post which has links for the Captivate in the Captivate section.. instead of having the default OP being for the I9000. Just a suggestion ;) Also, it of course needs to reflect I897 instead of the typo I987.. but now I'm just getting greedy heh.
[Captivate Android Development] TRusselo:
this is why people will say to read the whole thread.... or at least the first few pages, to make sure there were no problems... or more info...

Some authors use the first 4 or 5 posts as their "first post" for a thread.

also some authors dont update their threads. others take over later and cant edit...typo fixed.
[Captivate Android Development] J0ESK0:
No you're absolutely right.. it's just I had to pick today, the blackout day, to try doing this, and I only followed and downloaded what was in the OP the night before. So I couldn't really do anything until XDA came back up way later in the day to research where I went wrong. Thanks again though, much appreciated for the simple and easy guides you two! :D
[Captivate Android Development] TRusselo:
s'all good.
[Captivate Android Development] disellusional:
on glitch/miui and have tried JPU and KF1 packages but everytime i reboot back into recovery and i can't get into the phone mode

any suggestions?
[Captivate Android Development] TRusselo:
It's a problem with flashing once in a while, not the boot image itself. I had this problem (booting to recovery) when flashing ice cream sandwich last month... I had to flashback to stock a few times to boot into phone mode again
[Captivate Android Development] Limitz Cash:
I got it working!! I used a custom image I created in photoshop it was 47.7KB. I did all the steps that was posted, but when i rebooted there was still a pix-elated screen. So I ran Wifi file explorer pro and uploaded my logo.ATNT.jpg image file to mnt/.lfs/ then rebooted. And there it was, my custom boot logo.

Thanks allot guys!!!
[Captivate Android Development] dualmoon:
Ah, cool stuff. Now for someone to get this working on ICS and we'll be good to go.

Because some boys can be really immature and want to brag about the self-proclaimed largeness of their penises.
[Captivate Android Development] TRusselo:
ics devs dont see much point to putting in the work to add a mount point for the params.lfs partition just so this mod is possible.... i kinda dont blame them but it may be a really easy fix... or not.. they didnt look into it. AOSP guys that is...

nandroid backup ICS in CWM, odin flash to gingerbread. do mod. flash ICS and restore nandroid in CWM.

i had to do this too. use the flashing guide in my signature to quickly get back to ICS.
[Captivate Android Development] netpok:
I tried this with the uckf1 rom but the files in the OP wasn't compatible with it (reboot to recovery didn't worked and sometimes i got forced upload mode), so I created a param.lfs tar for it
[Captivate Android Development] TRusselo:
read post 4 it has to do with bootloaders not rom
[Captivate Android Development] planetdroid33:
Can someone please post the file because for some reason i keep getting unsuccessful downloads.

Edit. Sorry forgot to say i am on kk4 gingerbread at&t

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] myshinynewtouch:
OP or anyone, I tried the method as suggested in the readme file, and I do get a garbled screen first and then once again get the ATT screen. Are there two files that need to be changed ?

I followed the steps exactly and didnt see any errors during Odin or the bat file run.

Is this extra step now necessary as posted by one of the previous posters above 'So I ran Wifi file explorer pro and uploaded my logo.ATNT.jpg image file to mnt/.lfs/ then rebooted'

as it seems to make sense as there might be a logo.JPG file and another logo.ATNT.jpg file which explains why i see the garbled image first and att logo image next.

Can anyone please help me, have a att captivate i897 on legend v4 with corn kernel 6.0.3
[Captivate Android Development] netpok:
I didn't touched the bootloader (I'm using the 3FileKF1NOBOOT pack with the first TalonDEV kernel) and since i used the the modded param.lfs from uckf1 i never had any of those problem

the file name is logo_ATNT.jpg not logo.ATNT.jpg

the second ATNT logo is in the kernel if you flash a custom kernel it will replace it
[Captivate Android Development] TRusselo:
logo.jpg for i9000 bootloaders

logo_atnt for captivate bootloaders...

READ POST 4. if you don't read the instructions of course it won't work. It has worked for hundreds if not thousands of people. Posted well over a year ago
[Captivate Android Development] myshinynewtouch:
Oops sorry OP, was following the readme in the download, will try it out tonight..
[Captivate Android Development] planetdroid33:
Am i getting this failed download because i am on phone. I've tried it many times.

Sent from my SAMSUNG-SGH-I897

Edit....

Please disregard, was my own error that down load was failing.
[Captivate Android Development] bobo122:
partially worked for me?!

first of all , i didn't have rubbish screen for some reason (it stayed at&t) , didn't matter which param i flashed .. then i said i'll try the bat file anyway .. the result was that when i turn the cellphone on , i get my custom screen , and then it changes to at&t screen ..

i was on ics, went back to 2.3.5 (using odin one click) , then tried flashing the param files , none of them removed the at&t screen, then i rooted, tried flashing again , didn't remove it too , then i ran the bat file .. any suggestions? (i'm going back to ics for now, till i get an answer)

thanks anyway

EDIT: just changed the kernel to corn kernel so i can go back to ics and restore my nandroid, and the at&t screen got replaced with corn's screen .. i guess the stock kernel had the same logo as well..

EDIT2: alright, been on ics for some time now .. it worked :D thanks a lot
[Captivate Android Development] tidy:
Dose this work for JB ???
[Captivate Android Development] Kyuta Syuko:
The folder with the jpg doesn't get created/mounted in JB. You'll have to go back to stock and do it on stock and it'll stick when you flash JB. At least that was my experience.
[Captivate Android Development] TRusselo:
That's how I had to do it too
[Captivate Android Development] Bejda:
Wow,i didn't noticed the thread being active lately!

Could you check this guys please?

http://xdaforums.com/showthread.php?t=2214468

I have no idea where that param.lfs (original is the google one) that works directly under i9000 aosp comes from..
[Captivate Android Development] Kyuta Syuko:
I'm not sure what you're asking about. The param.lfs is in the stock rom tar package.
[Captivate Android Development] Bejda:
Sorry for imprecision,I know where to find param.lfs in a stock rom but such stock ginger param.lfs just like the "blanked" one from here doesn't work on ICS/JB (your ICS/JB running device will just get softbricked with only download mode available and even if it was ok you wouldn't be able to touch mnt/.lfs on aosp based ROM,know that too..).

On my thread I'm using as base a param.lfs with Google logo we once had in a ICS rom thread that works directly on ICS/JB, you just flash it auto-reboot ticked and that's it,your device boot fine with new logo.

I did nothing special,just found my way to edit that google param.lfs to replace its logo but it suffers from limitations (google logo is only 13ko when you extract it and new logo that will replace it can't exceed that, it's a little frustrating in terms of artistic will lol).

I'm not sure that Google param.lfs is a ginger one made compatible with aosp, that's why i'm saying "where comes from".

I tend to think it could come from another similar device that had stock samsung ics upgrade but i have no real idea actually.. I searched a little on Gnex or Nexus s side but didn't find nothing, i still wonder where (or how is made/edited) that param.lfs that works directly on ICS/JB i9000 rom (and should work the same on Captivate i guess).

Anyway,depsite the logo size limitation it still nice to be able to change our bootsplash logo in 2 minutes with no need to get back to ginger,i hope some will be interested by here and could help to know more :)
[Captivate Android Development] They Drew First Blood:
RE: for JB ROMs

Coming from JB 4.2.x:

(0. Create a Nandroid backup / verify you have an existing Nandroid backup.)

1. Odin back to stock KK4 with no bootloaders: http://xdaforums.com/showpost.php?p=18370912&postcount=3

2. Odin the Corn kernel 7.06 KK4: http://xdaforums.com/showpost.php?p=18233847&postcount=1 (load in PDA slot)

3. Within the Corn CwM recovery menus, install SuperUser and BusyBox to root the phone

4. Boot to OS and make sure SuperUser went in, and that debugging is enabled (should be by default)

5. Download applicable package from this (current) thread Post #4: http://xdaforums.com/showpost.php?p=13519860&postcount=4

(I am on i9000 bootloaders so I needed the MobileTechVideos_GB_Boot_i897_t959_i9000.zip file)

5. Unzip and follow instructions in the "!Read Me.txt" file in the zip folder: replace the logo.jpg image in the zip folder with one of your own, and "i9000_gb_boot_screen.bat" pushes it into the .lfs folder for you. Reboot and custom logo is now the boot screen!

6. Flash CM10.1 nightly to get back to JB partitioning, then Restore the proper Nandroid backup of your JB ROM.

7. Reboot a final time and check out your custom logo again!

Thanks everyone :highfive:
[Captivate Android Development] Bejda:
Sorry but I just would like to know if this:

http://xdaforums.com/showthread.php?t=2214468

(A param.lfs that works directly on i9000 running ICS/JB ROM)

...would work on captivate as well.

I thought that it should but i know nothing about captivate and now I'm wondering about captivate devices running different bootloaders,some with i9000 ones while others running different bootloaders?

Or maybe I'm just missing something obvious from the start and it's nothing new/interesting by here?

It's just that I have compatibility questions from captivate users and I can't clearly answer unless someone test it or at least gives me more infos.