yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] shumash:
The TTINSTALL directory is in /data, the TWRP directory is in /media, two different volumes, although they are really all part of the internal storage of the TP. You are correct that the TTINSTALL directory is created by TPTB when the files are copied from the PC to the TP, but the TWRP directory is created by TWRP. If you have ever used TWRP, it will be there in /media, and it contains TWRP config data and "nandroid" backups. You can't rely on it being there for users that only used Clockwork recovery. As far as removing the TTINSTALL directory, it's purposely unavailable inside the ROM system (unless it's mounted through a terminal). It's kind of nice to have as insurance for when you trash the system. I store my latest TWRP, ROM, and GAPPS there since CWR and TWRP can both read that directory, and I can install from there if something happened to /media.
[TouchPad Development] nevertells2:
Hey Shumash,

You have ttinstall and twrp reversed. TPTB does create ttinstall in the /media volume and the twrp folder does not get created until TWRP is run for the first time and that resides in /data.:)

NT
[TouchPad Development] shumash:
Yup.:good:
[TouchPad Development] DoubleStuff:
So from what I gather from the two comments above from Shumash and NT, the TWRP directory will always be created when my bat file loads, and starts the TWRP recovery? Am I correct? Because this is an important step, and in my various tests this is the behavior thats been observed, but I was not sure if TWRP dir was always there, or just got created with start of TWRP recovery.

Thus then users can copy the ROM, GApps and TWRP zips into this TWRP directory on their PC and flash.
[TouchPad Development] nevertells2:
Hey DoubleStuff,

OK, I get where you are coming from. Having read and commented on Shumash's post, I do now remember that a TWRP folder does not exist until the first time one uses TWRP to make a nandroid backup. I'm not quite sure how you are seeing a TWRP folder in the /media volume where the ttinstall folder is created by TPTB, I'm looking in my /media volume right now and TPTB did not create a TWRP folder there. Regardless, I like the method you have created to cleanly install a newer Rom, Gapps and Recovery that are not recognized by TPTB. As to where to put your batch file and the .bin, I have always put the TPTB files in the Palm, Inc folder for simplicity sake. But it's no big deal if you put them somewhere else since you set the path to find them where ever they reside. I'm also pretty sure because TPTB was created before all these new Roms came around, it does not properly set the size of /system for MM and Nougat. I do seem to remember reading that Flintman did include some code in his Roms that caused TWRP to resize /system correctly when flashing a Rom.

With regards to an "O" version of Android on the TouchPad, we'll just have to wait and see. I said that we were done with MM, but Evervolv proved me wrong. We are down on only one development team that is still supporting the TouchPad. And I just read an article the other day that most devices out are still waiting for an official version of Nougat from their phones manufacturer. With CyanogenMod gone now we'll see how well Lineage OS does supporting the number of devices that CM used to support. Only one guy released a version of Lineage OS(CM14.1) for the TouchPad and took it down pretty quickly.

Keep up the good work.

NT (aka. EverTells) :D
[TouchPad Development] DoubleStuff:
Forgive me NT, but I want to understand this correctly....About data, media and TWRP...

In my original post I said something like...

"...Once in TWRP Recovery, Copy ROM, Gapps, and Permanent Recovery zip files into the /TWRP directory on Touchpad. Full TWRP directory is /Touchpad/InternalStorage/TWRP on PC." -DS

Then you replied, "...Rom zip and Gapps zip and the TWRP.zip residing in this \TWRP folder located in the /media volume on the TouchPad. Do I have this right or am I having trouble understanding your instructions?" -NT

Because I said /TWRP did you interpret this to mean "media" because of the slash? Because on the PC the directory looks like this /Touchpad/InternalStorage/TWRP...which is on SDCard right? Sometimes I just type /Directory name to indicate its a directory. I am not saying its off the root.

Also you spoke about System partition size settings...I don't think the 7.1 ROM resize system partition because Flintman in his OP said this:

**REQUIRES 1312MB System Partition.

This is very easy to do via JCSullins Toolbox

...and some tests, setting System to some random number like 1344 MB, and after installing 7.1 ROM I checked system size again and its still 1344 MB....I also set it to a size below 1312 MB, ( 1288 MB ) and it stayed at 1288MB.

