Database Info

Changing Boot Screen animation

Here are 2 different way to get new BOOTANIMATION. Special thanx 2 ibussa & attn1 for helping me with this.
IF YOU ARE FLASHING NEW ROM AND WANT TO CHANGE ANIMATION WITH THE NEW FLASH
1. Open the ROM of your choose.zip
2. Navigate to System\Media and look for bootanimation.zip
3. Extract the original boot animation
4. Open it and delete the bootanimation.zip file, copy the new one of your choose or drag it the new one in.
5. Put Rom.zip on SD card.
6. Reboot into recovery.
7. Install zip and wait for it to finish.
IF YOU ALREADY HAVE ROM AND JUST CHANGING BOOT ANIMATION
1. Copy the NEW bootanimation.zip of your choice in SDK Folder
2. Open up CMD
3. cd C:\AndroidSDK\tools (or were ever you SDK files are)
4. adb remount
The filesystem is mounted read only. You need to mount it read/write.
5. adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
6. adb push bootanimation.zip /system/media/bootanimation.zip
7. adb push bootanimation.zip /data/local/bootanimation.zip
To return to read only,
8. adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
9. Reboot and there you go

I managed to get one on and working a few days ago. I don't remember/know what finally made it work, but I tried the adb push method.
But the thing is, I got curious and instead of moving it, I tried removing the old bootscreen before I tried to push the new on.
I'm not sure if that is what finally made it work though, so don't take my word for it. All I know is after I rebooted after the adb push, it worked.

Well this is how I did it. I delete the bootanimation in the rom zip file and then inject thw new bootanimation and reflash the rom.

ibussa said:
Well this is how I did it. I delete the bootanimation in the rom zip file and then inject thw new bootanimation and reflash the rom.
Click to expand...
Click to collapse
How did you extract and inject the new bootanimation? unzip and then re zipped? Oh and what ROM are you using it on?

No, I open the zip, navigate thru the file and extract the original boot animation, then open it and delete the animation file, copy the new one and drag it or inject the new one into the Rom zip and reflash it.
Sent from my HTC Liberty using XDA App

def changing my animation now!

ibussa said:
No, I open the zip, navigate thru the file and extract the original boot animation, then open it and delete the animation file, copy the new one and drag it or inject the new one into the Rom zip and reflash it.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Hmm... I have tried that and for some reason it wont let me extract delete or replace it..I will keep trying tho thank you
Edit: Scratch that I opened with WinRAR instead of zip and that allowed me to extract delete & replace it..Thnx Again

Try with the rooted Rom beta of att
Sent from my HTC Liberty using XDA App

What is the OP's boot animation? Where can I find some cool boot animations to try? I've seen some but not many that I really liked.

sfernandez said:
I am trying to change my boot screen animation to a new one and have tried multiple ways. Any help would be greatly appreciated. I have attached the file I am trying to install.
I placed the bootanimation on sd card & in C:AndroidSDK\tools
I have tried in recovery mode to install from zip on sd card and no luck
I have tried going thru OI file manager and deleting/renaming bootanimation.zip on system and no luck.
I have also tried to delete/move/copy bootanimation.zip threw Driod Explored and nothing
I have tried to remove the old bootanimation and no luck
adb shell rm/system/media/bootanimation.zip
adb shell rm/data/local/bootanimation.zip
I have even tried pushing and no luck
cd C:\AndroidSDK\tools
adb remount
adb mv( I tried with and without this command)
adb push bootanimation.zip /system/media/bootanimation.zip
adb push bootanimation.zip /data/local/bootanimation.zip
adb reboot
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The filesystem is mounted read only. You need to mount it read/write.
try
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
to return to read only,
adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system

attn1 said:
the filesystem is mounted read only. You need to mount it read/write.
Try
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
to return to read only,
adb shell mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
Click to expand...
Click to collapse
hell yeah that work :d thank you thank you thank you

Can't you just get a regedit and do it on the phone itself like on windows mobile?
I remember I changed my splash screen on my HTC Pure it only took like a second.

TheChemist187 said:
Can't you just get a regedit and do it on the phone itself like on windows mobile?
I remember I changed my splash screen on my HTC Pure it only took like a second.
Click to expand...
Click to collapse
Not to my knowledge. I know WM you were able to but yea, but not android. Ether way this is a very easy way 2 do it.

Wheres the best place to get boot screens?

SysAdmNj said:
Wheres the best place to get boot screens?
Click to expand...
Click to collapse
Check the g1 forum on xda and look for the boot animations thread.

Hi, I want to replace my bootscreen with this one.
I downloaded the zip files from the thread. I did what you said, but the only thing i saw when i rebootted was a black screen.

