yashsingh1/xdaforums huggingface dataset:
[TouchPad General] mpgrimm2:
Yep, file system corruption appears to have been the problem. I also saw something about not being able to set "set_metadata_recursive" or something like that and some sort of "error 7", which I recall several recoveries doing that around the time we switched over to /data/media builds. Ultimately TpToolbox fixed the corruption and got me back up and running.

Sorry for the confusion. I do a full (custom*) backup and then just restore the "/Data" partition if needed during an upgrade of the same ROM series like you mentioned (or just wipe /system & /cache), but...

I had several issues with that process this time ('dirty install') , force closes, reboots, apps that wouldn't work at all ...

so I had to go back to a clean install of CM12.1 (format of system, data, & cache) and then reload my apps & their settings via Titanium Backup.

PS:

* The reason I do a custom backup with Philz CWM is because the default settings backup the /cache (and /boot) partitions which I don't care for. There is no reason IMO to backup the cache and have the extra space tied up in a backup (can always manually wipe /cache before a backup) as it can rebuild the cache (and is sometimes needed anyway). Also, since the /boot contains the kernel, moboot, and recovery images, any changes to the /boot will be reverted with the restore, i.e. if you update the recovery or manually add TpToolbox, those will get wiped out. It's good to have the /boot backed up, but sometimes you don't want to restore it.

This is also a reason why I think I am going to go back to TWRP once I get cm12.1 setup, it doesn't automatically backup /cache (or there is a setting for it), and even though it doesn't have a "clean to install new rom" option, I can simply do a "factory data reset" (formats /data & /cache) plus manually format /system for the same effect. Another reason is that Koush stopped publicly developing CWM (around 6.0.4.7 / 6.0.4.8) and so did Philz <-- at least that's what I think I read last year. This isn't gospel, but its my impression. TWRP is still actively developed although neither matters much for our TP's as we still need our talented TP devs for modify each for our devices, from that point of view, it is really something that JcSullins actually built all 3 recoveries to cover everyone's preferences and hosted them in the TpToolbox thread.

Also, I am really not up to date on the recoveries since the original bunch came out for the /data/media builds, but JcSullins' recoveries in his TpToolbox thread seem to handle everything from what I have read so far. There is still some good general info in my data media "Info" and "CWM6" threads

My touchpad is the only device I have currently with root/custom rom. My nexus 5 died 4 months ago and I have left my LG G4 stock (6.0 Marshmallow) until I have significant time to understand it's root method or someone puts together a clear, single how-to thread vs the multiple threads and info spread out everywhere.
[TouchPad General] mpgrimm2:
Off the top of my head, I know its not an issue going between Philz Touch CWM and regular CWM because they use the same uImage filenames in /boot.

Not sure about TWRP and you might be correct, but I think there is likely a script to remove the uImage.ClockWorkMod filename before it installs in its script. I will check real quick and report back...

EDIT: NO issues switching between any of the 3 recoveries from JcSullins' TpToolbox thread. They all have install script code to remove the other recoveries before install (and update the default android recovery file) ...

delete("/boot/uImage.TWRP");
delete("/boot/uImage.ClockworkMod");
delete("/boot/android.default.recovery");

On a related note, I know the same scenario plays out when switching from Evervolv based roms to CM roms because CM doesn't check for a remove the other rom filenames. I really wish our DEVs would agree to standardize the rom & recovery filenames to avoid this issue (i.e. uImage.recovery and uImage.android ), but some people like the different naming conventions to try and squeeze multiple installs on the device at the same time.

From my [INFO] thread ...

Post 5: Current ROM installation "Updater-Scripts" Notes (3-10-14)

_____ Includes a Special Request to the Devs! (A bit technical, feel free to skip this one)
[TouchPad General] nevertells2:
One reason I use the "Clean to Install New Rom" feature of Philz CWM. I seem to remember a small script that was set up as a flashable zip that you could flash from recovery that would remove all known Rom files from boot before you flashed a new Rom. Don't know if it is still around anymore. I don't jump back and forth between different developers Roms like I used to.

