yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] iknight8:
Thanks. I seem to be having issue with the recovery zip file. It keeps failing at that.

It keep saying, unrecognized/unsupported zip 'update-PhilZ*.zip' 1 unrecognized/unsupported zip files. Any idea which recover will TPTB accept to continue the installation? Thanks. Please provide link if possible. I tried both CWM and PhilZ...

I am using the links provided in the first post of this thread.
[TouchPad Development] jerryatherton:
I think i usually rename to cwmxxxxxx.zip
[TouchPad Development] De4dSpace:
I'm having the same issue. I've tried renaming the recovery zip. I am using the latest TP Toolbox that was linked a couple pages back and the recoveries from the OP.
[TouchPad Development] nevertells2:
First off, sorry for the typo in my reply, TPTB v42 is the latest version. Mr. Sullin's latest version of CM11, 20150113 is what you should use. Yes, TPTB will install CM11 in the Android partition. It will also set the correct partition sizes for CM11. You really should have read the instructions in the OP and you would understand how TPTB does the install. After setting up the Android partitions, it creates a ttinstall folder and will prompt you at the appropriate point to copy the three files over to it. It will then exit TPTB and start recovery and complete the install.

If you are using v42, file names should not matter. That was an issue with v40. As to CWM, I am partial to Mr. Sullin's "update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip" You should find links to that in his OP or here: https://www.androidfilehost.com/?w=files&flid=14847

NT
[TouchPad Development] maur1c10:
can someone share the novacom drivers?

the universal installer fails and the other links send me to a different page
[TouchPad Development] maur1c10:
that worked thank you
[TouchPad Development] Slwitek:
Recovery Not Working

I have tried all of these recoveries and I cant get any of them to pass the check.

Latest try resulted in a unrecognized/unsupprted zip files.

I copied the 3 files to the folder requested over and over with different files, just trying to get a recovery to pass.

Can anybody get me to a supported recovery that they know to work.

using 20150113 Snapshot

gapps stock 4.4.4 20150221

twrp 20140512 (have tried a bunch of different ones)

Wasnt this supposed to be easy? :o
[TouchPad Development] jerryatherton:
Here is a snapshot of a successful ttinstall folder. I am travelling, it is the only machine i have here. I always start with a KK ROM the install the Lollipop ROM with recovery. It is easy once you get it done once.
[TouchPad Development] wpcprez:
this is the best thing since... samoa girl scout cookies
[TouchPad Development] nevertells2:
What version of TPTB are you trying to use?

Also, you should type the actual file names you are trying to install. I know that 20150113 Snapshot is the latest Sullin's CM11 build. But I don't recognize the gapps or twrp files by just the date you typed.

NT
[TouchPad Development] RolandDeschain79:
Its easy if you follow the super easy way guide;)

Supported Data Media Recoveries (TPtoolbox v42-v41x) Download:

Note: These recoveries are meant to be used with TPtoolbox v42 and v41x

View attachment 3128785

Download Philz Touch CWM Recovery:

Philz-CWM-jcs-dm-tenderloin-20140612 via mediafire:

Philz-CWM-jcs-dm-tenderloin-20140612 via androidfilehost:

Download TWRP Touch Recovery:

TWRP-jcs-dm-tenderloin-20140612b via mediafire:

TWRP-jcs-dm-tenderloin-20140612b via androidfilehost:

Download flintman's Dec. 23, 2014 build of TWRP (DM):

Download Traditional Non-Touch CWM Recovery:

CWM-jcs-dm-tenderloin-20141231 via mediafire:

CWM-jcs-dm-tenderloin-20141231 via androidfilehost:
[TouchPad Development] Moody66:
I copied the 3 files to the folder requested over and over with different files, just trying to get a recovery to pass.

Can anybody get me to a supported recovery that they know to work.

using 20150113 Snapshot

gapps stock 4.4.4 20150221

twrp 20140512 (have tried a bunch of different ones)

Wasnt this supposed to be easy? :o[/QUOTE]

Nvm RD posted . Check that.
[TouchPad Development] nevertells2:
Nvm RD posted . Check that.[/QUOTE]

Which TouchPad Toolbox version are you using? If it's not v42, try using that. I would also suggest using update-CWM-jcs-dm-tenderloin-20140317.zip to get things installed and then you can use that to flash whatever TWRP you want. Also, the gapps that has worked best for me with KitKat is one dated 20140105. There is also a 20140606 around, but I have never heard of the one you posted. Are you sure that it a Kk gapps?

