yashsingh1/xdaforums huggingface dataset:
[Streak 5 Q&A, Help & Troubleshooting] Techvir:
Two things i am looking forwarding in gingerbread

1. Better copy and paste fn

2. Gtalk video chat.
[Streak 5 Q&A, Help & Troubleshooting] fone_fanatic:
If dell plans to go ahead with the opus one then it would be a bad move on their part to upgrade the current steaks to gb. Because some people will overlook the new hardware changes and just upgrade their current devices and make due.

Sent from my Dell Streak XDA premium app - please excuse my miswyping ;)
[Captivate Android Development] connexion2005:
Well I had been getting asked a lot lately about the GB ROM's and my original boot screen packages that I had created where I modified a param.lfs to contain no boot image and allowed a script to place whatever image you wanted in it's place for a custom boot logo. In the past I had edited the param.lfs for the AT&T i897 bootloaders which does not work with the GB boot loaders.

This is not the boot animation, nor the kernel logo, but the first logo your phone displays when it's turned on.

Anyhow, I re-wrote the param.lfs to allow a blank for the logo.jpg that Gingerbread calls upon in the bootloader and it works great. So for all of you that used my boot screen package in the past for i897, i9000 and t959 2.1, 2.2 and 2.2.1 ROM's, here it is again for 2.3+ ROM's.

This should also work fine for Vibrant but I will check in case any T959 people are scoping this out.

These will not be compatible with CM7 (due to the proprietary fs used on param.lfs)...

Big thanks to TRusselo for being a BETA tester, tossing in the latest ODIN package and writing the readme as well as contributing the JPEG's offered in the package. I decided to keep the Canadian boot screens for you northern neighbors on the Roger's network up there... ;)

Donations are always welcome but not required, press THANKS, follow me on Twitter or like my cause on FaceBook.

Download the package below...

http://dl.dropbox.com/u/19201431/Files/MobileTechVideos_GB_Boot_i897_t959_i9000.zip
[Captivate Android Development] 4-2ndtwin:
^ Appreciate this....

and good to hear from ya again.
[Captivate Android Development] connexion2005:
No problem. I'm still really active, here on XDA. Just try to limit my content to my website since they monitor me very heavily... :)
[Captivate Android Development] TRusselo:
FROYO VIDEO!!

[YOUTUBE]RjRejS3gXaU[/YOUTUBE]

make sure to read the read me file!!!!

For i897 Froyo/ Ecliar /

Gingerbread bootloaders

http://download1073.mediafire.com/teuilo1p1h7g/n3l6527tvt7a4v5/MobileTechVideos_i897_Boot.rar

with images included : http://dl.dropbox.com/u/19201431/Files/i897_Froyo_Gingerbread%20boot%20fix.zip

note: jpg image called logo_ATNT.jpg (even for rogers) READ THE README!!!

For i9000

Gingerbread bootloaders running on captivate

http://dl.dropbox.com/u/19201431/Fil...t959_i9000.zipnote: jpg image called logo.jpg

FOR i896 ROGERS Gingerbread bootloaders

http://dl.dropbox.com/u/19201431/Files/i896_gb_boot_screen.zip

note : final image file called logo.JPG <captial JPG is IMPORTANT> and **not** ATNT like captivate version~!

READ THE README!!!

Here is the

GINGERBREAD

PICS that are included.

here are some more single images:
[Captivate Android Development] TRusselo:
see above...
[Captivate Android Development] kimchi0400:
Done, soft-bricked (Odin failed) but got back into DL mode and re-flashed. I've got the i896 logo up there now.

Thanks a lot!
[Captivate Android Development] TRusselo:
yeah odin sometimes does that... the newer odin does that LESS.. lol.

i soft bricked a few times using this.

just keep forcing the params until it passes, no need to go back to stock!

with GB button combos, and the soft brick, i found:

Vol Down + USB = Download mode

Vol Down + Pwr = Soft brick screen.

hope that helps.
[Captivate Android Development] impulser91:
Just an fyi to anyone not familiar with it, but you will have to make sure you have your screen active when running the batch file so that you can click Allow to the superuser permission request when it attempts to mount the partition.

