yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] nevertells2:
I thought if I gave you a prod in the right direction, that common sense would kick in. ;) J.C. is a pretty straight forward guy when I comes to his work. If it's not in the OP, then it's not a feature of TPtoolbox. As to his adding it to toolbox, you're going to have to wait for his answer on that. He is a pretty busy guy and you are talking about installing the reincarnation of OpenWebOS on a device the most users have been dying to get WebOS off of from the beginning. And now you want to put LuneOS back on it? Doubt you will get much support from anyone in this forum for that.

NT
[TouchPad Development] k4ever:
That's sad. I hope he considers it. I was a big fan of webOS. It is the whole reason I have a TouchPad. When HP killed the TouchPad, I was one of the first to come here and ask for an Android port, as a backup. I stuck with webOS as long as I could and when support had dried completely up, I completely jumped ship. J. C. and Roland were the ones that made the jump easy. Now with LuneOS out there, you can't expect guys like me to not want to at least give it a try. I figured if tptoolbox could install Android and webOS, than it should be able to handle LuneOS. If not, then I will find a way to do it on my own. Hopefully I won't completely mess up my Android setup.

http://xdaforums.com/showthread.php?p=16794995
[TouchPad Development] shumash:
If wishes were horses, beggars would ride.
[TouchPad Development] firepower9966:
I would like to see luneOS also as a option for Touchpad Toolbox. Only 1 ext3fs partition needs to be created.

There are no easy ways to create it, android does not have the full commands as Linux. You have to use novaterm or tailor that are webos based. I have created a post about this asking for help in doing this. I no longer want webOS as it no longer supported, but luneOS is built using latest open source tech and WebKit etc. I know its alpha but so was android on Touchpad but look how far its come from the great work of devs and support from users. hope luneOS can do the same.
[TouchPad Development] CalcProgrammer1:
Put a Debian chroot in Android, that will give you all the commands you could ever want.
[TouchPad Development] Probaholic1:
Sooo...in case we manage to brick this how do we recover. I think my touchpad died while it was going through the install. Now it won't power on or go into recovery. Sorry if this was already asked it's a big thread.
[TouchPad Development] jerryatherton:
Did you try holding down power and home button. Sometimes takes a while but it will usually wake it up.
[TouchPad Development] firepower9966:
Thanks for the info, will try to do same as you did with Debian but use luneOS instead. I have also wiped webOS and only have data media kitkat.
[TouchPad Development] Probaholic1:
Yeah unfortunately, the screen doesn't power on. When I plug it into the computer it recognizes the devic as "QHSUSB_Dload". but it doesn't install the drivers so it gives me an error
[TouchPad Development] mschumacher69:
Look for something called tpdebrick, it is also by [MENTION=2763462]jcsullins[/MENTION].
[TouchPad Development] real_sl4cker:
Yes, tpdebrick is the way to go. A colleagues TP had the same issue and recovering it was easy as ABC using tpdebrick :)
[TouchPad Development] nevertells2:
How about a direct link! :D

http://rootzwiki.com/topic/38786-tpdebrick-v004/
[TouchPad Development] worm9110:
First time to use TP Toolbox and I Installed the latest [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] without any problems. It was so cool using this tool, it makes things fun and simple. I have 4 touchpads in the household which I will be updating in the future because it makes it easy to do clean install.
[TouchPad Development] rebel1699:
Excellent tool and usage info. Expert job! Thanks for your hard work.
[TouchPad Development] garux:
I'm still having problems with 0913 version using MTP. Windows 8.1 will not recognize MTP but will recognize PTP. I’m using the latest TPToolbox v41 and did a full clean install. My band-aid for now is to use the WiFi File Transfer application for now. I tried enabling/disabling adb and it would not correct the problem.

Other than the issue with MTP, I'm not having any other problems. I must be doing something wrong, but can't figure out what it is.

Thanks again, I really do appreciate all you efforts you put into our HP TouchPad’s.
[TouchPad Development] numanoid50:
Sorry didn't get back to say thanks tried evervolv ROM and everything works perfect.

N.
[TouchPad Development] nevertells2:
You're welcome. Glad to help.

NT
[TouchPad Development] theechap:
It could be the lame ACER ADB driver that got installed on my Win 8.1 computer through windows update.

