Database Develop

[Q] HP Touchpad not recognized by Windows

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]

Touchpad Toolbox Mount Media Volume FAILED

I downloaded touchpad toolbox (TPToolbox v40) and the associated required files to update a WebOS-only (stock) touchpad to Android:
http://forum.xda-developers.com/showpost.php?p=52765126&postcount=2
I did these steps after I had the files ready:
1. Booted into WebOS recovery mode (worked)
2. Ran the TPToolbox script (tptb_v40_win.bat, worked)
3. Selected "Complete Data Reset" from the TPToolbox menu (worked)
4. Selected "Install Android" from the TPToolbox menu (failed)
The first step of "Install Android" attempts to mount the media volume. The TPToolbox description says that a new media volume should show up on my PC with a folder called 'ttinstall' in it. My PC never recognizes any new media volume, so I can't copy files or continue the installation. I need help in figuring out why the media volume isn't being mounted.
If I reboot into WebOS recovery mode, the PC will recognize the device and I can re-download TPToolbox to the device again. The fact that I'm able to do this confirms that the PC and USB cable are working properly.
I didn't see any other threads where this issue was discussed. Any clues about what could be happening here? Right now I'm left with a touchpad with no webos and no android.

What OS is running on the PC?
Sent from my TouchPad using Tapatalk

jcsullins said:
What OS is running on the PC?
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
The PC is running Windows 7, 64-bit.

Same problem
I have the same issue, my PC is running Vista SP2, 32-bit.

For more debug information (if it helps):
- I was able to reflash the A6 firmware successfully (just testing if other functionality was working).
- I believe it was updated with WebOS doctor 3.05.
- I have tried rebooting and shutting down the touchpad and the problem persists.
- I have also rebooted my PC and the problem persists.
- As mentioned previously, the touchpad will get mounted when I originally connect it in WebOS recovery mode. Once I run the TPToolbox .bat script, the touchpad mount automatically goes away and touchpad toolbox starts running. At this point I'm unable to get it to mount again until I restart the touchpad in WebOS recovery mode.

I tried going back to using the ACMEInstaller method, and since I did the complete data reset, some of the dependencies of ACMEInstaller3 fail:
...
Shrinking media partition size ...
/etc/init.d/S90partition: line 63: /webos/usr/sbin/fsck.vfat: not found
/etc/init.d/S90partition: line 70: /webos/bin/resizefat: not found
resizefat failed! Aborting! Please reboot
Looks like I'm locked into using the Touchpad Toolbox method to install now, or do I have any other options?

swackerl said:
I tried going back to using the ACMEInstaller method, and since I did the complete data reset, some of the dependencies of ACMEInstaller3 fail:
...
Shrinking media partition size ...
/etc/init.d/S90partition: line 63: /webos/usr/sbin/fsck.vfat: not found
/etc/init.d/S90partition: line 70: /webos/bin/resizefat: not found
resizefat failed! Aborting! Please reboot
Looks like I'm locked into using the Touchpad Toolbox method to install now, or do I have any other options?
Click to expand...
Click to collapse
FYI, same error using ACMEInstaller5.

