Database Info

Stuck on lockscreen - androidui has stopped

Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.

Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...

the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!

Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.

hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems

a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.

I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!

a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....

ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?

a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.

zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.

i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all

I wonder why this happened? I was using google play store at the moment, updating the flipboard app...

a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!

My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.

Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050

how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues

Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?

Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.

Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."

5.1 update issues

I apologize if this issue has already been addressed but Im beyond frustrated.
Since my OTA update to 5.1, my phone is completely crippled. It randomly powers off about 10 times a day (not a auto restart) and I have to power back up. It will also auto restart another 5 to 7 times a day, when it does this it will get stuck in a loop of trying to boot into the OS and restarting all over again. So it will display "Google" for about 2 seconds and then restart again. This is only stopped by holding down the power button. The best part about this happening is that the phone then thinks its the first time I have powered on since the 5.1 update and will initialize all of my apps, which takes about 5 to 10 min. I have had 5.1 for about a week or so and its been getting worse every day. More power off's and restarts each day.
I should note that I am with T-Mobile and my phone is not rooted. Bone stock
My phone is borderline unusable since the update. Please god somebody help me.........

Flash 5.1 factory images

beekay201 said:
Flash 5.1 factory images
Click to expand...
Click to collapse
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
Download the 5.1 stock image here: https://developers.google.com/android/nexus/images#hammerhead
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.

matt4321 said:
Basically something wierd went with the update, maybe a file got corrupt, some risidual 5.0 code is there. Who knows.
The best way out is probably to flash 5.1 again like said above although not really explained. This will ensure the entire phone is 5.1 and there isn't some 5.0 risidual code somewhere which is likely causing the problem.
It will flash your entire phone with stock 5.1, no root, custom recovery or kernel or anything, 100% stock. You will lose your data though, so if you can, back it up!
it will say 5.1 next to it, it'll be pretty clear.
Extract the contents after the download and run the flash-all script.
Click to expand...
Click to collapse
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??

dafababa said:
Before I do any of this I want to note that it appears there are many other people who are having the exact same issues as me. Is it possible that the update is just buggy??
Click to expand...
Click to collapse
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.

matt4321 said:
there are people that are reporting a few issues, mainly the memory leak issue still being present. There are none or very little talking about 7 - 10 random power offs a day. This is very unusual and likely to be a specific issue to you not mainstream.
Click to expand...
Click to collapse
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1

dafababa said:
Well I just finished flashing 5.1 build LMY47i and i can confirm the problem still exists for me. Im just gonna go back to 5.0.1
Click to expand...
Click to collapse
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.

dafababa said:
Excuse my lack of knowledge, but what good would that do? Didn't I get the factory image when I got my OTA update from Google?
Click to expand...
Click to collapse
OTA update ain't the same as a factory image.

beekay201 said:
OTA update ain't the same as a factory image.
Click to expand...
Click to collapse
I've flashed back to 5.0.1 and still have the problems. I'm going to assume its a power button issue.

chaose said:
I htink you may have a loose power button or a loose contact. i had the same problem. Try to press it in really hard and it should fix the issue.
Click to expand...
Click to collapse
So like how hard?

Recovered from boot loop but constant crashes with older ROM

I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?

I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine

Jst flash a newer modem in recovery

mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.

PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.

Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine

KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.

Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.

Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.

mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.

Galaxy S7 restarts randomly!

Hey, XDA-ers!
I got the Android Nougat 7.0 update for my Samsung Galaxy S7 SM-G930FD (DUOS) back in January if I remember correctly. And the update process went like how it normally does. But ever since I got the Nougat update, my phone restarts randomly for no reason. At first it used to restart when I click on the 'Recent Apps' button to switch between apps. When I tap on the button, the phone vibrates and restarts. The phone never over heated before this happens. During this, the phone used to restart 2-3 times a day. This went on for 2 months. Then now, the number of restarts reduced to 1-2 per day, but the problem still persists. And now, it restarts even when I don't touch the 'Recent Apps' button. So, if any of you has had a similar experience or if any of you could help me out Please share it here. It would be GREAT!
Also just one more thing- Any of you seen any DRASTIC or worse changes in battery life of your Galaxy S7 after the Android Nougat 7.0 update? Please share your thoughts here and do suggest how you solved the problem. (My battery drains so fast that I sometimes charge it twice a day. I don't even use my phone for half of the day because I'll be at school and still the battery drain is bad! )

