yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] bryantjopplin:
I fully understand, I was just giving an option for people that want to do it. I actually have been making a ton of the bat files for everything. So I was just in the mood to jack with it.

Sent from my Nexus 6 with Pixel XL build.prop
[TouchPad Development] nevertells2:
It would be helpful if you gave a detailed explanation how you used Nova term to remove the /media volume. That would show some of the less astute users how you did it and might help them try to do it. It's kind of like these users who want to install these experimental new builds of Android is something new and different they want to try. Trying out what you did would be something like that to them also. And don't stop experimenting with your batch files, that's where new ideas come from. Between you and Double Stuff who knows where this thing might go.

NT
[TouchPad Development] bryantjopplin:
I have been working on a write up. The picture I uploaded is basically all that needs to be done.

So basically through my tptb_sauce v1

Step 1. Start tptb_v42 from my tptb_sauce and go through the normal steps of setting up a data/media rom using tptb_v42 and resize the android partitions to were the media volume is the smallest volume.

Unless you need to do full reset first.

e.g. remove largest amount possible from media volume

make cm-system 1800mb+

make cm-cache atleast 500mb+ imo

make cm-data with the leftover

reboot via tptb_v42

Step 1.1 After reboot via tptb_v42 select webos recovery in moboot

Step 2. Start twrp temp and transfer over twrp zip file and flash twrp.

Step 3. Reboot recovery into the newest flashed twrp

Step 4. Load roms and gapps to drive

Step 5. Flash roms and gapps

Step 6. Boot into new rom and setup

Step 6.1 Flash kernel (IMO its needed for 7.1)

Step 7. Boot back into rom.

Step 8. Boot back to webos recovery

Step 9. From my tptb_sauce v1 run nova installer image (option 9)

Step 10. When you see the hp symbol after its load and your pc loads all the driver run novaterm (option 10)

Step 11. When novaterm opens hit File then connect

Step 12. type "lvm.static lvscan" without the quotes

Step 13. Verify there is a /dev/store/media volume with XXX amount of space.

Step 14. Type "lvm.static lvremove /dev/store/media" without the quotes and hit y to confirm deletion

Step 15. Type "lvm.static lvscan" without the quotes again to verify there is only 3 now cm-data, cm-system, and cm-cache

Step 16. Close out of novaterm and hold power and home button to reboot tp and have it boot back to moboot and select webos recovery once more

Step 17. Load tptbv42 from my tptb_sauce v1 and go back to android volumes and assign the remaining free space to what ever you like.

Step 18. Reboot and profit.

Now this also assumes you have novacom installed and everything is correct on your pc. I have novacom installer included as well in my tptb_sauce

MAIN LINK:

http://www.mediafire.com/file/lue5ool8pbasr1w/TPTB_SAUCE_V1.1.zip

SECONDARY LINK:

https://www.dropbox.com/s/wh93cnqyivoall0/TPTB_SAUCE V1.1.zip?dl=0

EDIT : Now added an option to install twrp from running android or from temp twrp without the need of flashing a zip.

I also have been so caught up in learning new stuff lol. I actually have made a multi-menu batch file that does loads of stuff for adb, fastboot, and some other nifty tricks. I can wait for twrp 3.1.0 to get added to our TP's. Its actually 1327 lines so far and still adding more. You should check it out. I will be updating a newer version soon.

https://xdaforums.com/android/software-hacking/tool-adb-fastboot-sauce-v1-one-options-t3579172
[TouchPad Development] nevertells2:
Just a couple of tips, cm-cache does not need to be set to 500mb. TPTB set it to 200mb for all installs and I have never found a case that it needed to be bigger. Same thing goes for cm-system, Flintman recommends 1312MB. Anything over those amounts is just unused space. Maybe with Android "O" or a later version, /system might need to be made larger. When the time comes, that can be done easily with TPTB.

I also noticed that in step #1 you install TWRP and then in steps #3,4 and 5 you use the installed TWRP to flash the Rom and Gapps. Why not just flash all three while the temp TWRP is running the same way DoubleStuff does in his procedure?

NT
[TouchPad Development] bryantjopplin:
You can use the temp twrp to flash but I don't like too. Up too you. Also I just always go higher with the settings for amount as I tend to install a lot if apps as system apps.
[TouchPad Development] RolandDeschain79:
Nice

