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.
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.)
Okay, first thing to mention is that I have searched for information on my issue and while I have found (and tried) solutions that approach my goof, I need to post this:
Last night I finished reading from Kindle app, hit the power button to shut off the screen and laid it down. I know I should have plugged it to recharge but too late now. I am running CM nightly from 07172012, so I know I didn't download the nightly CM battery issue versions.
This morning the screen will not light up; I have tried charging it, hard reset with power and home screen buttons for 15-20 seconds (and longer), and nothing works. My concern is that the screen is dead. I connected the touchpad to my laptop and I get the connection sound from the laptop; it sees the TP but does not accept it as a portable storage device. Device Manager lists it as: QHSUSB_DLOAD with driver(s) not loaded.
When I try the volume rocker button I do not hear the small audible ping as volume goes up or down. Of course, with the resets, who knows where I am in the OS (or even if it is WebOS or Android).
I really didn't want to be a noob and post this, but I need some advice from the brethren here on XDA. Thanks in advance.
It seems to me that it's not even booting if your getting that strange device in device manager. Try the webos recovery tool from hp. It may help. Although it will wipe android off.
Sent from my SGH-I777 using xda app-developers app
my son-in-law is in the same boat. Nothing he does wakes it up. I believe there are tp's out there with this hardware issue. I let my tp battery drain completely. It powers down around 4% battery. I place it on the touchstone, it charges backup and boots into moboot, then webos. I've done this twice. no problems. If it's under warranty still, send it in.
If you have a touchstone charger put it on that and leave it for a couple of hours and it Will come back to life.
See this article by Reverend Kyle http://www.reverendkyle.com/index.php/articles/146-hp-touchpad-charging-issues-solution
I hope this helps.
I've had multiple instances of black screen of death failure.
The latest one I had, I was able to restore by using a standard USB to micro USB cable (and recently NOT the HP OEM cable) to connect to the computer I usually use to sync or use HP web doctor with.
Same symtpom as the OP, get the three dings when connecting the touchpad to the computer, no responses and the QHUSB driver load error. HP charger wouldn't chage it, touchstone would not charge it.
Anyhow, I left it connected for a few hours to charge connected to my PC. Then, I disconnected from the PC using the large USB connector and reconnected. Whamo, got to the bootloader.
I believe what happened was I trickle charged the touchpad enough to get the touchpad to boot.
You can try the various hard boot keypresses too, but wait for a few hours while trying to trickle charge the touchpad via the computer USB.
Update
Okay, so I followed the old rule of doing the simple (and/or free) solutions first and then move on.
1) I set the touchpad on the touchstone for several hours yesterday - no luck
2) I connected the touchpad to my pc through the USB and let it charge - no luck
3) I let it be plugged into the standard charging plug all night - no luck
4) I prayed to the great old god Cthulhu - no luck
My only option remaining is to use WebOS Doctor. One question on that: in all the literature I have read thus far (and perhaps I am mistaken), I need to be able to get the TP into USB mode to download the corrections/reboot back into WebOS. Is that right or can I expect that when the doctor sees the mangled mess of an OS through the USB connection, it will know what to do?
Again, as always that for the previous posts and for the support.
mnachazel said:
Okay, so I followed the old rule of doing the simple (and/or free) solutions first and then move on.
1) I set the touchpad on the touchstone for several hours yesterday - no luck
2) I connected the touchpad to my pc through the USB and let it charge - no luck
3) I let it be plugged into the standard charging plug all night - no luck
4) I prayed to the great old god Cthulhu - no luck
My only option remaining is to use WebOS Doctor. One question on that: in all the literature I have read thus far (and perhaps I am mistaken), I need to be able to get the TP into USB mode to download the corrections/reboot back into WebOS. Is that right or can I expect that when the doctor sees the mangled mess of an OS through the USB connection, it will know what to do?
Again, as always that for the previous posts and for the support.
Click to expand...
Click to collapse
Another piece of black magic that worked for me and is worth a try as it is free. Connect Touchpad to standard HP brick charger plugged into power outlet. Unplug cable from charger, count to 5, plug it back in, count to 5, take it back out. Repeat the cycle until you get bored or until you get a red charging symbol. If you get the latter then let it charge up normally and you are back in business. The theory behind this method is that it takes a few seconds on plugging in for the circuits to realise they "shouldn't be charging" and this allows a little bit of charging to take place on each insertion. Repeat enough times and you get enough to kick start the proper charging. In my case about 20 times did the trick.
As I didn't want to get into this situation again I then set up a Tasker process to power down th eTouchpad if the battey charge dropped below 8% and I've been OK since.
RIP Touchpad / EOT
Well, I had to wait a day to get my hands on a WinXP laptop; I upgraded my Dell to Win8 about 3 months ago and WebOS Doctor does not play well with Win8.
While that time passed, the touchpad finally gave up the ghost. There is no power left in the TP. When I run WebOS Doc the laptop cannot see the TP connecting via USB. I also checked by connecting the TB to the Dell, since it would at least see the device. Not any more.
My thanks again to those that responded. I did try the plug in, plug out with 5 second waits between, just in case. You never know. However, after 50+ attempts I had to call it a no-go.
does your home button light come on at all? Are you able to see moboot bootloader at all or are you able to start the tablet in webos recovery mode by holding the vol key while powering it on? are you able to ./adb connect? Also I've never had much luck with the resest method youre using, holding down the power and home key, I always hold down the power key and press the home key 15 times, when I get hard freezes and lockups, it's always worked.
Mine is in the same boat for a couple of months, removed battery and charged. Boot loader is borked I get only get a qualcomm usb device but nothing thats of any use for webos doctor or qualcomm tools. We'll have to wait until someone figures out jtag or how to replace the bootloader with qualcomm tools. I'm amazed with the number of touchpads out there that something hasn't leaked from hp to fix it. Anyone got friend in hp or qualcomm :angel:
OP Update
Well, I thought this was a dead issue but here is the latest.
After wallowing it a pit of despair the likes of which can only be described as wretched, (I even coveted my wife's TP up close, almost giving into temptation and swapping decals to reverse ownership) I looked outside of XDA and did general Google searches and happened upon this site:
http://forums.webosnation.com/hp-touchpad/299256-dead-touchpad.html
After reading a bit I realized that the touchstone may be able to recharge the dead battery even though fully drained. I began the quest that Friday morning the 24th of August, after verifying that my Dell laptop did not see the TP when plugged in via the USB cable.
I just did a quick check and the laptop now "sees" the TP when connected. Still no luck on booting into Moboot or the USB icon screen - neither Power and Volume Up or Power and Home buttons achieve anything. But I am glad to see that the touchstone has placed enough charge into the battery that the laptop is aware of the TP when connected.
I believe that given a few more days on the touchstone I should be able to boot into moboot.
@ haxin - I have nothing. Not a single light from the Home button - my only evidence that there is SOMETHING going on is when I connect the TP to the laptop and get my connection "sound". Again, I have high hopes that the touchstone will get me where I am going, albeit at a snails pace.
@ paddy - Yeah, I hope that when (if) I get to a lit screen, I am able to move past where you are at. My big concern is that I am toast even with a semi charged or fully charged battery from the touchstone.
I will update later on. Again, thanks to all for the input and probing questions. You have made me think harder and work a bit longer on this project.
OP Update - 31 August
After 7 days on the touchstone, the touchpad is currently showing the low battery charge icon; I have now plugged it into the A/C adapter.
Each morning I have picked up the TP, held down the power button and held the home button for 15+ seconds. Today it worked, turning on the screen for the first time in a week and letting me see the low battery image.
In my quest to resolve this issue, I have read so many variations on what buttons to hold and how long to hold them that after awhile you end up considering the possibility that SOME of the button options are not correct. That the operator has booted their TP up, but they misconstrued the actual solution; how else can you explain the idea that HP built so many different button combinations and hold times to boot a TP from a nearly or fully dead battery state?
Anyway, I will continue to post updates until my beloved TP is back to running CM9.
And to all those who gave their TP up because the battery got too low; find a touchstone or other "trickle" charger solution, connect and let it sit for a week or so.
Thanks!
Glad the Touchstone worked for you , don't know why it has taken so long to charge but when your up an running properly Llama is a good app to install as
A:You can set alarms for when the battery gets to a certain level/levels
B:Have it shut down when the battery gets to a certain level.
I use 20% for an alarm and 10% to shut down which allows me to sleep easy and not worry if someone else is using it . .
I am up and running. I most definitely will load that app on my TP, plus my wife's and a coworker who bought a TP because of mine.
I don't know either why it took so long; I am just glad it worked and I have it back. I am on it right now.
Thanks again to all who provided feedback and guidance. This is why I love XDA.
Sent from my HP Touchpad using xda app-developers app
HP Touchpad sleeping and will not turn on
Just a note to those HP tablet owners who experience the Black screen of death or sleep of death.
I am the proud owner of 4 HP tablets and two of them so far have had the black screen of death. I have read forum after forum trying to get answers to this problem. There was only one posting that has made cense to me. Someone posted that the tablets symptoms are very much like when the Phones use to go to sleep. The solution was to disconnect the battery for a few minutes then plug it back in. Then simply hit the hold the power button down to turn on the tablet.
The problem is taking the TP apart. There is a video on youtube on how to disassemble the tp. It is a little annoying that you have to go to such lengths to reset the hardware but HP will charge you 250 dollars to fix the problem. After you watch the video on how to open the TP, remove the 3 little screws holding the battery. Now slowly pry the battery up, they use double sided tape to hold it in place along with the screws. Wiggle the battery side to side and try to disconnect the battery connector. This can be done without removing the boards in the TP. Wait 1 min then try to replace the connector in the socket. It is on the underside of a board so when you have it in place use something to make sure it is tight. Plug the charger in to the USB cable. Without closing up the unit hold the tablet power button in until you get the battery charging symbol on the display. Let the unit charge while it is still disassembled. Just in case you have a problem. Once everything is operating disconnect to charger and replace the battery screws, now snap everything together.
This was the only way I was able to fix two of my four TP's. I am sure I will have to do this again because my kids always let the tablets go dead and they don't pay attention when placing them on the Stone for charging. If the tablet is not properly placed on the stone the tablet will not charge.
Hope this helps.
This by far is the best tablet for the money anywhere.
msousa1 said:
Just a note to those HP tablet owners who experience the Black screen of death or sleep of death.
The solution was to disconnect the battery for a few minutes then plug it back in. Then simply hit the hold the power button down to turn on the tablet.
The problem is taking the TP apart. There is a video on youtube on how to disassemble the tp. It is a little annoying that you have to go to such lengths to reset the hardware but HP will charge you 250 dollars to fix the problem. After you watch the video on how to open the TP, remove the 3 little screws holding the battery. Now slowly pry the battery up, they use double sided tape to hold it in place along with the screws. Wiggle the battery side to side and try to disconnect the battery connector.
Click to expand...
Click to collapse
I realise this is an old thread, but I recently had a reoccurrence of the black screen of death issue and thought given the number of touchpads still out in the wild, I would share my experience on the off-chance it may help somebody.
My first experience of the black screen issue was a few months after having my touchpad (many years ago). The screen just went black and no combination of holding the reset keys for any period of time would restart the unit. I had suffered lock-ups before and found the reset combination to be successful, but this time none of that worked and I had effectively what appeared to be a dead unit.
Having contacted HP, I returned the unit under warranty and a unit was returned working. I say “a unit” as I was never quite sure if it was the same unit or a refurbed unit, but to be honest given the speed the units went out of stock during the fire sale, I was just glad to have a working unit again.
Well this week after several years of use including the installation of Android, the black screen occurred again. As before, no combination of the keys / holding for a period of time / pressing them a number of times etc had any effect. The unit was three quarters charged and I was using it up till the point the screen went black. :crying:
Given that the unit has no warranty and it was “dead” anyway, I decided to take it apart. Despite watching YouTube videos, this appeared to be more troublesome than I thought, but eventually I was in. Interestingly, the backlight on the screen was still lit, suggesting the unit was still powered. I did consider disconnecting the battery, having removed the screws as per the previous poster, but mine seemed to be well and truly stuck down and I felt I may damage it prying it away from the base.
However, looking around inside the unit, I spotted what was clearly a surface mounted switch that faced upwards towards the back of the screen. Out of interest, I pressed on this switch with my finger nail and my unit powered off (shown by the backlight turning off). I then pressed the normal power switch and the unit powered up as normal. I have attached a photo of the switch which resides close to the popout tab with serial numbers on that can be found on the right hand side of the unit.
It does appear strange that HP put this “reset” button inside the unit, facing inwards rather than outwards where a small hole in the back of the case could be used to press it. So if you do get to the opening the case stage, consider this as an alternative to prying the battery loose. Also if somebody can work out a way to make the button accessible from outside the case it might be a useful modification.
JoeG90 said:
<.......................................>
However, looking around inside the unit, I spotted what was clearly a surface mounted switch that faced upwards towards the back of the screen. Out of interest, I pressed on this switch with my finger nail and my unit powered off (shown by the backlight turning off). I then pressed the normal power switch and the unit powered up as normal. I have attached a photo of the switch which resides close to the popout tab with serial numbers on that can be found on the right hand side of the unit.
It does appear strange that HP put this “reset” button inside the unit, facing inwards rather than outwards where a small hole in the back of the case could be used to press it. So if you do get to the opening the case stage, consider this as an alternative to prying the battery loose. Also if somebody can work out a way to make the button accessible from outside the case it might be a useful modification.
Click to expand...
Click to collapse
Oh I was so keen when I came across this post. A Reset Button! How great would that be?
Tried it, unfortunately it did not resurrect my dead as a doorstop TP. I was so hoping...
I just put a 'new' EBay battery in it a couple of days ago and tried trickle charging with a 1000mA charger for 24hrs. No joy there either.
All I get when I plug it into the PC is that it shows up as a "QDLoader 9008" (QHSUB_DLOAD driver) .
No flicker of life or light whats so ever...
_mr
middle_road said:
Oh I was so keen when I came across this post. A Reset Button! How great would that be?
Tried it, unfortunately it did not resurrect my dead as a doorstop TP. I was so hoping...
I just put a 'new' EBay battery in it a couple of days ago and tried trickle charging with a 1000mA charger for 24hrs. No joy there either.
All I get when I plug it into the PC is that it shows up as a "QDLoader 9008" (QHSUB_DLOAD driver) .
No flicker of life or light whats so ever...
_mr
Click to expand...
Click to collapse
Try to borrow a Touchstone conductive charger if you can. It's the only thing that has worked for me when it has totally drained down.
All the best.
sstar said:
Try to borrow a Touchstone conductive charger if you can. It's the only thing that has worked for me when it has totally drained down.
All the best.
Click to expand...
Click to collapse
That's what I was thinking - no joy there either... It is not even showing signs of getting the least bit warm.
I keep thinking and hoping that there is some way to resurrect this one but I may be wrong...
It's currently trickling on a 1000mA charger. Tomorrow I'm going to try the Touchstone behind it.
If that doesn't start something then I'm going to yank the new battery and along with the old battery charge them like an RC device.
(if I can ascertain the proper way to do that --- )
_mr
After several days on the trickle, still no life.
Took it apart at lunch and with the battery still connected to mobo it is showing 3.1V across the red/black. So I figure the battery
is good. Looks like the mobo is gone.
Not sure what else to try.
_mr
Hello guys,
I'm new here at the HP Touchpad Section and XDA-Dev Forums.
I am running CM7 on our HP Touchpad and my little brother has been fiddling with it(downloading many apps from the playstore using my personal account, thus forcing me to create a new google account/other shiz).
Then one time, the screen kept turning on and off without us even touching it. Our guess was it was dust on the screen which is being register as touch.
After a week or so that that was happening, the touchpad ran out of battery and was not charged right away.
The result, it won't charge anymore.
Is there anyway to open the device and shock the battery? It may be a dead battery just like what happened to my sister's iPhone.
I've also been reading some charging issues with CM7 and CM9 and tried some of their troubleshooting methods but non worked.
If I just get a little juice to boot it, I would reboot back to webOS as fast as I can and uninstall CM7.
Thanks in advance,
Raphael
SCPadgeebar said:
Hello guys,
I'm new here at the HP Touchpad Section and XDA-Dev Forums.
I am running CM7 on our HP Touchpad and my little brother has been fiddling with it(downloading many apps from the playstore using my personal account, thus forcing me to create a new google account/other shiz).
Then one time, the screen kept turning on and off without us even touching it. Our guess was it was dust on the screen which is being register as touch.
After a week or so that that was happening, the touchpad ran out of battery and was not charged right away.
The result, it won't charge anymore.
Is there anyway to open the device and shock the battery? It may be a dead battery just like what happened to my sister's iPhone.
I've also been reading some charging issues with CM7 and CM9 and tried some of their troubleshooting methods but non worked.
If I just get a little juice to boot it, I would reboot back to webOS as fast as I can and uninstall CM7.
Thanks in advance,
Raphael
Click to expand...
Click to collapse
Try leaving it on the stock charger for several hours, maybe days. If you have a touchstone, try that.
If you get it to charge (make sure it's fully charged), uninstall CM7 using acmeuninstaller, then boot into webos. If you have preware installed fine, if not install it and download 'remove android' (or something like that). Run it, then install either CM9 or cm10, using acmeinstaller3. There are several good how-to's which you can search for here or at webos nation forum.
When you have it installed, go to settings > storage and click on the 3 little squares on the upper right hand side, and click on usb computer connection. Then make sure the MTP box is checked.
Hope this helps. Good luck.
chicle_11 said:
Try leaving it on the stock charger for several hours, maybe days. If you have a touchstone, try that.
If you get it to charge (make sure it's fully charged), uninstall CM7 using acmeuninstaller, then boot into webos. If you have preware installed fine, if not install it and download 'remove android' (or something like that). Run it, then install either CM9 or cm10, using acmeinstaller3. There are several good how-to's which you can search for here or at webos nation forum.
When you have it installed, go to settings > storage and click on the 3 little squares on the upper right hand side, and click on usb computer connection. Then make sure the MTP box is checked.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Thans for the reply chicle_11! Will try that on the weekends since I am very busy with school works. And thanks for the suggestion of installing CM9/CM10 but I will just stick to webOS and get an authentic Android Tablet(I'm choosing between Google Nexus 10 or Samsung Note 10.1).
I use webos at least 50% of the time. It's a shame that there aren't more apps compared to android. You don't have anything to lose by installing android. You'll have an excellent and unique dual boot tablet. CM10 is very stable now, I use it as my daily driver, I highly recommend it.
chicle_11 said:
I use webos at least 50% of the time. It's a shame that there aren't more apps compared to android. You don't have anything to lose by installing android. You'll have an excellent and unique dual boot tablet. CM10 is very stable now, I use it as my daily driver, I highly recommend it.
Click to expand...
Click to collapse
I still might reconsider flashing CM9/CM10 when I sort out the charging problems since I am just starting to save money for the Note 10.1/Nexus10.
Can you recommend a good CM10-based ROM for the HPTP or just the stock CM10 Jcsullins?
I use/recommend jcsullins' cm10.
Make sure MTP is checked (follow my first post) and that should take care of the charging problems.
Also, try to not let the battery run out of power. It could possibly brick the tablet.
It seems that I have somewhat sorted out the charging problems. I read an article last night that Samsung Chargers also work for the HPTP.
The process is fairly simple. Use the Samsung Charger first to charge a phone. After 2 hours or so, use that charger for the HPTP to charge the touchpad from a used/electrified wire. During the other process, use the HPTP Charger for the phone to power the cord up. After 10mins or so, switch both chargers. So the HPTP should be using the one that came with it by this time.
It worked for a while then the "Please use the charging cable that came blah blah blah to fully charge..." message came. I've read another article that the touchpad should be a little elevated or at least level with the cord so the cord will not fall down that is causing the message to pop up.
I've used both methods and the 2nd method is working like a charm. It shows a battery sign with a lightning bolt and the charging warning/message does not pop up. Will leave it overnight to see if it charges.
Then after, I might reinstall CM9(I've been from CM9 but downgraded to CM7 because of camera issues w/c my lil bro does not like).
So I left it overnight and it charged when I used the 2nd Method. Happy Days!
SCPadgeebar said:
During the other process, use the HPTP Charger for the phone to the cord up. After 10mins or so, switch both chargers. So the HPTP should be using the one that came with it by this time.
Click to expand...
Click to collapse
What?
*fixed*
Sorry, That was late night here in the PHL and was a bit sleepy when I was posting that.
Also have dead touchpad
I haven't been able to see any life from my touchpad after the battery completely drained. Its been 2 days since I haven't been able to use it.
I've tried charging it via the cable and adapter that came with it for a couple of hours, left my TP on the touchstone all afternoon to morning and no life either, the touchpad however is a bit warm at the back. Does that indicate its charging?
my TP is sitting on the touchstone now but I've replaced the AC adapter and currently using my HTC Sensation plug, I am running out of ideas and I'm going to presume its completely dead.........
I've tried connecting it to the pc but nothing happens, Can someone help me out, I've also tried the button combinations "Home, Home+Power and Home+Power+VolumeUp"
I tried both of the methods mentioned a couple of posts ago with no success.
I have also left it on the regular AC charger for 48+ hours and a Samsung cell phone charger for another 48+ hours and nothing.
It is sitting on the Touchstone now for 36+ hours and nothing yet.
I sent HP an email and here is what they said to try:
"We gather from your mail that your Touchpad is unresponsive and will not turn on. To be able to help you with this issue please take note of the following troubleshooting steps:
First of all leave the device on charge with charger for 48 hours after do the following:
Press and hold the power button + Center for 15 seconds. The device may take a few minutes to restart.
Please do the above with the device connected to the charger. (not charging dock nor PC).
Press and hold the power button + volume Up + Center and continue holding for 5 seconds after the Full Erase screen appears.
Also please try the above steps with another USB cable, also please try to connect the USB to the computer with the touchpad, if the computer doesn't recognize the device, the USB cable is faulty.
Please try your charger on another device to see if this charges the device. As the issue could be that the AC adaptor that is not working.
Have you tried another charger with the Touchpad? In order to verify where is the problem. Regarding to your problem ,do you know if the problem is with the charger itself or with the USB cable? Have you tried the complete charger with another Device, phone?
If the steps given do not help you with this issue, please send us a Proof of Purchase (scan of store`s receipt attached to your response) to validate your warranty or the order creation date of your device and your address.
If you need further assistance, please reply to this message and we will be happy to assist you further.
For information on keeping your webOS and Palm products up and running, please visit our website at: http://www.hpwebOS.com
Sincerely,
HP webOS SUPPORT"
None of that worked either. I just get the "Palm device" balloon on Windows XP when I hold the Power+Volume Up + Center button. It looks for drivers but never finds them.
Also try holding Home + Power button for 30 seconds instead of 15...This has been known to force some life back for some
Con500 said:
Also try holding Home + Power button for 30 seconds instead of 15...This has been known to force some life back for some
Click to expand...
Click to collapse
Nothing after trying that and leaving it on the Touchstone for 48+ hours. Time to leave it plugged up to the computer for 48+ hours and see what happens.
Nothing after 48+ with the factory USB cable connected to a desktop computer.
It would be nice to see a solution that works every time instead of a bunch of guesses.
abomb78 said:
Nothing after 48+ with the factory USB cable connected to a desktop computer.
It would be nice to see a solution that works every time instead of a bunch of guesses.
Click to expand...
Click to collapse
First my observations on three 32 GB TP's:
My discharge rate on WebOS in Airplane mode was arround -613 to -850mA. Screen on, (brightness affects this).
3. My discharge rate on CM10 in Airplane mode is about -520mA!!
4. A PC's USB port puts out 500mA's!!!
5. On the touchstone, (doesn't seem to matter if WiFi is on or off), with screen on 1/3 brightness + Battery Monito Widget = +853 to 945mA
6. On HP charger & cable, same as above = +1,377mA
What suprised me was the greater drain in WebOS.
You PC's USB port may be causing further discharge to the 2% TP's auto shut-off!
Actually none of these goofy button pressing and charging methods was right. A6 was faulty. It is fixed now.
My TouchPad is dead
abomb78 said:
Actually none of these goofy button pressing and charging methods was right. A6 was faulty. It is fixed now.
Click to expand...
Click to collapse
My TouchPad discharged overnight and now just has a black screen. None of the button pressing or charging suggestions described in these forums has worked for me. I was just running webOS 3.0.5. No version of Android was on the TouchPad.
Please tell me the trick you used to revive your dead TouchPad. Was it just a problem with your Andriod OS?
Much thanks.
bluechip64 said:
My TouchPad discharged overnight and now just has a black screen. None of the button pressing or charging suggestions described in these forums has worked for me. I was just running webOS 3.0.5. No version of Android was on the TouchPad.
Please tell me the trick you used to revive your dead TouchPad. Was it just a problem with your Andriod OS?
Much thanks.
Click to expand...
Click to collapse
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__300
I recently went on a 3 month trip. Before I left, my nook was working perfectly fine, when i got back, it didn't work at all. It's not dead because i left it plugged in overnight but it still didn't turn on. when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all. I can't get to recovery either.
This is a Nook HD, I believe it had CM11.
:crying:
Can this be fixed
or should i plan it's funeral
Same here
The same has happened to me. Screen doesn't turn on, but there is power, I can play it into my laptop and something is there, just not enough.
Good excuse for a new tablet!
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
tambourineman86 said:
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
Click to expand...
Click to collapse
If would be fab if you could fix. Seems to be a common issue
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
tambourineman86 said:
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
Click to expand...
Click to collapse
Not sure we have the same problem. My screen doesn't come on at all, I don't get a battery depleted icon, no matter how long I hold in the power button. The only sign of life I get is when it's plugged in, when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
YMMV. But mine was the same issue. You should be able to get the icon by holding the power button down for 5 or 6 seconds. I'd say just eff with it until that icon appears. Try different button combinations. I used power and home trying to get the icon to show.
developerbuzz said:
when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
Click to expand...
Click to collapse
Anyway... since people are continually running into this kind of issue...
Give or take 21 seconds after turning orange it turns green during actual boot cycle into rom
Give or take 10 seconds after turning orange is cwm internal recovery.
After about 10 seconds the charging screen image disappears.
The charging screen image once finally no longer may not show up again until full power off/on (holding power button > 10 seconds or full battery discharge). Unplugging and plugging back in does nothing except making the device look bricked if there's too much light shining on it.
Device may not automatically leave the above state under a specific situation(s). May still need manual full power off/on.
Guessing 10 seconds could also be something else during the early/late boot process or other. The light changing color though should indicate that something is indeed happening.
Light should stay green during the boot process if its completely and fully no questions asked 100%. If you go based on that than yours doesn't appear to be completely fully charged which should either mean its turning on and using battery or not charging correctly.
The light turning off is curious. The device could be shutting off. If light comes back on a moment later then the device has rebooted. if the light stays off = n/a.
If its booting into recovery then the device would be available via adb. At that point it could be further evaluated.
On the off chance the screen was damaged it should boot and usb should be available via computer as well as adb.
If not then its probably toast unless its simply not getting a good enough current causing mislead battery stats and/or not enough energy to get to charging screen (bad wall power adapter in use, damaged power cable - though could be bad battery, defect, damage or whatever). OR there's some major error on behalf of the user happening (think should have tried that in the morning not while 1/2 asleep or came home from long trip and forget how that works).
Maybe the only other things are the emmc brick bug, was left sitting in the sun or heat or ocean air or other physical damage/defect even to the power port as well.
Or maybe it was mad that you left it. Shouldn't have hurt its feelings you know. At least its not crying battery acid on you.
That should just about cover everything except for the things not mentioned. Since its your device, you decide what happened.
Its complicated so anyone see any improvements, clarifications, or mistakes? Please put it in a post.
Jsorren said:
when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all.
Click to expand...
Click to collapse
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
sandsofmyst said:
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
Click to expand...
Click to collapse
I actually ended up fixing it yesterday!! I haven't touched it in about 3 months, and I was planning on just throwing it out getting rid of it some how. For the heck of it, I decided to plug it in, assuming that it was gonna go through the same process. But this time it went from green to amber, but it never went off. So I pressed the power button and the battery icon appeared. This was a really good sign. So I left plugged in for about 5 to 10 minutes then tried to power on.:fingers-crossed: As soon as I saw that '' Nook" boot up screen, my heart stopped. It booted up perfectly and I almost blew up from excitement :victory:. So I then flashed the stock firmware back onto it, so this would never happen again.
I guess the battery had to be completely depleted or just had to cool down. Idk but either way this was one heck of a miracle
So I recommend for anyone having this problem to just leave it off and don't mess with it. I wouldn't say for 3 months like I did but maybe test it each week or wait a month if you have good patience
Wow. Man, that's awesome! Glad you posted that update on it. Thought if you had posted an update it would be the opposite as in trashed it
Actually, I guess only you could answer if you had also moved/unplugged the power cable from the wall adapter or put it into a different wall adapter, etc. Thinking there could have been a difference there.
These modern day devices are so finicky, guess anything is possible. Like you say, maybe sitting without power is another answer.
From some experimentation I have etermined that your power adapter (that plugs into the outlet) is the issue. It does not like to be leaft plugged in indefinately. It will continually use power even when the nook is not plugged in.
Also, if you use a differnt adapter you will have the same problem unless it is also of the exact same voltage and amps.
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.