Hi,
I have a Nexus 6 that hasn't been used for a couple years, and doesn't seem to be responsive. I've charged it for a couple hours, but nothing seems to happen when I try to turn it on. I notice a distinct vibration (just 1 vibration) when I press and hold the power button, identical to what happens when I hold the power button on another Nexus 5 I have that's turned on (the power off window comes on prompting me to power off).
Also, when I press the power button 2-3x in a row, I hear something like a shutter sound.
Because of this, I suspect the device may be working, but the screen may be dead (it is cracked, but was working before IIRC). I tried connecting it to my laptop but adb doesn't list it, so either it's really dead, or USB debugging wasn't enabled.
Is there any way of accessing the device, or figuring out if what state it's in?
Thanks!
goister said:
Is there any way of accessing the device, or figuring out if what state it's in?
Click to expand...
Click to collapse
You can try to enable TalkBack through a key combination. AFAIK both volume buttons for 3 seconds.
Maybe you'll be able to activate adb this way...but might be a bit cumbersome.
Try long pressing power and see if you can force a shutdown into a reboot. I've had a similar problem with the black screen on a battery that was on its last legs.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Related
My power button stopped working a couple days ago but I was still able to wake device with volume buttons. I was worried that if my phone were to shut off I wouldn't be able to turn it back on so I booted into bootloader and was going to try and flash "oem off-mode-charge 0" (which should then make the phone power on when plugged into charger).
At the time I couldn't detect the device using fastboot and as I was searching around on my computer the screen on the phone turned off (was in bootloader at the time). I'm not sure at this point if my phone was on and that both the power and volume buttons were not waking device or if the phone turned itself off.
I have tried the hold the volume down and plug the charger in trick to try and get back into bootloader but nothing happens. When I plug phone into my computer it takes about 20 seconds but I get the little windows ding that something has been connected but phone is still not responsive. I'm starting to think I'm a little screwed here but welcome any input.
You just looking to get the screen to light up so you can implement a way to use the device without the power button? You could try gravity screen or something but first things first...
If its not lighting up on plugin have you tried connecting to a computer and opening ADB and issuing the command adb devices followed with adb reboot. If you wanna go back to bootloader just adb reboot-bootloader. That will restart device so screen is back on and I would turn on the Ambient Display mode so when you pick it up the screen comes on or get a volume power button app or gravity screen app that turns on when you take it out of pocket. Thats all I can suggest and hope any of this helps.
With phone plugged into computer, nothing shows up when I check adb devices or fastboot devices. I guess I'm unsure on what state my phone is in. None of the buttons do anything and nothing happens when I plug my phone into my wall charger (no charge light or screen on). The only response I can get is when I plug the phone into my computer windows makes a noise.
Anyone know what happens when a powered off phone gets plugged into the computer? Does windows make the little noise indicating a device has been plugged in even with it off?
It does not make a noise if its off.. That much I know. Interesting though. Are you sure you have the correct drivers installed for your nexus phone if you are on windows. Go into hardware manager by right clicking on my computer and make sure that its reading it correctly in usb devices without a yellow triangle next to it.
I should have the correct drivers. I just went ahead and reinstalled them through the nexus toolkit. In device manager it says: unknown USB device (device descriptor request failed).
I checked adb devices before all this happened and it displayed correctly. I then rebooted into the bootloader but the fastboot devices command did not show anything. It was shortly after that that the screen turned off. Will the screen normally time out when in the bootloader? I'm wondering if my phone is still in the bootloader with the screen off and both power and volume buttons non functional.
Only thing I can think of is to wait for it to die, then volume down + plug in to pc and when bootloader screen appears issue command fastboot continue and it should boot up. Then get something to remap key or an app. If this all fails after it dies and you restart it assuming debugging wasnt on or its just reading phone as media device of sorts not allowing adb then you may have to get the power button assembly possibly and install it yourself or open the back case and hit the power contact under the button and see if you can get it on. Thats all the ideas I have.
I'd also suggest that after you reinstalled drivers make sure you did a reboot and then plug in the device and also try using a different USB port and or USB cord also as odd as that sounds Ive seen it work before. Im pretty tapped on ideas tho. Do you know if you had usb debugging enabled?
Wireless charger
Sent from my Nexus 6 using XDA-Developers mobile app
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
coremania said:
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
Click to expand...
Click to collapse
Ok, cool. I'll take a look.
Managed to get it back into the bootloader this morning. So I guess this is a PSA, if your screen times out while in the bootloader, the volume keys will not wake device so since my power button is broken I couldn't wake it. At that point, the phone is in a state where it cannot receive any fastboot commands, even though it is in bootloader with the screen off. What I had to do was wait overnight for the battery to drain and have the phone power itself off. At this point the volume down plus plug in charger trick worked to get it back into the bootloader with screen on. At that point I was able to 'fastboot reboot' back into system.
Thanks for the insight people
double post
coremania said:
Power Button replacement is pretty easy and cheap, there's a Tutorial
On YouTube
Click to expand...
Click to collapse
It's easy but also annoying. Removing the 18 screws is the most annoying part
clapper66 said:
It's easy but also annoying. Removing the 18 screws is the most annoying part
Click to expand...
Click to collapse
I think the Nexus 6 deserve it
brumby05 said:
I should have the correct drivers. I just went ahead and reinstalled them through the nexus toolkit. In device manager it says: unknown USB device (device descriptor request failed)......
Click to expand...
Click to collapse
Driver issue.
Remove/uninstall the drivers from your PC when the phone is connected.
After that reinstall the adb/fastboot drivers.
N6 - Power mapped to VOL DOWN; turned off and can't get it back on
Hi all, I had to remap my power button - I mapped it to VOLUME DOWN. The other day I voluntarily powered down my N6 at a test center.....and haven't been able to get it to respond since. I do have a Pixel 2 XL on the way - but not that sure I'll want to keep it. The N6 is so sweet.
I've tried holding the volume buttons (POWER and VOLUME UP) for like a minute, but nothing. When I charge it, I see the battery symbol (full) but only for about 5 seconds.
ADB does not see any connected devices. Wug's NRT does not see any connected devices. I'm at a loss and afraid that I've lost my N6 and will have to use the Pixel 2 XL regardless what I think about it.
Any other ideas?
JMacD said:
Hi all, I had to remap my power button - I mapped it to VOLUME DOWN. The other day I voluntarily powered down my N6 at a test center.....and haven't been able to get it to respond since. I do have a Pixel 2 XL on the way - but not that sure I'll want to keep it. The N6 is so sweet.
I've tried holding the volume buttons (POWER and VOLUME UP) for like a minute, but nothing. When I charge it, I see the battery symbol (full) but only for about 5 seconds.
ADB does not see any connected devices. Wug's NRT does not see any connected devices. I'm at a loss and afraid that I've lost my N6 and will have to use the Pixel 2 XL regardless what I think about it.
Any other ideas?
Click to expand...
Click to collapse
Wow - just got my N6 to boot using this little tip I found on Reddit - https://www.reddit.com/r/AndroidQue...ny_way_to_turn_on_phone_without_power_button/
I was holding down the Vol Up and Power buttons (which are both the Volume bar since I remapped my power to Vol Down), but I hit 'enter' on the 'fastboot continue' text in the CMD prompt just after I plugged in the USB and the battery icon came up. It booted into bootloader mode briefly first, then went into system reboot. Whew!
I think your button assembly is broken and I would replace it. You could try the work around in Broken power button, any way to boot? by altarity, post #3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
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!
Randomly throughout the day, my phone changes the ringer volume from vibrate to the lowest sound tick on the ringer. This happens at least 5 times per day (usually more) as long as the privacy switch isn't set to a silent mode. This happens on OOS, lineage, RR, etc. This happens to both me and a friend all the time. He bought his 3T a few weeks after I got mine, we're both bootloader unlocked, have different versions of TWRP, he runs OOS and I run Sultan's lineage build normally. Basically we're both extremely annoyed at this little issue. We cannot figure out why it's happening but it happens to both of us regardless of ROM or firmware version. This has to be a software issue, what are the chances that we both got devices with a hardware issue. I have a 64gb gray, he has a 128gb black, purchased about a month apart, no way we have phones from the same batch. Any help to fix this annoying little issue would be greatly appreciated.
Is you phone in your pocket when it happens? Any chance it can be something as simple as the power & vol rocker being pressed when the phone is in your pocket? Reason I say power & vol rocker, is that both would need to be pressed for the vol to change (pressing vol up/down when screen is off will normally do nothing).
Hasn't happened to me on this phone. But on my old M8, once in a while when crouching down (with phone in my pocket), the power button would be depressed long enough to reboot the phone. Although the power button was on the top of that phone (and easier to accidentally depress, I would think). I was starting to think there was some hardware/software fault making the phone reboot; before I realized it was just me depressing the button on accident.
redpoint73 said:
Is you phone in your pocket when it happens? Any chance it can be something as simple as the power & vol rocker being pressed when the phone is in your pocket? Reason I say power & vol rocker, is that both would need to be pressed for the vol to change (pressing vol up/down when screen is off will normally do nothing).
Hasn't happened to me on this phone. But on my old M8, once in a while when crouching down (with phone in my pocket), the power button would be depressed long enough to reboot the phone. Although the power button was on the top of that phone (and easier to accidentally depress, I would think). I was starting to think there was some hardware/software fault making the phone reboot; before I realized it was just me depressing the button on accident.
Click to expand...
Click to collapse
It happens even after sitting still on my desk after an hour of not being touched. It's been going on ever since I've had the phone. Definitely not accidental presses
CosMiiK said:
It happens even after sitting still on my desk after an hour of not being touched. It's been going on ever since I've had the phone. Definitely not accidental presses
Click to expand...
Click to collapse
I know that with some custom ROMS, it works in sets of three.
Alarms/priority/all notifications
Total silence/vibrate/ring
At least it's what I've noticed. And only with a few custom ROMS.
Hope this helps.
I did a search for my problem on XDA itself as well as the ol' Google - found these inconclusive threads:
https://forum.xda-developers.com/nexus-6/help/water-damage-t3135077
https://www.reddit.com/r/nexus6/comments/4ps502/power_button_acting_as_volume_control_button/
In 'short', this is what happens for me with my stock N6, updated to 7.1.1 (Oct 5, 2017 patch):
if device is off, power button turns device on as expected
if screen is off, power button turns on screen as expected
if screen is on, power button increases volume - not expected, faulty behaviour!
if screen is off and music is playing, pressing power button increases Volume and turns on screen - not expected, faulty behaviour! (should only turn on screen)
if screen is off and music is playing, pressing volume up increases volume and turns on screen - not expected, faulty behaviour! (should only increase volume)
if screen is off and music is playing, pressing volume down decreases volume, screen stays off, as expected
double pressing power button brings up Camera app, as expected
double pressing volume up button brings up Camera app - not expected, faulty behaviour!
occasionally this faulty behaviour also triggers the device to reboot and/or display 'bug report' notifications
The phone hasn't been exposed to water. Hasn't recently been dropped, last time was many months ago, prior to this starting. The last update applied to the device was Oct 5, 2017, and that was done shortly after that date, so shouldn't be causing this issue.
Things I have done:
factory reset the device
replaced the power+volume up/down button+ribbon part
Neither of which has made a difference. What is this, "planned obsolesce"? What are my options here?
Have you tried running in safe mode and see if the problems continue?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Have you tried running in safe mode and see if the problems continue?
Click to expand...
Click to collapse
Thanks for the reply! I seem to remember trying safe mode when it first showed up a few weeks ago, but maybe not, given that getting into safe mode requires that I hold the power button down to show the "reboot/shutdown" prompt and...
Since the power button is wonky, all holding it down does is increase the volume all the way! Kind of frustrating.
Well, a clean flash of the stock ROM would give a similar result. The goal would be to eliminate the possibility of any app causing the problem. I would have thought replacing the button adorably would be the hardware solution. Unless the phone's case is somehow interfering (I don't mean a protective case).
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Well, a clean flash of the stock ROM would give a similar result. The goal would be to eliminate the possibility of any app causing the problem. I would have thought replacing the button adorably would be the hardware solution. Unless the phone's case is somehow interfering (I don't mean a protective case).
Click to expand...
Click to collapse
Not the case, I tried it without the casing when I had it apart too. Thanks again.
Power and Volume button confusion on Nexus 6P
jaddison said:
Not the case, I tried it without the casing when I had it apart too. Thanks again.
Click to expand...
Click to collapse
Hello,
Did you find any solution? I'm experiencing the same thing on my Nexus 6P after a battery replacement.
Today I was in the car and using TeslAA Android Auto app on my Pixel 5a. At one point, the phone froze for a period and was unresponsive to any buttons. It then powered off, which I thought was restarting, but it never came back on. No matter what buttons I held down for how long, it was completely unresponsive. Nothing on the screen at all. I tried plugging it into my computer and when I held down the power button I could hear the USB sound on the computer. A long press (as if a hard reboot) would make it sound like I had unplugged the phone, and then pressing it again would sound like I plugged it back in. But still nothing on the screen. I have had zero issues with the phone up until now. What can I try?
I also tried power and volume down, but still nothing on the screen. It's like my screen completely died suddenly.
BlueWRXPride said:
Today I was in the car and using TeslAA Android Auto app on my Pixel 5a. At one point, the phone froze for a period and was unresponsive to any buttons. It then powered off, which I thought was restarting, but it never came back on. No matter what buttons I held down for how long, it was completely unresponsive. Nothing on the screen at all. I tried plugging it into my computer and when I held down the power button I could hear the USB sound on the computer. A long press (as if a hard reboot) would make it sound like I had unplugged the phone, and then pressing it again would sound like I plugged it back in. But still nothing on the screen. I have had zero issues with the phone up until now. What can I try?
I also tried power and volume down, but still nothing on the screen. It's like my screen completely died suddenly.
Click to expand...
Click to collapse
Never mind
BlueWRXPride said:
also tried power and volume down, but still nothing on the screen. It's like my screen completely died suddenly.
Click to expand...
Click to collapse
did you try power + vol down + vol up? all 3 at once for about 30 seconds then power on? that is a hard reset
Yeah I tried it all. I ended up realizing that for a problem like this, there's an additional year of warranty coverage, so I sent it into google for a free repair. So that was a nice surprise!