yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] asif9t9:
Tried both ACMEUninstaller2 and ACMEUninstaller and both ran with the double Penguins for a few minutes, but eventually failed and then just rebooted the Touchpad and it went back to Moboot and loaded CM10.1 like nothing ever happened.

I did catch a message at the end, "Resize FAT failed, you probably want to run fsck later".
[TouchPad Development] Vakman:
Thanks for the tool.

Quick question, is there any reason to keep WebOS on the tablet if I'm not using it. Don't get me wrong, it's a great UI and I love it but I never use it due to the lack of functionality now compared to Android.

I guess my question is are there any ROMs that rely on having webOS intakes for any features our anything?
[TouchPad Development] asif9t9:
My tablet is screwy now (see above posts), and when my Android loads, I get these errors popping up. So I have been loading it in WebOS mode lately just for the simple sake of things like charging it up. I'll tell ya, if I get my TP working again, I won't get rid of WebOS.
[TouchPad Development] hollywood084:
Battery is dead

My battery died and it won't charge. I can't even boot into USB mode (it displays the low battery plug and battery icon). I completely wiped my TP with TP toolbox and installed Evervolv. Since then, the battery died and it won't take a charge. I've tried resetting it every which way. WebOS doctor won't detect it either. Original 2A charger and cable. Has my battery taken a ****, or is this related to TPTB?
[TouchPad Development] asif9t9:
My battery had died and wouldn't charge. Until I tried my Touchstone charger. Since that worked, to get the device back up, the USB is working a again. Not sure if that helps.
[TouchPad Development] hollywood084:
I managed to fix it. It finally gathered enough charge (took hours) Was just a random coincidence.
[TouchPad Development] nevertells2:
To answer your question, no there are not any Rom's that rely on WebOS.

To remove or not remove WebOS is an individual decision. asif9t9's experience is not typical. I have used the toolbox to remove WebOS and install CM11 on several TouchPads and none are having charging problems. You can always try installing CM11 and not remove WebOS and if it works fine, then go back and run the complete data reset to remove WebOS and start over. Just remember that the best way to install CM11 using Sullin's toolbox without removing WebOS is use ACMEUninstaller2 to remove Android, boot WebOS and from settings/reset options erase the USB drive. It's important that if you have any data, backups, music, pictures etc, move them to your PC before erasing the USB drive from WebOS or running the complete data reset from TPtoolbox or they will be lost. Once you have removed Android and erased the USB drive, then follow the instructions for using the toolbox to install Android. I've done it this way and it worked great.
[TouchPad Development] jcsullins:
Why do you think it's best to use ACMEUninstaller(2) before using TPToolbox to install Android?
[TouchPad Development] nevertells2:
I am basing my suggestion based on the first sentence in post #3.

"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."

However, taking a couple of factors into consideration, one, the person wants to leave WebOS and all it's settings and current apps intact, and two, there is a pretty high chance that they are currently using an older Android Rom, ie, CM10 or older. Since using a "Complete Data Reset" is not an option in this case, as it wipes out all of WebOS' current settings and apps, to get a " reliable start fresh" condition, the user needs to use ACMEUninstaller2 to remove the old version of Android and reset the volumes in preparation for your toolbox set the proper volume sizes and install CM11.

If what I am saying is not the case and "Install Android" is doing some additional housekeeping that is not explained in the OP posts, then using ACMEInstaller2 to remove Android and reset the volumes might not be necessary to obtain that " reliable start fresh" condition.

Am I correct in suggesting the user protect all their data, files, backups and such by copying them off to their PC and then erasing the SD card/USB drive from WebOS? Or does your toolbox somehow handle moving everything except WebOS files over to the internal SD card in the process of switching all but the 600mb that gets left in the media volume? I remember a user posting that he used "install Android" without doing anything about the previous Rom(CM10) or what files were still in the media volume and toolbox took upwards of 40 minutes to finish. Afterwards, he had a long list of issues with the CM11 install as well as WebOS warnings about free space. I've never had the toolbox take more than 10 to 15 minutes by my cleaning up the media volume/USB drive in WebOS first.

I've used your toolbox both ways, complete data reset and leaving WebOS installed, but when leaving WebOS installed, I've always uninstalled Android with ACMEUninstaller2 and erased the USB drive in WebOS and never had a single issue. Just trying to be helpful and suggest for those who want to keep WebOS installed for one reason or another, the least problematic install as possible.

