My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
tdrussell said:
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
Click to expand...
Click to collapse
ask franco if fsync is enabled default and if is barrier=0 in the kernel
Try holding in the power button for 45-60 seconds. If that doesn't work then Plug in the unit, and let it try to charge for an hour or two. Then try holding in the power button for 45-60 seconds again.
There seems to be a glitch where the unit will die when the battery is low. Some people have report something similar when the unit was ~23% battery life.
Related
Hello all,
I got this phone about a month and a half ago, and since I got it I've noticed a lot of freezing and crashing (more so after the 5.1 update).
Some examples:
-I try unlocking the phone from active display and the screen goes black. The only way to get out of it is to hold the power button to restart.
-Sometimes the phone freezes on the lock screen randomly, and when I pick up the phone to look at it, the time is wrong and I can't physically unlock the phone, only turn the screen on and off, leading to me having to hold the power button down to shut off and restart.
-When on some apps, like twitter for example, the phone freezes, and I cannot do anything except turn off the screen by pressing the power button. When I try waking the phone, it stays black or sometimes theres a flash of the screen I was on before, and then it goes black again. Only thing I can do here is hold the power button down until "Power Off" shows up on the screen, and I press that to shut the phone off.
Today I cleared the cache, and since then the phone has froze once, causing me to do a hard reset. What should I try next? Any idea what the problem could be?
Thank you for the help.
I have pretty much the exact same thing going on. It started last night... I first noticed I had some charging issues where the phone wasn't charging very quickly after the battery died (after a day of heavy use). I let it sit for awhile, then it booted up, and it showed the motorola splash screen. It gets all the way to the lock screen, although I'm unable to unlock the phone. The screen goes dark. It appears to still be getting texts and the like- although this screen blackness issue makes it so I can't unlock the phone. The one thing I can do is hold down the power button and turn it off. I've tried loading fastboot and doing a factory reset, although nothing appears to happen and it boots the same way. The other thing about it is that it appears to be running hot- way hot. Any ideas? I'm running stock rom, Verizon network, just updated to 5.1 when it came out last week.
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Put down gently today and the right side of the screen displaying flickering dark/black stripes. Left side of screen perfectly fine. Touch still works over the whole display. Any ideas? Internal cable come loose? Or something more terminal? How easy to check/fix?
Xdaforumposter said:
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Click to expand...
Click to collapse
Hi, so I got an A2 which has been submerged in water for a while. I was not turning on at all (just showing the white led light blinking), so I bought a new USB part and battery for it, replaced it, and now it seems to react.
However, it keeps switching between the charging logo for a second, then vibrates and shows the Android One logo (this switch goes on and on forever). I have tried the button combo to go into recovery, but as soon as the Android recovery boot logo appears, it'll still timeout into the charging logo.
Does anyone know what may be going on? Or what component to replace? (the phone was only days old when it accidentally got soaked, so everything is new and it's a shame to just throw it away)
Hello,
the other day I had my phone on the sofa next to me, working fine, I leave it there 30 min, pick it up, and the screen has all kinds of weird glitches. After a couple hours now the screen is completely blank and whenever I press the power button the notification light blinks a couple times. It's kinda weird tho because touch seems to be working (if I boot to recovery, then tap on the screen the phone vibrates just like TWRP buttons) and I can still boot to fastboot. Of course when I say boot it means that `fastboot devices` shows the device ready, but I can't actually see anything on the screen. I'll try flashing the latest MIUI now, does anyone know what this could be? I mostly just like to know whether I should try changing the screen only or if it's likely to be a bigger problem and I'd be better off replacing the phone entirely. Kinda sad, I loved this phone. Thanks.