Hi there, so my g2 has worked flawlessly in the past other than losing and quickly regaining detection of my sim card once in a while, but a couple days ago it began freezing randomly and rebooting immediately after really often. When it reboots it gets stuck in a bootloop until I hold power and it eventually gets back to where it was. I'm really not sure what could be causing this but it is very bothersome.
Having the same problem. Let me know if you find a cure. I've tried everything I can think of short of flashing the KDZ or TOT again. That's my next move.
Mine turned out to be a hardware issue. Replacing the phone
Related
D800 randomly reboots while in use throughout the Day
My lg g2 has been randomly rebooting throughout the day ever since I upgrade to 5.0.1 from 4.4
It usually happens when something potentially resource heavy happens such as loading a large image or installing ad blocker. It should not be restarting for something like that.
Attached I have my last_kmsg.txt file after it happened again.
It usually turns off when this happens but sometimes reboots. Also sometimes it doesn't turn back in immediately. Like I would have to hold the power button for 30 seconds, then it would turn off again. It eventually does turn back on.
Attached I have my last_kmsg.txt file after it happened again.
Thanks for the help.
Can anyone take a look at the last_kmsg file and try and give me a fix?
I would go back to stock(look at my newbie thread - http://forum.xda-developers.com/showthread.php?t=2633150)
If you still see the problem then send it in to LG. I had a similar problem and they covered it (even though i was out of warranty by a few days)
I had a similar issue except mine wouldn't charge for a while during the process, and my screen wasn't always responsive. I sent it back (extended warranty) and got a G3 for $100.
Full wipe and clean ROM install usually did the trick for awhile, with mine, if you don't want to send it in.
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
Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone
Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.
Currently I can turn on the phone, but after I turn the screen off, it won't come back on again
Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.
I've been having some problems with my Galaxy S5 recently after ~2 years and some change of owning it. I'm stock rooted on the original ANCG KitKat version.
The problem: If I power off my phone, it will cause it to go into a bootloop, not going past the first screen (Samsung Galaxy S5, powered by android). I haven't found a reliable way to fix it from the loop, but I usually just remove the battery, wait, and try again until somehow it just works and boots up. This is extremely problematic because sometimes my battery runs out and after charging I'll have to go through this game of chance again until my phone works.
The next problem also adds to this frustration as well. When I attempt to pick up a call, my phone will sometimes just not work and restart itself. This leads to lots of confusion and I can't call them back for some time because the phone is stuck in a bootloop.
In the few times that I do get my phone to actually boot up, everything works fine except sometimes my Wifi just doesn't work. It gets stuck on "turning on" where the notification drawer quick setting icon is dim green and never gets to the turned on full green state, eventually just turning itself off (no green color).
I haven't done a factory reset or any real troubleshooting yet, as I'm a bit worried I won't even be able to boot up the phone and I don't have the time yet to spend a full day fixing it. Any help would be appreciated, thanks!
The calling problem may be caused by the google dialer app not being set as the the default phone app but as for the other issues i have no idea a factory reset is a good start though
unfortunately I had the same problem but I have marshmallow but the factory reset helped with the not booting up and see a big difference with the battery
I've enjoyed this phone the entire time I've had it but in the last ~6 months it's gotten less and less reliable, to the point that it crashes and restarts itself randomly at least twice a day.
To be clear, this phone was unrooted, locked and on stock firmware when the first symptoms appeared. The first symptoms were that it would fail to connect to bluetooth in my car about once every 10 times. That became more and more frequent, then it would randomly FORGET all my bluetooth pairings and it would work for a while then progress in the same manner.
More recently it would start rebooting itself (when I wasn't even doing anything -- it would just be sitting on my desk and reboot) -- and now it has started to do this but get stuck in a boot loop.
So I figured I would take the plunge and try a new rom if everything else failed. I installed Lineage OS and so far everything has been good, but now twice it's crashed, rebooted, and been stuck in a bootloop and had to be factory reset *again*.
Is this phone just defective or is there something I can do to fix this?
Sounds like a defective eMMC chip... Not common, but hardly unheard of.
You can try going back to stock, performing a full factory reset, and add nothing but essential apps.
Otherwise, without a realtime logcat of the reboot to determine the cause, it's all speculation.