I might test this by running my bat file, and not resizing any partitions ( media, cache, data and system ) and see what happens...

On the other hand I better not, until you get back to me....LOL
[TouchPad Development] DoubleStuff:
Yes your right!!

Dude! , NT, seriously after reading your post a few times I had to lay down for bit! LOL My brain hurt, you sure have alot of good information in your head!! :good:

Also if I remember right you only have one TP, and you have Sullins 4.4.4 KitKat installed, so you don't download nightlys like some testers of 7.1. But to help others in the past you have installed higher versions, but always go back to KitKat with your backup.

After reading your post and now understanding about data and media partitions, yes TWRP is created by TWRP recovery and its located in the Internal SD card, called data.

Using 'ROM Toolbox Lite' lingo so we both understand, on the Touchpad its the directory /sdcard/TWRP and also /data/media/0/TWRP which are the same directory. And yes your able to browse to those folders from TWRP 3.0.3 recovery.

On the PC once you see the touchpad icon...

Its the folder called /Touchpad/InternalStorage/TWRP and when you drag and drop files to this directory you will see them in /sdcard/TWRP and /data/media/TWRP. Then from TWRP install button you will be able to browse to these folders, and add, and flash the zips.

From our 'healthy' conversations I was able to edit and improve my original post, if you want to read through it again, and help improve people to understand it more, that would be fine.

Link #956
[TouchPad Development] nevertells2:
Wow, you were really paying attention while reading in these threads. You are right on every count. I always go back to Sullin's CM11. It is by far the most complete, mature, stable Rom around.

Good job, your post is much easier to understand and follow. I am curious, have you run into the situation that I did, while copying the three zips, with having to force a hard reboot of the TouchPad when TWRP goes to sleep and won't wake up? If that is the case, you might warn folks that if that happens they will have to force a reboot by holding power and the home button together and then run your batch file again to perform the installation. It happened to me twice while confirming that when TWRP is running you are able to copy files from your PC to the appropriate folder on the TouchPad.

The only other suggestion I can offer is it really isn't necessary to copy the zip files to the /TWRP directory. They can be anywhere on the TouchPad and the person installing Android can browse to the necessary folder. Since most people who have used TPTB are used to copying the needed files to the ttinstall folder on the external SD card, I would suggest you change your instructions to copying them there. It's the same step they would do if they were using TPTB to install android. The ttinstall folder is created by TPTB so it's there for the using. And you avoid mixing your three zips in with the other folders and files in the TWRP directory.

Lastly, once you have things the way you want, you might consider posting your instructions in the Devs Base Evervolv threads for the Touchpad. I'm sure you are aware that Evervolv is not updating or posting in this thread anymore. It's been a good place for us to brainstorm together, but if it had been an active thread, we might have been asked to take our conversation elsewhere or to PM's. I'm not sure how many folks still stop here anymore since Devs Base came into existence.

Later,

NT

---------- Post added at 10:34 PM ---------- Previous post was at 10:17 PM ----------

Will someone here who also posts in Devs Base please ask the administrator to reset my account. For some reason I was having a problem logging in and exceeded the login attempts. It says to contact the administrator, but when you click on that link, at that page it says the administrator page is disabled. BTW, I'm just nevertells over there, not nevertells2.

Thanks,

NT
[TouchPad Development] DoubleStuff:
NT,

I have run into the locked HP Touchpad many times, even during my last test, but when I unplugged it from the PC, it got unlocked. Then it locked again and usually if you press power or home, and wait for a while ( 3 mins maybe ) it will come back when you touch/move the TP. I have had this issue even during nightly flashes. Sometimes just play around with power and home button, and it will come back, without hard reset, but you have to wait, and touch and move the touchpad with your hand, just hitting the screen will work.

I just now tinkered with the TWRP settings->screen, and there is a toggle to disable screen timeout, or increase the time to timeout. I think the default is 60 seconds, I now increased mine, but I don't think you have to do a hard reset, just play with buttons and wait. But it can be disconcerting, because the buttons are not responsive and most users would think its dead.

