Hi!
I tried to install several kernel on CM11(2013 12 27 nightly)
the installation is doing well:good:, i quit CWM but when i reboot after the google logo i have some blue/cyan/pink stripes moving slowly, like a big graphic bug... the only kernel working is the CM stock...
have you ever had the same problem? how can i resolve it?:fingers-crossed:
Did you factory wipe before installing CM + the kernel?
What kernel are you trying to install? IIRC CM uses CAF libraries so some kernels might not work when used with CM
I have wiped the cache and the data (it has erased my music is it normal?:what: ) before installing CM but not before installing the kernels which are : Franco kernel nightly r10, and ElementalX N7 2.2 (and an other that I don't remember the name.
Sent from my Nexus 7 using xda app-developers app
e-53e said:
I have wiped the cache and the data (it has erased my music is it normal?:what: ) before installing CM but not before installing the kernels which are : Franco kernel nightly r10, and ElementalX N7 2.2 (and an other that I don't remember the name.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Pyroh is right, some kernels will Not work with CM. I know that ElementalX is one that will not work.
Oh! OK! I thought that all kernel were working with CM...
So I have to found a kernel made for C11...
Thanks guys☺
Sent from my Nexus 7 using xda app-developers app
Related
Don't know if this is the place to ask, but I need some help.
I flashed Cyanogenmod 10.2 (latest nightly) on my GNex (GSM), and tried installing a custom kernel (Franco kernel), but when I boot, the message "com.android.phone has stopped working" keeps popping. After reflashing original (CM) kernel, the mesage stops popping. Same happens with other kernels (tried Fancy and Trinity).
Any idea as to what might help?
Thanks.
Jujo12 said:
Don't know if this is the place to ask, but I need some help.
I flashed Cyanogenmod 10.2 (latest nightly) on my GNex (GSM), and tried installing a custom kernel (Franco kernel), but when I boot, the message "com.android.phone has stopped working" keeps popping. After reflashing original (CM) kernel, the mesage stops popping. Same happens with other kernels (tried Fancy and Trinity).
Any idea as to what might help?
Thanks.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache?
Sent from my Galaxy Nexus using XDA Premium HD app
Of course.
Have you installed franco fixed version? You shuold install franco v392 fixed by osm0sis.
lkeops said:
Have you installed franco fixed version? You shuold install franco v392 fixed by osm0sis.
Click to expand...
Click to collapse
Its cm10.2 not cm11
@Jujo12 what exactly did you do when you flashed it? What order and what wiped? (Just for my information: cm10.2 is Android 4.3 right?)
Did you flash the right versions of the kernels? (No I do not think youre retarded or something)
Sent from my Galaxy Nexus using XDA Premium HD app
CM10.2 is Android 4.3.1
Wiped cache and dalvik cache, then flashed kernel. Tried with different kernels. To fix, I have to reflash the CM (which installs the original CM kernel)
CM10.2 is Android 4.3.1
Wiped cache and dalvik cache, then flashed kernel. Tried with different kernels. To fix, I have to reflash the CM (which installs the original CM kernel)
Check other kernels if they will work.
Sent from my Galaxy Nexus using xda app-developers app
experiencing the same problem... franco kernel r392 and cyanogenmod nightly 10.2-20131121. coming from a clean install, cleaned cache and dalvik, looks like some kind of incompatibility...
Dudes, there is a fixed version by @osm0sis that specifically fixes the telephony FC problem on CM10.2.
I hate asking you to search, so here it is: http://d-h.st/KOd
Sent from Google Nexus 4 @ CM11
AndyYan said:
Dudes, there is a fixed version by @osm0sis that specifically fixes the telephony FC problem on CM10.2.
I hate asking you to search, so here it is: http://d-h.st/KOd
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
I told him!
lkeops said:
I told him!
Click to expand...
Click to collapse
...but they didn't listen
Sent from Samsung Captivate Glide @ CM10.1.3
Hello,
First, sorry for my bad english, I'm french.
I try to install this kernel in the Cm 10.2/11, but, one time I reboot the tablet, google logo appear, then, blue screen appear.
Do you have a solution? Need CM on my N7 13.
Thank's
Only certain kernels support cm
Sent from my Nexus 7 using Tapatalk
ElementalX will not work on AOSP or CM roms; installing it will either brick them or cause random reboots.
Birosso said:
ElementalX will not work on AOSP or CM roms; installing it will either brick them or cause random reboots.
Click to expand...
Click to collapse
Actually elemental x will work on aosp based ROMs.
The only kernals you can use on cm are ones that are compatible with them and elemental x doesnt work on cm.
Sent from my Nexus 7 2013
oadam11 said:
Actually elemental x will work on aosp based ROMs.
The only kernals you can use on cm are ones that are compatible with them and elemental x doesnt work on cm.
Sent from my Nexus 7 2013
Click to expand...
Click to collapse
I stand corrected.
You need a kernel that's says CAF compatible. Try glitch kernel, very good. Also I'd suggest reading more before doing things that could potentaly brick your device. Hope you made a backup first.
I've tried several 4.4 ROMs with Franco's latest kernel (r394 I believe) and they will not boot. I can run Dirty V and Tiny with no issues. Is this just me?
Latest is r395 and works properly.
In other news, official r394 won't boot on 4.4.x ROMs, but @osm0sis 's modified version will.
Sent from Google Nexus 4 @ CM11
Yeah r395 is the latest and greatest, and works fine, just choose wisely: http://franciscofranco.minooch.com/GalaxyNexus/
Thanks guys. That makes sense. I have the paid version of the app and r395 is there now.
Sent from my Galaxy Nexus using Tapatalk
When I try to install the Moto X patch on AOSPA 4.1 or SlimKat, I always get a bootloop. I'm just curious why it happens and is there a way to actually use the patch on custom roms
Sent from my Nexus 7 using Tapatalk
Don't use the motox patch, use the one for nexus 4. It works on some custom Roms. I had clean ROM and it kept crashing games and apps so I went back to stock and flashed the patches.
Really stock, xposed, custom kernel, and the dalvik and bionic patches works great.
Sent from my Nexus 7 using xda app-developers app
CleanRom is not counted, it is just a cleaned up stock, and the patches worked on it without problems
Sent from my Nexus 7 using Tapatalk
Hello, I have got a Nexus 7 2013 unlocked bootloader, rooted and running CyanogenMod 12.1 nightly. Recently I have tryed to install the Franco Kernel since i have heard a lot of good things about it, but whenever i do, it reboots into a very laggy CyanogenMod 12.1 boot animation and goes into a bootloop. I have tried installing through recovery and through the non pro version of the Franco Kernel app. The only way i could fix it is by installing the CyanogenMod 12.1 ROM again. Any help would be much appreciated
hassanz519 said:
Hello, I have got a Nexus 7 2013 unlocked bootloader, rooted and running CyanogenMod 12.1 nightly. Recently I have tryed to install the Franco Kernel since i have heard a lot of good things about it, but whenever i do, it reboots into a very laggy CyanogenMod 12.1 boot animation and goes into a bootloop. I have tried installing through recovery and through the non pro version of the Franco Kernel app. The only way i could fix it is by installing the CyanogenMod 12.1 ROM again. Any help would be much appreciated
Click to expand...
Click to collapse
That's because the kernel isn't compatible with cm12, cm and stock are built in a different way and a cm kernel is not compatible with stock and vice versa..
If you ever see a laggy bootanimation after flashing a kernel you can be 99,9% sure that it is not compatible with your rom
Sent from my GT-S7275R using XDA Free mobile app
noahvt said:
That's because the kernel isn't compatible with cm12, cm and stock are built in a different way and a cm kernel is not compatible with stock and vice versa..
If you ever see a laggy bootanimation after flashing a kernel you can be 99,9% sure that it is not compatible with your rom
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, explains a lot, glad to have got a reply on my first thread
Sent from my Nexus 7 using XDA Forums
noahvt said:
That's because the kernel isn't compatible with cm12, cm and stock are built in a different way and a cm kernel is not compatible with stock and vice versa..
If you ever see a laggy bootanimation after flashing a kernel you can be 99,9% sure that it is not compatible with your rom
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Do you know of any kernels compatible with CyanogenMod 12.1. Thanks in advance
Sent from my Nexus 7 using XDA Forums
Use the CAF version of a kernel for CM or CM-based roms. Use AOSP for stock or aosp-based roms.
Franco doesn't have a caf version but most of the other kernels do.