yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] 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
[TouchPad Development] 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.
[TouchPad Development] 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
[TouchPad Development] jcsullins:
reserved
[TouchPad Development] jcsullins:
reserved too
[TouchPad Development] phikal:
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 ?
[TouchPad Development] BIGSimon:
HP TouchPad Index

I've added this to the HP TouchPad Index

Great work JCS :good:
[TouchPad Development] donslade:
This is exactly the type of high quality, high functionality solutions that make this forum great. Thank you.

This just brought back my borked (yes, I did it) Touchpad to a fully functional tablet without resorting to WebOSDr. And in less time than it took me to download the required files and get novacom working!

Now to hit that Thank You button...
[TouchPad Development] theronkinator:
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.
[TouchPad Development] mpgrimm2:
Thanks for the work on the toolbox JcSullins. Looking forward to trying this out when I get home.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] donslade:
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.
[TouchPad Development] nightfireblaze8:
I think it is normal. I have it too.
[TouchPad Development] garux:
All I can say is W O W. Thanks you so much jcsullins, you really out did yourself. The HP TouchPad Toolbox is a real blessing. We now have an official android device for our HP TouchPad. Your directions were easy to following, I including flashing the A6 Firmware. Android runns really smooth. Thanks again for all the work you put into the toolbox, it was worthwhile waiting for.
[TouchPad Development] garux:
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?
[TouchPad Development] BIGSimon:
Looking at the way it re-sizes the volumes you should end up with a media volume of at least 600M

KitKat/DataMedia Volume (re)sizing criteria

system: MIN_SIZE: 704M

cache: MIN_SIZE: 200M

data: MIN_SIZE: 1500M

data: also takes any free-space "media" has over 600M

This would be where the installation files are stored while the TPToolbox re-sizes and creates the necessary volumes for Android to install.
[TouchPad Development] donslade:
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.
[TouchPad Development] dsmturbo:
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
[TouchPad Development] donslade:
Since Touchpad Toolbox makes it so easy I just wiped and started fresh. This time everything worked as expected!! Thanks for a great application!
[TouchPad Development] synchron50:
Hey, you're right! I just renamed bin to uImage.tptoolbox and put it in /boot via RomToolbox lite and can get into the tool without USB cord. Excellent!
[TouchPad Development] johnsmith33584:
Look at the "Other Items" link, apparently he is ripping off other people's work and selling it as his own.

Sadly, nothing he is selling is copyrighted or trademarked that I am aware of. What he is doing is highly unethical, but you can't stop him from being a jerk. If you can post feedback about him on Ebay, that might stop some of what he is doing or at least inform those buying what he is doing.
[TouchPad Development] Moody66:
EBay has a po!icy about beta software. And cydia is a program that allows downloading of pirated software aka vshare, appcake, etc. Both are no nos on eBay. Not to mention eBay does have ethics policy.
[TouchPad Development] johnsmith33584:
Are you serious!!!!!!:silly: Try mounting "media" and plug in the USB cable. Does the TouchPad communicate with your PC, can you copy files?

That .bin file is almost 12.5mb in size. I'm surprised it fit. How much space is left in /boot now that you have that huge file in there?

---------- Post added at 09:18 PM ---------- Previous post was at 09:16 PM ----------

[/COLOR]

Report his ass.
[TouchPad Development] garux:
WOW. This is really saying a lot. Thanks so much for all your efforts in putting the TPToolbox together for us. What a GREAT piece of work and so easy to use.

Thanks again for all you do for our HP TouchPad's.
[TouchPad Development] RolandDeschain79:
ebay auction removed

Hey guys thanks for reporting this, he was indeed just selling a copy of my instructions for $10 a shot. I've reported the problem but the ebayer was nice enough to remove the listing when contacted about it. Its unethical to be selling the info that we're giving away for free. Spreading the word about the great work of our talented developers (for free) is my way of giving back to the people who really make things happen.

