[INFO] My HP TP Data/Media Recovery, Rom Notes + Install Guide (6-2-14) - TouchPad General

My HP TP Data/Media Recovery, Rom Notes + Install Guide​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
This is just an FYI, a work in progress, it should not be considered wholly accurate and is just a reference for all this data media stuff.
RootzWiki version of this thread
---------------------------------------------------------​
What is a data media build?
Previously on the HP Touchpad Android and WebOS shared SDcard space in the media partition. This was the space you saw when transferring data via the USB cable. It stored all your media like music, pictures and movies. Data media builds separate the Android and WebOS space by emulating a 2nd ext4 SDcard in the data partition. The place where your app data was stored, separate from the SDcard media partition. You will need to move the majority of your free space from the media partition to the data partition, by using flashable zips, Tailor or android apps. With this setup the data partition now becomes the main place where your apps and users files(Music, pictures, movies, ect) are stored. The left over space in the media partition is now separate and only used by WebOS. WebOS will be left with just a small amount of free space and the majority will be given to the Android Data partition. You will need to boot into WebOS to access its media SDcard space or use the Evervolv build which allows you to see both partitions from Android. Following these instructions will leave WebOS perfectly intact and it can be used for useful things like flashing the A6firmware[Fix Guide] How to Reflash the A6 Firmware.
What are the Advantages and Changes for Data Media Builds?
New data media builds change the default partition layout to more efficiently use the available space. You get a larger area for storing apps and mount an emulated ext4 SDcard all on the Data partition. The ext4 doesn't suffer from the 4GB file size limit that the older Fat partition had and gives you more space for large apps. In additon there is no longer a limit of 50+ apps like some users experienced with the non data media ROMs. The next advantage for HP TouchPad users is the updated 3.x Kernels all the new Android 4.4.2 builds use. The updated Kernel's more efficiently communicates and allocates resources between the hardware and software. However data media Roms require newer data media recoveries to accommodate the new partition format and SeLinux support.
What is a data media device?(TeamWin)
Do I really need to do all this, how can I go back to my old setup?
If you’re happy with your current setup and Android version there is no urgent need to upgrade. However this is the direction that future builds will take and if you understand the basic concepts of flashing rom's and have previously install android with the ACMEInstaller, then you should be ready to test these new builds. Experienced users should backup all their data before trying out these new builds. If you wish to go back to your previous setup you can use Jcsullins' new CWM 6.0.4.9 DM and Jc's Philz CWM Touch DM recoveries (20140317) to restore your older nandroid backups. These two recoveries by JC can see both SDcards while restoring your backups. The Data partition will show up as SDcard and the Media Partition as SDcard1. Note that due to the larger size of data media backups (and SeLinux Context files) you cannot advanced restore the data partition of a data media back up on to a non data media rom.
Please leave ROM developers feedback in their respective threads. Reporting problems in the developer’s threads and submitting alogcats can help to move development along and fix bugs.
HP TouchPad non Data Media build guide threads
[ROM GUIDE] How to install Android on the HP TouchPad "The Easy Way" - Recommended for first time installers to intermediate users
(Covers the basic setup of Java, Novacom, and use of AcmeInstaller etc commands. Forgot something, check it out)
[ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
(Post 2 Covers Data/Media builds)
Important Posts You Should Read Before ANY Data Media Install:
Post 2: Data/media Build Recovery Notes (4-6-14)
Post 3: Data/media ROM SDcard Access Notes (4-8-14)
Post 4: Data/media Resizing Notes (3-31-14)
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)
Post 6: Troubleshooting Tools and Assistance Notes (3-10-14)
Post 7: How to move to CM10.2 Data/Media Build via "cminstall pack v2" - Part 1 (6-2-14)
Post 8: How to move from CM10.2 Data/Media to other 4.4 KK DM Builds - Part 2 (4-08-14)
Post 9: Option 2 - Clean Install Straight to a 4.4 KK Rom via cminstall v2 Pack (6-2-14)
6/2/14 UPDATE:
JcSullins has a new utility called TP Toolbox (thread here) for installing 'most' Data Media Builds and Recoveries. You can still use the install packs from post 7 & 9 if you prefer (while they are offered), but either way, the first 6 posts are still good background you should read ...
jcsullins said:
Touchpad Toolbox (aka tptoolbox) is a completely self-contained and user-friendly system for the low-level management of the HP Touchpad.
TPToolbox replaces:
ACMEInstallers
ACMEUninstallers
Various methods of resizing volumes (erroneously called partitions)
Various methods of reflashing the A6 battery monitoring chip
Various methods of completely wiping/recreating volumes
TPToolbox adds:
A straightforward, reliable and easy-to-use method of installing the current (i.e. KitKat/Datamedia) versions of Android on the Touchpad.
The ability to completely remove webOS.
Click to expand...
Click to collapse
.

---

