I am currently running a Nexus 4 with PARANOIDANDROID 2.99b+ (Feb03) flashed with the Franco r53 kernel.
I wanted to try out the Matrix 6.5 kernel on my phone and was wondering if there is any step that I need to perform before flashing the new kernel. I found the following post that includes a cleaner script: http://forum.xda-developers.com/showthread.php?t=2121701
I was wondering if this is required or if we can simply flash the matrix kernel over the franco kernel. Would that be possible?
Also, would it be possible to flash the new PARANOIDANDROID release (assuming it includes a kernel) then flash the matrix kernel over that? Would this cause problems because the cleaner script was not run before flashing the new rom which has its own kernel?
Was not sure how it exactly works and was hoping that someone would be able to help me out and clarify the process.
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
linelock said:
Currently, I think your safest option is to flash the newest version of the PA rom and gapps and then flash the kernel that you want. Because a lot of the kernel developers are are making changes to things that may not be overwriten when flashing a kernel from a different developer. For example I think that franco makes changes to the ramdisk that some other kernel devs don't touch.
Click to expand...
Click to collapse
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
jauwad.arshad said:
Cool, so I guess when we flash the rom and gapps it resets any changes that may have been made by Franco's kernel (or any other kernel for that matter). Hence, running any cleaner script is not required. Is this true?
Also, when flashing the kernel I wipe cahce, wipe dalvik, flash kernel, reboot. I read in another post that you should let it run for 10-15 minutes then reboot again to let the kernel "settle in". Is this actually required?
Click to expand...
Click to collapse
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
simms22 said:
if you are running franco kernel, you want to either reflash your rom then the kernel, or flash the roms boot.img then the kernel. coming from other kernels, just flash the new kernel on top. the reason being that franco kernel uses its own ramdisk(and you want your roms ramdisk).
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
you do not wipe anything when flashing kernels, there is no need. wiping cache or dalvik has nothing to do with kernels, its just a misconception that keeps getting passed along.
Click to expand...
Click to collapse
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
jauwad.arshad said:
Awesome, thanks for the info. So I guess it is a safe practice to flash the boot.img (or just update the rom if you were going to anyways) and then flash the kernel.
Click to expand...
Click to collapse
yup. i tell people to just reflash their rom(and gapps) with the kernel, then reboot if they were running franco kernel. but its safe to flash the stock or your roms boot.img also, then the kernel.
simms22 said:
then reboot if they were running franco kernel.
Click to expand...
Click to collapse
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
twitchcity said:
You might notice if you update your ROM (e.g. the next time PA gets updated, or if you switch to CM nightlies) that during the flash, the kernel will be overwritten - no matter which kernel you are using.
For example, flashing CM installs the CM kernel - regardless of if I was running Franco's before that. This is why apps like CyanDelta (which supports incremental updates to the ROM, but also the flashing of zips *after* flashing the ROM) are so handy. Every three days, I flash the latest CM nightly, and then Franco's kernel. If I left Franco's kernel off the CyanDelta list, the phone would be using the latest CM kernel after the flash.
EDIT: Your steps look good, if not a little bit overly protective. For instance, I don't think a full factory reset is required to test out a different kernel, generally speaking. Obviously, it wouldn't hurt to do... just takes time.
Click to expand...
Click to collapse
That is pretty cool. Would that same app work on the PA rom or is it just for CM nightly builds?
Yeah, I am doing the factory reset because its a new version of the PA rom. I prefer not to simply flash over my current rom.
If you're running the latest PA on a mako, just get their 'contrasty' kernel and no need for your voodoo rituals
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
auto freak said:
I am currently on franco kernel milestone 2 and want to try trinity kernel.
I have taken a 'back-up' of the stock kernel on the franco kernel updater app before i flashed franco.
Can I now restore my phone to stock kernel using this back-up and then flash trinity?
Will this work?
Click to expand...
Click to collapse
you can. or you can just reflash your rom and trinity, dont wipe a single thing. just flash the rom, kernel, then reboot.
jauwad.arshad said:
I am not sure what you meant by that.
What I get out of all of this, is that if I want to try a new kernel this is what I should do in recovery:
Factory reset + wipe cache + dalvik cache
Flash new rom (PA rom in my example)
Flash gapps
Flash custom kernel if desired (Franco's kernel in my example)
Reboot
Is that correct or am I missing a step/doing something extra?
Click to expand...
Click to collapse
Only if you have franco now and switch to another kernel. So if you want to flash franco you don't have to wipe anything.
I recently rooted my nexus 7 and now im trying to flash clemsyn's kernel to it, however i haven't been able to get it to work. I've tried rebooting into recovery and wiping the cache and dalvic cache, then installing from zip, but it always fails. any idea why?
You flashed it on which rom? I think it's not compatible with your rom.
Ensure you read the OP of the thread to verify that the kernel is compatible with the version of Android that you're using. Remember, always RTFM, even if you think you know what you're doing.
Do you have to flash a ROM before you flash a kernel?
The Drugs said:
Do you have to flash a ROM before you flash a kernel?
Click to expand...
Click to collapse
Roms include a kernel and will overwrite the previously installed kernel. If you want to flash a custom kernel in conjunction with a rom, you always flash the kernel after the rom.
Oh! That makes sense. I'll try that later and see if it works
Hi everyone,
I have an odd issue with my Nexus 7.
I have first used the Toolkit to make a clean update to 4.4.2. KOT49H.
Then I installed Purity Rom and PA Gapps, everything worked.
But when I tried to install a new Kernel (Oxydo or Faux123), I have a bootloop just after it.
I tried to wipe at differents stages, different roms, I tried the install in different orders but at the end, the only way is too wipe system or factory reset and then reinstall the custom Rom. I guess it works again because Purity has a proper kernel ?
I use TWRP v2.6.3.1.
Thanks.
Have you tried using the lean kernel?? I had issues with purity using m-kernel. I then switched to lean. I'm guessing with the minimalistic nature of lean kernel I didn't cause any problems with the system. Overclocked to 1500 using interactive governor.
Sent from my Nexus 7 using xda app-developers app
KKKlown said:
Hi everyone,
I have an odd issue with my Nexus 7.
I have first used the Toolkit to make a clean update to 4.4.2. KOT49H.
Then I installed Purity Rom and PA Gapps, everything worked.
But when I tried to install a new Kernel (Oxydo or Faux123), I have a bootloop just after it.
I tried to wipe at differents stages, different roms, I tried the install in different orders but at the end, the only way is too wipe system or factory reset and then reinstall the custom Rom. I guess it works again because Purity has a proper kernel ?
I use TWRP v2.6.3.1.
Thanks.
Click to expand...
Click to collapse
Oxydo kernel has some issues right now. Are you installing the v2 of the kernel?
i installed the motley kernal and trickster mod on my rooted nexus 7 using twrp. but now i'd like to try the elemental kernal. i downloaded the elememtal kernal and tried to flash it but i guess i have to uninstall the motley kernal first. can someone tell me what i need to do to get the elemental kernal installed?
I'm currently on Franco Kernel but want to change to ElementalX kernel.
I've read that you can't just install the new kernel over the old kernel is that true?
Will I need to do wipe my device in order to install?
It's recommended to dirty flash stock or your rom, depending on what you use. No need to wipe anything.
Regards,
JoKe_42 said:
It's recommended to dirty flash stock or your rom, depending on what you use. No need to wipe anything.
Regards,
Click to expand...
Click to collapse
I'm not using any ROM just the Franco kernel.... so I should just flash over Franco with ElementalX kernel?
Newerabs said:
I'm not using any ROM just the Franco kernel.... so I should just flash over Franco with ElementalX kernel?
Click to expand...
Click to collapse
Flash a stock boot.img (which is the stock kernel) first then flash SuperSU if you want root, then flash elemental.