Sorry I am new with this so don't laugh at the noob question
Is there a way to flash a different Kernel onto the phone? What would be the difference between the ROM and the Kernel?
I have rooted my phone and installed a recovery and loaded a ROM but is there another process to load a different Kernel?
Thanks!
Visit This Tread (Decad3nce's Kernel)
It goes over what's different between each Kernel and how to flash them
Flashing a kernel is generally done the same way as a rom
Related
Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
No one?
neroux said:
Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
Click to expand...
Click to collapse
It is not the Stock kernel, it is a customized kernel which can be used for the custom ROM installation via ClockworkMod_Recovery.
thanks.
Thanks forupeople but that was not exactly the question. I would like to know whether the mentioned kernel is the actual kernel on which a ROM then is running on or whether all ROMs come with their own kernel and this is something else.
Really no one?
neroux said:
Hi,
http://wiki.cyanogenmod.com/wiki/Sa...te_Guide#Installing_the_ClockworkMod_Recovery mentions a "hardcore's kernel". What kind of kernel is that? Is it the actual system kernel used by the ROM one is installing afterwards or is it just some sort of boot kernel for the recovery application?
It also mentions hardcore's even though the kernel logo during booting refers to Semaphore.
Click to expand...
Click to collapse
All ROM's have kernels included in their package, without it your phone wont be able to boot..In this case Hardcore ( its actually a speedmod kernel, maybe tweaked by Hardcore) is being used to give you CWM recovery on Stock ROM's which do not have CWM recovery but only 2e recovery., after you flash CM, its removed and the new kernel from your update, is used
Instead of Odin, CWM recovery is used for ICS and JB installation
xsenman said:
All ROM's have kernels included in their package, without it your phone wont be able to boot..In this case Hardcore ( its actually a speedmod kernel, maybe tweaked by Hardcore) is being used to give you CWM recovery on Stock ROM's which do not have CWM recovery but only 2e recovery., after you flash CM, its removed and the new kernel from your update, is used
Instead of Odin, CWM recovery is used for ICS and JB installation
Click to expand...
Click to collapse
Thanks. I have to admit I am not really very familiar with the boot process, however I was under the assumption that CWM is just a replacement for the stock's basic boot/recover loader and both do not need an actual Android kernel as they both come before it in the boot order.
neroux said:
Thanks. I have to admit I am not really very familiar with the boot process, however I was under the assumption that CWM is just a replacement for the stock's basic boot/recover loader and both do not need an actual Android kernel as they both come before it in the boot order.
Click to expand...
Click to collapse
To make it simple.
Boot loaders are generally locked, hence needs to be rooted (unlocked), in oder to add CWM to it.
Custom kernels or kernels that are customized, do this function of rooting (unlocking the boot loader) as well as adding the CWM (customized recovery features) to the boot loader.
Only customized kernels will work with custom ROMS.
Hence when you flash a custom kernel on top of a stock ROM/with stock kernel, it is replaced and gives the added features (that stock kernel lacks) that is needed for flashing Custom ROMS
The reason being Gingerbread stock kernels will not work for ICS ROMs..hence must be replaced and this is vital for phones operations, since one main function of kernel is to control the hardware.
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Thanks to all who responded, if anyone else wants to reply feel free but i'm going to mark this as resolved so their won't be any confusion.
amd-dude said:
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Click to expand...
Click to collapse
if you are on stock kernel then download Philz kernel for LP7, flash that in recovery, should give you root again aswell. then you can flash away to any of the ROMs you listed above. just every time you flash a ROM or think of factory reset or data wiping make SURE you're on a SAFE kernel. that's all
as you are rooted, just install any safe kernel like hydracore or philz. thats all. then you can try out any rom. Just make sure you follow the instruction to flash the rom in the OP
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
amd-dude said:
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
Click to expand...
Click to collapse
this is the one you use - PhilZ-cwm6-UBLPC-UUB-2.7
http://www.mediafire.com/file/35d4kd...2.7-signed.zip
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
nokiamodeln91 said:
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
Click to expand...
Click to collapse
First, forget about the franco kernel. The franco kernel for the Note is outdated and thus useless. Second, if you plan to flash a JB leak the only kernel you should use is PhilZ. And especially important with the JB leaks is to stick exactly to the instructions how to flash. Otherwise your phone won't even boot.
Have fun with your device! The Note is still an outstanding phone.
Sent from my revived Galaxy Note
Thanks guys for the quick replies, i'm gonna flash the philz kernel now and give the leaked version of JB a try.
make nandroid backup 1st..
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!
I have been using Samsung for a long time and so this process seems weird. All we use to do there was just put the custom ROM and GAAPS and flash it via recovery and wipe phone. But when i was going through a lot of forums here..i see that the OP has asked people to flash the boot file using command prompt and then flash the ROM. Is this process really required even if we have the dual recovery installed?
If the updater script in the .zip does not have the correct commands to install the boot.img itself it has to be manually flashed.
Untill recently this was always the case, it was not possible to flash a kernel using recovery, it had to be done via fastboot.
I think this is probably a hangover from then, but now it can be done in recovery.
Also, if you have just unlocked, but do not have recovery installed the quickest way to get recovery is to flash the boot.img using fastboot, then flash the update.zip.
If you already have recovery, just flash the update.zip and the boot.img will be flashed.
This is only for roms int he original development section, as they require a custom kernel, roms in the development section will work on the stock kernel, so there is no need to flash a boot.img at all
Actually you need to flash different kernels for different roms... Like Stock-based(Sony) Roms can be either run on Stock Kernel(Sony) or Stock-Based Custom Kernel(like DooMKerneL). while AOSP Roms(like CM11) should be run on AOSP-based Custom Kernels(like Pimped Kernel).
You can flash custom Kernels only if you have unlocked your bootloader. if you have recovery on locked bootloader, then you can flash only Stock-based roms because they dont need a different kernel becoz they run on Sony Kernel itself. If you have a unlocked bootloader you can flash custom kernel, Then you can use both Stock-based Roms or AOSP-based Roms by flashing respective kernels.
If you already have Custom rom installed and changing to another Custom rom, Then if you are changing from (Stock-Based Rom to another Stock-Based Rom) or (AOSP-based Rom to another AOSP-based Rom) then you need not flash the kernel again, you can just wipe all partitions and install the new Custom rom over it. But if you are Cross flashing from (Stock-Based Rom to AOSP-Based Rom) or (AOSP-based Rom to Stock-based Rom), Then you should flash respective kernel, wipe partitions and install the rom over it.
if you dont know, whether the rom is Stock-based or AOSP-based, it will be mentioned in the OP of each Thread.Usually Roms that are available for a wide range of devices across OEMs are AOSP. Roms like CM, AOKP, PAC, Carbon, etc. are all AOSP roms.
Hope it helped.
So I'm still kind of a newb in this flashing thing and since I couldn't find anything using the search box here it go:
I an using Xceed custom kernel and now I want to try another one, but even after I flashed another custom ROM I noticed that Xceed still is my current kernel.
How do I safely change from one custom kernel to another? Do I have to flash stock MIUI again to return to stock kernel or is there an easier way? I ask because the last time I flashed the stock ROM I thought I had bricked the device.
Thanks in advance.
You shouldn't flash a custom kernel over another custom kernel. If you have made a backup of 'boot' in twrp, restore 'boot' only and then flash another kernel. If you haven't made a backup, then your only option is reflashing miui.