yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] nevertells2:
Since you are able to install Lollipop 5.0 and Gapps, I would use recovery and flash 5.0. If that goes well, then flash the gapps that Flintman recommends using with his Rom. Be sure to do all the normal stuff, clear cache and Dalvik cache. Don't understand why TPTB won't install 5.1.1, but apparently Mr. Sullins has some work to do.

I just went and looked to see what Gapps CM recommends, it's this: gapps-5.1-arm-2015-05-03-16-32-37.zip. I don't believe you have tried it, so try the Rom, recovery and that in the ttinstall folder. I also did go back and reread the OP and had not noticed previously that TPTB v42 did not support a zero Gapps installation, so my bad on recommending that. I do remember that Mr. Sullins explained that v42 no longer cares about file names, but rather looks inside the zip and apparently it does not like the ones you have tried. And it may be he needs to adjust for Lollipop Gapps.

NT
[TouchPad Development] milski65:
Jesus, this was an easy upgrade from 4.2. Thanks JC, NT , and Roland for all the info provided. Upgraded to 4.4.4. and and snapshot 15/01/13. TP running stunningly.
[TouchPad Development] rolltide78:
ok tried to use CWM to flash ev_tenderloin-5.1.1-testing-2015.04.27.zip and it says "Patching system image unconditionally... blkdiscard failed: Invalid argument

E:Error in /storage/sdcard1/ttinstall/ev_tenderloin-5.1.1-testing-2015.04.27.zip

(Status 7)

Installation aborted.

This is with 5.0 installed and then rebooted to recovery and after a Davlik Cache wipe. Really don't know what to try unless try to use tptoolbox again and flash fresh this zip and that minimal edition gapps you mentioned. Craziness.
[TouchPad Development] jerryatherton:
Use Flintmans TWRP
[TouchPad Development] prodigalOne:
First and Foremost, this is hands down the most dedicated app for any Android device I've used, and I've used a lot.

I'm having issues after doing an android install using the below zips. It formats, clears and prepares the install, but when booting into recovery it froze. I had to do a hard reboot, and now it boots to blank screen.

RECOVERY - update-TWRP-jcs-dm-tenderloin-20140612b

ROM - ev_tenderloin-5.1.1-testing-2015.04.27

GAPPS= gapps-lpmr1-20150324-signed

Any Help?

EDIT::::: I allowed the device to cool down, VOLDOWN, POWER AND HOME for 10-30 seconds and I booted to WEBOS RECOVERY. Also, OP has a debrick util. I've donated to him for being awesome.
[TouchPad Development] shumash:
Use the Flintman TWRP recovery files recommended in his OP
[TouchPad Development] prodigalOne:
Thanks, and I've edited my post to reveal he also has a debrick util. Donated to OP.
[TouchPad Development] nevertells2:
Why don't you try the 5.1.1, Flintman's TWRP and gapps-5.1-arm-2015-05-03-16-32-37.zip using TPTB?

NT
[TouchPad Development] milski65:
Hey NT. What's your opinion on 5.1.1. Just went to 4.4.4 and am enjoying it. Take it not a DD?
[TouchPad Development] nevertells2:
The development for it is coming along well. Unfortunately, I still consider it a bit too experimental for my tastes. I am a big fan J.C. Sullin's CM11 Roms. That is why I keep my comments and suggestions here strictly to the installation or upgrading of the Android Roms and auxiliary programs. If you are the adventuresome type, then I would give installing it a try. Otherwise I would stick with CM11 as it is stable and very robust. There may come a time when I will try installing it but not yet. If you want some insight into 5. 1. 1 features, there are some great articles published on the Internet that should tell you what you need to know.

NT
[TouchPad Development] orangecream:
Need a little help. I'm trying to use HPTB to install the following after a complete data reset:

gapps-5.1-arm-2015-05-03-16-32-37.zip

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

cm-12.1-20150518-UNOFFICIAL-tenderloin.zip

But I keep getting an error saying that the gapps package is unsupported. Ty!
[TouchPad Development] shumash:
That's because milaq didn't update the tptoolbox.cfg file in the device tree to 5.1 from 5.0.
[TouchPad Development] black7:
Seems the Toolbox doesn't recognize the 5.1 gapps.

My workaround:

Use a 5.0.x GApps to get through the install process - this will, however, give a 5.0/5.1 compatibility error in Toolbox.

