yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] jasonsf:
Yeah, I should do that. But the button is broken because I took the TP apart once before and wasn't careful. It might simply be a connection that isn't seated all the way, but the volume buttons work and I think those are part of the same assembly. But as long as Android boots and powering it on triggers booting, I'm ok. Shutdown does require root, which is kind of ironic.

Jason
[TouchPad Development] nevertells2:
Well then the question of the day is why would you want to put WebOS back on it? WebOS is dead, support is gone! You did not explain, but I'm guessing you had already taken the web is off of it, correct? So why are you putting it back on?

NT
[TouchPad Development] jasonsf:
I misunderstood the instructions and thought it was a required step to getting back from a clean wipe. Now that I can get into recovery I've installed android and won't look back.
[TouchPad Development] JustMeToo:
I used this tool and erased the WebOS and installed a Lollipop ROM. Now when I go to WebOS Recovery, when I see the big USB symbol my computer doesn't recognize my tablet. I can connect the tablet to the computer when I'm in the ROM but not in the recovery
[TouchPad Development] vik5:
Make sure you have novacom driver installed
[TouchPad Development] nevertells2:
How did he use Touchpad Toolbox to install Lollipop without novacom installed on his PC?

NT
[TouchPad Development] an-cic:
hi, i have a problem reinstalling webos. i follow the post #64 instruction but when i try to start the system, after i choose the language and i set the wifi password, a box appear and he say to vistit the hp webos support page and resend me to the choice language screen. how can i solve the problem?

thanks
[TouchPad Development] curtisimo:
Is there a fix for the gapps .zip being unsupported/unrecognized by TPtoolbox v42? I'm using ev_tenderloin-5.1.1-testing-2015.08.15 and FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14 but none of the gapps packages linked in post #1 by flintman work. I've seen a newer version of TPTools (215-02-25) mentioned but I don't see that anywhere for download.
[TouchPad Development] curtisimo:
I tried to do this with the latest Evervolv but TPTools tells me the ROM is unrecognized/unsupported.
[TouchPad Development] nevertells2:
Why are you trying to reinstall WebOS? It's a dead operating system on the TouchPad. Otherwise, Mr. Sullins is going to have to explain to you how to overcome your problem.

NT

---------- Post added at 07:07 PM ---------- Previous post was at 06:58 PM ----------

Best I remember, TPTB will install Evervolv 5.0 and it's gapps. Once you get that installed, then you can just use recovery to flash the newer Rom and gapps. If for some reason that does not work, you can get an older Kitkat Evervolv data media Rom installed and as long as you wipe system you should be able to install Lollipop through recovery. You may have to use TPTB to increase the size of /system to 800mb. I think the requirement for KitKat was 600mb.

NT
[TouchPad Development] curtisimo:
Thank you for the information. I'll give this a try tonight.
[TouchPad Development] EnderIII:
Hello Everyone,

I am tryimg to install Andriod, but have come across a problem.

When the media volume is mounted, windows first gives me a 'No disk in device' error, and then asks me to format it. I can't get it actually mounted in windows.

Anyone know how to fix this?
[TouchPad Development] nevertells2:
First off, DO NOT format your TouchPad using Windows. Have you read through this entire thread? I'm pretty sure that problem has been discussed before. Configure a different PC and try it on that one. What version of Windows is giving you this problem. I have one of my Windows 7 PC's that flat refuses to recognize my TouchPad. All the others work fine. I know I've read of this problem being discussed and solved. Put Google to work and use the search functions of XDA and Rootswiki to look for the discussion. I seem to remember something about having to reinstall USB or MTP drivers. Have you started over with TPTB, complete data reset, etc? It's been a long time since I read about this issue, but the solution is out there.

NT
[TouchPad Development] EnderIII:
I had not, I just finished reading it. I tried 3 different PCs, same issue. I can&t even get it to mount in webOS anymore.

I am trying to rerun this toolbox, because my last android flash bonked my android install.

The search function on XDA is broken. T.T

A similar issue was discussed in this thread. But for those people, it seems the device wasnt recognized at all. Mine recognizes it, but thinks the file system is corrupt.

