Database Develop

[Q] How to Fresh install CM 10.2 on HP Touchpad

I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.

cmakar said:
I have 2 year old Touchpad that was running Android 4.2.2 and tried to update to 4.3.1 and trashed it. I was running CM 7, upgraded to 9, then 10, then 10.1. I did everything to try and salvage it and read every article possible with NO luck.
SO, I decide to use Acme Uninstaller to remove it, but had issues seeing the Partition and it wanted to FORMAT - I did NOT FORMAT because everyone said not to.
SO then I did a factory reset on the Touchpad and erased it. This worked and allowed me to try and get back to CM 10.2.
The problem is that I cannot find a single installation method that shows the simplest steps to install CM10.2 ( Android 4.3 ) without having to install older version of CM9, or CM10.
I have tried every possible article and method and so far here is what I am stuck with.
I can install CM9 with Moboot BUT CWM and TWRP will not install so I cannot update GAPS.
I erased and then tried using the TAILOR Web OS app to increase the OS partitions from 400mb to 600 mb and that installed fine.
Then I installed CM 10 using ACMEInstaller 3 and it boot loops.
Then I tried CM 10.2 using ACMEinstaller3 and it will not install and says the package is invalid.
It seems like something do to with the partitions and that is why I cannot installed CWM, TWRP or GAPS or even an update.
The only thing I have NOT done is use WEB OS Dr. because I thought this is for when WEB OS is trashed.
I know this seems like a re-post but it really isnt
IF anyone has a simple document that details exactly how a Touchpad should be correctly erased and then install a fresh CM10.2, I would really appreciated it.
There just does not seem to be any articles or you tube videos that show this processes.
I am sure there are a lot of people that would benefit from a guide for CM9, CM10 or CM.2 by doing a complete erase and start over.
I have started writing my own documents but of course I cannot finish it.
Please help and point me in the correct direction because I am stuck with only WEB OS.
Click to expand...
Click to collapse
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.

Finally have CM 10.2 / Android 4.3.1 installed
I wanted to let you know that I was FINALLY able to get a fresh install of CM 10.2 / Android 4.3.1 installed using the NEW ACMEInstaller 5 T.
I also used the ACMEUNINSTALL2 that was re-posted.
So I plan on Factory wiping my Touchpad so that I can document the process from beginning to end and if it works, then I will post my instructions.
Of course I make no guarantees like everyone else states, but I am following pieces and parts of what everyone else posts and just trying to make a simpler guide. There are lots of guides but nothing that seems to work at all for me and lots of other people are saying the same thing.
iamdestruktor said:
I too am having a confusing time with my TP. I've tried a few ROMs and I just want to basically erase everything and install a single, fresh new ROM. I haven't touched my TP in quite a while so i've forgotten all the confusing steps it took to originally root it. Some guidance would be great.
Click to expand...
Click to collapse

WebOS DEAD after Jan 15th 2015....?

Hi All,
So am I understanding this correctly, that after the 15th January 2015.... We will no longer be able to use WebOSDoctor to restore our Touchpads.....??
So should anything happen to our WebOS installation, we are screwed after this date....??
What would it be best to do in this situ...?? At the moment, I've layed off doing a Data Media partition layout, as I like the way my Tablet triple boots WebOS, Android and Ubuntu Linux. I've enjoyed all the older versions of Linux, however if I upgrade to DM, I can then enjoy all the newer Android's too...
However, I wont ever be able to go back to older Androids, and more importantly, wont ever be able to use and play around with WebOS anymore.... is that right??
There was a ported version of WebOS, that the community were building, does this work on our Tablets and would this keep working after the big switch off....??
Not sure whether to DM or not DM my Tablet now...??
Thanks, Lister

If I remember right, then you have to be able to sign into a webOS account in order to use webOS. So theoretically, using the webOS doctor may not be the greatest idea after the 15th. However, I do believe there is a way to bypass the login so you can still get into webOS after using the webOS doctor. We may have to do that from now on if we ever restore our tablets. But as long as you have android and a recovery right now, it shouldn't affect you going from different android builds.