NT
[TouchPad General] guynux:
After testing all ones in parameters, I'am unable to get the good résolution for the camera.
[TouchPad General] picassokat:
You should be able to do it with ROM manager.
[TouchPad General] nevertells2:
I'm not quite sure what you mean by all ones in parameters, but I would not waste your time. The HP TouchPad camera sucks. HP did not do anyone any favors with the crappy camera they installed.

NT
[TouchPad General] bsorli:
I've been switch back and forth from TWRP, Philz, and Philz CWM recoveries for over a year simply by booting into the present install and installing over the present recovery loaded into memory.

Please note, my original WebOS install is now gone using the TP Toolkit, so maybe why it simply works. Main reason for my flip flop related mostly to reinstalling the latest firmware that didn't work from TWRP and recommend using Philz recovery.

My process went basically moving to Philz recovery from TWRP, reboot to Philz CWM to install updates, and then back to TWRP that I prefer.

Just in case you don't know, this also required recoveries designed specifically for CWM installation using standard zip compression. Sorli...

---------- Post added at 02:20 AM ---------- Previous post was at 02:15 AM ----------

Yes I agree and barely works for me and even back in WebOS.
[TouchPad General] GnatGoSplat:
This is not correct. See my update on post #16. http://xdaforums.com/showpost.php?p=63957196&postcount=16

The update script in the zip actually checks for and requires minimum 1024MB. If you don't have at least 1024MB, the script fails with that error.
[TouchPad General] guynux:
But worked well in kitkat, even with skype
[TouchPad General] nevertells2:
I don't remember exactly when I increased the size of /system to 1024mb. I am pretty sure I have seen it posted somewhere that others have installed Lollipop with only 800mb allotted to /system. Like I showed in my post, only 592mb is used with 432mb still available. I am not disputing what happened to you in post #16, but I'm not 100% convinced that exactly 1024mb/1gb is needed. I'm not quite up to the task right now of completely removing Android(Complete Data Reset) and starting from scratch with TPTB v42. Sullins created TPTB v42 long before he released his first CM12.1. So, I am pretty sure he had not included the code to create a 1024mb /system volume for Lollipop. I am aware that TPTB when installing CM11 would create a /system volume sized at 800mb. I know a lot of folks have been using v42 to install various builds of Lollipop and I have not seen a lot of complaints about problems with the size of the /system volume. There were lots of complaints about it failing to install Gapps. Sullins straightened that out when he explained that most Gapps creators were leaving a crucial file out of their Gapps builds that was causing the install to abort. He recommended using Delta Gapps from here: http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368 That fixed that issue.

A couple of ways we could resolve this. We could ask anyone who has installed CM12.1 or for that matter any build of Lollipop to check their /system size by either entering df in terminal emulator or running TPTB and then selecting Volume Resizer and looking for the /system volume size and report back to us. If that does not get us what we need, I'll go through the tedious process of saving everything off my TP and starting from scratch.

One note about running Volume Resizer for those of you who have never used it before. Nothing is going to happen to your volumes by just running it. It gives you a report first and then asks what changes you want to make. Just don't make any and select the option to exit without making changes.

So any help from those of you who have used v42 to install CM12.1 would be appreciated. We know there are lots of you. The first build was downloaded over 1200 times and the latest has been downloaded over 350 times. Come on now, don't be shy. :o

Thanks, NT
[TouchPad General] GnatGoSplat:
It's not about Lollipop needing 1024MB, but this particular .zip requires it to install. I'm sure there are other builds that can install with <1024MB, but not this one.

It didn't make sense to me why it wouldn't install on just 1000MB or even 800MB till I took a look at the files. tptoolbox.cfg has this in it:

# minimum size of /system (in MiB) needed for this ROM
ROM_SYSTEM_SIZE 1024

I resized mine from 1000MB to 1024MB and voila! Works first time.
[TouchPad General] nevertells2:
Well, if the camera working well is a deal breaker, then you will have to go back to CM11.

It is a well acknowledged fact that the camera in the TouchPad is a piece of junk.

I'm wondering if you know the history of Android and the camera in the TouchPad?