I tried the numerous mentioned fixes anyway (reinstalling usb, trying different cables, etc.) but nothing seems to work.

It seems like that will be what I have to do. I didn't wanna wipe my webOS isntall but I guess it doesn't matter since I never use it anyway.
[TouchPad Development] nevertells2:
why do you want to keep WebOS? It has been abandoned by HP. All the servers are down. Being able to remove WebOS and have all the memory on the TouchPad available to Android has been the holy grail for years. I like you had not used it in years when TouchPad Toolbox came along. Hope you get this solved. I've pretty much run out of suggestions. I seem to remember back in the day, when there was USB connection issues, making sure WebOS was in developer mode was suggested. But with WebOS removed, that is not an option.

TouchPad Toolbox is run from your PC with the TP in WebOS recovery mode, reboot, and hold volume up until you see the large USB symbol. There is a way to run it from the TouchPad, but that can't be done until you have Android installed and running correctly. If you can't get connected in WebOS recovery mode, then you have a more serious problem.

Good luck, NT
[TouchPad Development] EnderIII:
My first smartphone was webOS and I loved the thing, just sentimental attachment I guess.

The full wipe did work however. Thank you for the assistance.

Other then some minor space hiccups with gapps, I had no problems getting Android installed. Works pretty well except for Plex being unable to run videos.
[TouchPad Development] poken1151:
Did yopu ever solve this? I'm stuck with a similar problem. No GApps I seem to use are being recognized...
[TouchPad Development] nevertells2:
Did you try everything I suggested to Curtisimo?

NT
[TouchPad Development] tribecca:
I get the same error.

unable to set superblock flags on /dev/store/cm-cache

-fp detected error on fs on vol cm-cache rc=8

help file "confirm_repair_bad" is missing
[TouchPad Development] nevertells2:
Besides the fact that fouad796 's post is over a year old and

I have not seen anyone else comment on this issue, I would say both

of you suffer from some type of device corruption. If you have not

seen Mr. Sullins comment on this, then I would suspect that you are

out of luck.

NT
[TouchPad Development] lepa71:
Can I use this toolbox to resize system partition without re-installing ROM? Thanks
[TouchPad Development] nevertells2:
Yes. Just remember you must borrow the amount of ram you want first from /data, then add it to /system. How much do you already have allocated to /system? I believe that TPTB normally allocates 600mb for a KK install. It's recommended to increase that to 800mb for LL. With WebOS removed, I was feeling generous and increased my /system to 1 gig, but that's not necessary. Just did it because I could. TPTB shows I have 488mb of that used.

NT
[TouchPad Development] lepa71:
Here is my situation. I have 32gb version with WebOS intact and 20gb free in data. I'm running Jcsullins 10.1 because I use camera for skype. I started getting 'Insufficient Storage Available' while updating some apps(like google, gmail etc...). I believe you are right and I only have 600mb.

I was thinking that I can remove WebOS completely and as needed would borrow space from data and make it a 1gb.

Q.

1. How do I remove WebOS without full reset?

2. How much space will I get from removing WebOS?

3. How much do I need to reduce data partition to?

Thanks
[TouchPad Development] nevertells2:
You are not going to remove WebOS without doing a complete data reset. Removing WebOS frees up 4 to 5 gigs of memory.

Here is what I would do in your situation, make a nandroid backup and save a copy of it on your PC. Do the complete data reset with TPTB. Then use TPTB to install Sullin's CM10.1 and it's Gapps. Make a nandroid backup of that install and then copy the backup you made earlier from your PC into the folder where the back up you just made is. Now do a restore of that backup and you should be right back where you were sans WebOS.