NT
[TouchPad Development] synchron50:
My boot partition using ES File Explorer currently shows:

Size: 29.6 MB (31,041,85 Bytes)

Used: 29.68 MB (31,117,312 Bytes)

Obviously, I can't copy uImage.TPToolbox since boot only holds 30MB. I installed Pac-ROM and kept WebOS with TPTB v.42 on this TP. Has anyone been able to either increase the boot partition size or trim it down to fit the 10 or so MB to have TPTB come up in the boot menu with WebOS? My other TP only has Android so it fits no problem.
[TouchPad Development] nevertells2:
Any discussion you have seen about putting TPTB in /boot is if WebOS is removed. And I don't remember which dev said it, but /boot cannot be increased in size.

NT
[TouchPad Development] lebenskuenstler:
Support for LuneOS desired

Hello jscullins,

would you consider adding support for luneOS? I think it is worth taking a closer look.

Best,

LK
[TouchPad Development] bryantjopplin:
Not too sure how many people have had this error but any idea if novaterm will be able to run e2fsck? If not what does one use? Any way to fix it? Could one basically disable this superblock?
[TouchPad Development] nevertells2:
I had to go do a little reading to find what I think is an answer to your question. You did not explain how you got to the error you posted the pic of. This is what I think you did. You had a problem trying to install Android and tried running "Repair Android Volume." If you read post #4, Mr. Sullins does not guarantee that doing that will fix your issue. He also does not offer any options if his repair routine does not work.

I did do a little Googling and found references to using ADB after using recovery to unmount the volumes you want to check, I assume you would want to unmount /data and /system. Or you could just unmount them via ADB and then check them.

NT
[TouchPad Development] bryantjopplin:
I got it figured out, Mr sullins and I had a pretty lengthy session on irc and had me do some advanced mode issues and found out its not repairable, he should be coming up with a new update to tptoolbox due to this little TP of mine. Learned a lot and hopefully will help some as well.
[TouchPad Development] nevertells2:
Care to share a brief report of what transpired. Sorry to hear your TP is done. Which version of TPTB were you using? Is it something it did that finished off your tablet?

NT
[TouchPad Development] bryantjopplin:
This is a spare TP that was given to me. Mine is fine. First update with only webos went bonkers and basically wouldn't doctor any way you tried. Then then the first tptoolbox came out I tried that and it never really did anything for me as well. So I tried the tpdebrick when it came out and never did anything either. Well after waiting , tptoolbox42 released and I wanted to upgrade my working one and when it went successful and super easy I figured why not try it on the broke one. Well it actually did some things and was like this might work. Complete data erase was first and I believe it work right out the box, next was to make partitions, well this is where it got tricky. First attempt was no go with one error, second was different error I believe, like the second partition inline failed. So I ran the android volume fix and retried the partition setup again. No go. Then I was like screw it, complete reset again and tried it all over. Well at like the 2nd attempt this time it all worked. I was doing each partition separately to keep from it freezing/not completing. Except I put 26gb to system instead of data and screwed up. After it mounted as USB I realized that it was only like a 250mb size and couldn't do a thing with that to load LP. Well I tried to redo everything all over again and tried numerous different methods via novaterm with the installer image and all different, heck even tried the tpdebrick on windows. I know it doesn't work but I wanted to load the image up and see if something I could do to get it to work. Well it tried to load a CDC USB device or something like that and found windows doesn't have a driver for it but Linux does and this is why it was required. Lol. I tried even more things like lvm.static lvremove and lvcreate and lvresize and even tried to rm mmcblk0p14 but no go, kept reinstalling itself or freezing or rebooting. Then I got ahold of jcsullins and went through some advanced mode of tptoolbox and ran ssh and modified the code and even got dmesg logs for him and was like different every time. I can load the log but not to sure if he wants the commands and access to the advanced mode known. But I'm sure irc logs will show lol. Anyways some crazy and fun stuff.
[TouchPad Development] nevertells2:
Thanks Looks like if you had not buggered up the sizing of the volumes, you might have gotten away with it. If anyone knows how to undo something like that, it's Mr. Sullins and since he could not resurrect your TouchPad, suspect your done. Did he have you doing anything via ADB? You might want to look through the Rootzwiki thread on the TouchPad. One guy had started a thread on rebuilding a totally messed up TouchPad volumes. A whole bunch of ADB commands entered one at a time, but when done, many said they had success on recreating the required volumes. The spam stopped at page 13.

