Touchpad Toolbox Mount Media Volume FAILED - TouchPad Q&A, Help & Troubleshooting

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

Related

USB Mount Problem after fully rooted.

I fully rooted my NC and installed a number of apps that work but now my NC wount mount to my computer as separate flash drives. How can i fix this problem? Did i do something wrong? Ill appreciate the help.
Funny, I just realized this happened on my NookColor as well - just got to the bottom of it though.
Somehow, my Windows box was recognizing the Android Composite ADB device twice, and this was somehow nuking the usb-storage mode. The fix was simple:
Make sure adb shell isn't running
Go into device manager, and uninstall both instances of "Android Composite ADB Interface" - I deleted the device drivers to be sure (Windows 7 option)
Unplug NookColor from USB
Plug it back in after a few seconds. Let Device manager do its thing. For me, it fails and gives me the 'Drivers not installed' caution symbol next to the "Nook" entry in the Device manager.
Rightclick on the Nook entry in Device Manager, then select 'update drivers.' Point it back at the original USB drivers that you used while rooting when prompted.
Wait for the system to do its thing, installing all the drivers - takes a good minute or so. Drives appear in your Explorer
(I had to unplug and replug before the computer would actually let me access CONTENT on the Nook and the SDcard - your experience may vary.)
Or you could just use adb to push/pull files.
You could - but I find it easier when my media directory (for instance) is just mounted as part of explorer.
Mine does the same thing. Tried your solution and it still don't work?
Plumbergeek -- I have found that sometimes the last installed APK (application) causes this fuss. Uninstall the last thing you added, reboot and try again. Sometimes I have to go back several applications to find the culprit. Once the offending APK is identified I then try to find an alternative application to install.
If you don't know how to uninstall applications, search the threads ... the answers are here. You can also install an application called Quick Uninstall. This app, though, usually will not delete/uninstall system applications.
Hope this helps!
indeana said:
Plumbergeek -- I have found that sometimes the last installed APK (application) causes this fuss. Uninstall the last thing you added, reboot and try again. Sometimes I have to go back several applications to find the culprit. Once the offending APK is identified I then try to find an alternative application to install.
If you don't know how to uninstall applications, search the threads ... the answers are here. You can also install an application called Quick Uninstall. This app, though, usually will not delete/uninstall system applications.
Hope this helps!
Click to expand...
Click to collapse
Well, the last one was Auto Config Script so I'll just wipe it and start over.
I have the same problem and can't figure out how to fix this
Both drives are listed in Device manager as B&N Ebook USB Disk storage
but the won't mount in windows.
When connected to PC that wasn't use to root it driver installation will fail
and there is Unknow device listed in Device manager (Nook) and two B&N USB Drives
but they will not mount as well.
Did anyone found what causes this ?
Thanks
Never mind, got it,
you have to push the n button to get it in to USB mode.
lifeisfun said:
Never mind, got it,
you have to push the n button to get it in to USB mode.
Click to expand...
Click to collapse
That's strange... i've never heard of anyone having to do that before...
Anyone else need to do this to mount?
I've always had to unlock mine to get it to mount in Windows. I just thought that was normal... is it not?
Sent from my Nooted friend...
I was going crazy unable to mount the storage and this did it for me
I have no-lock installed so unlocking wasn't the problem for me.
This didn't help. I can't even find those in Device manager
I'm also stuck with this problem. I am on Linux and can see two drives listed as B&N Ebook Disk, with all the other properties "unknown". I can neither open the drives nor connect to them with adb. It says that there is no device connected when I try to connect with adb.
This problem only started after installing Honeycomb. I was able to connect to the device through USB just fine when I was on a normal-but-nooted os.
Drive letters appear in explorer, but still can't write to them
Hi, I have a variation on the problem... My ADB install is confirmed (via cmd line) and I have two new drive letters appear (I guess it's one for the nook's internal memory, the other for the micro SD card). However, when I try clicking on either letter, Windows pops up an error message saying "please insert card". If it helps, my device list ID's the nook as a "composite USB device", not as a "nook"... Any suggestions? Thanks in advance!
MityaCat said:
Hi, I have a variation on the problem... My ADB install is confirmed (via cmd line) and I have two new drive letters appear (I guess it's one for the nook's internal memory, the other for the micro SD card). However, when I try clicking on either letter, Windows pops up an error message saying "please insert card". If it helps, my device list ID's the nook as a "composite USB device", not as a "nook"... Any suggestions? Thanks in advance!
Click to expand...
Click to collapse
Same issue. This is killing me.

Stuck at "Press the Windows key" in recovery mode Windows

After installing the dual boot bios on my teclast air III (M5C5) I tried to install Windows. Unfortunately, just before completion the installation was cancelled because of the following error: "Windows could not update the computer's boot configuration. Installation cannot proceed."
If I start my tablet and choose Windows, I get the following Recovery page:
The boot configuration data file is missing some required information.
File:\BCD
Error code: 0x0c0000034
You'll need to use recovery tools, if you don't have them...
Press the WIndows key for UEFI Firmware Settings
Click to expand...
Click to collapse
Of course I've tried to press the Windows key, but nothing happens. I've tried all keys and several common combinations, but none of them did anything, except spamming Ctrl-Alt-Delete, which forced a shutdown.
I can enter the BIOS, but for some reason there's no option to select Boot from USB stick (only UEFI OS and Windows Boot Manager). The strange thing is that I've used this usb stick to install Windows on the tablet in the first place and I've tried both GPT and MBR and used a usb 2.0 stick in a 2.0 hub, so the usb stick shouldn't be the problem I guess.
But probably even worse is that I cannot get into DNX mode anymore, so I can't install Android either. If I try I get the following message (instead of " Waiting for fastboot commands" ):
BOM Selection Switch (SW1B1) has been changed, but cannot take action. system will reset in 3 seconds
Click to expand...
Click to collapse
For some reason there is not much information about this error message and I could not find solutions to a similar problem ("BOM selection switch SW1B1 has changed Force_Windows"). In a desperate attempt I've tried to enable fastboot in BIOS to see if that would make a difference, but it doesn't.
Any help is welcome, thanks in advance!
Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.
Mikha777 said:
Are U sure you have flashed/installed the right BIOS/Firmware ? double check it !
Also if your USB drive is USB3.0 your hub must be 3.0 too OR you must connect the USB drive directly to the OTG cable.
Click to expand...
Click to collapse
It was a 2.0 drive in a 2.0 hub. But I've tried with a usb 3.0 stick in a 3.0 hub as well and that doesn't work either.
I've had some problems flashing the BIOS. Initially I tried the simple method using the UpdateIFWI app (using the Mirek V7 rom and downloaded the UpdateIFWI app seperately) with the bios "Dualboot Bios Tested C6J6 And C8J7" from here, but that didn't work. Then I used the Mirek's flash tool to update the BIOS and unfortunately selected the latest version, which apparently is not compatible. Luckily DNX mode worked and I could use the tool in this thread to flash the correct BIOS. I used the dualboot bios from techtablets. It finished with FPT operation passed, but did not automatically reboot. After manually rebooting, it launched the screen with the options Android and a small Windows logo. I selected Windows and it started the Windows installer from the USB stick and the rest I've described above. If I start my tablet now, the Android and Windows logo are equally large (so it did install a part of Windows?). Unfortunately I haven't checked if DNX mode worked between flashing Dual boot and installing Windows.
I've ordered an USB programmer already

Unable to mount Touchpad USB to PC after installing Android 4.4.4

I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.
Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...

Can't put Touchpad in USB Mode

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 **

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/

Categories

Resources