I am currently on CM10 Nightlies 11/01 with Imoseyon LK Kernal.
I was just wondering, if I update the nightly build, will the stock CM10 kernal be written, or will I retain the LK kernal.
If it does get over written, then that would mean each time my update process would be:
wipe cache/dalvik > flash CM10 > flash LK Kernal
Thanks!
Every time when you flash a new nightly, you'll have to reflash leankernel, as it gets overwritten.
MildSe7en said:
I am currently on CM10 Nightlies 11/01 with Imoseyon LK Kernal.
I was just wondering, if I update the nightly build, will the stock CM10 kernal be written, or will I retain the LK kernal.
If it does get over written, then that would mean each time my update process would be:
wipe cache/dalvik > flash CM10 > flash LK Kernal
Thanks!
Click to expand...
Click to collapse
That is the correct method, sometimes its best to stay on the integrated kernel and other times its best to do a clean install to lower chance for error.
Related
So, there is Haus's thread which provides download links to the ROM, Kernel and Radios.
I am currently running Salvage Mod and a Tiamat kernel.
If I flash the 2.3 OTA ROM while still running the Tiamat kernel, will I run into issues?
Mindspin_311 said:
So, there is Haus's thread which provides download links to the ROM, Kernel and Radios.
I am currently running Salvage Mod and a Tiamat kernel.
If I flash the 2.3 OTA ROM while still running the Tiamat kernel, will I run into issues?
Click to expand...
Click to collapse
No because after you flash you will no longer be running the Tiamat kernel you will be running the new stock HTC kernel. Flashing the ROM flashes the kernel as well.
zone23 said:
No because after you flash you will no longer be running the Tiamat kernel you will be running the new stock HTC kernel. Flashing the ROM flashes the kernel as well.
Click to expand...
Click to collapse
Oh...
I was under the impression (based off the links provided in the other thread) that the ROM and kernel needed to be flashed separately.
Thanks for clarifying!!
Mindspin_311 said:
Oh...
I was under the impression (based off the links provided in the other thread) that the ROM and kernel needed to be flashed separately.
Thanks for clarifying!!
Click to expand...
Click to collapse
Generally no I flashed it on my EVO and didn't flash any thing else. You might want to go back and take another look I will as well but that generally not the case they come with the kernel.
To flash back to sense you don't have to do anything special. You don't have to nandroid back to sense or anything like that. The only thing you have to do is clear user data, cache, and dalvik cache then flash. You don't need to restore anything first. I saw your other post. Also I'm fairly positive that the ROM has the kernel but if you want to be safe download the kernel as well and just stick it on your storage card just in case.
Remember clearing user data will wipe all of your apps and data.
The kernel is a modified one just incase you have the brightness bug still I think.
When I flashed the new mikg v1.0 i know I still did but I flashed that kernel and it fixed it but I never flashed one of the new stock ROMs cause of the 1.0 sense on it.
Sent from my PC36100 using XDA App
I'm on Caulk's 2.9. but, naturally I have the ICS itch. Reading up on install steps, I should be installing Rogue kernel/recovery -> CM9 -> Gapps. The question is though, if I'm following the steps in Rogue install, when I get to the steps to update profile and PRL, is it going to bork because I'm still on Caulk's rom?
Actually, it looks like the CM9 specific recovery download only includes the recovery. This should be fine.
Nix that, the recovery looks for a build prop version 4.0.3,0 so that's out. I tried flashing the ROM, but that too is giving me build prop prop issues. Fuuuu. Any ideas?
I'm on rogue 1.1.2 which I've flashed cm7 with
Sent from my SPH-D710 using xda premium
you need a stock recovery on your phone first to properly flash cm9
either download miui or cm7, reboot, then go to recovery and follow the directions on installing it
you can't install it properly with a custom recovery at this point, or, at least, no one has reported that they are able to
So Kernel > Rom > Gapps > Factory Reset (For calendar sync) > reboot all good?+
If I odin the kernel, its goes on PDA right?
Doncabezon said:
So Kernel > Rom > Gapps > Factory Reset (For calendar sync) > reboot all good?+
If I odin the kernel, its goes on PDA right?
Click to expand...
Click to collapse
Yes you should be good after those steps.
Sent from my SPH-D710 using xda premium
NOT true...
you flash the rom and gaps only FIRST..
make sure everything works, then add a custom kernel...
and, make sure you are on a stock cm type kernel when you flash it, like what you get from MIUI or cm7, or it won't work
wase4711 said:
NOT true...
you flash the rom and gaps only FIRST..
make sure everything works, then add a custom kernel...
and, make sure you are on a stock cm type kernel when you flash it, like what you get from MIUI or cm7, or it won't work
Click to expand...
Click to collapse
C9 3.1 doesn't give clockwork so odin. The kernel goes on pda like the roms right?
I don't use Odin, I have OSX at home, so I use heimdall, and I don't want to give you bad info on Odin..there are lots of posts here about that though, so it will be easy to confirm for you
But, the bottom line is, you need to come from CM7 or MIUI first, then flash cm9/gaaps, wipe data, reboot
once you are sure everything works properly, then you can odin the 1.2.1C kernel..
wase4711 said:
I don't use Odin, I have OSX at home, so I use heimdall, and I don't want to give you bad info on Odin..there are lots of posts here about that though, so it will be easy to confirm for you
But, the bottom line is, you need to come from CM7 or MIUI first, then flash cm9/gaaps, wipe data, reboot
once you are sure everything works properly, then you can odin the 1.2.1C kernel..
Click to expand...
Click to collapse
Thanks. I had CM9 installed but never flashed a new kernel on CM9 so I am being as careful as possible
i know you can do it easily in Odin, but I don't want to give you bad info..
its nice to have a custom recovery with cm9!
I flashed KT747 a two or three days ago. I just noticed that I am back to the stock kernel. I didn't flash back to stock kernel. The only thing I can think of is that I tried flashing the 10.1 12/10 preview build but CWM aborted right away due to bad download. So nothing should have been flashed. I have also made two nandroid backups since flashing KT747.
I didn't notice any big difference between stock kernel and KT747. I'm not sure if I'll relfash or not. I really just want to know what the heck happened
Turns out flashing nighties also flashes back to CM kernel.
cavolt said:
Turns out flashing nighties also flashes back to CM kernel.
Click to expand...
Click to collapse
Yes, flashing any ROM will over-write the kernel
Hi everyone,
I wasn't used to consider myself a too-much-noob anymore, but now I've plenty of doubts.
So, here's my problem: I've decided to give the latest ParanoidAndroid release a try and my maguro was "oem locked". Then, I've run the command "fastboot oem unlock" and copied all files I needed (PA rom, GlaDos v2.2 and latest GApps) into my /sdcard folder (usual job). I've rebooted into recovery (latest touch CWM), formatted /system, /data, /cache (usual full wipe), searched for the files and flashed them.
When it was time to reboot, the phone got stuck at the first screen (black, with the white "Google" and the white opened padlock). In other words, the bootanimation didn't even start.
Then, I've re-downloaded the stuff, double-checked all Md5 sums, re-copied everything in the sdcard but the result didn't change.
I've tried to re-flash the stock unrooted rom, then repeating the steps without formatting /system. I've also tried to not flash the kernel. No way the rom could even boot.
Now I'm seriously wondering what's wrong with what I've done . For completeness, my bootloader version is LC03 and the radio is XXLJ1 (same as the fully stock android bundle that can be found here)
I've also checked (maybe too much quickly, I may admit) the threads for PA and GlaDos, but I haven't seen anyone complaining about the same problem...
Could you guys please help me?
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
- Based on stock Android kernel Jelly Bean 4.1.1 JRO03C
Click to expand...
Click to collapse
Pirateghost said:
First of all....
all you need to do to wipe is select
FACTORY RESET in custom recovery
Secondly:
GlaDos 2.2 is probably not going to work with PA3.0
Click to expand...
Click to collapse
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Endriu90 said:
Thank you for the reply, but i've also tried the factory reset you mean (no results) and, for GlaDos, my bad, I've linked an XDA thread instead of the "original" updated thread on rootzwiki
Click to expand...
Click to collapse
i have been looking forward to a new GladOS...thanks for the link
in recovery, all you have to do is factory reset then flash the rom. thats it
EDIT:
which version of PA 3.0 are you trying to install
Pirateghost said:
which version of PA 3.0 are you trying to install
Click to expand...
Click to collapse
I've tried with all releases which can be found here
Flash Kernel too
Hi,
When the new PA version was uploaded (20 Feb), this was the warning posted by the developer:
WARNING
As I didn't have so much time, I couldn't make it booting with default kernel (Need to update prebuilt kernel). So if you're gonna use it BE SURE YOU FLASH A CUSTOM 4.2.2 KERNEL!
Click to expand...
Click to collapse
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Hope this helps.
Regards,
Neeraj
neerajvd said:
So I recommend you download any latest 4.2.2 kernel (AK kernel or franco) and flash it alongwith the ROM.
Click to expand...
Click to collapse
Thank you guys, I've solved (I've tried just with the factory reset as said by pirateghost, but I was used to format /system, /data and /cache when it was time to flash roms like AOKP and everything used to work properly) (I was used to do the same with the Nexus S).
Now I'm running the 15feb release with the stock android kernel (which comes with the stock 4.2.2 factory bundle) and everything just works as expected.
Anyway, I still can't get the reason why GlaDOS shouldn't work with the 20feb release. I mean, it's a custom kernel and it should work as well as AK or franco kernels, shouldn't it? If I'm wrong, could you briefly tell me why? (sorry, I won't move to other kernels, as I personally love GlaDOS and it provides my GNex with the optimal equilibrium performances/battery life)
EDIT:
alongside the 15feb release, I've tried to flash GlaDOS (just factory-resetting before flashing), but nothing boots. Restored the backup, now I'm still running PA with the stock kernel
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Il_Tene said:
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Click to expand...
Click to collapse
Try using AK's kernel revert (back to stock kernel.)
It works for some people and for others, it doesn't though. I also had reboot problems with AK so I don't use it anymore, and also it sucks that I had to revert to stock when it happens. Hope it works for you, goodluck man.
4.2.2 - http://d-h.st/R7y
4.2.1 - http://d-h.st/2w6
From AK's thread
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Il_Tene said:
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Click to expand...
Click to collapse
Yes. The kernel id's overwritten whenever you flash a rom.
Sent from my Nexus 7 using Tapatalk HD