And BTW, I have used your toolbox to install a legacy Rom(CM10.1) and it worked perfectly. This was on a TouchPad that had WebOS removed and it was cool to see all that extra room in /data on a non-data/media install.

NT
[TouchPad Development] synchron50:
That user is me and, true, the media volume resizing did take like 40 minutes, however, TPToolbox kind of warns you that particular step may take a long time. I believe my WebOS (including apps and shared media) was somewhere around 6G of data. There also seemed to be some wasted data space (a few Gigs worth) where ESFileExplorer was showing me remnants of CM10 data also on the media legacy partition sdcard1. The real data is on the data partition sdcard0 that was restored once CM11 was installed.

And after a few days, I made my own choice to start fresh and use TPToolbox with a complete data reset. Much cleaner and I gained a good 3-4 Gigs of space. This data/media structure just doesn't sit well with WebOS because more storage space is wasted since media files can't be shared across the 2 OS's anymore. Anyway, this is just my personal choice.

If TPToolbox was written to be a complete replacement for ACMEInstaller/ACMEUninstaller, then maybe it could use a little tweaking for those who want WebOS to still be around.
[TouchPad Development] nevertells2:
What you say then supports my suggestion that when one is not going to remove WebOS, uninstalling Android and erasing the USB drive/SD card via WebOS reset options probably should be the method used before using TPtoolbox to install CM11. Knowing about your experience should help others avoid the same difficulties you had. Thanks :good:

NT
[TouchPad Development] synchron50:
Well, I'm not quite sure if having to erase the SD card in WebOS is absolutely necessary. But yes, I would agree that if one chooses to just install Android and keep WebOS, some internal operation should do something like ACMEUninstaller and remove any old Android remnants before creating new volumes in preparation for CM11 data/media build.
[TouchPad Development] garux:
jcsullins, may I please ask which GAPPS you use with CM11?
[TouchPad Development] gyro_platter:
It's in the first post of his CM11 thread, http://xdaforums.com/showthread.php?t=2712680

gapps-kk-20140105-signed.zip Standard Gapps

pa_gapps-modular-mini-4.4.2 Paranoid Android Gapps
[TouchPad Development] nevertells2:
Actually, garux's question was what version of Gapps J.C. Sullins uses with CM11, not what versions his toolbox supports. I even saw a post by a fellow who was trying to install an unsupported Gapps and got it to work by renaming the unsupported version file name to one that toolbox supports. He said after install, Gapps worked fine.
[TouchPad Development] garux:
Thanks, Nevertells2, that's the question I was asking.
[TouchPad Development] theechap:
This may be a dumb question but why not have the toolbox expand the boot partition a little bit so that it can safely copy itself there without running out of room? It would be great having this live on the TP just like recovery.
[TouchPad Development] sstar:
jcsullins said quite a while ago that he was going to post an update over the weekend but after asking about a fortnight later if when or if it had been posted I was shot down in flames with the usual "Two weeks" answer.

JCSullins did not provide any further answer or update.

But I would agree that it would be useful not to always have access to a pc.
[TouchPad Development] nevertells2:
[MENTION=4580982]sstar[/MENTION], you must not be visiting or reading this thread often enough. Try checking post #175.

And as for the "two weeks" answer, that has been an ongoing inside joke here for as long as I can remember. It used to be people were chastised for asking for an ETA. Now they are just given the old "two weeks answer" in jest.
[TouchPad Development] sstar:
I was referring to post 92 on the 29th of may. I'm not aware of the update being posted but I may have missed it, I'm sure you will let me know if I have.
[TouchPad Development] nevertells2:
Then you must have missed post #181 too. See post #184 for john's reply. Syncron50 tried what johnsmith suggested and it worked. Have a read and you will see what I'm talking about.

Your no PC prayer has been answered, at least temporarily. :)
[TouchPad Development] Capt.Insano:
Thank you!

I am away travelling and needed to reflash A6 firmware to stop battery drain.

Just download tptoolbox.bin, renamed it to uImage.TPtoolbox and copied it to /boot with esFileExplorer.

Worked like a treat: after reboot I choose TPtoolbox from moboot and reflashed A6 firmware successfully!

Thanks all, especially jcsullins!

The.Capt
[TouchPad Development] sstar:
Thanks, I did miss it.

TP Toolbox now renamed and moved to boot folder. A6 firmware now flashed without using a pc.