Lol'd at this, good on you for contacting imarck90 and taking the time to do some TouchPad tinkering. :cool:
[TouchPad Development] Dellboy17:
I'm a little confused by step 2 " transfer over twrp zip file and flash twrp" - where do I find the TWRP zip file? - I've reached the stage where I've rebooted the tablet into TWRP but frankly I've no idea where to go next, I've done several Android installs in the past so I'm not completely new to it...
[TouchPad Development] bryantjopplin:
Flintman offers the twrp file. Its in the forum somewhere. But didn't I add install twrp from twrp option on the main menu of the program? You can do the flash or use the program to. All the program does is push the twrp.uImage to the boot folder and chmod the privileges. So its like the same thing as flashing a zip. I can get a screenshot of the option on the program if needed.
[TouchPad Development] bryantjopplin:
Here it is. Found it on dev base forum but am not allowed to link other forums so here is the direct download.

http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-3-24-17.zip

Also the next option would be to flash twrp and/or reboot back to the flashed twrp and then install android and gapps of your choice.

Let me know if anything else is confusing.
[TouchPad Development] cleverdicky:
Is anyone here that could help with a toolbox problem. Ive completed most steps for a fresh install.

Wiped, resized etc. Installing android is causing painfull headaches though.

installing ev_tenderloin 7.1.2

update twrp (old ver but latest I could find)

And gapps - grrrr

Dont even use / want gapps but toolbox wont complete without one. Trouble is, I cant find one that works.

Everytime after copying files over it checks them and fails!

"Error Incompatible gaps/rom versions None /7.0"

"blah blah aborting."

Must have tried a dozen or so gapps now
[TouchPad Development] DoubleStuff:
Try this "alternative" method of installing Nougat, and you should not get the incompatible error messages, give it a test and see what you think...

Click the below link and follow the nice easy to complete steps, and also a easy to follow video!!

Whats not to like!!

Easy as do, re, me and one, two, three, but in the end.... you tell me!

https://xdaforums.com/hp-touchpad/general/rom-guide-alternative-method-to-install-t3575861
[TouchPad Development] cleverdicky:
Thanks will give it a go.

Can i avoid installing gapps using this method?
[TouchPad Development] DoubleStuff:
Thats an interesting question about the gapps, well because in my code I avoid the TouchpadToolbox install which like you said requires the gapps, the alternative install is done with the temporary load of TWRP, so this could be possible to avoid the gapps, but I never tried it without the gapps, after the complete data reset.

So please if you can do 2 tests and report back to us:

1) first try to install just with TWRP, and ROM and avoid the Gapps and report back any errors.

2) second if that fails, try it using TWRP, ROM and Gapps.

Thanks for being the tester!!
[TouchPad Development] cleverdicky:
Rebooting now :) Thank you

Got the evervolve logo so appreciate it may still be a while before comple.

But the install was sweeet from usb onwards. No issues, easy peasy, and 'without' gaps.

Hadn't flashed anything for a while so a bit shaky.

Really liked how running the temp twrp bat file popped up on the tablet. Supurb

oops, finished booting - that was quick! time to play :)

Sorry havn't tried with gapps - no need lol
[TouchPad Development] alefisz:
I keep on getting "Error: Invalid number of ROMS (0)"
[TouchPad Development] bryantjopplin:
That's because it is a newer ROMs that's not compatible with the this program. There are multiple ways to make it work. Older ROMs work better.
[TouchPad Development] alefisz:
Thanks for the reply. Do you know where can i find the older ROMs?
[TouchPad Development] bryantjopplin:
You can basically follow this https://xdaforums.com/showthread.php?p=71589964

If you want to install newer ROMs and older ROMs. Just follow the normal tptbv42 instructions instead of the install android portion and continue on from my step 1-6. Anything else after is optional. Its an all in one tool I created that does a lot.

Easy as load tptb, full reset, resize volumes, reboot to webos recovery, load twrp, install twrp zip, ROM, and gapps. Should be very easy.
[TouchPad Development] alefisz:
Im having a little troubles with that. Im currently trying to use the TPTool Box from this link https://xdaforums.com/showthread.php?t=2756314 . Just need copy the right "Rom, Recover and GApps zip files to the 'ttinstall' directory".
[TouchPad Development] bryantjopplin:
Try these

