Hi all,
First:This is not kernel splash image nor bootanim,it's the first screen you see when you power on your device.
Here's a few modded param.lfs .tar to be flashed using Odin (at least they're in .tar made for and tested with Odin,i guess Heimdall users just have to take the param.lfs in it[EDIT:Confirmed here by Kasper-h itself]) on any I9000 aosp rom (ICS/JB tested).
PDA auto-reboot ticked and that's it,depending on the param.lfs you choosed you will boot with:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Black and white HEX edit method logo's:
Semaphore param.lfs .tar
Devil param.lfs .tar
Mackay param.lfs .tar
Fishears param.lfs .tar
Google param.lfs .tar
CyanogenMod param.lfs .tar
Samsung param.lfs .tar
BugDroid param.lfs .tar
Android param.lfs .tar
Bricked param.lfs .tar
Apple param.lfs .tar
Infamous param.lfs .tar
SexyNogen param.lfs .tar
GearKernel param.lfs .tar
HEX edit special requests:
AirChkoon param.lfs .tar
MarcouHotBunny param.lfs .tar
NezysJuve param.lfs .tar
SalzheldIsNotAfraidInTheDark param.lfs .tar
SadEff param.lfs .tar
ColinB63 IronMaiden param.lfs .tar
Haxxan7 param.lfs .tar
Gingerbread method Dump(how-to in 2nd post below):
i9000 param.lfs .tar
LiverpoolFC param.lfs .tar
Philman param.lfs .tar
All images are available alone as well in their respective zip.
Credits goes to:
DemonWav : [REF] Param.lfs / SBL.bin Image Locations [HEX]
Anarkia1976
sUsH667
Connexion2005 : [MOD] Custom Boot Screen *SGS II I777*
TRusselo : [MOD] Custom Boot Screen (for Gingerbread ROM's)
Ivan_Belarus : Your own logo.img in param.lfs
Contributions!
COMPACITY's BootSplash Collection
Member's name above is a link to his initial post so you know where to give your thanks View attachment 2022479BootSplash1BootSplash2BootSplash3BootSplash4BootSplash5BootSplash6BootSplash7BootSplash8BootSplash9BootSplash10BootSplash11BootSplash12BootSplash13BootSplash14BootSplash15BootSplash16BootSplash17BootSplash18BootSplash19
GINGERBREAD METHOD + DUMP TO GET A DIRECTLY FLASHABLE COLORED LOGO:
Rename your 480x800<100ko image (not sure maybe bigger's works,I heard that but a test with 177ko image didn't worked for me) as logo.jpg and copy it to /sdcard.
Flash a Samsung ginger rom (for me JVU).
Flash a kernel to get root (which one is up to you as long as it fits with the stock ginger firmware you just flashed,a matching CF-Root or Semaphore for instance but if semaphore don't forget to take superuser on market.
Tick usb debug in phone settings (somewhere under applications>development if i remember well) and set screen off delay to 10 minutes to be sure (adb loose connection when screen is off).
Go to download mode and flash that "empty" param.lfs .tar with Odin (or the param.lfs in it if using Heimdall):
https://dl.dropboxusercontent.com/u/25071013/i9000_gb_param_LFS.tar
That comes from here:http://forum.xda-developers.com/showthread.php?t=1065743
Device will reboot to recovery,choose reboot system.You may see download mode logo but it will boot fine.
Once device is running you plug USB (don't activate mass storage) , open command and type "adb devices" first to be sure adb see your device and then:
Code:
adb shell su -c "mount -o remount,rw /dev/block/stl6 /mnt/.lfs"
<enter>
Code:
adb shell su -c "busybox cp -r /mnt/sdcard/logo.jpg /mnt/.lfs/logo.jpg"
<enter>
Reboot device to check,if all went well you may see you have now two logo,the new one that appears fast followed by the samsung one...it sucks but when you'll get back to your CM10.1 or whatever aosp rom it will be ok and stay like this until you flash a stock samsung ginger rom again
If you have to use terminal emulator commands will be a little different:
Code:
su
<enter>
(allow root)
Code:
mount -o remount,rw /dev/block/stl6 /mnt/.lfs
<enter>
Code:
busybox cp -r /mnt/sdcard/logo.jpg /mnt/.lfs/logo.jpg
That's it you can now go back,if you came to ginger just for this, to your aosp rom but before that what about saving this new logo in a param.lfs file you'll be able to flash directly on top of aosp rom?
Open terminal emulator and type:
Code:
su
<enter>
Code:
dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096
You'll get a 1.25mb param.lfs file that can be flashed directly on aosp i9000 rom.
Use the param.lfs as it is if using Heimdall or .tar it for Odin (I use iZarc to get working Odin .tar on windows).
That's how it is: A param.lfs extracted from a stock Sammy ginger firmware can't be flashed on aosp (softbrick, only download mode available); but a dump of a stock ginger mnt/.lfs partition saved as param.lfs yes.
What you can get this way:
First a dump of the original i9000 logo:
Or something more shiny like this:
Download links in first post above.
Enjoy and share your products please
same (explanations,precisions,how-to...we'll see).
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
Well done buddy!!!! Very nice finding!
Envoyé depuis mon GT-I9000 avec Tapatalk
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
I hope you're ready for "some" requests .
Nicely done my friend.
Sent from my GT-I9000 using Tapatalk 2
---------- Post added at 12:23 PM ---------- Previous post was at 12:08 PM ----------
Dear Bedja can I have one boot splash logo only saying Samsung, like semaphore one. Please!
Sent from my GT-I9000 using Tapatalk 2
albertobom said:
I hope you're ready for "some" requests .
Nicely done my friend.
Sent from my GT-I9000 using Tapatalk 2
-----I'll -- Post added at 12:23 PM ---------- Previous post was at 12:08 PM ----------
Dear Bedja can I have one boot splash logo only saying Samsung, like semaphore one. Please!
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Thank you
Should be possible if you give me any image where "Samsung" appears the way you want it,I'm not very skilled with graphics you know i just learned recently to grab,cut,edit some images but create a logo from scratch would be very difficult for me.
Anyway,I'll check asap something for you but let's wait a little for further precisions on that whole param.lfs and bootsplash matter.As soon as time will allows me (mostly during the night in Europa) I'll try to explain the whole story.
There's two method for changing bootsplash logo actually, one is "known" and involve going back to stock Samsung ginger to do it but allows more elaborated images.
We'll talk about this too
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
Bejda said:
Thank you
Should be possible if you give me any image where "Samsung" appears the way you want it,I'm not very skilled with graphics you know i just learned recently to grab,cut,edit some images but create a logo from scratch would be very difficult for me.
Anyway,I'll check asap something for you but let's wait a little for further precisions on that whole param.lfs and bootsplash matter.As soon as time will allows me (mostly during the night in Europa) I'll try to explain the whole story.
There's two method for changing bootsplash logo actually, one is "known" and involve going back to stock Samsung ginger to do it but allows more elaborated images.
We'll talk about this too
Click to expand...
Click to collapse
There's no rush, take your time.
I'm not skilled too but I'll try to find our make a good one.
You're my Easter bunny friend.
Sent from my GT-I9000 using Tapatalk 2
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
Only the Galaxy S logo will be fine too.
Sent from my GT-I9000 using Tapatalk 2
Thanks Bedja, nice idea! Have been looking into this myself, but never ventured into it. Will give it a try soon
Can it also be heimdall flashed?
kasper_h said:
Thanks Bedja, nice idea! Have been looking into this myself, but never ventured into it. Will give it a try soon
Can it also be heimdall flashed?
Click to expand...
Click to collapse
For those windows-free people, heimdall can also be used!
-extract the .tar so you have a param.lfs file. Move this to your home folder
-open new terminal window
-do "heimdall flash --param param.lfs"
-phone will auto-reboot
-tada, you are done!
requesting google bootsplash...something like this...would be better...(screenshot below)
kasper_h said:
Thanks Bedja, nice idea! Have been looking into this myself, but never ventured into it. Will give it a try soon
Can it also be heimdall flashed?
Click to expand...
Click to collapse
I'd like to know about this, I never used Heimdall for now and thought that if the .tar'd param.lfs is ok for Odin the param.lfs itself would be ok through Heimdall?
I'll give all references I found about this,how I managed to edit one on windows but main point to know is that stock Samsung ginger param.lfs (or the "empty" one from ginger method) will softbrick an aosp running i9000,a real softbrick/dead like device with only download mode available and so only way to get out of it is flash a stock ginger rom or one of that modded param.lfs.
The difference is I used as base a param.lfs with Google logo that were on anarkia1976 AnarkyRom thread on i9000 dev section and was working directly under aosp.
I only found the HEX edit way and some rules behind but i still don't even know where that param.lfs come from.I asked Anarkia1976 and he answered me gently but about kernel splash i didn't bothered him again since then.
There's many unknown zones for me about this all and one of the goal of this thread will be to gather knowledge.As for me i've gone as far as i could/wanted but there's many things i'd like to know...it's kinda like an old i9000 mystery (the only device where it's that difficult to deal with splashscreen?).
The ginger method is just about pushing a logo.jpg to mnt/.lfs but things are different under aosp.
Would you have any idea about where that param.lfs that works directly on i9000 aosp rom could come from?
I don't think it's a i9000 ginger one made compatible,i thought about some similar device like gnex or nexus s but didn't find nothing.
Here's the original Google logo param.lfs:
http://db.tt/UrxXEDp7
roshan2989 said:
requesting google bootsplash...something like this...would be better...(screenshot below)
View attachment 1847975
Click to expand...
Click to collapse
See my post above
Bejda said:
See my post above
Click to expand...
Click to collapse
just flash the the google bootflash via odin(pda) would be ok...
Edit:Thanks its working fine... thanks for the google bootsplash...
finally...
hey mate!
finally a thread about this, hehe.
thx that you did it!
greetz,
sUsH
ps: you know how to reach me if you want/need.
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
Can this be used on art variant of sgs,i897?
Sent from my SGH-I897 using Tapatalk 2
Google original one and three others added to OP
+ bricked
Thunder22 said:
Can this be used on art variant of sgs,i897?
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Not sure,only hint i have is the gingerbread method (link in second post) where you can see that ON GINGERBREAD the same "empty" param.lfs can be used for both devices.
So maybe it's ok,i guess it should but can't say for sure...be prepared to reflash a stock rom if **** happens.. or try the ginger way,it's pretty cool as you can push any 480x800 logo.jpg < 100ko.
Re: [MOD][DEVICE BOOTSPLASH LOGO] kernel tribute edition
Thanks for including my logo Bejda. Truly nice work. I'll be flashing it as soon as I get to my pc
Sent from my GT-I9000 using Tapatalk 2
Related
Hi guys,
I picked up an I9100 SGS II the other day and decided to extend my development of the SGS boot screen MOD to it and was able to port it the same day as not much as changed in the way the param.lfs operates. I know this works just fine on the EURO I9100 SGS II in which the param.lfs calls for logo.jpg but if it fails, you can always re-flash a stock param.lfs to restore the boot screen which I have also included. I have written this for (I897, I9000, T959, T959V and now I9100). Per XDA's rules, I'll just attach the RAR package as an upload at the bottom of this post.
If you appreciate my work, just tap THANKS or DONATE me a drink or two if you are feeling generous. Here is the read me in case you don't want to open it with an additional text editor:
Code:
Brought to you by MOBILETECHVIDEOS.COM and CONNEXION2005 of XDA-Developers.COM
If the instructions below don't make sense to you,
JUST DON'T DO IT!
To change logo again, repeat the whole process!
=========================================================
| Instructions |
| ------------ |
| 1. Open Odin |
| 2. Boot Phone into Download Mode |
| 3. In Odin PDA select "SGS2_custom_param_lfs.tar" |
| 4. Click Start |
| 5. Boot Phone Normally and reconnect USB (dont mount) |
| You will have a logo draw fail! DONT WORRY! |
| 6. Rename the Picture you want to use to " logo.jpg " |
| 7. Run "MobileTV_SGS2_BootScreen.bat" from PC, follow |
| instructions. Keep phone screen ON, allow SU request. |
| 8. Reboot and Enjoy! |
=========================================================
NOTE about custom images!
480 x 800 and UNDER 100 kB
REMEMBER, THIS SCRIPT INSTALLS THE LATEST BUSYBOX INSTALLER, THIS MEANS IF YOU DIDN'T HAVE BUSYBOX INSTALLED, YOU MUST OPEN THAT INSTALLER AND ACTUALLY INSTALL BUSYBOX. IT INSTALLS AN APK TO USE TO INSTALL BUSYBOX, IT DOES NOT ACTUALLY INSTALL BUSYBOX ITSELF DURING THE SCRIPT.
ONLY USE THE LATEST BUSYBOX BY STERICSON TO ENSURE THIS WORKS BEST. IF YOU DON'T WANT TO USE THE SCRIPT FOR THE LATEST VERSION, BE SURE TO DOWNLOAD THE LATEST FREE INSTALLER OR DONATE VERSION IN THE MARKET BY STERICSON.
If the script doesn't work for you, it should if you have ADB installed, a rooted device plus the latest BusyBox (no offense but it's user error otherwise) just use root explorer to paste your logo.jpg in /mnt/.lfs AFTER running the custom param file via ODIN.
good job there mate !
does i9100 replacement logo.jpg also need to be less then 20kb?
also any other way to get out of soft crash except a jig(I dont have one)
and last request can you please also attach the original sgs2 boot screen plz?
thnx in advance..great work u r doing here bro..
THANKs
I followed all the steps , but without sucsess
I'm in Villain rom ... does it work with me ?
abumhmmd1 said:
THANKs
I followed all the steps , but without sucsess
I'm in Villain rom ... does it work with me ?
Click to expand...
Click to collapse
Does the script complete? Be sure logo.jpg is spelled in all lower case and make sure you don't accidentally have it named to logo.jpg.jpg
sumeshd said:
does i9100 replacement logo.jpg also need to be less then 20kb?
also any other way to get out of soft crash except a jig(I dont have one)
and last request can you please also attach the original sgs2 boot screen plz?
thnx in advance..great work u r doing here bro..
Click to expand...
Click to collapse
I've tested with files above 100k but recommend 100k or less. I'm not sure if the SGS II has the same issues with download mode in soft brick scenarios which require a jig. It doesn't hurt to have one just in case. To get the original screen back, simply flash the param.lfs from a regular i9100 ODIN package for your phone...
Works well here, I've now got a starfield picture as my bootscreen.
Nice one. No issues at all other than the script complaining about the fact that busybox was already installed.
If the .jpg is corrupt or too big etc. will the boot fail, or will I just get the little green "logo.jpg load failed" message that I saw during the initial boot?
Cheers!
Ok had time to create the actual SGS II video and added it to the OP...
Hi Josh....like your presentation style on your vids (though I'm glad there's a rewind facilty on vids to replay what I've missed that you've just said...very rapid fire, but get most of what you're saying, lol)
Before I go'n flash a new boot animation ( I was always changing it on my last Desire...) Is there a way (or a need) to back up the existing Sammy one, or will it get re-written when flashing back to the custom ROM/FW should I need to send my phone back for warranty purposes?? (BTW....what's the latest with the 'hidden' binary counter that the jig isn't supposed to reset??...any more been discovered about it?)
I made a small donation for ya too btw....(1UE79898RF509935C) good work, and thanks for all your help for us 'numpties' who rely on you clever dudes
Cheers...
Works great thanks
Thanks a lot, worked like charm!
I took a starfield picture I found somewhere and stuck the swirly S with the "Galaxy II" text on it so it looks semi-official, although the quality isn't as high as the real thing would be
I like it though, so here you are.
Looks like being in the "Yellow triangle" state over-rides the custom picture as I mis-flashed a zimage and it went away, flashed back to original & then CWM and all is well again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Worked for me - thanks.
I put my name, email address and home phone number on the screen. That way if it gets stolen it's fixed on the screen at startup.
As knightnz said, yellow triangle will override your image but it comes back if you get rid of the yellow triangle (i.e. proper kernel or samsung jig)
Stock param.lfs to flash through Odin
Worked for me,,thanks!
I created my own bootscreen with a Metallica logo and some text,, haha
Anyway, I've attached a stock param.lfs file(a tar file that is) to flash through Odin in case you want to return to the stock bootscreen...I've tested it and it works.
I thought, I'll share it with you guys to save you some time...
Grtz Dhanesh
How about getting Skyraider boot animation working on SGS-2?
Hi Josh, really appreciate the work you are doing there, making learn this all so easily with the help of all those videos and written instructions. I have a further question: -
Is it possible to get Skyraider boot animation work on my SGS-2 instead of stock boot animation "S"?? And also if 'Yes', then is there anyway to save the stock boot animation just in case if want to revert back to it?
Thanks
Update:
Got it done already, thanks to BMWpokerAce. Anybody interested go to:
http://forum.xda-developers.com/showthread.php?t=1150281
Hi, Thank you for the awesome video!
Even though the instructions are very clear, i still seem to have some trouble replace my bootscreen.
After running the SGS2_Custom_param_lfs.tar file in Odin (w/o any errors) i dont get the "logo.jpg draw failed" message that appears in your video, and i still got the same bootscreen as before.
Iam using [CF-Root v4.0] KE2/7/8, KF1/2/3/4 - su+bb+CWM4 with stock rom.
Thank you in advance!
RejjvarN said:
Hi, Thank you for the awesome video!
Even though the instructions are very clear, i still seem to have some trouble replace my bootscreen.
After running the SGS2_Custom_param_lfs.tar file in Odin (w/o any errors) i dont get the "logo.jpg draw failed" message that appears in your video, and i still got the same bootscreen as before.
Iam using [CF-Root v4.0] KE2/7/8, KF1/2/3/4 - su+bb+CWM4 with stock rom.
Thank you in advance!
Click to expand...
Click to collapse
Me too...
I experience the same problem...
May you've got a solution for this?
I'm running the Lite'nin Rom 1.5... (simply flashed with ODIN, no changes made... (kernel, busybox, ...))
Thanks a lot... =)
To both of you guys ^, I'd bet you have a variant of the SGS II that doesn't call the logo.jpg file and instead is calling some other file in the param.lfs. There are several logo files in that directory so my thoughts are that your variant calls for a different picture other than just logo.jpg. Especially if the script does not error out.
Thanks, you were right... =)
In my case the file is called logo_tel.jpg...
Now I'd need a SGS2_custom_param_lfs.tar, which "deletes" this file... (Or did you rename it?)
Is it possible for you to create one? Or could you explain how to do it myself? (I would love to know more about it... )
Thanks for your answer... =)
EDIT:
I just built a JIG for my galaxy s2, cause I thought I'd may need it some time... And when I tried if it works, I realized, that not only the phone boots into download-mode and resets the Custom Binary counter, but it also sets the source for the boot-logo to default... (in my case from logo_tel.jpg to logo.jpg)
So now I was able to change the bootlogo with your SGS2_custom_param_lfs.tar!
Maybe it also works for others... try it out... there's nothing to loose...
Havent had time to check if its the same scenario for me. But i´ll guess if your right, it prolly easier to create/buy a JIG then get a custom .tar file.. Thank you for sharing the information!
LichtiMC said:
Thanks, you were right... =)
In my case the file is called logo_tel.jpg...
Now I'd need a SGS2_custom_param_lfs.tar, which "deletes" this file... (Or did you rename it?)
Is it possible for you to create one? Or could you explain how to do it myself? (I would love to know more about it... )
Thanks for your answer... =)
EDIT:
I just built a JIG for my galaxy s2, cause I thought I'd may need it some time... And when I tried if it works, I realized, that not only the phone boots into download-mode and resets the Custom Binary counter, but it also sets the source for the boot-logo to default... (in my case from logo_tel.jpg to logo.jpg)
So now I was able to change the bootlogo with your SGS2_custom_param_lfs.tar!
Maybe it also works for others... try it out... there's nothing to loose...
Click to expand...
Click to collapse
dsixda's Android Kitchen - Now for Samsung Galaxy SII GT-I9100
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S2 custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
For the benefit of other readers and to prevent confusion, please stay on topic and only discuss Samsung Galaxy S2 in this thread!
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. The kitchen has been designed almost exclusively for HTC devices, although many people have had success using it with other manufacturers' ROMs. Recently I bought a Samsung Galaxy S2, and of course, I wanted to take control and create my own custom ROMs. However, ROMs for this device are totally different from those that I had worked on before, and so I decided to take on the project of supporting this device in the Android Kitchen. So, as of version 0.175, you can now create your own ROMs with the kitchen.
First, I'd like to thank pulser_g2 of Villain ROM for voluntarily helping me during his vacation to get started on this SGS2 project. Secondly, a big thanks to Noonski for testing and providing feedback.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
IMPORTANT: For this guide to work, you need one of the original Exynos-based Galaxy S2 variants, including the Galaxy Note GT-N7000. Unfortunately this means there is no support for the I9100G, since it uses a different chipset. For the Qualcomm-based AT&T Skyrocket, T-Mobile SGH-T989, Telus Galaxy S2 X (SGH-T989D) and other variants, please follow this thread instead.
First, you need a rooted Samsung Galaxy S2 with a ClockworkMod custom recovery.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT: To verify your variant of the Galaxy S2 works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.img, cache.img, zImage, hidden.img (if it exists), and modem.bin (optional)
TAR file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
TAR.MD5 file - Same as above but must be renamed *without* the MD5 part in the file name
ZIP file containing factoryfs.img, cache.img, zImage (and optional modem.bin)
Custom ROM:
ZIP file created by the kitchen from the stock firmware (other ROMs such as CyanogenMod may use a different file structure that is incompatible with the kitchen!)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
system.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a stock factoryfs.img but then didn't include the cache.img, then you have the option to add a cache.img later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
If your working folder currently has the stock kernel (zImage), you should replace it with the CF-Root kernel (or any other custom rooted kernel) which must match the stock ROM's Android OS version. Just replace the stock zImage with this zImage any time before you build the ROM. Otherwise, if you keep the stock kernel you will lose access to ClockWorkMod recovery!
OR, you can create a ROM without a zImage and thus keep the existing kernel on your device, although you must ensure the kernel is compatible with the ROM!
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM (Not required if you are using the CF-ROOT zImage)
Add Busybox (Not required if you are using the CF-ROOT zImage)
Disable boot sounds (if you find the Samsung starting sound a bit annoying)
In the Advanced options menu: De-odex your ROM
If you have trouble deodexing the leaked 4.0.3 ROMs, read this post for help.
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
Direct your questions to this thread, please do not PM me for tech support. Most of all, have patience, take your time and enjoy!!
USEFUL LINKS
Chainfire's CF-Root download thread
Infratech's official firmware thread
jazzor's guide for unpacking *.img in Linux
sicopat's guide for creating a ROM in Windows
mistadman's script for unpacking the initramfs (ramdisk) from the zImage
RyanZA's discussion thread on unpacking and re-packing the initramfs
Reserved...
Reserved For something Fun.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All the hiccups I had where because I was to anxious to read.
For Real Newbs setting up Sygwin on Windows is harder then baking the rom, I enjoyed myself thanks for that and thanks for your hours of work on this project since the beginning it already gave me great hours with my desire.
Enough with the ass kissing
Preserved...
Thankyou!...many thanks bro...nice job!
sure i will try...
Big thanks man
wow....welcome dsixda......finally
thanks for your hard work man!!!
Wonderful news, I always wanted to learn some cooking and you have made my life simpler by showing me the way. thanks a lot man
Cooking time
Hi guys, I have updated the kitchen to version 0.176, with a few changes related to the SGS2. Please see the release notes in post #2 of the kitchen thread.
Does this mean I still need to replace the update binary?
Noonski said:
Does this mean I still need to replace the update binary?
Click to expand...
Click to collapse
The correct update-binary was already in 0.175, no need to replace it. In the release notes the mounting stuff is in reference to the sysro script which had the wrong mount points in earlier kitchens.
I've now uploaded version 0.177 of the kitchen, which takes care of a few issues that came up while adding the SGS2 updates to the kitchen. Please visit the main kitchen thread to download the latest version. Release Notes are found in Post #2 of that thread.
Enjoy
I used xxkh3 stock firmware removed all bloat ware removed all crap I didn't Ned as ringtones and wallpapers. Added my own ringtones/wallpapers/transition effect and jkay themes . Removed ugly yellow triangle in boot logo added my personal logo and made a ugly dock for the launcher..
I used about one hour .
I've been using this kitchen since I got my N1 and it's the best ROM kitchen no discussion..
thanks Dsixda.
been waiting
Thank you Dsixda!
You made us chef!
Hope the restaurant goes on
By the way, to verify your Samsung Galaxy S2 variant works with the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2_variants/ folder then just create a file there with same name.
dsixda said:
By the way, to verify your Samsung Galaxy S2 variant works with the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2_variants/ folder then just create a file there with same name.
Click to expand...
Click to collapse
Hi dsixda,
Thanks to see here. i was used your ROM for HTC ELFin..
I am very happy ..
Now i have created a ROM for SG II, Where i will remove/add application in this kitchen.
Thanks this worked perfectly
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I cant bellieve how hard it was to find any info on this topic
I was working on my rom and wanted to change the secondary splash screen image.
I searched around, asked devs and had no success finding a step by step tutorial on how to do this.
Finally after much research I did it! so here i bring you my experience.
Click to expand...
Click to collapse
Boot order
1. To modify/change the first boot image go here:
http://forum.xda-developers.com/showthread.php?t=895089
2. To modify/change the bootanimation go here for some examples:
http://forum.xda-developers.com/showthread.php?t=1129705
Click to expand...
Click to collapse
First we need to establish where this splash image is located,
the image file is called logo.rle and is located here:
(i used 7-zip to view but don't use it to modify)
This is the file we need to change/modify, you can extract it with 7-zip.
Now we need to be able to convert this logo.rle to .png and back to a logo.rle
To do this go here:http://forum.xda-developers.com/showthread.php?t=1140406
Code:
1.run command promt
a.browse to folder with those bat files
-type:cd \users\you\desktop(if located on desktop)
-copy logo.rle to this folder
b.to conver rle to png type: Convert_rle_to_image.bat logo.rle
c.to convert back to rle type: Convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
If you have your logo.rle ready now we need to replace the one that came in your initrd.gz
this is harder than i thought, because initrd.gz is a image file it cant be modified with 7-zip
first you will need to be running linux (im running ubuntu on a virtual machine)
once you get linux create a new folder on the desktop called "temp" copy
the initrd.gz to this folder, open applications/accesories/terminal
and browse to the temp folder with the initrd.gz file(mine is "cd /home/isidro/Desktop/temp)
now type
Code:
gunzip -c ./initrd.gz | cpio -i
now in the temp directory you have unpacked initrd.gz. Replace logo.rle then when you're done still in the temp directory type:
Code:
find ./ | cpio -H newc -o | gzip > ./initrd.gz
this will replace the initrd.gz with the modified logo.rle
Click to expand...
Click to collapse
Now just Copy/Replace the modified initrd.gz to your Rom's boot folder and Test!
This worked for me on the HD2 but I would assume it works on any android Rom. Keep in mind this is the best way I could do it, if you know of a better way please share.
nice compilation...thanks bro
nice work bro
really
but I hope there i some easier way to do it
cuz this involves linux and virtual machines and I dont think many of us have this
Been looking for this for a while now, thank you very much !
very clear! i search for this a long time
THX bro
nice to see some dev sharing their knowledge ...thanks bro
If anybody cant get this to work at all!!!
send me your initrd.gz and your new image and ill give it a go.
thanks for taking so much time for making this excellent article. thanks added.
Excellent tutorial!! Very time consuming process for changing just one image but definitely easy when given step by step instructions.
Thank you for all your hard work and effort!
Ok, please tell me what am I doing wrong- I want to replace the logo.rle from one initrd.gz to another initrd.gz
I extract both with gunzip -c ./initrd.gz | cpio -i into their own separate folders
I copy the logo.rle I want over the logo.rle I want to replace
I do find ./ | cpio -H newc -o | gzip > ./initrd.gz after ensuring the old initrd is not there in the folder
I flash it on my phone, and it wont boot - if I flash same the initrd.gz without replacing the logo.rle, all is fine. I have tried this so many times
works perfect
10x
works nice. thanks.
you know what's nicer?
removing the logo.rle completely.
and what's even nicer than that?
finding the way to do it to clk boot.img
(how to patch it's initrd.gz or kernel)
then what you get is the First Boot Screen (HSPL) and then boot animation directly.
I can find a way to unpack the boot.img and repack it successfully.
If you find this out, that would be great.
Should be possible to do on linux, but I get a corrupted boot.img every time i try.
Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.
ellisbodds said:
Is there any way of changing this after the ROM is installed? Unfortunately the ROM I use requires that you flash a kernel .zip after installing it, which then resets the second splash screen.
Click to expand...
Click to collapse
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it
There is guide for change it use Window OS:
http://forum.xda-developers.com/showthread.php?t=1140406
isidromxz said:
open the update_kernel.zip with 7zip
replace the initrd.gz with the one with the new image, now just flash
the kernel and that's it
Click to expand...
Click to collapse
Unfortunately though, that doesn't seem to work. It's got a boot.img, so I had to extract that first in Linux, then I replaced logo.rle and recompiled boot.img. I then replaced the old boot.img in the kernel zip file and attempted to flash it, and I can't remember what happened. Either I got a message about update-script being deprecated and was told that installation was aborted, it flashed fine but didn't work, or it stopped my phone working.
tl;dr: I've spent far too long trying to figure out that one little image and in the end decided to just change the first splash screen to match the second one that flashes with the kernel.
Sent from my HTC HD2
I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem
BoBaN75 said:
I've follow all your staff and when I repack the initrd.gz with ubuntu I get this message error ( in french the message error so I try to translate) : cpio : the file ./initrd.gz is bigger, 163840 new bytes does not have been copied
That is the problem
Click to expand...
Click to collapse
Yeah I know it says it's not copied but it is just test the initrd after that
I found a guide to do it on window.
I will check and post here if I can find it on my Laptop
Sent from my GT-I9100 using xda premium
I Have tried it and it didn't work. When I tried to flash my phone via clk via rebuild rom installion aborted. Can explain how to put back the moded file on the phone
Sent from my HTC HD2 using xda premium
here is the guide
http://forum.xda-developers.com/showpost.php?p=24747881&postcount=4
thakz irfanbagus for the guide
where's the package link?have you try this guide by yourself?
i hope he tried
got a ubuntu, i will try this one (cross-fingers)
it's not working. sgy stock kernel do not have /proc/config.gz and gcc version in arm-2011.03 not compatible with other precompiled module.
this is work for me
requirement :
1. linux box 32 bit with working gcc. you can use real linux machine or virtual machine
2. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/ (Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)
3. mkbootimg with md5support. got it from http://forum.xda-developers.com/showpost.php?p=22224170&postcount=241 . credit to harish2704
4. split_bootimg.pl (google it)
5. kernel source from http://opensource.samsung.com . i use GT-S5360_GB_Opensource_Update2.zip
6. stock boot.img (or from your custom kernel).
step :
1. make folder "sgy" in your home. the result is folder "/home/<yourname>/sgy". <yourname> is your linux user name, and from now replace <yourname> with your user name. put all file you already download there
2. extract "GT-S5360_Kernel.tar.gz" from "GT-S5360_GB_Opensource_Update2.zip". put also in "sgy" folder
3. open terminal emulator and go to your working path with command
Code:
cd ~/sgy
4. extract your compiler with
Code:
tar -xvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
5. create folder "kernel" and extract kernel source there
Code:
mkdir kernel
cd kernel
tar -xvf ../GT-S5360_Kernel.tar.gz
you got 2 folder, "common" and "modules"
6. open folder "common", there is file "Makefile". open with text editor and find line with content "/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-". replace with "/home/<yourname>/sgy/arm-2009q3/bin/arm-none-eabi-", don't forget replace <yourname>.
7. in terminal goto folder "common" and load default config for sgy
Code:
cd ~/sgy/kernel/common
make bcm21553_totoro_05_defconfig
8. if you want change you config run
Code:
make menuconfig
9. if you ready to build then run
Code:
make
or if you have dual core cpu and want to make it faster
Code:
make -j3
10. when complete and no error appear, copy your kernel to "sgy" folder
Code:
cp arch/arm/boot/zImage ~/sgy
11. extract ramdisk from your boot.img
Code:
cd ~/sgy/
perl split_bootimg.pl boot.img
you got "boot.img-kernel" and "boot.img-ramdisk.gz". move "boot.img" and "boot.img-kernel" to other place.
12. repack your new kernel and ramdisk. but first get md5sum of your new kernel
Code:
md5sum zImage
you got something like
Code:
1fd319aa60abc2abae2e5932bcb9fc77 zImage
you need that "1fd319aa60abc2abae2e5932bcb9fc77" write it or copy to text editor. you need run it every time compile new kernel
13. repack
Code:
chmod +x mkbootimg
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 <your md5sum result> -o boot.img
14. make odin flash-able
Code:
tar -cf boot-sgy.tar boot.img
I thought you have to put your post into a new thread irfan...this one is a fake guide.
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
kurotsugi said:
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
Click to expand...
Click to collapse
His thread was closed by moderator.You can request MOD to reopen his thread.Motafoca wanted a galacy y to be lended for his experiments
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
Can someone download the sources around 15Gigs and stripe down the file and share it to Maroc ?
Whre can i download it?
Sent from my GT-S5360 using xda premium
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
i don't call it fake. it's just too general and missing some detail (but critical) for our device. and in the 'spirit of operation iron fist', i think it's better to put here
premolikeshtc said:
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
Click to expand...
Click to collapse
with my internet connection, it will take weeks just to download the source. and i think cm, like android source, use repo. so you can't just download it. you clone it from their source repository, that mean no download accelerator.
btw beside kernel source, samsung also release their mod to android source. but to build it, you still need to get android source (about 10GB according their website).
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
kurotsugi said:
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
Click to expand...
Click to collapse
if you (or others) think it's better to put in other thread, or maybe op wanna edit his post, fell free to copy my post (or just link, it's up to you). i don't take any credit to that post, because it just recompilation from other thread.
GT-B5510
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Rui Oliveira 21 said:
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Click to expand...
Click to collapse
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
sgy.creed said:
Hi guys,
This guide teaches how to make a new kernel for your device, it works in most of the cases but doesnt mean it will work for everyone
You need a minimal linux experice to know WTF you are doing
If you have any questions, post Belloowww
Download the required files
You will need a linux machine with the basic development tools or a virtualbox machine running a linux distribution (ubuntu 64bits will do fine)
I use the codesourcery package
Download the IA32 GNU/Linux TAR
The tar package is the easier to install
You will also need your kernel source from your manufacturer, for samsung the sources are available here
Install the cross compiler
Enter the folder were you downloaded the package and extract it, you will get something like arm-2011.03
Move that folder to some location, i use opt
ex: mv arm-2011.03 /opt/
or
sudo mv arm-2011.03 /opt
Done!
Extract and prepare the kernel sources
I will use the samsung sources as example, but anything can be used
For the samsung sources, after you extract the zip, you will get something like DEVICE_Platform.tar and DEVICE_Kernel.tar.gz
Extract the kernel:
tar zxvf DEVICE_Kernel.tar.gz
Enter the kernel folder and list the folder contents
ls
The structure is something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most devices contain the config file inside the device
You can extract it like this:
adb shell
su
cp /proc/config.gz /sdcard/
exit
exit
adb pull /sdcard/config.gz
Good, now we have the sources, compiler and configuration
Compiling the kernel
To compile ther kernel, i usually clean the sources first, with this i know for sure nothing will go wrong (usually )
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- distclean (Remember to replace acordingly the compiler folder)
Sources cleaned, time to load the config file
gunzip config.gz
cp config ./.config
Good, now lets check the menuconfig (menuconfig is a menu to choose the kernel options, created to make it easy to select)
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- menuconfig
Change whatever you want and exit and save
good, now its time to build
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- -j2
Now wait for it to finish!
Your compiled kernel will be located inside arch/arm/boot/zImage
Extracting a boot.img
Good, now we have the zImage, but WTF to do with it?
Well, android usually (some samsung devices use a different boot.img method, ex: I9000) has the boot.img, inside of it we contain:
- ramdisk (required files to load the /system partition and continue the boot sequence)
- zImage (our kernel)
- pagesize
- base
- cmdline (some kernel paremetes used on boot)
To create your own boot.img, you need one from a nandroid backup that was made from CWM or AmonRA custom recoveries (there are other methods, but for those use the madteam forum )
The boot.img is located inside your /sdcard/clockworkmod/backup/somedate/boot.img
You will also need the unpackbootimg and mkbootimg binaries, i this link there is the 64 bit version (wont work on 32 bit linux)
create an empty folder, copy the downloaded file inside, enter it and do:
tar zxvf bootimgtools.tar.gz
chmod 755 *
now copy the boot.img you got from the backup
and extract the boot.img with:
./unpackbootimg -i boot.img
this will create the files as explained above
Creating the boot.img
Before making the boot.img, we need some information from the files extracted
cat boot.img-base ( save the output #1)
cat boot.img-pagesize (save the output , place the value inside the Hex Value of this site, and copy the decimal value and save it #2)
cat boot.img-cmdline (save the output #3)
Good, now copy the compiled kernel (zImage) inside the current folder and do:
mkbootimg –kernel zImage –ramdisk boot.img-ramdisk.gz –cmdline “(replace with output#3)” –base (replace withoutput #1) –pagesize (replace with output#2) -o /tmp/boot.img
Good, the boot.img is created!
Now test on your device!
If you dont know how to flash the boot.img, enter the madteam forum and request help (its too difficult to explain the flashing of boot.img if you dont know how to do it )
Take care!
<External link removed>
Click to expand...
Click to collapse
please credits motafoca madteam
GT-B5510
Harsh06 said:
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
Click to expand...
Click to collapse
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Rui Oliveira 21 said:
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Click to expand...
Click to collapse
I believe Doky already reply your post n willing to help u in others thread.Give doky some info about your current FW.U need 3 complete files n flash through Odin.Key in *#1234# with your dialer(u will see current info version) and PM doky about the info.He surely gonna help u.
Sorry OP off topic.
GT-B5510
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Kernel
How to change Kernel Version when build kernel ??
usually display 2.6.35.7 [email protected] #1
i wanna change [email protected] #1 so how the setting on linux or maybe what file??
Thanks b4
Rui Oliveira 21 said:
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Click to expand...
Click to collapse
I was just wondering if you went to the oldest possible firmware you could find and then proceeded to update from that. Sometimes the updates only contain necessary info and kind of rely on the previous installs.
Sent from my TF101 using Crashntalk 2
We have 3 major works here... So I gonna to make it seperated
-1st post is HOW TO EXTRACT kernel.img (boot.img)
-2nd post is HOW TO CONVERT PICTURE FILE to BOOT.RLE
-3rd post is HOW TO REPACK THE KERNEL PAKAGE into boot.img
Requiredment
-Window machine
-installed cygwin
-the full boot.img/kernel (some kernel won't work because there is no full pakage/ i mean we can't)
-bootimg.zip (tool for UNPACK and REPACK kernel)
-boot_screen_logo_creation_package.rar
Thank and Credit
i- Credit to DooMLoRD Recognized Developer over most of XPERIA devices for his own tool and tutor that I learned before
ii- Credit to jimbo77 Senior Member for his tutorial that I used and learned and tool for unpack and repack
ii- Don't forget to give them a thanks meter
=============================================================================
Here we go
1-This section I will show u how to unpack and repack the boot.img
just see from original thread by jimbo77 from here and download the UNPACK and REPACK tool by him HERE
this is a fast guide from me:-
1-extract the bootimg-tools.zip into new folder (name it 'boot' folder)
2-move it into cygwin directory (cygwin/boot)
3- move your fav kernel into same directory
4-run cygwin.bat
cd /boot
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5-Now, unpack your boot.img by running the following command:
./extractboot boot.img
Click to expand...
Click to collapse
If your output looks like this, then the extraction has worked correctly! Note that the Command Line string has also been read from the source file, this will be used later when you go to re-pack your file.
Your script folder should now look like this:
boot.img-kernel is the compiled kernel blob that was inside the source boot.img, if you want to replace the kernel with another compiled kernel image, you can replace this file with another one (but leave the file name the same)
boot.img-ramdisk.gz is the gzipped ramdisk image which has been split from the boot.img, you should leave this file alone.
The “out” folder contains the EXTRACTED ramdisk, and this is where you should make your changes to the ramdisk.
Important Note!
Remember, when editing files in the ramdisk through Windows, such as init.rc, Windows notepad will not format the files correctly, making them almost impossible to read, wheras Wordpad will LOOK like it is formatting the files correctly, if you save one of these files from the Wordpad application it will BREAK the file and it will no longer be able to be read correctly by Android. To edit these files you MUST use an editor such as Notepad++ which you can download for free.
AGAIN...
Special thanks/credit to jimbo77 for his excellent guide
So.. NEXT step to change a kernel logo is here
Requiredment
1-a picture what are u like to look into the 1st boot screen (kernel logo) (make sure it size/resolution same your device resolution)
2-boot_screen_logo_creation_package.rar
3-some infos and knowledges here
4-window machine like i explained on 1st post
My quick guide
-extract the tool.rar
-move extracted files into new folder (name it 'rle' folder without quote)
-move into cygwin folder (to make it easy to follow my simple guide)
-copy your own logo.png (a picture u want to use on a kernel) into same rle folder
(for 4 steps above it shold look like tis)
-now launch cygwin.bat
cd /rle
Click to expand...
Click to collapse
./convert_image_to_rle.bat logo.png
Click to expand...
Click to collapse
Ah...my mistake..don't forget to move/copy/replace new logo.rle into
C/cygwin/boot/out/ramdisk/here
if you done good...follow next step on next post (to repack your moded kernel)
Last step before you flash a new look kernel (boot.img) is
Repack your moded kernel
./packboot
Click to expand...
Click to collapse
One thing to note that people may mention in other guides, is that when packing boot.img files, you will usually have to declare a base address, and a command line to the packaging tool. This set of scripts reads the existing command line and base address from the boot.img file you originally provided at the time of repacking, so always make sure you leave your original source boot.img file in the folder and do not re-name it after extraction, your newly created boot.img file will be named boot_new.img and will NOT overwrite the original.
Done! If your screen looks like the image above, then you should now have a freshly created boot_new.img file, ready to be flashed to Android for testing, you can now go ahead and flash it through FASTBOOT one thing I'll recommend though is to first do
I need this for an extra (extra thanks..)
(may U?)
Thanks a lot man, i'm looking for it.
thanks a lot my friend
now i can make may own kernal boot animation:silly:
Thanks! Subscribed to this thread, will try my best to do this soon.
and how to extract kernel.elf? ^^
jimRnor said:
and how to extract kernel.elf? ^^
Click to expand...
Click to collapse
Actually that's the same question I have lol
I think i can't do it with bootloader locked?
Thanks!
Thank you so much!
Working very talented!
R: [Tut] How to change kernel logo (1st boot srceen) [COMPLETED]
If you are on a linux distro, you can use championswimmer's kitchen
Sent from my LT26i using xda app-developers app
how to change the boot logo of the acro s?
I can't find any boot.img file in the rom.ftf
all I can see is KERNEL.SIN
I can extract it.
but how to repack ?
I just want to change the boot logo in this acro s kernel with the new logo.rle that is attached with,
pleaaaaaseeee
help me
Anyone could help me ??
No reply?
prob here is how can i find boot.img for stock rom
thanks
How can I extract elf kernel....
Sent from my LT26ii using Tapatalk 2
Why it says:
Android Magic not found in ./boot.img ????
phil1405 said:
Why it says:
Android Magic not found in ./boot.img ????
Click to expand...
Click to collapse
are you extracting kernel.elf?
this tut was not working on kernel.elf, or maybe your cygwin got problem
No i tried with a boot.img :/
Currently I'm trying to install the perl and cpio packages...