http://xdaforums.com/showpost.php?p=55277302&postcount=1692
[TouchPad Development] garux:
The ACER ADB driver is not installed on my Windows 8.1.

Thanks for the help.

*** UPDATE 1 ***

After renaming C:\Windows\Inf\wpdmtp.inf to xwpdmtp.inf, I'm now able to see the TouchPad in Windows 8.1 pro using Media device (MTP) on the TouchPad . All I know is that this worked for me.

*** UPDATE 2 ***

After renaming the wpdmtp.inf in UPDATE 1, Windows 8.1 pro was able to install the MTP USB Drivers for the TouchPad and re-created a new wpdmtp.inf file.
[TouchPad Development] spd2230:
That was quick and painless. So much easier than ACME. Thanks!
[TouchPad Development] nevertells2:
And how did you figure out to rename that file?

NT
[TouchPad Development] garux:
It dawned on me that I had the same problem with Windows 7 pro, so I thought I try it again with Windows 8.1 pro. Now I have everything working including all 4 Bluetooth.
[TouchPad Development] tjsooley:
Thats fantastic, However if I remove webos will I be able to reinstall it later?
[TouchPad Development] sstar:
Yes.
[TouchPad Development] tjsooley:
So how would one remove webos now?

its installed and fantastic but I want webos erased
[TouchPad Development] sstar:
Please make sure that you have the latest version, posted here, http://xdaforums.com/showpost.php?p=54986968&postcount=293, and read the Opening Post which contains all the info you need.
[TouchPad Development] mschumacher69:
Complete Data Reset wipes everything off ur TouchPad including webOS and starts u fresh...
[TouchPad Development] jerryatherton:
WIFI Issue

I have used TP Toolbox on several units, maybe 8-10 some with version 4.0 and mostly version 4.1. I just ran in to my first problem. I started with a fresh TP, ran Version 4.1 Toolbox, full data reset, and loaded Shumash Pac Rom, current minimal gapps. Could not get WIFI to connect.

Other devices, PC, phones and Touchpads all connected.

So I ran Toolbox again, full data reset, then ran WebOS Doctor. Rebooted WebOS and the WIFI worked. I did this to make sure it was not a hardware issue. Ran Toolbox again, installed android and Pac Rom, Gapps and recovery. I did not remove WebOS. Again no WIFI connect in Android, but good connection in WebOS. Then in recovery, I did a full wipe and installed Evervolv, same result no WIFI in Android, good connection in WebOS.

I am looking for ideas on what I could try next. Thanks.
[TouchPad Development] nevertells2:
Jerry, seems like there is always going to be one device that defies logic. I see no reason that WiFi should not connect. I personally have never tried Pac Rom and although I have tried Evervolv, I personally like CM Roms because of their full feature set of tweaks and settings while Evervolv uses the minimalist approach. Good move reinstalling WebOS to verify you do not appear to have a hardware issue. My suggestion, try a complete data reset again and install one of J.C. Sullin's CM11 Roms or install the previous Rom you had installed to see if the WiFI issue goes away. There was a time when certain folks were having an issue with WiFi not working when they had certain Roms or Roms built after a certain date. As far as I know, it was never resolved and they just had to use the version of Android that worked and not try to upgrade past that point. Keep us posted.

NT
[TouchPad Development] shumash:
Did wifi work in previous versions of the ROM? Describe what you mean by "could not get wifi to connect". Is the hardware active, but won't connect to existing sites? In that case; delete all current sites by hand, rescan, and see if you can reconnect.
[TouchPad Development] garux:
jcsullins, just want to say that the TPToolbox is a great piece of work you've done for our HP TouchPad. I just finished doing a friends TP and once again it went smooth. I can't speak for others, but both TouchPad seems to performance much better. I'm saying 'Goodbye' to WebOS. With WebOS going, it's like having a brand new tablet.
[TouchPad Development] alias4ever:
This had to be the EASIEST thing I have ever had to do with my TouchPad. Thank you SO MUCH jcsullins you truly are the greatest! A HUGE thumbs up to you and I thank you again for all your dedication and hard work in keeping our TouchPads alive and running smoothly and beautifully! :)
[TouchPad Development] biroot:
Tried yesterday night and approved!

Wiping the tablet and reinstalling lastest CM build took me arround 15 mins MAX, downloading the rom/gapps included!