Hi @jsgraphicart,
Thank you for your reply, and support.... Yeah, I'm not too bothered about what my account does, or whats in it... As to be honest, I never really used it when I got the Touchpad. I straight away dual booted to Android. Although now have Ubuntu Linux on it too...
However, I do still like the look of WebOS, and its nice to still have this feature/OS. As long as you can still re-install WebOS after the 15th, and still gain access to it one way or another, then I'll be happy.... I don't care much for what HP has to offer for it, as it was rarely used under WebOS. As long as there is a way to re-flash/re-install WebOS (via WebOS Doctor) and not rely on HP Servers, then all is cool with me...
I found this survival guide, which may be of use to others....
http://www.webos-internals.org/wiki/WebOS_Survival_Kit#Empty_Your_Profile
and this is what is affected come switch off...
https://developer.palm.com/content/resources/develop/faq.html
I have the WebOS Doctor files, one of the files is over 200MB, so I assume thats the full standalone OS without needing HP???
Cheers, Lister
jsgraphicart said:
If I remember right, then you have to be able to sign into a webOS account in order to use webOS. So theoretically, using the webOS doctor may not be the greatest idea after the 15th. However, I do believe there is a way to bypass the login so you can still get into webOS after using the webOS doctor. We may have to do that from now on if we ever restore our tablets. But as long as you have android and a recovery right now, it shouldn't affect you going from different android builds.
Click to expand...
Click to collapse

WebOS support Extended till March, 15, 2015
Hey guys, good news!
WebOS support has been extended till March, 15, 2015:good:
Timecode:
WebOS shutdown extended till March 15, 2015 @0:04
New TPToolbox v42 can install Android 5.0(CM12) @1:09
CyanogenMod 12 Nightlies by Invisiblek @2:14
WebOS shutdown Timeline
· 10/15/14 Announcement to users and developers COMPLETE
· 11/1/14 New app purchases end COMPLETE
· 11/10/14 App update submissions end
· 3/15/15 Public shutdown of services
WebOS Shutdown Email in full:
FAQ - webOS Shutdown
Download TPtoolbox V42 installs android 5.0, increase the system partition from 700MB to 1000MB(1GB):
[ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin)

@RolandDeschain79
Ah, thank the lord... thank god for this new bit of info.... I read last night (as completely forgot) for the first time in ages that they were shutting everything down on the 15th... and was like, cr*p... that only gives me 1x day to do everything!!!
From the link I provided, about what to do in advance about 'after the shut' I've installed Save / Restore, to backup all my Apps. And Show Properties to save my Tokens (not sure what they are for, but what the heck...).
And so I am hoping, after the dreaded shutdown, if I then choose to go to DM, then non-DM, and then DM again in the future, playing around with different Android roms, I'll still be able to re-install WebOS via WebOS Doctor....
Cheers, Lister

RolandDeschain79 said:
Hey guys, good news!
WebOS support has been extended till March, 15, 2015:good:
Timecode:
WebOS shutdown extended till March 15, 2015 @0:04
New TPToolbox v42 can install Android 5.0(CM12) @1:09
CyanogenMod 12 Nightlies by Invisiblek @2:14
WebOS shutdown Timeline
· 10/15/14 Announcement to users and developers COMPLETE
· 11/1/14 New app purchases end COMPLETE
· 11/10/14 App update submissions end
· 3/15/15 Public shutdown of services
WebOS Shutdown Email in full:
FAQ - webOS Shutdown
Download TPtoolbox V42 installs android 5.0, increase the system partition from 700MB to 1000MB(1GB):
[ROM][UNOFFICIAL][5.0.2][3.4 Kernel] CyanogenMod 12.0 Nightlies (tenderloin)
Click to expand...
Click to collapse
Thanks for the update. I just bought a Nexus 10 so I may do one last webOS doctor and clean everything up and re-install a fresh version of Android. By the way, has there been any news on that LunaOS that the developers started doing? I haven't heard anything about it.

