Database Info

S7 Black Screen + Blue LED

Hi All,
I wonder if you may be able to help. This morning we discovered one of our S7 phones was a black screen with solid blue light. It seemed completely unresponsive to touch, wouldn't wake. etc. The home, volume and power buttons seemed to do nothing. I plugged the phone into the computer, it didn't pick up a USB device.
Phone is stock from EE in the UK. No custom anything. Model: SM-930F 32GB.
EE and Samsung couldn't suggest anything to help.
We tried Power + Volume Down - This results in one of the following;
A (A battery with the current fill %) this happens when plugged in
B (Samsung Galaxy S7 powered by android) loading screen which then cycles or returns to a black screen with solid blue LED
We also tried Power + Volume Down + Home button. This does load the Warning screen about using a custom OS.
We have next day replacement warranty on the phone, i don't need to fix this phone. We only want to try and recovered some data and photos
Any help appreciated.
Kind Regards.

Shannaramoon said:
Hi All,
I wonder if you may be able to help. This morning we discovered one of our S7 phones was a black screen with solid blue light. It seemed completely unresponsive to touch, wouldn't wake. etc. The home, volume and power buttons seemed to do nothing. I plugged the phone into the computer, it didn't pick up a USB device.
Phone is stock from EE in the UK. No custom anything. Model: SM-930F 32GB.
EE and Samsung couldn't suggest anything to help.
We tried Power + Volume Down - This results in one of the following;
A (A battery with the current fill %) this happens when plugged in
B (Samsung Galaxy S7 powered by android) loading screen which then cycles or returns to a black screen with solid blue LED
We also tried Power + Volume Down + Home button. This does load the Warning screen about using a custom OS.
We have next day replacement warranty on the phone, i don't need to fix this phone. We only want to try and recovered some data and photos
Any help appreciated.
Kind Regards.
Click to expand...
Click to collapse
Hi, try turning off the App Power saving mode!! i had these problems also and it was caused by a app that cant handle the always on setting so when you use that app and then turn the phone in standby it will cause the freeze/black screen

Were you ever able to fix this problem? I just had it happen to me and I'm in the same situation.

This just happened to me. After an hour spent with tier II tech support, no progress.
You need to let the phone die completely. Once it's dead (and the blue light) is no longer dead, plug the phone into an OEM walk charger. In my situation,my s7 edge would vibrate to recognize the charge, than reset - before it could even build up a charge (so I thought). I left it alone for an hour or so, and amazingly, it booted up like normal.
Good luck!

I have this problem. How long will it take the battery to drain from fully charged with just the blue light on.

This just happened to me as well. I hope draining the battery works. This occurred when my battery drained and the phone turned off. When I tried to turn it back on after letting it charge for a few minutes it looked like it started to boot, then went to a black screen with a solid blue light. No button combination has any effect.
EDIT: Waiting until the battery died and then attempting to charge the phone has had no effect. No combination of keys has an any effect, either.
EDIT #2: I've taken my phone into the Verizon store. They tell me it's an issue with software and the phone is dead. They said this is "rare". Considering what I see here, I can't say how rare I find it. I have insurance, so they're replacing it, but now they're not keeping up their end of the deal on when the replacement phone will be delivered.

Flash it!
I had the exact same symptoms. What did the trick for me was draining out the battery and then fully charging it, WITHOUT TURNING ON the phone. If you do turn it on, you need to drain it out again. When the phone was fully charged I booted up the download mode and flashed the stock firmware with Odin. That was it, my Galaxy S7 was fully functioning again.
Hope this helps someone out there.

Just experienced kinda the same problem.
S7 died overnight on the charger. I was lucky to wake up on my own.
Just blue led.
I let it drain out over the day so it turned off (vol- + power no working).
Charged it a bit and try to go to recovery: loaded recovery but completely frozen.
I let it drain again and recharged it after it turned off.
Then I went to DL mode and reflashed latest carrier stock rom. AP. CP. BL. CSC. All.
Flashed fine! After rebooting it said "erasing...", rebooted and is back to the blue led only.
Strongly suggesting a hw issue at this point.
I'll let it drain again, fully recharge it, flash a non branded stock rom. If that wont work i'll probably need to bring it to my carrier on monday. Too bad its friday...
//Phone is r.i.p. even after a re flash of stock fw with full battery it only boots to blue led.
//Phone even deader. No more response in any way.
(some time later)
//Just received the repair report. The mainboard and some minor components were replaced under warranty even though my phone was rooted. Good thing for me it never turned on again.