To 'trick' Toolbox into allowing the install, I edited the "tptoolbox.cfg" file in the ROM compressed zip (I'm using latest Evervolv) to make Toolbox think it's a 5.0 ROM.

Allow Toolbox to install Recovery, ROM (with edited "tptoolbox.cfg"), GApps (5.0)

Boot directly into Recovery from Toolbox

Install proper ROM compressed zip file

Install proper 5.1 GApps

Reboot and enjoy
[TouchPad Development] orangecream:
Thanks, Black7, that worked for me.
[TouchPad Development] Domvillan:
Can we perm install tptoolbox on device yet?
[TouchPad Development] nevertells2:
If you have used "Complete Data Reset" which removed WebOS, then there is enough room in /boot to put TPTB there. You have to rename

TPToolbox-2014-05-18-v40.bin to something like uImage.TouchPad Toolbox. You have to include uImage.(+whatever name you want). I named mine uImage.TP Toolbox_V42. What looks like a lowercase "L" in uImage is actually an uppercase "i". Copy and paste the renamed file into /boot using a file brower like Rom Toolbox Lite. Whatever you name it will show up on your Moboot menu. Just select it and away you go.

NT
[TouchPad Development] clnzx2:
Where can I find a compatible gapps package? I have tried a few and they all say unsupported
[TouchPad Development] real_sl4cker:
Compatible with which ROM?

Please provide some more details what you want to do so we might provide a quite precise answer [emoji6]

(mobil gesendet / sent from mobile)
[TouchPad Development] clnzx2:
I have tried a few combos but my end goal is evervolv 5.1.1. I modified the cfg file to make it look like a 5.0 ROM. It works fine. I have a twrp zip that works fine. I have tried a few 5.0, 5.0.1 and 5.1.1 gapps and none work
[TouchPad Development] real_sl4cker:
Use TP Toolbox with milaq CM 12 nightly and the suggested combo (recovery, GApps) in milaqs OP. Afterwards boot to recovery, flash evervolv recovery, reboot to recovery, do full wipe, flash ROM and GApps, profit.

(mobil gesendet / sent from mobile)
[TouchPad Development] galaxykeks:
Hey :)

I tried that but directly form TWRP.

But the uImage gets deleted all the time... any ideas?

Thanks for your brilliant work btw.!
[TouchPad Development] eKeith:
Try doing it with a file manager like Root Explorer as described and not using TWRP.
[TouchPad Development] kupitz:
I used YP Toolbox V42 to do a clean wipe of the device. I downloaded an unsupported Revovery file and was unable to install Android due to the incompatible recovery. I downloaded a supported recovery and deleted the original recovery zip from the device. Now in an attempt to load the correct recovery zip my Windows 7 PC will not recognize the HP as a removeable drive. It recognized the device when I plug it in but won't show up in explorer. If I go to Eject the device in the taskbar it shows "Eject Palm" so it knows it's plugged in but not as a drive. Using same Novacomm drivers I used to load the wrong recovery in the first place. Any ideas?
[TouchPad Development] nevertells2:
eKeith is correct. TWRP does not have root permissions to copy and paste a file into the /boot folder. Rom Toolbox Lite is another good file manager to use. One advantage it has over Root Explorer is one has to flip a setting on the top of the screen to make the folder where you want to paste a file writable. With Rom Toolbox Lite, you do not.

NT

---------- Post added at 09:01 PM ---------- Previous post was at 08:53 PM ----------

You did not say if you tried a complete data reset again. You did not say which Android Rom you were trying to install. So at one point when TPTB mounts your tablet as a drive and has you copy over the needed files you were able to do so. I suspect that the failed attempt to install the wrong files probably left your TP in a corrupted state. Start over, complete data reset and use the correct files this time.

NT
[TouchPad Development] galaxykeks:
thanks, it worked. I was assuming at this low level there is everything writeable. I was proven to be wrong ^^

u never stop learning :)
[TouchPad Development] kupitz:
Thanks NT, that did the trick!
[TouchPad Development] nevertells2:
I know, I know, this is OT, but still worth it:

For all you lurkers out there, Mr. Sullins has posted a new CM11 build dated 6/12/15. It can be found here: https://www.androidfilehost.com/?w=files&flid=14849 and some of us are discussing it in the official Sullins CM11 thead here:http://xdaforums.com/showthread.php?t=2712680&page=125 starting with post #1244.

