How to extact zImage? - Android Q&A, Help & Troubleshooting

So i have extracted the boot.img file from my favourite ROM using abootimg and got the following:
bootimg.cfg
intird.img
zImage
Now i can see that the bulk of the kernel is in the zImage file though for the life of me i can't work out how to extract it.. Can it even be done?
I want to add overclocking to my old Grouper device i have the commits. if i could just see the file structure i can replace the files needed within the arch/arm folder and recompile i'd be done! i've searched everywhere though no one seems to advise on how to do it.
Thanking you in advance.

Related

Precook Kernel into Rom Zip

Is there a unified manner in which this is done?
I've been looking for a way to precook this kernel here: http://forum.xda-developers.com/showthread.php?t=756774 into my ROM's zip before flashing, to save myself the extra step.
Is there anything special to it? I assumed it might just be as straightforward as copying the entire folder structure into the ROM's zip, but the kernel inquestion actually has a third folder called "kernel".
Any help would be much appreciated, this combined with my LauncherPro cooking question earlier will make this ROM perfect for me
LiquidSolstice said:
Is there a unified manner in which this is done?
I've been looking for a way to precook this kernel here: http://forum.xda-developers.com/showthread.php?t=756774 into my ROM's zip before flashing, to save myself the extra step.
Is there anything special to it? I assumed it might just be as straightforward as copying the entire folder structure into the ROM's zip, but the kernel inquestion actually has a third folder called "kernel".
Any help would be much appreciated, this combined with my LauncherPro cooking question earlier will make this ROM perfect for me
Click to expand...
Click to collapse
unpack the existing rom zip's boot image, copy in the kernel you wants zImage, repack it and plop the boot image back into the sip. then remove all the modules in /system/lib/modules in the rom zip and copy all the modules from the kernel zip into the modules folder in your rom zip.
then you ware ready to go.
Yes man, but where to put the zImage? i have 2 GZ files and 1 folder. i tried to put it in the folder and repack that, and the rom stuck at the splash screen. where to put it and how?
thanks

Some tips regarding Unpack/Repack from kernel.elf

Just yesterday nikholtus told me
"you cannot repack a ramdisk twice. you always have to use a kernel.sin as source. a ramdisk extracted from kernel.elf will not work"
now ^^ that was strange, because if we can pack once we should be able to repack over and over again. So i went about trying to find what the problem was.
The problem as i understand is, the people over here at Xperia 2012 forum seem to use 7zip to extract the ramdisk from kernel.elf as explained in atarii's thread here
But we need to understand, that the proper method to unpack a ramdisk is
Code:
mkdir ramdisk-contents
cd ramdisk-contents
guncip -c ../ramdisk.img | cpio -i
using the 7zip method will destroy all symlinks and will NOT retain file permissions in the ramdisk
Thus such an extracted ramdisk will NOT be able to be reused by repacking it.
U might just have made alot of people do a tactical facepalm.
lol, that i didn't know this
now i have touch recovery (on my P)
very happy
btw lazy bummers (or even lazy developers) can use my kernel kitchen (link in my sig)
it can unpack and repack a kernel.elf for you as many times as you wish to make it do so
championswimmer said:
Just yesterday nikholtus told me
"you cannot repack a ramdisk twice. you always have to use a kernel.sin as source. a ramdisk extracted from kernel.elf will not work"
Click to expand...
Click to collapse
blame atarii
(i joke of course!)
nice one champ!!
Reviving old threads here, but alas, you are the only ones who know.
So if I unpack a ramdisk with 7zip and repack it later on, I won't be able to boot?
someone755 said:
Reviving old threads here, but alas, you are the only ones who know.
So if I unpack a ramdisk with 7zip and repack it later on, I won't be able to boot?
Click to expand...
Click to collapse
Sure,it will f))ck up the system!!
so unpacking a ramdisk should type the line like you post? so that it can be repack,right?
i can't access the third line command
is all of the step3 in unpack elf should change to the strings like you post?
and what is guncip?
gunzip
slsamg7112 said:
i can't access the third line command
is all of the step3 in unpack elf should change to the strings like you post?
and what is guncip?
Click to expand...
Click to collapse
gunzip as knows as
Linux Command - Unix Command.
Sent from Xperia Sola
but how it works? should i need anything else?
and it always says cpio is not a executable or bat file
how to solve it? thanks
I've heard from a very good source that our kernels don't in fact have symlinks. That same source has also said that the OP here is wrong and the ramdisk may be used as many times as we wish. And that we may use 7zip for unpacking it.
So yeah, I'll be using 7zip...