Now to be precise, the ttinstall is created by TBTP, but only after selecting "install ROM" from the TPTB menu, so in my method this never gets selected, hence the ttinstall directory never gets created automatically. But the good news is if you select "Mount Media Volume" then the PC will have an empty HP TOUCHPAD drive ( F: drive on my PC ) and you can drag and drop files there. Then unmount, resize Android partitions and run my special TWRP bat program to load TWRP recovery. Once in TWRP the default directory from INSTALL button is /sdcard/ but if you go up ( up level ) once, then select /external_sd you will see your zips to flash.

Is a tough decision how to direct users, might be easier to use TWRP directory because its the default that comes up, but like you said not something they are used to. Plus using Media, an extra step is involved because you have to select "Mount Media Volume", but using the TWRP internal SD, user don't have to select that "Mount Media" option. When TWRP is loaded, looking on the PC the touchpad drive shows both internal storage and external storage, which after a complete data reset is very clean, except for the nice TWRP directory in internal storage.

I did post to devs-base now, but I am having trouble uploading the zip to that site, giving me this error...

ERROR: "Sorry, the board attachment quota has been reached."

Sorry to hear about your account, I have registered now, so let me know if you want me to contact anybody, or if your up and running now.
[TouchPad Development] nevertells2:
Where you tell the user to copy the files is your call, I was just making suggestions. Was not aware that the ttinstall folder was created during the "Install Android" step. They could copy them to the root directory if they wanted. Just as long as they know where to find them during the TWRP install. I think if you check, once TWRP is running, you don't have to Mount Media Volume. That is only a step you have to do if using TPTB. Just to be clear on this, plug the TouchPad into the PC, put the TouchPad in WebOS Recovery( Big USB Icon), run your batch file and that starts TWRP. Start Windows Explorer on your PC and it should see the TouchPad and the two folder on it. Copy the three files over to the TouchPad. Just had a thought, once the user is connected between his PC and the TouchPad, he could use Windows Explorer to create a folder on either SD card to put the three files in. My thoughts on this is making it as easy as possible for the user to find the files once the starts the install process through TWRP.

The story on the Devs Base account is I had trouble logging in yesterday and made too many attempts. and got locked out. The message says to click on a link to contact the administrator and when you get there, it says the administrator account is disabled. So there is absolutely no way for me to contact them. Hopefully if you use the Quick Links link at the top of the page and try to leave a message for one of "The Team" or post something in this thread: https://devs-base.com/viewtopic.php?f=46&t=44 , maybe one of the Evervolv folks can contact the admins. It seems to be the busier of the two threads.

Thanks,

NT
[TouchPad Development] DoubleStuff:
Hello NT, I had already done all those experiments you said in your post and I had success in all and it helped me understand about data and media better too. Well I posted on dev-base lets see what the testers give for any further advice, but essentially you gave great advice and tips and we pretty much ironed out the rough edges.

About dev-base, I gave a PM to a guy elginsk8tr....and here was my message to him...

Hello elginsk8r, I was over at XDA, and a guy named "Nevertells" told me he can't get into Devs-Base and for me to contact somebody....Here is his SOS message...Are you the right person or should I go to JMZ admin guy?

Nevertells says,

The story on the Devs Base account is I had trouble logging in yesterday and made too many attempts, and got locked out. The message says to click on a link to contact the administrator and when you get there, it says the administrator account is disabled. So there is absolutely no way for me to contact them. Maybe you can contact one of the Evervolv folks who can contact the admins.

update 5:15pm - The wheels of justice are turning, Elginsk8r contacted me, and told me to contact JMZ who is an admin, he is the same guy I contacted for the attachment issue I am still having.
[TouchPad Development] nevertells2:
Thanks DS. I just finished reading your post over on Devs Base and found this: "1) Copy ROM, Gapps, and Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP directory on the PC." Shouldn't read

"1) Copy ROM, Gapps, and Permanent Recovery zip files into the /Touchpad/InternalStorage/TWRP directory on the TouchPad."

I would also change #2 to read, do not disconnect the USB cable until completing steps #3 and #4.

NT