Thanks, that's just amazing!
[TouchPad Development] jcsullins:
Yes, that's normal (at least for my CM11 build). The "internal storage" is what's located under /data/media. The "sdcard" is the legacy location for the sdcard (i.e. where it was on non-datamedia builds) that is shared with webOS.

The size of the "sdcard" will depend on what files are already on it. TPToolbox tries to resize it so that there is 600M of free space. So if you did a "Complete Data Reset" and then copied the install files there, 800M sounds about right. If webOS is siill installed, then it would be much higher.
[TouchPad Development] theronkinator:
Used this, worked great thanks! I did a full wipe then setup android from scratch. No WebOS listed in moboot.

I've got the following partitions:

System - 0.7GB

Data - 12.3GB

Media - 0.9GB

Total - 13.9GB

I know we have cache and stuff, but a clean touchpad on WebOS 3.0.2 has 13.5GB free excluding the OS, did WebOS really only make up the 400mb difference between it, or am I missing space somewhere?

Thanks.

Oh yeah, I flashed A6 firmware as well, just because, and that worked fine.
[TouchPad Development] jcsullins:
Doing a true uninstall of just Android or webOS is very difficult due to the shared nature of the "media" filesystem (and to a lesser extent /boot). ACMEUninstaller leaves various Android files in the "media" volume. I don't want to have a "Remove Android" that does that.

Given that you plan on removing webOS, what situation would you expect to use an "ACMEUninstaller replacement?"

There's a few reasons for keeping some free space on 'media'. Even without webOS, having some space on 'media' helps when you want to transfer files via a USB Mass-Storage mount (since 'media' is the only fat filesystem, that's the only one you can mount that way to the PC). In particular, that's the space TPToolbox uses when you copy files to do an install.

Even ignoring all that, I did some tests to see just how small you can make 'media' without causing problems. The Volume Resizer in TPToolbox is designed so that it shouldn't allow you to try to resize a volume smaller than you should. Based on my testing, it's not doing that as well as it should. One thing I noticed: when you make 'media' smaller than 264M, it (the lib that does the fat fs resizing) will convert the filesystem from FAT32 to FAT16. I'm not sure of all the problems that might cause, but think it's best we try to avoid them. So, I'll be enforcing a minimum size of 264M on 'media' in future TPToolbox releases.
[TouchPad Development] jcsullins:
I've been scratching my head trying to figure out how you could have ended up with the sizes you show with that 'df' output using TPToolbox to do the install.

Could you explain in more detail what you did prior to the "wipe and start fresh" you mentioned?
[TouchPad Development] jcsullins:
Yes, you'd need load TPToolbox via webOS recovery each time you want to 'run' it.

However, future versions may allow you to 'install it' so that you could just select it from moboot.
[TouchPad Development] jcsullins:
Yeah, the process should be the same no matter what you have installed.

It should create volumes, resize them, etc. as needed.
[TouchPad Development] donslade:
I went back and retraced my steps and determined that my situation was self induced: I played with the volume sizes after wiping the HPT but before installing your CM11. I adjusted the media and data volumes to about 1GB and ~2.3GB respectively erroneously thinking the remainder would be assigned to an SDCARD volume by default. The CM11 install went perfectly but then the remaining 12.3GB was not accessible. It wok me a while to figure out my error and my fix was just to re-do the install from scratch.

Now everything is fine after I redid the wipe and install. I let the toolbox size everything as it should and installed CM11. I have the proper volumes now including a 12.8GB DATA.

My thanks for a great tool. I passed this info on to my son so he could update his HPT also. I warned him not to do what I did!
[TouchPad Development] jcsullins:
I think you should have had ~12.5GB free with a clean webOS 3.0.2 install.

