I've got a Moto G 16GB XT1033, stock 4.4.2, unrooted, locked boot loader. I installed this game (https://play.google.com/store/apps/details?id=com.glu.dino) and went away for a bit while it was being downloaded. When I came back, AcDisplay had the notification that the game was installed. So I dismiss the notification and enter the pass code to unlock the device. That's when the trouble started. I got the message that the com.android.systemui process had stopped. Everything would disappear for a bit and then its back to the lock screen. I tried rebooting and a dialogue that 'Android was upgrading' and 'Optimising app 1 of 1' would show for a while and then it would reboot itself. This time, the boot animation would be all wonky but it would get to the lock screen but if I enter the pass code, the systemui message appears. I tried safe mode but no dice.
How do I go about solving my problem? I just think its ridiculous that installing an app from the Play Store can cause my phone to be unusable.
Spectcrono said:
I've got a Moto G 16GB XT1033, stock 4.4.2, unrooted, locked boot loader. I installed this game (https://play.google.com/store/apps/details?id=com.glu.dino) and went away for a bit while it was being downloaded. When I came back, AcDisplay had the notification that the game was installed. So I dismiss the notification and enter the pass code to unlock the device. That's when the trouble started. I got the message that the com.android.systemui process had stopped. Everything would disappear for a bit and then its back to the lock screen. I tried rebooting and a dialogue that 'Android was upgrading' and 'Optimising app 1 of 1' would show for a while and then it would reboot itself. This time, the boot animation would be all wonky but it would get to the lock screen but if I enter the pass code, the systemui message appears. I tried safe mode but no dice.
How do I go about solving my problem? I just think its ridiculous that installing an app from the Play Store can cause my phone to be unusable.
Click to expand...
Click to collapse
Can You see your Statusbar and Navigation buttons? Are you sure you are not rooted?? Just reconfirming:silly::silly:
Nope, not rooted. As for the status bar and nav bars, I can see them before entering the pass code but as soon as I enter it, I get the message and they disappear.
Spectcrono said:
Nope, not rooted. As for the status bar and nav bars, I can see them before entering the pass code but as soon as I enter it, I get the message and they disappear.
Click to expand...
Click to collapse
Try swiping to the camera and then pressing home
Related
hey guys, i hope you all doing fine.
i must admit that i really [email protected]#ed up this time. I was messing around with the software "rom toolbox" and i tried to freeze all of the system apps. after the progress bar reached 100% percent the phone started to constantly pop-up a message box which says that the "Dialer" app is crashed. after i click "force close" on that, it pops up again with the same message. between the pop-ups theres like half a second time which i can access the rom toolbox program so i tried and defroze the dialer application. now the pop-up is gone. after that i tried to enable the "Home" app to be able to access the home screen. But it somehow didn't response and i was forced to shut down the phone by pressing and holding down the power button. Now when i turn on the phone, first the LG logo then the LG animation come on screen but after like 10 seconds nothing happens the LG logo stays on screen and then again the LG animation.
I have clockwork mod recovery v5.0.2.0 installed and be able to boot into it but it doesn't have an option to defreeze apps. i don't have any nandroid backups and i don't want to hard reset either.
What can i do?
Install again some rom
I honestly need help.
I'm not sure what to categorize my issue under.
I am stuck in a screen with the green android and the spinning thing in the middle, with a progress bar, but the bar just has a moving animation, looks like it is moving to the left, not getting longer or filling up like usual progress bars.
I am unable to get to the boot loader or recovery.
The issue started after I flashed Cyanogen Mod 10.2 Stable.
it booted fine then, but when I went to use it, it would have a never ending cycle of app not responding at the part where it asks to sign in to cyanogenmod account. I got to settings without signing in by quickly sliding the status bar and clicked on factory reset.
From there it proceded to reboot and now I am stuck in the screen described.
I have tried all the button combinations, reset with pin, nothing will get to bootloader or recovery.
ADB does not find the device, also no devices found when try fastboot devices line.
I have also tried putting the firmware zip on a microsd, but nothing new happens either.
any suggestions appreciated.
** edited ** Issue is resolved. Turns out I just needed to wait longer (about 2 hrs) ... I did turn it off using combo of power and Vol -, left it off overnight, turned it on in the morning and left it alone. I finished whatever it was trying to do, and now CyanogenMod 10.2 stable is working great.
[SOLUTION] How To Fix "CM Lockscreen Has Stopped Working" Error in OnePlus One 38R
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Marvelite said:
DISCLAIMER: I do not guarantee that this method will work for you, but it doesn't require ROOT or a custom recovery, etc. So, it's safe.
So, three days after OTA updating my OPO to XNPH38R, I randomly got the "unfortunately, CM Lockscreen has stopped working" error, and my phone became virtually unusable. I was devastated! I didn't want to wipe my phone. So, I decided to just got into Recovery and wipe the cache. But my custom recovery was freezing, so I decided to boot up my computer and try to re-flash recovery... And while I was waiting for my computer, I stumbled upon this work-around. I hope it helps someone.
WORK-AROUND METHOD:
Step 1.) Reboot your phone. (You'll have to hard reset it by holding the power button down for 5+ seconds.)
Step 2.) After the phone restarts and you're faced with the persistent error of death again, just press the power button once to turn off the screen. Then, turn the screen back on.
Step 3.) When you turn the screen back on in Step 2, the screen should be totally black with the capacitive buttons still lit. If this doesn't happen, try repeating Step 2 until it does.
Step 4.) Just leave the phone on with a blank screen and lit capacitive buttons for 20+ seconds. This seems to be an important step.
Step 5. Turn your phone screen off and back on again. For me, this fixed the persistent error. Yay! Hopefully it works for you. However, for me, the error came back again in only 5 minutes, and I had to repeat the entire procedure. Which is why we need Step 6.
Step 6.) Disable the lockscreen. This can be done by going to System Settings > Lockscreen > Screen Security > Screen Lock, and then choose "none" to disable the lockscreen entirely. This has kept the persistent error from recurring for me for 12+ hours.
And, that's it! That's all. You get to keep your data and information. And you get to keep the latest OnePlus One software version... However, unfortunately, you lose all lockscreen Security. But, you could maybe try installing a third-party lockscreen like "GO LOCKER" until OnePlus recognizes this problem and fixes it in the next update.
Good luck everyone! Lemme know if this works for anyone else besides me.
Click to expand...
Click to collapse
This is not working for me as i cant get my phone to the stage where the screen is black with only the buttons lighting up
Alternative solution
I too faced the same problem with the lockscreen after changing my wallpaper.
However the method mentioned above did not work for me.
I tried this instead.
1. Restart your phone by holding down the power button for a few seconds.
2. Turn off the screen.
3. Use the play music gesture: swipe down 2 fingers to start the music player. (tried the camera gesture but did not work).
The lockscreen problem disappeared since then. I have also turned off the lockscreen in the settings in fear of it reoccurring.
Hope this helps any of you suffering from the same problem.
Cheers!
I found another way to get your phone unlocked
So the solution that was provided by Marvelite did not work for me. I tried many many MANY times, but to no avail.
After looking around the interweb, I found some other instructions to root my phone (FYI I had no experience in rooting) and I was able to fix it without flashing or re installing anything.
So... what did I do. All I did was unlock my phone. I got my phone and remember saying it was unlocked, as you could use any carrier. That is not what I mean by unlock. What I mean by unlock is you cannot flash it or erase it. See the command line window below saying the phone is not unlocked and that is why I cannot flash it. I thought I had to flash it or erase it to get everything working. Just unlocking it fixed the CM Lockscreen Has Stopped Working error.
So what will you need to install on your computer and do to your phone.
1) Download adb-setup- 1.3.exe (if you type "adb-setup- 1.3.exe" into google, you will find a download) and install ADB system wide on your computer.
2) Put your phone in Fastboot mode and plug it into your computer. To do this, have your phone completely off and then hold the volume up and power button. You will see the screen of your one plus one in fastboot mode.
3) open up a command line window (as in my attached picture) and type fastboot oem unlock
THIS WILL RESET YOUR PHONE! After I typed in fastboot oem unlock, my phone reset itself and it was though I had hit the factory reset.
You can see from the command line window attachment, that I tried to flash my phone based on this workflow (http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061), but I did not even need to do this, because my phone was not unlocked. Then when I unlocked my phone, the problem was fixed.
I hope this works for those that have this horrible bug.
Hi - I have tried multiple Lollipop based ROMs on my OPO. All the Lollipop ROMs have exhibited the same failure on my OPO: When the phone wakes up, I will randomly see a totally black - and basically unusable - desktop, but have a fully working Status Bar and working pull-down Navigation Bar. Holding the power button also brings up the shut-down options. so, I know that my phone isn't dead or frozen, I just can't see anything on my desktop. If I press the power button momentarily to lock the phone, I will see the unlock 3x3 pattern grid when I power on, and I can unlock the phone - but, I see a black desktop.
I recently loaded the official CM12 nightlies, and I am seeing the exact same thing. One thing I have finally determined (which I suspected previously), is that there was some sort of App crash during the phone sleep that had a pop-up message on the screen when the phone woke up. After a lot of random finger mashing and loud screaming at the phone, I saw my desktop again, and saw that "Google App" had crashed. After clearing the error pop-up, my phone has worked fine without rebooting ... for now.
The problem with this is that the black desktops become more frequent as time progressed, eventually reaching the point where I would reboot my OPO and it would power up to a black desktop. In the past, I occasionally saw a flash that looked like a pop-up message before the black desktop, and now I have confirmed that is what is happening.
Does anybody know what is going on?
The problem can be the gapps package you're flashing. Try another one.
MickyMax said:
The problem can be the gapps package you're flashing. Try another one.
Click to expand...
Click to collapse
Thanks! Do you have a suggested gapps I should try? I loaded pa_gapps-modular-mini-5.0.1-BETA7-20150111a-signed with this build.
How to restore into operation LG G2 D800 phone that says "Fastboot mode started"?
Current problem: phone is not operational (does not boot properly).
What I see:
Boot Screen 1:
Phone appears to boot as normal, makes the start-up sound, then it shows a white message box on a gray-screen background. The message box says "Unfortunately, Settings has stopped."
It gives me an option to click "OK".
Clicking OK, message box disappears, screen momentarily flashes an all-white background, (which sometimes changes into black and sometimes not), and then it goes back to the message box.
Boot Screen 2:
"[xxxx] Fastboot mode started" on a blank screen,
where xxxx is a number. 6180 one time, 9790 another during 2 individual boots.
Then the phone just sits there doing nothing seemingly indefinitely.
I am not sure yet how I bring those two different boot modes up but via pressing Power and / or Power and Down buttons in some fashion.
How do I fix this? Is my device bricked?
How I got to that screen
I was using a web browser or some other app on the phone when I have received a text message. I clicked on it inside text box to reply. But changed my mind, and clicked back on the background app. Suddenly the phone shut off unexpectedly. I thought it was related to phone drawing suddenly high battery power, not receiving it and shutting off as sometimes happens on very low battery power level 2-4%. However, my battery was charged over 40% so that was most likely not the cause.
Possibly relevant history (anything that could be contributed to the above):
phone worked okay for a while (since purchase)
~1 year in I tried rooting phone with towelroot/other options unsuccessfully. Gave up. Was never able to root the device. Lived with is as is for a while.
~2 years since purchase, somehow Bluetooth option started failing to turn on. Trying to fix that via doing a Factory Reset did not help. So I lived with BT being non-operational
A week ago I swapped SIM card with my buddy for a week, then swapped it back. Phone kept working as normal.
Today I charged the phone perhaps not using the best power source - it is possible I may have damaged phone using a questionable quality charger. Possibly. This could be the issue. However the phone seemingly worked fine after that for 2-3 hours.
Since my unexpected Shut-Off (most recent), I tried rebooting the phone, but that does not work as expected. First time it got stuck on LG screen forever. Kept pressing Power button, or Power & Down buttons to try to make it come alive. Other two times it brings up a message with "[xxxx] Fastboot mode started" on a blank screen and then it just sits there doing nothing.
Another boot, the process went further, past LG G2 logo, into white screen, and then it brought up a message "Unfortunately, Settings has stopped.", I clicked okay. It looped back to bringing up the message. I clicked Okay over 10 times, it was stuck in a loop.