I know this is a little indulgent but, does anyone know of a fast (optimized) rom with netarchy kernel and OC built in? I am very busy so if anyone knows the answer that would be great. If not, no problem, i'll look when I have free time. TIA
flash kush roms in teamwin recovery, without reboot flash, flash netarchys kernel.
thats what i'm using.
2fastkuztoms said:
flash kush roms in teamwin recovery, without reboot flash, flash netarchys kernel.
thats what i'm using.
Click to expand...
Click to collapse
Seems like netarchy's allows OC in every ROM. THat's awesome
I am using it on SupraRom with netarchy kernal...Love it
http://forum.xda-developers.com/showthread.php?t=1194137
Related
Ok, i need some help out here.
I flashed francos .35 kernel along with andy's ROM on my friends phone..and the following don't seem to work-
Bluetooth
Accelerometer
Wifi
Tethering
Before u ask any questions..Lemme tell you what i did-
Recovery
Complete wipe (system,data,factory reset,cache,dalvik)
Installed andy's rom
reboot
back to recovery
Wiped cache partition+dalvik cache
flashed kernel 2.6.35.14
reboot
Baam !.. and nothing works.
I kindly ask for possible solutions and screwups on my behalf.
Thank you.
Rutuj said:
Ok, i need some help out here.
I flashed francos .35 kernel along with andy's ROM on my friends phone..and the following don't seem to work-
Bluetooth
Accelerometer
Wifi
Tethering
Before u ask any questions..Lemme tell you what i did-
Recovery
Complete wipe (system,data,factory reset,cache,dalvik)
Installed andy's rom
reboot
back to recovery
flashed kernel 2.6.35.14
reboot
Baam !.. and nothing works.
I kindly ask for possible solutions and screwups on my behalf.
Thank you.
Click to expand...
Click to collapse
Ammmm I think....wipe dalvik before flashing krnel?
Did that too..
Typo
Rutuj said:
Did that too..
Typo
Click to expand...
Click to collapse
why dont you try a .32 and see if it has same effects?
or give a try to goldleaf's kernel
well yes!
.32 works but i wanted .35
Tried flashing .35, 3 times but to no effect.
Even goldeneaf has the same problems.
.32 kernels are more stable. That's why most ROMs still use .32.
why would you flash franco's kernel, since andy said that kernel is already installed in his rom? Just reflash the rom and all should work, franco didn't add any modifications since 02.10... And don't flash a .32 kernel on a .35 rom, that will just mess up your phone.
cr157y said:
why would you flash franco's kernel, since andy said that kernel is already installed in his rom? Just reflash the rom and all should work, franco didn't add any modifications since 02.10... And don't flash a .32 kernel on a .35 rom, that will just mess up your phone.
Click to expand...
Click to collapse
Well, the .35 works on everyone else's ROM.
And the default kernel is .32, however im not that satisfied with its performance so I wanted a switch
@Moderator
Please close/delete this thread, the problem has been solved.
Thanks.
Rutuj said:
@Moderator
Please close/delete this thread, the problem has been solved.
Thanks.
Click to expand...
Click to collapse
Send him a pm.
Sent from my LG-P500 using xda premium
Does anyone know how to change the boo
t animation on this rom. Help please
You need a kernel that supports custom boots. Comradesven's kgb kernel should do the trick.
mezster said:
You need a kernel that supports custom boots. Comradesven's kgb kernel should do the trick.
Click to expand...
Click to collapse
GeeWiz kernel will also work. I'm running it with Superclean and am seeing the TSM bootscreen.
thank you everyone for the help, i am running kgb 11/27 kernel. but i figured out how to do it.
I am on the 8-31-12 nightly build for CM10 and I want to flash a Evilz Kernel. Any idea how i am suppose to do this. Am i just suppose to flash through recovery, or do i need to do something special?
krobinso2295 said:
I am on the 8-31-12 nightly build for CM10 and I want to flash a Evilz Kernel. Any idea how i am suppose to do this. Am i just suppose to flash through recovery, or do i need to do something special?
Click to expand...
Click to collapse
You dont. Evil is a sense kernel.
But this is how you install kernels if you are on H-boot 1.15 or above:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
I'm S-Off TWRP 2.2.2 If I Flash EvilZ's kernel on Viper4g 2.0 can I use Viper Control to go back to the stock kernel or do I need to nand back or something similar?
You're s off, just flash stock kernel
Sent from my EVO using xda premium
mrlakadaddy said:
You're s off, just flash stock kernel
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Ok, sorry to be noobish, but how would I flash the Viper kernel? I'm only familiar with flashing zipped flashable kernels.
Just like you normally flash roms and kernels.
you can pull out the boot.img that comes in the viper2.0 rom.
I've been hearing people having screen tearing issues with evilz kernel and viper2.0.
IMHO i think the stock rom kernels are always optimized to the point where their battery life is great.
detatched said:
Ok, sorry to be noobish, but how would I flash the Viper kernel? I'm only familiar with flashing zipped flashable kernels.
Click to expand...
Click to collapse
just reflash the rom without wipeing
HTC EVO LTE
syaoran68 said:
you can pull out the boot.img that comes in the viper2.0 rom.
I've been hearing people having screen tearing issues with evilz kernel and viper2.0.
IMHO i think the stock rom kernels are always optimized to the point where their battery life is great.
Click to expand...
Click to collapse
Yeah, that's why I was making sure to find the easiest way to get back. Some people seemed to be getting good results from EvilZ, but maybe I'll just stick with the one with the ROM.
Thanks for the help!
syaoran68 said:
IMHO i think the stock rom kernels are always optimized to the point where their battery life is great.
Click to expand...
Click to collapse
Non stock kernels can add features way beyond stock. Not just battery but other things. I am a believer in kernels, you just got to find one that works with your setup.
Now that said evilz didn't agree with my phone, hoping to find some time to start work on a new kernel.
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
FredC94 said:
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
Click to expand...
Click to collapse
Necessary? No. I have switched kernels without using the script for the n10. (It is around somewhere on here, in the Apps section I think) But it does FEEL better when you do.
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
But if its the same kernel (updated) then flash without wiping anything because they will use the same ram disk (if they use one anyway).
iKarido said:
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
Click to expand...
Click to collapse
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
---------- Post added at 07:56 AM ---------- Previous post was at 07:44 AM ----------
Memp2Atl85 said:
Do I simply flash the zip file in clockwork mod or what? Currently using Franco and want to give Trinity a try
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Straight from the Trinity Ten Thread.
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had.
Click to expand...
Click to collapse
I know... Thats what I had just said.
iKarido said:
So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Click to expand...
Click to collapse
In my experience bootloop problems from kernel incompatibility with flashing over each other is pretty rare. I actually used to use a combo on Franco's ramdisk with the glados kernel on my phone and it worked perfectly fine. Even Morfic (the maker of Trinity kernel) said you can flash his kernel on top of Franco's and it will give you a sort of hybrid of them both. See here:
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
The governors and such arent part of the ramdisk, thats why. It would be nice to be able to load up the specific governors you want in any kernel, but sadly thats not possible. Those are part of the actual kernel itself and the ramdisk stuff is usually performance tweaks and mods to the system.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
FredC94 said:
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
Click to expand...
Click to collapse
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
iKarido said:
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
Click to expand...
Click to collapse
I am not worried. I have never bricked because I know what I am doing. The lucky part was sarcasm.
EniGmA1987 said:
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
Click to expand...
Click to collapse
That's clear, thanks a lot :good:
Another thing I just thought of is you can make a Nandroid backup of just the boot image as soon as you flash a ROM, give it a name of whatever ROM you are on "-kernel" and then you can restore that boot image whenever you want to restore back to your stock kernel + ramdisk. Alternatively, you can save a backup of your kernel in Trickster MOD and restore it that way at a later point. But both of these methods first require that you still be running your stock kernel and ramdisk that came with the ROM you are on. If you already flashed something else, you will have to re-flash the ROM again to get back to the stock files first
You could just grab the kernel from the rom and throw it into a flashable zip if you don't have a backup, instead of flashing the entire ROM again.