My /data/media build Recovery Notes (4-06-14)​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
This is just an FYI, a work in progress, it should not be considered wholly accurate and is just a reference until all these data media recoveries get sorted.
---------------------------------------------------------​
For those that want to rename their Twrp/Cwm backup files so that the md5 still passes and you are still able to use/restore that backup, I strongly recommend you try ... Nandroid Manager (PlayStore)
If you type in a filename that is the wrong format (ie special characters, spaces, etc.) it will prevent the filename from being changed.
---------------------------------------------------------​
FYI:
There are currently different partition setups (regular vs data/media), multiple different Recovery's for each build and each partition as well as different Gapps packages depending on the ROM and its base. Data/media builds also setup the sdcard differently as some have found out and as mentioned in RolandDeschain79's OP.
Surprise: Currently you can not mount the old WebOS sdcard (external_sd/ ) or the new "internal" Sdcard (data/media/0/ ) as you were used to previously to transfer files via Windows PC to the recovery. Here's a good Reference and another reference to use ADB_Sideload via recovery if needed (or Google it).
Make sure you are using the correct recovery for both your ROM and partition setup and have any files on the correct sdcard in advance!
(ie Jc's Regular CWM v6.0.1.9 20121215, vs. data media compatible Cwm v6.0.3.6, vs. a SeLinux data media CWM, etc)
So what's up with all these different CWM & TWRP /data/media recovery versions and where are they coming from?
(If you know of any new ones, and/or have experience with them please post a link to the related thread vs a download link as well as any details about it you know and I will try to add the information here)
- Jc's Cwm v6.0.1.9 20121215 (Original partition layout, Non-data/media. For Reference only)
Used with Cm7 / 9 / 10.0 / 10.1 or any ROM with the original /sdcard & partition layout.
Note: Click the link for some good general background info on Recoveries.
CAN mount USB Storage to Win7 PC (original external_sd only)
CAN consistently flash "data_plus" zips from The_Ape or Gradular.
A “Wipe Data/Factory Reset” will wipe the ENTIRE /data partition and /data/media/0 if it exists
CURRENT LIST OF DATA MEDIA RECOVERIES : Take a close look and soak it in!​
- JcSullin's Philz cwm6.0.4.7 DM touch 20140317 (SeLinux data/media) <<- - HIGHLY RECOMMENDED (3-18-14 edit)
Originally Posted Here (Discussion follows for a few posts)
CAN mount USB Storage to Win7 PC (original WebOS Sdcard1 only)
CAN consistently flash "data_plus" zips from The_Ape or Gradular.
CAN see both Sdcards (original WebOS "Sdcard1", and /data/media/0 "Sdcard")
Can be flashed with AcmeInstaller5
Has option to “Clean for Rom install”. (i.e. Wipes System, data, and cache but not data/media/0 sdcard)
Flashed JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = SUCCESSFUL
Flashed Milaq’s CM10.2 DM 2.6 Kernel and Gapps = SUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Caution: While this particular recovery 'Reportedly' can restore user /data from original partition layouts to a /data/media rom, it can not restore user /data from a /data/media rom to an original partition layout (likely due to extra SeLinux Context data and larger size).
Even So, This is NOT Recommended. Use Ti Backup to Restore your Apps Instead of mixing data b/w partition layouts!
Also see: Phil3759's General Philz Touch Reference thread here (Very Good Info)
- JcSullins' CWM v6.0.4.7 DM 20140317 (SeLinux data/media) <<--- Highly Recommended. Same flashing support as touch version above.
CAN mount USB Storage to Win7 PC (original WebOS Sdcard1 only)
CAN consistently flash "data_plus" zips from The_Ape or Gradular.
CAN see both Sdcards (original WebOS "Sdcard1", and /data/media/0 "Sdcard")
Can be flashed with AcmeInstaller5
Flashed JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = SUCCESSFUL
Flashed Milaq’s CM10.2 DM 2.6 Kernel and Gapps = SUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Caution: While this particular recovery 'Reportedly' can restore user /data from original partition layouts to a /data/media rom, it can not restore user /data from a /data/media rom to an original partition layout (likely due to extra SeLinux Context data and larger size).
Even So, This is NOT Recommended. Use Ti Backup to Restore your Apps Instead of mixing data b/w partition layouts!
- Philz CWM v6.0.4.7 Advanced (SeLinux data/media and supports TWRP/CWM formats.) <<- 2nd Recommendation
From Invisiblek's CM11 / KK 4.4.2 Data Media with 3.4 Kernel Nightly thread.
Couldn’t mount USB storage to Win7 PC.
Can only see /data/media/0 “sdcard”
Has option to “Clean for Rom install”. (i.e. Wipes System, data, and cache but not data/media/0 sdcard)
Flashed JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = SUCCESSFUL
Flashed Milaq’s CM10.2 DM 2.6 Kernel and Gapps = SUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Couldn’t Flash “data_plus” zips from The_Ape or Gradular.
- Flintman's TWRP v2.6.3.0 SeLinux Alpha Touch (SeLinux data/media) <<- 2nd Recommendation
From Flintman's Evervolv 4.0.0p1 AOSP / KK 4.4.2 Data Media with 3.4 Kernel Nightly thread
No Option to mount USB storage to Win7 PC.
CAN see both Sdcards (original external_sd, and /data/media/0 )
Couldn’t Flash JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = UNSUCCESSFUL
Couldn’t Flash Milaq’s CM10.2 DM 2.6 Kernel and Gapps = UNSUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Couldn’t Flash Milaq’s CWM v6.0.3.6 (no_metadata, data/media)
Couldn’t Flash Jc’s CWM v6.0.1.9 12/15/2012 (Original partition layout)
Couldn’t Flash “data_plus” zips from The_Ape or Gradular. Didn’t work on clean AcmeInstaller5T run of Moboot 3.8 and Flintman’s TWRP v2.6.3.0.
- Milaq's Cwm v6.0.4.7 (SeLinux data/media)
From Milaq's CM11 / KK 4.4 Data Media with 3.0 Kernel Nightly thread.
(This new version is said to be needed for Nightly's after 2/7/14 due to Custom-Updater feature)
Couldn’t mount USB storage to Win7 PC.
Can only see /data/media/0 “sdcard”
Flashed JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = SUCCESSFUL
Flashed Milaq’s CM10.2 DM 2.6 Kernel and Gapps = SUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Couldn’t Flash “data_plus” zips from The_Ape or Gradular.
- Milaq's CWM v6.0.4.5 (not v6.0.5.4) (SeLinux data/media from Invisiblek’s CM11 3.4 kernel thread)
From Invisiblek's CM11 / KK 4.4.2 Data Media with 3.4 Kernel Nightly thread
Couldn’t mount USB storage to Win7 PC.
Can only see /data/media/0 “sdcard”
Couldn’t Flash JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = UNSUCCESSFUL
Couldn’t Flash Milaq’s CM10.2 DM 2.6 Kernel and Gapps = UNSUCCESSFUL
Flashed Milaq’s CM11 DM 3.0 Kernel and Gapps = SUCCESSFUL
Flashed Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = SUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
Couldn’t Flash Milaq’s CWM v6.0.3.6 (no_metadata, data/media)
Couldn’t Flash Jc’s CWM v6.0.1.9 12/15/2012 (Original partition layout)
Couldn’t Flash “data_plus” zips from The_Ape or Gradular.
- Milaq's CWM v6.0.3.6 (no_metadata, for data/media)
From Milaq's CM10.2 / JB 4.3 Data Media Nightly thread
No Option to mount USB storage to Win7 PC.
CAN see both Sdcards (original external_sd, and /data/media/0 )
Flashed JcSullins’ CM10.1 01/25/14 (3.x Kernel Test) and Gapps = SUCCESSFUL
Flashed Milaq’s CM10.2 DM 2.6 Kernel and Gapps = SUCCESSFUL
Couldn’t Flash Milaq’s CM11 DM 3.0 Kernel and Gapps = UNSUCCESSFUL
Couldn’t Flash Invisiblek’s CM11 Data Media (3.4 kernel) and Gapps = UNSUCCESSFUL
Flashed Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) and Gapps = SUCCESSFUL
(Couldn’t flash Gapps 4.4 KK from Milaq’s site. P.A.’s 0-day Gapps flashed ok)
Flashing of “data_plus” zips from The_Ape or Gradular can be hit or miss. Works on clean AcmeInstaller5 run of Moboot 3.8 and CWM v6.0.3.6 but didn’t on Acme5M install of CM10.2 DM with all 4 files (Moboot, CWM, CM10.2 DM, and Gapps).
Now someone tell me why some of the recoveries can't flash some of the zips?
( Is it "edify" vs "amend" etc. syntax , maybe different "update-binary" file or something else between the recoveries? )
The only confirmed recovery's for flashing the data_plus zips are JcSullins' CWM v6.0.1.9 for the original partition layout (very reliable), JcSullins' CWM v6.0.4.7 DM & Jc's Philz Touch versions from 20140317 (Very Reliable/recommended), and Milaq's CWM v6.0.3.6 DM(Seems to work intermittently on a clean Acme5 install with only Moboot/CWM if android/CM hasn't been loaded to the partitions yet).
--------------------------------------------------------------------------------------------------------------------------
A QUICK NOTE ABOUT CLEAN VS DIRTY INSTALLS VIA RECOVERY:
The safest way to do a FULL "Clean" install from a currently installed recovery without carrying over any stuff from prior installations is to do the following from the custom recovery:​
1 ) Perform a factory/data reset.
This will format the /data partition (user apps and settings) and /cache partition (temporary app & system files).
** On data/media recoveries like TWRP, this should safely delete all files except the emulated /data/media/sdcard. Good. **
Note: If you 'manually' format /data on a data/media recovery vs. a factory reset, it will likely wipe the emulated sdcard as well!
2 ) Under mounts and storage, format the /system partition
(this is where the ROM actually is)
** Most CM Rom's install scripts have a command to perform the format for you when flashing but not all ROMs do it.**
3 ) Flash ROM and gapps as needed.
4 ) Reboot.
For a 'Dirty' Install to keep you user apps & settings within the same ROM series:
(If you experience issues you may have to do a clean install)
1 ) wipe/format cache partition.
2 ) wipe/format system partition
** (Again, some ROMs may do this for you when installed)
3 ) Flash ROM and gapps as needed.
4 ) Reboot
^^ Back to the OP ^^