This wasn't noted in the readme, someone without much experience might miss it.
[Captivate Android Development] jonnyg1097:
Just a question but why are there some screens with "AM HUNG" as the name and not Samsung?
[Captivate Android Development] jonnyg1097:
When you soft bricked and reflashed did you have to do the whole rom or just this process in particular?
[Captivate Android Development] TRusselo:
thanks i updated the readme in the dropbox link above.

man dropbox is amazing!
[Captivate Android Development] TRusselo:
read the post below that. please.

really? why? i need to explain?
[Captivate Android Development] TRusselo:
OP link updated.

1 new bootlogo added, instructions updated, 2 pictures fixed
[Captivate Android Development] TheEscapist:
OP, you should add that these will not be compatible with CM7 (due to the proprietary fs used on param.lfs).
[Captivate Android Development] TRusselo:
readme instructions updated. thank you

gotta love drop box!

im hosting the file and maintaining.
[Captivate Android Development] TRusselo:
tuesday morning bump!!!!!
[Captivate Android Development] jhr5474:
I

have adb installed and working for at least a year now. However, your program just tells me that adb is not recognized as a command. at the end it does say enjoy your new bootscreen and it gives me a screwed up bootscreen. Yes the file is only 96kb and yes I named it correctly. and yes I have usb debugging on and no the phone isn't mounted. I am using mosaic 1. Any ideas?
[Captivate Android Development] connexion2005:
Have you rebooted the PC? ADB is known to get stuck sometimes. Also retry the process but make sure to close all the adb.exe processes using task manager.
[Captivate Android Development] jhr5474:
OK I restarted the comp and made sure their were no adb processes running and still your tool does not work it says killing all adb processes and then says adb is not recognized as an internal command. I know adb works because I used cmd:adb devices and it showed my phone. So what is the deal with this program? I am on 7 but I used run as administrator so it should work.
[Captivate Android Development] connexion2005:
It's got to be something with your instance. I use this all the time with Windows 7 x64...
[Captivate Android Development] jhr5474:
So when I use the odin package on it it seems to get stuck. It says its done and then boots into recovery and then flashes back to digger with blue bar at the bottom and then back to recovery. No superuser request when i run the bat file either. I know su works i tested it also.
[Captivate Android Development] connexion2005:
From that description your not using it correctly. Flash the ODIN file then when it boots to recovery, select reboot now. When it's back in Android with your phone unlocked run the batch script and select allow on super user prompts.
[Captivate Android Development] connexion2005:
I just ran it again for fun and it works like a charm with a different boot logo. If the README is confusing you blame Trusselo! :)
[Captivate Android Development] jhr5474:
That is exactly what I did

1. reboot to download

2. flash odin

3. when recovery boots select reboot now

4. Run batch file

5. no su request and it says adb not recognized as an internal command and I can see my phone with adb so?

another funny thing is when I flash the odin file, right after that it makes the digger with a blue bar my first splash screen. It is like it is grabbing what is on the screen and making it my first splash?

DO you check repartition? I dont and that is what it does.
[Captivate Android Development] connexion2005:
After the param.lfs flash it will do that odd thing where the last seen screen will flash once or twice as there is no logo.jpg for the bootloader to reference as the param.lfs being flash is blank. Do you have root explorer? If so then just avoid the script and place the boot logo of your choice in /mnt/lfs and make sure it's name logo.jpg.

I'm not sure what's going on your machine not allowing ADB to run properly. Most likely your are having a driver conflict.
[Captivate Android Development] Graysonh:
I just followed the entire process to a T and I get a garbed screen on boot. I checked in the mnt/.lfs folder and the logo I chose is there with the name "logo".

My question is does it have to be named "logo.jpg" and then the file extension?

If not, can anyone offer some troubleshooting tips?

Thanks a ton.
[Captivate Android Development] neubauej:
Just "logo.jpg"

Try the whole process again. Ive done it 4 times now without any problems whatsoever.

Goodluck. :)
[Captivate Android Development] TRusselo:
what file explorer are you using?.

does it say .jpg for the other pictures in that folder? some file exploerers have the option to hide the extention, was it named logo.jpg before it was copied?

are you on Gingerbread bootloaders?***
[Captivate Android Development] Graysonh:
I'm on a GB rom. Serendipity to be exact.

Yes, it was named logo before copying. Just plain logo, then the file extension.

I don't know whats wrong! I tried it again and no dice :(
[Captivate Android Development] jhr5474:
yeah,