http://rootzwiki.com/forum/217-hp-touchpad/

Here is one guys suggestion:

http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/

There should be another thread where the guy gave step by step instruction using ADB. You also might want to try searching XDA.

NT

PS Hey, found this on XDA: http://xdaforums.com/showthread.php?t=1426244
[TouchPad Development] bryantjopplin:
The tp toolbox recreates the volumes and when you resize everything. Full erase removed them. But no his toolbox image is way more powerful than adb. The amount of commands in it is unreal. They are hard to explain what they contained.
[TouchPad Development] nevertells2:
You mentioned that there will be another TPTB because of your experience. What does that entail?

NT
[TouchPad Development] bryantjopplin:
He said it should be for the next update, not to sure though. But he said it was for to better handle drastic failures and rework a few commands. That's about it
[TouchPad Development] rebel1699:
MANY, MANY THANKS for the update. I have not had to use toolbox in quite a while, and not having to rename the rom/gaps/recovery to get them to pass checks. Much appreciation.

---------- Post added at 09:05 PM ---------- Previous post was at 08:23 PM ----------

I am having a very strange issue. Once I install any android rom, it is shutting down/rebooting at about every ten minutes. This is not the case in WebOS, only android. This started last week after I installed the new PAC rom. Thinking it was the rom, I flashed back to CM12 with 3.4 kernel by invivisiblek. When the problem persisted, I reset the whole tablet and started fresh with new install of WebOS. I left it as a WebOS only system for 3 days, and had no issues. As soon as I installed CM12 today, it started again. I ran CM12 for months without issue. It was only after installing PAC rom that this started. Nothing has helped since. Any ideas what may be causing this? Thanks for any ideas.
[TouchPad Development] DJames1:
I just did the update from WebOS+CM10.1 dual-boot to all-Android with CM11 (4.4.4) using TP Tookbox. As always, thanks to JC Sullins and to the Cyanogenmod folks for making this possible.

For the most part everything initially went ok with the wipe-and-fresh-install update. Just a few issues:

- After reading what there was about Datamedia vs. non-DataMedia, I still wasn't totally sure which was the right way to go when removing WebOS entirely. DataMedia seems to be the default choice, so I just went with that. [cm-11-20150113-SNAPSHOT-jcsullins-tenderloin]

- Everything went fine through the full data wipe and installing Android, but at step 5 when it booted Cyanogenmod for the first time, the big spinning circle froze after about a minute. I gave it 5 minutes to be sure it wasn't going to unfreeze, then I had to reset the TP with Power+Home. It rebooted successfully, and the 2nd time it didn't freeze. I hope I didn't miss anything - wasn't there a step 6 at the end of the Toolbox Install Android process?

- The first thing Android did was update 92 apps. I assume that's ok, but how would I know? [there might be a problem with the Camera app - see below]

So, Android 4.4.4 is up and running now, but there's still a few glitches in this process!

And it turns out that there are a number of problems with this CM11 ROM, most importantly with the camera. But I'll put that in the ROM thread.
[TouchPad Development] nevertells2:
I'm afraid you are pretty much a minority of one when it comes to your comments about data media Roms. The decision among the developers including Google is that using a data media build the natural progression of Android on all devices. You can always leave WebOS removed and go back to the Rom that suits your needs. The thing you have to remember is using any flavor of Android on the TouchPad is highly experimental and bugs are expected and chances are many will never be resolved. If you are one of the many die hard upgraders, then you have to live with what you get. Like I told you in the Sullin's CM11 thread, development on CM11 is done, so it's either go back to the Rom that worked best for you or live with the issues you are currently experiencing with CM11.

NT
[TouchPad Development] DJames1:
??

I said that I used the DataMedia ROM because it seemed to be the default choice now. Isn't that what you're saying?
[TouchPad Development] synchron50:
I own 2 TP's, one with WebOS, one without. Both have CM11 JCSullins latest 011315 ROM and the one that dual boots, I must say, is a pain in the neck regarding media file maintenance. Since webOS can't see the Android data partition sdcard, media files are set up to be shared on sdcard1 with the DataMedia ROM. This, of course, screws up some android apps that insist that media be read from sdcard, not sdcard1. Therefore, I have pictures/photos on both partitions and a lot more wasted space. But lets not forget that the big selloff of DataMedia is no more 50 app limit and dealing with moving large apps to SD Card.