Help Need Meta-inf

So, my phone recently got soft bricked....
I had the tar file of the XXELK4 leaked firmware and i extracted it, unpacked system.img.
Mounted it as ext4 and extracted the contents.
I want to make a flashable zip file from the system.img contents.
I made a folder called system. In which all app, bin, etc and other folders are.
Then i copied over the boot.img from the tar file...
Now, i need the meta-inf. I tried using some meta-inf from other roms, and removing the aroma functions from them.
Then trying to flash..
I get only a bootloop.
So, could someone provide a clean Meta-inf consisting of only the updater-script and update-binary??

[Q] Files in a nandroid back up

Ive done a backup on my phone and created a flashable zip (update.zip)
Now im playing around with dsixda's kitchen and trying to extract the system.tar, however it fails most likely due to fact the the system.tar is empty
the files in the archive are as follows
Meta-inf -- <folder>
boot.img -- <8192KB>
image-edify -- <1KB>
system.ext4.tar -- <0KB>
system.ext4.tar.a -- <976,563KB>
system.ext4.tar.b -- <68,151KB>
By the looks of things it has split the system.ext4.tar because its over a gig
How can i compile this into one file or one image so that the kitchen can read it, I'm on a windows 7 PC but i can run linux in a vbox if necessary.
Thanks
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
mikep99 said:
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
Click to expand...
Click to collapse
Already tried, it comes back saying its deleting the part a and part b files and then says the system.ext4.tar isnt a valid archive.
Is it a stock rom?
If so, download the firmware from sammobile and put the tar.md5 file into your input folder (after removing the .md5 suffix).
Thats worked for me in the past....
It is stock, but i have removed the bloatware, installed a few mods, i was hoping to use this particular one really as a base. Ive already played around with fully stock and i kind of broke the whole thing
I'm not too sure then unless theres some tool you can find to merge the 3 tar files into 1...
Never had to do it so I'm unable to suggest anything I'm afraid.

boot.img changes after unpack-repack without edit

I have met some problem with boot.img and need some help if there's somebody know it.
I used unmkbootimg and mkbootimg, I unpacked a boot.img then got zimage and initramfs.cpio.gz, I repacked it without any edit but the new boot.img becames smaller, it changed from 13M to 7.9M, and the phone couldn't boot from new boot.img,
and there is no question if I use a boot.img extracted from an android3.x-version rom, but if the android version changes to 4.x, the unpack-repack process would lose much size...I tested on mi2s' rom......I don't know if there are some files that will be lost in unpack process, or say the process just ignore files other than zimage and initramfs...
does anybody knows why?
binghemoye said:
I have met some problem with boot.img and need some help if there's somebody know it.
I used unmkbootimg and mkbootimg, I unpacked a boot.img then got zimage and initramfs.cpio.gz, I repacked it without any edit but the new boot.img becames smaller, it changed from 13M to 7.9M, and the phone couldn't boot from new boot.img, does anybody knows why?
Click to expand...
Click to collapse
It could be because of incorrect settings for mkbootimg or there more files,than zImage and initramfs, needed for proper work. Hard to say without more information.
Sorry for my bad English.
B.B.N. said:
It could be because of incorrect settings for mkbootimg or there more files,than zImage and initramfs, needed for proper work. Hard to say without more information.
Sorry for my bad English.
Click to expand...
Click to collapse
There is no question if I use a boot.img extracted from an android3.x version rom, but if the android version changes to 4.x, the unpack-repack would lose much size...I tested on mi2s' rom......I don't know if there are some files that will be lost in unpack process, or say the process just ignore files other than zimage and initramfs...

Categories

Resources