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.
Related
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!
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!
My device is GT-N7000, using N7000ZSLR1 Android 4.1.2 stock ROM （Build number：JZO54K.N7000ZSLR1）, used Chinese one key root app to root but unrooted to go to stock recovery to flash the newest Philz recovery (because Odin v3.09 failed to flash it), but fail like below screenshots:
I wonder why, I downloaded from the official platform (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/), and my internet is good so there should be no corrupted files. All stuffs are stock now, so I dunno why.
(Additional info: If I flash "PhilZ-cwm6-XXLTA-ATL-5.15.0.tar.md5" using Odin, it works, but I want to use the latest Philz recovery, plus, the recovery will switch back to stock one after usage, that means after I press "reboot system now" in Philz recovery XXLTA-ATL-5.15.0, and power off and go to recovery mode again, it's the stock one. Dot't say something like "Oh flash this one then").
If you are on a stock 4.1.2 rom there is no way you can update to a newer recovery using philz. As he stopped updating the old kernels. You may try some other custom kernel.
The advanced Cwm edition will not work using odin or recovery. So leave that alone.
The XXLTA you flashed is a right path but it should not revert to stock recovery. There is zip version of that file. Flash it through the stock recovery.
nokiamodeln91 said:
If you are on a stock 4.1.2 rom there is no way you can update to a newer recovery using philz. As he stopped updating the old kernels. You may try some other custom kernel.
The advanced Cwm edition will not work using odin or recovery. So leave that alone.
The XXLTA you flashed is a right path but it should not revert to stock recovery. There is zip version of that file. Flash it through the stock recovery.
Click to expand...
Click to collapse
Which custom kernal you recommend, and is stable then?
And which 'Old" Philz kernal is the "newest" to my ROM? I mean the newest in the old kernal, if you get what I mean.
Vulturon said:
Which custom kernal you recommend, and is stable then?
And which 'Old" Philz kernal is the "newest" to my ROM? I mean the newest in the old kernal, if you get what I mean.
Click to expand...
Click to collapse
The XXLTA you flashed seems to be the latest from Philz list of recoveries for TW 4.1.2 kernels for now.. You may check forest's kernel.. I think it has an updated recovery.
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
I need to flash Tangerine Kernel Or DooMLoRD Kernal.. one time i test. but my all data erased. i want flash one of kernal without data losing.. Please Can you Help Me ?
Stock 12.1.A.1.205
JellyBean 4.3
C5303
KoRTaN said:
I need to flash Tangerine Kernel Or DooMLoRD Kernal.. one time i test. but my all data erased. i want flash one of kernal without data losing.. Please Can you Help Me ?
Stock 12.1.A.1.205
JellyBean 4.3
C5303
Click to expand...
Click to collapse
Tangerine only works for Lollipop roms so don't even try it or you be stuck in a bootloop, Doom kernel I think it's too old, try Williams Kernel 9.1, best one for 4.3 roms. Did you unlock your bootloader?
HUEguy said:
Tangerine only works for Lollipop roms so don't even try it or you be stuck in a bootloop, Doom kernel I think it's too old, try Williams Kernel 9.1, best one for 4.3 roms. Did you unlock your bootloader?
Click to expand...
Click to collapse
Stock 12.1.A.1.205 / C5303 / JellyBean 4.3 / Bootloader Unlocked / Rooted
Can I Flash Williams Kernel 9.1 Without Any data losing (auto wipe data\chache) or bootloop error ??
KoRTaN said:
Stock 12.1.A.1.205 / C5303 / JellyBean 4.3 / Bootloader Unlocked / Rooted
Can I Flash Williams Kernel 9.1 Without Any data losing (auto wipe data\chache) or bootloop error ??
Click to expand...
Click to collapse
Flashing a kernel doesn't auto wipe data. Since you're completely stock right now, I am guessing you'll be flashing the kernel via fastboot so you should be fine. As for boot loop errors, the kernel's meant for stock based roms so it shouldn't be a problem. I remember using it with Existenz. Worse case scenario, you'll have to reflash the kernel part from the stock firmware with Flashtool if things go wrong. Alternatively you could take a backup of your kernel via Rashr since you're already rooted.
Speaking of Rashr, you could use it to flash a recovery in your Fota partition which doesn't go away unless and until you remove it using stock firmware. This means that no matter which kernel or rom you flash, you'll always have a working recovery to get yourself out of trouble. You can take a complete nandroid backup of your system before even trying Williams kernel and in the off chance your phone is stuck in a bootloop, you can just restore your nandroid backup and you'll be back to stock.
If you're still worried about your data, just get Titanium backup and make a backup before you proceed. I have switched over a dozen roms in the past few months only because of it. Imagine setting up 30-40 apps every time you migrate to a different rom
XenolithicYardZone said:
Flashing a kernel doesn't auto wipe data. Since you're completely stock right now, I am guessing you'll be flashing the kernel via fastboot so you should be fine. As for boot loop errors, the kernel's meant for stock based roms so it shouldn't be a problem. I remember using it with Existenz. Worse case scenario, you'll have to reflash the kernel part from the stock firmware with Flashtool if things go wrong. Alternatively you could take a backup of your kernel via Rashr since you're already rooted.
Speaking of Rashr, you could use it to flash a recovery in your Fota partition which doesn't go away unless and until you remove it using stock firmware. This means that no matter which kernel or rom you flash, you'll always have a working recovery to get yourself out of trouble. You can take a complete nandroid backup of your system before even trying Williams kernel and in the off chance your phone is stuck in a bootloop, you can just restore your nandroid backup and you'll be back to stock.
If you're still worried about your data, just get Titanium backup and make a backup before you proceed. I have switched over a dozen roms in the past few months only because of it. Imagine setting up 30-40 apps every time you migrate to a different rom
Click to expand...
Click to collapse
Thanks For Details And i need to know, How to flash recovery & kernal ?
Kernal Can speedup my XSP ?
KoRTaN said:
Thanks For Details And i need to know, How to flash recovery & kernal ?
Kernal Can speedup my XSP ?
Click to expand...
Click to collapse
If I am not mistaken, SP like most older Xperia phones (not sure about the new ones) does not have a stock recovery nor does it have a recovery partition. The recovery is part of the kernel (the boot.img file or the .elf file). So when you flash a kernel, you are flashing the recovery along with it. This is why people flash a recovery in the Fota kernel partition since its a separate partition and is not overwritten while flashing other roms or kernels. A recovery flashed in the fota partition becomes your primary and only visible recovery irrespective of how many recoveries came bundled with the kernel you flashed. The only way to remove it is by flashing stock firmware or to be more specific, the fota kernel from the stock firmware. If you need it, you can find it here :
http://forum.xda-developers.com/showpost.php?p=59908442
Now since your phone's already unlocked and rooted, go grab Rashr from the playstore and use it to flash the latest Twrp from here :
http://forum.xda-developers.com/showpost.php?p=61698751
This way you will have a permanent recovery which you can use to take a nandroid backup before you try new roms or kernels and restore it if things go wrong.
Your other option is to flash the kernel via fastboot but remember if you flash another rom, the existing kernel will be overwritten by the kernel that came with the rom. It becomes really cumbersome when you are trying different roms. Another reason to flash a recovery in the Fota partition.
As for a new kernel speeding things up, yeah it helps. The first link is also the main thread for Tangerine kernel which has CPU overclocking and governor options and a bunch of other tweaks to improve performance but its only for LP roms. If you wanna stay stock, you can try the Williams kernel. Doesn't have as many features as the Tangerine kernel but more than the stock kernel. If you know which tweaks to make, I am sure you can gain a performance boost from either.