Last night my A500 had an OTA update. My A500 wasn't rooted or had any mods running, and now whenever I try to unlock it, it has a tap saying 'Android system' and a notice in the middle of the screen that the device is shutting down. However, the device has not shut down after a good 15 mins.
That was a while ago.
The tab shut down after bugging out and letting me go to my home screen, and now when I try to turn it on, the android text that normally comes up while booting up shows, but it won't go past this screen.
Any way I can fix this?
It eventually booted up, and upon unlocking, the same Android System screen was up with the same shutting down notification.
Related
Guys,
I'm pulling my hair out over this. My MDA Vario has often rebooted itself and i've always put it down to a glitch of one form or another, but today it has been rebooting every few minutes.
Each time it reboots a text message i've read reappears as NEW, as though the phone doesn't register me reading it before it crashes and reboots. If I delete this and other messages, within minutes once it's crashed and rebooted they will all return like a CACHED memory or something.
I don't know what to do.
It seems as soon as my screen dims on power save, it won't come back on and within a few seconds the screen goes white as it is rebooting.
Sometimes reading this message or doing anything in the message application causes the crash, sometimes it's happenign even without me doing anything.
HOWEVER - once i've turned off the power saver dimming the screen, no reboot is occuring. I've gone into the messages, read and deleted this message among others, and no reboot. If I manually turn the screen off though, within a few seconds it reboots.
What is going on ?!
i have the same exact problem! I changed the battery the day before yesterday and it has not done it since, but im not sure if it solved the problem as sometimes it does not restart in one whole day!
So successfully rooted my phone and started removing bloatware using Titanium Backup. I freezed a number of AT&T applications, but avoided anything with an Android icon. I thought I was pretty careful when filtering out those apps I wanted to freeze, but when I was shutting down the phone for the night last night, I noticed that I didn't have a home screen anymore, it was just black. I had the notifications bar up top still with the date, and whether or not I was using wifi, etc., but when I clicked on the home button, blackness. Then the notification bar started to blink. I shut it down, thinking I just had to restart the phone after I froze some bloatware.
I turn the phone on this morning, and it keeps turning on, the Samsung logo pops up along with the AT&T music, and then when I see my home screen start to come up and I see the password field. At that point, it says "Unfortunately, com.android.phone has stopped." and then the phone reboots again. What can I do to stop this loop!?!?!? I imagine it was one of those apps I froze... maybe TouchWiz? Maybe I filtered something out by mistake and now the phone won't let me in!!
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits
So on Sunday I got a retail g6 from Verizon. About an hour ago it randomly turned off and then displayed the "device is corrupted and cannot be trusted message." It then proceeded to say startup failed and turned off again and wouldn't turn back on. After freaking out some I saw something online about trying to use the volume keys with the power key to reboot. So I held the volume down with the power button and my phone restarted like normal. Absolutely no issues or lag. I decided to restart my device to see if the message would display again, but my phone restarted as normal. All of my apps and data are there as normal. I read that this is an Android issue, not lg. But I also saw that usually the phone doesn't decide to just start working normally again. Should I be concerned?
Help! my 15 month old Umi Super shut itself off (battery almost full) and now won't reboot. The Umi logo appears as normal, then goes to the pulsing android thing. and stays like that for a few minutes until the screen goes blank. I have to hold the power button for a couple of minutes to start the sequence again.
I haven't rooted it (wouldn't know how, or feel confident doing so) Only thing I've done recently was update the OS to Nougat, using the update feature on the phone, so it's completely unmolested apart from the update. Since then, I've lost the fast charge facility, and it auto-locks the screen, and won't display the clock overnight, like it used to do. And all the settings menus have radically changed (for the worse). Can't even turn off the Auto-lock feature, just set the delay.
Is the update to blame? Can I undo it and revert to Marshmallow? Can someone please help? All my contacts are in the phone memory...
Sorted!
Don't know what happened but it eventually rebooted itself. I then deleted all the recently installed apps, and it's now working again. Must have been a rogue app, but I don't know which one. Slowly and methodically worked through the setup menu and found, in the Security submenu, some settings I hadn't previously found and was able to set a safe location at home where it doesn't Autolock. I have my phone back! And I take it all back. Nougat is a big improvement on Marshmallow, once you know how it works. Happy Days!