yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] skitty:
Can you add support for 4.4.3 gapps packages please? I know I can rename them, but some people might forget.
[TouchPad Development] anonxlg:
thanks, i have a recent backup of cm9 and updated to 4.2, i should just jump straight into 4.4 after learning about this

the only difference is, i'm using TWRP, is there any way of using the toolbox but keep TWRP and moboot? would there be any problems if i used a TWRP backup on CWM?
[TouchPad Development] johnsmith33584:
First off, TWRP and CWM backups are not compatible, so please do not try you you are asking.

Since the touch version of CWM was created, I prefer that over TWRP. Mr. Sullins says in post three that TWRP is one of the compatible files you can use. You might want to read through his instructions again before trying anything.
[TouchPad Development] anonxlg:
yes, i figured, i remember reading that it was incompatible, wasn't sure if anything changed

i updated from an old build of TWRP (i think it was either 2.0.x.x or 2.2.x.x) and I dont remember if I used which to backup with, is there backwards compatibility there, i'm running 2.6.3.0 right now (pretty sure i updated TWRP before doing a backup)

and i'm not even sure if i'm using the same version of TWRP as the one in the 3rd post (probably not)
[TouchPad Development] synchron50:
I used the 2.7 version of TWRP when going from CM10 to CM11. The only issue I had was figuring out where to restore the data from the nand backup which was on the legacy SD card. Not sure if older versions of TWRP support the new data media structure.
[TouchPad Development] johnsmith33584:
They do not.
[TouchPad Development] Ok_Kaleidoscope5109:
FYI because 4.4.3 has been merged into CM, some 4.4.2 builds are now 4.4.3 (like milaq), therefore I need to use 4.4.3 Gapps. Unfortunately, the Toolbox does not let me use 4.4.3 Gapps files, or rather it checks that the file name reads 4.4.2. I had to hack it and change the filename back to 4.4.2.

I would recommend updating the toolbox accordingly.
[TouchPad Development] theechap:
The only time I ever reflash Gapps is if I'm having issues. I had milaq's 4.4.2 build installed (with gapps) and then just upgraded to 4.4.3 on top and I haven't had any issues.
[TouchPad Development] Ok_Kaleidoscope5109:
Well I just did a brand new flash, so I wanted to use 4.4.3. It made sense given the OS is now 4.4.3.

The reason I update PA Gapps is because they are put in /system, thus making good use of extra space in the /system partition. Updates to Gapps will automatically be put in the /data partition.

This goes for any device and not TouchPad only.
[TouchPad Development] fourlans:
Can't switch off my touchpad

I used the Toolbox yesterday to remove Webos and install a clean version of JCSullins CM11 along with minimal Gapps as specified at the beginning of this thread. Today I switched on the Touchpad and then Bluetooth as I wanted to transfer a file to it from another device. Immediately after I switched on Bluetooth the Touchpad 'rebooted' and is now stuck on the Cyanogen boot screen. I've tried several combinations of keys to switch it off but to no avail.

Can anyone help ?
[TouchPad Development] chris5s:
Hold 'power' and 'home' buttons until the touchlad reboots. If it still sits on the boot screen, reboot using the two buttons and go into recovery. From there wipe cache and dalvik cache, you should be good to go…

I had this behaviour once and wiping caches got me back into the rom. However bluetooth never did work again - on that particular rom, I can't remember which one it was, but it wasn't jc's cm11 - until I installed a different rom.

Hope this helps.

Peace.
[TouchPad Development] fourlans:
I've held the home and power buttons down for over 5 minutes but nothing happens and I'm still stuck on the splash screen

---------- Post added at 06:57 PM ---------- Previous post was at 06:40 PM ----------

I've held the home and power buttons down for over 5 minutes but nothing happens and I'm still stuck on the splash screen
[TouchPad Development] chris5s:
I've never not been able to reboot using those buttons, that's strange… and more than a little annoying!

If you connect to a PC, are you able to connect via abd? Then you may be able to force it to reboot from a terminal?

Good luck!
[TouchPad Development] fourlans:
adb devices doesn't find any devices

Tried again and I'm now getting

List of devices attached

9CRHM59LH61F6GCV7DNH5CDV8H0OKR6? unauthorized

