HTC One M7 - Screen connector on motherboard is destroyed. Phone is fully encrypted but I have the password. Was trying to follow guide on stackoverflow "Mount Android encrypted data partition on PC" to recover data however I cannot get adb devices or fastboot devices to recognize my device.
When I plug in the device the red charging light comes on.
If I hit the power button the charging light turns off and the vibration motor spins.
If I hold volume down and power button the charging light turns off and the vibration motor does not spin (assuming this is boot loader).
I can't seem to get the phone to enter fastboot mode? I have HTC Sync latest installed on my PC.
Any suggestions?
Related
I think I was holding down the power while it was locked. it didnt reboot bus is now instead stuck with a black backlit display panel. home and return is on permanently and the charge light is also lit, despite not being plugged in.
holding down te power button for any length of time just makes the home and return flash for a minute and then back to solid.
no combination of power and volume up/down makes any difference. just flashing home and return lights.
HELP
do I just have to wait for the battery to run out?
Wait I'm a bit confused ...what current state is your phone in? Is it booted up if it is just adb that *****
a box of kittens said:
Wait I'm a bit confused ...what current state is your phone in? Is it booted up if it is just adb that *****
Click to expand...
Click to collapse
it was booted up. now it's just a dark screen with backlight, home and return buttons and charge light lit
plugging in USB and runningg adb reboot just says device not found
actually- when I plug it into USB it appears as in device manager for a few seconds
adb reboot during that period gives 'device offline' rather than device not found...
Evening folks..
I have a Nexus 6 that fell from pocket and screen cracked to include the digitizer. The screen flicks white light but mostly black screen. I want to turn phone in for repairs but i would like to back up all my data. USB Debugging option is not on. Is there another method to pull the data from the phone without having to use USB Debugging and/or screen touch?
Rooted - with [ROM][N6][6.0.1_r3][MMB29K] Chroma 12/10/2015 - but did not back up my phone
Any ideas?
Sorry for the late reply. i was recently in this same situation.
Heres what i did, you can do the same (assuming you have twrp and a computer with adb drivers)
Hold volume down and power, it should vibrate then let go of the keys.
wait 3 seconds and press the volume down key two times, then press the power button (this will put your phone in recovery)
wait a good 10 seconds then plug your phone to your computer, then using adb commands run "adb devices" make sure it sees your phone, then run "adb pull /sdcard"
Hey everyone,
I apologise if this has been asked many times before; but I need some assistance with my HTC one M7.
I was using the phone with low battery - with power saver turned on, it turned off completely after a few moments.
I have put the phone on charge, but the LED indicator is not showing up nor the phone turning on or charging at all.
I went through forums, and tried the power button + volume down button to bring up the boot menu, this menu did actually appear - but me being the fool I am - I selected the power down option.
I have been unable to bring the menu up again with the power + volume button combination.
I then connected the phone to my PC - where its installs a driver - qhsusb_dload. I have tried the power + volume button combination with it being connected to my PC - where I hear the device detected bing and device disconnected bing while I hold these buttons down, still unable to charge/power on/ or bring up the boot menu.
I have also left the phone on wall charger for over 12 overs again to no avail.
Can anyone provide any advice - or any method I can salvage the data stored on it i.e. photos?
Thanks for reading - appreciate any help!
AntMans123 said:
I then connected the phone to my PC - where its installs a driver - qhsusb_dload.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=67835309&postcount=2805
any method I can salvage the data stored on it
Click to expand...
Click to collapse
Not possible if its not booting...
AntMans123 said:
Hey everyone,
I apologise if this has been asked many times before; but I need some assistance with my HTC one M7.
I was using the phone with low battery - with power saver turned on, it turned off completely after a few moments.
I have put the phone on charge, but the LED indicator is not showing up nor the phone turning on or charging at all.
I went through forums, and tried the power button + volume down button to bring up the boot menu, this menu did actually appear - but me being the fool I am - I selected the power down option.
I have been unable to bring the menu up again with the power + volume button combination.
I then connected the phone to my PC - where its installs a driver - qhsusb_dload. I have tried the power + volume button combination with it being connected to my PC - where I hear the device detected bing and device disconnected bing while I hold these buttons down, still unable to charge/power on/ or bring up the boot menu.
I have also left the phone on wall charger for over 12 overs again to no avail.
Can anyone provide any advice - or any method I can salvage the data stored on it i.e. photos?
Thanks for reading - appreciate any help!
Click to expand...
Click to collapse
If you get it to go into that boot menu again. You sometimes have to hold the power and volume down for about 15 seconds, then release them and again start holding the volume down. This is something I had to do to get into recovery back when my bootloader was still locked.
The power may not coming on, but if you are getting usb sounds from plugging it in maybe the computer you are connecting to could be switched.
I had hard times connecting before from certain machines cause they wanted to run an HTC Sync program. You could try a different machine.
Often people say regarding the behavior of the 3.0 vs 2.0 USB ports, that it is 2.0 that will work. And you might try a Vista machine to get fastboot working.
kruc Ire said:
If you get it to go into that boot menu again. You sometimes have to hold the power and volume down for about 15 seconds, then release them and again start holding the volume down. This is something I had to do to get into recovery back when my bootloader was still locked.
The power may not coming on, but if you are getting usb sounds from plugging it in maybe the computer you are connecting to could be switched.
I had hard times connecting before from certain machines cause they wanted to run an HTC Sync program. You could try a different machine.
Often people say regarding the behavior of the 3.0 vs 2.0 USB ports, that it is 2.0 that will work. And you might try a Vista machine to get fastboot working.
Click to expand...
Click to collapse
qhsusb_dload is a well known issue, not caused by the computer you are coonecting to. Its can be caused by a bad firmware flash (flashing an incompatible firmware.zip) or because of an hardware failure. Easy to know what is the cause. Did the phone randomly went in qhsusb_dload mode? Yes ---> Hardware,will most likely need a motherboard replacement. Did the phone went in qhsusb_dload directly after flashing something? Yes ---> Software problem can be fixed with the unbrick project.
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,
This device had been flashed with LOS 13. It was working and functional, but some configuration(?) lead it to dead(?) screen! The Power, Volume +/- buttons aren't able to bring it back, neither touch screen. LED light keeps blinking.
I can't say for sure, but the option 'Do not turn screen on when pluging microUSB power charger/AC outlet.' was toggled to TRUE and some other tweaks I did at same time. So device suspended, then connected power cabble, next pressed power button. Frustration time, device went off, no signal of display viewability/working/etc.
I started trying to debug what happened: attached to Computer USB, from where it'd flashed, terminal prompt, ./adb devices and ./fastboot devices has no listing of it. Again, the white LED light keeps blinking.
What else can I do? Please help!? I have no working device atm and all ears to follow instructions/troubleshoot attempts/etc!