My apologies if this has been answered before -
1.) Should I flash a new kernel for my HOX? I am s-off, bootloader unlocked and running Viper XL 3.2.6.
2.) I know it is not absolutely necessary (flashing the kernel that is), but what are the advantages? what are the pitfalls should I be aware of?
3.) I am a relative noob so I don't think I'll be UV, OC or any of that cool stuff. So is stock better?
4.) Is there a thread out here where I can read about flashing kernels?
Thanks.
1:NO
2:None [edit] unless you flash aosp to sense kernel, visa versa.
3:matters of opinion
4:how did you achieve s-off and not know how to flash stuff?
Sent from my HOX w/CM10.1 4.2.2 s-off
Haha.. i know how to flash stuff.. it is just about the kernels.. and i wanted to read about kernels and such. not how to flash them..
thanks for the answers though
Flashing kernels is just like flashing anything else: Have a backup, clear cache/dalvik, and flash away.
The only thing to be aware of is that Sense roms need a Sense kernel, and AOSP roms need an AOSP kernel, and never the twain shall meet.
S-off removed the need to flash in fastboot that exists with 2.20 and later bases. The only reason to flash one now is because you want features in a custom kernel.
Custom kernels are "better" in the sense that you can do more with your phone, but they usually not as stable as stock, depending on how hard you push them.
Since I am not going to UV, OC etc, I guess it is better to stick with stock.
Thanks Elvis
sriramll said:
Since I am not going to UV, OC etc, I guess it is better to stick with stock.
Thanks Elvis
Click to expand...
Click to collapse
Keep in mind stability has as much to do with your phone as what kernel you pick. Some phones can't take overclocking or undervolting at all without losing stability; others (like mine) can run flat out without any problems. Only way to find out is to try it.
I'd definitely recommend looking into the ElementalX kernel. For me, it's increased my battery tremendously and it's also been a good bit smoother.
is there a way to go back to stock kernel? I guess flashing the rom again?
sriramll said:
is there a way to go back to stock kernel? I guess flashing the rom again?
Click to expand...
Click to collapse
You can extract the boot.img from the rom you flashed and flash that. This will be the stock kernel from that particular rom.
If you're using Viper, there's an option for flashing stock kernel within the viper installer so no need to worry about extracting or reflashing the whole rom.
Related
im flashing my g2x with a kernal and a rom so which do i do first, kernal or rom? or dose it matter?
1. ROM.
2. Compatible kernel.
If you do it the other way around you might not be able to boot the phone.
It's doubtful that you'd be unable to boot, more likely your custom kernel would be overwritten by the ROM's default and you'd have just wasted your time flashing the kernel.
But yeah, ROM first then kernel.
LordButtersI said:
It's doubtful that you'd be unable to boot, more likely your custom kernel would be overwritten by the ROM's default and you'd have just wasted your time flashing the kernel.
But yeah, ROM first then kernel.
Click to expand...
Click to collapse
well now my phone is way faster and smoother and stable
Well, I'm a complete noob and I'm a bit confused. Consider this:
I flash the phone with CM7(say). Here I'm assuming that CyanogenMod comes with its own kernel. My question is: Can I flash a custom kernel on top of this setup? and what difference does it make?
One can also think the other way round. I have flashed my phone with a custom kernel. Successively I flash CM7 on to my phone. What happens then? Is the original custom kernel wiped out to be over-written by CM7 kernel? What can be done to keep it intact? Please people solve this dilemma...
saurabh.khare1000 said:
Well, I'm a complete noob and I'm a bit confused. Consider this:
I flash the phone with CM7(say). Here I'm assuming that CyanogenMod comes with its own kernel. My question is: Can I flash a custom kernel on top of this setup? and what difference does it make?
One can also think the other way round. I have flashed my phone with a custom kernel. Successively I flash CM7 on to my phone. What happens then? Is the original custom kernel wiped out to be over-written by CM7 kernel? What can be done to keep it intact? Please people solve this dilemma...
Click to expand...
Click to collapse
If you wipe your data and system partitions on your phone and then flash a ROM you'll end up having that ROM's kernel.
Anytime you can flash another kernel over the default one. You might get some
advantages, but that depends on kernel's specifications. It might get you able to
increase more the frequency of your phone's CPU. There isn't necessarily an
advantage in flashing another kernel. ROM developers usually use to provide
the most stable kernel for their rom.
So coming from dx we had no kernels to worry about. Now, my questions are.
Say I flash to a rom that now has a kernel that's flashed with the rom. And I make a backup before I flash. After being on that rom with a kernel, can I restore the backup and it restores the stock kernel that the backup was running on?
It seems I've read some people coming from cm10 trying to restore to a tw rom and it not booting, thoughts have been because of the cm10 kernel it was
the on?
If I need to flash kernels before restoring backups where do I get stock kernel and what's the proper way to get to a working backup once kernels are involved?
I hope I'm not to confusing here.
Sent from my Synergized vzw S3!
silver04v said:
So coming from dx we had no kernels to worry about. Now, my questions are.
Say I flash to a rom that now has a kernel that's flashed with the rom. And I make a backup before I flash. After being on that rom with a kernel, can I restore the backup and it restores the stock kernel that the backup was running on?
It seems I've read some people coming from cm10 trying to restore to a tw rom and it not booting, thoughts have been because of the cm10 kernel it was
the on?
If I need to flash kernels before restoring backups where do I get stock kernel and what's the proper way to get to a working backup once kernels are involved?
I hope I'm not to confusing here.
Sent from my Synergized vzw S3!
Click to expand...
Click to collapse
im not sure but I think things are a bit different now with the unlocked bootloader. there was a lot of problems between kexec and switching between TW and CM10.
I think that any restore will get you back just fine as it flashes everything back including kernel. just be REALLY careful what CWM you are on. its just safer overall to stick with 6.0.1.0 as it works with every rom.
i have no idea if its on XDA but you can find imoseyon and stock kernel on rootzwiki.com
xicewallx said:
im not sure but I think things are a bit different now with the unlocked bootloader. there was a lot of problems between kexec and switching between TW and CM10.
I think that any restore will get you back just fine as it flashes everything back including kernel. just be REALLY careful what CWM you are on. its just safer overall to stick with 6.0.1.0 as it works with every rom.
i have no idea if its on XDA but you can find imoseyon and stock kernel on rootzwiki.com
Click to expand...
Click to collapse
That helps a little. I know with being unlocked any recovery should work. Twrp has been good to me so far, I'm going to try and stick with it.
Sent from my Synergized vzw S3!
Nobody else is used to flashing with kernels and can give a little input?
Sent from my Synergized vzw S3!
Yes there were issues going from kexec to no kexec...I have tried almost all the ROMs out since the unlocked bootloader and not had any issues with this I have also been using a Sprint kernel and not having any issues...just make sure that you flash aosp kernels if you're using aosp and tw kernels if using a tw ROM...and personally I use TWRP and have never had any issues at all...if using TWRP just pay attention to what you're wiping because you have lots of options there
Delete
1. Unlock your bootloader first. Skip anything that says for k-exec.
2. Use latest CWM.
3. Make sure that any Kernel you use is designed for your type of ROM. JB-AOSP Kernels for JB-AOSP ROMs, ICS-TW for ICS-TW ROMs, etc. Again, make sure it is non-kexec.
4. Always wipe cache and dalvik cache when switching kernels to be sure your dalvik is rebuilt by the new kernel.
If these steps are followed you should be golden. Happy flashing!
Sent from my SCH-I535 using Tapatalk 2
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Fulvio93 said:
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Click to expand...
Click to collapse
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
rzr86 said:
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
Click to expand...
Click to collapse
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Fulvio93 said:
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Click to expand...
Click to collapse
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
android1234567 said:
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
Click to expand...
Click to collapse
Yeah well, I was looking at the title of that kernel thread while I realized which was the problem, I'm glad to tell you that I flashed your kernel last night (I'm Italian) and after a whole day using it I have to say that I really like it (even if I've to settle with all the differences between the governors and the best way to set them with aroma).
Thank you!
Are there any negatives to flashing a custom kernel? I want to put the knock feature on my N5 and from what I understand it requires a custom kernel. Can I just flash it or do I have to wipe my data? Thanks.
Just flash it in recovery. Wipe is not needed. If you are worried you could make back up first. Stock kernel is also available aroud the forum.
However if you are talking about the knock which wakes up tje screen, it is very power consuming in my exp...
Sent from my Nexus 5 using Tapatalk
Not really any downside. I mean technically the custom kernels on here are experimental and they're always being updated, so you might run into bugs here and there, but if you can always reflash the stock kernel if you're unsatisfied with a custom kernel.