I have had this phone for months. Installed TWRP 2.6.3.4 and CM11 Official. Recently the phone has SOD, and when i hard reboot (hold power button), the screen stays black. I have to reboot multiple times, and sometime plug in the power to get it to come back. Also, after it finally comes back, the video will glitch for awhile and the be fine until the next SOD. Anyone heard of something like this? Thinking I should go back to completely stock and see if it continues.
Related
I was using my Nexus 7 (2013) this morning surfing some sites, when all of a sudden my touchscreen just up and died. No laggy response, no jittery response, just nothing. I can't even unlock it when I wake it up. I can't power it off (as far as I know), since after I hold the power button down, I can't select Power Off.
I'm rooted running a stock 4.3 as fas as I know. Any ideas of where to begin? Thanks in advance.
Sent from my iPad using Tapatalk
I had the same issue when I didnt use it for 4 days. Touch would respond and when the power off dialog came up I couldnt touch it but just hold the power button longer and it will reboot. I held it for about 15 seconds maybe 20 and it will restart
Well, if that previous posters suggestion does not work, or any software-related solution, my first suggestion would be to send it back for a replacement, barring that, it sounds like something could have come loose, if you're the type to try it, you can see how that is addressed with the 2012 version:
Google for "How to Fix Nexus 7 Touch Screen Problems", the video is by Tampatec.
Happened to me too once but i was on a custom rom and kernel. I freaked out when the touch wasn't responding!
I held down to power button to power-off/reboot. It seemed to result in a bootloop and i wasn't exactly patient because i was freaking out a bit!
So, i powered down the device again, booted into recovery (TWRP) and to my relief the touch worked!! I just rebooted back to the system and everything was fine.
This happened to me on stock android 4.3 twice. I believe it is a software issue with the last one or two factory builds of 4.3 for this device. As previously stated, my problem was fixed by holding down the power button for about twenty seconds until it rebooted.
Sent from my Nexus 7 using Tapatalk 4
I got it to reboot and that seemed to do the trick *crosses fingers*
Sent from my XT901 using Tapatalk
Had this issue too a few days ago. I connected it to my PC and rebooted it via adb reboot command.
Occasionally I get this issue after switching the screen on running completely stock 4.3, but I can solve it by holding the power button - not to reboot, but just so the menu comes up. That alone wakes the touchscreen up for me.
So I've attempted to debug this best I could but I've come up with absolutely nothing thus far.
About a month ago, I'd say, I started having very infrequent complete lock-ups. I'd pick up the phone and try to turn on the screen and nada. It would still be running as the notification LED would sometimes pulse according to my Lightflow settings. Plugging it into my computer, it appeared as an unrecognized device and adb wouldn't be able to get anything from it. I've never had this happen while I was actively using the phone, mind.
Holding down the power button until it force shuts down and rebooting it works just fine, but it's a bit annoying and worrying to have it go blank every few days. Once, it was even completely working but the touchscreen would not respond regardless of what I tried.
I since did a factory reset, thinking it might've been a kernel issue (I was running on faux's kernel) and it went fine for a week but it just did it again... And this is on stock 4.4.2, rooted, without any new app in a long time (ie. I can't think of an app that I'd have installed when the crashing started).
Any ideas, short of writing it off as the occasional problem and planning on a much earlier replacement than initially expected?
Hi guys!
I devoted myself a complete evening into fixing my little brothers GS5. 2 weeks ago he told me he was installing an original Samsung update. However after this update his phone would randomly turn off after a few minutes of being on. So I guessed something was wrong with the software. I flashed a stock rom onto the phone, but now it doesn't even boot. I tried multiple stock versions of Android 4x 5x and 6 for the GS5. None of them made the phone boot. Sometimes it showed the Samsung logo, but most often just black screen. I can't boot into recovery either, the same story. I tried twrp, the lights of the buttons were on, but the screen wouldn't turn on. When the phone normally boots with a black screen I sometimes get notifications though. LED flashes sometimes and there's audio.
Anyone having any thoughts how I can fix this? Help is much appreciated!
tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
chereko said:
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
Click to expand...
Click to collapse
That's interesting. My Essential did the restart but shut down thing for the first time today. I'm not rooted and only running the current Oreo 8.0 beta. The only thing I noticed is an update yesterday from the google play store of Essential Services. I wonder if for me they are related.
It's possible but in all likelihood the problem was there before and it just never happened until now. Even on my phone, sometimes it does reboot properly and sometimes it doesn't. I haven't figured out any rhyme or reason as to why it happens. I bet this is a problem that many people haven't noticed because few of us regularly reboot or shut down our phones. For me this has been happening since Nougat, and the Oreo beta didn't change it in any way.