We are lucky it even works at all. A really talented developer named Dorregaray

managed to get it working pretty well in CM7. The problem was with each successive

version, Google would change things and Dorregaray would have to figure out a way

to get it working again. Now you are using CM12.1 which Google did a lot of under the

hood changes again. And Dorregaray is no longer in the picture to the best of my

knowledge

.

So combine that with a lousy camera and you are probably not

going to like how the camera works. The same kind of thing has happened to WiFi,

the mic, BlueTooth and hardware video acceleration to mention a few.

You might want to go back to CM11 for now and as newer CM12.1 released happens,

try them out to see if there is any improvement in the camera.

NT

---------- Post added at 09:18 PM ---------- Previous post was at 09:10 PM ----------

What paticular zip are you talking about, CM12.1? If that is the case, why would Sullins release a Rom.zip that requires 1024mb and not a version of TPTB that fulfills that need? Is every Sullin's CM12.1 going all the way back to his Nov. 16th build this way? If that is the case, why aren't we seeing more people complaining about this? I guess I dodged a bullet when I increased my /system volume to 1024mb on a whim. By any chance is that line in the TPTB.cfg supposed to increase the /system to 1024mb? Kind of weird if it is not.

NT
[TouchPad General] lolcraft:
Edit: fixed
[TouchPad General] GnatGoSplat:
Yep, the CM12.1 zip. That line is in the .cfg file in the 1116 build and also the recent ones.

I didn't use TPTB to install it, but I do believe that line in the cfg makes TPTB increase /system to 1024MB. People aren't complaining about it because it looks like most people are using TPTB to install it which does everything for you.

Usually holding down the home button and power at the same time for > 10-seconds will get you out of any locked or unresponsive state.
[TouchPad General] mpgrimm2:
I haven't looked at the Cm12.1 install script yet but I can confirm that when I did a full reset with TpToolbox v42 followed by installing cm12.1, TpToolbox set the system partition to 1024mb automatically during install.

* Previously my /system was [MENTION=4502533]700Mb[/MENTION] from CM10.2 DM/acmeinstaller days, upgraded to cm11 via cwm and still had 700mb. Couldn't install cm12.1, tried bumping it to 956mb, still wouldn't install with CWM.

Never tried to go higher on size, but if there is a cfg file in the rom script for TpToolbox to know what to do, I don't see why it would be used by a recovery to prevent an install.

∆∆∆∆∆

This is exactly what happened to me. Looks like you may be on to something!

(I 'bolded' the key phrases for others to catch)
[TouchPad General] bsorli:
Hmm... Shame that browsing has become next to useless with Dolphin (crashes and force reboot), Firefox (better but also locks up), and Browser (need more testing). My system was clean when these problems began so starting over doesn't make much since. I honestly can't remember how long it has been since Dolphin even worked as usual.

Second thought may relate to changes in Dolphin, Firefox and other newer browser versions running on 5.1.x. I'm also running 5.1.x {really old temasek's Rom) on my OnePlus One without any problems , but it obviously has more everything (Processor's , RAM) and that may help keeping it's system rocking.

Would love to hear what other's have tried as fix for their problems and links to newer Google Apps version's (previous suggested option) that also may help? Thanks Sorli...
[TouchPad General] nevertells2:
Well, guess I got lucky when on a whim I increased the /system to 1 gig. :) Now that mpgrimm2 has confirmed that when TPTB is used to install Sullin's CM12.1, /system is increased to 1024mb, I'm wondering if the other developer's install scripts contain the same information for TPTB to use? You seem to know where to look gnat, do ya wanna take a look? :p Good catch on your part. :good:

NT
[TouchPad General] GnatGoSplat:
Sure. Downloaded the first other ROM I saw (Pac-man ROM) and it does have the same info for TPTB. However, its requirements are smaller.

# minimum size of /system (in MiB) needed for this ROM
ROM_SYSTEM_SIZE 800
[TouchPad General] mpgrimm2:
here is the full text of the CM12.1 TpToolbox.cfg file in the root of the install zip (opened via Notepad ++)

