I have seen this error around on the forums a little but have not seen any answers so I thought I would try here since I have a Oneplus One. I am using TWRP to wipe and flash the latest (Jan 20th) CM12 rom plus the full gapps. I was on CM11 before this. After it boots up and goes to the setup screen it gives me an error "Unfortunately, System UI has stopped." You click ok but it just pops up again. It is possible to get through the entire setup by hitting next fast in between pop ups, but once it finishes it still pops up.
Tried wiping again and reinstalling, but got the same error. Rebooted a bunch, made no difference.
I suppose I can go back to my restore, but was hoping to try out CM12
Any ideas?
Thank you!
Think it's just a problem with this particular build (20th). I had the same issue. If you're really desperate you could try a slightly older build 18th or 19th and see if they work. I'm just gonna wait a few days and hopefully it'll be fixed
Sent from my One A0001 using Tapatalk
facing the same situation
I am facing the same situation today!!
Same here reverted back to 19th build
Related
I have the Verzion Wireless 3g/4g Xoom. When I tried to flash the latest CyanogenMod (nightly 10.1) from here (http://download.cyanogenmod.org/?type=nightly&device=stingray) and gapps from here (http://d-h.st/kIQ), immediately after the bootanimation, I get the error message "Unfortunately, system UI has stopped". Everytime I hit "Ok", it just keeps popping up again.
Anyone with any ideas how to get out of this?
When you do can you let me know, thanks
blairpoodle said:
When you do can you let me know, thanks
Click to expand...
Click to collapse
You mean you asked already? How long ago, because I've searched and couldn't find a like problem.
Sorry. I should explain I had the same issue. Couldn't solve it went bact to 09/03
Sent from my Nexus 4 using Tapatalk 2
I had the same issue with the latest Wingray build (WiFi Xoom MZ604). I went back to the 3/10 build and all is well.
Kamau54 said:
I have the Verzion Wireless 3g/4g Xoom. When I tried to flash the latest CyanogenMod (nightly 10.1) from here (http://download.cyanogenmod.org/?type=nightly&device=stingray) and gapps from here (http://d-h.st/kIQ), immediately after the bootanimation, I get the error message "Unfortunately, system UI has stopped". Everytime I hit "Ok", it just keeps popping up again.
Anyone with any ideas how to get out of this?
Click to expand...
Click to collapse
easiest thing would be to boot into recovery and restore a backup. The system you flashed is bad. You can also flash a different rom from recovery but do a full wipe before flashing.
I also had the same problem on my Xoom wifi. Flashed the CM 10.1 20130310 nightly and everything was fine. Have not heard of any fixes or bug issues as of yet. Will post if I do.
Sent from my Xoom using Tapatalk HD
Looks like the bug issue for system ui message has been fixed in the newest cm10.1 nightly (20130314) for xoom>wingray. Thanks to the devs.
Sent from my Xoom using Tapatalk HD
I went from bone stock to the most recent PAC-man nightly (22.0.1) and its fine with a couple of exceptions. When the phone tries to re-download my apps each one gives me an error message. That's not a big deal since I can still manually re-download them. But the issue that does concern me is that every time I try to use voice-to-text, I get "Unfortunately, Google Search has stopped." Maybe not the worst thing in the world but it's getting in the way of my normal usage. I've tried wiping and re-flashing and I've flashed the latest modem but no luck so far. I tried the CM10.1 M2 snapshot too but I get the same issue. What am I missing?
SuperBrother said:
I went from bone stock to the most recent PAC-man nightly (22.0.1) and its fine with a couple of exceptions. When the phone tries to re-download my apps each one gives me an error message. That's not a big deal since I can still manually re-download them. But the issue that does concern me is that every time I try to use voice-to-text, I get "Unfortunately, Google Search has stopped." Maybe not the worst thing in the world but it's getting in the way of my normal usage. I've tried wiping and re-flashing and I've flashed the latest modem but no luck so far. I tried the CM10.1 M2 snapshot too but I get the same issue. What am I missing?
Click to expand...
Click to collapse
Apparently, I didn't search hard enough for an answer before. Turns out I just needed to update Google Search manually. Help on particular apps not downloading is still welcome though!
Hello, I thought I'd try to post this here to see if any one else is experiencing this issue. I am running PAC 2.3.0, the 8/20/13 release. I have my tablet updated to the 4.2 boot loader via Version US_V10.6.1.15.3, and flashed this with TWRP 2.6 after wiping system, data cache and dalvik. After flashing the rom and the most current gapps (8/12/2013) every thing boots fine. Then I get to the setup screen and there is an error message displaying the AOSP keyboard has stopped.
I hit ok then try to enter my wifi password and some error just flickers too fast to see. I attach the keyboard dock and still no luck for typing. The home and other keys seem to function properly. After skipping through the setup I notice that the choose keyboard lay out notification in the status bar, but when choosing it the error message pops up that Settings has stopped. I have downloaded this twice onced on my pad and once from the pc. Nothing seems to be diffrent.
I know that this is still early in the game for 4.3 but, I can't be the only one experiencing this. I haven't seen any other posts on this, so if any of you out there have any ideas I am all ears. Thanks in advance.
It happened to be, but only when I tried swiping. What you are experiencing seems to be a bit more complex.
Are you able to install a different keyboard, like Go Keyboard?
I haven't tried that. I'll give it a shot.
Sent from my TF300T using XDA Premium HD
That happened to me as well but I flashed again,the rom and gapps and it worked fine
mikep2323 said:
That happened to me as well but I flashed again,the rom and gapps and it worked fine
Click to expand...
Click to collapse
I will give it another try.
thanks!
JakaraRuus said:
I will give it another try.
thanks!
Click to expand...
Click to collapse
I tried again last night. I did a dirty flash over 23 with a dalvik and cache wipe and a re-flash of the latest gapps. same deal. Then I tried with a full wipe and flash of the rc1 from 8/25 same thing except now it tells me who to blame when the keyboard stops. lol.
I have a d2vzw galaxy S III and it give the same keyboard error. So it isn't just our build.
*I found a solution a while ago, but have been too busy to post. I downloaded the official PA gApps for 4.3. Problem solved. The gApps on goo.im were form 4.2.2.*
Admin please close
I got a Nexus 5 been using CM on it for a while now. Currently i have 11-20140708-SNAPSHOT-M8
the build date is july 8. I've been getting CM update for a new version for like a month now, tried installing it a couple of times, when i press to reboot and install it says it installed it, and after the phone reboots, it's still the same old version, and i keep getting the notification to upgrade, but i can't.
So I waited for another new build, thinking this is just some bug in the update. Yesterday a new version prompted for a update, but the same happened. So i tried to download the zip from CM website and flash it on recovery manually. And i got an error:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
I used to update with no problems, but I seem to be stuck on the july 8 build.
Anyone else dealing with this, or know how to fix this?
Is your bootoader up-to-date? CM often require you to have latest bootloader
No. I haven't upgraded it. I've found multiple threats about it, I'm not sure which one is the right to do so. As i'm not really familiar with this kind of stuff.
EDIT: My BL version is HHZ11K. From what i gathered it's the most recent one.
TheSidiO said:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
Click to expand...
Click to collapse
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Wakamatsu said:
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Click to expand...
Click to collapse
Was thinking if I can salve the problem without doing that. But i did a factory reset and it fixed the problem.
Thanks for the responses.
problems updating monthly snapshots of CM
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
acf150 said:
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
Click to expand...
Click to collapse
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
updating CM snapshot monthly problems
TheSidiO said:
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
Click to expand...
Click to collapse
Almost what I did, i l always do a nandroid backup before flashing anything in recovery, I downloaded the snapshot and the gapps, wiped, and installed snapshots along with gapps. So your telling me to just do a backup in recovery before updating that it cleans my files, then without wiping to try to update just the CM update from either my phone or their website? No gapps? Will try next time thanks.
I've been using Lineageos 14.1 (and Xposed) on my Nexus 5 for yesrs and am happy with it. But in the last week I've been having crashes, usually when waking the phone from sleep. When that happens I can sometimes just reboot but other times I was faced with repeated bootloops and I've had to go into twrp recovery and "reboot system" to get back to a working phone.
To resolve the crashes and boot loops the first few times this happened, I deleted the Davlic cache and cache. The problem persists.
I updated lineageos to the latest Jan 3, 2019 even though I don't think this has anything to do with linesgeos which has worked for years, but the crashes continue.
I just don't know "how" to troubleshoot this problem beyond what I tried. What should I do to find out what is causing the phone to crash?
Any troubleshooting suggestions appreciated.
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
audit13 said:
To determine if it a software issue, I suggest flashing the latest stock Google ROM. If the crashes stop, you'll know it is a custom ROM issue.
Click to expand...
Click to collapse
Thank you for replying . I'll try that although the problems started without my having upgraded from the same rom I've used for a long time.
Would some kind of log help?
Thanks again.
A log would certainly help the developer.
Have you posted your query in the ROM thread?
Yes and got no reply so far.