The 1G difference between 13.5G and 12.5G plus the 200M for cache and the 400MB ... ~1.6G for a clean webOS 3.0.2 install.
[TouchPad Development] garux:
Thanks so much for your reply. Great suggestion to add it to moboot.
[TouchPad Development] Bwangster12:
I haven't touched my Touchpad in a few months, but am running an older version of CM11 I believe. Before all this DM talk. If I load up Toolbox and do a total reset, I should be good to install the latest Android and choose the option to wipe WebOS?
[TouchPad Development] BIGSimon:
Yes, just do a complete data reset then install Android, just follow the on screen instructions and you should be good to go in around 10 - 15 minutes.
[TouchPad Development] garux:
You may want to get a backup before you start.
[TouchPad Development] Bwangster12:
As in a nandroid backup using my recovery?
[TouchPad Development] The Jack of Clubs:
is that a thing that can actually be done? like renaming the bin to a uimage and putting it in /boot?
[TouchPad Development] garux:
Yes. I used CWM for my recovery.
[TouchPad Development] Bwangster12:
Okay, so obviously if I am using CWM now (I can't remember, I have to go home and check), install that same version when I go through TPToolbox, or the backup won't recognize, right?
[TouchPad Development] garux:
If your using CWM before running TPToolbox, than use CWM for your recovery when using TPToolbox. I always using the same recovery in case I have to do a restore.

It's alway best to do a backup before making any changes.

.
[TouchPad Development] jerryatherton:
wifi

Thanks for responding Shumash and NT. It scans and finds the available networks, I select the best one, and key in the security. I click connect, and it doesn't always react, sometimes taking 3 taps. It then says "connecting" for a bit then it just goes back to "Save Secured with WPA2". When I do select the network it says signal strength "excellent". I am trying to figure out how to get a logcat with ADB.

Thanks again for your help guys.
[TouchPad Development] nevertells2:
Have you tried a couple of the old tricks when WiFi is acting up? Unplug your Router for a minute or so and let it fully reboot. Try a different network like at the library or Micky "D's". Change the name Android assigns to your tablet. Settings/developer options/ device name. Some routers don't work well with that long device name. I change it to TouchPad.

NT
[TouchPad Development] jerryatherton:
I have tried two different phones with wifi hotspots that I use often, no luck. I cant get the TP to come up on my ADB device list for a logcat. I may have to just set it aside for a few days. I will try it at work tomorrow.

Thanks again.

Edit, Got up early and tried another iteration. Loaded Toolbox with a different PC, (win 7 vs win 8), Full system wipe, did not reinstall webOS. Installed Milaq cm11. Same results.
[TouchPad Development] numanoid50:
Trying to install new nightly for HP touchpad on cm11. Do I do it the usual way go to recovery cwm and install zip. Or do I have to use toolbox. I've tried a couple of times and I keep getting the unfortunately the process. com android.systemui has stopped.
[TouchPad Development] mschumacher69:
It depends where u're coming from. If u've previously used the TPToolbox to re-partition ur TP for DM ROMs, then u can flash from recovery and wipe dalvik and cache.

If u haven't used the TPToolbox before and/or haven't re-partitioned ur TP for DM ROMs, then u have to use the TPToolbox.
[TouchPad Development] numanoid50:
Have used toolbox to install cm11. I'll try again to see what happens. I thought it should be straight forward.

Thanks
[TouchPad Development] jcsullins:
That issue has nothing to do with TPToolbox. It's a bug in the latest nightly (9-30). Install a different one.

.
[TouchPad Development] numanoid50:
Cheers.
[TouchPad Development] 35russ:
Installing Toolbox

Great stuff for the touchpad. I get to the point in installing the Toolbox to copy the Rom, Recovery and GApps zips. The problem is that my pc doesn't recognize the touchpad. I've tried unplugging and replugging usb and I rebooted and still nothing on the pc to show it recognizing the touchpad. Any ideas oris there another way to get the files to the toolbox? thanks
[TouchPad Development] mschumacher69:
Have u installed the novacom driver?
[TouchPad Development] 35russ:
Yes and have the toolbox to the point of the media volume should be available as an new "disk" usually named "HP Touchpad". Next it calls to copy the Rom, Recovery and GAps to the "ttinstall: directory. I have the zip files downloaded on my pc, the problem is that the pc doesn't recognize the touchpad.
[TouchPad Development] nevertells2:
Which version of the toolbox are you using?

NT
[TouchPad Development] 35russ:
The one on the 2nd page of this thread "TPToolbox is v40 released on 2014-05-18". Is there an updated version?
[TouchPad Development] 35russ:
My laptop is windows 8 so tried to install on a window 7 pc and same problem. When I get to copy the Rom etc in toolbox the pc doesn't recognize the touchpad. Is there another way to get the rom, recovery and gapps on the touchpad? thanks
[TouchPad Development] jerryatherton:
It sure sounds like the Novacom is not installed correctly. I have used version 4.0 and 4.1 on both Win 7 and Win 8.1 machines and it always comes up. do you see it install on the Touchpad when you mount the drive?
[TouchPad Development] 35russ:
Yes, it installs Touchpad Toolbox perfectly, it's when I get to the point of needing to install the Rom, Recovery and GApps that the pc does not recognize the touchpad so I have no way to get those zip files on to the touchpad.
[TouchPad Development] jerryatherton:
I am not sure I understand how it can install toolbox without recognizing the Touchpad.
[TouchPad Development] 35russ:
It sees the touchpad to the point that the toolbox is installed . As soon as the install is complete and I am at the main menu in toolbox the touchpad drops off the pc .
[TouchPad Development] jcsullins:
You should try using v41 from this post:

http://xdaforums.com/showpost.php?p=54986968&postcount=293

Also, notice that you will need to use one of the recoveries that are linked from that post.

NOTE: The primary reason v41 did not not replace v40 in the top posts was because it does not support the gapps

package that was (when it was posted) suggested by one of the ROMs. However, it seems that that gapps package

has since been discontinued. I.E. It should not be considered experimental, buggy, etc.
[TouchPad Development] 35russ:
Thanks, yes I found v41 after it was mentioned earlier and have tried that as well. It all goes well until the toolbox is installed, then the pc notification and the touchpad disappears from the pc. As I mentioned my laptop has windows 8 and I tried a desktop with windows 7, same thing. Is there another way to get recovery etc on the touchpad? Thanks.
[TouchPad Development] jcsullins:
Did you try selecting "Install" or "Mount Media Volume" using v41?

It changes how it is identified to the PC once it gets to "Mount Media" so it may

not appear until it gets to that point.

It you have tried select "Mount Media" using v41 and it still does not appear, please follow the instructions

on this post: http://xdaforums.com/showpost.php?p=53258228&postcount=10

so I can have a look at the kernel log (you can post it to this thread instead) to see what's happening.
[TouchPad Development] 35russ:
Thanks for you assistance! Here is the link: https://dl.dropboxusercontent.com/u/88325307/klog.txt
[TouchPad Development] nevertells2:
Novacom is only needed during the process of starting up toolbox. After that, except for needing one's TouchPad and PC connected to transfer the needed installation files to the ttinstall folder, you can unplug the tablet from the PC. Once you have removed WebOS from the TouchPad, there is enough room in the /boot folder/volume, that you can rename the .bin to uImage.TPtoolbox, and place it in the /boot folder and then it will show up on the Moboot screen and can be run from there. J.C can correct me or confirm that mounting the media volume is the same process as when you mount the old SD card/USB drive via WebOS or from recovery. That does not require Novacom.

The PC not recognizing the TouchPad was discussed and a process to hopefully correct the problem was discussed in one of Rolandeschain79's "Install Android the Easy Way" threads. You will have to hunt for it, as I do not remember exactly where I saw it. If I run across the discussion, I'll come back and post a link here.

One thing I do remember, if the USB drivers are correctly installed, you can see the TouchPad in "Device Manager" on your PC.

NT
[TouchPad Development] mschumacher69:
So why don't you replace v40 with v41 in the top posts now that this unsupported gapps package has been discontinued [MENTION=2763462]jcsullins[/MENTION]?
[TouchPad Development] theechap:
I'm not sure if it's the same issue but I was having problems getting my Touchpad to get recognized and it turns out that Windows Update automatically installed some adb drivers from ACER or something. Once I uninstalled them from the device manager, everything went back to normal and my TP would let me copy files again. I'm on Win 8.1 but I heard about it from someone with Win 7.

http://xdaforums.com/showpost.php?p=55277302&postcount=1692
[TouchPad Development] jcsullins:
OK, I've made some changes that I'd like you to test and get logs.

Please test and get logs from BOTH of these:

(LINK REMOVED)

and

(LINK REMOVED)

Thanks.
[TouchPad Development] 35russ:
Thanks and will do, although probably won't have time today. Will how to install be available at the links. Also, how how do I get logs?
[TouchPad Development] jcsullins:
Just do the same you did for v41 with v41a and v41b.
[TouchPad Development] 35russ:
Here is a link to test a : https://dl.dropboxusercontent.com/u/88325307/klog.a..txt

b to follow.....