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

Search This thread

jerryatherton

Senior Member
Sep 22, 2012
896
280
hey guys, this seems to be an awesome tool from what im reading, however im having an issue, maybe i missed something. i have wiped my tp using the toolbox and am now attempiting to intsall android as instructed, when the ttinstall folder pops up on my pc im dragging these 3 files into it and ejecting the touchpad, then hitting unmount media volume, but then it says

>>> checking install files...
1 logical volume in volume group "store" now active
no supported recovery file found. aborting.

im stuck,

any help?

thanks in advance.

josh.

Use one of the recoveries in the op. You can flash the selinux recovery later.

Sent from my TouchPad using XDA Premium HD app
 

shar88

Senior Member
Jun 14, 2014
89
19
hey guys, this seems to be an awesome tool from what im reading, however im having an issue, maybe i missed something. i have wiped my tp using the toolbox and am now attempiting to intsall android as instructed, when the ttinstall folder pops up on my pc im dragging these 3 files into it and ejecting the touchpad, then hitting unmount media volume, but then it says

>>> checking install files...
1 logical volume in volume group "store" now active
no supported recovery file found. aborting.

im stuck,

any help?

thanks in advance.

josh.


download one of the three supported recoveries in post #3
 

the fat kid

Member
May 10, 2010
6
0
Use one of the recoveries in the op. You can flash the selinux recovery later.

Sent from my TouchPad using XDA Premium HD app



i appreciate the quick response, so im throwing in the zip file that says " update-cwm-jcs>>>>>>>>>>>>" along with the "gapps-kk>>>>>>>"

and then unmounting media volume?

again, thank you,.

---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------

edit: just tried all 3 of the recovery files in the op and it still says same error message. any ideas? should i be renaming this from update-cwm blah blah, to the format that it is saying is accepted such as,

It will recognize as a compatible KitKat/DataMedia ROM files that look like:
cm-11-*-tenderloin.zip or
ev_tenderloin-nightly-2014.??.??.zip or
aokp_tenderloin_kitkat_*.zip

again im throwing the gapps-kk-20140105.zip in the ttinstall folder along with the update-cwm-jcs-dm-tenderloin.zip file and then ejecting the tp selecgint unmount media volume and am still getting the error message.

---------- Post added at 03:22 AM ---------- Previous post was at 02:47 AM ----------

geez im a freakin moron.... i had incompatible zip files... sorry folks for the clutter



all other noobs like me WATCH THE VIDEO TWICE.

thanks again, all of you are awesome and hopefully this makes my touchpad relevant again.
 

jerryatherton

Senior Member
Sep 22, 2012
896
280
I have only had to rename the gapps, I find that the

gapps-kk-****.zip works best.


I have done 6 machines with it. Keep at it, it works.

Sent from my TouchPad using XDA Premium HD app
 

emo72

Member
Aug 26, 2011
24
2
thanks mr sullins. i cant believe my tp is running 4.4.4 in 2014:good:

it worked so easy. the guys a legend.
 
  • Like
Reactions: BinkXDA

clutterking

Senior Member
Jan 15, 2010
77
4
Can someone explain how to navigate to the media folder from within android? It's the folder that shows up when connecting to usb storage on my computer, where I was able to upload my kitkat rom, etc. I can't find it anywhere while using esfileexplorer. Thanks for the help.
 

Moody66

Senior Member
Nov 6, 2013
1,573
453
57
Uhrichsville
Can someone explain how to navigate to the media folder from within android? It's the folder that shows up when connecting to usb storage on my computer, where I was able to upload my kitkat rom, etc. I can't find it anywhere while using esfileexplorer. Thanks for the help.

You can't . Probably with evervolv NON data/media ROM you can.
 

gradular

Senior Member
Jan 4, 2012
203
101
Dawsonville
Can someone explain how to navigate to the media folder from within android? It's the folder that shows up when connecting to usb storage on my computer, where I was able to upload my kitkat rom, etc. I can't find it anywhere while using esfileexplorer. Thanks for the help.
In non datamedia builds, media is mounted as sdcard or sdcard0. In most data media builds, media is mounted as sdcard1 since data is mounted to sdcard0.






You can't . Probably with evervolv NON data/media ROM you can.

That is only true with milaqs data media build. He decided not to mount media at all.



Sent from my GT-P3110 using XDA Free mobile app
 

Moody66

Senior Member
Nov 6, 2013
1,573
453
57
Uhrichsville
In non datamedia builds, media is mounted as sdcard or sdcard0. In most data media builds, media is mounted as sdcard1 since data is mounted to sdcard0.








That is only true with milaqs data media build. He decided not to mount media at all.



Sent from my GT-P3110 using XDA Free mobile app
Since he hasn't been able to locate it it would make sense he's using a ROM that doesnt mount it. BTW others are The same way. Pac rom by shumash doesn't mount It either........
 
Last edited:

clutterking

Senior Member
Jan 15, 2010
77
4
I am using Pac rom. I am able to mount /media from recovery and copy files over from my pc but it looks like there might be no way to access them from within the rom itself. Is there a way to mount /sdcard1 or some other directory that I might be able to access from the rom?
 

Moody66

Senior Member
Nov 6, 2013
1,573
453
57
Uhrichsville
I am using Pac rom. I am able to mount /media from recovery and copy files over from my pc but it looks like there might be no way to access them from within the rom itself. Is there a way to mount /sdcard1 or some other directory that I might be able to access from the rom?

As i stated earlier. Not using that rom. Pac Is basicly a Modified version of Milaq's CM11.
 

nevertells2

Senior Member
Dec 22, 2011
2,307
1,138
Sunny Central Florida!!!

dariuus

Member
Sep 19, 2008
7
0
youtube problem

First off... +8000 thank yous to JSCullins for this. I was thinking of buying my toddler a new Samsung tablet as the CM9 was beginning to act kind of dodgy. This new build is very solid.

We use the tablet for probably 90% YouTube use. We have noticed consistently after using the tablet and then putting it back on the charger for a little while, and then going back into YouTube that if you search for a video it will bring you to the play screen put it won't actually play anything. I have to reboot the tablet to get it to work. I have tried toggling WIFI, as well as task killing youtube (and all other processs) to try and get it to "reset" itself to no avail. I may be an isolated case here, and maybe it will function better after going into recovery and doing a cache/dalvik wipe again. But I was wondering if anybody else has experienced this behavior, and if so what was the fix.

Note: I did a full WebOS wipe when installing, I did not select the A6 firmware option as I was not sure what that did exactly.

Regards,
D
 

sstar

Senior Member
Apr 6, 2012
1,344
469
Brighton
A6 firmware is to flash /reset the battery to ensure longer lifespan. I do it once every couple of months.

PS now that you have removed webOS you can actually copy the toolbox uImage to the boot folder so that you don't have to use a pc as there is now enough space..
 

a in yul

Senior Member
Jul 23, 2006
203
9
Canada
A6 firmware is to flash /reset the battery to ensure longer lifespan. I do it once every couple of months.

PS now that you have removed webOS you can actually copy the toolbox uImage to the boot folder so that you don't have to use a pc as there is now enough space..

Be sure to tell him what to name it so it will work.:laugh:

this is really interesting, how do we go about doing that? and what do we name it?

thks
 
Last edited:
  • Like
Reactions: crashboxprime

Top Liked Posts

  • There are no posts matching your filters.
  • 281
    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.
    118
    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
    113
    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
    81
    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.
    66
    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