Hi All
Thank you for the great work however in order to enjoy the ROMS I will need to have a smaller boot.img in order to flash the roms.
The image must be 2.35 MB at most, A good example is the Enomther ROM that is flashable.
However the CM6 roms are not (except KANG O RAMA).
Since I dont think that someone is going to do it for me, can you at least explain how can I do that?
There are at least 10 more people that check this forum regulary looking for a solution.
Thank you.
CM6 boot image is just 2.25MB!!!
OHH yea.... checked it out on his site yesterday, then how come rodriguez's image is bigger?
He's most probably using another kernel for CM6, just like MicroMod uses another kernel for TheOfficial.
OK. How can I use those features with a smaller kernel? Is there a way?
1) Ask the kernel / ROM creator to "pack" it to fit in 2.5MB of space.
2) Compile your own kernel and make your own boot.img.
3) Try to mix your desired ROM (for example, Micromod's) with the kernel that fits your limited boot space (for example, Enomther's original). Or you could try to use rodriguez's ROM with CM kernel. To do that mix, replace the boot.img and the WiFi driver - bcm4329.ko - in their locations in the original ROM zip and resign the zip, then flash it.
Why the need for a smaller boot.img?
Sent from my Nexus One using XDA App
HTCinToronto said:
Why the need for a smaller boot.img?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Many N1s do not allow kernels later than 2.4MB (or something like that)... the kernel does not flash because of bad MTD blocks...
Jack_R1 said:
1) Ask the kernel / ROM creator to "pack" it to fit in 2.5MB of space.
2) Compile your own kernel and make your own boot.img.
3) Try to mix your desired ROM (for example, Micromod's) with the kernel that fits your limited boot space (for example, Enomther's original). Or you could try to use rodriguez's ROM with CM kernel. To do that mix, replace the boot.img and the WiFi driver - bcm4329.ko - in their locations in the original ROM zip and resign the zip, then flash it.
Click to expand...
Click to collapse
OK. Thanks.
Can you send me a link with the instructions on how to change and resign roms?
[sorry for being a noob]
Unfortunately, I don't have any instructions available anywhere, but you can use some Google searching.
The boot.img resides in the root of the ZIP, the bcm4329.ko is in /system/lib/modules/.
Changing the files in the ROM is easy - ROM is just a ZIP file, you take a ROM you want to change, open it in WinZip / WinRar / your favorite freeware archiver, find the files you want to replace (the ones I've mentioned above), download the original ROM which is the base (Enomther for MicroMod, CM6 for Rodriguez), extract those files from there, drag&drop them into the ROM you're modifying, that's it.
Then you search Google for "android sign zip apk", and you get a couple of guides that show you how to sign ZIPs.
Then you load the ROM and hope it works.
does not sound complicated
thanks.... I will try that.
Yes, what you need is:
boot.img and everything in /system/lib/modules
It's important that you replace everything in /system/lib/modules with the correct content for the specific boot.img you're using and delete everything else.
My boot.img which is based on Wildmonks BFS 950 kernel supports apps2ext and 720p and should be sufficient for any CM6 rom. It's worth noting that the current one in Kang-o-rama 1.0 Final is not as stable as I would like and I'll be updating it soon.
Since this seems a bit challenging for some rom devs an alternative approach could be:
Create update.zip for small boot image (I can help with this)
Rom dev creates rom update.zip without a kernel (may not boot properly)
Install rom without kernel
Install small kernel update.zip
Or everyone could use Kang-o-rama...
Hello i have compiled stock kernel from lg sources and created the zImage file in arch/arm/boot folder using 4.6 google toolchain.I want to know how to make it flashable as zip file.I have tried anykernel tool without success :/ Any help appreciated!
Hi,
I need help to unpack stock boot.img of kitkat rom.
Kitchen cannot do that because of LZ format..
I compiled the latest version of unpackbootimg but no way to make a "gunzip" of the ramdisk.
Thanks !
@GalaxyUser
lz4 compression
I just tried with this tool (Android.Image.Kitchen.v2.0-Win32.zip)
http://forum.xda-developers.com/show....php?t=2073775
Seems OK
Hi,
Do you know how to extract kernel from installation file of rom and make flashable (in TWRP) zip kernel file ?
I need extract ant make flashable kernel file from [ROM][AQF5][6.0.1][G900x]SkiesROM UX v3.1 A7 2017
I will be grateful for your help
tomaasz said:
Hi,
Do you know how to extract kernel from installation file of rom and make flashable (in TWRP) zip kernel file ?
I need extract ant make flashable kernel file from [ROM][AQF5][6.0.1][G900x]SkiesROM UX v3.1 A7 2017
I will be grateful for your help
Click to expand...
Click to collapse
Hi,
Sorry for the delayed reply.
Can you be little more specific? Do you want to 1) extract the kernel (that is an "zImage") image or 2) simply the "boot.img"?
The second task is simple as you can simply copy the "boot.img" from the ROM zip. You can flash "boot.img" directly via twrp (no need to make flashable zip).
The first task, however, is bit complicated as it requires the use of some tools like mkbootimg or Android Image Kitchen to split the "boot.img". You can flash the obtained "zImage" by simply copying that into an existing anykernel based klte custom kernel. :laugh:
Feel free to contact me for any further clarification/help.
Hi,
Thanks for your answer. I needed flashable zip kernel file extracted from SkiesRom.
I wanted patch this by DualBoot
tomaasz said:
Hi,
Thanks for your answer. I needed flashable zip kernel file extracted from SkiesRom.
I wanted patch this by DualBoot
Click to expand...
Click to collapse
Hi, if you have a Linux, you can easily extract the zImage from the "boot.img" using mkbootimg (see previous comment for links). If you want me to do that job, feel free to send the "boot.img" of that mentioned ROM (I'll make a flashable anykernel zip file for you so that you can flash over any ROM).
Regarding the DualBoot, I really do not know...
I want to custom kernel without magisk.
So i tried to unpack boot.img in order to modify kernel in boot.img.
But, i couldn't unpack boot.img with any other unpack tool like Android image kitchen.
Common problem is about ramdisk.
i guess common unpack tools can't unpack pie 9.0 boot.img.
so i used different ways flashing other rom's boot.img because of using recent custom kernel. However, it is just temporary action.
do you know any other ways to unpack boot.img?
Letmeseeforest said:
I want to custom kernel without magisk.
So i tried to unpack boot.img in order to modify kernel in boot.img.
But, i couldn't unpack boot.img with any other unpack tool like Android image kitchen.
Common problem is about ramdisk.
i guess common unpack tools can't unpack pie 9.0 boot.img.
so i used different ways flashing other rom's boot.img because of using recent custom kernel. However, it is just temporary action.
do you know any other ways to unpack boot.img?
Click to expand...
Click to collapse
You can unpack any boot image if you have the right tools. If the problem is with unpacking the ramdisk, that would be because you are trying to use the wrong tool to decompress it. Open the ramdisk image with an hex editor, and post the values of the first 4 bytes. And then tell us which tool you are trying to use to decompress it.
Why ramdisk is empty?
Bro I have redmi note 7 pro
when I unpack boot.IMG , ramdisk folder is always empty
Why ?
is there something that I missing?