# this file should be included as tptoolbox.cfg file at root of ROM zip
TPTOOLBOX_CONFIG_VERSION 1
FILETYPE ROM
# Android ROM version (needed for compat checking w/ gapps)
ROM_VERSION 5.1
# this is a data-media ROM (for resizing/recovery compat check)
ROM_IS_DATAMEDIA 1
# name of the boot image (boot.img is copied to /boot/uImage.NAME)
ROM_BOOTIMAGE_NAME CyanogenMod
# minimum size of /system (in MiB) needed for this ROM
ROM_SYSTEM_SIZE 1024

Note that the above config file is different than the actual rom's recovery install script that the recovery uses further inside the rom's folders at

cm-12.1-20160109-SNAPSHOT-jcsullins-Lp511-tenderloin.zip\META-INF\com\google\android\updater-script

assert(getprop("ro.product.device") == "tenderloin" || getprop("ro.build.product") == "tenderloin" || abort("This package is for device: tenderloin; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/store/cm-system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("f2fs", "EMMC", "/dev/store/cm-data", "/data", "");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/store/cm-system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/store/cm-system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
mount("ext3", "EMMC", "/dev/block/mmcblk0p13", "/boot", "");
package_extract_file("boot.img", "/boot/uImage.CyanogenMod");
package_extract_file("moboot.splash.CyanogenMod.tga", "/boot/moboot.splash.CyanogenMod.tga");
show_progress(0.200000, 10);
unmount("/boot");

Not sure why the TpToolbox.cfg file would affect the install via recovery at all, unless the devs have modified the recoveries to look for the file also. If that is the case, it would be nice to have a text output line that states file system size is too small to install.
[TouchPad General] GnatGoSplat:
I have no idea how it actually works, but my totally unfounded theory is that things changed with how the .zip files are made with Lollipop and newer ROMs. In the CM11 days, the ROM zips contained raw files. So it really didn't matter how large your /system partition was, so long as all the files fit on it. Now, instead of files and folders, the zips contain system.new.dat. Just one file, that looks like an image to me. Possibly it contains a partition image. What I've experienced with partition images (thanks to using Clonezilla on my PCs a lot) is that the destination partition has to be the same size or larger than the source partition or an error will occur. So I don't think necessarily that the recoveries look for the tptoolbox.cfg file, but that if the cfg file says minimum partition size is so many MB, that must be what the source size was. So therefore destination has to be the same size or larger.

Like I said, I could be completely wrong and only Jcsullins or another dev could confirm/disprove that. However, going along that line of thinking that the zip contains a partition image is what made me think there is a minimum size required on the destination partition regardless of how much space is actually used by the individual files.
[TouchPad General] nevertells2:
Wow, glad someone sort of understands this stuff. :D So to sum up this discussion, if you are going to install CM12.1 or any Android Lollipop build via TouchPad Toolbox, your covered. If you are going to dirty flash with recovery, you need to make sure the /system volume is 1024mb in size. Is that correct? :confused:

NT
[TouchPad General] GnatGoSplat:
Yep, that's correct as I understand it.
[TouchPad General] mpgrimm2:
NT,

Maybe.

Someone will need to do some tinkering to verify trying to install it via known workable recovery on a 800-900mb system, then bump up to 1024 or more and try again via same recovery. If that works, then yes.

It sounds like that gnat have done that exactly but it would be nice for a second person to confirm it. I was close but quit too soon.

Edit: he posted same time as me. Looks like that is his take on it.

Sent from my LG G4 on Tapatalk.
[TouchPad General] nevertells2:
Wow, that's spooky!

I would say that the dissecting of the scripts that you to have done as well as the installs that both of you have done pretty much verifies our theory. Maybe a few others will chime in with their experiences using touchpad toolbox or recovery to install Lollipop.

The only remaining mystery, is why the recoveries do not take advantage of the install script language to either increase the size of the /system volume or at least report back why they are failing to install the ROM. I'm pretty sure I know who could help clear that up if he would choose to do so.

NT
[TouchPad General] Frost Storm:
Hey guys

Dont know where to ask this question, so I do it here:

I come from Evervolv 6.01

and installed sullins 5.1. rom, which is absolutely great

everything works fine

But in my moboot the tab for Evervolv is still there (but not functional anymore) and it is the default :(

How to remove evervolv from my moboot?
[TouchPad General] nevertells2:
You need a file browser like Rom Toolbox Lite. Browse to the /boot volume and you will see a

file named uImage.Evervolv. Delete it. Also, there is a text file in /boot named Moboot.default.

You need to open it in a text editor and change the only word in it from Evervolv to CyanogenMod.

Reboot

Question, did you dirty install CM12.1 over Evervolv? Which recovery did you use? You should

never dirty flash a different design of Android over another one. Examples, never flash CM over

Evervolv or PAC ROM or the other way around.

NT
[TouchPad General] mpgrimm2:
I have a zip file to do this that I linked a few posts back... Just a sec

Go to this post and you will find the zip to delete Evervolv, its about half way down the thread.

Sent from my LG G4 on Tapatalk.
[TouchPad General] Frost Storm:
Thanks nevertells2 and mpgrimm2

That worked

I tried all recent ROMs and some time I missed to wipe the system and dirty flashed something over Evervolv

I used TWRP-jcs-dm-tenderloin-20140612b

**** happens

I am glad that I have found a such a great CM-ROM with working BT, camera, Xposed, Titanium, working Netflix and so on - the only compromise is that it is not M :eek:

But it took a while coz this ROM was not in the android development section of this forum

Someone should start a regular ROM-thread

Thanks to all who keep the TP alive
[TouchPad General] alan-31:
Please put these links in the first post:

Latest CM12.1 builds.

https://www.androidfilehost.com/?w=files&flid=43605

G Aaps:

https://www.androidfilehost.com/?fid=24369303960689639

To find the latest, go to: http://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

And search for "gapps-511"

Recovery:

https://www.androidfilehost.com/?w=files&flid=14847

Link to Toolbox software (v42 is the latest):

http://xdaforums.com/hp-touchpad/help/rom-guide-how-to-install-android-4-4-x-t2912820

JCsullins, HP Touchpad (main directory):

https://www.androidfilehost.com/?w=files&flid=9776
[TouchPad General] mpgrimm2:
Won't happen for a while, the OP's account is currently suspended. Perhaps a new, proper thread is in order.

Sent from my LG G4 on Tapatalk.
[TouchPad General] raz123:
Would of one you gents step up and describe his experience/satisfaction in using this rom vs Evervolv Marshmallow?
[TouchPad General] alan-31:
Ok thank you.

Jcsullins, if you can read this, the live camera shows a distorted view for me. It fills the screen in both orientations instead of maintaining the correct aspect ratio. I used the Toolbox and did a complete data reset. When I install Google camera, the app force closes. I attached the LogCat.

Thank you for all the stuff you've done!
[TouchPad General] guynux:
Same here. As I said before, wrong resolution (settings not working)
[TouchPad General] mschumacher69:
This is a known issue on the TP since CM7...
[TouchPad General] alan-31:
I think the previous rom I had worked fine and showed the correct proportions of the camera view: cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip

I will try to flash the version I had and see if it works. I think the version I had of cm11 (4.4.4) was built in June or July 2015
[TouchPad General] picassokat:
Just wondering, what exactly are you using the camera for? I'm assuming video chat and not actually to take pictures. It's a terrible camera, always was, even with the original webOS it sucked. As I think was mentioned earlier, getting the camera to function properly has been a problem since the earliest android ROMs.
[TouchPad General] BinkXDA:
I’ve been running the June CM11 build for quite some time now, but Android 4.4 is getting long in the tooth and I’m wondering if I should try this latest CM12.1 build. Would someone please COMPARE THIS TO THE JUNE OR A RECENT CM11 BUILD (I don’t care about the crappy camera)? Is it stable? How’s its performance (CM11 is somewhat sluggish, but I can’t expect miracles from this aging tablet).

Cheers.
[TouchPad General] GnatGoSplat:
I have no stability problems and battery life is great, but I find it's quite a bit more sluggish than CM11.