Bricked phone- bad screen or motherboard? - Samsung Galaxy S7 Active Questions & Answers

Hi everyone,
I have an AT&T Samsung Galaxy S7 Active SM-G891A that just became unresponsive. It began with a vertical pink line appearing and disappearing intermittently down the right side of the screen. After a few times if this happening, the phone froze while playing "Laser Overload," which I had just downloaded, for about 30 minutes. I performed a soft reset and the phone went into a boot loop that lasted 20 minutes or so- sometime it would make it to the AT&T screen and freeze, sometimes it wouldn't make it past the "Samsung Galaxy S7 Active" screen.
Finally, it booted up normally but was running slowly. I powered it down, thinking it may have been overheated, and left it alone for a few hours. Upon starting it back up, it worked fine for about 15 minutes but then froze once again. I performed another soft reset, but this time the screen stayed black- no image and unresponsive to touch, but with the top left LED indicator a steady blue. It stayed like this for an hour or so until I plugged it in; the screen did show the lightning bolt charginf icon but it took about 10 minutes for it to display the battery percentage (0%). The phone had 75% battery when it became unresponsive.
Once it had charged to about 15%, I booted it up (leaving it plugged in) and again it became stuck in a boot loop. I rebooted to the system menu (Home + volume up + power) and cleared the system cache in hope that this would resolve the issue, but again the boot loop. Finally, I performed a factory restore on the phone from the boot menu. This time, the phone booted to the AT&T screen before it froze with a horizontal line of static near the bottom of the screen. I soft reset it and the phone made it through the boot screens to a Wi-Fi login. I logged in to the network and the phone froze again, this time shutting down completely and is unresponsive to being plugged in- multiple cables and chargers being used. There is no top-left LED light when plugged in, and attempting to power on the phone using any method does nothing.
Is it possible that playing a game for a half hour was the final straw in killing a graphics processor? I hadn't used this phone for any thing graphics intensive and this game seems rather simple (2D only, no simulated camera, etc.), but it's a secondhand phone that I've had for a few months now. The phone had been dropped a few days ago- only about 2ft onto a rubber mat with no damage to the phone. Could this have caused it?
Is there any way to verify what the issue could be with the phone unresponsive as it is? Any help would be appreciated.

Related

[FIX] [GUIDE] My story of how I messed up in Aroma Installer + Fix

