Develop Bugs

AOKP stock kernel download?

Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.

mk_ln said:
Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.
Click to expand...
Click to collapse
Settings - about phone - kernel version. I think it's faux's kernel, at least used to be. Or just flash the rom again, it'll put back the stock (rom) kernel.

thanks, but doesn't flashing the rom again wipe data?

mk_ln said:
thanks, but doesn't flashing the rom again wipe data?
Click to expand...
Click to collapse
It doesn't, no

thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.

mk_ln said:
thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.
Click to expand...
Click to collapse
Not always necessary to update, 17+ is a heck of a kernel..

maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.

If you reflash the rom you have to reflash the gapps and you should be fine.
"Long is the way, and hard, that out of hell leads up to light."

Nandroid. It will backup the kernel, just make sure if you go back, you restore system as well because each kernel can have a few libs with it that another might not.
Also, you should be in the ha bit of making a nandroid whenever you flash something, until you can verify there are no bugs you can't live with.
Sent from my Sensation using Tapatalk 2

mk_ln said:
maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.
Click to expand...
Click to collapse
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.

RogerPodacter said:
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.
Click to expand...
Click to collapse
thanks.
just to confirm, is the command "fastboot boot boot.img" or "fastboot flash boot.img"...? or perhaps something else entirely?

Fastboot flash boot boot.img
"Long is the way, and hard, that out of hell leads up to light."

thanks!

boot loop pliz help fast dont have alot of battery!!!

hey. just now i unlocked my device and want toflashe rom cm10 in this forum,i didnt do root ,i flashed the kernal faux 0010b4 and flashe the rom and the gapps,i did all this ,iand not its in boot loop alot of time,i tried to restore to hwat i backed up- ,and still in boot loop... what i can do? pliz help.

Can you get into recovery? You can charge it there.
Sent from my HTC One X using xda app-developers app

you sure?
you sure in that? because i dont see red light when i am in recovery...

bardahan123 said:
hey. just now i unlocked my device and want toflashe rom cm10 in this forum,i didnt do root ,i flashed the kernal faux 0010b4 and flashe the rom and the gapps,i did all this ,iand not its in boot loop alot of time,i tried to restore to hwat i backed up- ,and still in boot loop... what i can do? pliz help.
Click to expand...
Click to collapse
Did you repack the kernel for the ROM.
Dude, I got to where you are a couple of weeks ago and I panicked. 10 minutes later I was sorted.
Download the rom and kernal again (prolly best to use a kernel already packed for the ROM you want to take a variable out of the equation). May I recommend Tripndroids CM10 ROM and the kernel that comes with it. This will be fast to flash before your battery dies and I am very familliar with flashing it so I'll be able to help more easily. You can always start again when you've charged. Alternatively, Use the boot.img from any ROM you like. Stick to a matching ROM and kernel for now as it saves the repack and a couple of steps in flashing.
Copy ROM zip to your SD (using ADB is easy: adb push yourfile.zip /sdcard/yourfile.zip)
Extract the boot.img from the rom zip (on your PC)
Go into fastboot and connect USB
fasboot flash boot boot.img
fastboot erase cache
Full wipe in recovery
erase cache and dalvik in recovery
Flash the ROM in recovery
Reboot - First boot will take a while.

very ty
hey, ty for the good explain ,now i tried another kernal and its worked,mabey the kernal just was fail,but now the phone is work ,very ty.
just 1 question,which rom is good and stable? and if good life battery that you can tell me? because i saw all the roms in this forum and i dont know which one is the best
ty for the help

bardahan123 said:
hey, ty for the good explain ,now i tried another kernal and its worked,mabey the kernal just was fail,but now the phone is work ,very ty.
just 1 question,which rom is good and stable? and if good life battery that you can tell me? because i saw all the roms in this forum and i dont know which one is the best
ty for the help
Click to expand...
Click to collapse
That's very subjective but I like TripNRaVeRs CM10 Endeavour Unleashed. It comes with a completely stable 2.x kernal and there is an almost totally stable 3.x kernel and an experimental (not at all stable) 3.x kernel. All cna be flashed without the re-pack.
BTW. If you ever get to panic stations again you can charge by going into fast boot and choosing power down. Then you can charge for a while before starting again.
BTW agian, there is a thanks button. You could click it if you wanted!

if you want to use other kernel (faux, ncx) than the one supplied in rom you should always repack it using online repacker http://nibble.cc/repack/
if not you will be 90 % stuck in bootloop

CWM/TWRP backup and restore vs. kernel flashing