Galaxy S7 won't turn on but will charge(kinda)

I've had this phone for about 2 months now, and from the beginning, it's had an issue where it would randomly freeze, restart, and get stuck in a boot loop for random amounts of time. Sometimes it would be fine after 2 minutes, sometimes it would need 10. I kept thinking this was a firmware issue - the phone WAS rooted with TWRP installed, but none of my past phones have had this issue and hardly anybody online seems to have had it, either - and just thought that maybe installing a custom ROM would fix it, but never got around to doing so.
3 days ago, my S7 went into a boot loop again, so I just decided to put it down and let it do its thing. After 20 minutes, however, it still wasn't booting, so I booted into TWRP, and cleared the cache and Dalvik cache. Another 20 minutes later, I went into panic mode and started doing Nandroid backups of my stuff. I decided that I had no other choice but to commence with finding a ROM to replace stock. In the meantime, I just plugged it in and let it keep looping, hoping against hope that it would just fix itself like it always did.
About half an hour later, I was ready to install the ROM I'd decided on. I went and picked up my phone, but all that I saw was the screen was black, and the blue notification LED was lit up. I tried holding Vol- + Power to start booting it into TWRP, but nothing happened. The phone didn't vibrate, the screen didn't change, and the LED stayed lit. I tried holding every button combination possible, for even as long as a minute, but the phone refused to respond. I tried plugging it into my computer, but Windows didn't detect anything.
Skip to today, and the phone's battery has long since died(the LED isn't lit up, so I can only assume...), and I just decided to plug the phone in for the hell of it just to see if maybe it would maybe work again. To my astonishment, 2 minutes later, the battery icon came up on the screen, but the charging animation wasn't there. When I held Vol- + Power, the phone actually responded and restarted! Though, it wouldn't boot past the Galaxy S7 splash screen, and when I tried to boot it into TWRP, it went back to being a brick. I let it sit for about 10 minutes, plugged it in, and this time tried to get it into Download Mode, and it worked!
I downloaded the Switzerland version of the G930F firmware, flashed it in Odin, and everything seems to have worked. Odin says it succeeded, but when the phone tried to restart, it got to the splash screen, and after a few minutes, the screen went black again. When I plug it in now, the Galaxy S7 screen will come up, but now I can't seem to get into Download Mode anymore(though, it DOES still seem to respond to me pressing Vol- + Power).
Does anyone have any idea what's going on? I can only seem to find 3 or 4 other threads on various forums about this problem, but none of them have any answers. People just keep saying the usual "Hold Vol- and Power to make the phone restart", but in case I haven't made it clear, THAT ISN'T WORKING.
And before you suggest that I return it to where I bought it for a replacement or refund: I bought this phone on eBay from a seller who said it was in pretty much mint condition. When the phone arrived, there was not a dent or scratch anywhere on the phone, even around the charger port, so I have no reason to believe he was lying. When I asked him about any possible problems with the phone's operational stability the other day, he says he tested it for about 2 weeks, and that he didn't notice anything.

Sounds like a hardware fault, not much else you can do other than flashing stock and factory resetting, which you've done
Considering it had a fault from day 1 it sounds like that fault finally caught up with it
Likely scenario if sent for repair, new motherboard replacement needed

Gear S3 Classic Bootloop Stuck

I have a gear s3 classic that is stuck in bootloop. It will NOT power on unless on the charging cradle. Off the cradle it will NOT power on at all. I have done more than several recovery resets and it just goes to the reboot screen and then just hangs on the Samsung logo. I ordered the bit set and will be disassembling today to check for water damage. I've read that ALLOT of people are having the same issues. And I can get into the wireless download. Is there a way to refresh the firmware from NetOdin3? I dont want to flash. If there is a way to refresh the firmware to stop the hangup, then I can at least do a firmware update one past the bootup. Any help would be great. Thanks.

Help getting S7 out of recovery loop?

There's a lot of aspects to this problem at this point, I'll try to be detailed.
I was recently given a bricked Verizon S7 (SM-G930V) to work on (full stock rom). The battery is completely dead, and when plugging it in to a high power charger it shows the recovery booting screen for 1-2 seconds, then black screen, then recovery booting again. So the recovery seems to be broken, and its putting it into a bootloop. From what I've been able to find over the last few days I believe it was caused by either a bad ota update, or it loosing power in the process of updating.
Im able to get it into download mode, but the recovery seems to be completely broken. I've left it on a charger overnight four times (combos of plugged in, on a pad, in download mode, and looping) and it hasn't charged at all.
When its on a high power charger I'm able to get it into download mode, but it dies as soon as i try to swap it to my pc. I have a high power official samsung wireless charging pad, but when its only on the pad its completely unresponsive. If I plug it into the charger and have it on the pad at the same time, im able to get it into download mode and switch it and get it to show up in odin.
I've tried flashing the latest verizon branded firmware, as well as the unlocked firmware (with various combinations of odin versions and settings) and I either end up with an error on the phone (odin/firmware too old) or it just completely fails and the phone turns off. Even when deselecting auto reboot in odin, after a failed attempt (complete(write) operation failed at various points) it reboots.
Only thing I can think of is that the charge pad + usb combo isnt providing enough power with a completely dead battery, but I don't have a working S7 to swap the battery into to charge it, and when its looping or in download mode its not charging at all.
Any ideas?

Download latest firmware using samfirm

Duraforce E6560 boot loop

I've had this phone 3 years and it worked well. It's an unlocked ATT phone so no OTA updates other than the standard app updates. It's on Lollipop 5.1. Been working perfectly fine until yesterday, I was watching the CBS app, when the phone rebooted. Now it's stuck on a boot loop and initally went to optimizing apps which it rarely finishes but the times it does, the phone just powers off. It then got into another loop later last night where it'd get to the Kyocera logo then reboot over and over. I let it do that until the battery died 2.5 hours later. Then I kept attempting to boot until the batter was entirely drained to the point it wouldn't attempt to power up any more.(battery is not removable on this model). I've now charged it up, trying to enter recovery mode with power+volume down. That doesn't seem to register. Tried volume up+volume down+power with no effect. Now after charging, it will do the reboot loop mentioned earlier to the Kyocera logo. If I plug it into a charger, it will go to the optimizing apps portion and repeat the above. At the optimizing apps screen, if I unplug the charger, the phone powers off immediately. It appears to be holding a charge according to the charge indicator and the fact that I can try to boot over and over unplugged. Any suggestions? Phone wasn't dropped or damaged in anyway. Very weird what could have happened.

An update: Phone finally got past the "optimizing app" phase last night sitting on the charger. Out of no where the phone booted completely. However, it only works while plugged in. If I remove the charging cord, the phone shuts down after about 2 seconds. Booting without charging cord results in the same boot loop. I've considered the battery has failed however when plugging in the charger, battery shows 100% and it will decrease appropriately over time. I'm thinking there must be a hardware issues at this point. Somewhwere in the charging/power circuit. Any other suggestions?

Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.

djhurt1 said:
Last update I guess. I was able to keep the phone up and booted as long as it was plugged into a wall charger. PC USB was not enough. I managed to grab my photos etc. thankfully. Factory reset the phone from the settings menu. Unplugged from charger, ran for about 2 minutes. Still said 99% charged, then went into boot loop again. Phone still shows near full charge if you let it run for awhile and decrements the charge state appropriately as time goes on. However, i guess this 3 year old phone is toast. No known reason for it to fail unfortunately. Thought I'd share the experience if anyone else has this issue.
Click to expand...
Click to collapse
I have the same exact problem. It started the crazy booting process in my pocket, and I did all the same things you did. Factory reset didn't correct the problem, so I'm think the battery has had a stroke. Sine your problem and my problem are very close to the same time frame, our phones are also probably about the same age, and its a quality control issue. Not bad quality control, just that these batteries were designed to last X number of months or cycles, and probably they died. Too bad, because my E6560 is the very best cell phone I have ever owned. Built like a tank and thank God for that.