I always do my best to give credit to Jcsullins and all our talented developers for their continued contributions to HP TP development. Jcsullins TPToolbox really is a stroke of genius and just what users have needed to make the DM transition smooth and easy. I look forward to testing new builds, It would be great to have it integrated into our TP's Moboot menu but it might be best to wait for Jcsullins OK before giving people the idea to do that.
[TouchPad Development] Moody66:
Thanks for the help. I reported them as soon as I saw it. The cydia is straight up copyright infringement. The. Touchpad part violates the rules on beta uncertified software. Devs could also flag it as violating their rights as well. Thanks again. Might want to keep a watch on. He has relisted the apple stuff. May relist yours as well.
[TouchPad Development] chris5s:
Not sure why you guys are all getting your knickers in a twist here about ebay on the TP Toolbox thread!!

Get a room/thread and let's keep stuff on topic...

Peace
[TouchPad Development] Moody66:
Because this tool was part if the sale.
[TouchPad Development] synchron50:
Like Philz/Jcs CWM recovery and TWRP, the TP toolbox only show's the smaller sdcard1 volume that has the ttinstall folder. I have 30.75M used currently on /boot so I'm definitely living on the edge.
[TouchPad Development] seboj:
Picked up the Touchpad for the first time in a while, glad to see JCSullins is still going strong.

Toolbox worked perfectly on the first try, complete data reset and Android install. Just followed the instructions in the OP. WebOS is gone, the partitions are all the correct sizes, and CM11/CWM installed like butter.

Awesome tool you've created.
[TouchPad Development] hanman:
Can't Mount Media

I can't get the media volume to mount on my PC. I've tried 3 different PCs, Windows 8.1 x64, Windows 7 x86, and Archlinux. I can boot into TPToolbox on all three, but none of them see a USB device at all, much less storage, when I select Mount Media Volume or Install Android. What can I do? Complete Data Reset seems to have worked as expected, but I can't proceed without being able to mount media. It's a 32GB Wifi TP, if that matters.
[TouchPad Development] synchron50:
Wow, that's a bummer. I have the same TP (32G) and installed with W7 x64 - that should make no difference. Can you repeat what I did (see post #107), that is do a CDR and then a Mount Media? You should see a very clean HP Touchpad volume assigned to a drive letter on the PC (mine showed 31,226,920,960 bytes free). If not, do you at least see W7 attempting to install drivers in the task tray? Try monitoring under W7 Device manager and see if anything is happening under 'USB Mass Storage Device'.

I did some research and came across Mpgrimm's notes regarding all the different flavors of data/media recoveries and it appears that all of them can either only mount sdcard1 only or attempt to mount with nothing happening or no mount features at all. So, is there any way of mounting to USB both volumes (sdcard0, sdcard1) through linux commands via terminal by booting into WebOS recovery? If not, why is there this limitation of not being able to xfer files via USB to and from the main sdcard volume within the bootloader? I know that I can resize the sdcard1 volume in tptoolbox but would like an understanding of why the mounting is not doable, otherwise, I would think JCS would have put that feature under Mount Media in tptoolbox.
[TouchPad Development] hanman:
It turned out to be the cable. I swapped to another one, and it works fine. Go figure.
[TouchPad Development] synchron50:
Yeah, I'll guess that it was an HP mico-usb cable which is always hit or miss (mostly miss).

Well, on another subject, I jumped the gun and attempted to install WebCM10 on CM11. Bad move, didn't work. I then tried to flash Remove WebCM10 and it still didn't work. I was left with a TP, most probably in an infinite stuck loop with the CyanogenMod 11 logo spinning endlessly. The good news is I get to say <whew> and test a restore of my very first CWM backup since I come from TWRPville. This was a little painful, here's why:

1) After the CWM backup I noticed that the sdcard was showing approx 2.25G less and I wanted to xfer to PC but I could not find it under sdcard/clockworkmod/backup. I used SD Card Analyst in ES File Explorer and it simply did not show up. Tried SDMaid and it didn't show up there as well.