Most people appreciate jcsullins removal of WebOS to gain 2 - 4 gigs of xtra space for Android. To me, removal of WebOS means I don't have to clone my media and have duplicate files. Going forward with Lollipop, etc. this is the way to go.

I can see the tradeoff, though, when it comes to the hardware. To this day, IMO the "beats" sound is better in WebOS with all the popular preware patches. And you mentioned the camera which I agree. The best thing about TPTB is flexibility.
[TouchPad Development] nevertells2:
Sorry, I got the impression you were a reluctant adopter of the data media Rom. Android is what it is on the TouchPad today because the developers managed to implement it. Otherwise, we would not be enjoying the latest versions and having it work as well as it does. Hopefully they will figure out Lollipop and ART. It's a daunting task.

NT
[TouchPad Development] kyzerdroid:
can i install ubuntu with the toolbox aswell?
[TouchPad Development] nevertells2:
The answer is NO! My question is did you read the OP. If you had, you would never had to ask.

NT
[TouchPad Development] branpurn:
Frustrating.

I've used TP Toolbox in the past- but please don't tell me my GApps archive is invalid if you're not going to tell me how you want the filename formatted.

---------- Post added at 06:53 PM ---------- Previous post was at 06:37 PM ----------

I thought the filename BS was sorted out as of v41?

Well here I am on v42 having done a complete erase having to wait on someone to tell me what arcane methodology I have to use to get around a perfectly valid Gapps archive not working.
[TouchPad Development] jcsullins:
Too much attitude; too little pertinent information.

I will tell you this, though: the only significance in the file name is that it ends in ".zip"

Everything is determined by the contents of the zip files instead of basing anything off how they are named.
[TouchPad Development] rebel1699:
[MENTION=2763462]jcsullins[/MENTION]

I noticed in the op that you wrote that install of third os was not yet supported, possibly eluding that it may be in the future. I have a third installed (Arch Linux), and the issue is, of course, /boot size. As a temp workaround, I made copies of all uImage's and put on my sd. That way, if I want to boot to arch, I can just remove another uImage (usually twrp or webos) from /boot and drop that one in. When done, I switch them back. Are you working on being able to raise the boot partition size?
[TouchPad Development] nevertells2:
I guess the $64,000 question is why do you still use WebOS? By removing WebOS, you would free up a bunch of space in /boot. Hopefully enough to allow you to keep Arch Linux there all the time. Mr. Sullins will have to answer you on whether he will ever support LuneOS or not.

NT
[TouchPad Development] rebel1699:
The $64,000 answer is the bt in WebOS is far superior to its android counterpart. I like the fact that I can connect to my phone and place and answer calls directly from the touchpad, as well as receive and send texts. Also, Arch linux needs WebOS present in order to operate correctly. Space is not an issue, aside from boot. I otg to a 250Gb ext hdd when at home, so I dont store much internally. The only space restriction I have encountered is /boot.
[TouchPad Development] mschumacher69:
Are you still using a webOS phone??
[TouchPad Development] rebel1699:
No, never had one. The bt to the touchpad works perfectly with my S4. Answers, calls and sms (map) all work great.
[TouchPad Development] mschumacher69:
How does it work exactly? Do u use some kind of an app that's available on webOS (tablet) and Android (phone) to achieve that?
[TouchPad Development] rebel1699:
All you do is when linking their bt, on the tp you choose to connect as a phone. After that, you just open the dialer app in webos and dial. While connected, incomimg calls will also be routed to the tp, as well as incoming texts. Send texts from tp also.
[TouchPad Development] mschumacher69:
Oh OK, so it's a feature in webOS. It's been a long time since i last used webOS but I do remember there was such a feature now.
[TouchPad Development] nevertells2:
Yeah, WebOS was a fully supported OS hardware wise. Trying to get things working in Android has always been a struggle, no support from the hardware manufacturers. We have always counted on the expertise and ingenuity of the developers. So very understandable why you keep WebOS installed. As to /boot, from what has been said in the past by folks a lot more knowledgeable, increasing /boot is not an option, so we live with what we have. You have it under control, PIA that it is. :p