---------- Post added at 07:47 PM ---------- Previous post was at 07:04 PM ----------

I read on another forum that pressing power and tapping home 15 times gives a a low battery indicator. I tried it and the Touchpad appeared to switch off. then pressed power & home and what do you know , it booted straight into Android.

Thanks for the suggestions Chris
[TouchPad Development] laspero:
If you are getting an authorized error from ADB try updating to a new version of adb.
[TouchPad Development] johnsmith33584:
Wow, where do I start. Never try to install two recoveries at the same time no matter what installer you use. Once you have a stable running tablet, copy the recovery.uImage into the boot folder and you should see both recoveries on the Moboot menu.

I would strongly advise that you use CWM when making nandroid backups and restoring them, at least to get one made from an older version of CM restored to a newer version. Did you read my post how I did mine?

From the time I started Sullins script to use the toolbox to when I was booted to Android, about 15 minutes, so I don't know what you had going on there. Maybe because you left WebOs installed. I also recommended using ACMEInstaller2 to remove Android before trying to use the toolbox to install CM11 if you plan to leave WebOS.

I agree with you when leaving WebOS installed, there needs to be more than 600mb available to it. And you will not be able to see the SD card in the /data folder when booted to WebOS. It would have to be recoded to be able to see it.

Personally, I don't think there is anything wrong with TWRP, but since CWM now has a touch interface, I fully prefer it over TWRP.

I noticed the SU requiring permissions again for all my apps that need them after installing CM11. Minor inconvenience.

I'm not sure how you got into the situation with two SD1's created. At this point I think you are going to have to start over by running the "Complete Data Reset" and after CM11 is installed and configured, either try to restore /data only from TWRP or allow the Play Store to restore your apps and settings. You may not get everything back that way, but should get most. Just make sure the TWRP backup(data only I think you said) is saved on your PC and before trying to copy it back, make a quick backup so all the proper folders/subfolders are created. Then put the backup from your PC in the proper location under TWRP.

You also might want to have a look here: http://rootzwiki.com/topic/179730-r...oolbox-to-install-android-the-super-easy-way/

RolandDeschains79 has created a new guide on how to use the TPtoolbox. The way he explains how to use it might help you better understand the installation process. His guides are thorough, easy to follow and he almost always includes video support so you get the visual in addition the written guide. Hope you get some useful info from it.
[TouchPad Development] synchron50:
Thanks for that advice, more importantly, thanks to JCS for properly aborting the script properly for that situation.

I'm pretty familiar with TWRP, although, this latest 2.7 version does not want to mount USB like older versions. Eventually, I would like to try the newer CWM with GUI Touch.

That's just it. I wanted to just experiment with the Toolbox by leaving WebOS intact. Unfortunately this left everything on the SDCard intact and resized it to leave just around 600M free. Once a fresh copy of JCS CM11 was installed, after restoring the CM10 data many files from SDCard1 needed to be xferred over to the new SDCard to support older apps. This sought of reminds me of those days with Windows when you needed to reinstall it for some reason and wound up with a C:\Windows and a C:\Windows1 folder and a lot of redundant mess. To date, I have never used ACMEUninstaller since I became very used to using Nandroid backups and could freely go from CM9 to CM10 to CM9, etc. with no hiccups. Not so sure this can be done with CM10.2 and above due to the new partitions.

There weren't two SD1's. As expected, under root in my CM11 there's a new SDCard folder and an external_sd folder which gets auto-mounted as SDCard1 in ES File explorer and contains all of WebOS as well as Android support files (i.e. the battery_history file that the Battery monitor logs to ).

Again, as a warning to other people using the tool, be aware that you might need to spend some additional time xferring from legacy to the new SDCard partition that was created for some apps to function correctly. In my case, I still think this is better than starting out clean and reinstalling apps again from the Playstore as you lose a lot of settings in the process.

I still would like to know if this is a 2 way street and once you have CM11 can you migrate back to CM10 or earlier using the new Toolbox? Does it delete the data media partition that was created? Or are you committed to stay at CM11?
[TouchPad Development] theronkinator:
My Touchpad toolkits at 14,000+ downloads, but who's counting... :p