2) I rebooted back to CWM recovery and sure enough the backup (folder) was in sdcard/clockworkmod/backup.

3) Back to CM11, scratching my head, I used RomToolbox Lite and it found both TWRP and CWM backups. The path for the CWM is not under sdcard but (from root): /mnt/shell/emulated/clockworkmod/backup.

So, when I moved the CWM backup to the sdcard/clockworkmod/backup folder in order to be copied to PC via MTP USB I was kinda stuck when I couldn't boot into CM11 after the WebCM10 fiasco. Very frustrating to not be able to restore a nandroid backup that's there but you can't access it. I guess the rule of thumb to get your nandroid backup to PC is to copy it to the sdcard temporarily and then copy it to PC. Once that's done, I guess the one on the SD card can be deleted since the one you need in case of trouble is on /mnt.

To be back on topic, the good news is I was eventually able to restore my nandroid using tptoolbox (the copy I put in /boot). It really didn't need to do that much because there's already a ttinstall folder prepared on sdcard1 and you don't even need to mount or change partition sizes when you just choose 'Install Android'. It eventually puts a clean copy of CM11 and then I had the hassle of reentering my wifi account, reentering my google account credentials just to get to the playstore and download ES Explorer so I could copy the CM11 backup back to /mnt which is where CWM apparently needs it to be even though once you're in CWM, it says its under the sdcard. This is Philz-CWM latest touch version that's in post #3, BTW. Also of note, when you choose just 'Install Android' my /boot remained untouched since it must have detected that whatever versions were in ttinstall were all ready the same so, unexpectedly, my tptoolbox remained on /boot.

A fun day today, now, back to the World Cup!
[TouchPad Development] cybershawngates:
[MENTION=2763462]jcsullins[/MENTION] you are truly a gifted genious!!! THank you for such an amazing tool and thank you once again for the Brilliant A6 firmware tool that rescued my dead TP about 1.5 yrs ago.
[TouchPad Development] Carpetman:
I've tried to use this and really screwed something up. I can't get the PC to detect the TP when I plug it in. I can't remember what I did but all that happens now when I turn on the TP all I get is a screen that shows : moboot 0.3.8

boot

boot webOS Recovery

reboot

shutdown

I can press "boot webOS Recovery" and get the big usb .If I run the novacom it will start running the double penguins but stops after it says"Aborting! Please reboot.

Any Help?
[TouchPad Development] chris5s:
Maybe try going into webos recovery and using webos doctor and starting from scratch?

Good luck...
[TouchPad Development] nevertells2:
Make sure you PC is correctly configured per the instructions for this tool.

Follow the instructions and put the TouchPad in WebOS recovery. Connect the PC and TouchPad via the USB cable and run the script file. Do the complete data reset again and then see if things work correctly. Except for a couple of prompts, everything is run by the script including mounting the media volume so you can copy the Rom, Gapps and recovery to the ttinstall folder.
[TouchPad Development] jcsullins:
Review Post #2 of this thread for instructions on loading TPToolbox.

It sounds like you are trying to load ACMEInstaller or ACMEUninstaller instead of TPToolbox.
[TouchPad Development] Carpetman:
When I get to the part that says"run the batch file named tptb_v40_win.bat" and click on it , I get so far as to the command prompt and it says"Cannot find Touchpad toolbox binary file TPToolbox-2014-5-18-v40.bin."
[TouchPad Development] Carpetman:
Reconnected on another PC and everything worked. Once I got to the ttinstall folder I wasn't doubleclicking on it and copying the files there, I was just copying under the" ttinstall" which of course didn't work. Now all is goooood!!! Thanks to all for replys and help.
[TouchPad Development] synchron50:
When I initially ran the bat script, it came up that same message and even though I see a '%PATH% in the BAT file, I needed to manually add the C:\Program Files\Palm, Inc to the system path and then things worked properly with the tp40 script as long as I left the MS command prompt session open.
[TouchPad Development] nevertells2:
Humm... I've used at least two different PC's to run the toolbox and never had to modify the path variable to get it to work. And the toolbox batch file and .bin do reside in a folder of their own. I would think as long as the batch file and .bin are in the same folder, it should work. Go figure!!! :confused:
[TouchPad Development] ColdSunNC:
Wow. I haven't played with my Touchpad in forever, but this is truly AMAZING. Sorry I'm so late to say thank you, but thank you!
[TouchPad Development] williamj1:
Thanks