☺
[TouchPad Development] nevertells2:
Yeah!!!!!! :D (BSEG)
[TouchPad Development] the fat kid:
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.
[TouchPad Development] jerryatherton:
Use one of the recoveries in the op. You can flash the selinux recovery later.
[TouchPad Development] shar88:
download one of the three supported recoveries in post #3
[TouchPad Development] the fat kid:
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.
[TouchPad Development] jerryatherton:
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.
[TouchPad Development] emo72:
thanks mr sullins. i cant believe my tp is running 4.4.4 in 2014:good:

it worked so easy. the guys a legend.
[TouchPad Development] clutterking:
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.
[TouchPad Development] Moody66:
You can't . Probably with evervolv NON data/media ROM you can.
[TouchPad Development] gradular:
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.
[TouchPad Development] Moody66:
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........
[TouchPad Development] clutterking:
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?
[TouchPad Development] XeKToReX:
This is a fantastic example of what can come from XDA. Excellent work JC!
[TouchPad Development] Moody66:
As i stated earlier. Not using that rom. Pac Is basicly a Modified version of Milaq's CM11.
[TouchPad Development] firepower9966:
Open webOS (luneOS) is now available for the Touchpad, is it possible to add to touchpad toolbox the ability to create an ext3fs lvm partition of at least 1GB. I sure many here would like test it :)

http://webos-ports.org/wiki/Tenderloin_Info

http://webos-ports.org/wiki/Install_WOP_for_Tenderloin
[TouchPad Development] nevertells2:
Why not just use Tailor as suggested in the second link you posted?
[TouchPad Development] firepower9966:
Because I have formatted as Datamedia and only have android kitkat installed. I have no webOS to run tailor.

I would prefer not to have to reinstall webOS, as i dont plan to use it anymore, but would like to try out luneOS.
[TouchPad Development] vik5:
Can we mount
[TouchPad Development] dariuus:
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
[TouchPad Development] sstar:
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..
[TouchPad Development] nevertells2:
Be sure to tell him what to name it so it will work.:laugh:
[TouchPad Development] a in yul:
this is really interesting, how do we go about doing that? and what do we name it?

thks
[TouchPad Development] sstar:
This is what you need to rename it to (uImage.TPtoolbox) without the brackets.

It's in the zip file which you need to unzip and you should be able to figure out which one it is, its called toolbox something. bin and it's the only one that is around 12mb in size.

It takes a few minutes to do the job but will say when it's finished /done running the firmware.

PS you will need to use an app with root privileges such as Rom Toolbox lite to paste it into the boot folder.

Have fun.
[TouchPad Development] cdmcfud:
I tried that and it did nothing. Is there a particular file in boot I should have put it in? Can anyone give more details?
[TouchPad Development] sstar:
OK here is what I did with Rom Toolbox available on play store after unzipping and renaming the the the correct file I then copied it and then opened the boot folder and pasted it. It is possible that you did not rename it correctly, please refer to my previous post and copy what I said to rename it to. If you have further problems pm me and I will Skype you through it.

All the best.