NT
[TouchPad Development] rebel1699:
Well, not a shock to hear /boot in not size adjustable. Disappointing, but not shocking. Being a measly .5Mb (+/- a few Kb) is maddening. May as well be off by a mile, lol. But like you said, its a pain, but well within manageable.
[TouchPad Development] synchron50:
You sure about that? I was told you can't put TPTB in /boot with a dualboot TP because it won't fit. My WebOS TP with Android boot size is around 29MB. There's plenty of room if it's what you say as I assume you mean 50MB but I always thought it was 30MB, at least back in the CM9 CM10 days.
[TouchPad Development] rebel1699:
I mistyped. I didnt mean to say it was .5Mb, but rather .5Mb short of what I was trying to put in it.
[TouchPad Development] FletchF:
Does anyone know if there is a novacom deb package somewhere that supports systemd?
[TouchPad Development] vqstaphbeard:
Good question. I haven't tried since Ubuntu switched to systemd.
[TouchPad Development] bobcote:
Hi,

I have a problem installing Android 5.1.1 with tptoolbox v42. GAPPS file is always flagged as unrecognized/unsupported.

I first did a Complete Data Reset.

I'm trying to flash:

ev_tenderloin-5.1.1-testing-2015.04.27.zip

FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip

gapps-lp-20150222-signed.zip (which user Medevila said have worked for him here http://xdaforums.com/showpost.php?p=60220727&postcount=1037) I also tried with other versions, did not work.

Can someone tell me if I did something wrong? Is there a solution/workaround ?

Thank you

---------- Post added at 07:05 PM ---------- Previous post was at 06:10 PM ----------

I was able to flash Android 5.0 with GAPPS from my previous post.

I guess now that tptoolbox installed a recovery I can now reflash 5.1.1 with correct gapps.
[TouchPad Development] jcsullins:
Using the three files you mention above, I get:

ERROR: Incompatible GAPPS/ROM versions 5.0/5.1

.. which is quite different than unrecognized/unsupported. This is a check that TPToolbox does to try to prevent errors that happen when you use a GAPPs version that is not compatible with the ROM version you are installing.

Did you not get the error I mentioned above?

Or, do you think the versions it's reporting for the ROM and/or GAPPs are incorrect?

Or, do you think it should allow you to install a 5.1 ROM with 5.0 GAPPs?
[TouchPad Development] bobcote:
I should have changed my post to avoid confusion.

In fact, I first tried with

jajb (http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330) gapps-5.1.x-20150404-minimal-edition-signed.zip

(http://fitsnugly.euroskank.com/?rom=banks&device=gapps) gapps-L-4-28-15.zip

And finally with the one I put in my previous post.

With the two above I got the message I reported. But as you said with the gapps-lp-20150222-signed.zip I got the message you also got. That's how I got the idea to try with a 5.0 ROM.

Sorry for the confusion.
[TouchPad Development] smartinez832:
any links to the 2015-02-25 TP update?
[TouchPad Development] rolltide78:
yeah I'm in the same boat. Someone mentioned to use Recovery to install gapps but I can't even get to a point where 5.1.1 is installed at all without gapps. Toolbox makes me add a gapps file so I'm confused.
[TouchPad Development] nevertells2:
Please explain exactly what happens when you just put the Rom and recovery files in the ttinstall folder. What does TPTB say when you don't include a Gapps file? BTW, which LL Rom are you trying to install? Which Gapps does the developer of that Rom recommend? Which version of TPTB are you using?

NT
[TouchPad Development] rolltide78:
2015-01-08-v42

It says something like invalid number of gAPP files (0) when I do not put at least 1 in there. I noticed in the notes for Toolbox that there is no support yet for no gapp file. I'm not sure if that still applies to the new version.

---------- Post added at 03:59 AM ---------- Previous post was at 03:57 AM ----------

I have tried these files in ttinstall:

gapps-L-5-1-15.zip

ev_tenderloin-5.1.1-testing-2015.04.27.zip

FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip

Then I tried just these 2:

ev_tenderloin-5.1.1-testing-2015.04.27.zip

FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip

---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------

This combination does work but it's not 5.1:

ev_tenderloin-testing-2015.01.03

gapps-lp-20150222-signed

FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14