swackerl said:
For more debug information (if it helps):
- I was able to reflash the A6 firmware successfully (just testing if other functionality was working).
- I believe it was updated with WebOS doctor 3.05.
- I have tried rebooting and shutting down the touchpad and the problem persists.
- I have also rebooted my PC and the problem persists.
- As mentioned previously, the touchpad will get mounted when I originally connect it in WebOS recovery mode. Once I run the TPToolbox .bat script, the touchpad mount automatically goes away and touchpad toolbox starts running. At this point I'm unable to get it to mount again until I restart the touchpad in WebOS recovery mode.
Click to expand...
Click to collapse
Hmm, strange, you get a shared-drive when you put it in webOS recovery mode? What files/dirs do you see on the drive?
When you get to the point (either via "Mount Media Volume" from main menu or via install process) that it gives the "Mount Media Volume"
menu (with the "Unmount Media Volume" menu e entry.... wait for a min or so to see if you get a shared drive. If not, disconnect the USB cable
for 5-10 seconds and reconnect. Wait a min or so to see if you get a shared drive...
If you don't get a shared drive in either case, does the PC make any indication that it sees a different USB device (failed or otherwise)?
---------- Post added at 11:25 AM ---------- Previous post was at 11:15 AM ----------
swackerl said:
I tried going back to using the ACMEInstaller method, and since I did the complete data reset, some of the dependencies of ACMEInstaller3 fail:
...
Shrinking media partition size ...
/etc/init.d/S90partition: line 63: /webos/usr/sbin/fsck.vfat: not found
/etc/init.d/S90partition: line 70: /webos/bin/resizefat: not found
resizefat failed! Aborting! Please reboot
Looks like I'm locked into using the Touchpad Toolbox method to install now, or do I have any other options?
Click to expand...
Click to collapse
No, not really. Other tools depend on webOS files to work.
Don't get discouraged by that, however.
If we can't get your PC to connect properly via the "Media Mount" I do have other tricks we can use if we have to do so.

jcsullins said:
Hmm, strange, you get a shared-drive when you put it in webOS recovery mode? What files/dirs do you see on the drive?
When you get to the point (either via "Mount Media Volume" from main menu or via install process) that it gives the "Mount Media Volume"
menu (with the "Unmount Media Volume" menu e entry.... wait for a min or so to see if you get a shared drive. If not, disconnect the USB cable
for 5-10 seconds and reconnect. Wait a min or so to see if you get a shared drive...
If you don't get a shared drive in either case, does the PC make any indication that it sees a different USB device (failed or otherwise)?
Click to expand...
Click to collapse
I tried again and waited several minutes, but no mount showed up. Then I unplugged the USB for 15 seconds, then reconnected and waited 10 minutes and no mount showed up. By comparison when I reboot into WebOS recovery mode, the USB connection is acknowledged within 1-2 seconds.
When I previously said
the touchpad will get mounted when I originally connect it in WebOS recovery mode
Click to expand...
Click to collapse
, I used the wrong term. Instead of using the term "mounted" I should have said that the USB connection is acknowledged and the device is acknowledged by Windows 7 (how it plays a notification sound and pops up a notification that says a device has connected via USB).
After I start Touchpad Toolbox, another notification occurs in Windows 7 to indicate that the device is no longer connected via USB. The USB connection is good, because it's what's sending the signal to the touchpad to start Touchpad Toolbox. Should the disconnect be happening? After this point, Windows 7 never gets another notification that says the USB connection has been re-established.

swackerl said:
I tried again and waited several minutes, but no mount showed up. Then I unplugged the USB for 15 seconds, then reconnected and waited 10 minutes and no mount showed up. By comparison when I reboot into WebOS recovery mode, the USB connection is acknowledged within 1-2 seconds.
When I previously said , I used the wrong term. Instead of using the term "mounted" I should have said that the USB connection is acknowledged and the device is acknowledged by Windows 7 (how it plays a notification sound and pops up a notification that says a device has connected via USB).
After I start Touchpad Toolbox, another notification occurs in Windows 7 to indicate that the device is no longer connected via USB. The USB connection is good, because it's what's sending the signal to the touchpad to start Touchpad Toolbox. Should the disconnect be happening? After this point, Windows 7 never gets another notification that says the USB connection has been re-established.
Click to expand...
Click to collapse
Yes, it should disconnect when TPToolbox starts ... then reconnect as a different type USB endpoint.
And do another disconnect/reconnect when it's supposed to give the "Mount Media".
Hopefully, the TPToolbox kernel log will provide some useful information. Here's how to get that.
1) Load TPToolbox as before and select "Mount Media"
2) Wait a minute, then select "Umount Media"
3) Select "Reboot" and start holding the VolumeUP button and hold it until you see the big USB symbol (i.e. webOS recovery)
NOTE: It's important that you go straight to the USB symbol in this way (i.e. not select webOS recovery from moboot)
If it doesn't go straight to webOS recovery (i.e. you get moboot menu or it boots to something else), you will go back to step 1.
4) Download http://goo.im/devs/jcsullins/cmtouchpad/tptoolbox/palmenv.bat
NOTE: Don't include the quotes ("") surrounding the commands to be run below.
5) Open a "Command Prompt" and then run "cd Downloads" (I.e. I'm assuming you saved palmenv.bat to Downloads above)
6) Run "palmenv"
7) Now run "novacom -t open tty:// > klog.txt"
8) At this point, it should appear that that command is still running (no new command prompt appears)
9) Now type "klog last" (w/o the quotes, enter afterwards)
10) Then wait 30 seconds and the type "poweroff" (w/o the quotes, enter afterwards)
Here's what it looked like in my command-prompt window:
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\jc>cd Downloads
C:\Users\jc\Downloads>palmenv
Setting Novacom path ...
C:\Users\jc\Downloads>novacom -t open tty:// > klog.txt
klog last
poweroff
Sat Jun 07 17:21:35 2014
novacomd socket was closed prematurely
novacom: unexpected EOF from server
C:\Users\jc\Downloads>
You should now have a file called klog.txt in your Downloads dir (or where you ran the above commands).
Upload that file somewhere and provide link here.

