I've been using Android Revolution 9.2 and this morning installed 10.0. Everything was working fine for a while, then all of a sudden the GAPPS process started force-closing and I lost all access to the Play Store. I would click on the play store icon and it would just bounce me back to the launcher (in this case, Nova Launcher 2.0). I decided I need to reflash Android Rev HD 10.0 (I have CWM Recovery 6.0.1 installed). The AROMA installer would start, but it would always lock up at some point before the installation began, usually at the prompt to backup the efs partition, sometimes earlier, sometimes later. I haven't been able to get a clean flash started. I even tried to go back to 9.2, but the same thing is happening.
I did a factory reset hoping it would fix the problem, but the GAPPS process continues to crash and I can't access google to restore my apps. So I'm really up **** creek here. Am I looking at a bad RAM problem all of a sudden? (god, I hope not!).
Any help/advice would be welcome.
mudge
Hello everyone,
So I installed CM13 as an update from 12.1 but it was stuck on the boot logo, then it counts up the updates, then does the same thing again in an endless loop.
I decided to do a clean install, so I wiped cache, system and data and installed CM13, then I installed Gapps6 stock with the exclusion of some general apps I can get from Play store, since installing stock without excludes renders error 70
Anyway, everything went well, but on the wizard setup I was expecting to see Google ask me to import apps from specific devices that was used on specific dates. But all I got was the NFC restore method.
What did I miss here? and what can I do to get to restore all my setting from before I updated the phone?
I know that option existed in Lollipop, as I have used the option when I clean installed CM12.1 many times.
Thanks all
I have heard, but have not yet tested, that you need to delete the cmsetupidwizard (or whatever it's named) before the initial boot.
On LineageOS 13, the latest official build of LineageOS for the Nexus 10, when I iinstall the Nova Google Companion for Nova Launcher, Google Play Services, Nova Launcher, and a number of other apps crash. When returning to the home screen, it freezes, then sends the app into a boot loop where after the LineageOS logo appears in it's entirety, my device tries to start LineageOS, but then crashes again and so the boot loop process continues. I have already reported this issue to the Nova Launcher Beta Google+ community and mentioned that Nova Google Companion ran fine on the stock 5.1.1 ROM. I've already tried reflashing LineageOS and GApps. Suggestions as to what I should do without flashing a different ROM?
Update: So as it turns out, ANY UI modifications (Launchers, TeslaUnread, Nova Google Companion/Action Launcher Google Plugin) will send the device into a bootloop. I suspect that the issue is with themes provider or GApps, since Google Play, Play Services, and Themes Provider are the first to crash.
I have a similar issue but I am unsure what program causes it.
The tablet was newly installed and installing my list of apps, one being Nova.
EDIT, information provided by op:
The August 5th nightly accepts Nova Launcher, but not TeslaUnread, Nova Google Companion, or Action Launcher
Hello, I have similar issue with my Nexus 10 on lineageos 13. I've reset from factory, reinstall all my apps except Nova and it works fine.
When I decide to reinstall Nova, my nexus immediatly boot in loop...
It arrive sudunly probably after an uptade of Nova...
Olivier.
Similar issue on Galaxy S3 running Cyanogenmod 13 (20161220 Snapshot).
Installing Nova Launcher causes the device to freeze and go into bootloop where it reboots after "optimising apps".
I've also tried installing Google Now launcher but " Home" option doesn't show up and there is no way to switch from Trebuchet to it.
Similar issue on S2 Plus CM13 after an update
Tested 2 weeks without Nova and nothing happened
Decided to give a shot again then bootloop happened again, luckily I had backup this time
I'm facing the same problem right now with my Redmi 4A. How did you solve it? Doing a factory reset?
I am currently facing a similar issue, but the culprit here for me is the facebook app, as soon as I install it from play store, it sends my samsung gt-i9082 (running cm13) into an instant bootloop, I tried deleting the facebook app's data from the twrp recovery's file manager.
but even then it kept on rebooting.
I had tested this even after a complete format of my device, including internal storage and external storage. even removing external storage, still as soon as the app was installed it went bootloop.
It's strange for me, cause it's the same rom and the same device, that was running the same app version before i format it to clean everything.
I would have doubt a data clash between my older files, but that was ruled out after a complete format. I have no clue why this is happening.
Edit: The only difference between my previous and the new installation is that I used deltagapps before and I am using opengapps now.
I will try with deltagapps again to see if it is sorted.
Edit 2: Well it did stopped the bootloop with the facebook app, but then again it started giving me the same issue with all the other random app I try to install(All those apps that previously were working on the same rom, same device).
Now the only suspect remains is the emmc of the device, maybe that is failing or got bad sector. strange that I haven't seen any issue on the device forum about this. Bad Luck, It reaches it's end.
The fix for this issue is available here (13):
https://forum.xda-developers.com/showpost.php?p=74636021&postcount=216
CM 12
https://forum.xda-developers.com/showpost.php?p=74842530&postcount=464
While updating/installing apps from the google playstore, the phone will crash and bootloop, and requires a full reinstall to get it working normally. I've attached 2 logcat files for both roms which give the same problem - Mokee5.1, CM13 on a clean installation with pico gapps and manually selecting several apps to install. One other custom rom also gave the same problem so I didn't bother trying any other custom roms. Reverting back to stock MIUIv8 gave no issues.
CM13 used to be mostly problem free until a few months ago I think when the update/install issue started happening. The playstore auto update is normally kept disabled on my phone so I'm unaware about when the problem really started happening.
Edit-
It doesn't seem to be happening anymore from a short test after flashing my CM13 backup but I've moved on to LO14.1
It may have something to do with some other complaints that people are having. It looks like some issue with Cynogenmod since Sept/Oct 2017 which needs some patching.
https://forum.xda-developers.com/general/help/bootloop-updating-apps-telegram-t3700773
Update to/ Installation of newest version breaks system
https://github.com/signalapp/Signal-Android/issues/7171
Several apps causes a phone reboot or boot loop
https://gitlab.com/fdroid/fdroiddata/issues/979
Can confirm the issue with CM13 on my Galaxy S3. Unfortunately, I do not know a solution. Just stick to older app versions.
Hi everyone, I have a xiaomi note 4 (mido) and I have been using lineage os for a while.
I updated to Lineage OS 16 from 15.1 few weeks ago, and everything was working just fine. I was running the 20191108 nightly build. Just today I checked for updates and updated to 20191122 and used for an hour or so and then got a notification to update to 20191124, so I updated again.
After this update the phone is very buggy, most google related apps open for a second and then close without error, the Gboard shows up for an instant and then disappears, play store won't launch, normal apps take too long to load, even the phone app. When I reboot the device the home screen keeps refreshing for a minute or so.
I downloaded and flashed the 20191122 build again but received the same result, I even flashed the 20191108 build that I've been running for weeks with no issues but still had these problems.
Does anyone have any idea what happened and how to fix it ?? I haven't made any settings changes or installed any new apps during the updates.