http://downloads.codefi.re/jcsullins/cmtouchpad
[TouchPad Development] DoubleStuff:
Well thanks for your good feedback, Nevertells2 and DoubleStuff worked hard on the documentation for that link, and when users like you ( who admit their a little rusty ) say that this alternative method was "easy peasy". Well for the self proclaimed EverTells team, that is "gold, baby, gold"!!! :highfive:
[TouchPad Development] alefisz:
So I was able to get the CM-11-20151027-snapshot and update-cwm-jcs-dm-tenderloin-20141231 files in. Which i think added the recovery and Rom. I still need GApps. Would you by chance have GApps zips I can add ?

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

So I was able to get the CM-11-20151027-snapshot and update-cwm-jcs-dm-tenderloin-20141231 files in. Which i think added the recovery and Rom. I still need GApps. Would you by chance have GApps zips I can add ?
[TouchPad Development] bryantjopplin:
Try this

https://r.tapatalk.com/shareLink?ur...share_tid=2997368&share_fid=3793&share_type=t

[GAPPS][CM11/12/13/14][4.4.4][5/6/7.x.x] Delta Gapps With Modular Addons (All DPI)
[TouchPad Development] alefisz:
I managed to find another link about an hour ago. But thank you so much for all your help. It worked!
[TouchPad Development] bryantjopplin:
That's great. Enjoy
[TouchPad Development] :
is it normal that there is no possibility to backup the system, I mean webos with the downloaded apps? That's mostly to run it in the future in a virtual machine if possible or trying to extract the installed apps and make an independant package or anything. Only "media" partition is accessible. Here on webos nation one person talk about the different partitions that should appear if the debug version of bootie is used. http://forums.webosnation.com/webos...222063-win-7-64-bit-novacom-installation.html and http://forums.webosnation.com/hp-touchpad/311955-bootie-mode-allows-image-backup.html
[TouchPad Development] bryantjopplin:
The novacom installer image should get you there to were you need to go. Basically recovery mode and bootmem the image then Nova term into the tp. I wouldn't know the commands to pull anything but that gives you full access to everything as far as I know. I have it included in my program if you want to dig into it and let us know what you come up with.
[TouchPad Development] :
image? I have installed the novacom driver, it let me use tp toolbox as described here, isn't it the same?

nova term? novacom also provides a terminal? and that runs from the touchpad?

which program?
[TouchPad Development] bryantjopplin:
https://www.mediafire.com/download/lue5ool8pbasr1w

Run the installer image from recovery from the program, you will see a HP symbol on the to and it will sit there. From there run Nova term from the program and choose file and choose connect to device. It might take some time to install the drivers. Fr there you will get a terminal that can do all kinds of things but I'm limited in what it can do. Webos nation might have more info. I hope you can figure out what your looking for.
[TouchPad Development] :
what is the filename of the "program"?

I downloaded and extracted your zip file, it seems to contain several windows executable files.

I think you suggest running the remote terminal as root from a usb connected computer. I just did it in linux with the "universal novacom installer" drivers. It contains three programms among which novacomd is intended to link to the device and novaterm to be the terminal of the touchpad internal linux system.

In fact i found the full procedure here : http://wiki.rootzwiki.com/HP_Touchpad. As they mention it needs to enable the dev mode through some sort of combo looking like those used for sony playstation.

That's interesting as I can locate the flash disk, and how it is partitionned, but is it possible to access it without having the system sitting on running? i.e. using the bootie mode. All I want is an image of the flash disk. When the system is running there are a lot of files open and when I'll want to restore the system it certainly will not work. It would have been nice to integrate this simple thing into the tp toolbox.
[TouchPad Development] bryantjopplin:
In the zip there is an exe and a files folder. Don't choose anything but the exe. It is only for windows BTW. You don't need the novacom installer if you have it installed. You want Nova installer uImage and then Nova term into the uImage. You have to boot to the uImage from bootie (USB symbol).

---------- Post added at 01:05 PM ---------- Previous post was at 12:59 PM ----------