This should clear up the 'Insufficient Storage Available' problem. I don't remember exactly how much memory TPTB allots to /system when installing CM10.1, but I believe the 600mb you have now will be the norm. With CM10.1 installed, 600 should be plenty. You can use TPTB to check how much of your memory is allotted to /system by running TPTB and then run "resize Android volumes". That will tell you how much memory is allotted to each volume in the Android install. /system will show how much is allotted and how much of that is actually used. Remember, i told you in my last post I had 488mb out of one gig used and that is with KitKat installed. CM10.1 should use even less. If you are intent on increasing /system memory, I would add 200mb for a total of 800mb. So you would remove 200mb from /data and then add it to /system. BTW, just to be sure we are on the same page, Sullin's CM10.1 is a data media build, right? It's been so long since I have had that old of a version of Android installed, I don't remember. I installed his first version of CM11 right after it was released back in May, 2014.

NT
[TouchPad Development] lepa71:
I don't think TP has 4 or 5 gigs of memory. I think you mean storage, but that's ok. I already resized with TPTB. I was just hopping I can delete partitions that being used by WebOS and re-allocate storage to other partitions.

Thanks anyway.
[TouchPad Development] nevertells2:
Memory, ram, storage, I use all three interchangeably. Your TP has 32 gigs of storage of which all of it is used for a variety of purposes. WebOS takes around 5 gigs leaving between 26 and 27 gigs for internal storage, Android if you have it installed and the like. By removing WebOS frees up the 5 gigs it was using. TPTB does keep about 800mb for the /media volume because it needs it to be able to do what it does. A clean install of a data media Rom will leave around 26.5GB of storage for the internal SD card and all other internal functions share that 26.5 gigs of storage with the internal SD card. Non-data media Roms were given 1.48 gigs of internal storage and the rest was used by the /media volume primarily for the SD card. Now that all storage is internal, all the issues that came with non-data media Roms are gone. The only partition ( J.C. Sullins says they should be called volumes) you should be concerned with is /system. The newer versions of Android need around 800mb of storage. You can make it bigger if you want. But if you checked it with TPTB like I suggested, you will see 800 is more than sufficient. All other volumes created by TPTB are correctly sized and do not need to be changed.

NT
[TouchPad Development] mschumacher69:
While "Memory" can be used interchangeably with RAM and Storage, you cannot use RAM and Storage interchangeably. RAM is the volatile memory of a computing device where the OS and apps run. Storage is the non-volatile flash memory that stores your data which includes the OS files, app files and personal files.

The TP has 32 GB of flash memory (storage) and 1 GB of RAM.
[TouchPad Development] nevertells2:
I believe in the case of the TP, the entire 32 GB of flash memory is used to provide for all functions of storage, memory, or ram, whichever you wish to call it. The TP originally came with 1.48GB of ram. Mr. Sullins figured out how to increase that thus reducing the amount available to the /media volume and other uses. Now with data media Roms, all memory except a small amount needed for the /media volume and the android operating system is dedicated to internal storage/memory which is used by the SD card where before internal memory was the 1.48GB internal storage and the rest went to the /media volume for the SD.

NT
[TouchPad Development] googlephone:
Google what ram is. Random access memory. TP has 1GB ram, no one can change it without open it and solder another ram. He already explained it to you and you just need to believe what he said, or if not just Google it and find your answer.

Memory includes storage, and ram.Storage is totally different from ram. Ram and storage are physically separated hardware. Storage can have several partitions or volumes, such as data, media, system partitions and you can adjust the sizes between them. The 1.48g "ram" you are talking about is actually the data partition of storage.

Ram will lose whatever stored on it once the power is shutdown, while for storage, the data saved on storage would be intact after the power is shutdown.

There is another term called "virtual ram" or "swap", which is actually storage, but is used to emulate the functions of RAM. You can create a virtual ram if you are short of actual ram, but it's still inferior to actual ram. Search ram expander in Google play store and there are lots of apps doing this.
[TouchPad Development] mschumacher69:
No offence but you've got it all wrong I'm afraid... All computing devices (TP or otherwise) have to have a volatile non-flash memory (RAM) that cannot be part of the non-volatile flash memory Secondary Storage, they are 2 different things and cannot be part of the same "memory".

[MENTION=2724524]googlephone[/MENTION] up there has explained it well, the TP only has 1 GB of RAM (Primary Storage) used to "run" the data, this is different from the 32 GB Secondary Storage used to "store" the data, period.

More in depth details on the difference between Primary Storage (RAM) and Secondary Storage:

