[Q] How can I extract CM11 kernel from CM11 ROMS and flash to another ROM - Nexus 5 Q&A, Help & Troubleshooting

I want to play with flashing the unofficial CM11 kernel onto different roms. How do you extract the CM11 Kernel from CM11 roms and flash to another rom? I've read in years past you can take things out of the rom zip file and throw it into a different zip and flash.
Thanks!

Extract the ROM zip and take out the boot.img. This is the kernel. It can be flashed via fastboot or flashify.
Sent using xda-developers app

Related

[Q] Need some guidance of kernel and custom rom install

I want to install ElementalX kernel and CleanRom JL. Since the kernel also supports hboot 1.4, i'm not sure what should be the order of installation?
1. Flash kernel along with boot.img. Then flash custom rom on the phone
2. Flash just the kernel and skip boot.img installation. Then push the boot.img separately and flash custom rom
3. Push the boot.img separately and flash custom rom. Then, flash the kernel without boot.img support.
Can somebody help me out here. Thanks in advance.
Flash clean Rom then elemental

SamHD V2.1 Custom ROM and boot.img issue

Hi guys,
I wish to install SamHD V2.1 which is recently been released by Kumar Abhishek, but this time he has not integrated the boot.img in the zip itself but just posted the ramdisk to make updated boot.img from boot.img of stock ROM.
I am not too comfortable in using SP Flash Tool as its driver always give me trouble, now my question is:
I have made my own updated boot.img using Android Kitchen now can I just integrate the boot.img in the SamHDv2.zip and flash my device like we use to do it with the older version of the Custom ROMs, is it safe to flash like this?
Secondly, would I be able to boot my device properly after flashing SamHDv2.zip and Gapps.zip (without flashing boot.img with SP Flash Tool)?
I am asking so if it boot properly can I use MobileUncle to flash updated boot.img?
I think if I integrate updated boot.img in the SamHDv2.zip it should work fine after we used to flash in this fashion earlier also but I got to be damn sure before I go ahead.
Please guys guide me I am a newbie.

[Q] Aero Kernel on other custom ROMs

Hi
Since the CM version of Aero isn't available as a single zip, I was wondering whether somebody is using Aero Kernel from Quarx's CM11 on other AOSP custom ROMs.
Do I just need to take the boot.img or do I need other files, too? For example Phantom Kernel also has Wifi files included
Edit:
Ok, I extracted the boot.img and flashed it using Flashify, but Wifi didn't work. So there is indeed something missing

[Q] about kernels of moto g [CM12]

i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
gearguy365 said:
i am not overly familiar with many things regarding different kernels and how to work with them, so i was wishing a few questions that i had could be clarified by someone who knows:
1. when a kernel is flashed? i mean except for the times when we flash kernel.zips via recovery, is it flashed whenever we install a custom rom? or is it flashed with bootloaders when we flash firmware?
2. I am using CM12 official nightly and facing camera frizz issues. I came across a post in the official CM12 thread where they said flashing a modified kernel supposedly fixed this problem. Now my question is, after flashing a custom kernel, is there any way to go back to the stock one? by stock i mean either the one i was on right before flashing the custom kernel or stock moto g kernel provided by motorola?
that also begets the question, can kernels be backed up like roms using recovery?
Click to expand...
Click to collapse
1. The kernel is first flashed when you install a ROM. You are supposed to flash a custom kernel after flashing a ROM otherwise the rom zip will overwrite it. It doesn't matter if you install it in the recovery or the boot loader.
2. To go back to the stock kernel just take it from the zip of the ROM and flash in the bootloader
where can i find the kernel inside the rom zip?
and if i want the stock motorola kernel that comes with factory firmwares
how can i collect that?
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
mistercheese said:
A ROM.zip contains the system folder and a boot.img
The kernel is in the boot.img
So if u flash a different kernel and still facing problems then flash the ROM again.
Click to expand...
Click to collapse
flashing only the boot.img of a rom wont bring back the default kernel?
and is there any way to make a flashable zip of a kernel from that particualr boot.img?cause all the kernels i see (like donkey kang/customized cm12 kernel) there are all distributed in .zip format.....

How do I find the original CyanogenMod 13 Stock Kernel?

So the situation currently is that I have flashed CM 13 to my Galaxy S4 Mini and I also flashed a custom kernel (from a different person) after. I am experiencing some multi-touch issues when using the antutu multitouch test. I wanted to see if it was the kernel that was causing it and if the stock kernel would fix the issue, however, to do this I need the original stock CM 13 kernel but I don't know where I can find the zip file to flash it. Can anyone help out?
Please and thanks!!
EDIT: Never mind I've figured it out. If anyone is in the same boat, simply extract the boot.img from your CM13 ROM zip file (this is the image file which contains the respective kernel) and use Flashify (requires root) to flash your stock CM13 kernel that you just extracted from your ROM zip file.

Categories

Resources