Lister Of Smeg said:
@RolandDeschain79
Ah, thank the lord... thank god for this new bit of info.... I read last night (as completely forgot) for the first time in ages that they were shutting everything down on the 15th... and was like, cr*p... that only gives me 1x day to do everything!!!
From the link I provided, about what to do in advance about 'after the shut' I've installed Save / Restore, to backup all my Apps. And Show Properties to save my Tokens (not sure what they are for, but what the heck...).
And so I am hoping, after the dreaded shutdown, if I then choose to go to DM, then non-DM, and then DM again in the future, playing around with different Android roms, I'll still be able to re-install WebOS via WebOS Doctor...
Cheers, Lister
Click to expand...
Click to collapse
Actually after the date you won't be able to reinsatll with the doctor due to not being able to active the device. So if you'd like to run the doctor I'd do it before March, 15, 2015, like jsgraphicar but not after I'd stick to the DM roms at this point, there isn't anymore non DM development happening and lolipop builds will be much more mature in several months. That being said the current Kitkat roms are nice, mature and ripe for upgrading from non DM builds. Whatever you choose have fun and happy flashing
"All devices running webOS will continue to run after the cloud services are terminated. However, they will no longer be able to:
Download new apps or updates. The HP App Catalog will be unavailable after the shutdown
Backup or restore devices from the cloud
Setup new devices
Recover lost passwords
What this means to you:
The HP App Catalog no longer supports new app purchases as of November 1, 2014.
Updates may have been posted by developers until November 10, 2014 and users can download any available updates until the services shut down
You should make arrangements to backup or transfer your contacts, etc.prior to the service shutdown on March 15, 2015
You will no longer be able to backup, restore, reset or initialize a webOS device as of March 15, 2015."
jsgraphicart said:
Thanks for the update. I just bought a Nexus 10 so I may do one last webOS doctor and clean everything up and re-install a fresh version of Android. By the way, has there been any news on that LunaOS that the developers started doing? I haven't heard anything about it.
Click to expand...
Click to collapse
Happy to share the TP love with news and updates, thrilled to see development go so far:highfive: Right I forgot about LuneOS that would be nice I'll have to look it up and see whats new, thanks for the reminder:good:

Live long and prosper WebOs
https://web.archive.org/web/20140214...octor_Versions

RamHa said:
https://web.archive.org/web/20140214...octor_Versions
Click to expand...
Click to collapse
Dead link, please fix:highfive:

RolandDeschain79 said:
Dead link, please fix:highfive:
Click to expand...
Click to collapse
Unnecessary and redundant:
HPTP WebOS essentials

Tnx again @shumash

CM-12.1 installed OK on Nook HD+ but failed on Nook HD

New member; just registered today. I'm really pleased to be here.
I've been learning how to install CyanogenMod CM-12.1 with help from many xda threads, but especially these two:
http://forum.xda-developers.com/nook-hd/development/unofficial-cm12-1-nook-hd-hd-2015-04-08-t3078260
http://forum.xda-developers.com/showpost.php?p=42406126
Many thanks leapinlar, e.mote, Hashcode, verygreen, and amaces.
I successfully installed amaces's CM-12.1 20150628 build on my three Nook HD+, and then successfully moved on to 20150706 build for each of them. Some details are mentioned below.
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I wondered if I was being punished for declining, but I did the same with the HD+ tablets without consequence.
I eventually shut down and restored to the stock HD OS, which appears to be working fine.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
I guess I'll have to learn how to use ADB to find and fix this problem, but if anyone has a suggestion to try before that I'm very anxious to hear it.
Thank you for reading my first post.
Some details:
My installation method, successful only for the HD+, is adapted from leapinlar's Installing CM11 for Dummies (Updated 7-13-14). I used the provided .rar file contents to build the external bootable microSD card with the CM-12.1 zips from amaces. But instead of flashing the provided CWM resident recovery zip I substituted a TWRP zip that I fabricated around amaces's TWRP 2.8.7 images. I was obsessively careful to use the model-specific images and zips in each case.
With build 20150628 on the HD+ I saw the Netflix green screen problem, and a serious screen instability when trying to manually enter a URL in a browser (keyboard and auto-suggest overlays). Disable HW overlays stopped this of course.
I then moved on to 20150706 build on each HD+. The only issues I now see are slight screen instability with overlays and restart about 15 seconds after power-down, which happens almost every time.
P. S. I really like the Nook HD and HD+ tablets. They are perfect for my use as annunciator panel displays for my horticultural controls (hobby), and so plentiful on eBay.

