Related
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
bone625 said:
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
Click to expand...
Click to collapse
Take a look at this thread. I think it could have information that could maybe help you.
forum.xda-developers.com/showthread.php?t=1508572
Thanks, bah tried all that - the problem is mounting USB recovery, can't get into androidto test anything else. I'll have access to a few other computers this weekend so I"ll see if they can find it. Going to rewipe everything tonight as well, will update... pretty annoying.
I have an idea.
What you can try is to reboot into WebOS, mount the /media drive so you can copy files to it from Windows. On that media drive, there should still be a folder called cminstall. Copy the moboot install zip back into there, and then reboot the tablet into recovery (Power+VolUp). From there, run AcmeInstaller2 again, and you should be good to go - it'll run, and force an install of the contents of that /media/cminstall folder, which'll put Moboot back in place.
At least, that's what SHOULD happen. I'm no expert, but from what I've seen and played with, that should do what you're trying to achieve.
Thanks for trying.. Not exactly what it needed to be fixed though. I have everything ready to go in uninstall, the computer (any computer I've tried so far, and its been quite a few - that all used to read the touchpad in recovery mode) won't register it and mount it as a drive so I can run ACMEInstaller in the first place.
It must have changed something on the touchpad itself, because it used to mount fine before that happened... Now every computer installs it as palm novacom booties and never mounts the actual drive, and acmeinstaller just says no device or something like that. Bah, still can't figure it out, I miss android haha.
Did you enable MTP in the advanced menu under the Storage section?
Are you trying to get the device to show up in adb? If you are having troubles with that I found a really nice guide on another website on how to get adb to read the touchpad if nothing else is working. Not sure if I can post the link or not. Send me a pm if this is something you need.
Sent from my cm_tenderloin using xda premium
Problem is I can't boot into android cause the bootloader broke and I can't get it to boot android period, even with cyboot. I know all l I have to do is run ACME again... But I can't run it cause it won't mount haha. Stuck in webOS for now, and every computer I've tried won't boot recovery mode anymore. Drivers check out and register but can't change anything to recognize it as a drive. I think I'm going to try to manually uninstall everything android, then reinstall webOS and see if it mounts then. Blah!
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
Click to expand...
Click to collapse
This trick with webOS doctor just saved my ass. I couldn't boot past the green cyanogenmod splash screen and needed to boot straight off an image from moboot on my desktop, and taking webOS doctor to that step was the only thing that would let me run the command line entry to make it where my PC would talk to my touchpad. So, thank you
Would this work for a TP that reads both ways on PC as listed by OP but is only stock?
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
Click to expand...
Click to collapse
What do mean by run ACMEInstaller? I only know using the novacom boot mem:// <ACMEInstaller method, though that's getting stuck while on the two penguin screen.
Hp touchpad 32GB converted into Android 4.4.4.KitKat with ROM CM11
Hi My name is Ramadoss.N Recently I have converted my touch pad to Android KITKAT 4.4.4. with Rom CM11 -20140625- Snap Shot- jcsulline. I used TPtoolbox V41d to install. Everything working fine. except few observation.
1. Bottom Menu Button like Home , Return to previous screen are not working in vertical position of touchpad, where as it works in Horizontal position.
2. There are 3 dots on right hand side corner to provide dropdown menu: it works in vertical position, does not work in Horizontal position.
3. search icon ( which looks like a magnifying glass) does not work in both positions.
4.Back space key working in Vertical position, does not work in horizontal position.
5. Could not load Music via computer after installing Android in the Touchpad,
I really appreciate if any one can give me solution for above.
Regards
Ramadoss.N
email : [email protected]
i've seen numerous posts about this all over the place and couldn't find a fix anywhere
after providing logs to jcsullins he managed to solve my issue and now have a fully working TP again
heres the thread i created over at rootzwiki http://rootzwiki.com/topic/37804-battery-question-mark-issue/
and heres the link to the irc post for jcsullins to guide people through it
only created this here as i know a lot don't go on rootzwiki but many have this issue
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__310#entry1068329
hopefully this will help someone out and resurrect your thought to be dead TP
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Thanks
Thanks, it helped me a lot!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
I was able to fix my touchpad with this rootzwiki guide above. My touchpad had JB installed, after a battery drain it was completly dead. I was able to charge it by cutting down an old USB cable and charging the battery alone (touchpad had to be opened).
FYI (Tried ubuntu 12.04.2 in 2 different machines, the tpdebrick only worked on my alienware on the Dell with 1GB of ram it did not worked. The alienware has 2GB of RAM.)
The battery took almost 50% charge, then tried booting it up and nothing (only got question mark).
Theres a small button inside the unit in the charging module, I pressed it, and the unit turned off (it was the only way I could get it to shut down.
Did the debrick process, after that the touchpad would not charg via the USB port and only via the touchstone, so I did the ACMEUninstaller to remove android and it's good as new again. The problem for me was caused by the JB android installed. I had no problems when it had ICS.
Followed the instructions in the link from the first post. And it works!
Was skeptical as instructions seems very complex, but I thought I got nothing to lose. In summary, it was straight forward and you just need to:
1. Download Ubuntu 12.04 LTS and burn the iso to a CD/DVD.
2. Boot up your PC with the Ubuntu Installation CD.
3. Select Try Ubuntu rather than Install.
4. Follow the listed steps/instructions. PS: If you see a "space" for the terminal command, there is a "space" required when you key in the terminal command. And when the script is running, its working, even though you see nothing on the touchpad screen. When "All Done", the touchpad simply rebooted by itself, and ran through the usual boot-up sequence.
Good luck.
Its fixed!!!! Thanks!!!
jackygogo said:
I noticed the links in this post doesn't really lead you to the debrick guide, so I am writing this.
P.S. I am ONLY reporting my experience as is to my HP Touchpad 16GB running CM-tenderloin. I am not in any way responsible for developing this method nor am I responsible for any extra damage that might happen to your already problematic Touchpad. Good luck, and research is your best friend.
I got this question mark battery problem as well and after doing some research I thought my HP Touchpad was gone for good. Then I saw this post and after reading it it inspired me to try the tpdebrick made my jcsullins. And... it worked and my touchpad is back to normal (with everything data intact as well, to my surprise!). My problem was similar to described by other posts in this forum: the touchpad was discharged until it turned off, and then it was left that way for a long time, and when I tried to charge again, it would first give me a flashing home button and then the battery with a question mark after a long time of charging. No matter how long I charged the problem persist, and the device refuses to go into recovery mode no matter what I do. WebOS is unable to detect the device as well, but the PC was able to recognize it as Palm or UQSB something something something (I forgot what it was). After this problem I did not do any battery change or hardware changes. Just me, the question mark battery, and the tpdebrick buigde by jcsullins.
So if you have this problem and absolutely cannot get into the recovery mode, give tpdebrick a try. I used tpdebrick-v004 by jcsullins: rootzwiki.com/topic/38786-tpdebrick-v004
Follow through the steps in that post and it should be okay. But, in case anyone needs it, this is all the steps I did:
0) While my screen was displaying the question mark battery, I pressed Power + Home + Vol Up + Vol Down for 30 seconds while USB plugged into PC to make sure everything turns off (i.e. black screen, no flashing home button). This step may or may not be necessary since part of the debrick process you need to do Power + Home + Vol Down, and it will most likely do the same thing. But just in case.
1) downloaded Ubuntu 12.04 32bit, downloaded webOS 3.0.5 doctor (this was in zip format, and I had to change it to .jar extension), and downloaded tpdebrick-v004.zip from the link above. You can download webOS doctor and tpdebrick in Ubuntu so that you can follow the instruction as written without any trouble, but I did it in my Windows and I fetched it from the Windows storage in Ubuntu. Whichever is easier for you.
2) Downloaded Universal USB Installer and made a bootable USB of Ubuntu. Followed instruction here: ubuntu.com/download/help/create-a-usb-stick-on-windows
3. Boot from USB and run Ubuntu OS
4. Found and moved the tpdebrick.zip and webos jar into the Ubuntu OS Downloads folder
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
6. Wait patiently for 5 - 10 minutes, and then it says All Done. By this point, my HP touchpad rebooted back to the original state. If this does not happen for you, then you might need to keep researching! Good luck!
NOTE: After the process, my touchpad rebooted back into CM, and I noticed the battery was fully charged. So, obviously there was no problem with the battery nor the charging process. My problem must be due to miscommunication with the battery status.
Click to expand...
Click to collapse
Thanks so much!!! I am so far from knowing how to fix a computer or tablet and my daughters HP touchpad did all of the things mentioned and I did the debrick and It is up and working. I was nervous to try this debrick thing since I have no clue how to do computer stuff but all the directions were clear and easy. Thanks!! I have a happy daughter
sudo ./tpdebrick command not found
hi dude, thank you for the post but i always got the message sudo ./tpdebrick command not found, could you help me?
note: the tpdebrick file is into the folder u.u
dfu-util and fastboot missing
[email protected]:~$ cd downloads
bash: cd: downloads: No such file or directory
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip tpdebrick-v004
Archive: tpdebrick-v004.zip
replace tpdebrick-v004/tp16.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: n
replace tpdebrick-v004/ebr16.bin? [y]es, [n]o, [A]ll, [N]one, [r]ename: N
[email protected]:~/Downloads$ cd tpdebrick-v004
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Aborted.
[email protected]:~/Downloads/tpdebrick-v004$
why is this coming up? i cant find any links to where i would find dfu-util or fastboot or where it needs to be.
What version of Ubuntu are you using? Is it 32 or 64 bit?
gtallmadge said:
What version of Ubuntu are you using? Is it 32 or 64 bit?
Click to expand...
Click to collapse
I used this particular file and made it into a bootable usb stick
releases.ubuntu.com/12.04/ubuntu-12.04.4-desktop-i386.iso
ubuntu.com/download/desktop/create-a-usb-stick-on-windows
It was a lot easier than I thought, just did the tpdebrick today :good::good:
fixed for the right links
Glad it worked for you. I knew the directions said to use Ubuntu 12.04 which is still available so it is good to know 14.04 which is
the current Long term release of Ubuntu works as well.
I'm sorry, but it was this one that I used
releases.ubuntu.com/12.04/
Thanks for the info..I obviously misread your post.
Questionmark of Death on TP
First problem I ran into, couldn't find a working link for the webos doctor, after an hour of searching, came across a link but xda won't let me post since I don't have 10 posts.
w w w . adbtoolkit.com /rooting/devices/hp/tenderloin/webOS-Doctor/wifi/#.VGYTS9YghCW
Next issue, when it told me to hold my power+vol down+home button down, it would time out with some error( I think it said qdl not found something like that). Tried a few times, then tried a samsung cable for my phone instead of the original touchpad cable, and that worked. Thanks to the guy at rootzwiki for the information.
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
ractar28 said:
Does anyone have information on where to find this information now? rootzwiki seems to have deleted it.
Click to expand...
Click to collapse
It's not deleted. You have to log into rootzwiki from the error screen, and the link will load.
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Gamedays said:
Unfortunately if you don't have an account, you can't register any longer for one (I couldn't get the registration process to work).
Luckily, there is the Internet Archive. I can't post a link, so change the 2 "URL" with HTTP in the below:
URL://web.archive.org/web/20150211095226/URL://rootzwiki.com/topic/38786-tpdebrick-v004
Click to expand...
Click to collapse
Do you happen to have the guide as well, or am I missing it somewhere? I was also unable to get the registration process to work... the step I am on specifically:
5. Followed steps 14 to 23 from the debrick instruction by JC above. (Basically run terminal, unzip tpdebrick-v004.zip, and hold power + home + vol down for 30 seconds, and run script, and then run "sudo ./tpdebrick XX" where XX = size of your touchpad)
Thanks!
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!!!
HI, I am trying to update my HP tablet to 4.x.x with a data media partition. I booted to webos, used the webos quicksetup application to install preware then installed tailor. With tailor I deleted the android partitions and created new partitions. I ended up with something like this
system = 600mb
cache = 200mb
media = 600
data = 11.2
Then I rebooted WebOS and got the message "Not Enough Storage to Download. You must clear space n your drive before you can download."
I cannot install stuff with quicksetup any more. it just keeps trying forever and does not do anything. My Mac only recognizes a 600mb partition for WebOS and wants to initialize it.
Any ideas how to fix this?
Jonathan
jonawald said:
HI, I am trying to update my HP tablet to 4.x.x with a data media partition. I booted to webos, used the webos quicksetup application to install preware then installed tailor. With tailor I deleted the android partitions and created new partitions. I ended up with something like this
system = 600mb
cache = 200mb
media = 600
data = 11.2
Then I rebooted WebOS and got the message "Not Enough Storage to Download. You must clear space n your drive before you can download."
I cannot install stuff with quicksetup any more. it just keeps trying forever and does not do anything. My Mac only recognizes a 600mb partition for WebOS and wants to initialize it.
Any ideas how to fix this?
Jonathan
Click to expand...
Click to collapse
bump. Anybody? When I go to device information I see Memory 16GB Available 0.0GB There's got to be somebody out there who can tell me how to redo the partitions.
I'm assuming Tailor will not let you resize your webos media partition?
If not, the easiest way may be to use AcmeUninstaller2 to completely remove Android, and start again but leave webos a larger media partition.
I have a 16gb Touchpad and have left 2gb for webos media, seems to do the job.
Cheers
Chris
chris5s said:
I'm assuming Tailor will not let you resize your webos media partition?
If not, the easiest way may be to use AcmeUninstaller2 to completely remove Android, and start again but leave webos a larger media partition.
I have a 16gb Touchpad and have left 2gb for webos media, seems to do the job.
Cheers
Chris
Click to expand...
Click to collapse
Thanks Chris
I can't install tailor because there is not enough space to install anything. I will look at AmeUninstaller2 when I have a bit of time. I hope it is something I can do from a PC or Mac because there is no way I can install anything to that TP or even read the webos drive... at lease from my macbook.
AcmeUninstaller is used in the exact same way that you would have used AcmeInstaller to get Android into the Touchpad in the first place.
I would use AcmeUninstaller2 from here to get rid of Android partitions and Acmeinstaller4 or 5 from that post install Android again.
Cheers
---------- Post added at 02:47 PM ---------- Previous post was at 02:19 PM ----------
It seems that going straight to a data/media build from scratch is difficult, if not impossible, due to the resizing required. You have to have JB/CM10.x installed first.
However, if you want to try Kitkat, and don't want to mess around with resizing partitions, this is an excellent rom!
Cheers
chris5s said:
AcmeUninstaller is used in the exact same way that you would have used AcmeInstaller to get Android into the Touchpad in the first place.
I would use AcmeUninstaller2 from here to get rid of Android partitions and Acmeinstaller4 or 5 from that post install Android again.
Cheers
---------- Post added at 02:47 PM ---------- Previous post was at 02:19 PM ----------
It seems that going straight to a data/media build from scratch is difficult, if not impossible, due to the resizing required. You have to have JB/CM10.x installed first.
However, if you want to try Kitkat, and don't want to mess around with resizing partitions, this is an excellent rom!
Cheers
Click to expand...
Click to collapse
Thanks for the Help
Ok I ran ACMEuninstaller2 on the Touchpad. Still same problem. When I go to Settings Device Information I see I have 16GB memory but 0.0 available. This is with Only WebOS installed no other apps. I have tried resetting the TP and erasing USB drive and Full Erase too. Any suggestions now?
Strange... When its plugged into a computer and you look at the files/folders, does it still tell you there's no storage space left?
Have you used webos doctor to restore partitions?
This thread may hold some clues/answers...
Good luck, cheers
chris5s said:
Strange... When its plugged into a computer and you look at the files/folders, does it still tell you there's no storage space left?
Have you used webos doctor to restore partitions?
This thread may hold some clues/answers...
Good luck, cheers
Click to expand...
Click to collapse
The computer only sees 1.4G of space that it wants to format because it can't read it. I figure that is the webos Space.
Ok, sounds like you need to use webos doctor to restore the original partitions.
Use version 3.0.0 first, then update to 3.0.5. Its a pain maybe doing it twice, but only 3.0.0 will restore partitions properly.
Cheers
chris5s said:
Ok, sounds like you need to use webos doctor to restore the original partitions.
Use version 3.0.0 first, then update to 3.0.5. Its a pain maybe doing it twice, but only 3.0.0 will restore partitions properly.
Cheers
Click to expand...
Click to collapse
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
jonawald said:
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
Click to expand...
Click to collapse
I guess I need to do this. Quoted from the Wikki
If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).
If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.
I am stuck at this part. I tried uncompressing the .jar folder. but could not find anything I could identify as a ulmage. This is the 3.0.0 image. Could you break this down a bit for me? I am using a Mac, but should be similar to PC. Many thanks in advance.
First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):
novacom boot mem:// < nova-installer-image-castle.uImage
After it boots, run novaterm:
novaterm
Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
then type:
mkdosfs -f 1 -s 64 /dev/store/media
Once that completes, put the device back into recovery mode and run the webOS Doctor.
"I am stuck at this part. I tried uncompressing the .jar folder. but could not find anything I could identify as a ulmage."
I think its in a zip file called webos under 'resources'.
Also look through this thread, it may help.
Cheers
jonawald said:
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
Click to expand...
Click to collapse
Did you have any version of android installed and if so did you run ACMEUninstaller 2 before running webOS Doctor?
sstar said:
Did you have any version of android installed and if so did you run ACMEUninstaller 2 before running webOS Doctor?
Click to expand...
Click to collapse
I had ICS installed. I ran ACMEUninstaller2. Thanks.
jonawald said:
I had ICS installed. I ran ACMEUninstaller2. Thanks.
Click to expand...
Click to collapse
Hi have a read of these 2 thread's (There only 6/7 pages long) http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/ , http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-4.html .
Hopefully they will be of some help , good luck.
sstar said:
Hi have a read of these 2 thread's (There only 6/7 pages long) http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/ , http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-4.html .
Hopefully they will be of some help , good luck.
Click to expand...
Click to collapse
Thanks. I am reading them. Will give it a shot when I have a bit of time again.
Jonathan
jonawald said:
Thanks. I am reading them. Will give it a shot when I have a bit of time again.
Jonathan
Click to expand...
Click to collapse
One more thanks to everybody. I got that Touchpad up and working perfectly again.
Jonathan
Bought 2 TP's 3 years ago. Operated one and the other stayed in the box. Flashed and installed Android on the first one and it recently died. Took # 2 out iof the box and can't activate WebOS or find a bypass. Am I SOL or is there a workaround?
bruce6735 said:
Bought 2 TP's 3 years ago. Operated one and the other stayed in the box. Flashed and installed Android on the first one and it recently died. Took # 2 out iof the box and can't activate WebOS or find a bypass. Am I SOL or is there a workaround?
Click to expand...
Click to collapse
Touchpad Toolbox should let you remove WebOS an install Android.
jerryatherton said:
Touchpad Toolbox should let you remove WebOS an install Android.
Click to expand...
Click to collapse
But since this is a new TP fresh out of the box how do I get to the "big USB" symbol tp connect it to the PC? Currently it is looping trying to reach the WebOS server which is no longer there.
bruce6735 said:
But since this is a new TP fresh out of the box how do I get to the "big USB" symbol tp connect it to the PC? Currently it is looping trying to reach the WebOS server which is no longer there.
Click to expand...
Click to collapse
Read through RolandDeschain's guides. You will find that if you hold Volume up while booting into webos, you will get USB mode.
Also there is a file you can flash whilst in webos recovery (big usb symbol) that bypasses activating the TP via webos servers.
Not at my home PC but will link the address later if its helpful?
chris5s said:
Also there is a file you can flash whilst in webos recovery (big usb symbol) that bypasses activating the TP via webos servers.
Not at my home PC but will link the address later if its helpful?
Click to expand...
Click to collapse
Please link the address. Have made progress. Got to the "Big USB". Installed TPToolbox and Novacom on my Windows 10 PC and I'm stuck.
Here is a thread about using the bypass activation tool. There are different links in the thread for the tool itself, if none work let me know and I'll post the file when I get in front of my PC. :good:
Peace
---------- Post added at 08:31 PM ---------- Previous post was at 07:47 PM ----------
However, if you intend to install Android and use it exclusively, it is probably worth considering deleting webos partition using the toolbox and getting all the files needed for whichever flavour of Android you decide upon. Saves all the hassle of bypassing webos activation and can be done from the USB symbol.
New Touchpad Activation ???
Here's where I am now. Installed HPToolpbox annd Novacom on my Windows 10 PC. Set the Touch pad to "Big USB" and connected to the computer which is not finding it in "My PC". However in the Palm directory in Windows 10 Device Manager it shows, but with an information indicator "Device requires further installation". Any help or further advice will be appreciated. My only desire is to get to the TPToolbox and install android. Once Android is installed I have no need for WEBOS
Don't know how win 10 works but can you click on device properties and get it to download the palm bootie drivers needed? Should do it automatically from the 'net.