THIS IS FOR ADVANCED/EXPERIENCED USERS ONLY
[ info ]
hello devs/users this should be a useful tool (its just a small CMD/batch script) for u guys...
so it will basically pack zImage and ramdisk into kernel.sin and then create an FTF which can be flashed via FlashTool...
[ requirements ]
windows
may be Java installed
[ supported devices ]
Xperia X10 ONLY
[ usage ]
place the compiled kernel zImage & compressed ramdisk (cpio.gz) in the same folder as these files
rename zImage to "image" (without quotes)
rename compressed ramdisk to "ramdisk" (without quotes)
edit the BUILD-IT.bat file and modify the following entries:
Code:
echo branding: DooMKernel-v06-BootManager-v1.4 >> manifest.mf
echo Created-By: DooMLoRD >> manifest.mf
echo version: 2.3.3 >> manifest.mf
ren kernel.jar X10_2.3.3_DooMKernel-v06-BootManager-v1.4.ftf
to whatever you want, as this is what will be displayed in FlashTool FTF window
once you are done editing that file save it
now double click on BUILD-IT.bat to launch kernel.sin & FTF build process
at end you will get a FTF which can be flashed via FlashTool
[ download link ]
kernel.sin and FTF creator v1.0
[ other useful links ]
[DEV][TOOL] kernel.sin unpacker
[How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
{
"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"
}
Enjoy!
DoomLord,
Very nice...
In theory this method work to all sin files (partition), right? I only need to have the partition attributes, right?
You know how to get the attributes for all partition?
adrianom said:
DoomLord,
Very nice...
In theory this method work to all sin files (partition), right? I only need to have the partition attributes, right?
You know how to get the attributes for all partition?
Click to expand...
Click to collapse
yes
check the_laser's thread for info related to partition table...
BUT DO SO AT UR OWN RISK
DooMLoRD said:
yes
check the_laser's thread for info related to partition table...
BUT DO SO AT UR OWN RISK
Click to expand...
Click to collapse
Thanks, I found.
adrianom said:
Thanks, I found.
Click to expand...
Click to collapse
but I can't found....
anyways... DooM does this compile the kernel? or does I just combine zimage + ramdisk?
thanks.
Sent from my X10i using xda premium
pheel said:
but I can't found....
anyways... DooM does this compile the kernel? or does I just combine zimage + ramdisk?
thanks.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Just combines zimage + ramdisk.
pheel said:
but I can't found....
anyways... DooM does this compile the kernel? or does I just combine zimage + ramdisk?
thanks.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1253277
How is the Bin2Elf and Bin2Sin different to mkbootimg? I ask because mkbootimg gives us some more options that we don't have with the tools by the_laser e.g. specifying the kernel commandline.
EDIT: Basically I want to learn more about the differences between boot.img and kernel.sin, I've crawled XDA for days but I don't think I can piece it all together. From what I understand boot.img is for fastboot/bootloader phones which the X10 isn't, though I am trying to figure out how to convert a boot.img to kernel.sin while retaining the command-line.
Boot.img seems to have only minor differences, the header starts with ANDROID and some other text such as the kernel command-line but I can't find any plain text in kernel.sin or loader.sin so I'm not sure where I can inject/remove some bytes to make the boot.img work with flashtool. Apart from the header the only other difference is random machine code two-thirds or so down, my guess is that's were the init.rd has been strapped on the end of the kernel.
Anyway, I tried flashing a boot.img in flashtool which I built based on the way custombootimg.mk does, but the flashtool freezes when it gets to kernel, I know that's probably silly but I hope there is some more material on the web or buried in XDA about the work you and the_laser have done that I could read up on.
jonusc said:
How is the Bin2Elf and Bin2Sin different to mkbootimg? I ask because mkbootimg gives us some more options that we don't have with the tools by the_laser e.g. specifying the kernel commandline.
EDIT: Basically I want to learn more about the differences between boot.img and kernel.sin, I've crawled XDA for days but I don't think I can piece it all together. From what I understand boot.img is for fastboot/bootloader phones which the X10 isn't, though I am trying to figure out how to convert a boot.img to kernel.sin while retaining the command-line.
Boot.img seems to have only minor differences, the header starts with ANDROID and some other text such as the kernel command-line but I can't find any plain text in kernel.sin or loader.sin so I'm not sure where I can inject/remove some bytes to make the boot.img work with flashtool. Apart from the header the only other difference is random machine code two-thirds or so down, my guess is that's were the init.rd has been strapped on the end of the kernel.
Anyway, I tried flashing a boot.img in flashtool which I built based on the way custombootimg.mk does, but the flashtool freezes when it gets to kernel, I know that's probably silly but I hope there is some more material on the web or buried in XDA about the work you and the_laser have done that I could read up on.
Click to expand...
Click to collapse
If u just want kernel command-line u can define it in defconfig whole compiling kernel...
Refer to the_laser's thread to get more info on SIN files...
Sent from my R800i using XDA App
i try change bootlog image..
it's work!! but not root...
DooMLoRD said:
If u just want kernel command-line u can define it in defconfig whole compiling kernel...
Click to expand...
Click to collapse
Yep, looks like I'll have to go that route. Would of been nice to specify MTD partitions without having to compile from source but oh well, it's a do-once kind of thing anyway. Thanks for the tip.
Thx...
It will be better if the tool support more devices like ARC/NEO/PEO etc.
DooMLoRD if you get chance could you test?
v0.1 of tool
DooMLoRD said:
THIS IS FOR ADVANCED/EXPERIENCED USERS ONLY
[ info ]
hello devs/users this should be a useful tool (its just a small CMD/batch script) for u guys...
so it will basically pack zImage and ramdisk into kernel.sin and then create an FTF which can be flashed via FlashTool...
[ requirements ]
windows
may be Java installed
[ supported devices ]
Xperia X10 ONLY
[ usage ]
place the compiled kernel zImage & compressed ramdisk (cpio.gz) in the same folder as these files
rename zImage to "image" (without quotes)
rename compressed ramdisk to "ramdisk" (without quotes)
edit the BUILD-IT.bat file and modify the following entries:
Code:
echo branding: DooMKernel-v06-BootManager-v1.4 >> manifest.mf
echo Created-By: DooMLoRD >> manifest.mf
echo version: 2.3.3 >> manifest.mf
ren kernel.jar X10_2.3.3_DooMKernel-v06-BootManager-v1.4.ftf
to whatever you want, as this is what will be displayed in FlashTool FTF window
once you are done editing that file save it
now double click on BUILD-IT.bat to launch kernel.sin & FTF build process
at end you will get a FTF which can be flashed via FlashTool
[ download link ]
kernel.sin and FTF creator v1.0
[ other useful links ]
[DEV][TOOL] kernel.sin unpacker
[How-To] Make custom bootscreen/bootlogo (image to rle)/(rle to image)
Enjoy!
Click to expand...
Click to collapse
I've edited built.bat as you suggest, but the output is just a kernel.sin and manifest.mf but not create files FTF, why is there anything wrong with that? Can you explain in more detail?
Apif Fuloh said:
I've edited built.bat as you suggest, but the output is just a kernel.sin and manifest.mf but not create files FTF, why is there anything wrong with that? Can you explain in more detail?
Click to expand...
Click to collapse
you do not have java installed ???
btw you can use this
kernel kitchen
I will try it
Sent from my Xperia X10 using xda premium
i see u got many brains so i ask...
with thies tools u show.
is it posseble to get an ftf file like ST18i_4.1.A.0.562_(1252-5332).ftf firmware but with root and cwm installed alreddy ?
If so please send me one.. im just goin crazy on having to reflash my device then installing cwm and root plus other things all the time...
Right now im up to 43 times installing over and over (im trying to get a rom to work) ( but always get it too loop the logo screen always)
REQUEST
championswimmer said:
you do not have java installed ???
btw you can use this
kernel kitchen
Click to expand...
Click to collapse
can U please Xplain me the step to create img to sin pleaseeeeeeeeeeeeeee................
and i installed jdk and android sdk
and since my phone doesnt go in fastboot mode I want to change my kernel via flashboot mode
so the file must be ftf and sin format .
SO PLEASE ............PLEASE .............. PLEASE help me .................
Will this work on a r800?
Related
Hi friends,
This Guide might be Helpful for all Xperia device Users/Developers
1.First you need to download these 4 files
a)FTF extractor
b)META-INF folder and ROOTING files
c)7zip
d)Notepad++(Optional)
2.Extract ftf extractor anywhere you like
3.Open the *FTF file with 7Zip
You'll see these files and folders
Code:
META-INF
adsp.sin
amss.sin
amss_fs_urushi.sin
apps_log.sin
cache.sin
fota0.sin
fota1.sin
kernel.sin
loader.sin
system.sin
userdata.sin
4.Extract system.sin to the folder where you extraxt ftf-extractor.
5.Press SHIFT+RIGHT CLICK on the empty space of the folder.You'll see a dialog 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"
}
6.select OPEN COMMAND WINDOW HERE
7.Type
Code:
aIUP.exe system.sin 4096 system
8.If this not work for you use 2048 or 8192 instead of 4096:good:
9.You'll see
Code:
C:\ftf_extractor>aIUP.exe system.sin 4096 system
UnPacking system.sin to system ...
done.
C:\ftf_extractor>
Congratulation now you have extracted System from the ftf file
10.Now open the downloaded META-INF AND ROOT.zip
then,go to system and cut
Code:
app
xbin
bin
and pasteit in your extracted system folder (In step 9)
***Now your rom is rooted*****
OR
You can use Kitchen to ROOT YOUR ROM
11.Then Move your Rooted system folder to the META-INF ZIP
***Now you have made a flashable zip file****
13.(Optional)go to META-INF/com/google/android/updater-script and edit it with Notepad++
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:Thats all:victory::victory::victory::victory::victory:
Lastly, Hit THANKS if you like it... and rate this thread 5-STAR
Knight47
That(aZuZu's tool for extract) worked with GB and ICS(only for Neo or Arc) ftf's, it doesn't work for Neo V or Arc S fw's, not sure about Ray.
Only way I found so far is, use flashtool to get yaffs img from system.sin, and then use unyaffs on that .img file to get extracted folders.
EDIT: log
C:\Users\Madfish\Desktop\ftf_extractor>aIUP.exe system.sin 4096 system
UnPacking system.sin to system ...
Error: Page size parameter is wrong.
done.
C:\Users\Madfish\Desktop\ftf_extractor>aIUP.exe system.sin 2048 system
UnPacking system.sin to system ...
Error: Page size parameter is wrong.
done.
C:\Users\Madfish\Desktop\ftf_extractor>aIUP.exe system.sin 4096 system
UnPacking system.sin to system ...
Error: Page size parameter is wrong.
done.
C:\Users\Madfish\Desktop\ftf_extractor>aIUP.exe system.sin 8192 system
UnPacking system.sin to system ...
Error: Page size parameter is wrong.
done.
C:\Users\Madfish\Desktop\ftf_extractor>
Click to expand...
Click to collapse
Madfysh said:
That(aZuZu's tool for extract) worked with GB and ICS(only for Neo or Arc) ftf's, it doesn't work for Neo V or Arc S fw's, not sure about Ray.
Only way I found so far is, use flashtool to get yaffs img from system.sin, and then use unyaffs on that .img file to get extracted folders.
EDIT: log
Click to expand...
Click to collapse
It worked on ray,mini pro.,neo
It'll work on neo v too but you have to try different compression value.
Sent from my ST18i using Tapatalk 2
Is there any way to make a rom from a nand backup ??
TheDarkDefender said:
Is there any way to make a rom from a nand backup ??
Click to expand...
Click to collapse
Yes there is ..
Take out nandroid backup
now go to the Folder where the backup is there ... extract the System.img through Cygwin ... and you are done!!
music.soul said:
Yes there is ..
Take out nandroid backup
now go to the Folder where the backup is there ... extract the System.img through Cygwin ... and you are done!!
Click to expand...
Click to collapse
there is a "system.yaffs2" disc image ..Im assuming that is the "System.img" you are referring to..right?
Knight47 said:
It worked on ray,mini pro.,neo
It'll work on neo v too but you have to try different compression value.
Click to expand...
Click to collapse
If you find which one to use, let me know.
music.soul said:
extract the System.img through Cygwin ... and you are done!!
Click to expand...
Click to collapse
cygwin is environment..
I guess you meant on dsixda's kitchen?
There is unyaffs.exe which work under windows so no need to mess with kitchen.
But yeah, for start kitchen is good.
Madfysh said:
If you find which one to use, let me know.
cygwin is environment..
I guess you meant on dsixda's kitchen?
There is unyaffs.exe which work under windows so no need to mess with kitchen.
But yeah, for start kitchen is good.
Click to expand...
Click to collapse
where is this "dsixda" and " unyaffs.exe".. ? could you elaborate,please? Im kinda new to this
TheDarkDefender said:
where is this "dsixda" and " unyaffs.exe".. ? could you elaborate,please? Im kinda new to this
Click to expand...
Click to collapse
Unbelievable, have you even bother to google for dsixda?? (no need to answer, I know answer)
Madfysh said:
Unbelievable, have you even bother to google for dsixda?? (no need to answer, I know answer)
Click to expand...
Click to collapse
yeah..sorry..did it..thanks
TheDarkDefender said:
there is a "system.yaffs2" disc image ..Im assuming that is the "System.img" you are referring to..right?
Click to expand...
Click to collapse
Hey Yeah! sorry! am just bit messed with the stuff in my mind
Yes! DSIXDA
Knight47 said:
It worked on ray,mini pro.,neo
It'll work on neo v too but you have to try different compression value.
do u know the compression value for extracting ics ftf file of neo v
Click to expand...
Click to collapse
roninnbaby said:
Knight47 said:
It worked on ray,mini pro.,neo
It'll work on neo v too but you have to try different compression value.
do u know the compression value for extracting ics ftf file of neo v
Click to expand...
Click to collapse
I think 4096
Sent from my ST18i using Tapatalk 2
Click to expand...
Click to collapse
Knight47 said:
roninnbaby said:
I think 4096
Click to expand...
Click to collapse
According to my log from post#2, it's not.
Click to expand...
Click to collapse
Knight47 said:
roninnbaby said:
I think 4096
Sent from my ST18i using Tapatalk 2
Click to expand...
Click to collapse
its not possible with 4096 compression value... i tried
Click to expand...
Click to collapse
Hello guys!
I've done the entire guide with my firmware (MT11i_4.1.B.0.431) but when I put the command line it says: done!, but I don't see any system folder so I can't paste root files. What's wrong? I don't understand it.
By the way, once you have done everything, is there any way to "compress" again the file into a rooted system.sin file so when i could flash it with flashtool?
Thanks!
gbueno6 said:
I've done the entire guide with my firmware (MT11i_4.1.B.0.431) but when I put the command line it says: done!, but I don't see any system folder so I can't paste root files. What's wrong? I don't understand it.
Click to expand...
Click to collapse
Have you even read reply's in this thread??
gbueno6 said:
By the way, once you have done everything, is there any way to "compress" again the file into a rooted system.sin file so when i could flash it with flashtool?
Click to expand...
Click to collapse
No.
Can I copy init.d folder to rooted ROM ?
Sent from my LT15i using xda premium
Madfysh, I think you don't need to talk to me like that, but yeah, I've read the entire topic twice (even your post of course) and I asked that question because It said "done" instead of "error" with 4096 but I saw no system folder.
Anyway, thank you for your help, I will root using the "normal" way.
gbueno6 said:
Madfysh, I think you don't need to talk to me like that, but yeah, I've read the entire topic twice (even your post of course) and I asked that question because It said "done" instead of "error" with 4096 but I saw no system folder.
Anyway, thank you for your help, I will root using the "normal" way.
Click to expand...
Click to collapse
So you don't get error about wrong page size parameter? Like logs in my post?
There are easier/faster way to root ics than messing with this. But if you really wanna try this there are 2 other ways explained in this thread.
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 extra (extra thanks..)
(may U?)
nelikp said:
I need this for extra (extra thanks..)
(may U?)
Click to expand...
Click to collapse
ähem lol thats not needed...?
jader13254 said:
ähem lol thats not needed...?
Click to expand...
Click to collapse
hahahahaa
Happy theme-ing
Thanks for the tutorial, I think I'll try this at the weekend just for fun. :good:
Nice tutorial, almost n00b proof. But I use kernel kitchen instead of cygwin. ?
Sent from my LT15i using xda premium
datagubben said:
Nice tutorial, almost n00b proof. But I use kernel kitchen instead of cygwin. ?
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
Seriously ??? Whats This?
$ ./extractboot boot_9.587c.IMG
./extractboot: ./split_bootimg.pl: /usr/bin/perl: bad interpreter: Permission denied
./extractboot: line 17: cpio: command not found
gzip: ../../boot.img-ramdisk.gz: No such file or directory
Click to expand...
Click to collapse
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
What kernel? Give me the link kernel
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
What kernel? Give me the link kernel
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=31910339&postcount=2304
nelikp said:
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
5-Now, unpack your boot.img by running the following command:
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
Click to expand...
Click to collapse
nice tutorial...how about working with ftf (kernel.ftf) can u make tutorial?
YeoZy96 said:
https://forum.xda-developers.com/showpost.php?p=31910339&postcount=2304
Click to expand...
Click to collapse
I can't pm u..
ad me
Android Magic Header ?
Code:
$ ./extractboot boot.img
Android Magic not found in ./boot.img. Giving up.
gzip: ../../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
Rom
Doesn't work for me :/ Can everyone make it from this kernel : forum.xda-developers.com/attachment.php?attachmentid=916452&d=1330029354 The ICS (SONY) logo? please
just want change to the old SE boot logo
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
how to get boot.img from kernel
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
anishkrsuman said:
how to get boot.img from kernel
Click to expand...
Click to collapse
plz make me clear how to get boot.img from any kernel and after that where to put them??
On windows using cygwin:good:
---------- Post added at 07:52 PM ---------- Previous post was at 07:46 PM ----------
nelikp said:
What kernel? Give me the link kernel
Click to expand...
Click to collapse
plz make this kernel with sony ericsson default logo
http://minicm.googlecode.com/files/E15_nAa-14_2.6.29.6-nAa-14.ftf
The main thing here is how you can successfully install cygwin . I see a lot of people get stuck with this software. You can follow the guide by jimbo77 (as mention in first post) for some error.
I think no one can do help for changing kernel logo.Because it's not right for kernel's owner
YeoZy96 said:
Seriously ??? Whats This?
Click to expand...
Click to collapse
install perl & cpio package in cygwin installer & run as admin
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 maybe)
(may U?)
great work man
:laugh:
i got this eror what to do?
Theliakos said:
i got this eror what to do?
Click to expand...
Click to collapse
run as administrator
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
LaShto34 said:
Thanks for this tutorial. But how about when the ramdisk is lzma? I tried changing commands from extractboot and packboot (from "gzip.... " to "lzma........." ) everything works well, the phone boots, but I don't have recovery mode anymore. In rest the kernel is perfect. But I need recovery mode, for installing things. I guess changing the command "gzip - or gunzip, whatever" to "lzma" is not all I have to modify. Any chance for a help?:crying:
Click to expand...
Click to collapse
same problem
Nice and awesome tutorial brother! :good::fingers-crossed::highfive:
Deleted
yamin8000 said:
same problem
Click to expand...
Click to collapse
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Sent from my ST15i using xda premium
Singgih4050 said:
So all the step is the same with the one on the OP except we need to change gzip -c into lzma -dc?
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work with this tutorial (at least for me, because I lost recovery - In rest the kernel behaves normal, but we all need cwm recovery). It only fully works (again, for me) with that modified version of android kernel kitchen 0.3.1.
Will this method work with LOCKED bootloader?
mine can't be unlocked
No it will not working because this is tutorial about to change a kerenl bootlogo (Sony Ericsson) word on startup phone..
Your phone cant be unlocked and no chance to change/flash custom kernel with custom bootlogo.
GSUKeitarou said:
Will this method work with LOCKED bootloader?
mine can't be unlocked
Click to expand...
Click to collapse
---------- Post added at 03:46 AM ---------- Previous post was at 03:45 AM ----------
Good job mate :good:
works for me after i edit bootlogo for Xperia play kernel by doomlord and i managed to enter cwm
LaShto34 said:
Finally. I made it. For lzma ramdisks use this http://forum.xda-developers.com/showthread.php?t=1659584&highlight=lzma but I modified it to something like this (see attachment). All credits must go to the original developer, I only changed some "gzip -c" word to "lzma -dc". And I managed to modify any kernel with lzma compressed ramdisk. :good:
Click to expand...
Click to collapse
thanks for the guide:fingers-crossed:
Al ok but phone not booting after bootlogo changed!!!!
Code:
[email protected] /boot
$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 5920144 (0x005a5590)
Ramdisk size: 4617107 (0x00467393)
Second size: 0 (0x00000000)
Board name:
Command line: androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-h
cd.park=3 vmalloc=400M androidboot.emmc=true
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
13874 blocks
[email protected] /boot
$ ./packboot
Using base address 0x80200000
Using command line 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F
ehci-hcd.park=3 vmalloc=400M androidboot.emmc=true'
[email protected] /boot
$
Whas is my erros?? My phone can't booting after flash boot.img (new), i don't change bootlogo, only unpack and repack .Thank for help
But now WORK when i change with android kitchen =))
I've been getting this error. I'm already run as administrator. What's the problem?
Xperia Boot Menu v1.0
Disclaimer:
- Me (munjeni) is not responsible for anything related to the our project, you using our project on your own risk! If you no want to risk than don't play with Boot Menu! You can play with Boot Menu but on your own risk!
Feature:
- multiboot based on kexec
- posibility for defining: menu title, path to the kernel, path to the ramdisk, kernel cmdline
- posibility for defining max 10 menus
- autoreboot to the first kernel if menu is not moved (stop timer on menu move)
- graphic timer
Instructions:
- create folder "bootmenu", add settings.ini to these folder, modify settings.ini for your needs
- flash bootmenu using fastboot command (fastboot flash boot recovery.img)
- since internal sdcard is only supported by now, you can define only kernel and ramdisk from internal sdcard path! Make sure you define right path and make sure create folders in bootmenu on your internal sdcard
- make sure settings.ini is in internal sdcard in folder bootmenu!!!
- kexec can boot only kexec patched kernels, so your kernel need to have kexec patch!!! Kexec patch you can ind o my git!
Simple settings.ini (example):
[rom-1]
menutitle=recovery touch white
kernel=/sdcard/bootmenu/examplerom/zImage
ramdisk=/sdcard/bootmenu/examplerom/initrd.gz
cmdline=cachepolicy=writealloc noinitrd init=init board_id=1 logo.nologo root=/dev/ram0 rw rootwait console=null androidboot.console=null androidboot.hardware=st-ericsson [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] mpcore_wdt.mpcore_margin=359 end lpj=24019
Click to expand...
Click to collapse
Download:
- http://d-h.st/2kZ
Kernel source code:
- https://github.com/munjeni/android_kernel_xperiago/tree/jb-dev
Reserved for feedback after Download and testing ...
Keep up the good work !!
Cheers !!!
Sent from my Xperia Sola using xda premium
Since Xperia Sola have small amount of developers, I will not post here, if you want to learn or to watch development progress you can go here -> http://forum.xda-developers.com/showthread.php?p=44933763#post44933763
Here I will update only new files when I make any more progress!
Boot Menu download link is ready!
Allso here -> http://d-h.st/rNX is example settings.ini, kernel, ramdisks, kernel modules, new cwm touch white.
How to test our boot menu:
- create folder caled "bootmenu" in your sdcard, extract settings.ini to these bootmenu folder
- create 2 folders inside bootmeny folder, first folder called "exse" and seccond called "cwmtouch", put ramdisk-recovery.gz to cwmtouch folder and copy zImage to folder cwmtouch
- copy zImage to folder exse and copy jb.ex.se.gz so folder exse
- reboot to the fastboot, flash boot menu using command: fastboot flash boot recovery.img, reboot and enjoy! Boot meny will contain cwm touch and extreme security boot options, to get extreme security boot you need to have extreme security rom installed! If you going to add another menu (aka antother android boot) simple extract ramdisk from these rom, create new folder, put zImage and these ramdisk to these folder, add new lines to settings.ini, make sure to carefully edit settings.ini , if you using zImage from out attacment make sure add modules to the /system/lib of your android...etc
Enjoy!!!
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
Resvered for feedback
I'll download and try it
Thanks for your dev for sola
Test ok
it's awesome
so it can put many recovery inside right?
Send with my Nokia 3310
munjeni said:
Guys, found a bug in Boot Menu! For example shifting trought menu failed to select right thing, for examle it select an submenu but boot another rom ...I will fix them in next version! You ca duplicate menus and experiment by now
Click to expand...
Click to collapse
New version is out, bug is fixed! Simple redownload from first post! Enjoy!
munjeni said:
New version is out, bug is fixed! Simple redownload from first post! Enjoy!
Click to expand...
Click to collapse
He is the man
Sent from my HTC_Amaze_4G using xda premium
munjeni said:
Xperia Boot Menu v1.0
Disclaimer:
- Me (munjeni) is not responsible for anything related to the our project, you using our project on your own risk! If you no want to risk than don't play with Boot Menu! You can play with Boot Menu but on your own risk!
.........................
Click to expand...
Click to collapse
Thanks a lot bro.........
I don't understand what's "zImage" and "initrd.gz"......
Can anyone explain those?
md094 said:
Thanks a lot bro.........
I don't understand what's "zImage" and "initrd.gz"......
Can anyone explain those?
Click to expand...
Click to collapse
Files that you get after you unpack your kernel ...
Sent from my Xperia Sola using xda premium
Thanks @soulhackereborn. I got it!
Excuse me, another question: Does Experimental kernel support Kexec? Which kernel supports that? Can anyone give me a link for Xsola kernel that supports Kexec? I searched but I didn't find anything.
excuse me for noob questions.
md094 said:
Thanks @soulhackereborn. I got it!
Excuse me, another question: Does Experimental kernel support Kexec? Which kernel supports that? Can anyone give me a link for Xsola kernel that supports Kexec? I searched but I didn't find anything.
excuse me for noob questions.
Click to expand...
Click to collapse
If you see the 4th post you will find that the whole set of kernel setting m other stuff already given
Follow the instructions carefully
N presently only Extreme JB supports but you can edit settings.ini and add respective kernels to boot the respective roms
Cheers
Sent from my Xperia Sola using xda premium
More info you can watch in Xperia U section! There was some problems related to corupted data partition but all is seems solved! Allso some example tutorials is given for beter understanding boot menu!
soulhackereborn said:
If you see the 4th post you will find that the whole set of kernel setting m other stuff already given
Follow the instructions carefully
N presently only Extreme JB supports but you can edit settings.ini and add respective kernels to boot the respective roms
Cheers
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Thanks a lot bro.... I didn't see the post#4 correctly......
I'm downloading now....
I have a problem with extracting kernels (boot.img).
I tried extracting a boot.img file with cygwin kitchen and some boot stuff (like extractboot) but when I do this I face this error message:"Android Magic not found in ./boot.img. Giving up. ...."
Here is the screenshot:
{
"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"
}
Please help me....
very thanks for your answers...
md094 said:
Thanks a lot bro.... I didn't see the post#4 correctly......
I'm downloading now....
I have a problem with extracting kernels (boot.img).
I tried extracting a boot.img file with cygwin kitchen and some boot stuff (like extractboot) but when I do this I face this error message:"Android Magic not found in ./boot.img. Giving up. ...."
Here is the screenshot:
Please help me....
very thanks for your answers...
Click to expand...
Click to collapse
me too, until now i can't extracting boot.img/kernel.elf for sola
Guys please watch Xperia U Boot Menu thread, there is a lot of tuts and allso tools for repacking, packing, extracting...etc! On page 7 I posted tools -> http://forum.xda-developers.com/showthread.php?t=2418241&page=7
Hey Guys......Can we DUAL BOOT with this method?
How?
md094 said:
Hey Guys......Can we DUAL BOOT with this method?
How?
Click to expand...
Click to collapse
Yes read the instructions given !!!!
Sent from my Xperia Sola using xda premium
soulhackereborn said:
Yes read the instructions given !!!!
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
I want to Dualboot "Ultimate Rom V11" and "Unofficial CM10.1" Where Should I place Roms? In sdcard/.... ??
Which of them should be installed completely (in /system)?
What should i do?
I read the instructions but there wasn't any guide to have dualboot. just mentioned.
md094 said:
I want to Dualboot "Ultimate Rom V11" and "Unofficial CM10.1" Where Should I place Roms? In sdcard/.... ??
Which of them should be installed completely (in /system)?
What should i do?
I read the instructions but there wasn't any guide to have dualboot. just mentioned.
Click to expand...
Click to collapse
Go to xperia u android development forum / xperia boot menu thread, there is some good tutorials! In short explanations you need to chose which one will be your primary rom (these rom going to emmc), all other roms is on sdcard (have file based partitions)...
Hello, everyone!
This is intended for everyone who want to modify kernels they are using. Since I could not find tutorials on how to repack kernels for our Novathor devices, I decided to write my own tutorial. Maybe there are other ways, but this is how I do it and it is 100% failsafe. I took transcendence CM 1.1.6 kernel as an example in this tutorial. So, let's start!
Requirements:
- Flashtool
- Linux (Ubuntu preferable), you can also use builduntu if you don't want to install linux to your hard drive
- Files provided in attachment
- Not to close terminal in linux at any price
- Brains
STEP 1: Unpacking
First of all, you want to unpack the kernel. This is the easiest one.
Fire up Flashtool, select tools/extractors/elf
Easy, right? Now, click on those three dots and find kernel you wish to modify. Kernel MUST have .elf extension for this to work, so if you have "boot.img" at you disposal, please rename it to "kernel.elf" (without quotes). Once you loaded your kernel, just click unpack. Do not close Flashtool yet. In it you will see logs that kernel is unpacked. Please take a screenshot of that window as we will need that report later. Screenshot should look 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"
}
After you have saved screenshot somewhere, look in the folder where your kernel is, and you will find two or three files additional files, sometimes even four, depending on the kernel itself. They should be named this way:
kernel.elf.ramdisk.gz (very rarely, this file may be called kernel.elf.2)
kernel.elf.Image (sometimes this file may be called kernel.elf.1)
kernel.elf.3
kernel.elf.cmd
It depends on the kernel how much files you're going to have. Now, please rename them, so that you delete kernel.elf from names. Now they should be named like this:
ramdisk.gz
Image
3
cmd
Bolded files are needed for our modifications. Now to the next step!
STEP 2: Modifying
Now that we have needed files at our disposal, it's time to do the modifications.
Image file
This file is zImage of the kernel. This is the core of the kernel, where CPU frequencies, drivers, governors, etc. are stored. This file you cannot really modify but if you have built your own specific zImage, you can replace it. I don't recommend touching this file unless you know what you're doing (in other words, unless you're developer or programmer).
So, noobs: don't modify this file; pros: Go ahead
ramdisk.gz
You want to change that sweet boot image, that's why you want to unpack kernel in the first place? On how to create boot image, go here.
This file contains the rest of the tweaks developers apply to kernel. Here you will find CWM, bootsplash image, autoroot files, etc, all depending on kernel you are modifying. Now, hot to unpack this bloody file? some suggest to use 7zip, but this way you will break symlinks and your kernel will definitely not boot. Proper way of unpacking ramdisk.gz goes like this:
First of all, boot up linux (or load builduntu into virtual machine, your choice).
We want to set up working folders, right? Fire up terminal and enter following commands, one line at the time:
mkdir kernel-working
mkdir ramdisk-working
cd ramdisk-working
mkdir ramdisk-contents
cd ramdisk-contents
Click to expand...
Click to collapse
Don't close terminal, or I will break you fingers Now in your home folder you will find folders we've just created. Nice, isn't it? Remember those files we've unpacked earlier? copy them to these folders. ramdisk.gz goes to ramdisk-working folder, while the rest goes to kernel-working folder.
Download kernel_repack.zip from the attachment und unpack files which are in it to kernel-working folder.
Now we're all set up for modifying
Go back to the terminal. Copy and paste following command and run it:
gunzip -c ../ramdisk.gz | cpio -i
Click to expand...
Click to collapse
Again, don't close the terminal. This time I will break your legs if you do so Now ramdisk.gz is unpacked in ramdisk-contents folder (which is in ramdisk-working folder). There you will find bunch of files and folders. After you have done all your modifications, it's time to pack it up. To do so, run the following command in terminal:
find . | cpio -o -H newc | gzip > ../newramdisk.gz
Click to expand...
Click to collapse
In ramdisk-working folder you will find newramdisk.gz file, besides ramdisk.gz. Copy newramdisk.gz to kernel-working folder and rename it to ramdisk.gz.
Now all files for compiling new kernel are prepared. To the next and final step.
STEP 3: Packing kernel back
In terminal, run following commands (and yes, you run cd .. twice in a row):
cd ..
cd ..
cd kernel-working
Click to expand...
Click to collapse
Remember that screenshot we've took earlier? This is where we need it Told you so
And finally, here is the mother of all commands which neatly packs all of our files back into kernel, but don't use it just yet, I will explain why:
sudo python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],cmdline
Click to expand...
Click to collapse
Take a look at the my screenshot and you will see that each of the files have its own adress. For example Image is at the adress 0x00008000 and ramdisk.gz is at the adress 0x01000000,ramdisk and 3 is at the adress 0x00000000,cmdline. By writing proper names and adresses, I'm telling computer where to pack files inside the kernel. You will have to change adresses in this command according to your screenshot, because not all kernel have the same adresses for same files. This is the most important step because if you do this wrong, kernel will not properly compile!
If you did all the work correctly, in kernel-working folder you will find new kernel.elf file. If it was named boot.img before editing, rename it back, if it was named kernel.elf then leave as it is. If you want, you can test if you packed kernel properly by trying to unpack it in Flashtool. If flashtool reports that you have some files to unpack, than all is OK, if it reports nothing, then something went wrong.
Ta-da! Your kernel is finally packed and is ready to be flashed to your phone. Hopefully, if you didn't messed up something when you did your modifications and alterations to ramdisk.gz, it should properly boot.
You can flash kernel in your preffered way.
Final words:
I tried to make this tutorial as user-friendly as possible. It is pretty straightforward once you get into it.
I hope that I clarified some thing, and more importantly, that I helped you.
Cheers everyone, and happy, repacking/flashing/modifying
Not a bad guide! Keep it up!
Sent my Carbonised Xperia P
Nice! :good:
Another good reference for kernel unpacking is this: http://forum.xda-developers.com/xperia-u/general/tutorial-explaining-stock-boot-image-t2126924
Enviado desde mi ST25i mediante Tapatalk
great guide
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Johnt880 said:
I just have windows , so am i doomed ?? I just wanted to change my kernel to Candy instead of Sony
Click to expand...
Click to collapse
Run builduntu in virtualbox.
If i got a sony kernel that sorted with the word sony out that will do my phone ?Just a standard kernel
I didn't quite understand you, can you clarify a little?
kernel 4.4.2
is there a way to modify the kernel aosp 4.4.2. This method does not work
kosmos-2011 said:
is there a way to modify the kernel aosp 4.4.2. This method does not work
Click to expand...
Click to collapse
Try that > http://forum.xda-developers.com/showthread.php?t=2073775