Question about kernels - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

If I flashed a rom that has a different kernel and then went back to a rom that has a stock kernel do I not have a stock kernel anymore?
I went from Poprocks to texodus then back to poprocks.

If the new rom you flashed included the stock kernel, then that's the kernel you have now. Kernels don't survive a rom flash, they get overwritten by whatever kernel is included in the rom.

Thanks

Related

How to flash new kernel

Can someone point me to a step by step guide on how to flash a new kernel to my HTC Hero? I currently have the following when I look under kernel:
2.6.49-bc0d2cff
[email protected] #1
I want to flash HoneyBun's kernel so I can achieve overclock on the nfinite stock 2.1 ROM.
Thanks..what I tried doing was completely wiping my phone, then flashing HoneyBun's kernel via recovery on my phone then flashing nfinite ROM, but I still cannot overclock when I try to use SetCPU (it still only lets me go up to 528 Mhz)
EDIT: Nevermind, I got it. I was flashing the kernel then the ROM over it, which basically overwrites the kernel anyway. So, I flashed the ROM first then the kernel, and now it works perfectly.

[Q] Looking for flashing advice for CM

I'm currently running a custom Gingerbread 2.3.6 with Semaphore JW1 2.40 kernel. I have root, superuser, and CWM, and I want to flash Cyanogenmod 9.1. I didn't get a specific answer in the CM forums, hoping for better luck here:
My questions:
1. The installation guide says to flash back to stock if already running a custom ROM, but what should I flash? Since CM9.1 is a ICS based ROM, do I need to flash a 4.0 ROM?
2. Should I flash the kernel to a stock one as well? I've seen a general guide in the CM forums saying to start from stock and Semaphore gingerbread based kernel, and then just run update.zip from CWM. On the other hand, I've also seen a contradicting thread saying that CM9 is only compatible with ICS kernels and using a GB kernel will cause a bootloop.
2. I also have the filesystem converted to ext4. Do I need to convert it back before doing anything?
3. Does CM9.1 installation come with its own custom kernel? If not, are there specific kernels that can be used with CM9.1 or is any Android 4.0+ kernel usable?
Hey
I think you should revert back. Flash stock gingerbread with odin, install sempahore kernel and flash the rom you want(I would actually recomend cm10, Its very stable). Goodluck!

[Q] Help flashing the right kernel

I have an untouched Note running stock ICS 4.03 -- Kernel 3.0.15-N7000XXLPY ...). I'd like to be able to safely flash a custom ROM, avoiding the brick bug. I've been digging through a lot of threads, but some uncertainties remain.
Here's what I'm about to do: I'll get the Philz kernel matching my current rom (this would be PhilZ-cwm6-XXLPY-XEN-v3.99, right?), boot into stock recovery, flash the .zip from the sd card, and boom, I'll have a safe kernel with root and CWM to flash any ROM from. Is this about the right plan?
2 more specific questions:
1. The matching Philz kernel was posted under the headline "Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99" in the Philz kernel thread. But I'm running 4.03. So is this the right kernel for me?
2. Will the ROM I install after that have to match the Philz kernel in some way? I'm thinking of getting the Official CM 10.1 from the nightlies thread.
Thanks so much!!
That's the right plan
1. The correct rom is found under rom build which is the last in the section where you found the kernel version. The 4.0.4 also works with 4.0.3 so it's ok.
2. No the new rom will install a new kernel. Philz won't work with cm as philz is Samsung kernels repacked for safety and recovery..
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Correct me if I'm wrong but I don't think you can flash CM 10.1 from stock recovery.
Philz kernel comes with CWM recovery which provides more functionality than the stock recovery.
For example you can do a nandroid backup (basically a snapshot of your current phone system) so if you ever flash a rom that you don't like or something screws up, you can just restore your backup.
I think your first priority should just be flashing a safe kernel (Philz) and only then should you be looking into flashing custom roms.
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Custom rom can only be installed using Cwm
OK, thanks for your help guys. I just flashed the Philz kernel following to the instructions and all is well. CWM is working, and I appear to have root access in my old stock ROM.
But in the phone info, the kernel version is unchanged. It stil says: "3.0.15-N7000xxlpy-cl474507 [email protected] # 3 SMP PREEMT Fri May 4 04" -- which is the exac same thing it said before I flashed the kernel.
How can I verify if I'm actually running the safe Philz kernel now?
PhilZ Kernel are only modded kernel, so they aren't change and stock kernels. And so you won't see a description made by PhilZ but only the normal information of the original kernel.
To be sure: boot into recovery and check the CWM version and compare it with the infos in PhilZ thread.
But you told already that you do not have the stock recovery, so everything is ok.
Thanks ThaiDai. The fact that I had moved successfully from stock recovery to CWM was already a strong hint that things worked out.
I wanted to make extra sure, so before flashing the first custom ROM I went into CWM, made a backup of the stock samsung, and then took this script right here to examine the operating kernel (boot.img in the backup folder) for the brick bug: http://forum.xda-developers.com/showthread.php?t=1807995 -- the script returned that the kernel was safe.
So I went on to flash CM 10.1 and I'm a happy camper now! This forum is a great place for getting help, you guys are terrific!

[Q] Can I flash the stock kernel on a CM ROM?

Can I flash the stock kernel on a CM ROM? Notably the latest stock kernel on CM11+.
The answer appears to be no unless maybe its patched. I restored a stock kernel over a CM11 TWRP restore and the screen just turned off after the boot logo.

base kernel??

I flashed **** kernel and now I have issues with aosp roms. Is there a way to go back to base? Its very annoying not being able to use PE
Kernel is actually in boot.img so whichever rom you were using just flash it's boot.img back and it will work

Categories

Resources