[TOOLS] Touchpad Toolbox (updated 2015-02-25)

Search This thread
By:
Advanced…
garux

garux

Senior Member
May 23, 2013
243
106
In the Heart of Central Pennsylvania
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.
 
  • Like
Reactions: graffix31
A

alias4ever

Senior Member
Sep 19, 2011
477
102
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! :)
 
B

biroot

Senior Member
Dec 30, 2008
82
5
Paris
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!
 
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
phikal said:
Used toolbox to do a full reset , wipe webos and install cm 11.
Worked fast and easy.
27 gb free after install.

One question though, is it normal to have a internal storage and a sdcard partition (about 800 mb) after install ?
Click to expand...
Click to collapse

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.
 
Last edited:
  • Like
Reactions: swear0730, xyomguix and phikal
T

theronkinator

Senior Member
Apr 16, 2011
526
214
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.
 
Last edited:
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
theronkinator said:
Brilliant, amazed by how much support the Touchpad has, it's embarrassing that as a none native android device it has better custom roms than my Sony Xperia U and Galaxy S3 (i9300).

Not a major issue, but I'd like to see ACMEUninstaller built in to remove just android and leave WebOS, not a major issue if not as I can just use ACMEUninstaller. *edit* Given the state of data media, this is probably useless anyway, unless it would reverse it all and redo the original partitions at the same time.

Soon as I get chance on Friday WebOS is getting nuked off my touchpad once and for all.

Thanks again for all the great work.

*edit* I'm running your 4.2.2 currently which is running great but will move to your 4.4.2 when I test this. If we've nuked webos does media still need to be kept at ~600mb, can it not be knocked down to a token size like 5-10mb or something?

Thanks.
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: swear0730, xyomguix and theronkinator
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
donslade said:
One question: after resizing the volumes before installing Android I'm only seeing about 2.7GB in data and about 900MB in Media after Android install. I had sized data to about 12GB.

I have a 16GB Touchpad and its running your latest 4.4 Android snapshot.
Click to expand...
Click to collapse

donslade said:
Please see info from df command:

u0_a57@tenderloin:/ $ df
Filesystem Size Used Free Blksize
/dev 403.3M 136.0K 403.2M 4096
/sys/fs/cgroup 403.3M 0.0K 403.3M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 403.3M 0.0K 403.3M 4096
/mnt/asec/com.speedsoftware.rootexplorer-1 4.0M 3.0M 1.0M 4096
/mnt/obb 403.3M 0.0K 403.3M 4096
/mnt/fuse 403.3M 0.0K 403.3M 4096
/boot 32.0M 13.0M 19.0M 1024
/system 755.9M 490.9M 265.0M 4096
/data 2.9G 517.1M 2.4G 4096
/cache 315.0M 5.3M 309.6M 4096
/mnt/shell/emulated: Permission denied
/storage/sdcard1 903.1M 208.0K 902.9M 8192
/storage/emulated 403.3M 0.0K 403.3M 4096
/mnt/media_rw/sdcard1: Permission denied
/mnt/secure/asec: Permission denied
/storage/emulated/0 2.9G 517.1M 2.4G 4096
/storage/emulated/legacy 2.9G 517.1M 2.4G 4096

As shown it looks to me like I have no permission to access sdcard1. How can I correct this so that the sdcard1 is mounted and becomes accessible?

Thanks in advance.
Click to expand...
Click to collapse

donslade said:
Since Touchpad Toolbox makes it so easy I just wiped and started fresh. This time everything worked as expected!! Thanks for a great application!
Click to expand...
Click to collapse

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?
 
  • Like
Reactions: swear0730
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
garux said:
JCS, I normally run the a6 firmware once a month. To do this monthly, please correct me if I am wrong, I would need to go into WebOS recovery and run the TPToolbox script to flash the A6 firmware? Is this correct?
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: MikeN68, swear0730, mpgrimm2 and 3 others
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
dsmturbo said:
I hope just a quick question so I understand.
If I already have 4.3 running, the procedure I follow is the same as not having Android previously?