What format are the bootscreens in? I need video size, format, and length please. Also, If I do make one, do I just zip it? Thanks in advance.

Rubinski_be said:
Hi, I want to replace my bootscreen with this one.
I downloaded the zip files from the thread. I did what you said, but the only thing i saw when i rebootted was a black screen.
Click to expand...
Click to collapse
hocplyr98 said:
What format are the bootscreens in? I need video size, format, and length please. Also, If I do make one, do I just zip it? Thanks in advance.
Click to expand...
Click to collapse
Often the black screen is caused by either improper resolution or the desc.txt file having some incorrect verbiage or syntax. The issue may also be caused by zipping up the bootanimation.zip using compression. When zipping bootanimation.zip, it's a good practice to use no compression. You can try my bootanimiation.zip for formatting to see if it works. It was created specifically for the Aria. (This one is the stock looking HTC logo with the green android peeking out from behind the logo.)
http://forum.xda-developers.com/attachment.php?attachmentid=359230&d=1278999405

I'm using a HTC Tattoo, and i think that the resolution of the bootscreen was wrong. The bootscreen wasn't original for the Tattoo, so it had another resolution. I changed the *.gif-files to 240*320 (Tattoo's resolution). I made a new zip (without compression) and tried to push it. But the files who where allready in there are not replaced :s

Someone needs to come up with an animation of Android peeing on Apple logo, Calvin & Hobbes style.

[22/9] newSense DesireHD ROM(1.15) file for Desire phone, rooted|A2SD+|OJWake|OVPN

23/9/2010 12:00 I've been to the Chinese Mid-Autumn Festival. Who want flashable ROM zip file will be try:http://forum.xda-developers.com/showthread.php?t=742371 or http://forum.xda-developers.com/showthread.php?t=789830, thanks to NeoPhyTe.x360 and robocik!
fastboot video:http://www.youtube.com/watch?v=fipvwzuNyEE
download url:http://www.multiupload.com/AVHZ2WJ4M4
mirror url:http://vipme.com/ROM/desireHD/, thanks to zexbig.
This is NOT a flashable zip file.
It is a file collections for ROM Dev.
09-22 15:48 update patch:fix gps FC & vold issue & Youtube HD no video issue:http://www.megaupload.com/?d=7YJ6B7UR
flash it with ROM Manager or recovery menu.
Known issue:
1.camera can not work
2.Location,CarPanel FC sometimes.
Thanks all Dev from XDA! This file pack is based on DesireHD leaked RUU/Dump.
Requirement:
1.Desire Phone
2.custom recovery(AmonRA,ClockWork)
3.parted SDCARD with ext2/ext3, ext partition size not less than 512M.
4.radio version great than 32.42.00.32U_5.09.00.08
use it with follow step:
1.unzip the ownhere.DesireHD.zip
2.reboot your desire phone to recovery mode,for example:"adb-windows.exe reboot recovery"
3.wipe data,system,sd-ext
4.adb connect to phone, for example:"adb-windows.exe shell"
Code:
mkdir /sd-ext
mount /sd-ext
mount /system
mount /sdcard
5.push ownhere.desirehd.system.tgz,ownhere.desirehd.sd-ext.tgz,ownheredesire_v2.0_acekernel.zip to /sdcard
for example:
Code:
adb-windows.exe push ownhere.desirehd.system.tgz /sdcard/
6.adb connect to phone
Code:
cd /system
rm -r *
tar zxvf /sdcard/ownhere.desirehd.system.tgz
cd /sd-ext
rm -r *
tar zxvf /sdcard/ownhere.desirehd.sd-ext.tgz
sync
lost+found may be error, ignore it.
7.flash ownheredesire_v2.0_acekernel.zip with recovery menu.
8.reboot,the first boot time is long, about 5 mins.
you got it.
removed file:
Code:
Facebook
Twitter
teeter
Metal(skin)
Black(Skin)
Wood(Skin)
Flash
Maps
Quickoffice
all of these files can be found in Market or leaked RUU.
modified file:
Code:
Vending(Market)
/system/lib/hw/
/system/lib/egl/
build.prop
and some files i forgot...
all of these files can be restore from leaked RUU(But may be crash the system)
HOWTO extract file from DesireHD leak RUU 2.15:
run RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662.exe in Windows box.Then some dialog appear(which include a 'next' button), look for your windows' temp dir, search the newest dir created by RUU, then copy rom.zip(about 277M) to another dir(or RUU will delete it automaticly).
send this rom.zip to Linux box,
in Linux box, unzip rom.zip, then
Code:
mkdir system
mount -o loop,ro system.img system
all files in system dir. you can simply copy files from it.

Ouch
I was hopeing for a flashable ROM ....
Well thx a lot man, now devs will be able to develop some great HD ROM

Would love to, Except I'm not Brave Enough
Excellent Work, Well Done!
KYI

first!
WELL DONE
edit: wasn't fast enough damn

sweet dude

Wow ! Thanks !!! :d

Thanks for sharing

ash1684 said:
Ouch
I was hopeing for a flashable ROM ....
Well thx a lot man, now devs will be able to develop some great HD ROM
Click to expand...
Click to collapse
It's because he is using the Sdcard as an extended System ftom what i know at least

can someone report if it works before i try
and ownhere take your place amoungst the xda legends

LOL rapidshare is already going 150 secs for a dl... they are getting overtaxed i advise everyone to use Megaupload... only 30 sec wait

Trying this now!

any one installed this ?

apologies for having doubted about you!!!GREATE job!

How is it working?

great now I need to learn adb but thanks now I can laugh at my cousin with cs hd
2

can anyone report on whats working and whats not?

NickChaplin said:
can anyone report on whats working and whats not?
Click to expand...
Click to collapse
according to the op everything works apart from camera app, neo said he will look into fixing it tho

AndroHero said:
according to the op everything works apart from camera app, neo said he will look into fixing it tho
Click to expand...
Click to collapse
am i correct in assuming that this rom doesnt have root access?

please make flashable zip

NickChaplin said:
am i correct in assuming that this rom doesnt have root access?
Click to expand...
Click to collapse
op said it rooted with apps2sd

[HOW TO] Open CGs

Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?

There is a Perl script which can unpack boot and recovery (CG35 & CG47) in this thread: http://forum.xda-developers.com/showthread.php?t=443994

Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
CG64.smg & CG65.smg: partition tables that you can open using fdisk/sfdisk
CG33.smg is a CDROM ISO file!
iirc one or two of them are the splash image (not 100% sure now)

Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.

rachit2588 said:
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
Click to expand...
Click to collapse
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows

^very good idea

danimagrin said:
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
Click to expand...
Click to collapse
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??

rachit2588 said:
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
Click to expand...
Click to collapse
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.

danimagrin said:
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
Click to expand...
Click to collapse
with mkyaffs2image its jus showing me a cmd windows for some less thn 1 sec and its jus goes away...please upload the version you are using...also let me know if it needs any prerequisite software to be installed.

It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"

danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
oh , ok.. its working..thanks

danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
ok last doubt...after creating system.img can it be restored via custom recovery..??
how to add md5 check sums for that so that custom recovery can identify as proper nandorid..!!??

rachit2588 said:
oh , ok.. its working..thanks
Click to expand...
Click to collapse
You welcome!
Sure you can use it with nandroid, you must download md5sum.exe, place it together with mkyaffs2image, after you used mkyaffs2image then type "md5sum system.img" and it will generate checksum. Create a file called "nandroid.md5" and paste what md5sum returned. You can open a nandroid.md5 file of another backup and you'll understand better how it's done..

excellent..i got it

@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..

rachit2588 said:
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
Click to expand...
Click to collapse
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...

danimagrin said:
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
Click to expand...
Click to collapse
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker

rachit2588 said:
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
Click to expand...
Click to collapse
I'll test it as soon as I get home and then I tell you!

[GUIDE] How To Convert ODIN Tars to System.imgs for CWM (and vice versa)

This will probably get moved, but I do believe it is development related because it is important to everyone who flashes ROMs but can't use ODIN for whatever reason (ie Linux/Mac users).
Seeing all the ROM cookers get asked so much to make system.imgs or update.zips to cater to the Linux/Mac users, I decided it was time to tell people how to just convert an ODIN Tar.
I will tell people how to do it on Ubuntu seeing that is what I have (in a VM), but once I have the patience to install Mac OS in a VM, I shall make a guide for that.
Please note that if the factoryfs.rfs is in RFS format (ie it's a stock ROM or it's a ROM by someone who doesn't like EXT4 for whatever reason), you will not be able to do this. The format the factoryfs.rfs is in (EXT2, 4, JFS, whatever) needs to be supported by your Linux kernel. You can check that by doing cat /proc/filesystems
After a lot of investigating, I have learnt that RFS is a broken version of FAT. You could poke around with it and try mounting it as vfat but I don't guarantee success.
ODIN TAR -> System.img
Download your TAR and save it to your Desktop (I will use Kyorarom Ascendency Beta)
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
tar cvf system.img system
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Copy the system.img to your phone
System.img -> ODIN TAR
Download a TAR from another ROM, and the system.img to your desktop.
Open the TAR with Archive Manager (or whatever you use) and extract the factoryfs.rfs from it to your desktop. You don't need anything else
Open Terminal (under Applications > Accessories)
Go into superuser mode:
Code:
sudo -s
Make a mountpoint for the system:
Code:
mkdir /mnt/system
Mount the image
Code:
mount -o loop ~/Desktop/factoryfs.rfs /mnt/system
Change directory to /mnt and make the tarball for the system.img
Code:
cd /mnt
rm -rf system/*
tar xvf ~/Desktop/system.img
Unmount and clean up
Code:
umount /mnt/system
rm -rf /mnt/system
Put the factory.rfs into a TAR and flash it with ODIN.
Done! Hopefully this should all work nicely for everyone.

Nice One... Should be helpful for ROM Developers to provide system.img for their ROM's...

Nice one. Thanks. Though I don't use .imgs still was quite Informative.
Sent from my GT-I5800 using xda premium

Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez

cdesai said:
Nice tut, on windows they can use adb and dd/ mkyaffs2img
From my fingers to your eyez
Click to expand...
Click to collapse
Can u pls explain tht furthur.

vsoft11 said:
Can u pls explain tht furthur.
Click to expand...
Click to collapse
Pretty much do the same thing but from in ADB shell, and instead of the command:
Code:
sudo -s
with
Code:
su
and
Code:
tar cvf system.img system
gets changed to
Code:
tar cvf /sdcard/system.img system
Also I'm pretty sure on the phone, /dev/loop0 is called /dev/block/loop0.

I'll probably have to wait until you put up a mac tutorial..

harkan89 said:
I'll probably have to wait until you put up a mac tutorial..
Click to expand...
Click to collapse
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....

Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me

mankokoma said:
As MacOS is basically Unix you should be able to do the same with/on/in a mac when you open a Terminal/Console (forgot how it's called exactly)....
Click to expand...
Click to collapse
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..

TearsDontFalls said:
Wouldnt it be easier if you run this commands?
Code:
mount -o loop factoryfs.rfs ~/Desktop/system
tar cvf system.img system
the mount command mounted it succesfully for me
Click to expand...
Click to collapse
Because I am foolish. I shall improve the guide later today.
harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
I got my Mac VM working so I will use that and make a Mac guide.

hillbeast said:
I got my Mac VM working so I will use that and make a Mac guide.
Click to expand...
Click to collapse
Yaay! Finally!

harkan89 said:
Wait a sec.. I have to use adb for this? Cuz I tried the commands as mark mentioned but it didnt turn up any results.. I do recognize some of these commands, so probably it should run on the mac Terminal..
Click to expand...
Click to collapse
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!

is there also a way to convert system.img to tar files...

cdesai said:
You can use adb too (but these commands should work on a Mac too, as Mac | Linux -- UNIX (based on)
Or you can always use cwm!
Click to expand...
Click to collapse
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..

mohsin2cool said:
is there also a way to convert system.img to tar files...
Click to expand...
Click to collapse
Yes, I shall make a guide for that after Christmas.
harkan89 said:
I have superuser enabled on mac.. WHen I try the first command.. mkdir /mnt/system.. it says no such file or directory found.. and losetup is apparently not a command recognized by mac terminal..
Click to expand...
Click to collapse
Macs don't use a /mnt directory. They use /Volumes, just like how Ubuntu is moving over to /media.
And I don't think the mach kernel supports losetup type stuff. I will make a Mac guide after Christmas.

HI
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.

devc0ol said:
If u got the time, Can u pls make a tutorial video for this using adb. Would have bn very helpful.
Click to expand...
Click to collapse
Sure. I will do it in the coming days.

nice guide, but will it also work if you convert it with CWM recovery?

JasonPurungrit said:
nice guide, but will it also work if you convert it with CWM recovery?
Click to expand...
Click to collapse
What do you mean?

[EP4D/FP1H/FP5E][MOD][ODIN] Change Boot Splash Image

This is from a whole lot of brainstorming, reading, headaches & lack of sleep. I now understand Odin & Heimdall a whole lot better; & my skills with Samsung Android phones have increased a bit more. I hope that at least one person can benefit from having a modified param.lfs for a custom boot splash.
Let me know if there are any ways that I can improve this post.
Before you begin, this is for the fearless types that know what they're doing or go all out even if they're jumping into a tornado. Your phone may soft-brick if something goes wrong.
Modified Instructions (from kmalinich's thread):
Needed:
Rooted Samsung Droid Charge
Working ADB
Latest Odin3
Hacked param.lfs (attached & mirrored)
New jpeg boot logo size 480x800 (less than 64KB - test to see if larger works)
Steps:
Copy your new splash image (logo.jpg) to your sd card however you'd like.
Remove your SIM card for safe keeping until this process is finished
Start Odin
Enter download mode (reboot to it or disconnect the phone, take out the battery, press the volume down button, plugin the USB cable, wait for the download screen to appear & place the battery back in)
Extract param_mod.tar.md5 from droid_charge_param_mod.zip
Flash hacked param_mod.tar.md5 via Odin3 in the PDA area _*ONLY*_
Reboot into CWM recovery
Mount the system partition from within CWM
Open ADB shell
Enter these commands:
Code:
mount -o remount,rw /dev/block/stl7 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
Reboot and enjoy!
Notes:
I've tested multiple versions of Heimdall with just the modified param.lfs & it fails to upload 99 times out of 100. I recommend Odin3, SamsungPST Lite, or redbend_ua.
The boot splash image only appears for a short while since the Droid Charge kernels have splash images, too. If you'd like the same image for the duration of boot, utilize an app or a guide to change your favorite kernel's splash image.
Mirror:
modded param.lfs - http://db.tt/fjyx4uEf
sample boot splash - http://db.tt/Nj26hmb6
original param.lfs - http://db.tt/HcCZ6O0H
Sources:
Free Your Android - Modifying Samsung Splash Screens (Galaxy S Series + SGS2) <- how I learned to do it
[Mod][ec09] samsung boot splash/image change 7.7.11 - xda-developers <- how I learned about it with the Fascinate
Fixes & verification of FP5E by Tanno of DroidForums

Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!

Endless2232 said:
Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!
Click to expand...
Click to collapse
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.

CrimsonKnight13 said:
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.
Click to expand...
Click to collapse
Nope, not a complete idiot. =) haha. I will try again later and report back.

Endless2232 said:
Nope, not a complete idiot. =) haha. I will try again later and report back.
Click to expand...
Click to collapse
I was hoping for the best. I'll do what I can to help & correct any errors that jack phones up. :fingers-crossed:

This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!

substanceD said:
This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!
Click to expand...
Click to collapse
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753

CrimsonKnight13 said:
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753
Click to expand...
Click to collapse
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.

Works.
Sent from my SCH-I510 using xda premium

dwitherell said:
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.
Click to expand...
Click to collapse
Any community effort to make this into a smooth working mod is fine with me. I'll do more research myself tonight.
kvswim said:
Works.
Click to expand...
Click to collapse
Great to know.

I attempted to make a usable CWM zip but it fails with a line in the updater-script.
assert(package_extract_file("param.lfs", "/tmp/param.lfs"),write_raw_image("/tmp/param.lfs", "/dev/block/stl7"),delete("/tmp/param.lfs"));
Click to expand...
Click to collapse
It gives the error:
assert failed: write_raw_image("/tmp/param.lfs", "/dev/block/stl7")
<snip> (Status 7)
Click to expand...
Click to collapse
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.

CrimsonKnight13 said:
I attempted to make a usable CWM zip but it fails with a line in the updater-script.
It gives the error:
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.
Click to expand...
Click to collapse
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me

dwitherell said:
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me
Click to expand...
Click to collapse
I'm glad that the original method does work & that we both came to the same conclusion. Thanks for looking into it.
Is there a method to split the zImage, change the RLE, & rejoin it into a workable kernel? Making this thread into a boot & kernel splash image mod combo would be nice. I'm coming up empty handed with my searches through Google & XDA. Most modifications are for Sony phones.

Is step #7 something that can be done within the stock recovery or is that a separate ADB command?

nismology said:
Is step #7 something that can be done within the stock recovery or is that a separate ADB command?
Click to expand...
Click to collapse
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.

CrimsonKnight13 said:
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.
Click to expand...
Click to collapse
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:

nismology said:
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Click to expand...
Click to collapse
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
nismology said:
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:
Click to expand...
Click to collapse
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.

CrimsonKnight13 said:
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.
Click to expand...
Click to collapse
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.

And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.

nismology said:
And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.
Click to expand...
Click to collapse
As I said, it shouldn't be booting into stock recovery when the modded param.lfs is pushed. If you have already flashed a custom kernel, CWM recovery will stay. If you still have a stock kernel, stock recovery will constantly take over.
Additionally, whenever I did it, due to lack of logo.jpg, it would kick me straight into CWM. I'm unsure what your setup on your phone looks like though.
nismology said:
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.
Click to expand...
Click to collapse
Yes, mounting through CWM is the easiest way.