I was trying to flash the Lifeless rom back onto my phone, and had Aroma wizard started up, and was checking the options I wanted, when I remembered that absentminded me had forgotten to do something in the OS that I can't remember at the moment. I didn't see a cancel button in Aroma, and since I'm so impulsive, I held down power and volume up to reboot the phone. It nearly booted to the OS, with the capacitive keys lighting up at the bottom, when it suddenly shut off and attempted to reboot (maybe because I was flashing AC!D audio earlier and had checked the build.prop tweaks). It didn't reboot, but seemed BRICKED.
Ok, the actual problem.
It seemed totally hard bricked to me, nothing when I plugged it in to my PC or charger, so I, enraged, walked away and left my Optimus plugged in. When I came back, I saw that the notification light was blinking red, one shade of red brighter than the other. I gained some hope back by...
The FIX
... following the directions on YouTube (look it up, I can't post links) on performing a hard reset by disassembling the phone and disconnecting/reconnecting the battery connector. I, however, had to do a little twist to get my phone to PARTIALLY boot.
When I detached the battery connector from the mainboard,(phone still plugged in) the phone would proceed to bootloop, showing up the unlocked Google screen, etc. (flashed the ZVB Teenybin, that's why the Google screen) until it got to the battery charging icon in the center with the lightning bolt in the center. At this point, I reattached the battery connector and BOOM, the phone rebooted NOT LOOPING , PARTIALLY STILL but with the battery icon animation stacking up.
Unfortunatly, my battery was nearly dead so I then waited for a bit and let it charge up.
I held down the power button + vol up (on my bare phone with the backing taken off) to get it to boot into fastboot, then TWRP to flash the rom. I SUCCESSFULLY flashed the rom (relieved at this point) and I booted FULLY :laugh: . It got me to the Optimizing apps numberhere/biggernumberhere screen. Suddenly, the frickin phone shuts off and the notification light blinks red, but with a delay this time instead of a brighter shade of red. I did what I did before numerous times, but the phone would stay alive less and less.
I let the phone cool off for a bit (Heating issues on the Optimus ), tried charging it again, and I managed to finish optimizing my apps. It loaded up the lock screen for a split second, and then shut off with the LG goodbye animation.... Which is a hell of a lot better than a blinking reset light.
So after it shut off I let it charge...
And I was back!
NOTES:
The video I describe was originally made to resolve some other reset indicator, with alternating blinking capacitive buttons and the notification light, but also helps with the issue I had with solely the notification light blinking.
I don't think that anyone has had this issue since not really anyone is retarded enough to force reboot with Aroma loaded up.. but I decided to type this up just in case.

[Q] S3 won't turn on past boot logo

I dropped my S3 yesterday from a height of maybe 8 inches. It froze, so I yanked the battery. Initally it got to my spash screen (running liquid smooth 2.9) but froze again. Turned it back on and it only got the boot logo. I tried recovery mode, but it turned off while loading the logo, same with download mode.
When I plug it into a charger without the battery in, it vibrates and the notification light turns red for a second and it dies (doesn't show anything on screen)
Also, it it supposed to turn on as soon as I insert the battery?
I opened it up to see if something was lose and I saw that one of the ribbon cables looked a little weird- is it messed up?
I'm at a loss for what to do
Thanks!

Some kind of battery issue.

I've tried looking up a solution to this but can't find anything anywhere, I've also been trying to fix it all weekend.
Friday night my phone's battery ran out, yeah whatever, I'll just throw it on the charger. Plugged it in, and the screen that normally indicates you should plug your phone should come up. It's an empty battery with a lightning bolt inside of it. A few seconds later, the red "This Build is for Development Purposes Only..." stuff that comes up because of the custom ROM shows up at the bottom of the screen. After a few seconds, the screen turns off. It then repeats this from charge me icon, showing red text, then repeating. I'll be referring to this as Boltlooping.
So the first solution I found was to reset the battery logic by holding vol up/down and power for a few minutes. I rubber banded the buttons down and tried it. Nothing.
Second solution, plugging it in and immediately holding power button hoping it would boot. I tried this 5-6 times. Nothing. I've also attempted booting in to bootloader and recovery from this screen.
Occasionally, however, something that I can't identify or reproduce causes it to go to the normal charging screen. Trying to boot it from here from any battery % puts it back in to a boltloop. I've also tried doing the battery logic reset from this screen, but it doesn't work and puts it back in to bootloop. After trying to do either of these methods and getting back to the normal charging screen, the battery will be back at 1%.
This is as far as I've gotten with troubleshooting. I can get to the normal charging screen, though the battery will die and reset the charge % if unplugged or an attempt to boot is made. Most of its time, however, is spent in this boltloop state. I've tried resetting battery logic, booting in to recovery, booting in to bootloader, and booting normally from both the boltloop and charging states. Nothing. I don't know what to do.
Did you ever find a fix? Same issue here.

Phone can't boot at all, loops on plug in screeen & occasionally "charges"...

Phone can't boot at all, loops on plug in screeen & occasionally "charges"...
I've tried looking up a solution to this but can't find anything anywhere. I've been trying to fix it since last week.
Friday night my phone's battery ran out, yeah whatever, I'll just throw it on the charger. Plugged it in, and the screen that normally indicates you should plug your phone should come up. It's an empty battery with a lightning bolt inside of it. A few seconds later, the red "This Build is for Development Purposes Only..." stuff that comes up because of the custom ROM shows up at the bottom of the screen. After a few seconds, the screen turns off. It then repeats this from charge me icon, showing red text, then repeating. I'll be referring to this as Boltlooping.
So the first solution I found was to reset the battery logic by holding vol up/down and power for a few minutes. I rubber banded the buttons down and tried it. Nothing.
Second solution, plugging it in and immediately holding power button hoping it would boot. I tried this 5-6 times. Nothing. I've also attempted booting in to bootloader and recovery from this screen.
Occasionally, however, something that I can't identify or reproduce causes it to go to the normal charging screen. Trying to boot it from here from any battery % puts it back in to a boltloop. I've also tried doing the battery logic reset from this screen, but it doesn't work and puts it back in to bootloop. After trying to do either of these methods and getting back to the normal charging screen, the battery will be back at 1%.
This is as far as I've gotten with troubleshooting. I can get to the normal charging screen, though the battery will die and reset the charge % if unplugged or an attempt to boot is made. Most of its time, however, is spent in this boltloop state. I've tried resetting battery logic, booting in to recovery, booting in to bootloader, and booting normally from both the boltloop and charging states. Nothing. I don't know what to do.
Please create only one thread for a topic, you already have an existing thread for this here:
http://forum.xda-developers.com/htc-one-m8/help/battery-issue-t3190337
Thread closed.

Lg G3 Phone not working / not responding

Hi,
Really need some help with my LG G3 phone.
Bit of background
My phone network is O2, my kid was watching a you tube video and all he did was hit skip ad and my phone shut down. My phone at the time of shut had around 95% battery.
The phone does not switch on now, when I insert the charger no lights appear stating it charging nor does the screen come on. The phone has not been rooted or anything like that.
When I remove the battery and put the phone on charge the screen displays an image which states no battery is included but when I insert the battery back in the phone displays just goes dead again and nothing occurs
What I have done
I have bought a new battery and still no joy with that
I have held Volume Button down and Power button and no joy
When no battery is in and the above process is followed the screen flickers after around 13-15 seconds but then still shows that no battery is present
Last night the phone did show a little sign of life. I left it all day by itself and then just switched pressed the power button for 3 seconds or so and the LG boot up screen kicked in but then after 10 seconds it switched off. It has not replicated this again though.
Does anyone have any ideas of what i could try next?

Categories

Resources