Also you don't need the tp booted into an os at all. You can do this from Linux but you need the installer image out of it and placed into the directory of novacom. Then you can novacom boot mem the uImage. Then novaterm should be installed in your novacom directory.
[TouchPad Development] ajimenez0777:
hoping someone can help me. I'm trying to dl the new android on my TP but i'm running into the problem of a GAPP file. I have the Toolbox installed but when i get to the point where i need the GAPP, ROM and Recovery file I'm stuck. Everything I'm finding is really old and the links are bad. I'm working on a Mac. Help if you can please! I'm trying to resurrect the TP for my son for Amazon Underground. TIA.
[TouchPad Development] bryantjopplin:
http://downloads.codefi.re/jcsullins

You should find everything you need here. Also to get the newest android you will have to read like the last few pages as everyone ask this same question over and over. I would definitely watch some of these videos from Roland deschain https://youtu.be/ISWZ0c48gNA
[TouchPad Development] silvbm:
How long is step "Checking zips" supposed to take? I'm waiting for over half an hour now with an 32GB.

I downloaded the zips from OP, and did not change the names. As far as I can see, the filenames were according to the naming scheme.

Thank you very much jcsullins for this great tool!!!
[TouchPad Development] jcsullins:
It shouldn't take more than a couple mins to check the zips. If the filenames were incorrect, it should have gave an error prior to "Checking zips".

Sounds like it's hung for some reason. Just hold Power+Home for 15-20 secs to reset, then reload tptoolbox and start over.

