Android OS Forum banner
1 - 20 of 135 Posts

·
Registered
Joined
·
460 Posts
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.

XDA 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-06-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.
.
 

·
Registered
Joined
·
460 Posts
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.
  • Couldn't Flash "data_plus" zips from The_Ape or Gradular.
  • 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

- 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 may 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 ^^
 

·
Registered
Joined
·
460 Posts
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) 4-5-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 ^^
 

·
Registered
Joined
·
460 Posts
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).
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 ).
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)
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.
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 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 ^^
 

·
Registered
Joined
·
460 Posts
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
0HPTPStdBootpartitionexample_zps81c8d751


image
1CM101Romzipformatscripts_zps0bdd5c7a.jp


image
2EvevolvRegampDataMediaUpdaterScript_zps


image
3CM102andCM11DataMediaUpdaterScripts_zps


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 ^^
 

·
Registered
Joined
·
460 Posts
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 ^^
 

·
Registered
Joined
·
460 Posts
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 - 259.01 MB

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 ^^
 

·
Registered
Joined
·
460 Posts
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 recover, from a non selinux recovery first and then Flash the 4.4.2 rom and gapps package.
Option 1 - Moving on to a 4.4 KK Rom ( 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) 4-5-14 Build

  • See's both Sdcards from OS (external_sd and /data/media/0 )
  • OTG works with USB Mouse (USB 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) 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
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.
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 ^^
 

·
Registered
Joined
·
460 Posts
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.
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). 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

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 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

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) 4-5-14 Build

  • See's both Sdcards from OS (external_sd and /data/media/0 )
  • OTG works with USB Mouse (USB 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) 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
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.
^^ Back to the OP ^^
 

·
Registered
Joined
·
460 Posts
Posted 14 February 2014 - 03:35 AM

mpgrimm2 said:
Snowed in. Can't get any solid answers so, data media (DM) testing is in progress. I have my 32Gb TP set up with:
- 6.7Gb external_SD (orig. WebOS /sdcard/ )
This should let me jump back and forth between DM and Non-DM builds.
- 20Gb /data partition (for /data/media/0 "internal" sdcard)
Thanks Gradular for the zip!
- 600Mb /system partition (other defaults from ACMEinstaller5 series).

I also have all 5 data media recoveries and Jc's original Cwm 6.0.1.9 zips on both scards.
- Jc's original Cwm 6.0.1.9 (no data media support)
- Milaq's cwm 6.0.3.6 DM no_metadata
- Milaq's cwm 6.0.4.7 DM SeLinux
- Invisiblek's cwm 6.0.5.4 ? DM SeLinux
- Philz cwm 6.0.4.7 DM SeLinux (TWRP and cwm format support)
- Flintman's TWRP 2.6.3.0 DM SeLinux Alpha

I also have the following ROM and gapps zip packages on both sdcards:
- Jc's CM10.1 01/25/14 3.x kernel test
- Milaq's CM10.2 DM 02/10/14 2.6.35 Kernel
- Milaq's CM11 DM 02/10/14 3.0 kernel
- Invisiblek's CM11 DM 02/10/14 3.4 kernel
- Flintman's Evervolv 4.4.2 DM 02/10/14 3.4 kernel

I will keep track and report back on the results on what can flash what. Time to play. This will take a while, stay tuned.

I am checking for:
- Does the recovery mount "Usb Storage" to a windows pc for file transfer?
- Can the recovery format the partitions appropriately?
- Can the recovery successfully flash each rom and gapps?
- Which sdcard partitions are available to the recovery? (i.e. original /sdcard/ and, or, /data/media/0 )
- Can the Recovery successfully flash either the_ape's or Gradular's Data_Plus zips after AcmeUninstaller2/AcmeInstaller5?
(this will be done separately from the rest because of time constraints)

I am also checking the roms once booted for:
- Which sdcard partitions are available to the OS? (i.e. original /sdcard/ and, or, /data/media/0 )
I am checking this with a basic playstore setup using EsFileExplorer and/or Freespace apps.
- Does USB OTG work (ie with wireless mouse) and check for ID pin activation bug.
( I am probably one of the few with a TP set up to check for this ).
 

