Database Users

[Q] Going back to original kernal.

I'm thinking of flashing Trinity kernel on my Nexus 7. If I have troubles after flashing the Trinity kernel and want to revert back to my present kernel do I restore a nandroid backup or is there something else I have to do to get present kernel back? Am currently running CM 10.1 jb 4.2.1 on my Nexus 7. Any input would be greatly appreciated. Thanks.

Just do a dirty flash (flash CM10.1 again without factory reset, just wipe cache and dalvik). Your kernel will be overwritten.

kevk60 said:
I'm thinking of flashing Trinity kernel on my Nexus 7. If I have troubles after flashing the Trinity kernel and want to revert back to my present kernel do I restore a nandroid backup or is there something else I have to do to get present kernel back? Am currently running CM 10.1 jb 4.2.1 on my Nexus 7. Any input would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
davisac said:
Just do a dirty flash (flash CM10.1 again without factory reset, just wipe cache and dalvik). Your kernel will be overwritten.
Click to expand...
Click to collapse
yup, thats the easiest way. but you dont have to wipe anything, not even dalvik or cache. you can always extract the boot.img from the cm rom and flash it via fastboot too.

Thanks simms. I'm still trying to figure everything out just got my Nexus for Christmas.

davisac said:
Just do a dirty flash (flash CM10.1 again without factory reset, just wipe cache and dalvik). Your kernel will be overwritten.
Click to expand...
Click to collapse
Thanks for all your info. Appreciate it. Have a good one!

How about if Im using stock rom and I want to flash a different kernel, what should I do?

Leonhan said:
How about if Im using stock rom and I want to flash a different kernel, what should I do?
Click to expand...
Click to collapse
Flash the kernel? Lol !

Wilks3y said:
Flash the kernel? Lol !
Click to expand...
Click to collapse
Ive read that franco has a ramdisk of his own, how do I apply a new kernel without problems if I will try a different one (say motley kernel)?

Trinity kernel working great.
kevk60 said:
Thanks for all your info. Appreciate it. Have a good one!
Click to expand...
Click to collapse
Flashed Trinity kernel on my Nexus 7 and it is great. Am running CM 10.1 JB 4.2.1 latest nightly and so far everything is working awesome. Thanks for everyones input. Thanks to morfic for a wonderful kernel. Boom! Freak out now.

[Q] Flashing different Kernels - Nexus 4

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.

[Q] Flashing kernel issue

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

[Q] Custom Rom to stock 4.3?

The situation is fairly complex right now;
Earlier today;
I had my Nexus 7 (2012) running Paranoid Android 3.something with 4.2.2 as the base rom.
My objective was:
To update to Paranoid Android 3.the latest version (which uses 4.3 as the base rom)
What I did:
I downloaded both the latest rom + gapps from the proper xda site for Nexus 7 and tried flashing them from TWRP.
It installs the rom just fine, but gives me an error on the Gapps (Error 7, if that helps).
I'm guessing this is because I'm not on 4.3 but on 4.2.2. Can someone confirm this please?
What I have done now:
So I thought I should flash a stock 4.3 rom and then try installing the new PA rom. But The flashing method for the stock rom is completely different than a custom rom, it seems.
What I think I should do:
So, should I somehow install the stock 4.3 rom and THEN try to flash the new PA rom?
If not that, then what can I do to get to the latest Paranoid Android?
Thank you!

It is totally unnecessary to upgrade to stock 4.3 prior to PA 3.9x.
Firstly, which GAPPS package did you attempt to install? The packages for 4.2.2 and 4.3 are not interchangeable.

najaboy said:
It is totally unnecessary to upgrade to stock 4.3 prior to PA 3.9x.
Firstly, which GAPPS package did you attempt to install? The packages for 4.2.2 and 4.3 are not interchangeable.
Click to expand...
Click to collapse
The 4.3 gapps gives me an error and says incompatible rom, the 4.2.2 gapps installs just fine, but the my tablet is stuck at the PA boot logo.
If I'm on 4.3 stock, shouldn't it install 4.3 gapps and 4.2.2? :S
And if 4.2.2 is the right one for me, then what to do if I'm stuck at the boot?

railpressureflip said:
The 4.3 gapps gives me an error and says incompatible rom, the 4.2.2 gapps installs just fine, but the my tablet is stuck at the PA boot logo.
If I'm on 4.3 stock, shouldn't it install 4.3 gapps and 4.2.2? :S
And if 4.2.2 is the right one for me, then what to do if I'm stuck at the boot?
Click to expand...
Click to collapse
Are you using pa_gapps-full-4.3-20130808-signed.zip? There should be no issues using it with PA 3.9x. If you're having problems installing 3.9x with that package, you may have a corrupted download.
Sent from my Nexus 7 using Tapatalk 4

najaboy said:
Are you using pa_gapps-full-4.3-20130808-signed.zip? There should be no issues using it with PA 3.9x. If you're having problems installing 3.9x with that package, you may have a corrupted download.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
All good now, I fixed it.
The issue was that the Paranoid Android rom link is of the 3.5x version, which is essentially a 4.2.2 rom. And that was the latest rom the PA poster had. I realized it's not 3.91, which was the one I needed. So I went fetching for it on google and finally found it, then ran the 4.3 gapps and **** was all good.
Thanks for your help though, I truly appreciate it!

[Q] Nexus 7 kernel

Hi,
Can I use the M-kernel with C-Rom?I am currently using the smoothrom v5.3.Do I flash the kernel after flashing C-Rom and gapps?

You can use M kernel with C-rom. And yes, flash it after rom and gapps. Personally, I flashed rom and gapps, rebooted, set up N7, then rebooted to recovery to flash kernel. It may not matter, just my preference. Enjoy!