Related
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
EtherBoo said:
Hi All,
I'm having an issue with my G2. I've been running the CM11 nightlies for a while now, they've been pretty decent.
I decided to flash the newest Snapshot today when I saw it pop up on my update list. As soon as I booted, I got the error "Unfortunately, the process com.android.phone has stopped".
This happened yesterday, so I booted into recovery, cleared cash, reinstalled the rom, cleared cache again, reinstalled gapps, cleared cache again, and it worked. Now I'm not getting so lucky. Anyone have any ideas on how to fix this? I'm really hoping this isn't going to be an issue with every CM nightly moving forward.
The best solution I could find seems to be specific to HTC phones, which involves reinstalling the boot.img. I don't think that applies to us, but if it does, how can I do that.
Thanks for your help.
Click to expand...
Click to collapse
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
xxxrichievxxx said:
You've done a clean flash? Meaning you wiped Dalvik, Cache, System, Factory reset? I usually erase twice and then install CM and then GAPPS then restart the phone (Don't install custom kernel) some custom kernels are having trouble because looks like they updates some things in their kernels.
Click to expand...
Click to collapse
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
EtherBoo said:
Thank you.
After some more digging, I had the idea to check the development thread of the CM ROM here. Apparently, a few other users have had the same issue.
It turns out, the newest version of CM needs to be cleanly installed, a dirty flash won't work. I just did a wipe and it's now downloading all my apps and reinstalling.
*sigh* such a pain, but whatever. Could be worse.
Click to expand...
Click to collapse
Yeah it can be such a pain, I flashed nightlies when they sounded like they fixed an important issue (it'd be every other day) and I flashed clean all the time. Now im just going to stick to CM11 M4 until the next milestone.
try changin network type to GLOBAL.
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later
If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.
vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.
I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!
Hello all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
x2b said:
Hello all,
I installed this ROM on my phone: http://forum.xda-developers.com/galaxy-s3-neo/orig-development/rom-cyanogenmod-12-1-s3-neo-t3099384
Notably I used the 20151111 version. Everything worked fine. I did however decide to try to encrypt the phone. Everything looked ok, but now the phone is stuck at booting. Notably, at the "Starting apps" stage of the boot process. Unfortunately this is too early to get a logcat. I already tried wiping the cache partition, doing a factory reset and reinstalling the image.
Any ideas on how to unbrick the phone?
Click to expand...
Click to collapse
Reinstall stock rom via Odin btw encryption screws up the phone in every aspect I recommend not doing so
Hello!
I am using LOS 13... no gapps!
I update only when Android Security Bulletin (ASB) gets merged...
I was on July ASB nightly... everything was fine...
Updated from around July 22 nightly to August 12 nightly... Big Mistake! Things went bad.
Oh, I have to flash LOS SU binary everytime, which I did.
Getting bootloops, taking too long, and it goes to optimizing apps, then, before finishing, reboots!
I tried flashing older nightly and newer, 26 aug, one from feb, and again 12 aug, ... with and without SU binary... no luck!
Same problem as mentioned above! When I do manage to get in, apps are force closing, Trebuchet errors, settings options freeze/close, file manager, etc. Some apps works, some force close. And, root is not available even when flashed.
Is this even related to related to current SUPERSU problems being reported?
I looked at recovery.log and kernel.log -- don't know wtf to look for.
I am going to factory reset and start fresh... pain in the A$#
I am asking if anyone else had problems and what could be the cause because I don't want this to happen again when I flash an update next month. I have had no problems since Jan this year!
Thanks!
Identical situation here, never had problems before... Still hoping to avoid factory reset...
Same problem for me, on DU rom, had random reboots constantly since a few days ago. Tried doing a factory reset first, then a factory reset and reinstalled rom and gapps, but every time before the optimizing apps dialog disappears it reboots. I'm going to try installing a different rom.
Update: Wiped system/cache/dalvik/data, installed RR, same problems as before. Tried skipping account setup, android worked fine. Logged in and again the constant reboots.
I guess the nexus is unusable for now.. Hope someone comes with a solution asap
Same here as well... Factory reset didn't help... Every attempt seemed to work in the beginning but bootloops started again soon afterwards.
Thank for replying!
Thanks: Thank you guys for replying! At least now I feel like I am not crazy or alone... especially with such an old device!
What I did: factory reset+Complete wipe (data, cache, system, etc.)/+factory reset... installed TWRP (update), then, LOS 13 8/26 nightly, (no GAPPS), alternative store... and then, apps <--- pain in the ass to do but I got there!
Things are working fine... but I fear still! I am running the basic (minimal, essential) config+apps, just in case things go wrong again!
Rant: I just don't understand how hard it could be to simply patch monthly security updates carefully, while keeping things stable. [I complain, but of course, I am not doing it ; ) ] I blame Oreo coming out 22 aug, as all eye balls moved to LOS 15 bring up!
Future: I might have to look into an alternative ROM myself... with ROOT and without GAPPS... but most important an active community. Let me know if you guys have any suggestions -- something working well with better (active) community support!
PS: August ASB has been merged (LOS 13) but no zip file has been generated yet! I hope that does not fsck things up again, when I flash!
Thanks!
Now it got me too. Yesterday i flashed the current / official LOS13 nightly 09/9 and since reboot i've constant bootloops.
Help! I've got a bootloop problem, the Nexus 10 will not hard reset, it just goes back into android os then re boots.
I first tried to backup and reset from within the device by using settings backup and reset
that sent it into an endless bootloop which then led me to try the hard reset with power and vol up down then power and vol up to access the erase all data setting but that still goes back to the android os, and before you have a chance to do anything re boots. So the hard reset is not working, what do I need to flash it via windows or mac and how do I do that? This is my 1st post so if anyone can help me thanks in advance. I am hoping that something along the lines of this will fix it. https://forum.xda-developers.com/nexus-10/general/guide-how-to-install-android-t3312390 any help is great appreciated
For me, it turned out that the latest nightly of LOS seems to have a problem with additional launchers. For me Nova was installed. After the factory reset and reinstalling of all apps I installed Lawnchair-Launcher and the problems started again. I managed to deinstall it and everything is running smoothly again.
In my case it's happening even without additional launchers installed, I just have Trebuchet that comes with LOS13...
Update from 8/26 to 9/9 -- all good, so far!
Hello!
The instructions from your link on how to clean install and update Nexus 10 are excellent!
I clean wiped and installed LOS 13 on Nexus 10 -- 8/26 nightly and then, updated to 9/9 nightly with August ASB merged! -- I have had it going for a few days -- and so far not experiencing any problems! I have additionally flashed SU to have root access and no GAPPS!
Some one else has a thread [https://forum.xda-developers.com/nexus-10/help/nexus-10-manta-lineage-os-13-bootloop-t3672215] and thinks that not launchers (or other apps) but something else within the system is the problem. I think I agree, because, I had basic LOS 13 running all along, with SU root and no GAPPS. Going from July to August, I had bootloop/force close/app crash problems!
Something is definitely going on -- so, I am running just a basic setup for now! Not sure if we will get LOS 14.1... maybe! I am going to update carefully and only after backing up data, when new ASBs get merged -- just in case this happens again!
Thanks!~
Da71 said:
Help! I've got a bootloop problem, the Nexus 10 will not hard reset, it just goes back into android os then re boots.
I first tried to backup and reset from within the device by using settings backup and reset
that sent it into an endless bootloop which then led me to try the hard reset with power and vol up down then power and vol up to access the erase all data setting but that still goes back to the android os, and before you have a chance to do anything re boots. So the hard reset is not working, what do I need to flash it via windows or mac and how do I do that? This is my 1st post so if anyone can help me thanks in advance. I am hoping that something along the lines of this will fix it. https://forum.xda-developers.com/nexus-10/general/guide-how-to-install-android-t3312390 any help is great appreciated
Click to expand...
Click to collapse
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I'd say do a clean install. If i have any issues with a rom booting i'll factory reset and install again. If i still have issues i'll just use another rom.
fraxby79 said:
Thanks to XDA, I've been running LineageOS 14.1 on my LEX727 for months now, updating to most nightly releases with no issues. However, when the phone rebooted after updating to the 10/20/17 nightly, it got stuck on the boot animation screen (green circle moving right to left on the arc) and would go no further. I rebooted into TWRP and flashed back to 10/13 which has been working fine. Same results after attempted updates to the 10/27 and 11/3 releases. I even tried a manual update from TWRP using USB OTG with the same result.
Any ideas of what's gone wrong here? Anything I can try? All I know to do at this point is wipe and install clean but I'd rather not if possible. Thanks!
Click to expand...
Click to collapse
I am in the same situation. Have tried all combinations of wiping and resetting with all 3 of the latest nightlies and still cannot boot. I can successfully boot into a stock rom but, I'd rather not. I guess I will go back to the 10/13 nightly since it worked (mostly) before this debacle. Hopefully next week's update will solve this problem.
Thanks for your reply, islandlife98. I'm not super-confident at this ROM thing yet so backing up, wiping and reinstalling is something I'd undertake reluctantly. I was hoping this was a common situation with a simple fix that I just had been unable to find. Always prefer to actually solve a problem if possible rather than just wipe it out. (Although when it comes to tech, wiping it out is often the best or only solution. Almost always the quickest.)
JBealZy, thank you for letting me know you're in the same boat! After seeing no mention of this issue here, I assumed it was some weird glitch with my phone rather than a problem with the updates. If you've done a full wipe and re-install but still haven't been able to boot into any of the last three releases then I'm glad I hesitated. (That was a concern I'd had: that it might not work even after a clean install.) Think I'll stick with 10/13 for now and keep trying the new releases; easy enough to roll back if it fails now that I've figured it out.
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
I am using Paranoid ( latest version) and everything works flawlessly.
Sent from my LEX727 using XDA Labs
Deediezi said:
Lmao same problem here with the 2017-11-11 and 2017-11-03 udpate. Not tested yet with 2017-10-27 or 2017-10-20 but that's my last choice because after 2017-10-13 update all links are removed. I do a clean install every time .. What other rom is better ?
Problem resolved .. i have wiped internal storage too and able to install the last version. I think i'm gonna use another ROM because i don't really want to reinstall all of my applications everytime i do an update. :/
Click to expand...
Click to collapse
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
fraxby79 said:
Another victim! So weird, I wonder what's going on there. None of the updates since my original post have worked so I've come to the conclusion that I'm going to have to do a clean install. Just need to find a time do it. Good to hear it worked for you.
LineageOS is the only ROM I've tried but since I have to wipe my phone anyway I may try some others. Paranoid Android looks interesting and Tsongming says it's working well.
Click to expand...
Click to collapse
Yea i'm downloading Paranoïd right now for testing it .. Don't want a broken operating system on my phone haha
If anyone's still interested, I first tried flashing Lineage after wiping all but internal storage and still couldn't get past the boot animation. Then did a full factory-reset wipe including the internal storage, re-flashed, and it finally booted. The first OTA update since then came through today and went off without a hitch so all seems well for now.
I did take a look at Paranoid before going back to Lineage. One big reason I use a custom ROM is to get security updates quickly and LOS reports the security patch level in the settings; I couldn't find this info in PA. Also, I use a pattern to unlock my phone and there didn't appear to be a way use a larger grid than the default 3x3. On the plus side (sort of), PA includes the LeEco remote control app, which seems to be the only way to use the IR hardware on this phone, but it asks for more permissions than I want to give (which, of course, is not PA's fault). So admittedly I didn't really give it a full and fair trial but those few little issues sent me back to the (usually) reliable familiarity of LOS.
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Heistergand said:
I received a new LEX722 yesterday. The TWRP for zl1 is working fine, but I cannot get lineagos working.
I deleted:
- dalvik,
- system,
- cache
- data
- and also the internal storage
after rebooting into twrp I enabled usb debugguung and pushed the lineageos and gapps images via adb push to the phone.
I installed lineageos and gapps nano, but after booting to system, I get stuck in a black screen looping to a dark grey luminated display (no graphics at all).
Click to expand...
Click to collapse
Sorry, can't help you with that since I have a LEX727 which is apparently quite different from the LEX722. Official LineageOS is only supported on the LEX720 and LEX727: [ https://wiki.lineageos.org/devices/zl1 ]. The LEX722 (Elite) has it's own section here on the LeEco Pro 3 forum so check that out and see what they've come up with.