Related
Let me start by saying, Power + Home does not work. Yes, really. I know there are a dozen threads about Touchpads not turning on, and they all have "Hold power and home for 20s" as the reply. Please don't respond with "Hold Power and Home for 20s". I have tried it.
Background
I took my Touchpad with me on a road trip. I did not have an official car charger, but I had one rated at 1 amp. I used this charger with my Touchpad, and it said that it was not powerful enough (as expected). I figured I would let the Touchpad at least get some juice while it was not being used. The battery steadily drained over the next couple of days, to the point where the screen did not come on. I assumed this was because the Touchpad was completely drained.
Once I got to a location with an actual outlet I used the original Touchpad wall adapter and let it charge for a few hours. The screen still did not come on, and there was no response (sound/light/vibration) from any buttons. I let the Touchpad continue to charge over night with the same result.
The Touchpad has alpha 2 on it.
What I have done
I have tried:
Power + Home for 15s
Power + Home for 30s
Power + Home for 1min
Power + Vol Up for 15s
Power + Vol Up for 30s
Power + Vol Up for 1min
Power + Vol Up + Home for 15s
Power + Vol Up + Home for 30s
Power + Vol Up + Home for 1min
All of the above with and without the Touchpad being plugged in to the wall and PC.
Trying WebOS Doctor (does not recognize a device)
Trying novacom directly (does not recognize a device)
Letting the Touchpad charge for > 1 day and repeating all of the above
Letting the Touchpad sit on the Touchstone for > 1 day and repeating all of the above
Verifying that the AC adapter is secured properly and repeating all of the above
Changing the USB cable and repeating all of the above
Changing the AC adapter and repeating all of the above
Results
The only time I have gotten any indication that the Touchpad is actually doing something is when using Power + Vol Up (and Vol Down) with the Touchpad connected to the PC. Vol Up has the Touchpad recognize as Palm. Vol Down has the Touchpad recognize as QHSUB_DLOAD. If I have the Touchpad connected to the PC in one of these states, Power + Home will reset the device (and Windows will not recognize it until I use Power + Vol Up/Down again).
That is the only response I get from the Touchpad. Anything else I have tried results in nothing.
My current plan is to attempt to let the battery completely drain, and then charge it again. I was previously under the impression that my Touchpad was out of power, but the testing with Vol Up/Down has shown me otherwise. My hope is that losing all power will truly "reset" the device.
Does anyone have any advice on anything else I should try? Is there a way to recover the Touchpad via booting it as Palm or QHSUB_DLOAD?
Volume Up + Power while connected to PC, then run WebOS Doctor?
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Another method
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
DJ_SpaRky said:
Volume Up + Power while connected to PC, then run WebOS Doctor?
Click to expand...
Click to collapse
It may not have been clear since it came after the list, but I did try this. WebOS doctor does not recognize the device in any mode. I do not know if this is simply because I lack the necessary drivers when it is in one of the other device modes. On the off chance that I didn't I will try again when I get home.
Dbarker 2 said:
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Click to expand...
Click to collapse
I do believe I have tried this, but I will try again when I get home.
FishDoc said:
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
Click to expand...
Click to collapse
It is my fault for leaving it out, but I tried this after exhausting the other options.
chrischoi said:
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
Click to expand...
Click to collapse
I really wanted to avoid the slew of "Hold power and press home!" comments and the followups telling me to hold it longer, hold volume, and all of the other normally recommended fixes. I know how to write a bug ticket or two. I'm also the type of guy who posts a followup with what actually fixes the problem (No "nm, fixed it" from me).
It sounds like my current plan of action is going to mimic what you did. I originally thought the Touchpad was getting no power, so I kept trying to charge it. Now I am waiting for it to lose all power, so I can repeat the process after the device (hopefully) resets. I'm not sure how long that will take since I cannot actually use the device to drain the battery.
Thanks for the responses. Some replies are better than no replies.
So i had a similar situation and tried everything you had mentioned and all the suggestions in the thread. Nothing. No power, completely dead. I even left it
overnight on the charger... nothing. For sure i thought I bricked it. Then, I read online that someone tried the following:
Press and hold Power + Volume Up and click the card (menu) button a thousand times.
Wow! It worked! The TP is alive! In actuality, it only took about 30-50 times (not a thousand) of pressing the menu button while holding power + volume up.
I then got the white USB icon in the middle of the screen and then pressed and held the power + menu button to reboot.
What I did find interesting though is the battery was almost discharged even after having it on the supplied charger (not touchstone) overnight.
Anyway, hope this resolves your issue as well.
No go with Home + Power, Power + Vol Down, Power + Tapping Home
suremail said:
No go with Home + Power, Power + Vol Down, Power + clicking Home
Click to expand...
Click to collapse
Just making sure you read it right since you didn't list it above.
Power + volume up + clicking home button repeatedly.
All 3, same time. Just trying to help.
^ worked for me..thanks
Sent from my HTC Inspire 4G using XDA App
Well this is a really strange one...
Touchpad was completely non-responsive, I'd tried everything above about 5 times and it just wasn't showing any signs of life. I have left it charging all day today.
Assuming it was completely dead, I sat it down. 5 minutes later, it inexplicably just started booting up.
Wish I knew what I did, if anything to make it boot.
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Phillip Fry said:
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Click to expand...
Click to collapse
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
menting said:
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
Click to expand...
Click to collapse
Well I installed Android uninstalled it. Then installed it again and forgot mboot then uninstalled it. So I belive I am back to stock but I wanted to upgrade to 3.0.4 then install Alpha 3.5 as I has having problems with the Touchpad rebooting in both Android and WebOS.
So when do I know if it is bricked. And what do I say to customer support to get it fixed? I just bought the Referbed ones off ebay the other day.
Here's an update...
No luck with anything so far. I caved and decided to take the Touchpad apart to disconnect the battery. I did this and still no screen response. The only changes have been it's a bit more difficult to get it into Palm mode (if it does at all), and now it seems that I can get into QHUSB mode just by repeatedly pressing the vol- button (no need to hold anything else). I do not know if the QHUSB thing was like that before disassembly, or if it is a result of me mucking around.
Unless anyone has any great ideas it looks like I will have to hope HP fixes it in order to tell me it is out of warranty for having Android.
If you send it to Hp and If they can't power it on, I'd say they would definitely replace it. Problem is, I doubt they have any more TP's in stock. Not sure how the warranty would work now being that its a discontinued product.
Hopefully after toying with it enough you'll figure it out and get it powered.
Mine is stuck in download mode too. Still no success.
Here's my experience so far.
Black screen.
When connected to PC :
Home + Vol UP - Device Manager shows PALM (with yellow exclamation) - no driver found.
Vol Down (no need to press home or power) - Device Manager shows QHSUSB_DLOAD (with yellow exclamation) - no driver found.
WebOS Doctor fails to detect device (palm ! in device manager)
I tried forcing novacom drivers on the Palm device (both novacom and novacom-bootie) and then running WebOS Doctor, still refuses to enable next button.
Tried connecting with novaterm, cannot find device. (both novacom and bootie driver).
Power + Home for 15 - 20 secs always resets and clears device from device manager.
I installed QHSUSB Drivers.
now when I Vol Down it installs as a com port (Qualcomm HS-USB QDLoader 9008).
I installed QPST_2.7.323 and am able to see the device as Q/QPC-XXX - ESN=*Download* - Phone Number=*Download* - Banner=*Download*.
I tried resetting the device with QPST, fails to complete the command.
I think I need a new boot.hex to flash to the TP, or a way to force it to charge (if that is the problem).
My Touchpad was low on power when I put it away in the car while on a road trip. I plugged it in to the wall the next day when it wouldn't turn on. After charging overnight, it still refused to power on. That's when I started combing the web for possible solutions.
Please stop posting irrational solutions, such as Power + tap home 5,000,000 times as the few times this did work for others, it was merely coincidence, and power + home would have worked also.
Any rational solutions are welcome.
I may just send it in for warranty. Although I bet that at HP, they will just hook it up to a machine with "special" drivers and re-flash it with Web-OS. I wish they would just let me do the repair myself with the appropriate files.
Who knows, maybe it is a hardware issue, but I doubt it.
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
skiinginstead said:
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
Click to expand...
Click to collapse
Having the EXACT same problem....anyone have any solutions to this? WHy is this happening?
It's a long shot, but it might help if you are getting to the USB symbol on the Touchpad .
I spent hours trying to connect with no luck with the Touch pad in that state. I rebooted my PC and it connected to the TP right away. (I was using a Win 7 64 bit PC.)
NOTE - I added this post here thinking the CM9 experts could help. I then realized it should be in the Q&A section. If this does not belong here, I ask a moderator to please delete it.
I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
chozyn said:
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
Click to expand...
Click to collapse
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
It's a good idea to use only stock cable and charger.
Sent from my ClassicJewel
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
Are you able to get into download mode at all?
A$$h4t said:
Are you able to get into download mode at all?
Click to expand...
Click to collapse
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
enmriley said:
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
Click to expand...
Click to collapse
This happened once to my TP when I first put CM7 on the device a while back. I woke up one morning, forgot to plug it in overnight and it had died. No response to any charger, I was getting worried but then I found a solution. With it plugged in, hold the power button and home button down together for 15 to 30 seconds. It was that or hold the power button down and keep pressing the home key over and over. Not 100% sure, but it came back to life and I remember it took me a couple tries. Try holding both down simultaneously for 30 seconds or a minute, if that doesn't work, push and hold power first then home right after and hold both for 30 seconds.
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
-SGA- said:
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
Click to expand...
Click to collapse
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
rhidalgo1973 said:
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
Click to expand...
Click to collapse
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
enmriley said:
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
Click to expand...
Click to collapse
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
sstar said:
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
Click to expand...
Click to collapse
In Tasker add a New profile and give it a name like Battery_Low
Choose State and then Power for the profile.
In Power choose Battery level and set From to 0 and To to say 8%
Set New Task and do Add give it a name like Shutdown and then pick the Misc category
Choose Reboot and set Reboot type to Shutdown
All done. When battery level drops to 8% or below then Tasker will shut the tablet down. Note it will do this without warning. I think one could probably arrange a pop up warning first but I preferred to keep it simple.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
enmriley said:
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
Click to expand...
Click to collapse
The only way I know is to put it on a Touchstone and after an hour or so it Will come back to life. All thanks to Reverand KYLE. His site is well worth checking out.
My Droid Turbo power buttons seems to no longer make contact (I don't hear any 'click'). I was concerned about these from the start (I've owned it since right around it came out in October last year). At the least, I was able to wake my phone up by calling it and setting the volume rocker to wake the phone. I leave the country in about 12 hours so this is a pretty frustrating discovery.
Anyway, can anyone confirm whether the Droid Turbo turns on after charging after it was turned off?
I've read in another forum that a Qi wireless charger will turn the phone on to charge it- does any know if this is how it works? If the phone is off, the Qi charger will turn it on and then perform a charging? What if it is drained completely? My buddy at work has an Energizer Qi charger, and his phone (Nexus something) did not turn on from being off when I placed it on the charger.
I have USB debugging enabled- would I be able to utilize adb to turn my phone on when it is off?
Thank you in advance, I'd try everything I'm asking except if none of them work my phones kaput.
'adb reboot' might turn it on if you have USB debugging enabled, but I would wait for someone to confirm this (I can't try it right now). I don't know how this would work but one Google result says it does.
For waking up the screen, there is Moto Display which responds to accelerometer motion and Moto Actions, Approach... which senses your hand motion.
I would just not turn it off, turn on airplane mode to conserve battery when not in use, maybe bring another phone as a backup.
Sent from my XT1254 using Tapatalk
Moto assist for the waking up
Enviado desde mi MT2-L03 HAM2 ... i'm lovin' it
Still no workaround?
I just ran into this problem. Power button is completely broken (no click, or any resistance given when pushed in), and phone died last night. The first time this happened, i plugged it in to charge and it booted right up after getting an initial charge of about 5%, but now nothing. The display shows that I'm at %100 charge, but cannot figure out how to actually power on without using the power button. Anyone had any luck with this yet?
Assuming your phone is powered off , Hold volume down key and connect charger cable. You will get into bootloader screen. Disconnect charger cable and connect phone to PC and use the following fastboot command to boot your device without actually using power button for once.
fastboot reboot
Semseddin said:
Assuming your phone is powered off , Hold volume down key and connect charger cable. You will get into bootloader screen. Disconnect charger cable and connect phone to PC and use the following fastboot command to boot your device without actually using power button for once.
fastboot reboot
Click to expand...
Click to collapse
Thanks for this. I'm in the same boat. I'm at the bootloader. What do I need to be able to send the command to the phone? Is this what ADB is for?
You're welcome
First of all, you will need to have motorola usb drivers installed in your pc, download and install from motorola
Then, you need fastboot.exe in your p and,execute from windows command line. Have a look at Minimal ADB and Fastboot thread for information on how-to and downloads.
The rest as i posted, when the phone is off, keep volume down key pressed, connect charger, you will be in bootloader mode. This mode will let your phone and pc communicate only via fastboot protocol. So you can use the " fastboot reboot " command to start your device without a working power button.
dude you are the man. this thread and method saved me of having to buy a new phone cause i thought my phone was gonna be a paper weight. thanks for all the info on the fastboot protocol
i love you, thanks man.
from Brazil
Semseddin said:
You're welcome
First of all, you will need to have motorola usb drivers installed in your pc, download and install from motorola
Then, you need fastboot.exe in your p and,execute from windows command line. Have a look at Minimal ADB and Fastboot thread for information on how-to and downloads.
The rest as i posted, when the phone is off, keep volume down key pressed, connect charger, you will be in bootloader mode. This mode will let your phone and pc communicate only via fastboot protocol. So you can use the " fastboot reboot " command to start your device without a working power button.
Click to expand...
Click to collapse
It's been stuck on "waiting for device" for a while now, how long should it take?
Qi Charger Works
"I've read in another forum that a Qi wireless charger will turn the phone on to charge it- does any know if this is how it works? If the phone is off, the Qi charger will turn it on and then perform a charging? What if it is drained completely? My buddy at work has an Energizer Qi charger, and his phone (Nexus something) did not turn on from being off when I placed it on the charger."
The Qi Wireless Charger works whether your phone is charged or not.. I went to the Verizon store and asked to see the charger demo'd... I placed my powered off, Fully Charged, Broken -power- button- Droid Turbo on the charger and it Came to life.
I immediately configured the phone with an alternate power button app to control the screen on/off. FYI None of the apps I found will actually power the phone on from off, but will control the screen once it is powered.
I actually tried everything in this forum short of the disassembly of the phone but that was next... the program download.. Reboot Fast Boot; I couldn't get it to download correctly. after about 3 hours I quit... drove to the store and the rest is history. So Glad Not to have Lost everything!..
When I try this in the command prompt it says The device is not ready. I have all the Motorola's drivers downloaded so why isn't it working?
Thanks so much for sharing the minimal adb fastboot info, my son had issues with his droid turbo power button. I ear raped him for not taking care of his phone. I felt bad but we were both amazed at my new computer skills. im totally a computer retard and powering his phone back up with that program felt great ....THANK YOU SO MUCH!!!!
You are welcome and i would like to thank to that unknown hero for gifting me one month adfree xda
Thanks - using Qi charger "solution"
N7FALCON said:
"I've read in another forum that a Qi wireless charger will turn the phone on to charge it- does any know if this is how it works? If the phone is off, the Qi charger will turn it on and then perform a charging? What if it is drained completely? My buddy at work has an Energizer Qi charger, and his phone (Nexus something) did not turn on from being off when I placed it on the charger."
The Qi Wireless Charger works whether your phone is charged or not.. I went to the Verizon store and asked to see the charger demo'd... I placed my powered off, Fully Charged, Broken -power- button- Droid Turbo on the charger and it Came to life.
I immediately configured the phone with an alternate power button app to control the screen on/off. FYI None of the apps I found will actually power the phone on from off, but will control the screen once it is powered.
I actually tried everything in this forum short of the disassembly of the phone but that was next... the program download.. Reboot Fast Boot; I couldn't get it to download correctly. after about 3 hours I quit... drove to the store and the rest is history. So Glad Not to have Lost everything!..
Click to expand...
Click to collapse
Thanks for the confirmation that this works. Not comfortable taking my Droid Turbo apart and would prefer to avoid that if at all possible. I have multiple QI chargers at home and work so hopefully that sustains until I get a new phone in 6 months. Will re-explore disassembly as an option when I find a good video for the Droid Turbo.
The Fastboot method worked perfectly! I'll be able to limp along until I get my upgrade. Thanks!
Like yours, my Verizon Droid Turbo has a broken power switch. I accidentally allowed the battery to drain completely and could not get it powered on. However, I placed it on my QI charger I use for my Samsung Galaxy S7 Edge and it powered right up. Very happy that worked for me.
stuck in fastboot flash mode
Somehow I uninstalled my OS when trying to flash a ROM, and I'm stuck in Fastboot Flash Mode. My power button is broken. I can use ADB and do "Fastboot Reboot" but I'm still stuck in the bootloop. What other fastboot commands can I use to install a ROM that is on my internal storage? Or I have a download on my computer that I can use... Please help!
gherman222 said:
Somehow I uninstalled my OS when trying to flash a ROM, and I'm stuck in Fastboot Flash Mode. My power button is broken. I can use ADB and do "Fastboot Reboot" but I'm still stuck in the bootloop. What other fastboot commands can I use to install a ROM that is on my internal storage? Or I have a download on my computer that I can use... Please help!
Click to expand...
Click to collapse
Well, using fastboot you can boot to TWRP.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
adb reboot recovery
Function: Reboot your phone into recovery mode.
A lot of functions like flashing ROMs to your phone require you to boot into recovery mode. Normally, this requires you to hold down a particular set of buttons on your phone for a certain length of time, which is obnoxious. This command allows you to boot directly into recovery mode without performing the complex finger dance of your people.
Click to expand...
Click to collapse
From TWRP you can install the OS, you can drag files from your PC to install on your phone, you can RESTORE the backup I KNOW you made before doing any of this.
ChazzMatt said:
Well, using fastboot you can boot to TWRP.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
From TWRP you can install the OS, you can drag files from your PC to install on your phone, you can RESTORE the backup I KNOW you made before doing any of this.
Click to expand...
Click to collapse
Haha, yes I do have a backup, but I can't get into recovery due to my broken power button and being in Fastboot Flash Mode. I checked the link, but didn't see the proper command... what is the command for Fastboot to TWRP recovery?
Here is what I'm seeing:
Bootloader: Slot-count: not found
Bootloader: Slot-suffixes: not found
Thank you for any more help you can provide!
I've had my Droid 4 completely lose battery on one or two occasions where I wasn't paying attention to it while doing something else.
It turns out that I have to plug it in and wait until the battery is at 100% to get it to start up again. What is the way around this? Just holding the power button turns the phone on, shows the motorola boot logo, and then shows the battery at whatever percentage it's currently charged to. How do I bypass this and start into the ROM and then just charge from there?
In an emergency when I'm waiting for a call or something, this is something I need to be able to do.
Careless_ said:
It turns out that I have to plug it in and wait until the battery is at 100% to get it to start up again. What is the way around this? Just holding the power button turns the phone on, shows the motorola boot logo, and then shows the battery at whatever percentage it's currently charged to. How do I bypass this and start into the ROM and then just charge from there?
Click to expand...
Click to collapse
The power button on my phone is completely non-functional, so I have to plug it into a charger to "kick-start" it on the rare occasion that it's completely shut off; which, more often than not, is when my now rapidly-aging battery craps out and I don't catch it in time. So I face this every now and then.
The solution:
Let the phone charge enough to safely boot; 10% oughtta do it. It seems that the phone does charge whenever power is being supplied regardless of its state, but the amount of drain while booting means your charger by itself probably won't keep up
Unplug the phone; this should make it shut off
While holding Vol+ and Vol-, plug the phone back in (you may be able to use the power button instead of plugging in, but I wouldn't know). This will bring up the menu of which the name escapes me at the moment
Unplug the phone (may or may not actually be necessary for success, but I always do)
Select Recovery (Vol- navigates, Vol+ selects); this will get you into the 96% useless stock recovery
Press Vol+ and Vol- together until the menu comes up; this might take several tries because either the phone is fidgety or the timing is stupid-precise
Select Reboot (either Enter or Ok on the keyboard to select, I forget)
The phone should reboot properly, skipping the forced charging thing. You can (and should) plug the charger back in anytime after you hit Safestrap/the post-SS kexec buzz if you have the custom SS installed which disables the popup at boot.
Septfox said:
The power button on my phone is completely non-functional, so I have to plug it into a charger to "kick-start" it on the rare occasion that it's completely shut off; which, more often than not, is when my now rapidly-aging battery craps out and I don't catch it in time. So I face this every now and then.
The solution:
Let the phone charge enough to safely boot; 10% oughtta do it. It seems that the phone does charge whenever power is being supplied regardless of its state, but the amount of drain while booting means your charger by itself probably won't keep up
Unplug the phone; this should make it shut off
While holding Vol+ and Vol-, plug the phone back in (you may be able to use the power button instead of plugging in, but I wouldn't know). This will bring up the menu of which the name escapes me at the moment
Unplug the phone (may or may not actually be necessary for success, but I always do)
Select Recovery (Vol- navigates, Vol+ selects); this will get you into the 96% useless stock recovery
Press Vol+ and Vol- together until the menu comes up; this might take several tries because either the phone is fidgety or the timing is stupid-precise
Select Reboot (either Enter or Ok on the keyboard to select, I forget)
The phone should reboot properly, skipping the forced charging thing. You can (and should) plug the charger back in anytime after you hit Safestrap/the post-SS kexec buzz if you have the custom SS installed which disables the popup at boot.
Click to expand...
Click to collapse
Yes... this is the method I remember using once, but I couldn't get passed the useless stock recovery this time around so I thought maybe I was just dreaming. I guess my timing was just bad this go around.
Thanks again, Septfox!
My DROID 4 is like my DROID 3. When the battery completely dies, you cannot press the power button while it's plugged in.
So, Dead phone. Plug it into the charger. Wait a couple minutes, so it gets some charge. Unplug the charger, Hit the POWER button, then plug it back in.
It won't work if it's plugged in, dead, and charging. You gotta unplug it to turn it on, then plug it back in to continue charging.
That is happening not only with this model phone. On other brands is the same.
Stuck on "please lock bootloader" screen when plugging in after depleting the battery
No button inputs work. The only solution seems to be waiting until the battery fully runs out and plugging it in again, after which it sometimes boots up. At least I got it to the first time, it failed just now. Maybe I need to hold some button combination while doing so?
How do I fix this properly? And what's a sure way to get it to boot from this? I'm already wasting half and hour on a minute's charge, God forbid I ever forget about it plugged in for longer. Would have to throw it in the drawer for a couple days and probably end up with some permanent burn-in too.
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
What seems to have done the trick is holding power&volume+ (probably just power is enough), so it loops through the 'empty battery' splash screen at least once. I think that's how I did it the first time too.
drwharris said:
I haven't seen the screen in ages but doesn't it tell you to press the power button to acknowledge the unlocked bootloader? Also from memory it tells you it will automatically continue but it never does.
Click to expand...
Click to collapse
It never seemed to make any difference whether I pressed the power button or not, in fact it always booted up automatically after some time, this scenario excluded.
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
VonZigmas said:
I suppose my problem might lie in the fact that buttons aren't working on that screen for whatever reason? Rather than it not going away automatically after battery depletion.
Click to expand...
Click to collapse
i had a similar problem after a failed attempt to boot into recovery.
for me the following did do the trick and booted my phone back into system:
- deplete battery completely
- plug in charger and keep power button pressed until phone is charged enough to attempt boot
- keep the power button pressed until nokia logo appears
THMSP said:
It is a bug in the bootloader. You can get out of the screen by disconnecting (!) the cable, and then holding all three buttons for multiple minutes until the device forcefully shuts down.
Before you do that, leave the phone plugged in for 10 minutes or so, so it can charge the battery to some extend. Then start the phone without (!) the cable plugged in, and wait until it boots into Android. When it is booted, you can safely plug in the cable and let it charge to 100%.
Just make sure you leave it for some minutes so it has enough charge to boot through the bootloader and start Android.
Click to expand...
Click to collapse
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
VonZigmas said:
How long is "multiple minutes"? I tried holding all three buttons at first, but gave up after probably a minute of nothing happening. I'll keep that in mind though.
Is there any hope for this to be fixed in the future?
Click to expand...
Click to collapse
Well, multiple definitly isn't one I haven't stopped the time yet, but expect waiting and pressing them for around 2 to 3 minutes, maybe even 5. It might sound stupid, but it will work.
About fixing it, I don't know. It might be a bug in the reference bootloader that Qualcomm provides for Snapdragon 835 chipsets, and I doubt that FIH / HMD have the resources to debug and fix that.
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
OneDream said:
I get this same screen while the phone's powered off + charging and it's annoying.
I was going to start a thread to ask whether it's possible to charge this phone while it's turned off (without the screen being kept on) after unlocking the bootloader. I guess based on the posts in this thread, that's not possible? [emoji2357]
Click to expand...
Click to collapse
No, I guess it isn't. I've tried to plug it in while it's off and turn off as it's charging and in either case it resulted in the phone hanging up on that screen. I can confirm though that holding all three buttons for a while does turn it off and allow me to boot normally which is cool.
But is that possible with a locked bootloader anyway? Or does it always power on? I can't tell if I ever needed it to charge like that.
I see this "warning" message only on android pie builds, it doesn't seem on oreo builds. I think problem seems that kernel dependent (oreo is on 4.4.78 and pie is on 4.4.153). There is one way to get rid of that message, as @THMSP said, holding all 3 buttons pressed during 2-3 minutes and let it to be shuted down. Then, let the device to boot normally and plug in. Finally you shouldn't connect to charger when it's turned off on any pie build.