Currpted Filesystem for TP - TouchPad Q&A, Help & Troubleshooting

Hi Guys,
I was trying to install Arch Linux on my TP to trippleboot Webos/Arc Linux and Android, I ended up in completely curruting the file system. Webos dector didn't help.
I am trying to recreate after deleting the whole file system. Can anyone suggest some steps to recreate my filesystem so that I can run webos dector.
Thanks

http://forum.xda-developers.com/showthread.php?t=1426244 is the thread that allows you to recreate your WebOS filesystems to make room to reinstall Android.

Thanks a lot ve6ay. That's really helpful. after I wiped all the partition. the battery died ( since I was not able to boot, I was not aware of battery level ). now I charged it for a day and it doesn't comeup. It would be really helpful if you suggest can I do something. or I need to throwaway my touch pad.
Thanks,
Pav

Using the HP supplied charger cord and adapter, plug it into the power socket for about half an hour or so, then you should have enough juice in it to turn it on. Press and hold Power-VolUP and you should have it come up - if not that, then Power-Home. Either method should force it to turn back on. As soon as it comes up, hit Power-VolUp and go back to flash mode, and then run the Doctor.
Also, when trying to turn it on, keep it plugged in - either to the computer or the wall, with the cable provided. Any other cable and it might not work.

Related

Bricked Touchpad need help

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.

[Q] Bricked? HP Touchpad