·
Registered
Joined
·
460 Posts
Posted 17 February 2014 - 07:29 AM

mpgrimm2 said:
I discovered part of the glitch... If I just flash Moboot 3.8 and Cwm v6.0.3.6 via Acme5, and then run the data Resize zips from Milaq's CWM v6.0.3.6 DM it will work, but if I include CM10.2 DM and Gapps (all 4 files) via Acme5 (or Acme5M) then it won't work after CM10.2 has finished booting up for the first time. It might still work if you catch ClockworkMod from Moboot screen before first load of CM, but I don't know for sure and may not go back to test it, idk.

Summary: Jc's CWM v6.0.1.9 will consistently flash any of the the_ape's data_plus or Gradular's data_resize zips. Milaq's CWM v6.0.3.6 DM will do it but the sequence of events has to be correct otherwise you have to load Jc's Cwm v6.0.1.9, resize /data, and jump back to Milaq's CWM v6.0.3.6 DM.

RolandDeschain79 and NT, check your PM's, I think I have a new "version 2" cminstall pack that will solve the issue of first Data Media install for CM10.2. It seems quite reliable but it has to be broken into a few more steps. I have acmeuninstalled, wiped Sdcard from webOs, and reinstalled about a dozen times in the last few days working it out.

PS:

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.
 

·
Registered
Joined
·
460 Posts
Posted 18 February 2014 - 02:52 AM #45

topher67 said:
So none of the current recoveries that support data/media builds can mount usb storage under win 7 whilst in recovery mode?

Thanks again mpgrimm2!
Kind of silly isn't it?

If you don't transition correctly, you won't have an easy way to get the files to the sdcard that is seen by the recovery and you won't have anything to flash.

