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
Related
Ok, i bought an HP Touchpad but it has webOS + Android installed.
I don't want Android, and i don't care do a Factory Reset if this leave the HP Touchpad as new.
So, can i do a Factory Reset without problems?
Also, how?
Thank you very much
If you want to completely remove Android/clockwork/moboot I think you have to use the the ACMEuninstaller... search here or on rootzwiki for the link. Then to be sure, I would doctor the touchpad with the latest webOS 3.0.4 (search for that too, there is a link to the file).
But, I would personally keep android on there too. It doesn't affect webOS at all and you can always switch between them.
Factory reset in WebOS or Android?
Factory reset in Android wont damage anything in both OS...I am not very sure about doing factory reset in WebOS...but as the above poster said, you should do a ACEMuninstall before...its super easy.....I will also recommend to keep both as you might get bored of WebOs due to lack of apps.
Factory reset on webOS. It's second hand and i want to test the tablet as new.
if you want to do everything from webos, you can install an app from preware called remove android. Then install internalz pro from preware and remove any remaining android files. Follow this with a secure full erase in webos. You should then have a clean webos install. Sounds like a bit of work but it should not take more than an hour to complete.
That being said, the methods mentioned above from your desktop using acmeuninstaller also work well. Unless you use a root file manager soch as root explorer in android or internalz pro in webos, there will still be a few random android files to be removed. While webos doctor is an ecellent tool, even HP recommends that as a last resort. I would suggest the secure full erase within webos to give you an out of the box experience.
Just my 2 cents....
Sent from my Touchpad using Tapatalk
i don't know about removing android with webos, but with ACMEuninstall the android memory partitions will be returned to webos.
Then you should use the webos Doctor.
Thank you very much. Very helpful.
Thanks.
[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
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
Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?
anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp
Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.
shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5
mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse
shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.
issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
"
Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.
Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.
No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1
HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.
Hi there, so I saw that you do a lot of videos about the HP touchpad, Basically I decided to delete android off my touchpad and I did but in the process I also deleted webos. Only thing that comes up is the webOS logo and that's it...I've tried to use webOS doctor and WebOS quick installer but for some reason these programs refuse to pick up the device. All my computers are seeing my device as "palm" and "unidentified" I tried looking for the drivers but because it's such a out dated I couldn't find anything...please help me get webOS back!!
coolzab123 said:
Hi there, so I saw that you do a lot of videos about the HP touchpad, Basically I decided to delete android off my touchpad and I did but in the process I also deleted webos. Only thing that comes up is the webOS logo and that's it...I've tried to use webOS doctor and WebOS quick installer but for some reason these programs refuse to pick up the device. All my computers are seeing my device as "palm" and "unidentified" I tried looking for the drivers but because it's such a out dated I couldn't find anything...please help me get webOS back!!
Click to expand...
Click to collapse
Do you have novacom and novaterm installed, including Java Runtime Environment? hope it helps
http://forum.xda-developers.com/hp-...roid-4-4-x-t2912820/post56167358#post56167358
A)You must have the novacom software installed on your PC before running Jcsullins Touchpad Toolbox.
Download and run the Universal Novacom Installer 1.4.1. Click here:
Note:You will need to have Java installed to run the Universal installer. Click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS. Click here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
ashTP88 said:
Do you have novacom and novaterm installed, including Java Runtime Environment? hope it helps
http://forum.xda-developers.com/hp-...roid-4-4-x-t2912820/post56167358#post56167358
A)You must have the novacom software installed on your PC before running Jcsullins Touchpad Toolbox.
Download and run the Universal Novacom Installer 1.4.1. Click here:
Note:You will need to have Java installed to run the Universal installer. Click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS. Click here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
Click to expand...
Click to collapse
Err I'm confused Sorry, I'm so new to all this. So I have Novcom, Novaterm and JRE(Java Run time environment) Do I now just run the WebOS Doctor?
EDIT: I tried that and still it WebOS Doctor does not work.
Read my Super Easy way thread for full details on everything
coolzab123 said:
Hi there, so I saw that you do a lot of videos about the HP touchpad, Basically I decided to delete android off my touchpad and I did but in the process I also deleted webos. Only thing that comes up is the webOS logo and that's it...I've tried to use webOS doctor and WebOS quick installer but for some reason these programs refuse to pick up the device. All my computers are seeing my device as "palm" and "unidentified" I tried looking for the drivers but because it's such a out dated I couldn't find anything...please help me get webOS back!!
Click to expand...
Click to collapse
So you did a complete data reset and you want to reininstall WebOS. You've already run the TPtoolbox from your PC so you must already have the novacom software installed. You just need to read the last two lines in my thread info to find the detailed instructions you'll need.
A)(Optional) Complete Data Reset, Completely Removes WebOS and Android
-The procedure will completely remove WebOS and Android from the device. The partitions/volumes will be rebuilt new and boot will be remade with a minimal amount of programs provided by the TPToolbox.
-Scroll down to Complete Data Reset and select it with the home button and choose yes to begin the process.
-If you previously did step number 3 then skip this step and proceed to step B.
-If you previously removed WebOS but want to add it back use Jcsullins instructions click here:
-If you need to bypass the WebOS activation get the tool and instructions click here:
Read this thread.
[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way
RolandDeschain79 said:
So you did a complete data reset and you want to reininstall WebOS. You've already run the TPtoolbox from your PC so you must already have the novacom software installed. You just need to read the last two lines in my thread info to find the detailed instructions you'll need.
A)(Optional) Complete Data Reset, Completely Removes WebOS and Android
-The procedure will completely remove WebOS and Android from the device. The partitions/volumes will be rebuilt new and boot will be remade with a minimal amount of programs provided by the TPToolbox.
-Scroll down to Complete Data Reset and select it with the home button and choose yes to begin the process.
-If you previously did step number 3 then skip this step and proceed to step B.
-If you previously removed WebOS but want to add it back use Jcsullins instructions click here:
-If you need to bypass the WebOS activation get the tool and instructions click here:
Read this thread.
[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way
Click to expand...
Click to collapse
Hey thanks! Everything has been fixed