Update 5:22pm, Thanks again for the help with the account. Hope you get your attachment issue resolved. :)

And BTW, your instructions are looking good. Much easier to follow than when we started out. :D
[TouchPad Development] DoubleStuff:
This is an interesting question, my thought is this: When your on the PC, and double click the Touchpad icon drive

you can drill down to /Touchpad/InternalStorage/TWRP and place zip files into this directory, and by doing so it will transfer the files via the cable to the same directory mounted on the touchpad which is /data/media/TWRP.

I see them as the same directory, but one is mounted on the PC, the other is on the Touchpad..

I got it I maybe should say, "touchpad directory which is mounted on the PC" !!

What are you thoughts on this? Think out loud? So I can understand your reasoning..
[TouchPad Development] nevertells2:
I guess it's just semantics DS. In the Android world, when you mount a volume it's on the

Android device so it can be viewed and accessed by the PC. If a volume is not mounted,

the Windows Explorer will not see it. The developers kind of resolved this issue with the

MTP mode which keeps the TouchPad mounted all of the time. Before, you had to mount

USB, copy files and then unmount USB. If you forgot to unmount the TouchPad, you risked

causing file corruption. With MTP(media transfer protocol), no unmounting required.

Does that make sense?

NT
[TouchPad Development] DoubleStuff:
Yes, good info! I will say, "to the mounted Touchpad volume"

---------- Post added at 06:09 PM ---------- Previous post was at 05:41 PM ----------

NT I made this change in another way, I put disconnect after the last step, but I am curious cant you disconnect the cable once the zips are copied? Because now everything is on the touchpad and you don't need the PC anymore....Comments? Why do you say its the last step? I want to know your reasoning....

In fact I just tested it by pulling out cable after zips where copied into TWRP, and TWRP install button works fine. So I would like to know why you want cable plugged in for an extra step...
[TouchPad Development] nevertells2:
I never tried disconnecting the cable while the install was running just on the chance that it might bugger it up. But since you have tested it, guess it's OK. And you are right, once TWRP is launched by your batch file and the zips are copied over to the TouchPad, there is nothing left for the PC to do.

I looked at your instructions over on Devs Base and they look good. I wonder if you are getting that error because of all the other links in your post? I just thought of a temp work around. Add the following to the bottom of your post in Devs Base: " Since I am unable to add the link to my doubleStuff_v02.zip file, most of you should know Evervolv's/Flintman's old Nougat thread over in XDA. You will find a working link in post #956. Once I get this issue resolved here, I will include it in this post."

This will allow the folks in Devs Base to start testing your instructions.

NT
[TouchPad Development] DoubleStuff:
No the links are not the issue, because at first I did not have the links there, just text, and could not attach zip file. I have put a PM to the admin JMZ about you, and my attachment issue. He has not PM me back, but I will wait at least 24 hours.

I wonder how dev-base would feel about me putting a XDA link in their forum?? I know XDA does not like it, and you know me and you we are "rule followers" :laugh:

Did you see I put comments now about different volumes like data and media, and gave them a heads up about the TWRP going to sleep. But I like a good clean post and not much extra clutter but I think that is good needed advice, especially for newbies.

I am anxious to have dev-base people test it....although nobody has responded yet, my post had been the last post since noon! Most of them are pretty knowledgeable and probably don't want to start from scratch, and risk running a BAT file from a guy with 2 posts!!! LOL

Thats why I hope RolandD gives it a thumbs up, and can start the ball rolling.
[TouchPad Development] nevertells2:
yeah, XDA goes all hyper if you post a link to another forum and removes it. What I am suggesting is just mention to the folks in Devs Base can find your download over in the Nougat thread in XDA until you can get the issue resolved in Devs Base. Hopefully this will get them testing in the mean time. I don't think the admins would object to doing something like that. When I said link in my last post, what I meant was your download. BTW, I have been in touch with Roland and he is waiting for the instructions to get sorted out. I told him that he should have a second read, that you have done a lot of work on them.

OK, signing off for the night, be back tomorrow.