Factory reset. Backup your data via kies and then reset it.

Change your battery

What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333

Us3rNam3d said:
Factory reset. Backup your data via kies and then reset it.
Click to expand...
Click to collapse
Hey, man!
I already tried it like 3 times now. No luck!?

CurtisMJ said:
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Click to expand...
Click to collapse
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!

Hmm... and after the factory reset with no apps installed you are still rebooting?
Why dont you try to reflash your firmware via odin.
Download it from sammobile and reflash it.

AgentArjun56 said:
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Click to expand...
Click to collapse
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.

CurtisMJ said:
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
Click to expand...
Click to collapse
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?

GeekTN said:
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
Click to expand...
Click to collapse
If it's restarting due to the firmware bug then DQD7 will most definitely fix it. Beware of the emergency recovery though. Ive not used Smart Switch but the "initialization" part sounds like it would wipe the device, though that could fix any issues. Backup first, if you can.

Note 10.1 unresponsive to touch but S-pen works fine

So 3 days ago I got bored of Android 4.4.2 on my 6 years old tablet. It worked fine for browsing the internet and watching youtube but I wanted more. I thought that was installing a new android an easy business but I was wrong. I downloaded TWRP and lineage os android 7.1. for my N8000.Then I flashed my recovery and later I download a sketchy rooting app from an internet called "iRoot". Then "iRoot" downloaded and installed an app with some Chinese characters. I wanted to delete that but there was no icon in "manage apps" tab
then I disabled it in other tabs and rebooted my device. when my device rebooted my touchscreen wouldn't work. I pulled my S-pen out and it worked perfectly fine (the device was never dropped). So I tried factory resetting my device and the problem was still there. I installed SuperSu app I thought that it would help me but when I open it it said ''binary occupied''. I was hopeless. Then I installed lineageOS and the problem was still there. I tried going back to my old android 4.4.2 but my sd card was corrupted. I installed Odin and flashed factory OS for my device. now I have the same problem. btw this was my first time doing this stuff so I made a lot of mistakes. I saw people fixing this problem simply by calling *#2663# but when I do that my screen flashes back and then it forwards me to my home screen. The problem was still there. Do you guys know the solution?
'

Its the rooting app that is your problem .
TWRP install via Odin wipe data system cache etc reboot to download mode .

JJEgan said:
Its the rooting app that is your problem .
TWRP install via Odin wipe data system cache etc reboot to download mode .
Click to expand...
Click to collapse
I wiped everything. I just installed Factory android 4.4.2 with Odin. Then I installed TWRP 2.8.4.0 via Odin and wiped everything. but my touchscreen still doesn't work even in TWRP. I was installing Lineage 14.0 from this thread https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514 and I ran out of time. I will update you guys tomorrow. :fingers-crossed:

So *#2663# doesn't let you reflash the tsp firmware?
If not, your tsp ic need to get replaced.

html6405 said:
So *#2663# doesn't let you reflash the tsp firmware?
If not, your tsp ic need to get replaced.
Click to expand...
Click to collapse
What do you mean by that? Do I need to replace my digitizer, motherboard, or something else? I'm quite new in this type of stuff so I don't understand most of the things
Also, I tried installing multiple versions of official os and other versions of Lineage and Slimroms and my touch still doesn't work. I also tried reflashing firmware on all those versions but it still work.

This menu which appears, when you dial *#2663#, it let you update the touch screen panel firmware,
it flashes it directly to the chip.
If this fails or simply doenst work, you have to replace this chip (TSP IC) or your mainboard.

html6405 said:
This menu which appears, when you dial *#2663#, it let you update the touch screen panel firmware,
it flashes it directly to the chip.
If this fails or simply doenst work, you have to replace this chip (TSP IC) or your mainboard.
Click to expand...
Click to collapse
Thanks for your quick response. Basically, because this tablet is over 6 years old, and I am unable to find the correct motherboard in my country. I found tablets (used) like mine for something near 40 euros. I wanted to buy a whole motherboard and replace it, but it was like 30-40 dollars and shipping is an additional 50 - 60 euros. So I think that I should wait for a cheap broken one and then try to make Frankenstein from those two. Anyway thanks for your help!