PeteInSequim said:
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
Click to expand...
Click to collapse
A Factory Reset solved the CWM problem and I was able to get a good install of CM-12.1 UNOFFICIAL build 20150706. I exercised a few things including the Android browser, and entered a URL manually from the overlay keyboard with no screen instability. Really looked good.
Sadly though, after shutdown it won't complete a restart. Just hangs with the cyanoboot universal bootloader banner in view.
Can anyone suggest what might be wrong?
FIRST EDIT: I should add that I am able to restart and boot into the resident TWRP recovery utility that I flashed during the installation. Just can't boot into CM-12.1.
SECOND EDIT: Rebooting from TWRP seems to have blazed the trail for a normal boot from power-up, which has worked 4 times out of 4 tries. Maybe its fixed now.
Still have the unexpected reboot after shutdown, though it doesn't happen every time. It seems to shut down and stay there if I've exercised it a bit with some apps. I did install Netflix and watched a few minutes of something, then shut down and it stayed off.
Things are definitely improving.

Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.

ieatabiscuit said:
Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.
Click to expand...
Click to collapse
Thanks for the reply. The only builds I've been able to find are the UNOFFICIALS from amaces, for which I am most grateful. CM-12.1 nightly download pages for ovation and hummingbird always come up blank. Where should I look for those beta releases you mentioned?
But yes, I've moved on to amaces's build 20150716, which when installed by CWM 6.0.4.6 from a booted microSD card to a wiped target has shown no problems, except of course for the reboot after shutdown.
But when installed with resident TWRP over an earlier build the "Unfortunately Google Play services has stopped" problem appeared. I got it fixed on one of the Ovations but not on a second one.
I noticed build 20150717 this morning which I might try on an additional Nook (I have 7 of them scattered around here).
I wonder what's counting out the approximately 10 seconds between shutdown and reboot?

It sounds like you might want to try a different gapps file then. The unofficial amaces builds are the ones I meant, the latest ones are great. For gapps try googling "tk gapps pico" its a bare minimal gapps that let's you install the rest that you use from play store. It works for me, so maybe it will help you. Also, a full gapps file runs the ovation and hummingbird pretty hard on RAM, that could possibly cause an out-of-memory error and make the kernel panicked, which leads directly to a reboot. That pico gapps can help by freeing up ram for more useful things than having everything Google has to offer running all at once.

All sorts of pain trying to install Android (tenderloin-6.0.1)

Edit: Not sure what I've done differently that I can see but it's suddenly accepted the cm and install is ongoing. Fingers crossed I make it through to the end
Got my 32gb Touchpad webOS 3.0.5 to come back to life after sitting in a draw for 3 years without a charge. It runs great!
I'm on Win10 (64bit)
Now the issue is the universal novacom installer fails everytime. Detects win 64 but then won't install the drivers. So I found the drivers separately and put those on manually.
Now when I hit the batch file in TPToolbox 2014-05-18-v40.bin (I believe this is the most recent version) it comes up with
Setting Palm Path . . .
Checking novacom service . . .
Loading TPToolbox . . .
unable to find device
.
Cannot connect to Touchpad
then the stuff about the cable (using original HP cable I used to charge it) have it in usb mode (this is the usb image it says should be on screen).
Now if there's a way to get it into "Recovery (bootie)" mode that gets the large usb symbol on screen that I'm failing to comprehend then maybe this is my issue.
Begging for assistance before I lose my mind. Also first post, great forum been here the last 4 hours but I think I'm going word blind now.:good:

Something else not working now.
When I get to the install Android bit on the toolbox it says "there are differences between boot sector and its backup.
Not automatically fixing this.
Free cluster summary wrong
few more bits like that then it aborts back to media volume mounted.
Just noticed I was on version v40 of tptoolbox so I've switched to v42.
Now it checks the tenderloin and gapps zips but says "Invalid number of recovery zips (0)
So where do I get that from? I didn't see any recovery zips at the downloads link or have I missed something glaringly obvious? I watched one of the videos through and he put on 3 zipped folders but one was an update. No sign of recovery zips so how do I deal with this?
Here goes the umpteenth attempt.
I could use some help that the guides seem to be missing. I've tried different tenderloin zips and added in the update zips but still falls flat at Invalid number of recovery zips.

Unfortunately there is lack of details in you posts to be able to be of much help.
I would personally either go with 4.4.4 KK or leap over to EVs nougat 7.1.1
Reference Roland's tutorial's, they are the best source of info out there.
There are two of his threads pinned/stickied above this thread, & one below.
They have _all_ the details to install any version you want. There is an abundance of info.
WebOS, imo is dead for these. I haven't touched it for over 4 years.
It is not on any of mine.