I can not seem to download the rom and gapps from:
http://xdaforums.com/showthread.php?t=2712680

Are there other links?

Edit: nevermind, appears I grabbed the correct files from goo.im
Click to expand...
Click to collapse

Yeah, the process should be the same no matter what you have installed.

It should create volumes, resize them, etc. as needed.
 
  • Like
Reactions: swear0730 and xyomguix
donslade

donslade

Senior Member
Mar 4, 2010
164
48
El Paso, TX
jcsullins said:
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?
Click to expand...
Click to collapse

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!
 
J

jcsullins

Senior Member
Jul 20, 2010
237
1,878
theronkinator said:
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.
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: swear0730, xyomguix and theronkinator
B

Bwangster12

Senior Member
Jan 3, 2011
969
107
New York
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?
 
BIGSimon

BIGSimon

Senior Member
Jan 19, 2012
556
807
Barnsley
Bwangster12 said:
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?
Click to expand...
Click to collapse

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.
 
  • Like
Reactions: BinkXDA
garux

garux

Senior Member
May 23, 2013
243
106
In the Heart of Central Pennsylvania
Bwangster12 said:
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?
Click to expand...
Click to collapse

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.



.
 
You must log in or register to reply here.

Similar threads

Leoisright
  • Locked
  • Poll
[Super Tweaked][vB2.9.1 Odexed][CM7 XRON-ified][Updated 01/03/2012]
Replies
8K
Views
1M
Leoisright
Leoisright
D
  • Locked
[ANDROID] Android on the TouchPad?
Replies
1K
Views
672K
j.a
j.a
A
[webOS] [GUIDE] Overclock the HP Touchpad to 1.9Ghz
Replies
528
Views
533K
D
Don_Mayor
BIGSimon
  • Poll
