So I've had my GS3 since launch, about 14 months. Up until Monday, everything was working fine and I had been through a dozen ROMS. Sometimes things would get buggy, I'd flash a new ROM and it would all be great again.
On Tuesday I noticed that when I'd go to use my phone it would not wake up and need a hard reset. As I went through my day I noticed it would randomly freeze to black while being used and require a hard reset to get going again. It probably went through 20 random resets throughout the day until I had a chance to flash a ROM in the evening, thinking everything would be fine.
Flashed the new ROM, noticed almost immediately the freezes were still going on, tried searching various forums for a fix and couldn't find anything that sounded like this problem. I did check through the Ultimate GS3 freezing thread and Ultimate GS3 Sudden Death threads, but neither seemed to have the same problem. Finally I decided to try the dummy file generator described in the freezing thread and after a while it gave a FC. I tried to run it again and it would not run properly, I cleared the data/cache for the program and was trying to try again when the phone froze for the last time.
It is now bricked, it will not hard reset, respond to battery pulls, respond when charging, boot to recovery, nothing. Can't be detected when plugged in to a computer and I will be taking it in today to see if it can be repaired out of warranty. I doubt anyone here can help with fixing the phone, I just thought I should post this so other people might find it if they suffer the same symptoms and can share similar experiences.
Related
So... maybe someone else can help me out here. My phone started doing this really cool thing about a week ago where it will just shut off out the blue. I've been scouring Google for similar problems, but cannot find anything. Lots of people complaining about reboots or sleep of death, but not hard shut downs. I don't have to pull the battery to reboot or anything, and it's not restarting, it just shuts off.
Sometimes it will only do it once or twice a day, other times it will do it 5+ times an hour. There seems to be no pattern to it either. Sometimes I will just pick up my phone and its off. Sometimes I will be listening to music with it in my pocket and it goes out. Quite a few times I've been texting or something and watched it just shut off.
It was right around when I flashed AOKP M5, so I assumed it might be that. I tried a new kernel first, which didn't help. Today I flashed MIUI, hoping it would fix my problem, but nope. Still getting reboots. So it does not seem ROM related.
Anything else I should try before trying to get my phone replaced? Who would the warranty even be through. I bought the phone from Amazon wireless. Them? Verizon? Samsung?
go back to complete stock, then see if the problem occurs
Maybe try using the samsung stock rom, without root. If you still have the problem, I think you should contact amazon. Be sure to reset the flash counter before you send it away
Sent from my GT-9100 using ICS Remix pro AOKP
There isn't a flash counter on the GNex.
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
I haven't hit my ten message minimum yet so I can't post this in quite the right thread.
I'm running Quantum 3.4 right now and its been like butter., No problems and no hiccups. Tonight, the phone randomly turned off and when I went to turn it back on it went into a sort of boot loop. It just kept restarting itself as soon as it started the loading animation. All I could get was the vibrate and bit of load screen.
It'll load up every so often, but when it does the screen does this flickering thing and then reboots shortly thereafter.
Any ideas? May not have enough info here, so let me know if more is necessary to diagnose or even suggest a problem.
Thanks in advance
You could try wiping cache and Dalvik to see if that helps. If not, you may have to do a wipe of the data too.
Ok.... So here's some schadenfreude for everyone's amusement. My solution was to do just as Audit suggested, whic, unfortunately, didn't work (Thanks for the suggestion though). So I tried to dirty flash an earlier version of Quantum thinking that the voltages may have finally caused some sort of failure and an earlier rom wouldn't have this problem. No success... So I went all the way to a completely clean flash of the earlier Quantum and still no luck.
Finally, it was time to put the kiddos to bed so I put the phone on the charger and lo there was the little battery saying 0%. I swear I looked when this whole thing started and it said 38%, but nope. 0% So I let it charge and everything's flying along beautifully. Ugh.
Time for a beer.
Hello!
Everything was working fine until my phone started acting up about 6 months ago. The screen began to become unresponsive, apps crashed when switching between them and random reboots occurred frequently. I thought back then it had to be software related, so I completed multiple factory resets, and completely removed everything on my phone. It became slightly more usable, but these crashed and random reboots still occurred.
Last week, my phone continued to reboot, but a new problem occurred-it no longer would turn on after the reboot. I tried plugging it into the wall, pressing the volume down + home + power to force bootloader mode, but it wouldn't turn on at all. The fix was I had to remove the entire case, take out the battery and put it back in the phone. After that it would turn on, but only for a few minutes before another random reboot occurred and I had to remove the entire battery again. My phone is now virtually useless as I cant before even the basic functions, calling and texting without it becoming unresponsive or shutting off and not turning on.
I narrowed it down to the eMMC chip. I am almost certain that is corrupt, because during some of the reboots it would fail and throw me into download mode with the error:
mmc0_read_fail
or something along those lines. My last attempt at recovering the phone was to the stock rom PE2 with a PIT file (I had created before I started flashing custom roms). Each time I would attempt to flash with ODIN it would result in a:
mmc0_write_fail
However, I was finally able to get the PIT and PE2 firmware to flash. Now I have a half-working phone that will randomly reboot still and in order to turn it back on, the battery has to be pulled out for a minimum of 15 seconds.
New Issue I just noticed: When the screen turns off when the phone is inactive, it won't turn on again after pressing the power or home buttons. Only solution to this is once again, pull battery and hope I boot into system again.
I am pretty sure there is no fix to this problem on the software side, but let me know if you have a suggestion! Thanks!
Same situation. This thing is a lemon!
Sounds like hardware failure.
Replaced the battery yet? My original didn't last fifteen months before it started shutting the phone down. It's the first thing I think of when someone reports having to pull the battery.
Are you checking battery capacity before the battery pull by plugging in when it shuts down? Mine showed 0%. Before the shutdown, it may have indicated as high as 30%. It gets worse.
You didn't mention capacity when plugged so I thought I'd ask.
Sent from my SM-N910P using Tapatalk
One of my note 4 had same issue. Its a hardware issue. I was able to get the phone working by using a heatgun on the motherboard to try and reflow the solder on the chips. The phone works like brand new after the heatgun but the phone would only work for like 3 or 4 days before crapping out again. Ultimately ended up buying a used motherboard on ebay with a clean esn and its working perfectly again.
My wife's Note 4 started the random reboot thing and screen being unresponsive thing last week. She said it randomly started after installing Snapchat, so she uninstalled it hoping that would fix it. It didnt. I put a new battery in it thinking the original was bad, but still same issues. Then did a factory reset but that didnt work. After a lot of searching I stumbled on to someone who mentioned downloading an app called Wakelock. I did and phone has been running smoothly for several days now.
I also recently did the most recent update hoping that would fix the issue, it didnt but during the install I did get one error of emmc read failure or something like that. May just order a used/new motherboard just in case.
Just be careful when swapping out the motherboard as it essentially is taking apart the whole phone including the removal of the LCD.
Hello all,
My Pixel XL randomly started resetting on its own and then gets stuck in a bootloop. It used to reset 1-3 times a day a do this (Its been going on about a week now), but the last couple of days its been doing this several times an hour. I can get it to stop the bootloop and finishing turning on by pressing the power button a bunch during the loop, but it will shortly reset and start the bootloop.
I can't even power my device off, because before it can finish powering down, it will reset into the bootloop. I have contacted Google, and they weren't much help. They said they can send me a new device, but it will be a week or two. Any suggestions on what I can do in the meantime to try and fix this? I've already done a factory reset and that did not help.
Thanks!
This keeps happening to me. Any luck finding a fix?
Same here. I updated to the latest patch a few days ago and now my Pixel (not Pixel XL) goes through bootloop a few times a day...
I've had similar issues with my Pixel XL recently. It started with a random reboot, after which it just ran really slowly, with apps telling me they weren't responding or the whole thing just freezing up. Shortly after that it went into a boot-loop (boot, input PIN to unlock, screen freezes, auto reboot, rinse/repeat).
For me, a factory reset would solve the issue for a couple of days then it was back to the same problems.
I returned mine to the shop this weekend, and they have sent it off for repair/replacement; in the meantime they've given me a basic Android loan-phone.
Sorry; I'd like to tell you I had a fix for this, but I just wanted to say that I too experienced this issue and simply took it back for replacement/repair. I guess it depends where you bought it (I got mine SIM-free from a shop in the UK) for them to offer something else to tie you over.