---

My data/media ROM SDcard Access Notes: (4-8-14)
These are just some quick ROM notes.​
JcSullins’ CM10.1 01/25/14 (3.0 Kernel Test) NOT A DATA MEDIA BUILD! Reference Only!
Only see’s original external /Sdcard ( can’t see /data/media/0 )
OTG works but has OTG ID pin activation bug (Causes Reboot if incorrect order. See xda post)
----------------------------------------------------------------------------------------------------------------------​
Milaq’s CM10.2 Data Media (2.6.35 Kernel) 02-10-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse
JcSullins' CM11 Data Media (3.0 Kernel) 04-05-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse (OTG Activation bug fixed)
Milaq’s CM11 Data Media (3.0 Kernel) 02-10-14 Build
Only see’s internal Sdcard ( /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Invisiblek’s CM11 Data Media (3.4 kernel) 02-10-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) 02-10-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
^^ Back to the OP ^^

---

Data/media Resizing Notes (3-31-14)​
mpgrimm2 said:
Summary: The only confirmed recovery's for flashing the data_plus zips are JcSullins' CWM v6.0.1.9 for the original partition layout (very reliable), JcSullins' CWM v6.0.4.7 DM & Jc's Philz Touch versions from 20140317 (Very Reliable/recommended), and Milaq's CWM v6.0.3.6 DM(Seems to work intermittently on a clean Acme5 install with only Moboot/CWM if android/CM hasn't been loaded to the partitions yet).
Click to expand...
Click to collapse
sstar said:
In Android open the app terminal emulator and type: df and hit enter and you will see all your partition sizes before or after resizing.
( Can also use Quick System Info Pro if you want to install another app ).
Click to expand...
Click to collapse
Switching the majority of your free space from Media to Data:
With the basic partition layout setup using Acme5 (System Partition=600MB) and only recovery and Moboot 3.8 installed, you should be able to move your free SDcard space from the Media partition to the Data partition. There are a few different methods to accomplish this. The Flashable zips are recommended.
Before Data Media setup
system = 600MB
cache = 200MB
media (16GB TouchPads) = 11.5GB
media (32GB TouchPads) = 28GB
data = 1.5GB
Rootz: Gradular's Guide to Changing Partition Sizes - Post 195: My notes about Data and Sdcard sizes after data_resize zips
Mpgrimm2 said:
Data Partition sizes AFTER AcmeInstaller5 and Gradular's Resize Zips ( Originally Sys: 600mb, Cache: 200mb, Data: 1.5Gb * default)
Data Resize Zip _ _ _ _ _ 16GB TP /Data _ _ _ _ 16Gb TP orig. “media” Sdcard (external_sd )
data_resize_8192 _ _ _ _ _~ 8.2Gb _ _ _ _ _ _ ~ ??? Gb (need someone to tell us! )
data_resize_12228 _ _ _ _ ~12.2Gb _ _ _ _ _ _ ~ ??? Gb (need someone to tell us! )
If anyone with a 16gb TP can help fill this in it would be great
Data Resize Zip _ _ _ _ _ 32GB TP /Data _ _ _ _ 32Gb TP orig. “media” Sdcard (external_sd )
data_resize_8192 _ _ _ _ _~ 8.2Gb _ _ _ _ _ _ ~19.1Gb
data_resize_12228 _ _ _ _ ~12.2Gb _ _ _ _ _ _ ~15.0Gb
data_resize_20480 _ _ _ _ ~20.5Gb _ _ _ _ _ _ ~ 6.9Gb
data_resize_24576 _ _ _ _ ~24.5Gb _ _ _ _ _ _ ~ 2.8Gb
Data Resize Zip _ _ _ _ _ 64GB TP /Data _ _ _ _ 64Gb TP orig. “media” Sdcard (external_sd )
data_resize_8192 _ _ _ _ _~ 8.2Gb _ _ _ _ _ _ ~48.3Gb (Est.)
data_resize_12228 _ _ _ _ ~12.2Gb _ _ _ _ _ _ ~44.3Gb (Est.)
data_resize_20480 _ _ _ _ ~20.5Gb _ _ _ _ _ _ ~36.0Gb (Est.)
data_resize_24576 _ _ _ _ ~24.5Gb _ _ _ _ _ _ ~32.0Gb (Est.)
data_resize_40960 _ _ _ _ ~39.7Gb _ _ _ _ _ _ ~16.8Gb (Est.)
data_resize_49152 _ _ _ _ ~47.8Gb _ _ _ _ _ _ ~ 8.7Gb (Est.)
data_resize_56320 _ _ _ _ ~55.0Gb _ _ _ _ _ _ ~ 1.5Gb (Verified by Garux)
Click to expand...
Click to collapse
A] Flashable zips (Recommended):
Gradular and The Ape have both created zips you can flash through recovery that can make the partition changes quick and easy. Download the desired .zips either directly to your TouchPad or to your PC and then transfer them to the Touchpad with the USB cable. There are several flashable zips available but you must choose one that best accommodates your TouchPad model 16GB or 32GB. It’s recommended to use the largest possible zips for your TouchPad model, a 32GB TouchPad could use the 24576 zip and 16GB HP Touchpad would use the 10752 zip. Flashing these zips will leave about 2.5GB of space on the Media partition for WebOS and move the majority of space to the Data partition for Android apps and file storage.
Note: Before changing your partition size you must have enough free space on the media partition in order to add that space to the data partition. If the zips fail to flash make sure that you have previously wiped your USB drive via WebOS. If you use WebOS often, then you might wish to leave more space on the media partition.
Download Flashable zips to move your free space from Media to Data:
How to guide for changing your system, data, and cache partition sizes to whatever you want By Gradular (See Quote Above)
16gbTP_Gradular_data_resize_10752-0.1.zip (i.e. for 16GB and up Touchpads)
32gbTP_and_up_ONLY_Gradular_data_resize_24576-0.1.zip (i.e. for 32GB and up Touchpads)
64gbTP_ONLY_Gradular_data_resize_56320-0.1.zip (i.e. for 64GB and up Touchpads)
(Gradular has additional sizes available. Included in my cminstall v2 packs)
Or
Data Partition Size Changer CWM ZIPS By The_Ape
data_plus_24576mb-signed.zip for 32GB Touchpads
data_plus_16384mb-signed.zip for 16GB Touchpads
Mpgrimm2 said:
I have decided that I prefer Gradular's "data_resize" zips over the "data_plus" zips because Gradular's will always check the current size and calculate what changes need to be made to come up with the "planned" /data partition size. Whereas the data_plus zip can be used repeated to increase the /data partition by the stated "increment" and could cause problems (i.e. if the 8gb data_plus is run 2x on a 16gb TP it will run out of space). Both version are useful, I just think Gradular's method is safer for the average user.
Click to expand...
Click to collapse
B] Tailor: (Advanced Users)
The WebOS Preware app Tailor can also be used to make the necessary partition changes. This method also works well but can take longer to setup and complete. Note: Make sure your HP Touchpad is fully charged before making changes with tailor. Checking the file system and resizing the partition can take some time, so be patient. If you get an error during the file system check, run it again. Do Not restart or shutdown the device until it completes. Read all about using tailor by watching RolandDeschain79's video and reading the OP in Gradular’s thread.
Note(Important):If you have accidentally interrupt tailor you may need to run the WebOS Doctor.
C] Android Partition changing apps: (Not Recommended)
There are a number of apps in the Play Store that could help you change the partitions sizes. However the success rate of using these apps is questionable and some require you to get a paid version. If you wish to try using apps make sure you have a full backup before proceeding.
-------------------------------------------------------------------------------
ADDITIONAL REFERENCES:
XDA posts 61 - 63 over at The_Ape's thread : Problems flashing Data_Plus zips with various recoveries
Rootz: Gradular's Guide to Changing Partition Sizes - Post 195: My notes about Data and Sdcard sizes after data_resize zips
^^ Back to the OP ^^