Some of the difficulty getting switched over to data media builds and repartitioning could be avoided by having a recovery that can:
- see both sdcard locations
(some of the OS's can though)

- mount USB storage to winPC.

- Able to flash the resizing zips
(NO ONE seems to have ANY explanation on why only JcSullin's Cwm 6.0.1.9 and Milaq's Cwm 6.0.3.6 DM are the only ones that will work).

- Able to support all data/media builds
(i.e. both CM10.2 no_metadata and 4.4 kk SeLinux builds)

None of the recoveries support all features. It is piecemeal at best and requires a few jumps to get where you need to be.

There are also a few issues with the CM ROM install updater-script that can cause limited /boot space if you were previously on another ROM (i.e. Evervolv). It can be easily prevented by adding in a few lines of code to delete prior ROM from boot and set CM as default OS in Moboot just like the Evervolv script does. Or it can be prevented by standardized android filenames for the boot partition so the files are always overwritten and duplicates/extras are avoided.

Sent from my "Up All Night Sleep All Day" Nexus 5!
 

·
Registered
Joined
·
460 Posts
Nevertells said:
Been trying to wade through all the posts, notes, suggestions and impressions. :dafuq: Pheew!!!!! I'm worn out. You sure have covered the gambit and then some. I'm trying to decide if I want to subject myself to a data/media install. The amount of data I will have to move or remove to do a proper install is not going to be fun especially if I decide to return to my current setup. Would have been so nice it this had all been the norm from the beginning. And as I continue to read the data/media threads by Invesiblek, Milaq and Flintman, I am still not convinced that enough issues have been resolved to make me even want to try any of them. If I had to pick, it would probably be Evervolv as he seems to have less issues to resolve than the others, is more responsive to user posts than the others and keeps everyone informed of what he is up to. I am not saying that Milaq or Invesiblek aren't doing anything, they just aren't very forthcoming about their progress.

I am convinced that the best method to set up one's TouchPad is using the zips rather than Tailor. Most everyone knows how to flash a file from recovery. Tailor on the other hand is way too labor intensive and requires a lot more technical expertise than most of the average users out there have.

I also think that at this point, with all the research and testing that has been done, that we need to start developing a standardized method of installing a data/media Rom. And, I don't think the developers are going to agree to standardize the naming of their images that get installed in /boot. The only fly in the ointment with standardization is how do you support the guy who just wants to upgrade and the rest who are rabid flashers who jump around from Rom to Rom? The process for preparing and upgrading is one thing. What happens if the user does not like data/media and wants to go back to the way their TouchPad was before installing a data/media Rom? Well, depending on which philosophy they follow, their original SD card has been cleaned to oblivion, if they weren't careful they lost their backup of their old installation and all their data, ie., music, pictures, videos are gone too. OH, yeah, we still have the issue of not being able to see both SD cards.

Well, if I get up the nerve to take a run at this and see what I can see, I'll come back and update with my observations.
.
 

·
Registered
Joined
·
460 Posts
Posted 24 February 2014 - 05:55 PM #55

I have been on Invisiblek's CM11 DM 3.4kernel (2-20 build) for a few days but kept randomly getting the "sleep of death" mentioned in the OP requiring "Home + Pwr" to reset. Got a bit annoyed with it, wiped cache and flashed Milaq's CM11 DM 3.0Kernel (2-20) build to test for a day or two. I think I am working my way back to Flintman's Evervolv 4.4kk DM 3.4 kernel or back to Milaq's CM10.2 DM w/2.6 kernel (originally recommended by RolandDeschain79). It has been a bit of a pain, but I have been restoring most of my apps with Ti Backup.

Flintman is at least aware of my suggestion on the filenames and willing to discuss it with the devs, but I haven't heard anything yet.

I am sure you can walk through all the details to get to a DM build if you want but here's another less clean option (still move the backup off the TP):

If you already have a 600mb system partition and depending on the amount of original sdcard space you use now, just convert the rest over to /data with CWM 6.0.1.9 and Gradular's zips. On my 32Gb TP I found I previously used about 5Gb of the sdcard, so using the 20gb data_resize zip left me about 6.9gb on the original sdcard to go back more easily and keep those regular backups and recovery zips available (Jc's CWM 6.0.1.9, Milaq's Cwm 6.0.3.6, and Philz CWM 6.0.4.7).

Note: I am still trying to get someone with a 16gb TP to fill in the left over sdcard sizes after using the 2 data_resize zips.

(the 8Gb data_resize will likely leave about 5-6gb for the old sdcard, but idk yet).

Once you have a bigger /data, just flash the new recovery, perform a factory/data reset, and flash a DM build and gapps (original sdcard left alone).

To go back and keep the larger /data, reflash cwm 6.0.1.9, format system, data, cache, and restore a backup (will wipe the /data/media/0 sdcard).

or run AcmeUninstaller2 to reset all the partitions and clear off android, and reflash original setup with acmeinstaller5.
 

·
Registered
Joined
·
460 Posts
Nevertells said:
I don't know how much longer Flintman wants to try to keep up with two different builds. The obvious direction of the builds is data/media, so if anyone wants to keep up with the evolution of the builds on the TouchPad, then they are going to have to get used to installing and updating data/media builds. I agree 100% that the process of a clean or fresh install is a royal PIA. Grimm has spent days sorting it out and has narrowed it down to a limited number of steps with a minimum of confusion. The more users who voice their dissatisfaction with the current process will hopefully get the attention of the developers and hopefully they will do something about it. That is why I said in post #58:

"What needs to be done is a recovery like Philz that can flash all the resize zips that right now only 6.0.3.6 and the original CWM6 can. We need one ACMEInstaller and one ACMEUninstaller that can do it all. Installing a data/media Rom should not have to be a PIA to install or upgrade. It should require no more effort than what was required to install older versions of CM and the other Roms."

And posted a warning in post #60.

Through Grimm's efforts the process of installing a data/media Rom on a clean TouchPad or upgrading from a non-data/medial Rom, is down to the following:

1. Run Acmeuninstaller2 to remove android (if upgrading from a non-data/media Rom)
2. Boot to WebOs and reset/wipe the Sdcard to clear out the last bits of Android(this frees up ram for the resize step below)
3. Run ACMEInstaller5 to install Moboot 0.3.8 and CWM 6.0.3.6 DM
4. Boot to CWM v6.0.3.6 and run the appropriate data_resize zip. Immediately reboot back to CWM, this initializes the resize
5. Now with CWM v6.0.3.6, install Milaq's CM10.2 DM and Gapps for Android 4.3
6. Now use CWM v6.0.3.6 to install Philz CWM v6.0.4.7 DM SeLinux
7. Use Philz CWM v6.0.4.7 DM SeLinux to install whatever version of Android 4.4.2 and it's gapps you want.

Now that is just the basic steps laid out without links to files needed and instructions for housekeeping you need to do. You will find all that in Grimm's post #56. If Grimm had not done all the homework, testing and finally writing that guide, we all would still have to jump around several different forums trying to sort out what to do. There still would be a lot of confusion on which recovery to use for which step during installation or with which Rom.

Now if you all want to have to continue to do it Grimm's simplified way(groan), then make yourselves heard to the developers that something needs to be done. The developers want us to adopt their vision of what Android installed on a TouchPad should be like. That's great, but they also need to provide the support via the installers and recoveries that keep that vision as uniform and easy as possible.

My hat of off to Flintman for continuing to provide a temporary method of testing Android 4.4.2 without having to endure the hassle of a data/media installation.

And my hat is off to MPgrimm2 for making the effort to simplify the process of trying to follow the developer's vision.
 

·
Registered
Joined
·
854 Posts
Great thread! Im currently rewriting the resize scripts but its a lil bit more involved then I thought. I hope to have something to test tonight or tomorrow that will make the data the intended size no matter if it is more or less then the current size. Ill post it here as well as my thread.

Sent from my SPH-L710 using RootzWiki mobile app
 

·
Registered
Joined
·
225 Posts
I finally got around to doing this myself last night, as I got tired of Chrome always freezing on me and making my Touchpad reboot. It was a single, continuous installation from the first CM7 build to whatever CM10.2 build I was using, so it had a good run. I had a hell of a time finding all the files I needed, since apparently the time I chose to finally make the move to KitKat and an internal storage build was the same time information's getting reorganized around here or whatever the deal is, but I managed it after a fashion. My installation process differed a bit from what you quoted from Nevertells, so I'll detail it:

1) I backed up what I wanted (my Nova Launcher backup, CircleLauncher backups, the CM10 boot animation (Cid is lame), and some games' save data, basically), then rebooted into USB boot mode and ran ACMEUninstaller2
2) Then I booted to WebOS, wiped the user storage, added the zips for Moboot 0.3.8 and Milaq's CWM 6.0.3.6 (from post #2 of this thread) to a cminstall folder, and added the zips for Invisiblek's latest CM11 build (which I had to Google for at the time) and KK Gapps, Flintman's TWRP, and the 24GB resize script to the root
3) I rebooted into USB boot mode and ran ACMEInstaller5M
4) On reboot, I went into CWM and installed the resize script zip, rebooted again and installed TWRP, then rebooted again and installed CM11 and Gapps
5) Finally, I rebooted into CM11 and after a lengthy first boot, I went through the Android setup wizard and set about restoring my homescreen layout and such once all my apps were reinstalled.

Other than having to get used to the volume buttons being switched back to normal in landscape mode, rather than being reversed like in 10.2, I've had zero issues. It's only been a day, true, but most of the issues I've ever had in the past made themselves known rather quickly.
 

·
Registered
Joined
·
460 Posts
Thanks for the post Executor, that is one of the ways to get a DM build installed. I very much like TWRP's touch interface and the ability to see both sdcards, but aside from it not being able to flash the resizing zips I also had a few hit or miss occurrences of it not wanting to flash the DM Roms and Gapps without a few reboots back to recovery. If it could mount the sdcards to PC I would likely prefer it. Let us know if you see any of those issues.

FYI, Philz Cwm 6.0.4.9 is also compatible with TWRP backups. And there is or was an option to switch the volume button orientation under settings--> interface I think.

If you need flash to work, this is what I use....

[Guide][Flash]How to play flash video on Android 4.4 Kitkat

Sent from my "Up All Night Sleep All Day" Nexus 5!
 
1 - 20 of 135 Posts
Top