I'm a long time user of CWM on my SGS1 and, lately, of TWRP on my SGS3, but I never had to restore a backup created in either recovery.
Now, I'm looking forward to flashing ktoonsez's Sammy kernel on my rooted Bell LH1 ROM and there is one piece of warning that makes me a little unconfortable...
ktoonsez said:
WARNING: This kernel has updated WIFI and Bluetooth drivers. If you are going back to stock, you need to get those drivers back or those 2 devices will not work. Simply flashing a kernel will not do it unless it also flashs back those drivers (they are in "/system/lib/modules" folder).
Click to expand...
Click to collapse
Let's say I create a backup of my current config in TWRP, flash ktoonsez kernel and then restore my backup.
Will I restore the original kernel along with the rest (wifi and usb drivers included) or is the kernel not part of the backup ?
Thanks

HiKsFiles said:
I'm a long time user of CWM on my SGS1 and, lately, of TWRP on my SGS3, but I never had to restore a backup created in either recovery.
Now, I'm looking forward to flashing ktoonsez's Sammy kernel on my rooted Bell LH1 ROM and there is one piece of warning that makes me a little unconfortable...
:laugh:
Let's say I create a backup of my current config in TWRP, flash ktoonsez kernel and then restore my backup.
Will I restore the original kernel along with the rest (wifi and usb drivers included) or is the kernel not part of the backup ?
Thanks
Click to expand...
Click to collapse
I suggest you test it out for another type of kernel like flash two jb roms and flash a cm10 kernel and see if you still have the original kernel with the first rom just to test if it actully backups the kernel too.. i have TWRP too xD too bad i got my fone tooken away or id test this out my self :laugh:

nandroid backs up your kernel and drivers. So as long as you have a backup you should be fine

amzi said:
I suggest you test it out for another type of kernel like flash two jb roms and flash a cm10 kernel and see if you still have the original kernel with the first rom just to test if it actully backups the kernel too.. i have TWRP too xD too bad i got my fone tooken away or id test this out my self :laugh:
Click to expand...
Click to collapse
Dude, that's like going to New-York from Montréal but stopping by Los Angeles on your way.
Feasable... but it'll take you ages!

HiKsFiles said:
Dude, that's like going to New-York from Montréal but stopping by Los Angeles on your way.
Feasable... but it'll take you ages!
Click to expand...
Click to collapse
bro ur just lazy it doesnt take that long LOL

True, I am lazy by nature and I assume it pretty well!

[Q] How to choose a ROM

I just got my replacement HTC One V CDMA unlocked and rooted. I want to overclock and understand I need a custom ROM to do so. My first HTC One V I bricked trying to flash rhythmicrom. I unlocked, rooted, backed up using TWM. Each time I tried to flash the new ROM it would get stuck on the HTC screen with the red writing talking about developmental purposes, etc. Each time it would hang on that screen I would simply do a recovery to the back up file and everything would go back to normal. The last time I tried to flash it hung up, and when I tried to go back it would not go back. I am not sure why Rhythmicrom would not work. Is there another one I should try? Does it matter if my HTC one V is a newer version, etc? I just need a basic ROM with the ability to overclock. MMS is a necessity and the camera would be nice. Thanks for any help you can give me.

Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one

zzjoshzz said:
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
Click to expand...
Click to collapse
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?

tackj said:
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
Click to expand...
Click to collapse
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.

why u no flash kernel omg! just read the trouble shooting section

lilrob1213 said:
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
Click to expand...
Click to collapse
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.

tackj said:
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
Click to expand...
Click to collapse
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup

lilrob1213 said:
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
Click to expand...
Click to collapse
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?

tackj said:
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
Click to expand...
Click to collapse
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not

lilrob1213 said:
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
Click to expand...
Click to collapse
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.

tackj said:
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
Click to expand...
Click to collapse
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha

lilrob1213 said:
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
Click to expand...
Click to collapse
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.

tackj said:
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
Click to expand...
Click to collapse
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help

lilrob1213 said:
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
Click to expand...
Click to collapse
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.

tackj said:
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
Click to expand...
Click to collapse
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself

lilrob1213 said:
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
Click to expand...
Click to collapse
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!

tackj said:
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
Click to expand...
Click to collapse
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"

lilrob1213 said:
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
Click to expand...
Click to collapse
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.

tackj said:
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
Click to expand...
Click to collapse
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first

lilrob1213 said:
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
Click to expand...
Click to collapse
You are right, the phone is more snappy for sure. What GHz do you use for everyday? I was using [email protected]$$v2 gov but put it on performance just during the test. I also have buzzlauncher as my launcher so I am not sure if that is taking away from the performance, but it looks nice. I am just happy that it is working, so again thanks for your help.

Process com.android.phone has stopped

Hi, I was running the latest AOKP and I decided to install franco kernel. After doing that, on the reboot I had this error repeteadly and I can't get into the system. How do I enter TWRP? Usually I used to longpress power and select reboot -> recovery, but now I can't use that option.
If I turn on the phone by using volume down + power, I get into the recovery stock, but I can't select anything.
How do I resolve? I managed to get into the recovery once, I wiped data, but the error comes out again. Now I'm stucked on the initial wizard with this popup message :crying::crying:

Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Just keep pressing ok to it and get to settings/apps/all and clear data in contacts and contact storage. Then let it all re sync from Google
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?

