I have an HTC Desire 610, a little over two years old.
Out of no where I started getting the error 'com.android.systemui has stopped' that I usually can't get passed. If I hit 'ok' it pops up again right away, and changes my background back to default with all my wiggits and apps still showing.
I reset it a bunch of times, left it off to charge (realized today that was a correlating issue) and it seemed to stop. I redid my background, and it messed up again.
I'd just downloaded a bunch of new apps, but nothing I hadn't used before (it was going slow so I uninstalled just about everything to try and speed up)
I reset it through the phone settings, and was still getting the error in the set up page.
Tried turning it on and off a few more times and I either get the error message, or my screen will come up, but without the soft buttons and top menu bar.
Let it charge for the night, and seemed to be fine, but as soon as it turned off again, back to errors.
Noticed today, if it's charged (maybe over 20%) the error message doesn't pop up, but neither does my buttons or top bar.
Done safe mode,just got message.
Recovery, no bars.
Tried messing with the settings for the top bar, noting.
Didn't have anything fancy done to it, not rooted or anything, and none of my peeps have any idea.
http://forum.xda-developers.com/desire-610
Related
I hope someone can help me, I have a Sprint Touch Pro2. Last night it randomly started rebooting itsself, i was not loading a new rom, i was not installed any software, i wasn't doing anything other that texting and IMing people. After i removed the SD Card, there were a few times i got it to load to the unlock screen, but once i got passed that it would say "starting device activation..." or something like that. Then i got it loaded but Touch Flo 3D would not automatically start. So i removed the battery and restarted it again and i went to bed and left it charging, and it kept restart itself again, when i woke up it the phone was dead, and will not turn on. The charging light is on but it will not turn on.
This happenned to me, i ended up having to exchange the phone.
have u tried a hard reset. U can do this by holding power button and call and end keys.
Phone must be off and it will completely erase your data
this sounds like what my phone is doing. is there a fix? i think im sol because i didnt buy it though sprint.
Not Hopeless
This happened to my Sprint TP2 I soft and hard-reset it but it still went back to the reboot loop.
I put it in the tri-boot screen and re-reflashed the stock ROM and all was well.
Same here
The same thing is happening for me right now. Soft-resets aren't helping. It's sporadic, however, sometimes saying it successfully activated and needs to reboot (then going into activation right away), sometimes saying it failed, and sometimes not coming up at all (but I'm pretty sure it's running in the background, even if I hit cancel, because the phone is very warm and the battery drains very quickly).
I took it to Sprint and they confirmed it was already activated. They tried manually activating it, succeeded, and it still kept doing it. However, both them and I were able to place a phone call, text, and visit a website... so basically it was working. But, like I said, this constant nagging of activation was running in the background sucking juice and killing performance. Their diagnosis was "it's acting weird". The main home screen clock has also been stuck at 0:00 ever since this started (though the lock screen clock and clocks in the World Clock screen are correct).
They said I could go to their service shop and do a diagnostic and backup/wipe/restore or they'd replace it under warranty if it still didn't work.
I figured I'd just try the hard reset myself tonight. Will post how that goes. I'm not sure what this "tri-boot" screen is, but I'll do some searching and check that out too.
I was using an app on Sunday, when the app froze completely and the screen of the s3 went black. The only thing I could see was the status bar up top, but even that was unresponsive. So I pulled the battery and turned it back on, and it was acting extremely slow so I got impatient and started trying to get into settings, when it went unresponsive again.
This time I held down the power button to see if I could get it to respond and the lock screen came up, without my wallpaper and instead of Verizon Wireless at the top, it said "No Service". After a couple of seconds my wallpaper showed up and then it said Verizon Wireless. After I get through the lock screen, I would go through the same whole routine - e.g. try and get into settings, freeze, hold power, have it come back up, etc. So I battery pulled again.
Finally, I got it to boot OK, by just letting it be for 10 minutes and completely ignoring it.
However, today my battery drain was pretty fast, it was on for 12 hours and was down to 40% after only 30 minutes of screen time. The culprit was "Android System" at 61%, i've never seen this that high before. Because of the high "Android System" power usage, I thought it might be good to power it down. Upon boot up, I assumed I'd be able to use it immediately, so I started going into Settings, and yet again it went unresponsive.
Are the two issues unrelated? What should I do?
As a warning, I'm extremely new to anything smarter than a Nokia brick, so be patient - Thanks!
As inconvenient as it is, I would recommend a full system wipe and go back to out of the box. That seems to fix everything and unfortunately it is rather difficult to diagnose issues on phones, especially unrooted.
In order to do a wipe you can do one of two things, goto settings then backup and reset, then hit factory data reset.
-OR-
Turn off the phone. When you start it again hold volume-up, power, and home to get into recovery. Then do the factory reset.
Ok, I thought that's what my option was. Thanks dwibbles.
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Blitztorm said:
Sorry but i have tried to find similar threads without a clue what happened with my Nexus 5.
This just happened few hours ago during work. i have done nothing to the phone and eventually enter a bootloop mode at the end.
The phone. is using ART runtime for quite some time, never have any issues. now when i find out the phone is off and i tried to reboot the devce, the second time it booted normally and i went check everything if there were something wrong, first Whatsapp jump out a warning date and time error. so i went to system clock and recheck the boxes to auto. problem solved. after few seconds a screen pops up and saids "android upgrading, optimizing app xx/xx. it was very strange..but i can do nothing with it. so i went back to my meeting and leave the phone charging. when i came back 10 mins later i tried to check everything again and end up finding out the runtime, supposed to be ART, went back to Dalvik , i was thinking "oh snap..whats wrong"
try to reboot the device and it entered bootloop, occationally i could see the 4 color dots and mostly didnt.
tried to use fastbook/recovery mode also failed. (after seeing the screen it restarted again, if i keep on holding it repeated 4 times and turns no respond)
All this happened in a sudden, please help, the point is i didnt even do anything to the phone..
thanks.
Click to expand...
Click to collapse
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
pigstew said:
tap the power button vigorously. i mean hard taps. use your finger like a hammer basically... the power buttons are known to **** themselves on the nexus 5 and this can un-stuck them.
Click to expand...
Click to collapse
Good Lord!! It actually did work, but how to explain the ART and Dalvik thingy?!
thanks
I factory reset my phone and during the process of signing in, agreeing to T&C's etc, a strange problem started occurring - the touchscreen became super unresponsive (had to press something three of five times for it to respond), however, at the same time, the phone would quickly vibrate on touch multiple times, but again, not actually do anything. Moreover, a weird blue text box started appearing around the options I touched and I can't swipe down to access the normal settings menu.
And to top it all off, if I long hold the power button to force restart/power off, it just won't do it. (tried the old "turn it off and on" trick to see it'll do the trick)
Everything was all normal until this point, had my phone for a couple of months, haven't dropped it or anything. Does anyone know why this is happening, and if so, how to fix this?
Thanks so much in advance!
shnk said:
I factory reset my phone and during the process of signing in, agreeing to T&C's etc, a strange problem started occurring - the touchscreen became super unresponsive (had to press something three of five times for it to respond), however, at the same time, the phone would quickly vibrate on touch multiple times, but again, not actually do anything. Moreover, a weird blue text box started appearing around the options I touched and I can't swipe down to access the normal settings menu.
And to top it all off, if I long hold the power button to force restart/power off, it just won't do it. (tried the old "turn it off and on" trick to see it'll do the trick)
Everything was all normal until this point, had my phone for a couple of months, haven't dropped it or anything. Does anyone know why this is happening, and if so, how to fix this?
Thanks so much in advance!
Click to expand...
Click to collapse
In fact, I can't swipe at all ... in the app drawer if I swipe, it just goes to the next app , instead of the next screen.
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.