Seriously though, mines a glorified batch file, this toolbox has been one of the biggest developments we've had in years for the touchpad.
[TouchPad Development] johnsmith33584:
OK, the little light bulb just went on. The reason it took so long for TPtoolbox to do it's thing is it had to deal with the media partition SD card full of files. You are installing CM11 and the toolbox is having to deal with all the files on the media partition SD card. Like I said previously, use ACMEUninstaller2 to remove Android. What I forgot to say, move any files or folders you want to keep to your PC including your nandroid backups. Boot WebOS and go to settings/device info, reset options and run the erase USB drive option. Now start TPtoolbox and use "install Android". You are going to still end up with a very small amount of memory in the media partition, but I suppose you could adjust that using "Resize Android Volumes". I've never tried that tool, I have always just accepted the default.

Two way street is not what I would call it. The toolbox can install non-data/media Roms as Mr. Sullins states in the OP. But I don't believe it can reset the data/media partitions back to a non-data/media configuration. You would either have to do the full data reset again and then run the android install with the non-data/media files in the ttinstall folder. Then restore the backup of your old setup.
[TouchPad Development] theechap:
Sometimes that doesn't work for me. What always works for my TP is if I hold the power button and then press the home button on the front over and over again. Sometimes it takes only 10 presses and others more like 30, but it has never failed me. Just keep pressing home!
[TouchPad Development] synchron50:
According to JCS's instructions (post #3), it looks like I can't go back to my original 4.1.2 JB CM10.0 . Therefore, its time to finally deal with ACMEUninstaller2 but with CM11, will it really remove all of Android currently residing on both partitions and just leave the WebOS portion of SDCard1? Will it display the Moboot menu when complete? I'll also make a CM11 Nandroid backup just in case before doing the uninstall. Thanks for your valuable suggestions.
[TouchPad Development] sarahlegs:
Wow, just wow. This is an example of selfless, generous, dedicated, competent and elegant coding. Jcsullins, your work is a gift to the community and we thank you for it.

Just to help a bit, here is my brief usage report with a small possible small bug report:

Installation Experience

-I installed novacom using the java-based link provided on my Windows 7 PC with no issue.

-I rebooted my device into WebOS Recovery, no issues.

-I used the .bat Windows batch file noted to install Touchpad Toolbox, no issues.

-I fired up Touchpad Toolbox and performed a "Complete Data Reset" to be sure I wiped my device clean (I had no media or data worth backing up). No issues, worked great.

-I downloaded three files to my PC from relevant links:

1) CM11 (from invisiblek's thread)

2) GAPPS (from jcSullins post above)

3) A "datamedia" recovery (*various -- see report below)

-I initiated "Install Android" and proceeded to follow the prompts, loading the three .zip files above onto my device from my Windows PC via USB connection.

Possible Bug Report

***However, when I tried to install the TWRP version of the linked recovery, the device told me "no compatible recovery found." I tried another version of the recovery from invisiblek's thread, and still the device told me it was not compatible.

-Finally, I tried downloading and using the traditional CWM recovery listed in your post above, and that worked.

-My device rebooted, executed the flashing script and I'm now running CM11 on my Touchpad with minimal effort and a worry-free installation....THANK YOU SO MUCH!!!

As for the minor recovery bug, you may wish to edit the guide on how the TP Toolbox looks for a compatible recovery with whatever parsing you have coded, or perhaps edit the code of TP Toolbox accordingly, if this is in fact a repeatable error.

Thanks again so much and hope this brief bug report was helpful to you and others.

Cheers.
[TouchPad Development] chris5s:
+1

This was my experience too, regarding installation of recovery. Otherwise agreed, superb tool.

Peace
[TouchPad Development] fattire:
Congrats, jcsullins!

I told you this privately, jcsullins, but wanted to do so publicly as well-- this tool is absolutely

amazing

. Incredible.

ft
[TouchPad Development] anonxlg:
i used the TWRP in the post and it worked for me

i'm guessing this is not possible, but can i use the toolbox to downgrade? any way to modify the files so i can put custom sizes into the repartitions?