[ROM] [CM10/CM10.1] [Experimental Preview by Jcsullins] [01/05/14]
Replies
3K
Views
1M
A
anonxlg
krarvind
[GUIDE][Update][Android CM Alpha 3] How to Install CM Alpha on Touchpad
Replies
640
Views
327K
M
Mcintyre94

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 281
    J
    jcsullins
    Touchpad Toolbox (aka tptoolbox) is a completely self-contained and user-friendly system for the low-level management of the HP Touchpad.

    TPToolbox replaces:
    • ACMEInstallers
    • ACMEUninstallers
    • Various methods of resizing volumes (erroneously called partitions)
    • Various methods of reflashing the A6 battery monitoring chip
    • Various methods of completely wiping/recreating volumes

    TPToolbox adds:
    • A straightforward, reliable and easy-to-use method of installing all versions (ICS to LP) of Android on the Touchpad.
    • The ability to completely remove webOS.
    User Interface
    As the toolbox name implies, there are several tools in tptoolbox. These tools are accessible via a menu-driven interface:

    tptoolbox_v40_mm.png


    The interface consists of three primary panes: menu, help and output. The menu pane is toward the top left. The help pane is toward the top right. The output pane is at the bottom.

    When a tool runs, output (and possible error messages) will appear in the output pane (doh!). Also, the very bottom of the menu pane will have a "WORKING" status indicator. When a tool fails to complete successfully, the status indicator will change to "FAILED." When a tool completes successfully, the status indicator will change to "DONE." The DONE/FAILED status indicator will remain until the next user input (i.e. VolUp/VolDn/Home is pressed).

    Most tools, however, are not simple one-step operations. They may require additional confirmation or input during the process. In those cases, the "WORKING" indicator will disappear (without a DONE/FAILED) after part of the process completes and a new menu will appear. You will be guided through these processes with appropriate information in the help pane. Also, if an operation is cancelled (i.e. you say 'no' to a confirmation, etc.), the status indicator will be reset (be blank).

    The VolumeUp, VolumeDown and Home buttons are used to select menu items.

    The screen will automatically blank if there is no user input for 20 mins. The Power button can be used to blank/unblank the screen.


    Installing Android
    Although the on-screen help will guide you through the process when you select "Install Android", I'll give an overview of the process here and how it differs from previous methods. Unlike previous methods of installing Android, you do not need to copy any files onto the Touchpad prior to running TPToolbox. After you select "Intstall Android" it will do some basic checks on the volumes and filesystems on the device. Then, it will share the "media" volume to your PC allowing you to copy the installation files (ROM, Recovery and GApps) to the Touchpad. It will then check these install files to make sure they are compatible and have no obvious errors (i.e. basic zip integrity check). Assuming those tests pass, it will create a set of volume resizing criteria based on the type of Android being installed (i.e. DataMedia vs Non-DataMedia) and confirm that you have availablespace on the device. Next, you will be presented a menu allowing you to confirm to proceed with the installation. It will then install moboot (which is included in TPToolbox) and recovery and resize the volumes. Then it will generate an "install script" for recovery and boot into recovery to complete the installation of the ROM and GApps. After recovery completes it's installation of the ROM and GApps, the Touchpad should boot into the newly installed ROM.

    TL;DR: Select "Install Android," Copy files when it asks, Confirm when it asks

    For more information on compatible ROM/Recovery/Gapps, etc., see post #3.

    Complete Data Reset, webOS Removal and Android Uninstall
    One of the tools available is "Complete Data Reset". This will completely wipe all OSes and Data from the Touchpad and rebuild the volumes fresh (actually, there will only be one volume after this, 'media') and rebuild /boot with a minimal set of programs (provided by tptoolbox) that are required by Android to boot. After doing a "Complete Data Reset," you can then "Install Android" (i.e. without webOS). Or, you can re-install webOS (see "Create webOS Volumes" in post #4) and then (optionally) "Install Android." Note that there are no separate "remove webOS" or "remove Android" (This is by design!).

    See Also
    Post #2 - Loading TPToolbox
    Post #3 - Installing Android via TPToolbox
    Post #4 - Other TPToolbox Tools
    Post #5 - TPToolbox Limitations/FAQs/etc.
    View
    118
    J
    jcsullins
    Loading TPToolbox

    The latest version of TPToolbox is v42 released on 2015-01-08.

    It can be downloaded from:
    http://downloads.codefi.re/jcsullins/cmtouchpad/tptoolbox/TPToolbox-2015-01-08-v42.zip or
    http://www.mediafire.com/download/kuz6e3itpudl9q2/TPToolbox-2015-01-08-v42.zip or
    https://www.androidfilehost.com/?fid=95887005526788942

    Loading TPToolbox is as simple as A, B, C

    A) Have novacom installed
    To load TPToolbox, you will need novacom to be installed on your PC.
    You can download novacom drivers from: http://downloads.codefi.re/jcsullins/webos/novacom
    Or, you can download and run a java-based "universal installer" from http://123haynes.github.io/universal-novacom-installer


    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.


    C) Run the script provided with TPToolbox
    Extract the contents of the TPToolbox zip file from above.
    Navigate to the tptoolbox_v42 directory that was extracted from the zip.
    On Windows, run the batch file named tptb_v42_win.bat
    On Linux, run the script named tptb_v42_nix.sh
    On Mac, run the script named tptb_v42_mac.command
    View
    113
    J
    jcsullins
    Installing Android via TPToolbox

    Installation Overview
    For the most reliable install, it is suggested that you consider doing a "Complete Data Reset" (as mentioned in the OP) prior to doing the install as it's the best way to "start fresh."

    The OP gave an overview of the process that TPToolbox uses to install Android.

    From a user perspective, it's pretty simple: copy three files (ROM, Gapps and Recovery) when and where TPToolbox asks and then select "yes" when asked to confirm the install details.

    Below is the list of Recoveries that you can use with TPToolbox. Those marked with "DM" are for data-media ROMs and those marked with "NODM" are for non-datamedia ROMs. Unless the developer has specified otherwise, you can assume that any KK or LP ROM is datamedia and ROMs previous to KK are non-datamedia. However, TPToolbox checks to make sure that the ROM and Recovery are compatible and will tell you if they are not.

    Compatible DataMedia (DM) recoveries

    Download traditional CWM (DM):
    http://downloads.codefi.re/jcsullins/cmtouchpad/recovery/update-CWM-jcs-dm-tenderloin-20141231.zip or
    https://www.androidfilehost.com/?fid=95887005526788938 or
    http://www.mediafire.com/download/eyugz1w6twld313/update-CWM-jcs-dm-tenderloin-20141231.zip

    Download Philz-CWM (DM):
    http://downloads.codefi.re/jcsullin...date-PhilZ_CWM-jcs-dm-tenderloin-20140612.zip or
    https://www.androidfilehost.com/?fid=23610159112654007 or
    http://www.mediafire.com/download/vvldbc3380y4pl1/update-PhilZ_CWM-jcs-dm-tenderloin-20140612.zip

    Download TWRP (DM):
    http://downloads.codefi.re/jcsullins/cmtouchpad/recovery/update-TWRP-jcs-dm-tenderloin-20140612b.zip or
    https://www.androidfilehost.com/?fid=95784891001615841 or
    http://www.mediafire.com/download/d155um5531ymp3h/update-TWRP-jcs-dm-tenderloin-20140612b.zip

    Download flintman's Dec. 23, 2014 build of TWRP (DM):
    http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip

    Compatible Non-DataMedia (NODM) recoveries

    Download traditional CWM (NODM):
    http://downloads.codefi.re/jcsullins/cmtouchpad/recovery/update-CWM-jcs-nodm-tenderloin-20141231.zip or
    https://www.androidfilehost.com/?fid=95887005526788937 or
    http://www.mediafire.com/download/y7xqj521a76z4ml/update-CWM-jcs-nodm-tenderloin-20141231.zip

    Download Philz-CWM (NODM):
    http://downloads.codefi.re/jcsullin...te-PhilZ_CWM-jcs-nodm-tenderloin-20140614.zip or
    https://www.androidfilehost.com/?fid=23610159112654008 or
    http://www.mediafire.com/download/eb602915di0gcuc/update-PhilZ_CWM-jcs-nodm-tenderloin-20140614.zip

    Download TWRP (NODM):
    http://downloads.codefi.re/jcsullin...update-TWRP-jcs-nodm-tenderloin-20140614b.zip or
    https://www.androidfilehost.com/?fid=95784891001615842 or
    http://www.mediafire.com/download/r4grp5bu6brsl6l/update-TWRP-jcs-nodm-tenderloin-20140614b.zip
    View
    81
    J
    jcsullins
    Other TPToolbox Tools

    Mount Media Volume allows you to access the 'media' volume from your PC

    Reflash A6 Firmware allows you to reflash the A6 firmware.

    Resize Android Volumes
    This allows you to interactively resize the Android (and media) volumes.
    This is not needed to "Install Android", but can be used at other times to 'tweak' the volume sizes as needed.

    Repair Android Volumes
    If a fsck (file system check) determines that there are non-trivial errors on a filesystem, then this can be used to attempt to fix those errors.

    Create webOS Volumes
    If you want to re-install webOS following a "Full Data Reset," you will need to run this prior to running webOS doctor.
    At this time, re-installing webOS should only be done prior to installing Android. Tools to assist re-installing webOS after
    Android has been installed (without detriment to the Android install) may be provided in the future.
    View
    66
    J
    jcsullins
    TPToolbox Limitations/FAQs/etc.

    Limitations

    • This thread
    • Re-install of webOS after Android installed is not supported yet. (i.e. after a "Complete Data Reset", you must re-install webOS before Android)
    • Method for permanently installing TPToolbox (always available via moboot) not available yet
    • Installation of a "3rd OS" (i.e. luneOS) not supported yet
    • Installation of Android without Gapps not supported yey
    View

New posts