NT
[TouchPad Development] sting5566:
Try flashing everything with the new recovery, not the toolbox.
[TouchPad Development] arongriffis:
Thanks! Your clue led me to http://xdaforums.com/showpost.php?p=68590890&postcount=54
[TouchPad Development] flintman:
I glad 6.0 - 7.0 dirty flashed worked. yes you can dirty flash. I usually dirty flash unless I have issues.
[TouchPad Development] olsent:
seems ok

I did the 6.0 to 7.0 via dirty flash and now did the dirty flash for this update and everything seems to have ended up OK.
[TouchPad Development] tpuserhp:
I dirty flashed the latest build on top of the 0906 build and got the following message:

E: unknown command [log]

But the install zip was successful.

Will reboot and check.

Thanks!
[TouchPad Development] rebel1699:
You have already asked this and been answered. The recovery is in the very first post (op=original post)
[TouchPad Development] muerte33:
I already was on the 3.0.2.0 recovery from the old 6.x days, but I tried to install the newest one on page 1.

It gives me a zip file verification error and fails.

I have downloaded it twice with the same error.

Maybe I am running the current version?

I went ahead and updated the ROM to the newest version and Bluetooth works now!

I did get some kind of weird e:logs error when updating to the current ROM using TWRP, but all seems good.

Thanks to all !
[TouchPad Development] flintman:
You will get that error on the older 3.0.2.0 TWRP recovery hence the new one. What do you have in your boot partition. The newer recovery is larger so there maybe no room. If you have terminal install on your TP. Type 'df' and you will see how much space is left in your /boot partition. I can shrink the ROM boot.img but performance is affected so I don't want to touch that any more then I have. Ill see if I can shrink recovery any more. Let me know what you have left for space in /boot
[TouchPad Development] Nomad1600:
Just did the update to 9/9, after a nandroid and wiping dalvic and cache. No issues with download and booted up fast and fine. Will obviously need to let it bake in for a day or so before seeing if battery has been improved, but its slick as snot and nice seeing the Toolbox in Settings. Thanks again Flintman.

One thing I am noticing, not with the ROM, but with the new twrp (in the OP)... seems to take a longer time firing up... noticebly longer on the initial twrp screen before showing the twrp options. Anyone else seeing this? Not a biggie, and the twrp does everything without an issue.
[TouchPad Development] rebel1699:
Flashed 09-09 with no twrp errors at all. Confirmed bt is working properly. Still seeing fairly frequent screen freeze that require screen off/on to resolve. Great work on the quick bt fix flintman.
[TouchPad Development] flintman:
Can someone get a log after the screen freeze will be great. Im trying to catch it but im rebooting and installing too much to experience it.
[TouchPad Development] heavyt:
Screen freezes for me to, but not enough for it to be a show stopper.:good:
[TouchPad Development] rebel1699:
Sure thing

Definitely not a show stopper. Small bugs like this are to be expected with such a new rom, especially on a device of this age.
[TouchPad Development] muerte33:
Here is what it shows:

Filesystem 1k-blocks Used Available Use% Mounted on

/dev/block/mmcblk0p13 32745 28324 4421 87% /boot

But it is giving me a zip file verification error, there is a check box to ignore the zip signature verification this in TWRP though.

This new TWRP recovery is only 9.08mb

Here is what it says:

verifying zip signature...

Zip signature verification failed!

Error installing zip file /sdcard/download/flintman-twrp-touch-data_media-selinux-f2fs-3.0.2.0-09-06-16.zip

Updating Partition details

...done
[TouchPad Development] flintman:
Yes sorry misread its not a signed zip. So uncheck
[TouchPad Development] muerte33:
That worked!

Since it is the same version, I don't know whether it updated, but it looked like it did.

I really appreciate you getting that BT fixed so fast

So many people use it for keyboards, external speakers, and mice, that it is almost a deal killer when it does not work!

THANKS Flintman!
[TouchPad Development] rebel1699:
For verifying in the future, just go to settings-about- and build number will reflect current build
[TouchPad Development] muerte33:
In TWRP 3.0.2.0 did not see an about under settings.

Inside the evervolv build there is, but it does not show the recovery version?
[TouchPad Development] rebel1699:
Sorry, I misunnderstood the post I replied to. Please disregard