BTW, I'm curious, did you do a "Complete Data Reset" prior to trying install or not?
[TouchPad Development] silvbm:
No, did not do a "Complete Data Reset", but I rebooted into your TWRP Recovery and wiped everything there ( Didn't want to go through the hassle of setting up WebOS, as I am still using it from time to time), and now it proceeding with install :good:.

Thanks a lot for this handy tool!!

EDIT: Everything went fine, CM11 is up and running :good:
[TouchPad Development] nevertells2:
[MENTION=4461461]silvbm[/MENTION], what finally got your install working?
[TouchPad Development] johnsmith33584:
Just curious, with all of the pieces of WebOS removed from the boot partition/folder, wouldn't that leave enough room for your touchpad toolbox?

John
[TouchPad Development] silvbm:
As proposed by jcsullins, I held Power+Home for 15-20 secs, then went into TWRP Recovery and wiped everything possible there. Next step was restarting Android Install through TP Toolbox, which went fine.
[TouchPad Development] mpgrimm2:
Something to keep in mind: It appears that if someone performs a full recovery restore from before using the TP Toolbox that it may restore some of the /boot files from webos before it was removed as I found out in post 74

Went through the install again to make sure my /boot was devoid of WebOS and also verified that you can't use the TP Toolbox to install only Jc's DM recovery for installing/restoring a ROM afterwards. The prerequisites require all 3 files (recovery, ROM & Gapps) as previously stated for the android install.
[TouchPad Development] johnsmith33584:
Yes, [MENTION=4328058]mpgrimm2[/MENTION],

I saw your post about that. That should probably get a big RED warning in the OP or one of the first posts not to do that. I'm wondering with a partition that consists of around 30mb space, how much is freed up by removing all the WebOS files and how much space do the toolbox files need. The /boot on my TouchPad with JC's CM11 installed along with WebOS still has 4.66mb space free. Since I have not used his toolbox to remove WebOS, I have no clue what files are removed and which ones still remain. I count 32 files and folders in /boot with Android and WebOS installed. It's just a curiosity question. Mr. Sullins is driving this boat and we are all just along for the ride. So whatever he decides to do is fine with me.:D

John

---------- Post added at 01:30 AM ---------- Previous post was at 01:25 AM ----------

For those who want to keep WebOS, using ACMEUninstaller2 to completely remove the old Android installation and reset the partitions back to WebOS only condition, then running the toolbox to install Android would be less problematic, at least from your experience it seems that way. :fingers-crossed:
[TouchPad Development] BIGSimon:
This is what I get on my Touchpad with a complete data reset and only CM11 installed
[TouchPad Development] gradular:
Great! The bin file is only about 12 megs. Ill have to play with this over the weekend.

You can restore pre tool backups if you do a custom restore and uncheck boots, I think.
[TouchPad Development] swear0730:
Posting this again because nobody posted any ideas for me and its getting buried in the thread. Not complaining as nobody here owes me anything, just hoping somebody sees this who has an idea.

Additionally, when I go into CWM and try to wipe caches it fails on the when it tries to format the cache.

First error is E:format_volume: make_extf4fs failed on /dev/store/cm-cache
[TouchPad Development] jcsullins:
The metadata for the Logical Volumes is corrupt. Pretty much anything will fail until that gets rebuilt (i.e. Complete Data Reset).

One of the big objectives with tptoolbox is that it check everything for errors and report them appropriately. It turns out that I needed to ignore any errors for the first command that gets run when a "Complete Data Reset" gets run. I didn't expect that command to fail when the metadata is corrupted, but apparently it does.

Also, those "lseek" errors make me suspicious that the partition information might be incorrect for the device (i.e. tpdebrick was run with incorrect size, perhaps). Those errors may simply be a symptom of corrupt LVM metadata, however. I'm adding a check for inconsistent partition info into "Complete Data Reset" to catch if it's that.

These fixes will be included in a new version of tptoolbox this weekend.
[TouchPad Development] johnsmith33584:
So with over 18 megabytes free, is that enough space for the toolbox to reside in /boot instead of putting it somewhere else?
[TouchPad Development] dragonfuego:
84B2111103834192U

Thanks, great work.
[TouchPad Development] mpgrimm2:
Another potential "thorn" in this idea is that since there isn't a standard naming convention for Android ROM (kernel) files in the /boot that there is the potential for ROM files to be left behind when switching ROMs and use up space i.e. from Evervolv, or AOKP to CM11.

Some of that was detailed ... post 5 here

I'm curious what [MENTION=2763462]jcsullins[/MENTION] thoughts are on TP naming conventions from that post even though it sounds like he has a different volume in mind for TP Toolbox.

6/1/14 Edit ( [MENTION=5870418]johnsmith33584[/MENTION]) :

Added Picture of boot size & files using TP Toolbox with before/after restore of prior recovery backup
[TouchPad Development] gevans01:
Thanks jcsullins for the explanation. I was currently running 2.6 kernel (4.2.2 rom) I was hoping to upgrade to kitkat with 3.0 kernel but I guess I need to wait. I didn't see any articles telling me 3.0 isn't ready for 4G. Maybe I need to read the notes again.
[TouchPad Development] johnsmith33584:
I would think that would only be a problem when using TPtoolbox to dirty install a different Rom. Maybe Mr. Sullins can put a routine in his toolbox script to check for and erase any OS.uImages in /boot when dirty installing a Rom.
[TouchPad Development] BlvJohn:
Hi gevans01:

As far as I know, my CM10 builds for the TP 4g are the latest with full MBM support (Ericsson or Sierra). Working now on CM11 datamedia builds using the 3.0/3.4 kernel with a lot of help from jcsullins and flintman. If you are not already aware, I am moving all my TP 4g platform info and builds here: http://www.hptouchpad4g.com. I will put up a link there when a CM11 build for the TP 4g is ready for testing.

John
[TouchPad Development] johnsmith33584:
Hey guys,

How long does it take from the time you run the tptb_v40_win.bat to when the TPtoolbox menu appears?
[TouchPad Development] tivofool:
It definitely takes a while. I thought something was wrong. Maybe 4-5 minutes? But I wasn't timing it, I just remember wondering what was going on then finally it worked.
[TouchPad Development] :
So the file is "FILES/nova-installer-image-topaz.uimage"

In linux in my universal novacom installer folder I put the uimage file. Here along with it I have "novacomd", "novacom", and "novaterm", and a folder, named "scripts". The latter containing scripts to launch novacomd deamon.

novacom boot mem?

I had to explore the tp_toolbox script for linux to understand this since novacom -h does not mention anything about "boot" subcommand.

so I did : ./novacom boot mem:// < nova-installer-image-topaz.uimage

The tab which was in bootie mode and usb connect and link enabled with novacomd started to display the hp logo in the middle of the screen and stayed like that. Then I ran the already there novaterm and got a "root@webos-device" prompt:/# ".

I think I'm where you meant. From here I have to find a way to communicate with the host system.
[TouchPad Development] bryantjopplin:
Hey you did it. Good on you for finding it through my horrible instructions haha. You can use http://webos-internals.org/index.php?title=Bootie

Like I said this should get you everything you need. Well at least I think. Let us know what you find out. I believe you can use "novaterm pull" command. Sorry for not making it easier for you as a Linux guy.