Not quite sure if my touchpad is bricked or not. I had it set up to triple boot web os, android, and arch linux.
Due to an unknown error installing arch corrupts my android 'SD card.' So to fix this I was going to start over, doctor the tablet to stock, moboot, install arch then put on android.
I put the tablet into the USB/recovery mode (power + volume up,) started doctoring it (doctored as normal, rebooted tablet, showed the arrow pointing to the chip)
When it was done the tablet restarted, then it went into this infinite boot loop. I left it for about half an hour, when I came back it was still stuck, holding the power button doesn't do anything, so I power+volume+center button to force shut down. Now it won't start, when I plug it into my computer it registers as an unknown device with the name of "palm"
I've looked and no one has had the 'same' problem as I have.
2kool4u526 said:
Not quite sure if my touchpad is bricked or not. I had it set up to triple boot web os, android, and arch linux.
Due to an unknown error installing arch corrupts my android 'SD card.' So to fix this I was going to start over, doctor the tablet to stock, moboot, install arch then put on android.
I put the tablet into the USB/recovery mode (power + volume up,) started doctoring it (doctored as normal, rebooted tablet, showed the arrow pointing to the chip)
When it was done the tablet restarted, then it went into this infinite boot loop. I left it for about half an hour, when I came back it was still stuck, holding the power button doesn't do anything, so I power+volume+center button to force shut down. Now it won't start, when I plug it into my computer it registers as an unknown device with the name of "palm"
I've looked and no one has had the 'same' problem as I have.
Click to expand...
Click to collapse
Read this thread, it might help : http://forum.xda-developers.com/showthread.php?t=1426244
Good luck.
I went to try that out today, i pressed the power button and it came up with the Low Battery icon, so i plugged the charger into the tablet and it just hangs at the image. It charged for over an hour an a half, but still shows the dead battery symbol.
Condition just keeps getting worse :/
After leaving the touchpad disconnected since my last post, I got home tonight and tried something new, knowing the battery was dead again, I held the "power + volume up" until the device turned on. When it did, it displayed the dead battery symbol, WHILE STILL HOLDING THE POWER+VOLUME BUTTON, I plugged the tablet into the wall charger, and then left it to charge for about 45 min. When I came back it was displaying the usb connect mode, from there I used the guide posted above. I reformatted the logical volumes, starting webos doctor 3.0 my touchpad battery died again, so its charging now, ill try again in a bit. But many, many thanks to you for posting that guide, I thought my touchpad turned into a paperweight.
2kool4u526 said:
After leaving the touchpad disconnected since my last post, I got home tonight and tried something new, knowing the battery was dead again, I held the "power + volume up" until the device turned on. When it did, it displayed the dead battery symbol, WHILE STILL HOLDING THE POWER+VOLUME BUTTON, I plugged the tablet into the wall charger, and then left it to charge for about 45 min. When I came back it was displaying the usb connect mode, from there I used the guide posted above. I reformatted the logical volumes, starting webos doctor 3.0 my touchpad battery died again, so its charging now, ill try again in a bit. But many, many thanks to you for posting that guide, I thought my touchpad turned into a paperweight.
Click to expand...
Click to collapse
Try to not let the TP run out of power completely, it's definitely not good for it. I'm glad you got it running again.
chicle_11 said:
Read this thread, it might help : http://forum.xda-developers.com/showthread.php?t=1426244
Good luck.
Click to expand...
Click to collapse
I have similar issue as OP. My TP will not charge or even boot up after unsuccessful "visit" to the doctor (12% freeze error then strange pc disconnect)... I have same "palm" recognition in device manager. The screen had HP logo with chip. I messed up and reset the TP now won't start up...
I will let it sit on the charger for a bit. Any suggestions to recovery this is appreciated.
mexigga said:
I have similar issue as OP. My TP will not charge or even boot up after unsuccessful "visit" to the doctor (12% freeze error then strange pc disconnect)... I have same "palm" recognition in device manager. The screen had HP logo with chip. I messed up and reset the TP now won't start up...
I will let it sit on the charger for a bit. Any suggestions to recovery this is appreciated.
Click to expand...
Click to collapse
Leave it plugged in for at least a few hours, then try the link.
http://forum.xda-developers.com/showthread.php?t=1426244
chicle_11 said:
Leave it plugged in for at least a few hours, then try the link.
http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Ok, I'll give it a shot.
thing is dead... Only pc picks it up as a palm device...
Will a battery pull do any good?
Bump.
mexigga said:
thing is dead... Only pc picks it up as a palm device...
Will a battery pull do any good?
Click to expand...
Click to collapse
I don't know if you've solved the problem or not, but take a look at this thread :
http://forum.xda-developers.com/showthread.php?t=1971859
I hope it helps.
BTW, it's a pain to get to the battery (opening the TP).
chicle_11 said:
I don't know if you've solved the problem or not, but take a look at this thread :
http://forum.xda-developers.com/showthread.php?t=1971859
I hope it helps.
BTW, it's a pain to get to the battery (opening the TP).
Click to expand...
Click to collapse
thanks...I checked this out and if only I could get the TP into USB mode I'd be home free. I believe it to be stuck in download mode. The last screen I saw was the white arrow with the micro chip

[Q] HP Touchpad Not Charging.

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'm not sure if my TP is charging...