https://en.wikipedia.org/wiki/Computer_data_storage#Primary_storage
[TouchPad Development] nevertells2:
Are you familiar with J.C. Sullin's scirpts that allowed you to expand the memory used for running data to pretty much any size you wanted. This came about because people were running into the 50 app limit when offloading apps to the SD card on the /media volume.

I'll take you at your word

that there is a little 1 gig ram chip in there, but it sure does not make sense. This is part of what Sullins said in that thread:

"The other fixes are not true fixes, but work-arounds for the 50+

apps on sdcard issue. One of them allows you to increase the size

of your 'Internal storage' so you do not have to move apps to the

'sdcard'. The other allows you to move these apps back to the

'Internal storage' after you have encountered the 50+ issue."

My thinking is he was referring to 1 gig or so that you are speaking of.

Back when we first started installing Android on the TP, going to settings/storage/ reported 1.48gb of available internal storage. With his scripts, you could pretty much increase that figure to anything you wanted which eliminated the need to move installed apps to the SD card. You may remember when you hit the 50 app limit, the SD card would become unmounted. Now correct if I am wrong, when you install an app, the code for that app is placed in that 1 gig of ram you are talking about. Download enough apps and you run out of ram. Solution, move apps to the SD card. Except on the TP, the /media volume SD card and internal memory reached some sort of conflict when you moved too many apps(50) to the SD card. But now that the SD card and the internal memory share the same space, and internal memory is now 26.5GB(data media Roms) in size so you don't have to move apps to the SD card, so no 50 app limit. If you are a real app hog and love to install every app you can think of, more internal memory is used and less becomes available to the SD card. I know, I'm probably way out in left field. From now on, I'll just not comment on memory/storage/ram posts. Thanks

NT
[TouchPad Development] googlephone:
Whatever you are talking about in your lengthy words above has nothing to do with ram. What you are talking about is actually the data partition of storage.

Apps are not installed into the ram, but to some part of storage. Ram is used only when you are running the apps.

You can see the ram usage by going to Apps -->running tab, you can see how much ram used and how much ram is free. You can see the ram used and free ram are changing but the total is fixed at around 800MB. Out of the 1GB ram, only 800MB is available for apps and the left are reserved for some drivers or hardwares such as modem or GPU.
[TouchPad Development] mschumacher69:
You're totally wrong, no offence again but you actually don't know what you're talking about...

As [MENTION=2724524]googlephone[/MENTION] said, the 1.48 GB of internal storage that you're talking about is the data partition, it has nothing to do with RAM, you actually can't have partitions on RAM. RAM is just a volatile (temporary) memory used to run (not store) data.

Yes I'm aware of [MENTION=2763462]jcsullins[/MENTION]' scripts to expand storage, those options are actually still available in his toolbox, but again, this allows you to re-size the storage volumes and has nothing to do with RAM. He definitely wasn't referring to RAM. Again, you cannot create partitions/volumes on RAM, let alone expand them. The amount of RAM is preset by the RAM chip that's installed on your device and cannot be expanded/reduced unless you physically change the chip which is of course only possible on PCs and Laptops.

Now to correct you, when you install an app, the apk for this app is stored on the data partition which is on Storage not in RAM. The OS is also installed on Storage on the system partition. When you first boot your device, all the OS data needed to operate your device is loaded from the system partition to RAM and your device would be operating out of RAM. Same with apps, when you run an app, it is loaded from the data partition to RAM and it would run out of RAM. Now all data in RAM is temporary and because it's limited to 1-3 GB on mobile devices, it needs to be managed and this is where Android memory management comes into place. If you run too many apps at the same time, your RAM would fill and in order to be able to run more apps, Android memory management terminates one of the background apps that you're not using to free up some space in RAM for the new app to run. That's why if an app or the OS has memory leaks, it means it is filling your RAM with unwanted data, that's why your device would run slowly because Android would constantly need to free up space in RAM for your apps to run.

