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]

[Q] windows asks to format touchpad when connecting to a windows pc

hi,
whenever i connect my touchpad to my windows pc it asks me to format it
I did originally have cm9 install but run in to trouble and me being the noob i am didnt have a restore so i uninstalled cm9 using the acme uninstaller and everything was fine, I then proceeded to try and reinstall cm9 back onto the touchpad however it seemed to me that all the files i had put on my touchpad gets deleted.
i have doctored my touchpad twice and removed the cm9 stores using novaterm via the lvs method as for some reason when i uninstalled cm9 the cm-data, cm-system etc and resized the media partition but still when i connect the touchpad to the computer it still asks to format the drive.
I have searched the forum and the internet and still no joy :/ any ideas for a fix would be apperciated
Thanks

If you reset the partitions like in the recovery thread, then you should be set, but if not, try this:
Rebuild them completely, as per the thread in the General about Recovery and Downgrade. Then Doctor it with 3.0.0, then 3.0.5. Once that's done, boot into WebOS, and do a full erase and format - that should fix it. Theoretically.

thanks for your help ve6ay I followed the thread and it seemed to fix the problem thanks so much ics install time

Glad I was able to help, mate.

[Q] BRICKED?

[Guide] Factory condition restoration / Downgrade to webOS 3.0.0
Was running above guide all went well until the end.
started to enter recovery phase and run webos doctor and got the low battery message and now I can not connect with tablet from webos doctor, novacom or novaterm.
any ideas?

Charge the battery for a long while. It wont run the webOS doctor until the battery has a decent amount of power

I charged it overnight. get as far as the plug device in message, next button stays grayed out.
can get into twrp or cwm. twrp I can see the partions but none of them are populated.

reinstalled windows 7. used the 32bit disc. reinstalled nova term and it looked as though novaterm could see the tablet.
still need to figurre out why webos doctor 3.0.0 is behaving differently than webos doctor 3.0.5.
ok just downloaded here at work and 3.0.0. worked just the way it should and im running the latest java so maybe it has something to do with windows 7.

geomonroe said:
reinstalled windows 7. used the 32bit disc. reinstalled nova term and it looked as though novaterm could see the tablet.
still need to figurre out why webos doctor 3.0.0 is behaving differently than webos doctor 3.0.5.
ok just downloaded here at work and 3.0.0. worked just the way it should and im running the latest java so maybe it has something to do with windows 7.
Click to expand...
Click to collapse
I used windows 7 with no problem. You have to make sure you have a full charge. Depending on how much the battery has run down, you might have to charge it 24 hrs +.
On that guide, there's a good work around, if you're having trouble with novaterm. Page 12.

OK will get left charging over night, will get back to it tonight, thanks
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for your help.tablet is restored. Only hitch was, windows handling of file extensions. It kept turning the. Jar into zip.
Sent from my Galaxy Nexus using Tapatalk 2

geomonroe said:
Thanks for your help.tablet is restored. Only hitch was, windows handling of file extensions. It kept turning the. Jar into zip.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just use a different browser or as you already figured change the extension.

sstar said:
Just use a different browser or as you already figured change the extension.
Click to expand...
Click to collapse
Found out in Windows, unhide file extensions is possible, than just change them as needed
John 3:16

[Q] Help with Bricked HP 32 GB TP

Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970