NT
[TouchPad Development] buzz86us:
can this support linux? I have deleted webos, but i'd really like linux on my HP Touchpad since there isn't a good DCPP client for android
[TouchPad Development] mschumacher69:
No, just webOS and Android for now (and probably forever)...
[TouchPad Development] buzz86us:
do you know if i could still install it? or is that option off the table?
[TouchPad Development] gtallmadge:
Check in the forum for Other Touchpad Development. Several threads there on installing Linux but not a lot of current activity.
[TouchPad Development] GwidionR:
There is a homebrew solution for ubuntu 11.4

Do a search at webosnation for further information
[TouchPad Development] Razor512:
Is there a recommended way to get this to work with CM9?

I know it is old but after trying the latest CM11 and 12 builds, 9 is simply offering the best user experience for me since I get more vertical screen space. Youtube app actually offers the 720p HD option, and dice player is stable on it.

On top of that, the CM9 home screen when set to 120 for the screen density,holds far more icons and widgets than with any of the newer builds.

Anyway, I have the partition sizes set how I want them, is there a way to just get it to install CWM, and leave me to install CM9 and gapps through the recovery?
[TouchPad Development] nevertells2:
What did you do before touchpad Toolbox came along? Oh well, here's the link. You should know this, but anyway, here it is:

http://rootzwiki.com/topic/31548-ro...ndroid-23-43-on-the-hp-touchpad-the-easy-way/

NT
[TouchPad Development] Razor512:
It is just that the toolbox is easier to use, as well as being far quicker. The only issue is that it does not support any partitioning done with other tools (it simply sees every partition as bad if you want to use the toolbox afterwards).
[TouchPad Development] nevertells2:
Well, I don't see anything on the OP that says you can't. Sullins even mentions non-dm versions of the recovery you can use. Have you tried and it didn't work? I seem to remember that Sullins wrote the toolbox to look at the version of Android you were going to install and then it set up the volumes accordingly. I would go ahead and try and see how it goes. If it does not work to install CM9, you are going to have to install some kind of non-dm version of Android and then use CWM to revert back to CM9. Just remember, you will have to use the feature of CWM to completely wipe out the previous version of Andorid. And, you can always use toolbox to change the volumes back the way you like if toolbox changes them during the install of CM9 to something you don't like. One thing I did learn a while back, and especially with WebOS removed, you can make the /data volume pretty much any size you want using the toolbox. The old WebOS/media volume only has to be around 800 mb to support using the toolbox to install Android. However, CM9 might look for the SD card in the /media volume, not in the /data volume like a dm version does and in that case, you would have to move a nice chunk of memory back to /media. But you can still leave a nice chunk of memory in /data so you never run out of internal memory. In fact, the more I think about it, you will have to configure memory to support the SD card in /media for CM9 to work correctly.

NT
[TouchPad Development] Razor512:
It detects the android build and if it detects a non data media build, it refuses to install. The issue is essentially extra code that cripples the toolbox by refusing to install non data media builds.

Based on the controls, it already has everything that it needs to install CM9. It allows you to manually specify partition sizes, thus I can set the proper sizes for CM9, but give the data partition more than 1.5GB space (e.g., give it 8GB of a 32GB touchpad), and then have the media partition take the rest.

A fix to the entire issue would be for that crippling part of the code to be removed, and then just inform CM9 users to simply manually set the data partition to a size they would prefer, and then allocate the rest to the media partition.
[TouchPad Development] jcsullins:
Which version of TPToolbox are you using?

What (exact) error message(s) do you get?
[TouchPad Development] Razor512:
tptoolbox_v42

