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."

D801-20G OTA Update from t-mobile..

I got this update a few days ago on my rooted Tmobile G2. Applying the update bricked my phone, as it was stuck in a recovery boot loop. Had to use this:
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
to get it unstuck. Also, I tried the LG Support Tool to pull the update, but it was trying to download a 1.7gig update. I cancelled it before the install process in the fear that it would bork my phone.
Has anyone gotten the update to install successfully on their phone? (rooted)

I got the update but didn't run it. I learned my lesson last time. I'd love to know what it brings and how to install it though.
Sent from my LG-D801 using XDA Free mobile app

sidog said:
I got this update a few days ago on my rooted Tmobile G2. Applying the update bricked my phone, as it was stuck in a recovery boot loop. Had to use this:
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
to get it unstuck. Also, I tried the LG Support Tool to pull the update, but it was trying to download a 1.7gig update. I cancelled it before the install process in the fear that it would bork my phone.
Has anyone gotten the update to install successfully on their phone? (rooted)
Click to expand...
Click to collapse
I'm there but can't figure out how to type in terminal command, can you help me out with this? I'm stuck in the recovery boot loop.
*EDIT* nevermind I figured it out after a factory reset though UGH!

I also got the update notification. I deleted 213MB upgrade file in cashe. It was in the root of cashe folder not in /cashe/foa/. I still get the stupid upgrade notification. How can we kill it? I have Titanium backup but software MUC is not an option on our phones.
OK found how to turn it off. Long press the update, App Info pops up, uncheck show notifications. Clear cashe and then reboot.

You can use stomproot (brute force method) to root this OTA. towelroot won't work. Before applying OTA, make sure custom recovery is replaced with stock recovery. Otherwise you will end up in boot loop.

sam298 said:
You can use stomproot (brute force method) to root this OTA. towelroot won't work. Before applying OTA, make sure custom recovery is replaced with stock recovery. Otherwise you will end up in boot loop.
Click to expand...
Click to collapse
Can confirm this works...thanks...autorec still works as well

If I have not installed a custom recovery, but just rooted the phone with AutoRec, will it soft brick my phone? Since I don't have TWRP or CWM, I would have no way to enter adb shell. So, it sounds like if I soft brick it, I'd have to restore factory settings to get it to boot, right? Are there any significant improvements to the 20g versus the 20e? Thanks.

I got this this morning and installed it...no issues whatsoever. Not sure what its for, but I got it.
Im stock unrooted.

I ended up going with the LG support tool method and installed the update (1.7gigs)...not really sure what the changed though. Root was lost, but I used Stump Root to get it back and everything is normal again. If anyone has the list of changes, plz post

tpaxadpom said:
I also got the update notification. I deleted 213MB upgrade file in cashe. It was in the root of cashe folder not in /cashe/foa/. I still get the stupid upgrade notification. How can we kill it? I have Titanium backup but software MUC is not an option on our phones.
OK found how to turn it off. Long press the update, App Info pops up, uncheck show notifications. Clear cashe and then reboot.
Click to expand...
Click to collapse
Where exactly do I "long press the update? I deleted the update file from cache but can't find this App Info popup menu. Is it within the file explorer or the settings menu?
Sent from my LG-D801 using XDA Free mobile app

As long as you deleted the update you can safely press the install button...it may or may not actually power off...but if it doesn't just reboot after pressing and the notification will be gone...also to prevent it from downloading in the future you can dial 3845#*80X# and click wlan test then ota setting and click disable...you can re-enable by going through the same process and pressing enable...works for most variants

Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon

you press and hold on the update in the notification bar and app info will popup.

nolig2278 said:
Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon
Click to expand...
Click to collapse
Same here, just rooted, no custom recovery and went through the update process. Completed update, still on e not upgraded to g

Plugged into LG Mobile Support Tool and updated that way, ran STUMPROOT and bruteforced. Rebooted and had root ^_^ Updated SuperSU binaries and rebooted once more and ran AutoRec. Now time to update everything again and remove the bloat they put back on.
Also to find the dialer code to update touch software, knock on isn't working. :silly:
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
nolig2278 said:
Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon
Click to expand...
Click to collapse
From what I saw on androidpolice it includes in-flight wifi stuff and some patches. Probably blocking some of the older rooting methods

Took the update last night, i was rooted with stock recovery but it went through just fine. Now when i try to root via StumpRoot it says my device is rooted before i even do anything. I don't have root access though.
Anyone else experience this problem? I've already tried a factory reset but still no-go.

this "update" seems absolutely useless. however, it could be nice to get a flashable radio from it.

mannequin said:
this "update" seems absolutely useless. however, it could be nice to get a flashable radio from it.
Click to expand...
Click to collapse
No change in radio...still same version

FIX
snowlin said:
Took the update last night, i was rooted with stock recovery but it went through just fine. Now when i try to root via StumpRoot it says my device is rooted before i even do anything. I don't have root access though.
Anyone else experience this problem? I've already tried a factory reset but still no-go.
Click to expand...
Click to collapse
I had the same issues and figured it out!
http://forum.xda-developers.com/lg-g2/help/fix-trouble-putting-download-mode-t2979318

when i am trying to do that its says ( NO UPGRADE ITEMS TO FIX ) any idea guys.............

How to stop lollipop from installing automatically?

I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.

Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.

Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.

I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.

I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.

Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850

So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.

Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.

jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.

aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.

adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.

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.

FlashFire!

Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?

https://forum.xda-developers.com/showpost.php?p=70793032&postcount=589

Oface82 said:
Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?
Click to expand...
Click to collapse
Yes I was going to try to do a back up. When I pick slot b it shows double of every partition is that normal? I never have used FlashFire

If I pick slot a it looks normal I think

To be honest I'm pretty that I've never seen it list two of everything like that with another device but not positive. I'm running a backup right now then I'm going to try flashing stuff

]
Oface82 said:
To be honest I'm pretty that I've never seen it list two of everything like that with another device but not positive. I'm running a backup right now then I'm going to try flashing stuff
Click to expand...
Click to collapse
just did one. I did a reboot and opened it up and it shows it just one time. But if I close FlashFire and reopen it. It shows double or triple partitions. If I reboot system it's OK again. Might just be a glitch.

Oface82 said:
Hey guys, has anybody seen that the flashfire app has been updated to work for our pixels? I've installed and can confirm that it sees both boot slots and everything seems good but I havent had time to actually attempt flashing anything with it. Still, with the silly number of steps we have to go through to flash mods and updates to this device, I feel like this app could really cut back on some of the hassle. Thoughts?
Click to expand...
Click to collapse
Just tried to update 7.1.2 OTA with flashfire on a rooted Pixel with Adaway.
Major fail. It put the device into a boot loop.

Download 7.1.1 April security patch zip and flash OK
Then download 7.1.2 zip and flash OK
Root access intact for all time.
Now I want to stretch for other mods like WETA audio MOD.
Is it possible?
P.S. WETA mentioned that only support TWRP