I tried the file thing also to no avail. I wish my first splash wasnt such a mess I guess I will just flash back to stock gb and reflash another rom. Thanks for the effort. I really dont understand why it wont work.
[Captivate Android Development] sinichi21:
is this working for gb rom jvh? just want to confirm
[Captivate Android Development] TRusselo:
@ sinichi21 this has nothing to do with rom.

boootloaders

@ other guys. - method 2

1. flash the params.lfs with odin. again.

2a. use a file explorer like root explorer to mount system RW then drop the " logo.jpg " in the folder " mnt/.lfs/ " then mount RO and reboot,

2b. or use SGS tools > apply script > mount system RW, then use a file explorer to drop file in " mnt/.lfs " then appy script > mount RO. and reboot.
[Captivate Android Development] TRusselo:
serendipity isnt gingerbread!!!

thats your problem! you dont have gingerbread bootloaders.

use the i9000 fix for froyo!

http://www.youtube.com/watch?v=RjRejS3gXaU
[Captivate Android Development] connexion2005:
Damn Trusselo! I'm gonna have to hire you as a thread admin / editor for my site! Your on the ball on these threads buddy!
[Captivate Android Development] geokilla:
Been trying to run the custom boot screen for the past 20 minutes and for some reason, the batch file is stuck at *daemon started successfully*. I used to use it on Froyo and it was fine so I'm not sure what's wrong....

Also I flashed the Param.lfs with Odin, and the bootup screen is now the page you see in Download mode. Is that right? In Froyo, it was just random pixels.

Edit: Turns out USB Debugging was disabled...
[Captivate Android Development] TRusselo:
gold star for you! debugging...