Klog link
I did this, see if the klog helps.
the url is dropbox.com forward slash then s/8cd53d3rthbtcvc/klog.txt

jcsullins said:
Yes, it should disconnect when TPToolbox starts ... then reconnect as a different type USB endpoint.
And do another disconnect/reconnect when it's supposed to give the "Mount Media".
Hopefully, the TPToolbox kernel log will provide some useful information. Here's how to get that.
1) Load TPToolbox as before and select "Mount Media"
2) Wait a minute, then select "Umount Media"
3) Select "Reboot" and start holding the VolumeUP button and hold it until you see the big USB symbol (i.e. webOS recovery)
NOTE: It's important that you go straight to the USB symbol in this way (i.e. not select webOS recovery from moboot)
If it doesn't go straight to webOS recovery (i.e. you get moboot menu or it boots to something else), you will go back to step 1.
4) Download http://goo.im/devs/jcsullins/cmtouchpad/tptoolbox/palmenv.bat
NOTE: Don't include the quotes ("") surrounding the commands to be run below.
5) Open a "Command Prompt" and then run "cd Downloads" (I.e. I'm assuming you saved palmenv.bat to Downloads above)
6) Run "palmenv"
7) Now run "novacom -t open tty:// > klog.txt"
8) At this point, it should appear that that command is still running (no new command prompt appears)
9) Now type "klog last" (w/o the quotes, enter afterwards)
10) Then wait 30 seconds and the type "poweroff" (w/o the quotes, enter afterwards)
...
You should now have a file called klog.txt in your Downloads dir (or where you ran the above commands).
Upload that file somewhere and provide link here.
Click to expand...
Click to collapse
I uploaded the klog.txt file as an attachment to this post. Please let me know if you're unable to read it. Thanks for all the help!

