Which one should you use?
What are the benefits?
Security concerns?
Can I install a kernel without reflashing OS?
Used my T now for some days rooted with supersu and using xposed, but would like to tweak the performance and battery life some more.
Cheers.
Kernels tend to work differently depending on your individual setup. I recommend trying each one you like for a week so it can settle in. Flash in twrp and wipe only the caches. Your OS will be fine.
In terms of security I would use kernels that are frequently updated and maybe are always upstream synced. I would dirty flash the OS or the stock kernel at least before changing custom kernels as they tend to have unknown bugs when dirty flashing custom kernel over custom kernel.
The benefits are that you can choose whether to limit performance for more battery life or to go beast mode with full power but by sacrificing battery life. It simply gives you more advanced control over it.
Thanks for the replies!
Installed Blue_spark kernel and tweaked the clockspeed some. Works like a charm, I guess OTA updates are out of question?
Would agree mostly with the above. But I tried dirty flashing FreedomOS Rom once, and that was a bootloop. Dirty flashing with OnePlus isn't like HTC 10/11 Roms/Devs. They always work no issues when dirty flashing.
You could always flash the stock boot.img in TWRP, Select flash Image, select the boot.img, and the boot partition to flash. You will lose root though. So you need to install Magisk, have that handy as well. And, then try another Kernel.
Related
Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.
PeterGunz said:
Is there a normal procedure people follow when flashing new kernels on JB in order to ensure they are removing any scripts or tweaks left behind by previous custom kernels?
On ICS, I used to wipe cache/dalvik and flash faux's reset kernel just to be sure, but faux hasn't released a kernel like that for JB yet.
I understand the faux reset kernel replaces the boot.img(?) but I was just curious if there is standard procedure most people follow to make sure new kernel flashes are starting from scratch.
Click to expand...
Click to collapse
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.
crazybone21 said:
bro, most of the time, i just follow the authors instruction on how to install the kernel. i don't do wipes when installing kernel ever since gingerbread and i never encountered any problem.
Click to expand...
Click to collapse
Thanks. I noticed some people having trouble with scripts sticking around after flashing new kernels, so I was just double checking,
Hi all,
Since installing cwm a week ago i started experimenting with different kernels and mods. However i noticed that my phone is somehow rejecting some mods/kernels. I run stock jb yakju image with cwm 6.1.1.0 and at the moment fugumod kernel 505 stable. I succeeded at running Franco and trinity 1420-535 previously but that's about it. Airkernel, tuna kernel, even the same version of trinity but with lower clock speeds was rejected. I always get a Google splash screen bootloop. Only way to get rid of it is flash another kernel over it or restore a nandroid. I always wipe the cache and the dalvik cache prior to install. Is there a way to make my phone accept that kernels? And is it my phone fault out the kernels. I'm using a gsm international version.
Thanks in advance!
Sent from my Galaxy Nexus using xda app-developers app
dont wipe anything when flashing kernels.. not your cache, nor your dalvik. if it wont pass the splash screen, i suggest that you reflash your rom and the kernel together then try to boot. sometimes if its not booting, taking your battery out for a minute then putting it back in and booting up works. also, sometimes you have to be a little more patient, giving it more time to boot. if you are flashing any kernel after flashing franco kernel, you have to flash your rom with the next kernel(for the first flash), because franco kernel uses its own ramdisk. most other kernels use anykernel which grabs the available ramdisk, you want it to grab your roms ramdisk. thats where franco kernel keeps franco kernel tweaks which would interfere with other kernels.
I indeed started with the franco kernel. So you are basically telling me that next time i should wipe nothing, reflash my Rom, then reflash my kernel hand reboot. But how do i flash a stock Rom? Is the Google image flashable? And do i get to keep all my stuff etc on my device?
Sent from my Galaxy Nexus using xda app-developers app
tobitronics said:
I indeed started with the franco kernel. So you are basically telling me that next time i should wipe nothing, reflash my Rom, then reflash my kernel hand reboot. But how do i flash a stock Rom? Is the Google image flashable? And do i get to keep all my stuff etc on my device?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
there are a few stock plus root roms floating around, you can flash those over stock. yea, im telling you to wipe nothing. wiping cach/dalvik is like buying your child a swing set when preparing to fill your cars gas tank up. they have nothing to do with each other. btw, thats only with frano kernel, all the other kernels you can just flash on top of each otger and not worry about it. none of your stuff will get lost unless you wipe data/factory reset, and theres no need for that.
maybe that explains why trinity gave me battery drain after installing it after franco?
and to respond to OP no phone is built the same. Your phone won't accept EVERY kernel. Its just something you have to accept (from my experience)
For example every android phone i've owned has reacted poorly to undervolting but for those kernel devs who do it don't have a problem with it. U never know how your phone might react
I have a GSM Galaxy Nexus and I am currently using 4.2.2 Cyanogen Mod released in April 2013.
It has the following Kernel
3.0.31-cyanogenmod-g64e9296
I have flashed ROMs many times mostly CM ROMS.
I want to try changing kernel to improve battery life and check what kernel changes actually is all about.
Since I havent done it earlier, I want answers to following questions:
1) Is it safe to change my kernel to another one? I want to install http://forum.xda-developers.com/showthread.php?t=2115590 or maybe someone can tell me a better one with focus on improved battery life.
2) What if the above kernel screws up? can I recover the old kernel back?
3) Is kernel flashing Permanent or any ROM I flash will have it's own kernel?
4) Just in case my kernel screws up, I have a full TWRP backup as well, would flashing that change my current kernel to old one that came with cyanogenmod last ROM?
Thanks.
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
jsgraphicart said:
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
Click to expand...
Click to collapse
Advanced restore should work, no need to restore the whole thing, just system.img and boot.img should do the trick.
Sent from my Nexus
Hi,
I am considering to flash ElementalX kernel and CleanRom on my stock nexus 7 2013 wifi. Is it correct if the steps I take are:
1. Rooted with Toolkit (i. unlock bootloader and ii. root?)
2. Flash CleanRom
3. Flash Stock kernel (is this step necessary?)
4. Flash ElementalX
Please let me know if there are other steps or things that I need to be aware. Thanks!
For step one you have to unlock boot loader in order to root. You also need to flash a custom recovery such as twrp or clockworkmod.
Also step 3 is unnecessary. After you flash cleanrom, you should just flash ElememtalX. Have fun
Sent from my Nexus 7
The toolkit will do it for you, I recommend TWRP recovery.
After that just flash the kernel.
Remember always to follow instructions.
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
That means you're flashing the incorrect version of the kernel, from now on if you are flashing a rom see if its CAF-based or AOSP-based, for example CM is CAF-based, so you'll need to flash the correct version of the kernel, look in the kernel threads for the CAF kernel download, I know that Glitch and ElementalX have kernel compatible for CAF -based roms
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
ElementalX kernels newest build is 4.4.2 not 4.4.1 and also a good tip stated above to see if you need a CAF of AOSP kernel.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Thanks for the advice, i'll try to flash it again when i'm back home. Cheers guys!
I haven't even booted the device yet, but would like to make slight modifications.
I have to stay "stock" / non-root because of apps I use for work, but can do roms & kernels.
I intend on booting up, installing Pie / latest updates, etc....
I want to use AOSPex & ElementalX right off the batt.
So should I:.
1. Flash AOSPex & set everything up, then flash ElementalX afterwards?
Or.
2. Flash AOSPex + ElementalX together at boot?
Ph0z3 said:
I haven't even booted the device yet, but would like to make slight modifications.
I have to stay "stock" / non-root because of apps I use for work, but can do roms & kernels.
I intend on booting up, installing Pie / latest updates, etc....
I want to use AOSPex & ElementalX right off the batt.
So should I:.
1. Flash AOSPex & set everything up, then flash ElementalX afterwards?
Or.
2. Flash AOSPex + ElementalX together at boot?
Click to expand...
Click to collapse
Shouldn't be a problem flashing kernel straight after the rom and before first boot. Though worst case scenario just reflash the rom zip, boot to system, reboot to recovery then flash the kernel
cd993 said:
Shouldn't be a problem flashing kernel straight after the rom and before first boot. Though worst case scenario just reflash the rom zip, boot to system, reboot to recovery then flash the kernel
Click to expand...
Click to collapse
Right on. Thank you.