Soulace1970 said:
Hi
Long story short - I bricked my 32GB HP Touchpad after running online WebOS Doctor 3.05 which worked and rebooted. But when I went to connect USB to see drive in Windows it wouldn't access it and wanted to format the SD CARD. So I said yes. A reboot later and it sat on HP logo.
So I did another online WebOS Doctor 3.05 and it stuck at 12% for ages. I disconnected the device and it then said ! www.palm.com/ROM screen.
I did a little research and came across http://forum.xda-developers.com/show...6#post20989526 and have followed the novaterm commands for 32 GB device.
But I am stuck at Step 9
9) Run webOS Doctor 3.0.0 (This is to ensure a repartitioning and no other version will work at this point )
I have downloaded webosdoctorp300hstnhwifi.zip from the Internals site but I am unsure how to start this from the command prompt.
Is it done from the Windows command prompt or the Novaterm command prompt? And what command do I issue to finish Step 9?
Addendum to the thread mentioned above: I'm running Windows 7 64 bit as the host PC...
Regards
Soulace1970
Click to expand...
Click to collapse
If you've made it this far after running all of those Novaterm commands, you're in for a treat. Just turn off your HP Touchpad, run the WebOSDoctor 3.0.0 by double clicking it on your desktop (if you can't run it, you need to install java, see java.com) Once the dialog box tells you to connect your Touchpad, make sure to hold the up power button when you plug it in, this will boot you to the USB symbol, which is Webos Recovery. Click next button on the dialog box on your computer. It will do the rest. Make sure to charge the unit for awhile with it off if possible (hold home+power for 10-20 seconds after the HP symbol shows up to force it to turn off), as it's a good idea to have at least 30% battery when you do. I've done this process many times to reset my TP when I tried out Ubuntu.
Edit: By the way, you need to extract that zip file prior to running the .jar file (which is the WebOSDoctor program)

fixed
I got my brothers... tried everything... saw this...
http://rootzwiki.com/topic/38786-tpdebrick-v004/
downloaded ubuntu like it suggested... ran it as a live cd... downloaded the stuff... followed the directions (Spelling is CaSe sensitive in ubuntu) and holy crap... it worked!!!

[Q] Accidently ran WebOS update and fubared everything

Any idea on how to fix this? A basic explanation would appreciated.
I came across this thread: http://forum.xda-developers.com/showthread.php?t=1564938
But I'm having some trouble following it

A little more info would be helpful....
Did you have android installed? Which version?
Webos update from within webos or using webos doctor, or...? What were you doing before the touchpad became fubar?
What do you mean by fubared? What can you / can't you do?
Does the device actually boot? If not, where does it hang?
Cheers

Sorry for the lack of detail.
chris5s said:
A little more info would be helpful....
Did you have android installed?
Click to expand...
Click to collapse
Yes I did, dual booted with WebOS.
chris5s said:
Which version?
Click to expand...
Click to collapse
I don't remember the exact one. I believe it was a CM9 nightly. It's not any of the new ones...and it was running one of the original recoveries as well.
chris5s said:
Webos update from within webos or using webos doctor, or...?
Click to expand...
Click to collapse
Within WebOS.
chris5s said:
What were you doing before the touchpad became fubar?
Click to expand...
Click to collapse
I booted into WebOS to check it out and it prompted me saying it needed to update. So I went ahead and let it do that.
chris5s said:
What do you mean by fubared?
Click to expand...
Click to collapse
It turns on to the HP logo, the logo acts like it's loading. Then it turns off, restarts, goes back to the HP logo, then continues this dance until the battery dies. When the battery dies the red battery picture shows up until it fully charges again.
chris5s said:
What can you / can't you do?
Click to expand...
Click to collapse
I can't get into the recovery, and I can't get into Android or WebOS. I can force restart it.
chris5s said:
Does the device actually boot? If not, where does it hang?
Click to expand...
Click to collapse
It hangs at the HP logo.
chris5s said:
Cheers
Click to expand...
Click to collapse
Thanks for any help!

I'm wondering, did webos perform a system upgrade, i.e. from version 3.0.x to 3.0.y, and in doing so it has screwed up your system partitions?
Did the touchpad reboot itself after 'upgrading'? If so, it probably was the above.
There may be a way to boot into webos recovery and repair the partitions, I'm not sure. Unless there's stuff on your touchpad that you want to keep (on the android partitions), I would be tempted to boot into webos recovery (holding volume up while pressing power), use AcmeUninstaller2, and then try booting into webos. If it won't boot, reboot into webos recovery and use webos doctor to rebuild webos system and then reinstall android.
Not an ideal solution, I know, as you will lose stuff on the tablet. Like I said, there may be a way of putting it into recovery and using novaterm to rebuild without a full uninstall/install.
Hope this helps!
Cheers

scl23enn4m3 said:
Any idea on how to fix this? A basic explanation would appreciated.
I came across this thread: http://forum.xda-developers.com/showthread.php?t=1564938
But I'm having some trouble following it
Click to expand...
Click to collapse
chris5s said:
I'm wondering, did webos perform a system upgrade, i.e. from version 3.0.x to 3.0.y, and in doing so it has screwed up your system partitions?
Did the touchpad reboot itself after 'upgrading'? If so, it probably was the above.
There may be a way to boot into webos recovery and repair the partitions, I'm not sure. Unless there's stuff on your touchpad that you want to keep (on the android partitions), I would be tempted to boot into webos recovery (holding volume up while pressing power), use AcmeUninstaller2, and then try booting into webos. If it won't boot, reboot into webos recovery and use webos doctor to rebuild webos system and then reinstall android.
Not an ideal solution, I know, as you will lose stuff on the tablet. Like I said, there may be a way of putting it into recovery and using novaterm to rebuild without a full uninstall/install.
Hope this helps!
Cheers
Click to expand...
Click to collapse
Yep sounds like you need to run the ACMEUninstaller2 and then the WebOS doctor to fix your tablet, this should help
How and when to Use the WebOS Doctor(Important):
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.0 to 3.0.5 Official Links
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode. Note the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.

chris5s said:
Hope this helps!
Cheers
Click to expand...
Click to collapse
RolandDeschain79 said:
Yep sounds like you need to run the ACMEUninstaller2 and then the WebOS doctor to fix your tablet, this should help
Click to expand...
Click to collapse
You both are absolutely awesome people! Worked perfectly and took much less effort than I was expecting to put in. Thank you!

Also, is WebOS doctor required if it booted into WebOS after the acmeuninstaller?

I would say not, if webos is working as it should, sounds like all is good.
However using the doctor - 3.0.0 then updating to 3.0.5 - might not be a bad idea, just so all your 'housework' is up to date and the tablet is back to original condition. Try using webos a bit and see, it may not be necessary...
Cheers