i want to repartition it back to cm9 sizes and do recover from a backup, cm11 is giving me too much headaches
[TouchPad Development] BIGSimon:
Yes it's possible to downgrade with the toolbox, do a complete data reset and just put a non data media version of Android in the ttinstall folder when installing Android and the toolbox will resize all the volumes accordingly
[TouchPad Development] alias4ever:
Sorry about this post. Please delete. Daughter got a hold of my phone! :D
[TouchPad Development] frumpy:
Thanks Mr Sullins. Superb tool and your behind the scenes work - both much appreciated.

I used the latest milaq CM11, PhilZ CWM and January GApps, did a full reset, re-flashed my A6 just for fun and ran the install. Ran perfectly.

:)
[TouchPad Development] simonsayz31:
Speechless...wow...Best....Tool....EVER!!! Thank you!
[TouchPad Development] anonxlg:
i'm trying to revert back from cm11 to cm9 and i'm having some problems

i used the toolbox to repartition the sizes, but i didn't exactly make the partition sizes match the old state

i reverted from twrp 2.7 back to 2.6.3.0, the version i did the backup on previously

i can't find the backups when i choose recovery, does it not allow you to recover unless the partition sizes matches whatever the backup was before? that's the only thing i can think of right now, the files are all in the right directory
[TouchPad Development] nevertells2:
Did you remove WebOS? The way I read the OP, TPtoolbox is not designed to install CM9. Sullins states that support for legacy Roms is limited. If you did not remove WebOS and just used the toolbox to install a CM11, data/media Rom, your best bet would be to run ACMEUninstaller2(which sets the partition sizes correctly) and then install CM9 the way it's always been done. Once you have it installed, make a quick backup using the same TWRP you used, 2.6.3.0, and then copy the backup you made into the proper folder in the TWRP file structure which if I remember correctly is something like TWRP/backup/00000000000 or a number other then zero's if you installed Moboot 0.3.8. Now TWRP should be able to find the backup file and restore it.

If you did remove WebOS, you are going to have to follow Sullins instructions on how to reinstall WebOS. Then install CM9 and then restore your backup the same way I suggested above.

I would strongly recommend to anyone who has not tired CM11 to not remove WebOS until you have installed and used it for a while. The best way I have seen is use ACMEUninstaller2 to remove your current Android install and then use the toolbox to just install CM11. Once you are confident you want to keep CM11 and have no use for WebOS, run the "Complete Data Reset" and reinstall CM11 and restore that backup of that installation that you made and saved on your PC, right?
[TouchPad Development] anonxlg:
ya, i didn't use toolbox to install cm9, i used to to repartition then booted into twrp to do the restore

turns out that the folder name in the twrp backup is specific, i did a backup to force the folder structure and moved the old backup into that folder

worked out at the end, back to good old cm9
[TouchPad Development] nevertells2:
Glad you got it working. What is it about CM11 you don't like that made you want to return to CM9? :(
[TouchPad Development] anonxlg:
main issue was the battery, idle battery drain was a killer

audio turns off after deep sleep, needs to restart to fix

random freezes, power/home button not responsive in waking up touchpad

less stable than cm9

bluetooth works, but sixaxis doesn't
[TouchPad Development] nevertells2:
Your's is a case where the experimental nature of CM11 if not for everyone. I have the same home button response issue, but found that just holding down the home button until the screen comes on works reliably. Hopefully that can be tweaked. My battery drain is good, -6 to -10mA. No freezes or audio issues. Wonder what would happen if you used ACMEUninstaller2 first and then installed Sullins CM11 clean would get you better performance? What kind of battery drain were you seeing? Were you measuring it with BMW?
[TouchPad Development] cdmcfud:
After first loading cm11 I had that problem, then a week later the problem just stopped. The power button works better then the home button,in fact the home button almost becomes unresponsive taking a lone time to come out of sleep.
[TouchPad Development] nevertells2:
As I have suggested previously, try holding the home button down until the screen comes on. It should come on within a second or so. Did you read my post about the suspicion I have about why using the power button to wake up the TouchPad could be detrimental?
[TouchPad Development] cdmcfud:
The screen comes on instantly when I hit the start button, I have to wait for the home screen button.

It's like it crashes for a moment when I hit the home screen button. I'm using cm11 4/9/14.

It had trouble when I first loaded coming out of sleep with the start button and had press the home. Now it's the opposite.
[TouchPad Development] sstar:
Any news on the proposed update?
[TouchPad Development] fouad796:
I was hoping this will fix the Hp touchpad with Read only problem, but unfortunately it fails.