Just wanted to add my piece.

Thank you very much for this wonderful tool. As someone with little experience in ADB or this sort of thing, at first glance it looked incredibly complex and beyond my capabilities. Much to my surprise however, it was not - and worked flawlessly.

I have to suggestions which I feel if added to the main posts, might help other novices like me. To some, these will seem glaringly obvious which I appreciate, but nonetheless they are the only bits of information not provided which confused me.

1. The most basic of all - I was expecting this to be some console which ran on the PC, as per other toolkits I've used from XDA. Much to my surprise, I was amazed when it suddenly booted up into it on the Touchpad device itself.

2. That the files (ROM, Recovery and Gapps) don't need to be loaded onto the device before the process begins. It stated it would ask you to copy over, but I wasn't sure if this meant on the device itself and didn't realise I could just leave them on the computer for the initial steps.

---------

Once again, thanks very much for this superb bit of work.

Much, much appreciated.

William
[TouchPad Development] goalcam:
After removing webOS, flashing A6, and (re)installing Android, I've noticed that my TouchPad no longer charges in Android. I reinstalled webOS and found that it charges properly there. Went back to Android only again and found that it was again not charging. Am I doing something wrong? :confused: Is this a symptom of removing webOS or is it probably the ROM I'm using (milaq's CM11 nightlies) which is to blame?
[TouchPad Development] nevertells2:
Make sure that settings/battery, MTP is checked, and if that doesn't help try installing jcsullins latest CM11 ROM, dated 0409. Make sure you do a complete data reset so no remnants of the other ROM are left behind to contaminate things. I've been using his April 5th Rom since it came out, without issue. With all this practice, you're going to be a touchpad toolbox expert. :good:

BTW, you might want to mention how it went reinstalling WebOS to test out your battery charging issue.
[TouchPad Development] goalcam:
I tried Settings/Storage/MTP and USB, neither way helped. Ended up flashing the most recent build of milaq's nightlies and it seems to be charging properly now though nobody in that thread seemed to mention any issues with charging.

Can't really provide good instructions with regards to reinstall WebOS as I think I was too impatient when waiting for it to boot after restoring with WebOS Doctor, but I manually recreated the volumes through novaterm and ran WebOS Doctor 3.0.0.
[TouchPad Development] nevertells2:
So you did not download his two files that fixes the WebOS certificates and use them? I understand that your intent was to install enough of WebOS to insure that you could charge your TP via WebOS. I have not heard of anyone using his procedure to fix the expired certificates and was wondering how it goes doing that. Thanks
[TouchPad Development] goalcam:
Ah, nope, I hadn't seen those instructions.
[TouchPad Development] nevertells2:
Check out post #64
[TouchPad Development] asif9t9:
My Touchpad has WebOS 3.0.5 and a CM10.1 ROM, but ever since it lost all battery charge and I had to reboot, it seems to have lost the ability for me to delete anything off the memory. I can make changes to either CM or WebOS (copy files, load apps), but as soon as I reboot, all changes are lost.

Anyway I ran TP Toolbox to start over with a Complete Data Reset, but I get an error,

ERROR: LVM config erase check FAILED. Possible read-only failure.

Any other way to just start over? WebOS doctor doesn't work. :(
[TouchPad Development] nevertells2:
ACMEUninstaller2?
[TouchPad Development] na_tra:
If the ACMEUninstaller2 does not work, get the ACMEUninstaller instead.