Michigan3002 said:
I did this, see if the klog helps.
the url is dropbox.com forward slash then s/8cd53d3rthbtcvc/klog.txt
Click to expand...
Click to collapse
Based on that log, I think the problem is the USB cable you are using.
It thinks you are using a USB OTG (On-The-Go) cable. They are used when you want to connect a "client" device (i.e. keyboard, mouse, USB drive, etc.) to the Touchpad (on the Touchpad you also need a "Y" cable or powered hub too, but that doesn't matter here).
So why does it work loading TPToolbox via the bootloader, you ask? I think the bootloader is too "dumb" and doesn't know about the special pin that OTG cables have that enables the "host" mode. So, in effect, it just gets ignored by the bootloader and stays in "client" mode. The kernel used by TPToolbox has much more functionality, though, and sees that extra pin that OTG cables have.
---------- Post added at 11:56 PM ---------- Previous post was at 11:47 PM ----------
swackerl said:
I uploaded the klog.txt file as an attachment to this post. Please let me know if you're unable to read it. Thanks for all the help!
Click to expand...
Click to collapse
Based on your log, you have the same issue as above -- it thinks you have a USB OTG cable instead of a normal USB cable.

jcsullins said:
Based on that log, I think the problem is the USB cable you are using.
It thinks you are using a USB OTG (On-The-Go) cable. They are used when you want to connect a "client" device (i.e. keyboard, mouse, USB drive, etc.) to the Touchpad (on the Touchpad you also need a "Y" cable or powered hub too, but that doesn't matter here).
So why does it work loading TPToolbox via the bootloader, you ask? I think the bootloader is too "dumb" and doesn't know about the special pin that OTG cables have that enables the "host" mode. So, in effect, it just gets ignored by the bootloader and stays in "client" mode. The kernel used by TPToolbox has much more functionality, though, and sees that extra pin that OTG cables have.
---------- Post added at 11:56 PM ---------- Previous post was at 11:47 PM ----------
Based on your log, you have the same issue as above -- it thinks you have a USB OTG cable instead of a normal USB cable.
Click to expand...
Click to collapse
Excellent, I didn't notice it but after you said that I looked at the USB cable and it was one from LG, rather than HP. Luckily I had another HP Touchpad with the OEM USB cable. I swapped out the LG USB cable with the HP OEM USB cable and it worked as expected. Thanks jcsullins!

Touchpad toolbox no recovery file found, aborting
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...

coleraine said:
I am new to this,I am running Touchpad toolbox,and did a complete reset then Install Android the touchpad folder opens on the PC i then copied over the following 3 .zip files
recovery-clockwork-6.0.4.7-tenderloin.zip
gapps-kk-20140105.zip
cm-11-20140609-UNOFFICIAL-tenderloin.zip
then eject touchpad from pc and unmount.
I just keep getting the error NO RECOVERY FILE FOUND, ABORTING
Could someone help please,I don't know what to do.
Thanks...
Click to expand...
Click to collapse
I don't think that the file "recovery-clockwork-6.0.4.7-tenderloin.zip" is a supported recovery file. You can see the list of supported recovery files (CWM, Philz-CWM, TWRP) at the Touchpad Toolbox thread:
http://forum.xda-developers.com/showthread.php?t=2756314

jcsullins said:
Based on that log, I think the problem is the USB cable you are using.
Click to expand...
Click to collapse
Sure enough, I swapped USB cables and it worked like a charm. Thanks so much!

media volume mounts, able to copy to ttinstall, but also cannot continue
swackerl said:
I downloaded touchpad toolbox (TPToolbox v40) and the associated required files to update a WebOS-only (stock) touchpad to Android:
http://forum.xda-developers.com/showpost.php?p=52765126&postcount=2
I did these steps after I had the files ready:
1. Booted into WebOS recovery mode (worked)
2. Ran the TPToolbox script (tptb_v40_win.bat, worked)
3. Selected "Complete Data Reset" from the TPToolbox menu (worked)
4. Selected "Install Android" from the TPToolbox menu (failed)
The first step of "Install Android" attempts to mount the media volume. The TPToolbox description says that a new media volume should show up on my PC with a folder called 'ttinstall' in it. My PC never recognizes any new media volume, so I can't copy files or continue the installation. I need help in figuring out why the media volume isn't being mounted.
If I reboot into WebOS recovery mode, the PC will recognize the device and I can re-download TPToolbox to the device again. The fact that I'm able to do this confirms that the PC and USB cable are working properly.
I didn't see any other threads where this issue was discussed. Any clues about what could be happening here? Right now I'm left with a touchpad with no webos and no android.
Click to expand...
Click to collapse
I always see the "HP Touchpad" device mount as drive letter under Windows 7 64-bit (using Universal Novacom driver)
and am able to copy files, so I am a step ahead, but cannot continue
THIS WAS A BAD USB CABLE FOR ME ALSO - It appears to work fine for TPToolbox load,
but that is deceptive, the zip files copied are never valid!! Once I switch to new mini-usb it was fine....
http://forum.xda-developers.com/showthread.php?t=2777744
SOLVED BY ABOVE THREAD http://forum.xda-developers.com/showthread.php?t=2774779&page=2
which was excellent effort in the debugging process ...Where do these other cables come from?
http://forum.xda-developers.com/showthread.php?t=2774779&page=2

Tptoolbox not loading
swackerl said:
I uploaded the klog.txt file as an attachment to this post. Please let me know if you're unable to read it. Thanks for all the help!
Click to expand...
Click to collapse
My problem is I can load tptoolbox. I've tried multiple times. Windows 7 64bit HP All-in-One Touchpad. Help! I also loaded novacom which appears in the Palm Folder, but pc doesn't recognize touchpad when plugged in to USB.

no supported recovery file found
Hi,
I followed the below link to install the new android version and after the data has been erased I got a message on my Touch pad as "no supported recovery file found". I'm attaching the klog file. Could someone help me here?
liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html?preview=true

[Q] TP Toolbox, Cant connect TP to any PC

Wondering if im screwed or if someone can help me, I think the USB port on my Touchpad is gone.
I have been trying to use TP Toolbox but it always fails when finding device.
I have tried 4 different computers (3 Win 7 and 1 Win XP) to recognize the Touchpad as being connected via USB.
Its note a Novacom issue, when I connect the touchpad to the computer I get NO confirmation from Windows that a device is connected, no chime, no listing in the device manager, nothing, years ago I remember that even with no Novacom installed I at least got a notice saying a Palm, Inc device had been connected.
The Touchpad thinks its connected to a charger.
Under Android 4.2, only charging, going to USB connection option and selecting MTP doesnt do anything.
Under Web OS, get a notice that the charger is low capacity, but no option no mount device as USB drive.
Under TWRP when I go to Mount SD card, nothing happens.
The TP charges without any problem otherwise, using wall chargers or the wireless charger.
Any help would be appreciated, otherwise Im stuck on Android 4.2 forever

CYGNUZY said:
Wondering if im screwed or if someone can help me, I think the USB port on my Touchpad is gone.
I have been trying to use TP Toolbox but it always fails when finding device.
I have tried 4 different computers (3 Win 7 and 1 Win XP) to recognize the Touchpad as being connected via USB.
Its note a Novacom issue, when I connect the touchpad to the computer I get NO confirmation from Windows that a device is connected, no chime, no listing in the device manager, nothing, years ago I remember that even with no Novacom installed I at least got a notice saying a Palm, Inc device had been connected.
The Touchpad thinks its connected to a charger.
Under Android 4.2, only charging, going to USB connection option and selecting MTP doesnt do anything.
Under Web OS, get a notice that the charger is low capacity, but no option no mount device as USB drive.
Under TWRP when I go to Mount SD card, nothing happens.
The TP charges without any problem otherwise, using wall chargers or the wireless charger.
Any help would be appreciated, otherwise Im stuck on Android 4.2 forever
Click to expand...
Click to collapse
This should be in [email protected] thread. Not development.

CYGNUZY said:
Wondering if im screwed or if someone can help me, I think the USB port on my Touchpad is gone.
I have been trying to use TP Toolbox but it always fails when finding device.
I have tried 4 different computers (3 Win 7 and 1 Win XP) to recognize the Touchpad as being connected via USB.
Its note a Novacom issue, when I connect the touchpad to the computer I get NO confirmation from Windows that a device is connected, no chime, no listing in the device manager, nothing, years ago I remember that even with no Novacom installed I at least got a notice saying a Palm, Inc device had been connected.
The Touchpad thinks its connected to a charger.
Under Android 4.2, only charging, going to USB connection option and selecting MTP doesnt do anything.
Under Web OS, get a notice that the charger is low capacity, but no option no mount device as USB drive.
Under TWRP when I go to Mount SD card, nothing happens.
The TP charges without any problem otherwise, using wall chargers or the wireless charger.
Any help would be appreciated, otherwise Im stuck on Android 4.2 forever
Click to expand...
Click to collapse
Try a different cable. Make sure it's not an OTG one.

TPtoolbox Troubleshooting video
CYGNUZY said:
Wondering if im screwed or if someone can help me, I think the USB port on my Touchpad is gone.
I have been trying to use TP Toolbox but it always fails when finding device.
I have tried 4 different computers (3 Win 7 and 1 Win XP) to recognize the Touchpad as being connected via USB.
Its note a Novacom issue, when I connect the touchpad to the computer I get NO confirmation from Windows that a device is connected, no chime, no listing in the device manager, nothing, years ago I remember that even with no Novacom installed I at least got a notice saying a Palm, Inc device had been connected.
The Touchpad thinks its connected to a charger.
Under Android 4.2, only charging, going to USB connection option and selecting MTP doesnt do anything.
Under Web OS, get a notice that the charger is low capacity, but no option no mount device as USB drive.
Under TWRP when I go to Mount SD card, nothing happens.
The TP charges without any problem otherwise, using wall chargers or the wireless charger.
Any help would be appreciated, otherwise Im stuck on Android 4.2 forever
Click to expand...
Click to collapse
Video Timecode:
Intro: @ 0:00-0:50
TPtoolbox file confusion and version history v40 @ 0:51
TPtoolbox v41x post 293 @ XDA and recoveries for v41x @ 1:58
TPtoolbox not flashing corrupted files @ 3:44
TPtoolbox volume buttons don't navigate the menu @ 4:14
Alternate install guides for CM11/Android 4.4.x on the HP TP(4G) 5:41
Bricking and Bootloops help starts @ 6:41
Touchpad doesn't charge or turn on when plugged in @ 7:04
Always try using a different USB cable! @ 7:46
Jcsullins TPdebrick Last resort @ 8:00
Bootloop help and fixes @ 8:20
Can't activate WebOS after Jan,15, 2015 @ 9:42

Well for one, as someone said before, make sure you are using a proper USB cable, they aren't all the same, some cheap cables are designed to charge devices but won't work for connecting a device to a computer for data transfer. And also, you need to be in recovery mode for the toolbox to start. Turn the tablet off and then hold the Power + Vol UP until you see the USB symbol appear on the tablet. Connect it to your computer and open the batch file for the toolbox. If you have Novacom properly installed, it should recognize it right away and the toolbox will show up on the tablet.

Thank you to everyone for trying to help but nothing works, I have tried 3 cables so far:
1 that came with a Nexus 5.
The original Touchpad cable with the silver dimple.
A generic cable I have lying around.
Also tried 4 different computers, all same effect.
Does anyone have any other ideas? As I said in the opening post, Touchpad Recovery mode doesnt work, Android USB Mode doesnt work, Web OS USB and TWRP Mount mode the same.
No matter what I do, Windows wont detect that ANYTHING is connected to the USB port, no chime, no entry in the device manager, Novacom installed or not.

CYGNUZY said:
Thank you to everyone for trying to help but nothing works, I have tried 3 cables so far:
1 that came with a Nexus 5.
The original Touchpad cable with the silver dimple.
A generic cable I have lying around.
Also tried 4 different computers, all same effect.
Does anyone have any other ideas? As I said in the opening post, Touchpad Recovery mode doesnt work, Android USB Mode doesnt work, Web OS USB and TWRP Mount mode the same.
No matter what I do, Windows wont detect that ANYTHING is connected to the USB port, no chime, no entry in the device manager, Novacom installed or not.
Click to expand...
Click to collapse
Are you going to sell it?

bryantjopplin said:
Are you going to sell it?
Click to expand...
Click to collapse
Nope, just gonna keep it in this half broken build of Jelly Bean

CYGNUZY said:
Nope, just gonna keep it in this half broken build of Jelly Bean
Click to expand...
Click to collapse
Lol you might be able to replace the USB board inside.

CYGNUZY said:
Thank you to everyone for trying to help but nothing works, I have tried 3 cables so far:
1 that came with a Nexus 5.
The original Touchpad cable with the silver dimple.
A generic cable I have lying around.
Also tried 4 different computers, all same effect.
Does anyone have any other ideas? As I said in the opening post, Touchpad Recovery mode doesnt work, Android USB Mode doesnt work, Web OS USB and TWRP Mount mode the same.
No matter what I do, Windows wont detect that ANYTHING is connected to the USB port, no chime, no entry in the device manager, Novacom installed or not.
Click to expand...
Click to collapse
Have you tried the newer UniversalNovacomInstaller-1.4.1? I've just added into my thread recently. Just incase its a driver issue, sounds like your USB might be fried however:crying:
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:

RolandDeschain79 said:
Have you tried the newer UniversalNovacomInstaller-1.4.1? I've just added into my thread recently. Just incase its a driver issue, sounds like your USB might be fried however:crying:
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:
Click to expand...
Click to collapse
Thank you so much, I will give it a try as soon as I get home.
Also, is there anyway to upgrade Android on the TP without USB? I could transfer files using FTP or Wi Fi File explorer.

Possible but problematic
CYGNUZY said:
Thank you so much, I will give it a try as soon as I get home.
Also, is there anyway to upgrade Android on the TP without USB? I could transfer files using FTP or Wi Fi File explorer.
Click to expand...
Click to collapse
It might be possible to update your tablet without using the TPToolbox but you may have to manually change some partition sizes. I have an older guide for installing data media builds below that doesn't rely on the Toolbox. However I still recommend doing things like uninstalling android, which you can't do, so the procedure might be hit or miss. If you make a nandroid backup and transfer it to your PC you could attempt it. I've updated some of the links and you can find the newer recoveries at the bottom. Have a look and feel free to ask questions if you plan to attempt it, I'll try to update the info a bit.
[ROM GUIDE]How to install Android 4.4.x Data Media builds on the HP TP(Non-TPToolbox)

RolandDeschain79 said:
It might be possible to update your tablet without using the TPToolbox but you may have to manually change some partition sizes. I have an older guide for installing data media builds below that doesn't rely on the Toolbox. However I still recommend doing things like uninstalling android, which you can't do, so the procedure might be hit or miss. If you make a nandroid backup and transfer it to your PC you could attempt it. I've updated some of the links and you can find the newer recoveries at the bottom. Have a look and feel free to ask questions if you plan to attempt it, I'll try to update the info a bit.
[ROM GUIDE]How to install Android 4.4.x Data Media builds on the HP TP(Non-TPToolbox)
Click to expand...
Click to collapse
Thank you very much for updating the links for me, I really appreciate it, and will give it a try later! :good:

TouchPad Toolbox nor AcmeUninstaller2 working anymore

Hi there,
Looking to revive my touchpad after its been sitting on a drawer for a few years, but I'm having trouble getting anything to work on it.
TPTB executes and I see the USB icon change to the HP logo then some very quick text scrolls by faster than can be read (or filmed, I tried) and then the screen goes black and either it reboots or stays black waiting for power to be pressed. If it reboots it just goes back to the moboot 0.3.5 menu. This is what it shows on the Mac (also tried form a PC with same results)
$ /Users/Dennis/Desktop/tptoolbox_v42/tptb_v42_mac.command ; exit;
Checking novacom service ...
56135 e6efc17aff0b4e0a9b6754c5090fb0c4df565e67 usb topaz-bootie
Loading TPToolbox ...
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Click to expand...
Click to collapse
I tried removing android (to start from scratch) with ACMEUnistaller2
./novacom boot mem:// < ACMEUninstaller2
Click to expand...
Click to collapse
Same situation, from the USB Icon it goes to the HP logo, text scrolls by real quick and then either black screen or a reboot and Im back on the moboot 0.3.5 choose menu.
At this point neither boot webOS, CyanogenMod or ClockworkMod work, when I try CyanogenMod it gets to the green Loading screen then reboot back to the mooboot.
Any suggestions? Ive already tried:
- Different USB cables, including original USB cable that came with tablet.
- Fully charged over night after first shutting down from moboot menu
- both Mac and PC
- TPTB v42 and V41x
I would really appreciate some help, now that my daughter turned 3 I want to give her this as her own tablet.

Can't transfer files to my HP touchpad

I can't find a way to transfer the ROM files to my Touchpad to flash it.
I have TWRP on my touchpad already. I have the Novacom drivers on my PC.
I currently have a Dirty Unicorn ROM on my touchpad, which is fine, except the wifi has never worked, and and neither does the bluetooth. And now, when I connect my touchpad to my PC with a USB cable I can't get my PC to see the touchpad as an external drive. It will see the touchpad (and I have the option to eject it), but when I try to open it there is just a blank window with no files in and I can't copy anything to that. When I try on my touchpad to change the USB connection option all of the options are greyed out, so it is stuck with charging from USB.
I tried in TWRP using the "Mount as USB" option, but this doesn't do anything.
Is there another way to force files onto my touchpad? I seem to remember there used to be another program that would do something like that, but no idea what it was...
Oh, I'm running Windows 10 on my PC.
Let me know if you need any more information.

... one other thing!
I also have platform-tools installed on my pc.

One step at a time:
What type of USB cable is been use to connect Tablet to PC?
If is the original HP cable, then the issue may be the partition not set up properly.
It can be resolve by flashing Wipe_ALL, it will reformat everything, if not using WebOS.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
If the USB cable is not the original, then make sure it supports DATA transfer.
Not all USB charging cable support DATA.
To test connect another Android Device to PC, if DATA can be transfer then it should work on the HP_TP, if not then it can be the partition.

I have a similar problem.
I have put the Evervolv (this file ev_tenderloin-9-userbuild-2019.08.30.zip) on my TouchPad after it hasn't been used for many years. And now the TouchPad is stuck on the Evervolv logo.
Since I have deleted the previous ROM's zip file from the partition, I cannot flash the previous ROM with TWRP. I need a way to somehow put a ROM on the tablet.
When I connect the Touchpad to my Windows 7 PC, Windows does not recognize it, even when the tablet is in WebOS recovery with a USB symbol on the screen.
HELP!!!
I am hoping there a little thing I am not doing which will allow me to revive the old but dear device.

AlexeiHPTP said:
I have a similar problem.
I have put the Evervolv (this file ev_tenderloin-9-userbuild-2019.08.30.zip) on my TouchPad after it hasn't been used for many years. And now the TouchPad is stuck on the Evervolv logo.
Since I have deleted the previous ROM's zip file from the partition, I cannot flash the previous ROM with TWRP. I need a way to somehow put a ROM on the tablet.
When I connect the Touchpad to my Windows 7 PC, Windows does not recognize it, even when the tablet is in WebOS recovery with a USB symbol on the screen.
HELP!!!
I am hoping there a little thing I am not doing which will allow me to revive the old but dear device.
Click to expand...
Click to collapse
The Tablet does not need a ROM to transfer files, it is done by Recovery.
The WebOS Recovery mode is not for file transfer, is only use to load uImages onto memory, like the ToolBox.
Are you using the original USB cable?
The cable must provide Data, not all USB cables provide data.
The MiscroSD partition or USB must be mounted in Recovery TRWP, before conecting to PC for data transfer.
Take a look at this guide if need it to re-partition the Tablet or run the ToolBox.
https://forum.xda-developers.com/t/hp-touchpad-debrick-linux-live-cd.4189245/