This is the second time I've had my TP hit 0% battery while in CM9 (relatively recent nightly build) and auto power off and not respond to charging or boot attemps. I can't say for sure which nightly but probably from 6-12 months ago. It's been realtively stable with no problems i could discern. Anyways. Recently, the first time it lost power down to 0% I searched for solutions to the problem. I found the solution, based on the symptoms, to be TPdebrick. I followed those directions to the letter and within a day or two my TP was back up and running after fully charging. I don't recall precisely what occured after completing TPdebrick and the TP booting up again as I had gone to sleep, then to work, had a bunch of other stuff to do after work, then sleep again before I went to check on the TP to use it.
I'm concerned that it isn't actually charging it this time, even though TPdebrick completed successfully. I have tested the USB cable and charger and they are both fuctioning and able to charge my smartphone. The wierd thing is it did charge for a short period of time right after using TPdebrick (according to the output the battery voltage was at 30xxxxx [I don't remember the numbers where I substituted xxxxx]). But not enough for it to reach minimum charge to boot. When after 24 hours on the charger it was still no responsive I thought I'd run TPdebrick again to try and jump start it again so to speak. This time around from the log is the following:
Starting battery authentication...
Battery authentication successful.
battery_info.percentage = 0, battery_info.voltage = 3225680, battery_info.current = 937, battery_info.temperature = 20
This appears to show that it did charge up a little bit from that brief time it began to charge. And that it was recieving a small amount of charge from the PC. Typically when it is charging the cylinder part that plugs into the outlet gets warm. But it isn't getting warm as expected when the TP is connnected. I've also twisted the plug part off and back on several times along with using my smartphone to test that it was able to charge each time. So I'm stuck not knowing if the TP is actually charging because I have no visual or physical indicators that I can determine if it is or not. Any help would be appreciated.
Install the attached file to your touchpad and run it with your charger plugged in. It will tell you if your battery is charging and what current it is receiving.
Just unzip the attachment and install the .apk
Peace
chris5s said:
Install the attached file to your touchpad and run it with your charger plugged in. It will tell you if your battery is charging and what current it is receiving.
Just unzip the attachment and install the .apk
Peace
Click to expand...
Click to collapse
Since I can't boot the TP how do I install that and use it to get the info? Unless there is a misunderstanding. TPdebrick fixes it so it can charge so it will boot but I don't know if it is for sure charging so that it will eventually boot or if I need to use TPdebrick again. Assuming that despite the appearance of TPdebrick having completed successfully running it somehow didn't fix something. I would assume that at this point my options are few. If software means of getting it to boot again don't work I would have to disassemble the TP to get inside and somehow charge the battery up with a crude hand made rig or something. Assuming that the failure to boot is simply lack of charge. As it was the last time this happened. And needed TPdebrick so that it would charge up in that too low state. The last resort option would be get inside it or whatever other method needed to copy the data off of the internal storage (part seen as SD card) in the state it is in. And if the storage can somehow be wiped from there sell it for parts if it ends up not repairable.
It could also be a dodgy Usb connection/board on the TP several people including myself have had this problem.
Well if tpdebrick got it up and running before can you not repeat the process to enable you to charge the tablet. Then you'd be able to install the tpcharge app and go from there ...
Does the back of the TP get warm/hot after charging? On my TP the back area near the volume buttons gets warm after being plugged in for a few hours.
sstar said:
It could also be a dodgy Usb connection/board on the TP several people including myself have had this problem.
Click to expand...
Click to collapse
chris5s said:
Well if tpdebrick got it up and running before can you not repeat the process to enable you to charge the tablet. Then you'd be able to install the tpcharge app and go from there ...
Click to expand...
Click to collapse
HKSpeed said:
Does the back of the TP get warm/hot after charging? On my TP the back area near the volume buttons gets warm after being plugged in for a few hours.
Click to expand...
Click to collapse
When charging any old day while I am using it I have noticed that area get warm. Just like the cylinder of the charger getting warm almost hot. Neither of that is happening which leads me to believe there may be something more wrong than just the simple yet not so simple problem that TPdebrick fixes. I've ran TPdebrick on it several times now twice before posting the thread and twice after. In completed it's execution with "all done" message. The port itself appears to function otherwise TPdebrick would fail before completing due to a USB connection failure. At least it seems to me it would fail as a result of that. Is there a way any of the parts can be tested for failure to figure out what has failed? Again assuming that something has gone bad internally on the TP. It has been plugged in for now 48 hours only interrupted by running TPdebrick. Of which I could run it again and get the info from the log I previously posted to see how it has changed. I have no idea what the numbers mean other than the battery percent being reported as 0.
I forgot to mention previously that it was plugged in at the time the battery went to 0%. Something I had not expected to occur. The battery icon in CM9 indicated charging with the lighting bolt icon as I had seen the icon just before it auto shutdown. Something I didn't give much thought to as that had happened one time a long time ago when I still had only webOS on it. Except webOS didn't let the battery get too low and it simply booted back up a minute or two after the charger was reconnected after it auto shutdown. So I guess if there is anything I can do to figure out why it isn't charging to know what needs to be fixed and if it is worth fixing and I'm able to fix it then I'd like to fix it. Otherwise I'll need a way to recover the data off of the storage so I can at least not have to start completely over with most of it. Nothing real important on it or anything that if lost would be detrimental just time lost in game progress and related and having to download oddball files for other apps again.
Just out of interest ... my touchpad that was not charging properly thru the usb port still managed to get thru the tpdebrick process to the "All Done" stage. However, it would only take a maximum of 100mA, even off the 2A mains charger. Changing the usb port resolved the chraging issue.
Peace
Edit: also, a touchstone - wireless - charger will eliminate a battery vs USB port fault ...
I have good news and bad news. The good news I'm able to charge my TP with a charger other than the official one. I tried my smartphone charger which is significantly lower amps. In 9 hours it has charged it 30% while it remained in the powered off state. I booted it up a few minutes ago hoping that it had charged it up. I powered it off again and will charge it to 100% before using it.
The bad news is the official chargers cylinder is shot. This is the second official one I have gone through since purchasing my TP during the fire sale. So I'm not sure what I'll do about that. I only really use it as an ebook reader right now and as an alternative to some things I use my smartphone for when I have both available to me. Considering my netbook is in need of replacing due to a failing charging port I am looking to get a windows 8 pro hybrid tablet (ex acer w700) which would effective replace both the netbook and TP. Leaving the TP as a much more of an experimentation device.
mine does not charge in android OS after installing CM 4.1.2 over old cherry kang
im getting current500mA in touchpad chargetest if connected to PC back 2.0 port, charge icon does not appear
charges if on webOS
Having the same issue as serialteg described. Just flashed to 10.2 (09/20 NIGHTLY) and TP cannot charge on CM. Switching back to WebOS, it's being charged.
Fixed. The infamous MTP issue was what I had. Solution found.

[Q] Not Quite Dead TP...maybe

Should I go ahead with the TPDebrick voo4 to try and revive my TP?
Apologies to those who know what to do and it is written somewhere. I have either missed it, or did not recognize it. Anyway, old subject, but after reading several threads, procedures, and processes, I guess I just wanted to make sure that I am finished with the "normal and easy" checks before I proceed with the TPDebrick v004 or whether I can based on the info below. My TP shows no signs of life except the menu light button going back and forth when plugged in. Here is what I know and have done to my TP is as follows:
1. When plugging in the usb port to either a less than 2.0a or 2.0a power source, including a pc, the menu button will light up and go left to right.
2. There has been no visual screen activity.
3. I have left it trickle charge over night (8+ hours).
4. I now have it on the 2.0a power charge (but no indication that it is charging other than the menu light)
5. I have tried the numerous button pressings (10, 15, 30 seconds and or more times), and combinations (menu, power, vol all at once or combinations of the two while holding and or pressing multiple times).
6. The battery has been changed to a new one (before all the charging noted above).
7. Two times when I plugged it into a win7 64 pc and pressed the menu, pwr and vol button, the pc recognized it, but could not find a driver. I could not find a driver or did not know what it was called. It has not been recognized since and there was no indication on the tp screen that it was in usb mode.
8. I do not know if the os is original or has been modified.
9. I do not have the touchbase charger.
10. I have tried different chargers and cables to no avail.
11. I do not have a win xp or 32bit system.
12. It has been sitting dormant probably 6 months, so I'm sure the battery was dead but again, I have had it plugged into various power sources for almost 24 hours.
13. I did read where someone said they found a reset button on the inside. There seemed to be some conflicting writings on that subject so I have not taken it apart to try method.
14. Perhaps the tp is so outdated that it is not worth the hassle, but I don't mind trying it...if the instructions are very detailed for this newbie. Besides, I have a couple of grandkids that might enjoy playing with it if I can get it going.
Thanks in advance to anyone who can advise my next steps.
Update: I went ahead and ran the tp debrick-v004 and received the "All Done" statement. I also noticed the battery was showing 0 and 0% in the statement. I have had it plugged in for about a day now, but no status change on the tp, meaning other than the menu button flashing back and forth, I have seen no screen life whatsoever. Any ideas?
golfnut22 said:
Should I go ahead with the TPDebrick voo4 to try and revive my TP?
Apologies to those who know what to do and it is written somewhere. I have either missed it, or did not recognize it. Anyway, old subject, but after reading several threads, procedures, and processes, I guess I just wanted to make sure that I am finished with the "normal and easy" checks before I proceed with the TPDebrick v004 or whether I can based on the info below. My TP shows no signs of life except the menu light button going back and forth when plugged in. Here is what I know and have done to my TP is as follows:
1. When plugging in the usb port to either a less than 2.0a or 2.0a power source, including a pc, the menu button will light up and go left to right.
2. There has been no visual screen activity.
3. I have left it trickle charge over night (8+ hours).
4. I now have it on the 2.0a power charge (but no indication that it is charging other than the menu light)
5. I have tried the numerous button pressings (10, 15, 30 seconds and or more times), and combinations (menu, power, vol all at once or combinations of the two while holding and or pressing multiple times).
6. The battery has been changed to a new one (before all the charging noted above).
7. Two times when I plugged it into a win7 64 pc and pressed the menu, pwr and vol button, the pc recognized it, but could not find a driver. I could not find a driver or did not know what it was called. It has not been recognized since and there was no indication on the tp screen that it was in usb mode.
8. I do not know if the os is original or has been modified.
9. I do not have the touchbase charger.
10. I have tried different chargers and cables to no avail.
11. I do not have a win xp or 32bit system.
12. It has been sitting dormant probably 6 months, so I'm sure the battery was dead but again, I have had it plugged into various power sources for almost 24 hours.
13. I did read where someone said they found a reset button on the inside. There seemed to be some conflicting writings on that subject so I have not taken it apart to try method.
14. Perhaps the tp is so outdated that it is not worth the hassle, but I don't mind trying it...if the instructions are very detailed for this newbie. Besides, I have a couple of grandkids that might enjoy playing with it if I can get it going.
Thanks in advance to anyone who can advise my next steps.
Update: I went ahead and ran the tp debrick-v004 and received the "All Done" statement. I also noticed the battery was showing 0 and 0% in the statement. I have had it plugged in for about a day now, but no status change on the tp, meaning other than the menu button flashing back and forth, I have seen no screen life whatsoever. Any ideas?
Click to expand...
Click to collapse
Update: Still no change after another 24 hrs of charging. I think I have one of those that is bricked. I still get the menu lights and still get either the "Palm" or "Qhsusb_dload" in win 7 device manager but with the yellow ! (I have not been able to find drivers....even if they are needed). I'll let it charge another couple of days to see if anything new happens. I did run the debrick-v004 again if nothing else to see if the battery positions had changed...and they did not.
HP TOUCHPAD DEBRICK Linux Live CD
I have created an Ubuntu Live CD with all the necessary files to Debrick the Tablet from TP Debrick v005 by jcsullins.
If there is any Tablet that did not finished the flash process, run this Live CD and perform the Debrick again.
If you do not know the Tablet model do the following:
Flash using the 16 GB, then connect to charger. If the home LED does not come on after some time then.
Flash using the 32 GB, then connect to charger. If no LED light then
Flash using the 64 GB.
All process must finish in " ALL DONE "
Click HERE for the HP TOUCHPAD DEBRICK LIVE CD
For information about charging a Tablet after been store for 9 years go here:
https://forums.webosnation.com/hp-touchpad/332615-hp-touchpad-won-t-turn-brand-new-never-opened.html

Categories

Resources