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?
Related
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.
Hi everyone, after trying everything I could to fix this phone I don't know what to do anymore so I'm here asking for other options.
So the story is, I was just using my phone as I usually would that day and it just randomly turned off and won't turn back on anymore.
(it randomly turned off before a couple of times but it would always turn back on)
- It won't go into recovery mode or any other of the 'modes' (I tried all the different combinations of pressing the keys).
- It's not a battery issue as I've tried my battery on my brother's phone (he has a Note 4 too) and it worked fine and I tried his battery on mine and it wouldn't work.
- I tried the 'drain' method (removing the battery and holding the power button for a minute or more).
- I tried using multiple cables to charge my phone nothing worked.
I didn't drop my phone, wet it, root it or anything and it was working fine the day it happened until it just powered off by itself. When I plug it in my laptop it would make
a sound indicating I've plugged something in but nothing happens. It was version 5.1.1 model SM-N910F.
TLDR; Is there a way to somehow recover the files in the internal phone memory?
This is happening to me as well, also started in February. I'm suspecting a hardware issue. Tried it ALL but rooting. In the past 30 minutes my phone has booted and rebooted itself till it died. If someone can confirm it is a hardware issue. Maybe it's time to unite and get it fixed for free. ~Tamarnouche
Recovering data from a brain dead phone may not be possible, as it probably need some internal component replacement which may erase the data(Mostly). Have u tried connecting it to pc? Better give it to service immediately. Good Luck.
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
HXOY said:
My phone has done exactly the same thing, happened in February too, initially it did the random freeze then started to reboot itself, went back to stock software and full wipe but no improvement; now it will only boot if I leave the battery out for a prolonged period, otherwise it doesn't respond to the power button at all.
I occasionally see MMC Read Fail on boot but not all the time so presumably the internal memory has a bad contact or is failing.
Can it be replaced?
Click to expand...
Click to collapse
I have the same problem with my Note 3. Only if I keep the battery out for a long (over 24 hours) time I can see the boot logo. So if you find a solution to this kindly don't forget to tag me, will really appreciate it.
I was wondering..
I came across this Forum group since I was looking for boot problems with my SM-N910T3
I hope flashing pit will resolve this..
I recently started to have some low level issue and was hoping it was partition/boot related and not hardware.
Randomly phone boot directly into Download mode with error;
ddi: mmc_read failed
Often I have to pull battery and hold down /power / home for 10 sec to boot up again.
Thanks
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
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
chereko said:
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
Click to expand...
Click to collapse
That's interesting. My Essential did the restart but shut down thing for the first time today. I'm not rooted and only running the current Oreo 8.0 beta. The only thing I noticed is an update yesterday from the google play store of Essential Services. I wonder if for me they are related.
It's possible but in all likelihood the problem was there before and it just never happened until now. Even on my phone, sometimes it does reboot properly and sometimes it doesn't. I haven't figured out any rhyme or reason as to why it happens. I bet this is a problem that many people haven't noticed because few of us regularly reboot or shut down our phones. For me this has been happening since Nougat, and the Oreo beta didn't change it in any way.
hello,
my note 4 has been working pretty good up until maybe a week ago, and then it started to randomly turn off and sometimes it would re-boot. other times pushing the home button it wouldnt awake, even thou the blue led lights was flashing like i had a message or notification, pushing any button would not awaken it, pushing and holding the power button would not turn it off, prompting me to pull the battery out. put the battery back in, push and hold the power button had no effect, having to volume down, home button, and push power button, and then volume down when prompted would boot the phone.
many times the phone would freeze, and pop up window would say X app has stopped working do you want to shut it down?, play store, samsung ui, various apps.
so, i googled my symptons, several suggestions suggested remove google play updates and then reinstall and update everything, that was last night. it casually freezed more and then it seemed to sort of work better last night and this morning. and just a few minutes ago, i had a new pop up screen "Runtime Error bad argument#1 to 'abs' (number expected, got nil)" as google is one of my loyal and usually helpful friends i asked it, to my surprise i found basically zilch. putting "Runtime Error bad argument#1 to 'abs'" inside quotation marks was limiting results, it didnt look like other phone users had had similar troubles.
i did see this hit "http://geco.mines.edu/guide/Run-Time_Error_Messages.html" lightly scanning over it made me think i was not looking in the correct place. as the word "intel" was mentioned a few times.
i found another page "https://github.com/layeh/gopher-luar/issues/1" as the title is similar to my issue "bad argument #1 to <function name> (userdata expected, got string)"
those with far more of an understanding of android and code, please assist...
thank you
View attachment 4419367
More and unusual pop ups
nothing?
seems my phone has signed me out of google play
and has unrooted itself
many times the "Samsung UI has stopped working" pops up
i was hoping those with much more knowledge would have offered some suggestions.
i will back up all my data (in several different ways)
root my phone (again)
do a system re-format
and then re-install my apps and crap
crossing my fingers that that is all it needs... cause frankly i have no idea what, how, or why it recently crapped out. i suspect it was one of my apps, as the phone was working very well for several years, and within the last few days its all freezes and hangs, and occasionally crashes and reboots..
This morning I woke to find my phone looking like this