Hi everyone,
I know this is probably a really nooby question, but im running the most recent nightly of cyanogenmod and i noticed it has its own kernel under About Phone. I would like to use faux kernel instead. Is it safe to flash faux kernel over the top of it or will it mess things up? Thanks guys!
All ROMs have kernels. They can't work without one so this makes the rules of changing kernels with cm no different from any other Rom.
You're right though, it's a really nooby question. I'm not trying to offend but not knowing this means you're not ready for flashing kernels. Please read the sticky threads in Q&A and general to bump your knowledge up to the next level first
Fyi, cm use CAF kernels only so you can only Flash CAF kernels.
Sent from my Nexus 5 using Tapatalk
you can flash any kernel you want.. but it doesnt mean that itll run. cyanogenmod uses caf for source, the moved away from aosp. so you can flash and run kernels based in caf, not aosp. faux kernel is an aosp kernel, so if you flash it you wont boot up.
Yeah, but only flash kernels for the n5. Flashing something else can brick it. If it's a caf based rom flash a caf kernel.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
rootSU said:
All ROMs have kernels. They can't work without one so this makes the rules of changing kernels with cm no different from any other Rom.
You're right though, it's a really nooby question. I'm not trying to offend but not knowing this means you're not ready for flashing kernels. Please read the sticky threads in Q&A and general to bump your knowledge up to the next level first
Fyi, cm use CAF kernels only so you can only Flash CAF kernels.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ive read the stickies. I wanted to be cautious because im new to cyanogen and i didnt wanna mess anything up. I was using Cataclysm with Faux so I didnt need to know about CAF kernels back then. Thanks for your help anyway
simms22 said:
you can flash any kernel you want.. but it doesnt mean that itll run. cyanogenmod uses caf for source, the moved away from aosp. so you can flash and run kernels based in caf, not aosp. faux kernel is an aosp kernel, so if you flash it you wont boot up.
Click to expand...
Click to collapse
jd1639 said:
Yeah, but only flash kernels for the n5. Flashing something else can brick it. If it's a caf based rom flash a caf kernel.
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Alright got it. Ill have to go for a CAF kernel, thanks guys!
ProVickers said:
Ive read the stickies. I wanted to be cautious because im new to cyanogen and i didnt wanna mess anything up. I was using Cataclysm with Faux so I didnt need to know about CAF kernels back then. Thanks for your help anyway
Click to expand...
Click to collapse
It's good to be cautious.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It's good to be cautious.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
right
Related
Guys i have two question..Whats the difference between All other ROMs and Custom IO control (CM tweak)
links from https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdEt6NWVkX01vNmpfbEh4MHo4eDRCbXc#gid=0
And the second one is to flash the kernel i must first flash kernel and then the rom or first the rom and then the kernel??Thnx
Cm tweak is for cm based ROMs, all others is for, well, all others. Flash kernel after flashing ROM.
Sent from my ns4g using Tapatalk 2
p1gp3n said:
Cm tweak is for cm based ROMs, all others is for, well, all others. Flash kernel after flashing ROM.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
How i will find which roms are CM based?
Read the thread about the ROM you are interested in. If I'm not familiar with a ROM, i generally read the first page and the last few pages. That way I see what the dev says about it, and see more recent reviews/comments about the current version
Sent from my ns4g using Tapatalk 2
Guys i flash marmite 7.3.1 kernel but from NSTOOLS i cant change cpu governor...Says not availbale...do u know why?thnx
keymaster123 said:
Guys i flash marmite 7.3.1 kernel but from NSTOOLS i cant change cpu governor...Says not availbale...do u know why?thnx
Click to expand...
Click to collapse
go to recovery ->advance->fix permission
keymaster123 said:
How i will find which roms are CM based?
Click to expand...
Click to collapse
U can go to setting-->about rom and read the information of your rom
So I lost my phone, got a new one, rooted using the casual root/unlock w/twrp method found on this forum http://forum.xda-developers.com/show....php?t=2332825
Is it possible to somehow improperly root/unlock without bricking? Or that I just got a bad download. I am having random reboots with just about every kernel I flash, some worse than others. I can only run the stock kernel. Running a clean 2.9 and the latest TWRP. Would it be useful to do a full wipe and "reroot/unlock"
What rom are you using and what kernels are you trying to flash?
Sent from my SCH-I535 using Tapatalk 4
Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Well, I follow AOSP kernel development a little bit. If I were you, I'd start by flashing a kernel built within seven days of July 20th cuz it seems every two to three weeks, kernel commits render older roms useless. If you don't follow AOSP commits in the more popular rom or kernel threads then I suggest staying away from custom kernels cuz they move quickly. Custom AOSP kernels built on 8/13 won't work on older roms for example.
Edit: I got July 20th cuz LiquidSmooth was last updated on July 20th btw. Just to be clear.
Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Hope so too. I'm trying out Slim Bean beta 2 with BMS kernel from 8/15 and it's working great performance wise. I'd even suggest trying newer 4.3 rooms (CM, Unofficial CM, PA, etc) just for a couple hours and trying your hand with a custom kernel from 8/13 or newer. Or trying a newer 4.2.2 nightly with a custom kernel. For BMS, I believe GideonX said that 7/30 is the last JB 4.2.2 kernel he's made.
How long would you say you waited before flashing the kernel? I usually flash rom, reinstall my apps, set up home screens, then flash a kernel. Maybe 20 minutes between rom and kernel flash cuz of habit.
Sent from my SCH-I535 using Tapatalk 4
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
alexm231 said:
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
Click to expand...
Click to collapse
1st option
Primokorn said:
1st option
Click to expand...
Click to collapse
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
alexm231 said:
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
Click to expand...
Click to collapse
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
Great. Thanks so much for the detailed answer, it clears up my confusion!
Now off to try Franco's kernel
Alex
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
I actually have an additional question: do we need the same process even if we're talking about the newer version of the same kernel? Like going from an older version of Franco's to the newest
Alex
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
kufikugel said:
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
alexm231 said:
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
Click to expand...
Click to collapse
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
rootSU said:
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
Click to expand...
Click to collapse
Yes, I consider your guideline (on your signature) very good advice indeed.
Thanks again to all
Alex
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
I know I had to do that when I flashed elemental. Otherwise some apps won't open. But now I want to find out was the the full correct way? Or was it the lazy way
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
Flash the stock boot.img and system.img and then flash the kernel you want to change to..
I have also tried just flashing the stock boot.img and then the custom kernel.. Sometimes it works, sometimes it doesn't. So I would reccomend flashing both! (boot and system)
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
simms22 said:
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
Click to expand...
Click to collapse
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
akmsr said:
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
Click to expand...
Click to collapse
yes. they arent located in either of those locations, so my advice applies, and is the only reason why i posted this. they are located in /etc/init.d/. you either dont have that location (best option), have it but an empty folder, or have an init.d folder with files in it. if there are files there, delete them.
Flashing a system.img will overwrite init.d scripts. /etc is a symbolic link to /system/etc so when you replace /system/etc with whatever is in a ROM.zip or a system.img, these changes apply to /etc too.
If you look in any ROM.zip or kernel.zip, they all flash their scripts to /system/etc/init.d
Sent from my Nexus 5 using Tapatalk
Think I am going to go ahead and make a switch to Paranoid Android. I had been using Franco Kernel on stock, but it looks like that won't work with PA. Which are the most stable kernels that do work?
scottharris4 said:
Think I am going to go ahead and make a switch to Paranoid Android. I had been using Franco Kernel on stock, but it looks like that won't work with PA. Which are the most stable kernels that do work?
Click to expand...
Click to collapse
wouldnt asking what kernels people use in the PA thread get you an answer the quickest?
Ive used Franco on PA for months. No problems
Why wouldn't Franco kernel work?
#stayparanoid
Pirateghost said:
Why wouldn't Franco kernel work?
#stayparanoid
Click to expand...
Click to collapse
Its got an "o" in the name. I heard kernels with an "o" in their name aren't compatible
Sent from my Nexus 5 using Tapatalk
Is Mahdi-Rom AOSP or CM (CAF) based?
I've been researching of this for the whole night last night but keep on finding mixed answer.
and now I'm hoping for you guys to answer me...i wanted to install elemental x but don't know which version to install aosp or cm
and will franco kernel be comparable since its for aosp?
Thanks soooo much to who ever answer this...!
matthewle96 said:
Is Mahdi-Rom AOSP or CM (CAF) based?
I've been researching of this for the whole night last night but keep on finding mixed answer.
and now I'm hoping for you guys to answer me...i wanted to install elemental x but don't know which version to install aosp or cm
and will franco kernel be comparable since its for aosp?
Thanks soooo much to who ever answer this...!
Click to expand...
Click to collapse
Its AOSP with CAF stuff in it. Just flash one and if it doesn't boot reflash the ROM and flash the other.
Thanks
Lethargy said:
Its AOSP with CAF stuff in it. Just flash one and if it doesn't boot reflash the ROM and flash the other.
Click to expand...
Click to collapse
so just to make sure that franco is FULLY comparable with this rom?
matthewle96 said:
so just to make sure that franco is FULLY comparable with this rom?
Click to expand...
Click to collapse
Make a backup, flash. If it doesn't boot then it isn't compatible.
matthewle96 said:
so just to make sure that franco is FULLY comparable with this rom?
Click to expand...
Click to collapse
make a backup in recovery and just flash the darn kernel. if its not compatible, it wont boot. then you can either flash a known booting kernel or restore the backup you made in recovery. that's the quickest way to find your answer.
simms22 said:
make a backup in recovery and just flash the darn kernel. if its not compatible, it wont boot. then you can either flash a known booting kernel or restore the backup you made in recovery. that's the quickest way to find your answer.
Click to expand...
Click to collapse
thanks
Haha this really is a good question though. I myself didn't know either. I had been under the impression it was full AOSP.
Last time I ran Franco kernel on it though all was fine.
Sent from Tapatalk on Nexus 5
TheLastSidekick said:
Haha this really is a good question though. I myself didn't know either. I had been under the impression it was full AOSP.
Last time I ran Franco kernel on it though all was fine.
Sent from Tapatalk on Nexus 5
Click to expand...
Click to collapse
Quite a few ROMs say AOSP but have CAF parts lol. Rarely are ROMs full CAF though, the only one that I know of is CM of course. Some AOSP kernels work with hybrids and some only do after modification.
An AOSP Dalvik will only boot up on full AOSP ROMs so it the Z2 Dalvik boots, it's full AOSP. If a CAF Dalvik boots, it's either hybrid or full. Nice way to tell
Lethargy said:
Quite a few ROMs say AOSP but have CAF parts lol. Rarely are ROMs full CAF though, the only one that I know of is CM of course. Some AOSP kernels work with hybrids and some only do after modification.
An AOSP Dalvik will only boot up on full AOSP ROMs so it the Z2 Dalvik boots, it's full AOSP. If a CAF Dalvik boots, it's either hybrid or full. Nice way to tell
Click to expand...
Click to collapse
Ah thanks. I never really messed with the custom dalvik because I didn't see anything other benchmark gains.
Sent from Tapatalk on Nexus 5
TheLastSidekick said:
Ah thanks. I never really messed with the custom dalvik because I didn't see anything other benchmark gains.
Sent from Tapatalk on Nexus 5
Click to expand...
Click to collapse
Some people say general usage is slightly better, some say it doesn't help in general ui. Experience varies. Lol.
I ran mahdi rom for a long time use aosp kernel caf will not boot
Franco Kernel on OPO?
Any update on whether Franco Kernel is compatible with this CM based Mahdi rom on the OnePlus One?