I'd disagree regarding installations of Marshamellow having all the info as I followed the available info and came up with those errors time and time again, specifically the "recovery zip" folders.
I gave up after losing a day to this. Installed 4.4.4 kk before I went to sleep as that absolutely had _ all _ the info and it went on first time. Ty for your input.

6.0.1 Marshmallow cant be installed directly with the TPtoolbox
Mr_Endz said:
I'd disagree regarding installations of Marshamellow having all the info as I followed the available info and came up with those errors time and time again, specifically the "recovery zip" folders.
I gave up after losing a day to this. Installed 4.4.4 kk before I went to sleep as that absolutely had _ all _ the info and it went on first time. Ty for your input.
Click to expand...
Click to collapse
Hey Android 6.0.1 Marshmallow cant be installed directly with the TPtoolbox due to an incompatibility with the required recovery file. Hence the reason my TPtoolbox guide specify the install of android 4.4.4 or 5.0 but not 6.0.1. In addition to keep WebOS on the tablet you will need to follow a few extra steps or you may get errors and issues. Not to worry every link and piece of info is provided in detail below, you could even successfully install 6.0.1 with this guide but 7.1.1 is better, happy flashing.
[ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad

Thanks for the reply Roland

Is there any OS that works ?

Hello .... I'm finding whatever OS I'm trying becoming unstable to use . So, I'm asking if there is any OS that is actually stable enough to use . I don't care whether it's an old version or what . I'm not using the tablet for games, just something I can browser the internet with . TIA

The one that has given me the fewest issues is https://forum.xda-developers.com/showthread.php?t=2712680 [ROM] [4.4.4] [CyanogenMod 11 by Jcsullins] [DM] [06/12/15]
everything works extremely well except the DSP manager when adjusting audio settings for the built in speakers where changes beyond the defaults do not have any effect on the audio.
Sadly many of the links are dead for things like gapps.
The ROM I use is cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
The gapps I use is: gapps-444-base-20160802-1-signed.zip
If needed, I can upload the gapps that I use though I am unsure if the forum has any rules surrounding it if I were to upload them to something like dropbox.
I try the others from time to time (easier for me since I really only use BSplayer and chrome in order to watch videos in a hover window while surfing the web (occasionally using my Bluetooth speakers or headphones).
Anyway, the main reason why I keep coming back to it, is the memory management. For many newer ROMs, you have issues such as the google calendar widget not working,or chrome not working properly, or when it is working, frequeny memory issues, especially if you want to upload an image to a site where it switches to the gallery app. by the time you select an image, it would fail to attach it because it will complain that the previous action could not be completed due to low memory.
With android 4.4, I do not have that issue. I don't know why it keeps happening for me since there are times when there will be over 100MB of free RAM, and chrome will still fail to do things with that error message.
Beyond that, the home screen under android 7.1.1 does not hold as many icons or widgets, even if you set the screen size to small, or adjust the dpi to 120. the home screen holds fewer icons and fewer widgets.
Overall, while it si great that newer versions of android are being supported, I feel that from a hardware standpoint then tablet has reached its limit with android 4.4
While there is also an evervolve version of android 4.4, for some reason it does not perform as well, even with more kernel features such as being able to overclock past 1.78GHz. it takes longer to boot, and some widgets do not work, along with issues with chrome.

https://forum.xda-developers.com/showpost.php?p=71176374&postcount=937
Check out the Nougat Evervolv thread. I've been using it, and it's fantastic.

Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable

Dude905 said:
Thanks for your input Razor512 .... And crazyates : Has this been updated since its first release, because when I gave it a go it was very unstable
Click to expand...
Click to collapse
Yes it has, but you need to download the nightly from their website. The XDA thread has an older version.
http://evervolv.com/devices/tenderloin

Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA

Dude905 said:
Ok, great news there crazyates. I installed evervolv from the YouTube guide, Do you know whether it still will work with those methods in the guide just as long I replace it with
ev_tenderloin-7.1.1-nightly-2017.03.03.zip and I believe you are using gapps-511-base-20161007-1-signed.zip , yes ? Thanks
YouTube >>> https://www.youtube.com/watch?v=ISWZ0c48gNA
Click to expand...
Click to collapse
I'm not sure about the Youtube instructions, and I followed the written instructions on the forums.
Also, IIRC, if you're using a 7.1.1 ROM, you can't use a 5.1.1 Gapps. I would recommend downloading the newest 7.1.1 Gapps.
Here are the instructions I followed:
AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
4. When given the option to adjust partition sizes, increase the System partition to at least 1312mb
5. Finish install, and reboot to TWRP
6. While in TWRP, flash the 9/6/16 TWRP 3.0.2.0 or the smaller 9/11/16 TWRP 3.0.2.0
7. Reboot into the new TWRP that you just flashed
8. In TWRP advanced wipe menu, wipe the System partition
9. While still in TWRP, flash the ROM from the OP along with some OpenGapps
10. Worship @jcsullins and @flintman, as they are your gods.
Click to expand...
Click to collapse
Here are the changes/differences I made/noticed:
crazyates said:
Step 3: While you're copying the older ROM/Gapps/TWRP into the "ttinstall" folder, I also copied everything you need for the new install into an "evervolv" folder. This way you can copy everything at once, and formatting a volume in TWRP doesn't destroy your install files.
Step 4: I have a 32GB TP, and don't use hardly any of it, so I increased the System to ~2GB, and the Cache to ~1GB. I figured going on the big side couldn't hurt.
Step 6: There's a newer version of Flintmans TWRP, 3.0.3.0(12/22/16).
Step 8: After you wipe the System, reformat the Data and Cache volumes as F2FS. Because your install files are on the External_SD instead of the Data, you can do this without recopying your install zips back again. I installed the system twice, once with Ext4 and once with F2FS. It feels snappier, and runs a lot better with F2FS.
Step 9: I used the Nightly build for the ROM, which is working great. Then the newest Gapps. Then I also flashed the SKZ overclock kernel at the same time.
Few other notes: Changing the Governor to LionHeart and Scheduler to Tripndroid made a noticeable difference for me. Also, because this doesn't have a lot of RAM, I gotta be careful with what I install, and how much I try to use it. Do NOT install Chrome from the app store. It will eat every bit of RAM available, and slow the whole thing down. I also use Greenify (with root permissions) to hibernate any app I can so it saves a lot of RAM that was as well. I'm using ~329MB (40%) for the system, with ~500MB (60%) available for apps.
Click to expand...
Click to collapse

@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.

bobcote said:
@crazyates Did you try Evervolv 7.1 nightlies? I'm curious to read your experience feedback because I'm on it and getting tired of always having a non-responsive tablet. I might go back to 4.4 as I'll go mad otherwise.
Click to expand...
Click to collapse
I am running the 7.1.1 nightlies. I haven't had any problems, and it's running very smooth. I'll randomly update it to the newest nightly, and haven't noticed any issues.
I do remember the time I first installed Evervolv 6.0 nightly last year. I installed it, and the touchscreen didn't work. At all. Looked into it, and it was a problem with that specific nightly build, so I went and reflashed everything with the one from the day before, and it worked great.
Anyways, all that to say it's working great, but it's still a nightly, so sometimes things go wonky.

I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?

wprpalmeida said:
I am still running a really old ICS build, and I noticed i can't update all my apps no more... what is the best Android version to run on the TP. Bluetooth is a must, but Camera isn't. Heard good things about 4.4.4 and 7.1.1, which one would you guys say runns smoother?
Click to expand...
Click to collapse
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.

crazyates said:
Can't say much for 4.4.4, but I'm using 7.1.1 and it's great!
The only argument I could see making for 4.4.4 is if it runs a bit lighter than 7.1.1. These only have 1GB of RAM, so if 4.4.4 is capable of using less RAM for the android system, that means more RAM for apps. On the flip side, 7.1.1 uses such things as zRAM and KSM for better memory management, so it may be a wash.
Click to expand...
Click to collapse
yeah, this is what I want to figure out. The developments in the Android codebase were quite extensive between these two releases, and the huge influx of budget phones in some markets (like mine for example) lead me to believe memory management would have been a key point in developing versions after 4.4.4. I'll give 7.1.1 a whirl and see how it goes.

Here are the instructions I followed:
...
Here are the changes/differences I made/noticed:
Click to expand...
Click to collapse
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
I used the latest nightly (ev_tenderloin-7.1.1-nightly-2017.03.08.zip) and tried both open_gapps-arm-7.1-pico-20170312.zip and open_gapps-arm-7.1-pico-20170312, also I tried some of the TWRP-Versions you linked. I'm using TPToolbox v42 2015-01-08). So I wonder how you can figure out which versions fit together, I can remember this nagged me last time until I found a combination that worked...

AlwaysLucky said:
If you end up having to start from scratch in TP Toolbox v0.42, follow these steps:
- Download a TP Toolbox Compatible ROM
- Download a TP Toolbox Compatible GApps
- Download a TP Toolbox Compatible TWRP
1. In the TP Toolbox v0.42 main menu, do a 'Complete Data Reset' to start from scratch
2. Select the 'Install Android' option from the main menu
3. Copy the 3 above files to the install folder after the TP is mounted
Click to expand...
Click to collapse
Flexmaen said:
I tried to follow your instructions, but I get error messages like:
Error: unrecognized/unsopported zip 'FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.0.3.0-1-23-17.zip'
Error: Incompatible GAPPS/ROM versions None/7.0
Click to expand...
Click to collapse
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)

Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.

7.x is very slow some times.
Flexmaen said:
Thank you! I installed the latest nightly, and it works fine so far.
The only thing I noticed that some apps now are blocking the device. This was also the case with the Android 4.4 Pac-Rom I used before. So it seems that some apps are using recources that aren't working well on the Touchpad at all, or that there is a general problem in several CM-versions.
For example the current version of Google Maps is so slow, you won't use it. I installend an older version (7.7.0), and this one works very fine. Also the new version of Maps lost the WiFi connection, which didn't cause any problem with the older version. So I wonder if there is some kind of incompatibility.
Another example: Fake GPS Location is much quicker than GPS-Emulator which also got stuck from time to time. Also the current Amazon App store was slooow.
Summary: Android 7.x runs fine so far, but you have to make sure that you get rid of the apps which block the device for some reason.
Click to expand...
Click to collapse
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?

giolc90 said:
When you say "blocking" you mean very slow? Since I uptaded from 4.4 to 7.x I've noticed that lots of apps are very slow. Some freezes for seconds and returns only when I block the device and turn on again. I dont know if its only on mine or its normal because of the old hardware. Is there any version that run real smooth? Or other system?
Click to expand...
Click to collapse
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.

Flexmaen said:
Yes I mean very slow. Often so slow that it takes a minute until you can change to another app.
The Problem also existed on my 4.4 Pac Rom, so I guess it's rather caused by new apps who might expect some feature, like multicore, etc. Or it is some fault, that already existed in older custom roms. Not sure. However, I can recommend downgrading apps in this case, older versions often work like normal.
Click to expand...
Click to collapse
Perhaps using F2FS could help, if not currently using it?

crazyates said:
Was that error message from TP Toolbox, or from TWRP? TP Toolbox won't recognize the newer TWRP images, nor will it recognize any 7.1 ROM/Gapps, so you need to use an older version to get things started. Once the older TWRP is installed, then you can use it to update to a newer version.
All in all, I had 8 ZIP files on my HP Touchpad to get a complete 7.1.1 install, but you can do it with as few as 6:
OLD ROM: CM 12.1
OLD Gapps: 5.1
OLD TWRP: 2.8.3.0
NEW ROM: Evervolv Nightly
NEW Gapps: 7.1
NEW TWRP: 3.0.3.0 F2FS
SKZ Kernel (Optional)
SuperSU (Optional)
Click to expand...
Click to collapse
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!

DoubleStuff said:
I guess there is a "new" method out there that can install Nougat 7.1.1 in as little as 3 zip files!!!
check it out, it comes with instructions and a new video...
I can name that tune in 3 zips!!
Click to expand...
Click to collapse
It doesn't work for me ... I'm having issues . First off I like to ask why he didn't use the latest Rom ? And the part with go to the PC Mounted Touchpad internal drive for the TWRP ? When I open the TWRP folder I don't see twrps file, why not ? There nothing in this folder, its empty . What I done was just placed those zip files in the TWRP folder . Afterwards once I do the final reboot to Evervolv it will just show those Evervolv lights flashing like its trying to load up but it doesn't, it just keeps continuously trying to load but it never does