Develop Bugs

Stuck at CM boot screen after flashing back to 10.0

I've had CM10.0 installed on my Verizon GNex since it was released. Just today, I decided to update to the newest experimental CM10.1. I was wary about an experimental, but it displayed as a stable release, so I figured I would give it a shot. After having the 10.1 experimental running for about 10 minutes, I decided to see if I could flash back to 10.0, because there was no option to add/sync my google account in 10.1 experimental. I saw that 10.0 was still able to be flashed from the updater within 10.1 experimental, so I started the installation. Everything seemed fine with the flash, but then when it rebooted, it just got stuck looping the CM boot screen.
I can still access the bootloader and get into ClockworkMod Recovery 6.0.1.5. What can/should I do to get CM10.0 booting? If it's not possible, how would I go back to stock firmware?
Thanks all!

All fixed now. Thank you! I used CWM Recovery to push the newest CM nightly and gapps to the sdcard, then just flashed them from within CWM and rebooted. All good now.
PHEW!

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

A few issues Tapped Out, CM 11 and AOKP

Is AOKP broke for the T-Mobile S3? I tried installed and kept getting (status 7). So I modded the file to make it boot and still nothing. I did everything I could and it just wouldnt work. I prefer AOKP so any help is greatly appreciated.
Then I booted CM11 and it worked fine. But now Tapped Out wont work. It goes to start, gets just past the initial screen and force closes. So any help is appreciated on that.
I am pretty sure that if I can get AOKP to run then Tapped Out will work. So there in lies my issue.
I am using TWRP if that helps. Thanks in advance.

In the meantime I went to AOKP JB MR-1. Its their last JB and its a milestone. But I would like to get 4.4 until Dandroid does Wi-Fi calling.

Please update your Recovery to the latest version.

im on a note 2 running the latest PA and also have this issue. my recovery is the latest Philz.

This is not a forum for your device.

Perseus71 said:
Please update your Recovery to the latest version.
Click to expand...
Click to collapse
I am on the latest recovery. Still no workey. I think its an issue with AOKP. I will give them some time before I try again.

Problems after installing CM12.1 nightlies

Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)

Copy important files to computer. Factory reset. Set it up as new device.

ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help

jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.

decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova

Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?

jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.

decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova

[Q] PA 5.1 OTA issues

Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance

paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...

You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi

I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?

paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.

@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.

paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!