So a while back I got a crack on my screen but it never got any worse. then suddenly a couple weeks ago, screen suddenly started going weird colors (purple and pink) then shut off completely. Now, I went to get the insurance for the phone but I realized I want to wipe the phone before I send it back to the insurance people. It may have been on, when I plugged it into my computer it was recognized as a GS7 but there was nothing in the directory when I brought it up in Win10 explorer. I tried installing Smart Switch but unfortunately it says MTP isn't activated. I had updated to Nougat when it started rolling out recently, if that matters. Maybe it reset some stuff, because I could swear I had it on. Also I don't think I have USB Debugging on. So I messed around with some button configurations to soft reset it, and now it seems to be stuck with a blinking red light and isn't being recognized by Windows so I'm guessing isn't actually on.
Is there anything I can do at this point? Why the blinking red light? Someone suggested just remote wiping it, but after I got stuck where I'm at now. if I can get back to where Device Manager can find it then I would be fine and just remote wipe it. I think it was on at least for a while since Device Manager says it was last on on April 28th.
Related
Hello,
Runnin an unlocked bootloader, rooted, running Melvin's ADT rom so its just stock and rooted, nothing special on ATT. I installed the no CID flash last week and it worked fine. I have rebooted several times and there was no issue for the past week. Today i had my phone on my desk and i went to unlock it so that I could check the time and the screen wouldnt turn on. I waited about 5 mins and it still wouldnt turn on. I pulled the battery and put it back and tried to turn it on and it vibrated but the screen never turned on. I pulled the SIM, the SD card, and the battery and still no luck. I put the battery in and it wont light up at all. The buttons on the bottom, nor the screen will light up. Cannot get into the the boatloader either. Anyone have ideas on how to fix this?
i have not experienced this nor heard about it until today. i saw another thread with 2 other people with the same issue.. maybe some defective devices floating around out there? take it too at&t for an exchange.... here is the other thread
http://forum.xda-developers.com/showthread.php?t=1356670
well it ended up being an easy fix. The phone just wasnt showing the currect battery percentage. It said the phone was at full charge but it was empty so the battery died. I went to plug the phone into the computer and see if can go into download mode to flash via odin but then it turned on. It recharged and it worked of course.
I just got the moto g
I had updated to marshmallow just after opening the box.
It's the second day of the device and the display just turned black all of a sudden. On screen buttons gone too.
I pressed the power button and the screen turned off. When i turned the screen on again after 5 secs the screen turned black again.
I turned the screen off and on again.
This time the screen kept blinking. It didn't turn off just the contents of the screen kept blinking.
After I rebooted the phone, the issue disappeared.
I'm not sure if it is a software bug that happened or early signs of some hardware issue. I still have the 30 days for replacement.
Rest of the device is working fine.
Has anyone found the same issue?
I am using stock software, no root.
Yes brand new stock moto g updated to m and had the exact same issue, it's happened once a day so far to me (I'm on day three of owning the phone) A reboot fixes it but it's annoy I don't want to have to reboot the device all the time. I can see it being annoying trying to get the device swapped because when I wipe the device to give it back to the shop it will be working fine :-\
It just seems to happen randomly, nothing to do with a certain app I don't think, I can't replicte it when I try to figure out the cause of it.
I know some people had the same problem with Lollipop but I hadn't any issues. Already updated to latest marshmallow. I dropped my devices a few months ago and the frame took a heavy blow from that. But the screen was working without a problem and had no damage at all. A few days ago I used my phone and took put it on the desk and connected the charger. An hour later I wanted to unlock the S6 and only the lower keys lit up.
Searched a bit and used volume down + power to restart the phone. It worked again and I immediately made a backup (used the Dev options to keep the phone on while charging).
Samsung Store denied to do anything. First they said they might reinstall the whole software by some hardware (as expensive as a two family house ) but the technican said no because they don't know if that reallyhelps or might break the phone :silly:
I tried to reinstall via Samsung switch and odin but the still the screen won't wake up after going to sleep. Sometimes it works a few times but most of the times one time.
Anyone can help me, or is my phone simply broken? :crying:
Have you tried factory reset?
Factory reset via settings menu and recovery. And reinstalled via Samsung switch and odin. Still same problem.
If the screen doesn't turn ON after it turns OFF then it could be bug of some sort . Try downgrading to the build right before the one you updated. There's a few MM builds for the S6. Say you on the latest. Downgrade to the one before that and see
yasteellutch said:
If the screen doesn't turn ON after it turns OFF then it could be bug of some sort . Try downgrading to the build right before the one you updated. There's a few MM builds for the S6. Say you on the latest. Downgrade to the one before that and see
Click to expand...
Click to collapse
Downgraded to previous version and now the display won't turn on at all. Reverted back to newest version, and stays black. Look like now I finally broke it
I used it yesterday for about an hour with the screen always on and it just worked. The screen still recognizes touch input and the pc shows me the phone has started.
Dr.Hfuhruhurr said:
Downgraded to previous version and now the display won't turn on at all. Reverted back to newest version, and stays black. Look like now I finally broke it
I used it yesterday for about an hour with the screen always on and it just worked. The screen still recognizes touch input and the pc shows me the phone has started.
Click to expand...
Click to collapse
Really whoa. OK take your S6 to a technician and ask them to check if the LCD cable is connected properly. That thing can come out easily
Just tried to restart the phone with volume down and power button and it suddenly showed the samsung boot logo. It was kinda dimmed and not the bright white it used to be but when the it finally booted up everything was fine.
Only way is a technican as you said. Sad is Samsung is not going to do that on guaranty because of the damage on the frame
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
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.
check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging
So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.