---

My Current ROM installation "Updater-Scripts" Notes (3-10-14)​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
This is just an FYI, a work in progress, it should not be considered wholly accurate and is just a reference on the various regular vs current data/media builds and their "updater-scripts".
---------------------------------------------------------​
Summary:
1) The /boot partition is about 30.99mb and is shared with both WebOS, Moboot 0.3.8, any recoveries, and any android Roms.
- The Rom's "kernel" or boot.img is stored here as a .uImage file with a "splash" file (is this the rom's splash screen image? IDK ) .
- As a reference, my previous install of JC's CM10.1 VPN build takes up about 25mb-27mb, so there is very limited free space for ANY redundancy without causing installation or reboot issues.
- data/media roms and recoveries have larger /boot/ "uImage" files so keep an eye out for left over ROM and Recovery files that "may" need to be manually removed.
2) Both the CM and Evervolv Roms (regular and data/media versions) currently format the /system partition for you during the installation process.
3) ONLY the Evervolv Rom install scripts currently delete a few "Select" Roms from the boot partition for you during installation.
(only CM, AOKP, ICS, & ClassicNerd)
4) If you are coming from Evervolv or another ROM to a CyanogenMod ROM, the CM installation scripts WILL NOT remove ANY other ROM from the /boot partition and you may run out of room or get an installation error.
5) Removing previous ROM files from the /boot is not specifically a function of the recovery but a command issued to the recovery by the ROM's installation script!
- One of the main differences I noticed between the CM10.2 and CM11 data/media build install scripts is that CM11 scripts appear to need Recovery support for "set_metadata" where as Evervolv and the CM10.2 currently do not for "setting permissions".
2-22-14 TESTING UPDATE (Moving from Evervolv to CM):
- If you are coming from an Evervolv ROM to a CyanogenMod ROM (Regular or Data/Media), I have modified JcSullin's "Set CyanogenMod as Moboot Default zip to also delete the Evervolv ROM from /boot to prevent you from running out of space.
Flash the zip after a wipe/format and before flashing a CM rom zip.
Thanks to JcSullins and Flintman for the original zips and script templates.
- Here you go: JCs-update-boot-cm-default_Plus-DELETE-EV .zip - 143.89 KB
If you prefer to manually push or remove files from the /boot partition, there is some discussion in Flintman's Evervolv thread starting here.
BONUS:
Please see my additional thoughts on the install scripts, naming conventions, and AcmeInstallers after the screenshots.
image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image
image
image
A Request to the Devs on install scripts, naming conventions, and AcmeInstallers (again, I am not a Dev! )
Now that we have explored some of the reasons why the /boot partition might run out of space, some of us have also wondered why there was a need for some of the "extra" AcmeInstallers (ie iMarck90's Acme5, 5M, 5E, 5T, & 5ET) beyond just having a larger "system" partition size.
Now take a look again at the above updater-script screenshots. Pay attention to the bottom sections where the /boot.img gets installed. On dedicated android devices with only one /boot.img the installation is easy because the filename never has to change from one rom name to another, just extract/copy the boot.img to the /boot and it will overwrite the previous one. Done.
On the TP:
- CM's boot.img file gets copied to the /boot as a custom filename "uImage.CyanogenMod"
- CM's splash file gets copied to the /boot as a custom filename "moboot.splash.CyanogenMod.tga"
- Evervolv's boot.img file copies to the /boot as a custom filename "uImage.Evervolv"
- Evervolv's splash file gets copied to the /boot as a custom filename "moboot.splash.CyanogenMod.tga"
- CWM's boot.img file is copied to the /boot as a custom filename "uImage.ClockworkMod"
- TWRP's boot.img file is copied to the /boot as a custom filename "uImage.TWRP"
- Moboot's boot.img file is copied to the /boot as a custom filename "uImage.moboot"
Perhaps if the devs would consider something similar to the following for the TP, we could avoid any space issues in the /boot:
- Copy all ROM's boot.img's to the /boot partition with the standard filename of "uImage.Android"
- Copy all ROM's splash files to the /boot partition with the standard filename of "moboot.splash.Android.tga"
- Copy all recovery boot.img's to the /boot partition with the standard filename of "uImage.AndroidRecovery"
Then there would never be any doubt about left over files in the /boot. And AcmeInstaller wouldn't need modified for specific /boot.img filenames between roms other than data/media builds that require "metadata" in the install scripts which may be a work in progress by iMarck90 for SeLinux 3.x kernel builds and recoveries (we hope).
TP Developers please note:
I appreciate all your hard work and can only hope that no one takes offense to the above thoughts or is discouraged as I promise no slight is intended. As an average user I am merely peaking behind Oz's curtain whenever I manage to learn something new and seek to share with others. Perhaps a properly placed question like mine, even one without all the information, can be useful.
Comments welcome.
Sincerely,
Mpgrimm2
^^ Back to the OP ^^

---

Troubleshooting Tools and Assistance Notes (3-10-14)​
For those that need help with logs for bug reports to the devs, Here is a thread to help people post logs etc:
Tutorial: How to properly post a bug
As well as the following apps to help make things easier for people to get the files:
- Bootlog Uptime (get last_kmsg or specified file i.e. last_klog on the TP)
- CatLog and aLogcat (get logcats)
- Dmesg Log Viewer (get Dmesg's)
Haven't tried it yet myself, but with a Pastebin account and an app such as Pastebin for Android posting links to the logs should be easier.
^^ Back to the OP ^^

---

How to move to CM10.2 Data/Media Build via "cminstall pack v2" - Part 1 (6-2-14)​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
-------------------- THIS IS STRAIGHT FORWARD BUT IS NOT RECOMMENDED FOR BEGINNING USERS --------------------------​
I have a new cminstall v2 pack for the CM10.2 Data Media build. Currently it is considered the more mature of the DM builds (probably because of the 2.6 kernel). There are other ways to get this done. Chase the rabbit down another hole if you like, but be prepared for the snags you will likely encounter if you haven't been following some of the posts in the various XDA Data Media threads by the uninitiated. If you are capable and interested in trying out the new cminstall v2 data media pack for CM10.2 here is some info you need to consider.
A few Q's first:
- Are you able to find specific details for any missing steps?
(i.e. from RolandDeschain79's OP and other threads)
- Are you confident in your ability without assistance to run ACMEuninstaller2, ACMEinstaller5, reset/wipe WebOs sdcard From webOS) , and if needed run WebOS Dr? (Have you done any of these before?)
Made it this far? Ok.
You will find the download link to the data/media pack near the end.
Please read THE IMPORTANT POSTS LINKED IN THE OP FIRST BEFORE downloading the pack!
Notes:
You should already be familiar with RolandDeschain79's How To Install Android the Easy Way thread and especially My data media recovery and rom notes in the first 6 Posts for some of the issues with the different recoveries and using them with the different DM builds as well.
Because the data resize zips can't be used going backwards, ie from a 12Gb data partition to an 8gb data partition currently you may want to start small. You can always reboot back to recovery (See below) and reflash the appropriate data Resize zip.
- Just use JcSullins' Philz CWM 6.0.4.7 Touch 20140317 (or his 20140317 Non-Touch version). It supports all DataMedia Roms, access to both sdcards (sdcard1 = Webos Sdcard), and can mount Sdcard1 via to PC. (Included in cminstall v2 packs as of 3/18/14)
I may leave out some of the details but I assume you can fill in anything I forgot to mention
IMPORTANT: Make backups before hand and move them off of the TP to your PC. This will wipe your SDcard contents and give you a clean transition to data/media builds.
01. Run Acmeuninstaller2 to remove android and reset the partitions back to normal
(I verified it removes /data partition adjustments and returns extra back to sdcard)
02. Boot to WebOs and reset/wipe the Sdcard to clear out the last bits of Android.
(settings, device info, reset, erase usb drive. Or something like that ).
03. Extract the 3 folders from the zip and copy them to the root of /sdcard via WebOS.
(should be "cminstall" , "01. DM Resize zips", and "02. DM ROM Install Files" )
04. Eject the sdcard from WinPC, and reboot to webOs Recovery mode "bootie", then plug USB into PC after symbol comes up on TP.
05. Run AcmeInstaller5 (standard version, not 5M) to install Moboot and JcSullins' Philz CWM 6.0.4.7 Touch.
(no need for the other Acme's b/c none of the other recoveries can see the WebOS sdcard AND flash the data_resize zips repeatedly)
06. After it finishes, boot to JcSullins' Philz CWM 6.0.4.7 Touch and run the appropriate data_resize zip.
Go to: INSTALL ZIP FROM SDCARD -> CHOOSE ZIP FROM SDCARD1 (WebOS Sdcard) --> select the "01. DM Resize zips" folder
and flash the resize zip according to your TP and the size you want. See Gradular's thread post 1 and 2 for details.
( I run the 20gb /data partition for my 32gb TP which leaves me about 6.5gb for the old CM versions and external_sd for now.)
See size details here
NOTE: if you have a 16Gb TP, DO NOT run either of the larger zips ( i.e. the 20Gb or 24Gb resize).
07. Reboot back to "CWM Recovery" to initialize the partitions ( IMPORTANT! It tells you to reboot afterwards! )
08. Flash the CM10.2 JB data media ROM and Gapps :
Go to: INSTALL ZIP --> CHOOSE ZIP FROM SDCARD1 (WebOS Sdcard) --> select "02. DM ROM Install Files" folder
and then flash CM10.2 DataMedia Rom and Gapps files in order, i.e. 01., 02., 03., etc.
(it's the only sdcard you can use until a DM Rom is loaded)
NOTE: Until CM devs consider standardizing /boot/ uImage filenames and updater-script's this next step will be needed because they do not include these few lines of code in their installer. I think Acme5 sets up default boot if CM is present in the cminstall folder, but it's not...
See Post 5 for Details
08a. (For CM ROMS ONLY) If you didn't already do it, also flash "03.JCs-update-boot-cm-default_Plus-DELETE-EV .zip" from the external_sd card.
This zip will set Moboot default OS to CyanogenMod and also delete the Evervolv uImages from the /boot partition if they exist.
Note: You can skip this zip for now and come back and flash it later once you see what I mean.
I basically downloaded JC's file from goo.im and added in the 1 line of code to delete evervolv because I ran into that problem while testing/nearly filling up the boot partition. Previously I modified JC's CM10.1 3.0 kernel Test installer to do it successfully.
(Big thanks to JcSullins and Flintman for the templates)
09. Reboot to CM10.2 DM OS. Done.
Alright here's the CM10.2 JB CMINSTALL v2 download link:
DataMedia CM10.2 20140602 2.6Kern cminstall v2 Milaq.zip
(EDIT: Link removed/outdated. See RolandDeschain79's "Easy Install" threads)
Reminder:
At this point with your TouchPad booted to CM10.2 and connected to your PC, you will be able to see both SD cards. This would be a good time to copy any zips, and files that are on your PC or the old media/SDcard (external_sd) over to the new internal SDcard (data/media/0 ) because depending on the data/media Rom/Recovery you choose to flash later, you may not be able to see or mount the media/Sdcard again.
FYI:
- Want to go back? Run AcmeUninstaller2 and go from there.
- CWM Data Media backup files are stored in the same folder but have extra "context" files that are not present in backups made from the original recovery. I doubt that any prior recovery backups can be restored by a Data Media recovery and I don't recommend you try it.
^^ Back to the OP ^^

---

How to move from CM10.2 Data/Media to other 4.4KK DM Builds - Part 2 (4-8-14)​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
-------------------------------------------------------------------------------------------------------------------------​
Android 4.4.2 data media builds can’t be installed from a regular non selinux recovery or with the ANY CURRENT ACMEInstaller. You will need to install a selinux recovery, from a non selinux recovery first and then Flash the 4.4.2 rom and gapps package.
Click to expand...
Click to collapse
Option 1 - Moving on to a 4.4 KK Rom ( RECOMMENDED. Assumes you completed Post 7 - Part 1 ! ) : ​
1. Boot CM10.2 DM and plug it into the Windows PC so that you can see both sdcards via windows, i.e. "internal storage" ( /data/media/0/ ) and "SD card" (external_sd or original webos/sdcard/ ).
2. Copy over the following files to a folder on the "Internal Storage" ( /data/media/0/ ).
Any 4.4 KK Roms and Gapps. Links in quote below.
- Just use JcSullin's Philz cwm6.0.4.7 touch 20140317 (or his 20140317 Non-Touch version). It supports all DataMedia Roms, access to both sdcards (sdcard1 = Webos Sdcard), and can mount Sdcard1 via to PC. (Included in cminstall v2 packs as of 3/18/14)
Note: depending on the rom and recovery you move to, you may no longer be able to see or mount the original webOS /sdcard/ to get access to any files for flashing ! (you read the important posts in the OP already right? See Posts 2 & 3 again if needed )
3. Perform a "wipe data/factory reset" (or from Philz CWM "Clean for new Rom install" ).
This will format data and cache but not data/media/0 (Philz will also format /system ).
4. Flash new 4.4 KK ROM and KK Gapps.
Try it with Invisiblek's CM11 DM with 3.4 kernel and Gapps because you can still mount both sdcards to windows from CM11 !
(I had a few "sleep of death" issues with it currently and moved on to Milaq's CM11 with 3.0 Kernel).
5. Reboot to 4.4 KK OS. Done.
4.4 DM KK ROM Links and Features from Post 3:
Mpgrimm2 said:
JcSullins' CM11 Data Media (3.0 Kernel) 04-05-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse (OTG Activation bug fixed)
Milaq’s CM11 Data Media (3.0 Kernel) Nightly Build
Only see’s internal Sdcard ( /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Invisiblek’s CM11 Data Media (3.4 kernel) Nightly Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) 4-5-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Click to expand...
Click to collapse
4.3 JB DM ROM Links and Info from Post 3:
Mpgrimm2 said:
Milaq’s CM10.2 Data Media (2.6.35 Kernel) Nightly Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse
RolandDeschain79 Note: Low battery drain (-4mA to -10mA), h/w video, Audio & Mic, Nightly Builds, Most mature data/media build available, Pie Controls, Inverted Volume controls, Camera, Bluetooth.
Click to expand...
Click to collapse
Option 2 - Clean Install straight to a 4.4 KK Rom (See Post 9) : ​Reminder:
Wanna go back? Run AcmeUninstaller2 and go from there.
CWM Data Media backup files are stored in the same folder but have extra "context" files that are not present in backups made from the original recovery. I doubt that any prior recovery backups can be restored by a Data Media recovery and I don't recommend you try it.
^^ Back to the OP ^^

---

Option 2 - Clean Install Straight to a 4.4 KK Rom via cminstall v2 Pack (6-2-14)​
DISCLAIMER: I'm not a dev, nor do I play one on t.v. Use the information and links at your own risk. READ and UNDERSTAND what your doing before flashing is the best bet. I take no responsibility or credit for the information.
-------------------- THIS IS STRAIGHT FORWARD BUT IS NOT RECOMMENDED FOR BEGINNING USERS --------------------------
I have new cminstall v2 packs for the 4.4 KK Data Media builds. These builds have issues and you should see the respective dev's thread for support and details. There are other ways to get this done. Chase the rabbit down another hole if you like, but be prepared for the snags you will likely encounter if you haven't been following some of the posts in the various XDA Data Media threads by the uninitiated. If you are capable and interested in trying out the new cminstall v2 data media pack here is some info you need to consider.
Android 4.4.2 data media builds can’t be installed from a regular non selinux recovery or with the ANY CURRENT ACMEInstaller. You will need to install a selinux recovery, from a non selinux recovery first and then Flash the 4.4.2 rom and gapps package.
Click to expand...
Click to collapse
A few Q's first:
- Are you able to find specific details for any missing steps?
(i.e. from RolandDeschain79's OP and other threads)
- Are you confident in your ability without assistance to run ACMEuninstaller2, ACMEinstaller5, reset/wipe WebOs sdcard From webOS) , and if needed run WebOS Dr? (Have you done any of these before?)
Made it this far? Ok.
You will find the download link to the data/media pack near the end.
Please read THE IMPORTANT POSTS LINKED IN THE OP FIRST BEFORE downloading the pack!
Notes:
You should already be familiar with RolandDeschain79's How To Install Android the Easy Way thread and especially My data media recovery and rom notes in the first 6 Posts for some of the issues with the different recoveries and using them with the different DM builds as well.
Because the data resize zips can't be used going backwards, ie from a 12Gb data partition to an 8gb data partition currently you may want to start small. You can always reboot back to recovery (See below) and reflash the appropriate data Resize zip.
- Just use JcSullins' Philz CWM 6.0.4.7 Touch 20140317 (or his 20130317 Non-Touch version). It supports all DataMedia Roms, access to both sdcards (sdcard1 = Webos Sdcard), and can mount Sdcard1 via to PC. (Included in cminstall v2 packs as of 3/18/14)
I may leave out some of the details but I assume you can fill in anything I forgot to mention
IMPORTANT: Make backups before hand and move them off of the TP to your PC. This will wipe your SDcard contents and give you a clean transition to data/media builds.
01. Run Acmeuninstaller2 to remove android and reset the partitions back to normal
(I verified it removes /data partition adjustments and returns extra back to sdcard)
02. Boot to WebOs and reset/wipe the Sdcard to clear out the last bits of Android.
(settings, device info, reset, erase usb drive. Or something like that ).
03. Extract the 3 folders from the zip and copy them to the root of /sdcard via WebOS.
(should be "cminstall" , "01. DM Resize zips", and "02. DM ROM Install Files" )
04. Eject the sdcard from WinPC, and reboot to webOs Recovery mode "bootie", then plug USB into PC after symbol comes up on TP.
05. Run AcmeInstaller5 (standard version, not 5M) to install Moboot and JcSullins' Philz CWM 6.0.4.7 Touch
(no need for the other Acme's b/c none of the other recoveries can see the WebOS sdcard AND flash the data_resize zips repeatedly)
06. After it finishes, boot to JcSullins' Philz CWM 6.0.4.7 Touch and run the appropriate data_resize zip.
Go to: INSTALL ZIP FROM SD CARD -> CHOOSE ZIP FROM SDCARD1 (WebOS Sdcard) --> select the "01. DM Resize zips" folder
and flash the resize zip according to your TP and the size you want. See Gradular's thread post 1 and 2 for details.
( I run the 20gb /data partition for my 32gb TP which leaves me about 6.5gb for the old CM versions and external_sd for now.)
See size details here
NOTE: if you have a 16Gb TP, DO NOT run either of the larger zips ( i.e. the 20Gb or 24Gb resize).
07. Reboot back to "CWM Recovery" to initialize partitions ( IMPORTANT! It tells you to reboot afterwards!)
08. Flash the 4.4 KK data media ROM and Gapps :
Go to: INSTALL ZIP --> CHOOSE ZIP FROM SDCARD1 (WebOS Sdcard) --> select "02. DM ROM Install Files" folder
and then flash 4.4 KK DataMedia Rom and Gapps files in order, i.e. 01., 02., 03., etc.
(it's the only sdcard you can use until a DM Rom is loaded)
NOTE: Until CM devs consider standardizing /boot/ uImage filenames and updater-script's this next step will be needed because they do not include these few lines of code in their installer. I think Acme5 sets up default boot if CM is present in the cminstall folder, but it's not...
See Post 5 for Details
8a. (For CM ROMS ONLY) If you didn't already do it, also flash "03.JCs-update-boot-cm-default_Plus-DELETE-EV .zip" from the external_sd card.
This zip will set Moboot default OS to CyanogenMod and also delete the Evervolv uImages from the /boot partition if they exist.
Note: You can skip this zip for now and come back and flash it later once you see what I mean.
I basically downloaded JC's file from goo.im and added in the 1 line of code to delete evervolv because I ran into that problem while testing/nearly filling up the boot partition. Previously I modified JC's CM10.1 3.0 kernel Test installer to do it successfully.
(Big thanks to JcSullins and Flintman for the templates)
9. Reboot to 4.4 KK DM OS. Done.
Alright here are the 4.4 KK CMINSTALL v2 download links:
DataMedia CM11 20140409 3.0Kern cminstall v2 JcSullins.zip - 272.68 MB
DataMedia CM11 20140602 3.0Kern cminstall v2 Milaq.zip - 280.28 MB
DataMedia CM11 20140602 3.4Kern cminstall v2 Invisbk.zip - 280.63 MB
DataMedia Ev Ntly 20140530 3.4Kern PAmini cminstall v2 Flintman.zip - 297.43 MB
(EDIT: Link removed/outdated. See RolandDeschain79's "Easy Install" threads)
Reminder:
At this point with your TouchPad booted to 4.4 KK and if connected to your PC, you may or may not be able to see both SD cards depending on the ROM you choose. If you can't see the original WebOS "external_sd", you can boot to webOS if you really need to. See the quote below for details.
FYI:
- Want to go back? Run AcmeUninstaller2 and go from there.
- CWM Data Media backup files are stored in the same folder but have extra "context" files that are not present in backups made from the original recovery. I doubt that any prior recovery backups can be restored by a Data Media recovery and I don't recommend you try it.
4.4 DM KK ROM Links and Features from Post 3:
Mpgrimm2 said:
JcSullins' CM11 Data Media (3.0 Kernel) 04-05-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse (OTG Activation bug fixed)
Milaq’s CM11 Data Media (3.0 Kernel) Nightly Build
Only see’s internal Sdcard ( /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Invisiblek’s CM11 Data Media (3.4 kernel) Nightly Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Flintman’s Evervolv 4.4.2 Data Media (3.4 Kernel) 4-5-14 Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works but has same OTG ID pin activation bug as JC’s CM10.1 3.0 kernel Test
Click to expand...
Click to collapse
4.3 JB DM ROM Links and Info from Post 3:
Mpgrimm2 said:
Milaq’s CM10.2 Data Media (2.6.35 Kernel) Nightly Build
See’s both Sdcards from OS (external_sd and /data/media/0 )
OTG works with USB Mouse
RolandDeschain79 Note: Low battery drain (-4mA to -10mA), h/w video, Audio & Mic, Nightly Builds, Most mature data/media build available, Pie Controls, Inverted Volume controls, Camera, Bluetooth.
Click to expand...
Click to collapse
^^ Back to the OP ^^​

---

This came just in time. I was running the latest official CM (4.0.3). I ran the acmeuninstaller2 and went back to stock on my 16G Touchpad, then went into WebOS and ran the secure erase. Threw the cminstall folder on TP (moboot, cwm 6.0.1.9, rom, gapps) and ran ACMEinstaller5M.
Installed fine. Updated the recovery to the latest selinux, did a factory reset, and could not install the 4.4.2 rom or another recovery because I cannot find the .zip files! Now in limbo with a 4.2 rom and the latest selinux recovery cwm.
I will try to reread all of this so I can get 4.4.2 running properly. I have 4.4.2 roms with selinux recoveries running on all my devices with ART. Would like to get this TP there too.
Edit: Thank you for trying to get everyone on the same page.
When running the acmeinstaller5, it does not set the partitions correctly for 4.4kk roms? No way around using the resize zips? I have a 16GB TP and don't know which to use. I never use WebOS, so I need no space for it.

---

apicia said:
When running the acmeinstaller5, it does not set the partitions correctly for 4.4kk roms? No way around using the resize zips? I have a 16GB TP and don't know which to use. I never use WebOS, so I need no space for it.
Click to expand...
Click to collapse
Acme5 is still setup for standard partition layouts until one of the devs decides it needs work and there is agreement on the sizes. There are other ways to resize the /data (i.e. Taylor, which will allow you to maximize the size) but if someone isn't knowledgeable and careful they seem to make things worse, so the zips just simplify things.

---

Use the 12228 zip. This will leave a few gigs for external sd which some apps require. Thier is currently no way around flashing the zips.
Sent from my SPH-L710 using xda app-developers app

---

I followed the instructions for installing CM10.2 Data/Media Build via cminstall pack v2. When I flashed "16gbTP_Gradular_data_resize_12228-0.1.zip", I got this error:
Ivextent cm-data failed rc=5
>> Failed <<
I ignored it, and installed the ROM and the Gapps package. I connected my device to my computer, and I found only the internal storage (1.48GB). I could see only the internal storage in the storage settings too. Please help me.
Thank you.

---

nightfireblaze8 said:
I followed the instructions for installing CM10.2 Data/Media Build via cminstall pack v2. When I flashed "16gbTP_Gradular_data_resize_12228-0.1.zip", I got this error:
Ivextent cm-data failed rc=5
>> Failed <<
I ignored it, and installed the ROM and the Gapps package. I connected my device to my computer, and I found only the internal storage (1.48GB). I could see only the internal storage in the storage settings too. Please help me.
Thank you.
Click to expand...
Click to collapse
It seems that with all the prior testing of the cminstall packs, CWM 6.0.3.6 occasionally doesn't want to play ball and won't flash the resize zips (2 out of 10 fail) . Saw a report of this last night in the rootz thread before work. JcSullins' CWM 6.0.1.9 for the original partition layout seems to work every time. I literally just updated posts 7, and 9 while you were posting.
As a work around now that you are booted with CWM 6.0.3.6 if you don't want to start over again...
(Basically, switch to CWM 6.0.1.9, flash resize zip if you have room to pull from WebOS sdcard still, reboot to initialize, then switch back to the DM Recovery for the ROM)
- Reboot to webOS, connect the TP to PC and copy over JC's Original CWM v 6.0.1.9 (20121215) and Milaq's CWM 6.0.3.6 no_metadata to the webOS sdcard.. Eject the TP from PC.
- Reboot to Current Recovery and Reflash CWM 6.0.1.9 and reboot back to new CWM again (verify it says CWM 6.0.1.9)
- Flash the resize zip (it should work now).
- Reboot back to recovery again and reflash correct DataMedia CWM 6.0.3.6 and reboot back to new CWM again (Verify it says CWM 6.0.3.6)
- That should do it. Reboot back to CM10.2 and verify partition sizes and functions
Recovery thread links in post 2
Sorry for the hang up. Getting this DataMedia setup done is a bit of a pia currently. Hope that helps you out. I really have to get to bed. Will check back when I get up. Let me know how it goes.

---

mpgrimm2 said:
It seems that with all the prior testing of the cminstall packs, CWM 6.0.3.6 occasionally doesn't want to play ball and won't flash the resize zips (2 out of 10 fail) . Saw a report of this last night in the rootz thread before work. JcSullins' CWM 6.0.1.9 for the original partition layout seems to work every time. I literally just updated posts 7, and 9 while you were posting.
As a work around now that you are booted with CWM 6.0.3.6 if you don't want to start over again...
(Basically, switch to CWM 6.0.1.9, flash resize zip if you have room to pull from WebOS sdcard still, reboot to initialize, then switch back to the DM Recovery for the ROM)
- Reboot to webOS, connect the TP to PC and copy over JC's Original CWM v 6.0.1.9 (20121215) and Milaq's CWM 6.0.3.6 no_metadata to the webOS sdcard.. Eject the TP from PC.
- Reboot to Current Recovery and Reflash CWM 6.0.1.9 and reboot back to new CWM again (verify it says CWM 6.0.1.9)
- Flash the resize zip (it should work now).
- Reboot back to recovery again and reflash correct DataMedia CWM 6.0.3.6 and reboot back to new CWM again (Verify it says CWM 6.0.3.6)
- That should do it. Reboot back to CM10.2 and verify partition sizes and functions
Recovery thread links in post 2
Sorry for the hang up. Getting this DataMedia setup done is a bit of a pia currently. Hope that helps you out. I really have to get to bed. Will check back when I get up. Let me know how it goes.
Click to expand...
Click to collapse
When I flashed the resize zip, I got this error:
Scanning media (SD card)
fsck.vfat media failed rc=1
>> FAILED <<
I made sure I was on CWM 6.0.1.9. Same result with both the 8192mb and 12228mb zips.
Thanks!

---

nightfireblaze8 said:
When I flashed the resize zip, I got this error:
Scanning media (SD card)
fsck.vfat media failed rc=1
>> FAILED <<
I made sure I was on CWM 6.0.1.9. Same result with both the 8192mb and 12228mb zips.
Thanks!
Click to expand...
Click to collapse
Trying starting over with acmeuninstaller2. Then use acmeinstaller5 to install moboot and jc's 6.0.1.9. Flash the 8GB resize zip for 16GB TP (that will leave about 3GB free in WebOS). Reboot into recovery. Flash TWRP provided. Reboot into recovery. Flash ROM and gapps. Reboot.

---

Thanks for the assist Apicia.
Sent from my "Up All Night Sleep All Day" Nexus 5!

---

apicia said:
Trying starting over with acmeuninstaller2. Then use acmeinstaller5 to install moboot and jc's 6.0.1.9. Flash the 8GB resize zip for 16GB TP (that will leave about 3GB free in WebOS). Reboot into recovery. Flash TWRP provided. Reboot into recovery. Flash ROM and gapps. Reboot.
Click to expand...
Click to collapse
Did you mean Flintman's TWRP v2.6.3.0 SeLinux Alpha Touch? According to mpgrimm2's second post, CM10.2 can't be flashed using this recovery. I tried it anyway, and the install failed.
I flashed CWM 6.0.3.6 instead of TWRP, and installed the ROM and gapps package. I'm able to see both SD cards now.
Thanks for the help, apicia and mpggrimm2.

---

@nightfireblaze8,
So are you up and running on cm10.2 with resized partitions and cwm 6.0.3.6?
Sent from my "Up All Night Sleep All Day" Nexus 5!

---

mpgrimm2 said:
@nightfireblaze8,
So are you up and running on cm10.2 with resized partitions and cwm 6.0.3.6?
Sent from my "Up All Night Sleep All Day" Nexus 5!
Click to expand...
Click to collapse
Yeah! So far, everything is working well.