Hello. I've been having problems trying to install any CM based rom for the last couple of months. My daily driver is the CM 11 M9 rom by percy (which is the last cyanogenmod rom I was able to install without any problem), but whenever install any other rom, I have the "unfortunately the process com.android.systemui has stopped" loop, right after the device goes to sleep for the very first time.
I don't have any idea why this is happening. I've tried with both cwm and twrp, just in case my recovery was messing up the process. I'm worried that when a stable CM12 comes out I won't be able to use it because of this problem. Any help would be appreciated!
Got that Problem too..
Related
Hey guys, I'm a pretty heavy tinkerer and I know that comes with some risk. But before I completely wipe and reflash everything I wanted to see if someone could help diagnose my problem.
I have a Nexus 5 and have been running MultiRom for a while. I currently have Paranoid Android and Android L dual booting. I was on the newest version of PA (4.6 BETA 1) but I just flashed back to a past backup so now I am on PA 4.4 (I think). I have been having random reboots for about a day and now I can't even get my phone to stay on longer than a few minutes. I just installed Xposed and a few Modules so I assumed those were giving me the trouble, but I uninstalled Xposed when I started having problems and that didn't help. Even my backed up ROM and my Android L won't work without rebooting. This leads me to believe its something deeper down than my ROM.
Before I clean off and reflash, is there any way I can diagnose or fix this issue?
Thanks a ton.
Hi guys,
After searching for a few days and doing stuff myself (perhaps not everything for the best), I finally get it over with and ask for advice.
I've got a GT-N8010, since long been running an unofficial CM11 build (since one of these CM11 builds, the device was known as a GT-N8013).
Last week I started looking at the unofficial CM12.0 and CM12.1 builds, those looked promising.
After some info, I flashed to the CM12.1 build. A few minutes later, Android 5.1 in all it glory... everything running fine. Saturday evening I noticed I didn't get root.
Without thinking straight, the next morning I started flashing superuser but as you might imaging, that totally f'ed the system.
Now logically, one could just reflash CM12.1 and be done with it .. somehow I skipped all logic and started tinkering in recovery (TWRP).
After some doing, I managed to even F-up TWRP, it wouldn't boot anymore. The TeamWin logo was visible, screen flashed, logo and back.
No worries, there's still the download mode .. yeah about that ... already in panic mode .. doing more harm than good.
So .. Now I'm at this curious state.
I've managed to get it booting to a stock ROM. TWRP is also running.
The weird stuff I'm encountering now:
The device is semi recognized as a GT-N8000, if it was just that, I really don't care.
I said semi, when I want to flash another ROM (even specifically the CM12.1 for GT-N8000) it always states (in ADB Sideload in TWRP) that the package is not for this device.
There's a whole lot of devices listed, then it states "this device is ." , as in blanco device?
Anyone got an idea how to fix it so I can enjoy the Android 5.1 build again? (and seriously, remove the stock rom would be the first priority)
Thanks.
Greetings. How can I fix this error on boot on my OPO. "Unfortunately, settings has stopped"
Ive rooted my OnePlus One, added TWRP and installed LiquidSmooth (LS-LP-v4.1-2015-04-20-liquid_bacon) with gapps. L-4-21-15.
If I only install LS, my device starts, no *****ing. Add gapps, it *****es immediately at boot that settings has stopped.
So, I installed Pacman Rom and a differnt gapps.... dunno what versions. The current. Same error.
I'm back to LiquidSmooth (LS-LP-v4.1-2015-04-20-liquid_bacon) with gapps. L-4-21-15.
At every boot, same error. Haven't driven phone yet to see how it runs but, an error at boot... isn't right.
Thoughts? Fixes.
(I tried to add all pertinent information here. And, not ramble on. Any suggestions to better my post, please tell me)
hi..
i hav this problem with my tab 2 p3100..and its bit annoying me for som time nw.
i was using the cyanogenMod (CM 12.1) by @Android-Andi ..the earlest build..bt due to some soft reboot problm i changed to official cyanogenmom 11 nighties. and its respective gapps..
aftr some days its started showing "unfortunately process.com.google.process.gapps has stopped" message continuously..it was annoying ..it also shows fc messages of most of the apps installed including trebuchet app.
so i thought its a rom issue or gapps issue..so chaged by rom to stable official jellybean cyanogenmod and its gapps..but agn i encounter similr annoying problem of "unfortunately process.com.google.process.gapps has stopped" message and other apps
atlast i chage bac to Android-Andi's cyanogenMod (CM 12.1) and lollipop Base Gapps package for 5.1.1 by Deltadroid..
bt i am stll having same problem..first i thought its a sofware problm ..nw am confused whtr its a hardware problm..
please help me
I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.
Hassan 4 said:
I had some of this trouble once, It was fixed by installing stock rom for a few days then returning to CM11, it seems something wrong with our eMMC, may be disabling on the kernel trim caused it, on stock trim is working, Anyway on returning to CM11 it's much slower than it used to be before, So I am now with Next Rom from ketut.kumajaya, A good smooth stock based rom and could be the smoothest among stock based roms.
Click to expand...
Click to collapse
thnks for the replay..nw am on stock rom..working fine
pauldominik said:
thnks for the replay..nw am on stock rom..working fine
Click to expand...
Click to collapse
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.
Hassan 4 said:
Urw, If it doesn't get fixed for CM11, you may try Next rom, It's a non-laggy stock rom even in games it's as cm11.
Click to expand...
Click to collapse
ok...i wll try..bt crrnly i am running it on slimkat..and its wrks ok..so wll keep it runnig fr som days..
It will come back again after a few days. I haven't discovered any permanent fixes but resetting app preferences in app settings helps. If even Settings is also FCing then go to recovery do backup and restore. You don't need to have old backups, you can backup the broken ROM itself and restore it. That way you can restart and not face Settings FC. Then you can reset preferences and the problem will go away for sometime.
Issue might be lollipop or the recent stock gapps post-PA Gapps era. Stock gapps get very close to occupying system partition during installation itself. Try having a smaller Gapps and download any google app you require from playstore
Hey
I'm facing a problem with CM13 and i was wondering if anyone can help ..
Here is what happened;
Yesterday I updated my software and didn't notice that it was updating from CM12.1 to CM13
After installing the update it started giving errors similar to "Google Play Services has stopped" bla bla bla
So I said maybe I should flash new compatible GApps
I downloaded OpenGApps arm-6.0 and installed it, it went smooth
When I restarted into the system it was worse! more and more errors with even black home screen
So I wiped the cache/dalvik/system and decided to install them fresh
It went fine, finished optimizing apps then out of nowhere it rebooted and stuck on the Cyanogen loading animation
While searching I found this; github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
It mentions that I have to download a certain patch -Which isn't found in AOSP ROMs- to prevent force closures at first boot
I'm not sure if I need that for CM13 or not and also I don't know how am I supposed to compile that patch with the rom?
TLDR; Problem with installing OpenGApps and CM13, wiping cache/dalvik didn't fix
Any help would be appreciated, Thanks.