I have now attached a big picture of my boot folder hopefully that will help, but I'm British so therefore at the office (Pub).
[TouchPad Development] johnsmith33584:
Sstar is correct in everything he has posted. You have to use a file browser that has root permissions such as he suggests, Rom Toolbox Lite, to copy and paste the renamed file into the boot folder. And no, you don't put uImage.toolbox anywhere except in the boot folder itself. You have to be exact in the spelling of the name, uImage.TPtoolbox. That's u(uppercase(i)mage.TPtoolbox, uImage.toolbox. People mistake the uppercase i for a lower case L.
[TouchPad Development] shumash:
You can actually name it anything you want as long as you prefix it with uImage.xxxxx (and uImage has to be exact and no spaces in the suffix xxxxx)
[TouchPad Development] cdmcfud:
Thanks I had an L instead of a uppercase I. I changed that and it worked perfect.

I expected it to be harder.
[TouchPad Development] sstar:
You are more than welcome, I'm glad you've got it sorted. Now the fun begins. ☺?
[TouchPad Development] gtallmadge:
Thank you for the walk through on how to do this. Just flashed the A6 firmware without issue. This is great!
[TouchPad Development] FishDoc:
I can't believe I'm having problems with something this straight forward. But I am and it's driving me nuts. I followed the instructions carefully and each time I start to paste the file into boot it copies about half the file and then I get an error message that the process has failed. The uIimage.TPtoolbox file is sitting there showing a bit over 7 mb. I delete and repeat with the same results. Any thoughts? Thanks

FishDoc
[TouchPad Development] shumash:
If you actually spelled it this way (uIimage.TPtoolbox), that's one of your problems. It should be uImage.TPToolbox. Are you sure you've given root privileges to your filemanager?
[TouchPad Development] FishDoc:
Sorry, it was a misspelled in the message, I had it correct on the try and yes I had given root privileges to the file manager. I've repeated the process from downloading the original to the final paste process and still the same result. Thanks for your reply but I'm giving up for now--
[TouchPad Development] sstar:
Hopefully I've attached a screen shot of my boot folder but if not the size of of the file you have renamed to read uImage.??? (the second letter is an upper case i everything else is lower case) is 12.17mb. So probably it may have been a corrupted DL or whatever you used to unzip it did not work correctly.

Come back if this hasn't helped.

Have fun.
[TouchPad Development] nevertells2:
Let's clarify a few things here. You used touchpad toolbox to remove webos using the complete data reset? You have verified that you have sufficient room in your boot partition or folder do actually copy and paste the renamed file? You have only renamed the .bin file to you uImage.TPtoolbox?
[TouchPad Development] FishDoc:
Yes to all the above. Strange thing, I have two TPs (one is my wife's). Both handled the same over the years. Both updated using TPtoolbox. Hers worked like a charm, mine refused. Finally went back to square one, data reset, resized volumes, reinstalled ROM, and now mine also works. Go figure. But thanks for your input. I'll never know where the glitch was but at least it's fixed.

FishDoc
[TouchPad Development] mistermojorizin:
Can I use tptoolbox to increase the size of the /data partition in a cm10.1 based rom so as to have more room for apps?

If so, is there a guide or video I could follow to do that so I know what to expect and don't mess something up?

thank you
[TouchPad Development] nevertells2:
I see no reason why you could not use TPtoolbox to do that. However, from my past experience with using J.C. Sullins flashable zips that increased /data, there was an issue with using his zip and there may be the same issue with using TPtoolbox. It has to do with long standing installs vs. a new install. The only way the zips would work reliability was when they were used on a new/fresh install of Android. The only thing that would happen on an old install is the flash would fail to increase /data. No harm was done. So I would say try the feature of the toolbox to increase /data and the worst that could happen is it won't do it.

As far as I know, there are no videos available about using that feature. It's not hard to use. The only thing you have to remember is you have to deduct the amount of memory from the /media volume first and then add it to /data. I did this the other day and it took me a couple of tries to figure it out. But once I did, it worked quickly and smoothly.

Basically, the steps are:

1. Get TPtoolbox running on your TP.

2. Select the "Resize Android Volumes" option

3. Follow the steps to subtract one of the available amounts from the /media volume, which then becomes unallocated memory. I used the

- 4096 amount.

4. Follow the steps to add the amount you deducted from the /media volume to the /data volume. One note of caution, you must have the

amount of memory free in the media volume that you want to move, or it won't work.

That's it. If TPtoolbox cannot complete the resize because of what I mentioned above in the first paragraph, it will tell you it cannot do what you ask. Then the only way around that would be to make a nandroid backup of your current setup, run ACMEuninstaller2 and then reinstall CM10.1 either the old fashioned way or follow the instructions to use TPtoolbox to install CM10.1. Immediately after installing CM10.1, use TPtoolbox to increase the /data volume and then restore your nandroid backup.

A note here, you have to decide if you want to keep WebOS or remove it using the "complete data reset" option. If you opt for the "CDR", you incur a whole other set of issues. For simplicity sake, I would keep WebOS for now and use the old fashioned method if needed. Hopefully, TPtoolbox will move the amount of memory you want without a problem.

NT
[TouchPad Development] mistermojorizin:
This worked perfectly! Didn't have to reinstall or restore android! I had a harder time copying my nandroid to my PC than doing these steps. Took about 10 minutes and rebooted back into my android after.
[TouchPad Development] nevertells2:
Good to know that you did not run into the issue of having to do the memory resize after a clean install. Hope it's that way for all that use TPtoolbox to make a volume size change.
[TouchPad Development] rjpear:
UM....Perfect..

Been doing roms on tablets and phones since Droid 1..and may i say this is the best setup/program/ essentially auto installer i have ever used. This needs to be an example for all the other devices out there and strive to achieve this level of competence and ease. Kudos fine sir!

:good: