My S7 is stuck with a black screen after reboot. It has a solid blue LED light showing but all buttons are not responding.
I have tried inserting the charging cable but it doesn't do anything and when I try to force reboot it (Volume down+Power) it isn't also working.
What should I do
As of right now, you're probably f***ed. I just had that problem 3 days ago, and after letting the phone die, I plugged it in, and while I couldn't get into TWRP, I managed to get it into Download Mode, but after using Odin to flash the stock firmware and everything, I now can't even get back into DM. I made a post just a few minutes ago going into more detail if you're interested in reading it.
Related
Got a perculiar problem with the S6. The screen suddenly went black with just the blue LED blinking in the upper left hand corner of the sreen. I am assuming the phone went off completely as I cannot access it via the PC also. I have tried all possible button combinations for reset but no luck so far.
Anyone else experience this? Did you find a fix?
Sent from my SM-G920V using XDA Free mobile app
Well the phone is not off if the blue led light is blinking, I've never had it happen to me where the phone didn't come back though. I was using an app one day (YouTube I think) and the app crashed and bugged the phone out to where the screen went black but the led was blinking. I left the phone alone after several attempts of hitting home and power to get the screen to come back on and finally I think I plugged it into the charger and it kind of just fixed it self and has not happened again. This is the scary parts of not having a removable battery.
Sent From My Rooted Galaxy S6
I've got the 128GB and yes I have experienced this as well, twice! I hold down both volume buttons the home button and the power button at the same time, this will put you in maintenance mode. It'll take a couple of seconds holding those buttons but just keep them pressed. Be careful because when it does come on it comes on fast and factory reset is the second selection in that mode. The first time I did it I wiped my phone, the second time it happened I lifted my fingers fast enough not to make a selection. Give that a try and see what happens.
frostysax said:
I've got the 128GB and yes I have experienced this as well, twice! I hold down both volume buttons the home button and the power button at the same time, this will put you in maintenance mode. It'll take a couple of seconds holding those buttons but just keep them pressed. Be careful because when it does come on it comes on fast and factory reset is the second selection in that mode. The first time I did it I wiped my phone, the second time it happened I lifted my fingers fast enough not to make a selection. Give that a try and see what happens.
Click to expand...
Click to collapse
Thanks very much.
Hey guys, i really need someones help. Everything in my life runs on my phone. The phone is Samsung Galaxy Note 5. Its screen is black and there is a blue blinking light. I have tried to hold the volume down and power buttons but it didnt do anything. It doesn't respond even after plugging in.
chaudharysafi said:
Hey guys, i really need someones help. Everything in my life runs on my phone. The phone is Samsung Galaxy Note 5. Its screen is black and there is a blue blinking light. I have tried to hold the volume down and power buttons but it didnt do anything. It doesn't respond even after plugging in.
Click to expand...
Click to collapse
Sounds like you have the same problem as stated in OP. You could try doing what was recommended earlier in the thread. By the way, this is an inappropriate location to put your problem. Read the forum rules
Never rooted.
I am having the same issue. I have tried everything. Factory reset. Reboot/wiped cache and even trying to install verizon's Fireware again as it come only up to the Samsung S6 logo then goes blank. This is now my 4th replacement with Verizon and getting sick of it. How do I fix this? Odin stops at Get Pit mapping then when I do that says it can not install NAND. Using Odin 3.10.6 and 3.10.7. Tried mutli cables and restarted computer as well. This is driving me insane these phones keep doing this.
same problem except nothing comes on. no led, no reset, no computer recognition...
Same issue. Boots into and displays recovery fine and download mode. I can also bring up the safe mode menu ... just can't boot into the OS. Blue light on. I get a response in ADB when powered on, just can't enter any commands due to not being able to authorize access via phone screen.
Update:
Well as strange as it sounds, as soon as I plopped it down on the wireless charger for my S7 the screen came to life. It was at 95% battery prior to. Whatever gremlins got into the gizmos within the wireless charging apparatus seems to have caused this strange occurrence.
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.
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
So a relative of mine brought me an S6 with a cracked screen. It belongs to his 15 year old daughter. He told me that she dropped it and the phone is now stuck on a black screen. When I put the phone to charge it didn't respond in any way at first. After leaving it like that for 2 hours I tried to boot it up. Only response I got was a flickering blue - light blue led light. So I searched on the net and found a couple of people fixing this problem by holding the power button with the volume down button which performs a simulated battery disconnect, unfortunately absolutely nothing happened. The phone continued to flicker the blue - light blue light. The screen is probably dead as no matter what I try it is also black. I tried entering recovery mode, nothing changed (flickering blue light), than I tried entering download mode and the flickering blue light changed to a constant red light which after a while changed to green, I am guessing the phone was charging now (screen still black). So I downloaded ODIN to see if the PC will recognize the phone and oddly enough when I connected the USB it did recognize it. So what I'm thinking is that the screen is probably dead as no matter what I do it is always black, but I am not sure what else is wrong with it... Is another hardware peace broken from the fall or did the system just got messed up is that even possible from a fall? If just the screen is dead shouldn't the phone just boot up normally and have sound, like being able to ring and stuff ... Any advice/ opinion will be greatly appreciated.
Hello
Today my SM930F seems to have freezed. Basically I picked up the phone and the display would light up only one pixel. Others are utterly black. I tried rebooting the phone. PWR + VOL DOWN, tried rebooting into recovery and download. It seems to reboot into them just fine, but I can't operate them, beacuse nothing shows up. Screen is dead black. Phone is recognised by my computer and Odin. Seems to be charging normally when plugged in a wall charger. As I recall the phone was running a stock rom. LED and soft keys light up normally. Glass is a cracked on both sides of my phone, but I think it's a software issue. In other threads people have reported that Spotify app can cause similar problems and I have it installed.
EDIT: it seems that I cannot boot into download - I tried it, plugged my phone and flashed a stock rom. Whole process ended in 5 seconds, so it seems that the device is either still powered on or hangs on a bootloop - idk