thanks
[TouchPad Development] nevertells2:
Two weeks :D
[TouchPad Development] BIGSimon:
Lol, Come on [MENTION=4580982]sstar[/MENTION] you should know better than that.. Ha ha
[TouchPad Development] ekunagba:
Many thanks for this wonderful TP Toolbox. I have used it and it works well. My hope is that you will update it to recognise any ROM and also to be available on the touchpad without a laptop connection in the nearest future.

Aready hit thanks.
[TouchPad Development] synchron50:
On the subject of downgrading from CM11, these 2 responses seem to be contradictory. I think you can just use JCS Toolbox to wipe WebOS and still reinstall older ROMS like CM9 or CM10 in order to gain the extra space but since these ROMS are "limited", re-installation of any older non-data media ROM should be done the traditional way with cminstall folder and running ACMEInstaller. The key thing to realize is that WebOS Recovery acts as the gateway for any Android version installation and WebOS should not have to be required anymore.

I recently made a TWRP 2.7 CM11 nandroid backup. I would like to test this backup by downgrading to CM10 traditionally (ACMEUninstaller2, then ACMEInstall CM10 and restore my nandroid backup for CM10). Then use JCS Toolbox but this time I want to try the Philz/JCS CWM recovery and see if I can successfully restore the CM11 TRWP backup. (The docs say TWRP is compatible with this CWM version). Once that's done, I will eventually remove WebOS and continue to make nandroid backups from time to time using the new CWM touch interface. I'm really starting to like CM11 as I use it more and more.
[TouchPad Development] nevertells2:
Best way to prove your theory would be do a complete data reset and see how CM9 installs. Same thing goes for using a recovery that supports data/media Roms and try to use it to install or restore a non-data/media Rom, or use a data/media recovery to restore a data/media backup over the top of a non-data/media install. This toolbox is still very new and experimental and what it can or cannot do is still to be discovered. You very well may be right about installing any CM Rom with WebOS removed as long as the toolbox supports doing it. But like I mentioned, Sullins states that legacy support of limited right now, so be careful.
[TouchPad Development] synchron50:
Yes, I agree and I can be a little more daring now since I'm working with a backup TP. I am confident in what JCS says about the Complete Data Reset and that it rebuilds volume fresh with just a /media and a minimal /boot, sought of equivalent to a low level format in the PC world. This is something we never had with our Touchpads so applause, applause! Eventually, I would hope that we can just use recovery to restore CM9, CM10, CM11 but it sounds like more development work might need to be done and if one doesn't mind losing WebOS, than JCS CDR will suffice for now.
[TouchPad Development] BIGSimon:
And that is exactly what I have done, all you have to do is think about exactly what the Toolbox does, it completely wipes the Touchpad and installs moboot and whatever recovery you put in the ttinstall folder, then you can adjust the volume sizes to whatever you want using the Toolbox, and then flash any rom you want with your chosen recovery.
[TouchPad Development] johnsmith33584:
Good point. I wonder then what Sullins means in the OP about limited legacy support for now? Do you suppose if you put CWM6, CM9 and the appropriate gapps in the ttinstall folder that toolbox will not recognize the file name format and stop? If that is the case, can you put just CWM6 in the ttinstall and have the toolbox install that, then mount the media folder and copy CM9 and gapps over? Then boot to recovery and manually install them. It appears that the toolbox sets up the partitions based on the name of the Rom you are installing. Until that happens, there are no partitions created yet, right? Interesting situation! :)
[TouchPad Development] synchron50:
I am going to speculate and say that the install process will abort unless you have all 3 types of files in ttinstall: ROM, Gapps, and just one recovery. No more, no less. Once that criteria is met, all 3 files go through a zip file integrity check and if that's OK you're good to go. I think the filename format is only checked to decide whether to create the 2nd volume for Kitkat, specifically looking for tokens he mentions in Post #3. Words like "limited capability" just means that he picked some popular ROMs and tested just those. As NT mentions, it is up to us to try other ROM/gapp/recovery combinations and post the success or any anomalies.

I'm looking forward to a new moboot version that permenantly adds 'Touchpad Toolbox' as a menu selection so we don't have to do this with a PC!