Tommolo said:
I reinstalled the rom and it seems to work, but then I tried reinstalling franco kernel and the popup is here again. Why? Is the kernel the problem?
Click to expand...
Click to collapse
I assume the latest AOKP is based off Android 4.3, and you're trying to install Franco r392? Have you tried the modified Franco r392 by @osm0sis?
Sent from Samsung Captivate Glide @ CM10.2

I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you

lanruid said:
I am experiencing the same behavior on the 2013-11-14 AOKP build. I have tried r392-fixed by osm0sis and was surprised to see the same issue. I've used that kernel on an earlier build of AOKP without issue. I would really like to reinstall Franco kernel. Is there anything else that I can try?
Thank you
Click to expand...
Click to collapse
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Did you try my above post? I used to test the official PAC rom for the Xperia S so it happens a lot with test builds. It always sorted the issue
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried the r392-fixed by osm0sis. I used the same .zip file that I have successfully installed on previous AOKP builds. While there is no way to clear Contacts and Contact data once in this "com.android.phone has stopped" loop, I have tried clearing the Contacts & Data, then immediately rebooting into recovery and flashing r392-fixed. Upon reboot I am presented with the same message. Thinking that this may have been something caused by restoring data from Titanium, I did a factory reset and clean install of AOKP 2013-11-14 along with franco r392-fixed and I still see the issue. I have cleared both cache and dalvik on every flash. Could there be some other cache stored on the sdcard somewhere causing issues?
At this point I was planning to wait for the next AOKP release and hope the issue goes away unless someone has other suggestions.
Thank you.

i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.

handofdark said:
i had the same problem with franco kernel.
go into bootloader mode , and use the wugfresh root toolkit to boot your phone into custom recovery , and flash another kernel.
Click to expand...
Click to collapse
I was able to get into recovery and simply restore the ROM, which replaces the kernel. I was posting to see if anyone could help me actually get the franco kernel installed on the 2013-11-14 AOKP build. I would like to have posted this in the kernel dev thread, but my post count isn't high enough.

i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version

For future readers who may find themselves in this situation, I found the following procedure to allow you to get out of the error loop and boot into recovery without pulling the battery provided your power off menu has an option to reboot into recovery [AOKP provides this option].
When the phone first boots you will be stuck in an infinite "Process com.android.phone has stopped" popup loop. Dismissing the dialog simply brings it right back.
1. Turn the display off by pressing the power button.
2. Turn the display back on using the power button.
3. Dismiss the dialog. It did not come back at this point for me, leaving me at a normal looking slide to unlock screen.
4. Long press the power button to bring up the Power Off / Reboot menu.
5. Reboot into recovery.
At this point you can re-flash your ROM which should restore the stock kernel provided with your ROM.
---------- Post added at 01:26 PM ---------- Previous post was at 01:16 PM ----------
handofdark said:
i think the problem is with the r392 franco kernel , cause i had the problem with the latest cm 10.2 nightly version
Click to expand...
Click to collapse
Please try the r392 FIXED version provided by osm0sis. I believe there is a link provided earlier in the thread. While this did not work for me with the 11-14 AOKP build, I have had it work with earlier builds and many have had luck with it using CM based ROMs.
My problem is that even the fixed version left me with the com.android.phone error and I'm not sure why.

im good with leankernel at the moment thanks

I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?

TheNexian said:
I'm having the exact same problem. I'm using AOKP 2013-11-14. I also tried the previous version of the Franco kernel, r391, but it did the same thing.
Is there another kernel that you guys can recommend that's as well supported and has similar features?
Also, I wanted to say that I've seen posts from lots of people using AOKP+Franco, saying that it works perfectly. Why is it suddenly not working for us? Could it be our particular AOKP nightly version?
Click to expand...
Click to collapse
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.

lanruid said:
Did you try the fixed version by osm0sis? If not, you can find a link earlier in this thread and in the Franco kernel thread. If it works for you, please let me know because it didn't for me with this build.
Click to expand...
Click to collapse
I'm sorry, I can't find the link in either of the locations. I did a search for the word "osm0sis" in the franco kernel thread and it doesn't show up.
I'm very much a newbie at rooting and roms at the moment, so please excuse the question, but is there any reason that two identical phones running the same rom, kernel, and recovery should behave differently? My phone's the I9250, and I'm using clockworkmod recovery.
Thanks

try franco r394
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.

Sczep said:
I was having the same problem while using CM 10.2 and several Kernels.
I have now flashed franco.Kernel r394. All modification done by osm0sis are included and it's working fine on my Nexus.
Click to expand...
Click to collapse
Same here. r394 is working fine with AOKP nightly 2013-11-14 on my GNex as well.

I got this error when I try to place or pick a call in PAC or Carbon or crDroid rom. But no such error in slim rom. Can anyone tell me why. I really want to try pac rom.
sent from a phone running on SLIM ROM