and the pixel screen will pixelate the last thing on the screen, usually download mode, but the %age of the pixelation is random, so sometimes it looks almost perfect of the last image. if you were to reboot again you would have seen a different boot image.. i experienced this while testing. no problem
[Captivate Android Development] neubauej:
I discovered this also. The first time i rebooted after flashing, i got a perfect download screen. Kinda surprised me!
[Captivate Android Development] Cezar`:
Great work here guys! :-)
[Captivate Android Development] stangri:
Thanks you guys, I've also fixed some minor misspellings in the readme and attached the modified file.
[Captivate Android Development] stangri:
Uhm, just tried it and I might need some help here.

First of all, Root Explorer crashes when I try to go into /mnt/.lfs now, which hasn't happened before I flashed the i9000_gb_param_LFS.tar from Odin (I could see all images there just fine before I flashed).

I've copied my preferred logo using adb tho and on start it does show up. However it's almost immediately replaced by the Galaxy S I9000 logo (I'm on Cezar's Continuum 5) followed by the C5 animated logo.

So where does the Galaxy S I9000 logo come from and how can I get rid of it?

PS. If anyone can point me to the stock galaxy animation in C5-compatible form I'd be much obliged.
[Captivate Android Development] neubauej:
The Galaxy S I9000 logo is the kernel splash screen. Not much you can do about that one unless you know how to compile your own kernel...

As for the stock galaxy bootanimation, go system/media and delete sanim.zip.

This will make the stock bootanimation reappear.
[Captivate Android Development] TRusselo:
yeah i got the FC issue too.

read the first post please

it explains the i9000 logo that you STILL see!

thanks. filed updated. you had an older version..
[Captivate Android Development] stangri:
Ah, I see. And I'm guessing kernel renders picture based on build.prop.

I've removed sanim.zip and now it's flashing android text, while I want the stock Galaxy S animation. Any clues which ROM I can rip it off?

thanks!
[Captivate Android Development] TRusselo:
no kernel renders something built in i beleive, many 2.2 kernels had custom images, onix did and i never seen that image hidden on the phone.. leads me to think its built in or can be built in. and right now it would point to the same i9000 image (which you customized!) so.. dont think so from logic... but i could be wrong. not a kernel dev... not a dev really...

and not off the top of my head at the moment...

try google.
[Captivate Android Development] neubauej:
Odd.

Here is the original.

Rename to sanim.zip for gb
[Captivate Android Development] stangri:
neubauej thanks, but I've tried renaming it to sanim.zip and putting it in /system/media and now the kernel logo changes to a black screen until I'm booted. Also, one of my archiving programs failed to extract from this zip-file, while the other one did work (it's just a bunch of PNG files in the folder, right) -- could that be corrupted zip-file?
[Captivate Android Development] Jay_eS_Iye:
Thought I'd share a couple logo's I made while making my own (the rest have my username, doubt anyone would want that)
[Captivate Android Development] Jirv311:
Those screens are nice. Good work. :)
[Captivate Android Development] Jay_eS_Iye:
I'm not totally savy on ADB commands, but I wanted to change the logo after I had already put one on. But when I run the batch file I get that logo.jpg already exists. I tried going into the .lfs folder via Root Explorer but it FC's whenever I do. So I assume I'll have to add a adb command in the batch file to delete the current logo.jpg but don't know how that would look esp with the busybox command in the line already. Any help would be great
[Captivate Android Development] TRusselo:
thanks i added your logos to the zip file!! thank you!!!

read the instructions again!

how does it say to change the logo again????

repeat ALL steps including the odin flash!

read instructions and read the posts above, you are not the only one with the FC issue. but it doesnt stop you from doing anything
[Captivate Android Development] neubauej:
Png files in a folder called part0 and a desc.txt

I dunno why its not working. I tried it here, and have been fiddling with it all day, including replacing the bootsamsung.qmg files, and it just isnt gonna work for me...

Im stumped. Worked just fine on froyo.

Sorry
[Captivate Android Development] TRusselo:
one of your pictures was undersize.. 478x799. i fixed it!

i did the same thing originally.

original files updated again in OP! thank you dropbox!
[Captivate Android Development] stangri:
Whew, at least it's not just me. Well, it's outside of scope of this thread, but still if anyone can point me to the stock (Sammy's) Galaxy S boot animation it would be much appreciated.
[Captivate Android Development] TRusselo:
guys if you want to further pursue this, find another thread or if there isnt one close enough, start a new one. it is getting off topic and could confuse people about

this threads LOGO,

where you are talking about the ANIMATION.

thanks
[Captivate Android Development] Jay_eS_Iye:
<face slap, follwed by hanging my head low in shame> yeah ok thanks. I was trying to save time by not reflashing i9000_gb_param_LFS.tar again (and obviously by only skimming the thread...)

That's really odd because according to Windows all of them are 480x800, but thanks for the fix
[Captivate Android Development] TRusselo:
no prob.. it happens.
[Captivate Android Development] TRusselo:
video added to page 1 for froyo version

only difference to gingerbread is the download file and you name to "logo.jpg" for gingerbread files.

"logo_atnt.jpg" for eclair/froyo
[Captivate Android Development] connexion2005:
That video SHOULD be allowed here but don't be surprised if it gets pulled.
[Captivate Android Development] TRusselo:
I posted the video on my own accord, i have no official affiliation with the author (you), and it does not make me money in any way.

it is no different than me posting

ANY link in the world

in which the site contained 1 or more ad(s) or banners, it incurs the same potential for any outside party to make money.

i post and help purely for the "thanks" not for money.
[Captivate Android Development] connexion2005:
I agree 100%. I'm just stating the way things have been handled in the past.
[Captivate Android Development] TRusselo:
i know... and its half my point.

there's a method to my madness. now i wait...
[Captivate Android Development] rquiett:
So I was really looking forward to giving this a go, but when I try to unzip the files I get error messages and the readme file is blank
[Captivate Android Development] kant5t1km3:
same, could someone tell me how to flash and what to flash sorry for the noob question.

EDIT: i tried to extract it and it say the fies are corrupt.
[Captivate Android Development] IRONMAN-NC:
The zip archive for the Gingerbread boot logo mod is definitely corrupt and needs to be uploaded again.
[Captivate Android Development] eliwu26:
Yep connexion, could you re-upload? The files are corrupt. Loved this on froyo, would love to try it on ginger.
[Captivate Android Development] TRusselo:
sorry about that all fixed! im hosting the file and keeping updated.
[Captivate Android Development] rquiett:
Thank you very much. I will give it another go when I get back home tomorrow and will make sure to also hit the thanks button then
[Captivate Android Development] superj3211:
i guess i should of read that this doesnt work with CM7........well this sucks....anyone have the CM7 param file i could flash so i dont have to reflash everything?
[Captivate Android Development] TRusselo:
use the files for froyo/eclair from post 2
[Captivate Android Development] superj3211:
i have tryied that....i cant even get that to work with stock rom

someone said to change the logo on stock rom then flash cm7 and it should work but it wont even work on stock from odin one click
[Captivate Android Development] topiratiko:
Lol. Odin included wont open. Starts to extract then dissapears. Use a diff version of odin weekly with no issues. Any ideas? The version i use is the one from installing talon kernel on continuum 5.5 says gt I9000p at top can i use it instead?

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] topiratiko:
So i got odin to open but when i select file shouldnt it show up next to pda slot? Mine stays blank. Hesitant to attempt flash

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] IDoMy0wnRacing:
Thanks connexion2005,

I saw this on Mobile Tech Video for froyo / eclair. I have been eagerly waiting for a GB version.

Thanks,

Keep up the great work... it IS appreciated.
[Captivate Android Development] Maltz:
I tried this on continuum v.5.6 and the boot screen ended completely black
[Captivate Android Development] jonnypinkeyes:
Will this work with the I897UCKF1 bootloaders?
[Captivate Android Development] Peaster111:
Hi

+ 1... Good question. Anyone try yet?
[Captivate Android Development] KayvinM:
Bumping this question since I'm also interested in knowing :D
[Captivate Android Development] connexion2005:
Alright you punks, I'll put a Captivate on the line here ;)...after all I can just JTAG it if I mess up right? LOL.
[Captivate Android Development] kimchi0400:
Sweet! I've been dying to flash the new kf1-based roms
[Captivate Android Development] KayvinM:
*clenching fists together in anticipation* :D
[Captivate Android Development] alrit:
I tried and got a real garbage boot screen, and then came still the AT&T logo.

So I think it's not ready for UCKF1 yet.:(
[Captivate Android Development] connexion2005:
Ok fellas,

The KF1 release still utilizes the param.lfs from an original Captivate containing the logo_atnt.jpg blank. I tested and verified it works beautifully with my i897 boot package for the KF1 official Captivate builds. Use this video and this link to my site for the correct package. Run the "froyo" batch script after flashing the param.lfs file. Trussello repackage this with an appropriate read-me if you have time as you are the man on keeping this thread up to date bud!

http://www.mobiletechvideos.com/blog/?page_id=197

http://www.youtube.com/watch?v=RjRejS3gXaU
[Captivate Android Development] connexion2005:
Try again but use the i897 package as this is a true Captivate build. It will work perfect. If you used the GB bootloader package which is based of the i9000 build's for KF1 then yes that will not work. It's all dependent on which file the param.lfs calls for (i.e. "logo_atnt.jpg, logo.jpg, logo_t959.jpg and so on)
[Captivate Android Development] zephyrcube:
I used the i897 package, screen shows up with custom boot screen, and then still followed by the AT&T logo boot screen.
[Captivate Android Development] 13_:
Just a heads up for peeps attempting this. This is as it went for me.... your mileage may vary...

On Serendipity7 Build2 , Talon2.2r2 BigMem

Flashed UCKF1 bootloaders ... successful

Flashed the param.lfs from above link (i897 Boot Screen Package) .. successful??

First I got some crazy usb upload modem screen... I lol'd, rebooted.

Rebooted from clockwork 2 times as it came up in a loop... then fully booted.

Used "Eclair" batch script to replace file. Negative.. tried again, Negative...

When it went to push the file it said file not found , sumthin sumthin... error.

Rebooted for the hell of it, crazy garbled screen.. kinda kool lookin though.

Used "Froyo" batch to push logo_ATNT.jpg... successful.

Reboot and boom my boot screen.

Also noted that from root explorer I can not even look at the files, it FC's on the folder. May have just been my device, but I post here so others who may run into this don't flip ;) ... if the eclair batch does not work, try the froyo batch, don't assume you just jacked up your phone.

Of course this is assuming no Odin errors or other problems. :rolleyes: Point is follow the instructions and maybe you has to run froyo batch.

Also, Thanks for being the guinea pig connexion2005, jtag is a powerful peace of mind tool. :D
[Captivate Android Development] zephyrcube:
I am running Cognition 5, Beta 2. I ran the i897 package and like 13_ I had to run the Froyo batch file, as the Eclair would not work. I got the same error.

So it worked, sorta. I do see the custom boot logo, but only for a second before the stock ATT logo still shows up, then I see the galaxy S boot animation.