i've seen numerous posts about this all over the place and couldn't find a fix anywhere
after providing logs to jcsullins he managed to solve my issue and now have a fully working TP again
heres the thread i created over at rootzwiki http://rootzwiki.com/topic/37804-battery-question-mark-issue/
and heres the link to the irc post for jcsullins to guide people through it
only created this here as i know a lot don't go on rootzwiki but many have this issue
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__310#entry1068329
hopefully this will help someone out and resurrect your thought to be dead TP
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Thanks
Thanks, it helped me a lot!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
I was able to fix my touchpad with this rootzwiki guide above. My touchpad had JB installed, after a battery drain it was completly dead. I was able to charge it by cutting down an old USB cable and charging the battery alone (touchpad had to be opened).
FYI (Tried ubuntu 12.04.2 in 2 different machines, the tpdebrick only worked on my alienware on the Dell with 1GB of ram it did not worked. The alienware has 2GB of RAM.)
The battery took almost 50% charge, then tried booting it up and nothing (only got question mark).
Theres a small button inside the unit in the charging module, I pressed it, and the unit turned off (it was the only way I could get it to shut down.
Did the debrick process, after that the touchpad would not charg via the USB port and only via the touchstone, so I did the ACMEUninstaller to remove android and it's good as new again. The problem for me was caused by the JB android installed. I had no problems when it had ICS.
Followed the instructions in the link from the first post. And it works!
Was skeptical as instructions seems very complex, but I thought I got nothing to lose. In summary, it was straight forward and you just need to:
1. Download Ubuntu 12.04 LTS and burn the iso to a CD/DVD.
2. Boot up your PC with the Ubuntu Installation CD.
3. Select Try Ubuntu rather than Install.
4. Follow the listed steps/instructions. PS: If you see a "space" for the terminal command, there is a "space" required when you key in the terminal command. And when the script is running, its working, even though you see nothing on the touchpad screen. When "All Done", the touchpad simply rebooted by itself, and ran through the usual boot-up sequence.
Good luck.
Its fixed!!!! Thanks!!!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
Thanks so much!!! I am so far from knowing how to fix a computer or tablet and my daughters HP touchpad did all of the things mentioned and I did the debrick and It is up and working. I was nervous to try this debrick thing since I have no clue how to do computer stuff but all the directions were clear and easy. Thanks!! I have a happy daughter
sudo ./tpdebrick command not found
hi dude, thank you for the post but i always got the message sudo ./tpdebrick command not found, could you help me?
note: the tpdebrick file is into the folder u.u
dfu-util and fastboot missing
[email protected]:~$ cd downloads
bash: cd: downloads: No such file or directory
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip tpdebrick-v004
Archive: tpdebrick-v004.zip
replace tpdebrick-v004/tp16.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: n
replace tpdebrick-v004/ebr16.bin? [y]es, [n]o, [A]ll, [N]one, [r]ename: N
[email protected]:~/Downloads$ cd tpdebrick-v004
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$
why is this coming up? i cant find any links to where i would find dfu-util or fastboot or where it needs to be.
What version of Ubuntu are you using? Is it 32 or 64 bit?
gtallmadge said:
What version of Ubuntu are you using? Is it 32 or 64 bit?
Click to expand...
Click to collapse
I used this particular file and made it into a bootable usb stick
releases.ubuntu.com/12.04/ubuntu-12.04.4-desktop-i386.iso
ubuntu.com/download/desktop/create-a-usb-stick-on-windows
It was a lot easier than I thought, just did the tpdebrick today :good::good:
fixed for the right links
Glad it worked for you. I knew the directions said to use Ubuntu 12.04 which is still available so it is good to know 14.04 which is
the current Long term release of Ubuntu works as well.
I'm sorry, but it was this one that I used
releases.ubuntu.com/12.04/
Thanks for the info..I obviously misread your post.
Questionmark of Death on TP
First problem I ran into, couldn't find a working link for the webos doctor, after an hour of searching, came across a link but xda won't let me post since I don't have 10 posts.
w w w . adbtoolkit.com /rooting/devices/hp/tenderloin/webOS-Doctor/wifi/#.VGYTS9YghCW
Next issue, when it told me to hold my power+vol down+home button down, it would time out with some error( I think it said qdl not found something like that). Tried a few times, then tried a samsung cable for my phone instead of the original touchpad cable, and that worked. Thanks to the guy at rootzwiki for the information.
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
ractar28 said:
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
Click to expand...
Click to collapse
It's not deleted. You have to log into rootzwiki from the error screen, and the link will load.
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Gamedays said:
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Click to expand...
Click to collapse
Do you happen to have the guide as well, or am I missing it somewhere? I was also unable to get the registration process to work... the step I am on specifically:
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
Thanks!
Related
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
bone625 said:
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
Click to expand...
Click to collapse
Take a look at this thread. I think it could have information that could maybe help you.
forum.xda-developers.com/showthread.php?t=1508572
Thanks, bah tried all that - the problem is mounting USB recovery, can't get into androidto test anything else. I'll have access to a few other computers this weekend so I"ll see if they can find it. Going to rewipe everything tonight as well, will update... pretty annoying.
I have an idea.
What you can try is to reboot into WebOS, mount the /media drive so you can copy files to it from Windows. On that media drive, there should still be a folder called cminstall. Copy the moboot install zip back into there, and then reboot the tablet into recovery (Power+VolUp). From there, run AcmeInstaller2 again, and you should be good to go - it'll run, and force an install of the contents of that /media/cminstall folder, which'll put Moboot back in place.
At least, that's what SHOULD happen. I'm no expert, but from what I've seen and played with, that should do what you're trying to achieve.
Thanks for trying.. Not exactly what it needed to be fixed though. I have everything ready to go in uninstall, the computer (any computer I've tried so far, and its been quite a few - that all used to read the touchpad in recovery mode) won't register it and mount it as a drive so I can run ACMEInstaller in the first place.
It must have changed something on the touchpad itself, because it used to mount fine before that happened... Now every computer installs it as palm novacom booties and never mounts the actual drive, and acmeinstaller just says no device or something like that. Bah, still can't figure it out, I miss android haha.
Did you enable MTP in the advanced menu under the Storage section?
Are you trying to get the device to show up in adb? If you are having troubles with that I found a really nice guide on another website on how to get adb to read the touchpad if nothing else is working. Not sure if I can post the link or not. Send me a pm if this is something you need.
Sent from my cm_tenderloin using xda premium
Problem is I can't boot into android cause the bootloader broke and I can't get it to boot android period, even with cyboot. I know all l I have to do is run ACME again... But I can't run it cause it won't mount haha. Stuck in webOS for now, and every computer I've tried won't boot recovery mode anymore. Drivers check out and register but can't change anything to recognize it as a drive. I think I'm going to try to manually uninstall everything android, then reinstall webOS and see if it mounts then. Blah!
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
Click to expand...
Click to collapse
This trick with webOS doctor just saved my ass. I couldn't boot past the green cyanogenmod splash screen and needed to boot straight off an image from moboot on my desktop, and taking webOS doctor to that step was the only thing that would let me run the command line entry to make it where my PC would talk to my touchpad. So, thank you
Would this work for a TP that reads both ways on PC as listed by OP but is only stock?
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
Click to expand...
Click to collapse
What do mean by run ACMEInstaller? I only know using the novacom boot mem:// <ACMEInstaller method, though that's getting stuck while on the two penguin screen.
Hp touchpad 32GB converted into Android 4.4.4.KitKat with ROM CM11
Hi My name is Ramadoss.N Recently I have converted my touch pad to Android KITKAT 4.4.4. with Rom CM11 -20140625- Snap Shot- jcsulline. I used TPtoolbox V41d to install. Everything working fine. except few observation.
1. Bottom Menu Button like Home , Return to previous screen are not working in vertical position of touchpad, where as it works in Horizontal position.
2. There are 3 dots on right hand side corner to provide dropdown menu: it works in vertical position, does not work in Horizontal position.
3. search icon ( which looks like a magnifying glass) does not work in both positions.
4.Back space key working in Vertical position, does not work in horizontal position.
5. Could not load Music via computer after installing Android in the Touchpad,
I really appreciate if any one can give me solution for above.
Regards
Ramadoss.N
email : [email protected]
Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970
Soulace1970 said:
Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970
Click to expand...
Click to collapse
If you've made it this far after running all of those Novaterm commands, you're in for a treat. Just turn off your HP Touchpad, run the WebOSDoctor 3.0.0 by double clicking it on your desktop (if you can't run it, you need to install java, see java.com) Once the dialog box tells you to connect your Touchpad, make sure to hold the up power button when you plug it in, this will boot you to the USB symbol, which is Webos Recovery. Click next button on the dialog box on your computer. It will do the rest. Make sure to charge the unit for awhile with it off if possible (hold home+power for 10-20 seconds after the HP symbol shows up to force it to turn off), as it's a good idea to have at least 30% battery when you do. I've done this process many times to reset my TP when I tried out Ubuntu.
Edit: By the way, you need to extract that zip file prior to running the .jar file (which is the WebOSDoctor program)
fixed
I got my brothers... tried everything... saw this...
http://rootzwiki.com/topic/38786-tpdebrick-v004/
downloaded ubuntu like it suggested... ran it as a live cd... downloaded the stuff... followed the directions (Spelling is CaSe sensitive in ubuntu) and holy crap... it worked!!!
HP TouchPad Battery Drain issues during sleep (Important):
New Video and methods for flashing the A6 Firmware with the TPtoolbox (Method 3)
https://www.youtube.com/watch?v=NnWH7FhaMg4
Full Guides for the TPtoolbox:
[ROM GUIDE] How to Install Android 8.1.x/7.1.2 builds on the HP TouchPad(XDA)
How to test:
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
1) Download and install the Novacom drivers below:
Download and run the Universal Novacom Installer 1.4.1 here:
Note: You will need to have Java installed to run the Universal installer, click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS here or here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
2)Place the tablet into WebOS recovery mode and run the TPtoolbox
3)Download, unzip and run the TPtoolbox
Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
-Note* after setting the calibration, users will have to allow several hours to pass before the history can be accumulated.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to Reflash the A6 Firmware Method 2:
https://www.youtube.com/watch?v=5lOGY94RRDs
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)On your PC Install Java, Novacom and the WebOSQuickInstall-4.5.0 software*
- Note* If you have already previously installed Android with Java and Novacom, then skip it.
a]Download Java:
c]Download WebOSQuickInstall-4.5.1:
3)Run the WebOSQuickInstall-4.5.1 software, note your TouchPad must be connected with the USB cable.
-Click on the Small globe icon located under the plus minus buttons.
-This will take us to a new menu where we will search “preware”
-Click the install button and the Preware app will be installed.
-You may now unplug the USB cable.
4)On the tablet while booted into WebOS navigate to downloads and select Preware.
-scroll down until you see a button appear to continue
-Search for “wterm” and install the app.
-Run wterm, and set a password to give the app Root permissions.
- You can set or change the password by looking for the wterm menu in the upper left corner and select setup.
-Click on New password and enter a simple password like ”0000”
-Confirm the password and press “Set Password” button, now hit done and exit.
-Note you can increase the font size by going to wterm preference settings.
5) Now in wterm enter one of the following commands:
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
PmA6Updater –a (Note this shorter command flashes two firmwares)
-It should take about 20-30 seconds to complete and will inform you upon completion.
-Congratulations you have now reflashed the A6 Firmware and can safely close the terminal and reboot your HP TouchPad.
Note: If you input the command and get a message saying it said can't open the A6 device, then try toggling developer mode off and on.
Additional WebOS Preware Performance Tweaks:
I would highly recommend doing the following tweaks. Read the full instructional guide in the link below:
HP TouchPad Setup Guide Part 1: Speed Up Your Tablet With Preware, Homebrew & Patches [WebOS]
Download and install the following packages from Preware:
You should see a noticeable speed improvement while using WebOS. Also a few apps to improve functionality.
Note* You will need to reboot the device after installing most of these packages:
-EOM Overlord Monitoring
-Muffle System Logging
-Remove Dropped Packet Logging
-Unset CFQ IQ Scheduler
-Unthrottle Download Manager
-Increase Touch Sensitivity and Smoothness 10
-Quiet Powerd Messages (sic)
-Faster Card Animations HYPER Version
-Advanced Rest Options
-Disk Cache Mod
-Unhide Developer Mode Icon
-Reduce Minimum Brightness
-CyBoot
-Ad Blocker OR Max Block – Do not install both.
-Private Browsing (adds an option to your browser)
Reduce Logging & Patch ‘em Up:
This patch require you to log into Skype with the "Phone and Video Calls" app.
Once there place a call to this number using the dialer type: "##5647#"
A logging window will launch, choose to "Clear Logs" first then "Change Logging Levels" and setting logging to "minimal".
Once done, exit the app – your logging levels are now changed.
If you have never used Preware you can watch this video about Flashing the HP Touchpads A6 Firmware.
You will also learn how to use the WebOSQuickInstall-4.5.0 software to install Preware.
Both of these procedures are highly recommended and can be done as part of your post apocalyptic WebOS Survival.
How to Reflash the A6 Firmware Method 3:
https://www.youtube.com/watch?v=3T2Apdc15uY
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)Install Java and the Novacom software*
- Note* If you have already previously installed Android with, Java and Novacom drivers, then proceed to step 3.
a]Download Java:
b]Install Novacom drivers for your OS:
Win32:
Win64:
Linux32:
Linux64:
Mac OSX:
3)Open windows explorer and go to C:\Program Files\Palm, Inc\Terminal
-Now run the Terminal.bat*
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
4)In the open Novaterm window, select file\connect\Ok
-Now copy and paste the following line into Novaterm and press enter*
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
-Note* Do Not! disconnect the TouchPad After starting this procedure.
-Novaterm will tell you "firmware update complete"
- In the open Novaterm window, select file\disconnect\Ok
-Congratulations you have now relfashed the A6 Firmware and can safely disconnect your HP TouchPad from the USB cable.
Note: Get the latest version of WebOS Doctor 3.0.5 Official here:
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
https://www.youtube.com/watch?v=L63RiBXhQCY
How and when to Use the WebOS Doctor(Important):
https://www.youtube.com/watch?v=wFAIJiS8g4o
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note: If run the WebOS doctor after March, 15 ,2015. then you will need to bypass the WebOS activation with the instructions here
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing up your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.5 Official Link
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode. Note the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Every month or so depending on usage
Juan685 said:
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Click to expand...
Click to collapse
The discussion over at Rootzwiki seems to indicate that it should be done every month or so depending on your usage. I turn my tablet off when I'm not using it actively so I can do it every couple months or so.
Use the battery monitor widget to check the sleep history. After you've run this procedure once it becomes very easy to repeat.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to test:
How to monitor your battery
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
theronkinator said:
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
Click to expand...
Click to collapse
i hope so too. especially if it is recommended to do this once a month =/
chicle_11 said:
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
Click to expand...
Click to collapse
Thank you for the heads up, I will have to make a note about it in my CM10.1 thread.:good:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
jacobas92 said:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
Click to expand...
Click to collapse
I should add a little note about that. The shorter command flashes two firmwares (as seen in the video) and therefore takes a little longer but less time to type in. Once you've typed it once in the terminal you can just hit page up to bring up again for future flashing.
Just wanna say thanks again, my battery life has increased by tenfold.
Sent from my cm_tenderloin using xda premium
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
henry333 said:
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
Click to expand...
Click to collapse
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
RolandDeschain79 said:
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
Click to expand...
Click to collapse
Yes, I was using method 1 and copied javaw.exe on both PC. I remember doing WebOSQuickInstall stuff when I first got the touchpad and try not to install WebOS stuff if I can avoid it.
Finally, I am seeing lots of -3 and some -4 from BMW when I was content with -19. From the early A6 thread, I though that I would have to re-setup everything for the touchpad.
Thank you very very much.
Would this wipe my sd ?
having issue.while input PmA6 updater -a, it said can't open A6 device??
Does this affect everyone? I haven't had a problem with battery life since JC fixed the deep sleep in cm10
Sent from my TouchPad using Tapatalk 2
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
More info needed
wqt0926 said:
having issue.while input PmA6 updater -a, it said can't open A6 device??
Click to expand...
Click to collapse
Which method are you using? Is WiFi connected? Did you remember to set a password for method 2? Help me, help you
Deteriorating battery health
apicia said:
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
Click to expand...
Click to collapse
Lets see your battery monitor widget history. There should be gapps from where you have the tablet turned off and on. This could also be a symptom of your battery health deteriorating. We were just talking about these sorts of problems today.
Nevertells has another battery health thread here:
unable to find wterm in Preware, used Method 1
Just to mention this, I used to have all kinds of stuff installed in WebOS when I first got my TouchPad and then it died on my and had to use the TPDebrick process in RootzWiki to bring it back to life... anyway, I know I used to have terminal installed but I also remember having to add feeds so that I could find the terminal package.
This time around, I had only gone through the WebOS wizard because I needed to connect via USB so I could add the cminstall folder to the SD so I could reinstall Android...
Long story short, when I went into the Preware app to search for "wterm" it was nowhere to be found in available or installed packages... so I used the Method 1 and it worked just as well, the whole process took no more than 5 minutes
So, if anyone knows what feed url has to be added to Preware to find wterm it may be helpful...
Thanks for all your work guys on keeping the TP alive
PS: the only reason I flashed the A6 firmware is because yesterday I finally made the leap from CM10 to 10.1... I even dirty flashed on top of the 0418 CM10 build and have had absolutely zero issues (I just hate the dang navigation bars in the center but I like the status bar on top because I can now use CoolTool again :good:
PPS: Just want to mention also, I have read in a couple of threads that Windows 7 x64 users haven't been able to get UMS drivers to use the TP in mass storage mode in case anyone has any suggestions for that as well...
Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?
anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp
Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.
shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5
mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse
shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.
issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
"
Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.
Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.
No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1
HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.
Hello,
Days ago I tried to uninstall from my Touchpad since I wanted a clean reboot to reuse the tablet. However I realized that the tablet wasn't turning on, and she wasn't able to get in USB Mode.... The thing is that to get a clean wipe I need to use ACMEUninstaller2, but it says that the device is not found, so I guess that It's the USB Mode that's breaking everything. I tried quite a few things but nothing works, the tablet just don't want to get in USB Mode.
By the way, when I connect with USB the Touchpad to the PC, the PC recognizes it, but tolds me that "The drivers of this devices aren't installed", which is strange since I installed all Novacom drivers I could find...
Also, I'm asking if you could help me with that, since I searched everywhere I haven't found anything on this.
The novacom driver is what communicates to the HP Touchpad and is use to load any boot uImage into memory.
( It does mount or allow the use of the USB drive ) The USB drive is a partition formatted in vfat that gets mounted by TWRP or any other Recovery and also Android.
To load any boot uImage into memory.
Boot Tablet and select ((( boot WebOS Recovery ))) from the moboot 0.3.8 menu
If there is no moboot 0.3.8 menu, then press power and volume key closes to the power key and the same time until the big white USB symbol comes up.
Plug the tablet into PC using USB.
On the PC unzip the Recovery file you will like to use.
Go to the extracted folder and open a terminal window or command prompt.
Type:
novacom boot mem:// <
after < ( place the name of the uImage file)
Example for TWRP will be
novacom boot mem:// <uImage.TWRP
If you want to load the ToolBox, then unzip TPToolbox-2015-01-08-v42.zip
rename the file TPToolbox-2015-01-08-v42.bin to uImage.TPToolbox
Open a terminal window in that directory and load it:
novacom boot mem:// <uImage.TPToolbox
Thank you for you answer !
I followed everything you said but my tablet isn't getting on USB Mode, I tried so many things but it don't wan't to.... When I do Power + Volume UP, I'm getting a charging icon, but when I try to charge the tablet, as I don't have any official charger, it tolds me I need to get one, but I don't really have 15 dollars to use in a charger, since I remember that I could charge the tablet without the official one when she was still working...
Patahuete said:
Thank you for you answer !
I followed everything you said but my tablet isn't getting on USB Mode, I tried so many things but it don't wan't to.... When I do Power + Volume UP, I'm getting a charging icon, but when I try to charge the tablet, as I don't have any official charger, it tolds me I need to get one, but I don't really have 15 dollars to use in a charger, since I remember that I could charge the tablet without the official one when she was still working...
Click to expand...
Click to collapse
To charge the HP Touchpad you need any charger that will meet this specifications:
Output: 5.3volts, 2.0amps
For all of you that think your tablet is Brick or not functional or having issues:
No electronic device known to man existence can work without been properly charge or connected using the proper power source.
Even for a car, if it does not have a full working battery it will not start no matter if you replace the engine.
It is a basic procedure to follow.
1. Check for proper charging.
2. Start trouble shooting.
Thank you for your answer.
I see. I searched and I'm still searching for that charger, but, just to know, if I connect the tablet to the USB ports of my computer, will it charge it even if there's a message telling me that I need the official charger ? Also, does USB 3.0 or 2.0 changes anything to the charging speed ?
Because I don't see any LED or sign of the tablet charging so I'm a little bit confused on how it works...
Patahuete said:
Thank you for your answer.
I see. I searched and I'm still searching for that charger, but, just to know, if I connect the tablet to the USB ports of my computer, will it charge it even if there's a message telling me that I need the official charger ? Also, does USB 3.0 or 2.0 changes anything to the charging speed ?
Because I don't see any LED or sign of the tablet charging so I'm a little bit confused on how it works...
Click to expand...
Click to collapse
The HP TOUCHPAD will ONLY CHARGE using a charger providing the following:
Output: 5.3volts, 2.0amps
It will not take enough charge to make it boot from no other source, NO USB connected to PC.
It will be the same as using a 9volt battery to start your car.
An inexpensive option:
https://www.ebay.com/itm/5V-2A-AC-Charger-Power-Adapter-Supply-for-HP-Touchpad-16GB-32GB-Tablet-PC-Tab/122752649546?hash=item1c94a0c94a:g:~ygAAOSw9-FZ3wWS
Ok ! I've got something ! So I managed to get the tablet charged, and so I used ACMEuninstaller2, the thing is that it told me something like "ERROR : unable to.... When the tablet will boot, it will fail to launch, and then use webos doctor !" So I did it and I'm struggling with a 8% error, wich tells me that webos doctor is unable to reset the phone... I tried wikipedia and every xda thread I could see and nothing works... I'm desesperate, It's really the kind of things that happens to me and just me....
Do you want to use WebOS or Android on the HP Touchpad Tablet?
** The information is to be use on a Tablet not a Phone **