As [MENTION=2724524]googlephone[/MENTION] mentioned, you can checkout the amount of RAM available for your device by going to Settings > Apps > Swipe to RUNNING. You'll see that the total amount of RAM available on the TP is around 800 MB regardless of the size of your data partition. This 800 MB is part of the 1 GB RAM chip installed on the TP, not the 32 GB flash memory that's in there. This screen also shows you how much each running app is taking and how much free RAM is available. An app needs to be running to take up space in RAM, it wouldn't take up space in RAM if it's just installed and not running.
[TouchPad Development] nevertells2:
OK, you guys have had enough fun beating me up. I actually do know what I am talking about, just somewhere along the way got the idea that HP had done something different with the TouchPad. I had never noticed in settings/apps/running that at the bottom was a realtime report of how much of the TouchPad's one gig of RAM was used and available. I'm all straight now, thank you very much! :p

NT
[TouchPad Development] GiSS88:
Also having issues, not recognizing Gapps from evervolv ROM.
[TouchPad Development] nevertells2:
It's already been mentioned more than once, TPTB v42 does not like Roms past CM11. Please read Evervolv's

thread throughtly on how to work around that or here: http://rootzwiki.com/topic/3784025-new-jc-sullins-kitkat-build-uploaded-today/

I know it's about Sullin's CM12.1, but the concept works the same for Evervolv.

NT

---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------

Obviously by the 216 downloads from Sullin's Android Host File account, someone is interested and using his CM12.1 Except for a couple of guys who posted in a thread I started over on RootzWiKi, no one is talking about how they like it or problems they are having with it. So I am inviting those of you who are trying it out to visit this thread and tell us about your experience and ask questions if you are having problems. http://rootzwiki.com/topic/3784025-new-jc-sullins-kitkat-build-uploaded-today/

Guess we can call it the official unofficial Sullin's CM12.1 thread. :p At least one guy figured out how to get it installed since TouchPad Toolbox is not CM12.1 friendly. See you over there!!!!

NT
[TouchPad Development] garux:
I was able to use HP Toolbox v42 using the following Rom, Gapps & CWM without any problems:

update-CWM-jcs-dm-tenderloin-20150703.zip

cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip

gapps-511-base-20151114-1-signed.zip

I have Bluetooth working with Keyboard, Mouse & Headset. Still checking CM12.1 out. Taking some getting use to using.
[TouchPad Development] jcsullins:
Since TPTB v42 was released, the groups releasing GAPPs packages (or most of them, at least) have stopped including the file inside the GAPPs package that TPTB v42 uses to identify what version of Android the GAPPs package is compatible with.

I have been able to come up with a more reliable method to determine the GAPPs version information (it does not rely on a file included by the GAPPs packagers, but looks inside the APKs from Google instead) that will be used in the next TPTB release.

Sadly, I've been very frustrated by the number of posts on these forums that contradict and/or misdirect people from the documentation that I provide for TPTB. I don't feel comfortable releasing a new version of TPTB under these conditions.

For now, you should be able to use one of the base GAPPs packages from this thread:

http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[TouchPad Development] johnsmith33584:
Thanks for clarifying the situation about how v42 works and that it's the gapps packages causing the problem. I have one question, in the evervolv LL thread, it seems to be the consensus that TWRP should be used to flash LL builds. I feel from what you are saying here and in your OP that any DM compatible recovery will handle installing any LL build. One should just be sure he uses one of the gapps that you recommend. Thanks
[TouchPad Development] GiSS88:
Seems the link you gave me works, thank you for that! Shame that there is misdirection on the forums. I also find it silly that the dev who made the Evervolv ROM suggests a specific installation, then links files that won't work with that installation method. Silly.
[TouchPad Development] garux:
Thanks for the explanation. I've installed your CM12.1 via TPTB v42. Thanks So Much for the work you do putting this all together for us.
[TouchPad Development] shumash:
I would be very saddened if users who greatly appreciate and need the tools you develop would be deprived of them because I mistakenly directed help requests to some other thread. If you post a new version and require that any requests for help be directly linked to your documentation, I would certainly abide by your wishes. I can't speak for others, but I expect they would also agree. I suspect that your thread could be sticky'd if you so requested.