Hmm, it seems the issue with with the recovery that I was using. It was complaining that the recovery used was datamedia while the ROM was not. (though i have been using the TWRP recovery for some time now with CM9

(currently difficult to find downloads for the various recoveries (links are either dead, or lots of rom pages will list what you need, but never directly link to the listed items thus you go searching for them). When I originally did the CM9 installs a while back, I had not kept s backup copy of the install files, and thus when I got another HP touchpad, I ended up having to redownload everything, and ended up getting TWRP.

Anyway, the TWRP 2.7.1.0 works file with CM9, and properly detects the media partition, and uses it for the various backups and installation of files.

The main reason why I wanted to use the toolkit, was because it was simpler to get the partition sizes that I wanted. With the old acme install, when it partitions the device, the tptoolbox is unable to do anything with the partitions as it just finds them to be corrupt and unfixable.

Anyway, i was able to find a workaround. I installed CM11 and TWRP, (with the partition layout and sizes that I wanted, then used TWRP to install CM9 and its gapps. everything is now working well with extra space allocated to CM9 (and no webOS installed :) )

Main thing that I missed from CM11 is that after a few hours of browsing large webpages, chrome did not eventually hang, causing the OS to reboot, but that issue is worth it to have CM9 and the extra vertical screen space.
[TouchPad Development] mschumacher69:
If ur main issue is space on the home screen, this can be easily fixed in trebuchet's settings, just change the grid size to match ur preference.

Regarding 720p videos, I use milaq's cm11 nightlies and 720p videos work fine on YouTube.
[TouchPad Development] Razor512:
For the icon grid, with newer versions of android, there is essentially a bounding box containing all of the icons, and it is much smaller than on CM9.

CM9 gives you a 10x10 grid for icons with decent spacing and size, and no clipping, thus more widgets and icons http://i.imgur.com/xmrVj0y.jpg (currently doing a few random tests to ensure that everything is working fine when the workaround).

But my main issue is the top bat in newer versions of android.

On CM9, the usable screen space is 1024x732 (the bottom bar takes the rest of the vertical screen space).

While it would be great to get even more free screen space, (thinner bottom bar), 1024x732 is acceptable on a 1024x768 display.

http://i.imgur.com/VAyXbqx.png

With builds newer than CM9, your available screen space becomes 1024x695 thanks to a screen space wasting top bar eve though there is more than enough space to combine the top and bottom bar (kinda like how CM9 had everything in the bottom bar)
[TouchPad Development] mschumacher69:
All this can be adjusted in trebuchet's settings. U can turn off the search bar and adjust the grid size...

Believe me cm11 is smoother than cm9 and you would gain all the space that u are wasting on the SD card partition in cm9. Also, on cm9, u are limited to just 50 apps on the SD card, if u install more, all hell would break loose. So basically, you are wasting the 32 GB that u have if u use cm9. With cm11, u would claim all this wasted space back.
[TouchPad Development] synchron50:
I tend to disagree and, although Razor512 reasons is for screen real estate, I actually feel that CM10 Jellybean was smoother than CM11 KitKat and the smoothest of them all. If I could have JCS CM10 (not CM10.1) ROM work with Data/Media space saving partitions that would be ideal. My attempts in downgrading (either via flashing with CWM or Restore CM10 Backup from CWM) have led to bootloops so if there's a way to downgrade with TPTB yet still benefit from DM build structure, I'm all ears!
[TouchPad Development] mschumacher69:
Anything is better than cm9. But I would strongly recommend DM builds, whether cm10 is available as a DM build or not, I don't know. But I know cm11 is and it runs smoothly on my TP.
[TouchPad Development] nevertells2:
I see you figured out that you have to use an older, non-dm version of TWRP. Mr. Sullins only has a link to a dm compatible version of TWRP on his OP.

So are you saying that with a non-cm version of TWRP and CM9, the toolbox still refused to install CM9?

NT

---------- Post added at 04:29 PM ---------- Previous post was at 04:11 PM ----------

The problems that folks had with the 50 app limit was because CM9 only allocated 1.5gb of space to internal memory. So once that started filling up, they were forced to move apps to the SD card and that is when they started running into the 50 app limit. When Mr. Sullins created a script to allow increasing the size of the /data volume, that eliminated the 50 app problem because there was plenty of room in the internal memory area. Once the dm builds came along and the SD card was moved to /data, there is absolutely no 50 limit to deal with now. Since razor is happy with CM9 and now has his /data volume sized large enough, he will never has to worry about moving apps to the /media volume SD card.

And as far as CM11 goes, it does have limitations that CM9 did not have. Best as I remember audio and Bluetooth worked flawlessly, so did the camera and support for HD video works better than CM11. Those items worked great on the 2.65 kernel of CM9 and have always had problems on the 3.0 and 3.4 kernels used by the dm builds. I prefer Mr. Sullin's builds because he uses the 3.0 kernel which has fewer issues than the 3.4 kernel. The last builds of CM9, which back then had support from CyanogenMod, were as about as issue free as one could ask for. CM10 was very good too, probably because it still used the 2.65 kernel. It's when CM10.1 came along, the switch to dm and newer kernels created new and sometimes insurmountable issues. As useless as it is, the camera will never work as well as it did on CM9 and 10.

And one last thing. I don't see what you guys see in Trebuchet. There are much better launchers out there like Nova or ADW. They run circles around Trebuchet. Back in the CM7 days, ADW was the default launcher. When CM9 came out, CyanogenMod started bundling Trebuchet with it and I could not switch fast enough to something else. When Google released GEL I tried it once and switched right back to my two favorites. It's as big a piece of crap as Trebuchet.

NT

---------- Post added at 04:37 PM ---------- Previous post was at 04:29 PM ----------

Best of my knowledge, dm did not come along until CM10.1.

NT
[TouchPad Development] anewbieuser:
I just want to say thank you for the developer/s for doing this for us and continued to support this device! just updated to CM11 from CM9 flawlessly! Once again, BIG THANK YOU!
[TouchPad Development] vik5:
Thanks for your hard work I need some help sorry to bother you I now it is not the write thread but if u can help me .my touchpad is acting funny it was on cm 9 but never charge from a long time and I was trying debrick bec it won't start and I follow your step but I can't go pass qdl not mount aborting error .

I tried 12.04 again qdl error .when I connect touchpad to comp wind 7 64 bit it say USB not recognize and in device manager under USB I can see unknown device but it won't stay ,it goes away and than I can see it again it keeps on doing need help
[TouchPad Development] nevertells2:
http://rootzwiki.com/topic/38786-tpdebrick-v004/

Go read the thread and afterwards, if you still have questions, ask them there.

NT
[TouchPad Development] Razor512:
Sorry for the late reply, I think my issues stemmed from most of the recoveries were designed for datamedia builds, and others are just not available, or not easy to find.

Though from testing, the recoveries designed for datamedia builds seem to work fine on CM9 non datamedia. I think if all of the recoveries and other items were all designed for non datamedia builds, it would work fine.

Anyway, I will have to probably give the newer builds another chance. I just wish there were a way to get rid of that top bar and recover that vertical screen space.

Anyway, the touchpad toolbox is one of the best tools for android that I have ever used. I really wish that more devices will gain similar tools which help to automate the tedious processes.
[TouchPad Development] shumash:
Some unnamed ROM's will allow you to change the DPI and enable Expanded Desktop, which lets you hide the top and/or bottom bars for selected apps in the Display Settings. You ought to have an alternate way to navigate, however. :)
[TouchPad Development] jcsullins:
Look under "Below is the list of Recoveries that you can use with TPToolbox" on post #3 of this thread [1].

There is a section for data-media (DM) recoveries and a section for non-data-media (NODM) recoveries.

[1] http://xdaforums.com/showpost.php?p=52765140&postcount=3
[TouchPad Development] jasonsf:
Anybody know if there is a way to get the Touchpad into webOS recovery without a power button? My power button is completely non-functional. I was getting boot loops in TWRP recovery so I let the battery die and used moboot to get to webOS recovery. I then did a Complete Data Wipe in TPToolbox and started the WebDoctor install. The instructions say to run the root certificate script from the WebOS language screen. Novacom won't find the device and now there is no Moboot screen. It boots directly in to the webOS language screen. And draining the battery to reboot is a pain. Any other choices? I'm just about to resign this to a total loss. Unless I can get novacom to connect to the device outside of recovery or there is a way to force it in to recovery without the power button, it is game over. I can't seem to fix the power button. It clicks but does nothing.

Thanks-

Jason
[TouchPad Development] Atari-San:
When you connect the usb plug for powering the device, press volume down (or up), it should put you in WebOS recovery. For shutdown your HP Touchpad, check for an app on the app store or use the dev mode to be able to use the app injector on PC for looking for a shutdown shortcut (i don't remember the name but it was from a preview method of resizing the Touchpad before this tool) or let simply the battery drain, i cannot remember a shutdown function from WebOS. When you are able to powering it up, just press one of the volume down when the HP Logo show at first before it load WebOS, as a trick, press the button and connect the USB cable in the charger so it boot on recovery instantly.
[TouchPad Development] jasonsf:
This worked! Thank you so much!

Jason
[TouchPad Development] nevertells2:
You really need to look into finding a DOA TouchPad and use it to cannibalize the power button and replace yours. Otherwise, you can add a quick settings button to shutdown the TouchPad and when your pad starts to boot up, at the Moboot menu, press either volume up or down to stop the countdown to boot up and use it to navigate to "boot WebOS Recovery".

NT