Related
IRC on freenode: #sk8erwitskil
NEW: I have created a script to easily update to the latest version of my recovery.
- Download this file ----> updater.sh
- Put it on your sdcard
- open adb and type:
Code:
su
sh /mnt/sdcard/updater.sh
- it will reboot you into recovery and automatically install recovery and reboot
- only ATT version is supported right now
- must be on at least v14.4.7 for script to work
Click to expand...
Click to collapse
Here is a video of how it works: --------> YOUTUBE LINK
Flashable zip:
cwm6027touch_v14.4.7_geeb.zip: ---------> DOWNLOAD
Click to expand...
Click to collapse
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
[/CODE]
Current Version:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Click to expand...
Click to collapse
Major update to how touch works now:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Whats in the extras menu?
- change bootanimation (this lets you select a bootanimation form your internal sdcard. it backs up your current bootanimation to /{internal sdcard}/clockworkmod/ba_backup/. it only backs up the original bootanimation so if you keep changing your bootanimation you will still only have your original one in ba_backup.)
- enable/disable one confirm (this makes it so you only have to scroll through one confirm selection when installing something instead of having to go through 10 of them to click yes)
- hide/show backup & restore progress (this makes it so the progress bar when you backup/restore doesnt show up and makes backups/restores a bit faster since it doesnt have to show you the progress and files its backing up)
- select android_secure on internal/external (use this to select where you have .android_secure. default is internal, so if you have it on external make sure to choose this once to set it up)
- aroma file manager (file explorer)
- create custom zip (this will create a custom rom from the currently installed files you have on your phone. it takes your /system partition and /boot partition and makes them into a zip file ready to be flashed. the end product will be in clockworkmod/custom_rom/. this has recently been fixed to work on all phones/roms
- choose custom openrecoveryscript (read THIS)
- recovery info (shows the version of recovery and the build date)
- Special Backup & Restore (backup and restore your kernel/boot and /misc partitions)
- Misc Nandroid Settings (change time zone, turn preload support on/off (default is off), enable md5 checking, disable assert check)
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
it doesn't work although it flashes successfully all I get is a kernel crash, tried manually booting into recovery and adb reboot recovery no dice. btw I am rooted with an unlocked bootloader.
sk8erwitskil said:
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
Click to expand...
Click to collapse
are u gonna work on roms for this phone
Sent from my LG-E970 using xda premium
sk8erwitskil said:
i dont actually have my LGOG yet. it comes on monday. once i get it tho i should be able to have a completely stable build in less than a week
Click to expand...
Click to collapse
Glad to see you here in the OG forums! Thanks for working on this!
Ok got it to work. I can create a fakeflash that you flash in your current cwm. All touch code is working great which is the hardest part
I'm gona have to make some ramdisk edits to make an installable recovery.img. hopefully iomonster gets back to me on how he fixed the ramdisk to get it booting
Sent from my LG-E970 using xda app-developers app
sk8erwitskil said:
Ok got it to work. I can create a fakeflash that you flash in your current cwm. All touch code is working great which is the hardest part
I'm gona have to make some ramdisk edits to make an installable recovery.img. hopefully iomonster gets back to me on how he fixed the ramdisk to get it booting
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
You can probably just add etc and default.prop from IO's image to the mako cwm touch.
Sent from my SPH-D700 using Tapatalk 2
got it working great. just uploaded now.
Just installed on e973, works well, looks nice. Thanks for your work.
Installed on my E973 and work nice too. Thanks for the work. If you could add a bit more space between menu item, it would be perfect. I have big finger
Gr8 stuff sk8. Only problem i found is the md5 mismatch bug (it doesn't create an md5sum while creating backups). No biggie, but if it's easily fixed it'd be nice to not have to make an md5 manually every time.
Also curious if it's possible to change the font. Thanks!
chadouming said:
Installed on my E973 and work nice too. Thanks for the work. If you could add a bit more space between menu item, it would be perfect. I have big finger
Click to expand...
Click to collapse
Yah this isn't a final product at all. I will be making more updates soon. And this is one of them
carrett said:
Gr8 stuff sk8. Only problem i found is the md5 mismatch bug (it doesn't create an md5sum while creating backups). No biggie, but if it's easily fixed it'd be nice to not have to make an md5 manually every time.
Also curious if it's possible to change the font. Thanks!
Click to expand...
Click to collapse
Hmm I've never encountered this bug and ive been using this exact recovery on my other devices for a long time. Can you create a backup and pull /tmp/recovery.log when you do?
Sent from my LG-E970 using xda app-developers app
I'll have an update tomorrow that fixes the background and font sizes and a few other features.
Sent from my LG-E970 using xda app-developers app
sk8erwitskil said:
I'll have an update tomorrow that fixes the background and font sizes and a few other features.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
nice, I always favor the touch recoveries it make navigating thru the menus so much easier without having to mash the volume/power keys all the time :laugh:
Any chance you could make this a flashable zip?
davideholland said:
Any chance you could make this a flashable zip?
Click to expand...
Click to collapse
Yes I will do that.
Sent from my LG-E970 using xda app-developers app
I second the flashable zip. Tried the other methods and have failed for some reason
Sent from my LG-E970 using xda app-developers app
Will this work on the sprint version too?
Sent from my LG-LS970 using xda app-developers app
Has the MD5 issue been fixed in the release yet? I saw it mentioned but I didn't see any posts that stated it was fixed in the current release. Thanks for the clarification.
Another port of my custom recovery.
For the aroma file manager option to work you have to flash the zip at least once as the zip file will put aroma in the correct place on your sdcard.
Download ------> cwm6032touch_v15.0.2_m7.zip
Thanks to :
gweedo767 (for creating the original touch recovery)
koush (for creating CWM)
PhilZ (for his amazing improvements and help with applying universal touch code) BIG THANKS!
htc-msm8960 for their device tree
PREVIOUS VERSIONS:
Code:
v1:
[CODE]initial release
v2:
Code:
- updated to latest version of clockworkmod
- add reboot download option
- add reboot recovery option
- add power off option
- change font size
- add various internal/external sdcard options from cwm 5.5.0.4 touch recovery
- change order of internal/external sdcard so internal comes first on backup/restore/install
v3:
Code:
- add support for phones that sdcard mounts as external_sd
- fix the line below the menu to actually be below the menu
- clean up the "andy the android" picture. (if you make a backup you will see that the picture in the background has been poorly edited. there are bits of black spots around him)
- JellyBean Background
v4:
Code:
- fixed missing slash that was not allowing installs from external sdcard
v5:
Code:
- update to latest version of CWM 6.0.0.8
v6:
Code:
- updated to latest version of CWM 6.0.0.9
- added ability to delete nandroids from recovery (in backup and restore menu)
- changed order of internal/external so external comes first
- fix timestamp creation on backups
v7:
Code:
- updated to latest version of CWM 6.0.1.0
- fixed bug that would not allow backup of /system
v8:
Code:
- update to latest version of CWM 6.0.1.1
- allow customization of backup format (dedupe/tar)
- use minizip tool instead of e2fsck, etc.
- more....
v9:
Code:
- update to latest version CWM 6.0.1.2
- fixed bug where backing up to external wouldnt backup /emmc/.android_secure
- ADDED DUAL LUNFILE SUPPORT! (thanks to topprospect for this!)
-- what this does is when you mount USB storage you
will see both of your sdcards mount at the same time
- various /emmc fixes (recovery now looks for all clockworkmod "." files in /emmc instead of /sdcard)
- this is useful for people who dont use an external sdcard at all
v10:
Code:
- grabbed latest commits to official CWM 6
- added new extras menu (look in 2nd post for info)
- some other stuff i dont remember
v11:
Code:
- fixed hide nandroid progress bug (it now works)
- added sk8's fix permissions option (logging is disabled so it runs faster and it also clears stale data directories)
- fixed bug where normal fix permissions wouldnt create a log to correct location
- cleaned up some syntax
v12:
Code:
- added darkside wipe/super wipe built in
- added aroma file manager built in
- added ability to backup/restore the /efs partition
- cleaned up oneconfirm/hidenandroidprogess features to be one menu item
- more......
v12.5:
Code:
- fixed bug where darkside cache scripts wouldnt work
- added option to create a custom zip (read 2nd post)
v13:
Code:
- report log gets copied to /emmc instead of /sdcard
- add support for roms without busybox (stock roms) to create a custom rom zip
- add support for openrecoveryscript (read [URL="http://forum.xda-developers.com/showpost.php?p=31093552&postcount=344"]THIS[/URL])
- add support to choose a custom created openrecoveryscript
- use goo-manager to flash roms and create openrecoveryscripts
- now detects where android_secure is automatically
- fix ors-mount.sh to work even if 'sdcard' is in the path
- misc code cleanups.....
v13.1
Code:
- bug fixes
- android_secure fixes
v13.2
Code:
- that pesky android_secure - bugfixes for restoring android_secure
v13.3
Code:
- updated to latest 6.0.1.4
- some bugfixes
- added option to select where android_secure lives (hopefully this is the last time. i promise)
v13.4:
Code:
- updated aroma file manager to latest version
v13.5:
Code:
- add initial support for whole-device encryption (thanks topprospect)
v14:
Code:
- updated to latest CWM 6.0.1.5
- fixed some mtdutils issues
- added a bootanimation changer
v14.1:
Code:
- not released
v14.2:
Code:
- added bootanimation change selection from external sdcard
- added newest aroma filemanager w/ console support (you can use terminal in recovery)
- updated to latest changes of official CWM
- added support for Android 4.2
- zip file now installs updater.sh to your internal sdcard
- updated updater.sh to fix typo
v14.2.1:
Code:
- openrecoveryscript automatically runs if script is found in /cache/recovery/
- this is good for using my updater.sh or goomanager
v14.3
Code:
- skipping this number to keep in line with my other devices
v14.3.1
Code:
- lots and lots of under the hood improvements
- re-wrote OpenRecoveryScript and efs backup/restore code
- these work alot better now (thanks so much to PhilZ for his amazing help)
- add option to backup/restore boot.img from sdcard
- now using latest stable kernel
- completely re-wrote the touch code for some improvements
- now to select you tap anywhere on the screen
- fixed some typos
- made my source code universally compatible with all phones using ICS or greater
- compiling in jellybean base recovery code now
Code:
v14.4
- fixed soft keys (virtual keys on bottom) (credit to PhilZ for this)
- reverted back to swipe to select
- tweaked some features in the extras menu
Code:
v14.4.1
- messed up on the mount points so i fixed them now
- added some buffer to fix ability to accidentally select wrong item
Code:
v14.4.5
- skipped some versions because they were made for other phones
- re-wrote the create custom backup feature to be universal now with all phones/roms (thanks to PhilZ for the help)
- added new settings menu
- add ability to change timezone
- added /preload support [B](must go and enable it in misc nandroid settings)[/B]
- add rom name to nandroid names
- more i just cant remember now....
Code:
v14.4.6
- added exFAT support
- some under the hood optimizations
Code:
v14.4.7
- added extras>>misc nandroid settings>>disable assert check
- removed black space in error icons
- some under the hood optimizations
- added updater.sh script
Code:
v15.0.0
- updated to latest cwm source
- added HTC One into the group
Code:
v15.0.1
- fix zip file
[/CODE]
Current Version:
v15.0.2
- update to latest cwm official changes
Click to expand...
Click to collapse
How touch works:
UP - swipe finger up on screen
DOWN - swipe finger down on screen
SELECT - swipe finger from left to right
BACK - swipe from right to left
SOURCE: https://github.com/sk8erwitskil/touch_recovery_cm10.1
This is what the new dedupe format does. This is a direct quote from the original creator of clockworkmod:
Code:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard(or emmc)/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Sk8! Glad to see you deving here! You did such a great job with the skyrocket... Are you getting this phone/do you have it?
Sent from my SGH-I927 using xda premium
spitfire2425 said:
Sk8! Glad to see you deving here! You did such a great job with the skyrocket... Are you getting this phone/do you have it?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
yah my work bought it for me so ive been doing a little dev work on the side for it
sk8erwitskil said:
yah my work bought it for me so ive been doing a little dev work on the side for it
Click to expand...
Click to collapse
sk888888888888888888888888888888888888888888 let's do some work on the beast of an htc one I've got the Canadian one
Awesome man. Just the more reason to get this phone. Just 3 more weeks....
Sent from my SGH-I927 using xda premium
Glad to see you here sk8, great work!
heh this thread is like a little reunion.
this was the easiest phone to port my recovery too. only think i need to fix is the offset for the battery display in the right top corner.
sk8erwitskil said:
heh this thread is like a little reunion.
this was the easiest phone to port my recovery too. only think i need to fix is the offset for the battery display in the right top corner.
Click to expand...
Click to collapse
Yeah. I noticed that. No biggie. Aroma seems to work great on this recovery. The display actually looks correct.
Now to get my stock rooted backup converted to CWM format as a failsafe in case I have to go back to stock due to the lack of AT&T RUU images.
tiny4579 said:
Yeah. I noticed that. No biggie. Aroma seems to work great on this recovery. The display actually looks correct.
Now to get my stock rooted backup converted to CWM format as a failsafe in case I have to go back to stock due to the lack of AT&T RUU images.
Click to expand...
Click to collapse
i dont think there is a way to convert from twrp to cwm atm. if you need that backup you can just make a backup of your current rom on cwm, then flash back to twrp, restore that stock rom, flash cwm then backup the stock rom, then restore your custom rom.
Been waiting for an update for this much underrated recovery. I like the gestures in this one over the click on item to select it.
literally working on it as i type this
There's a pesky bug in my code. New release is going to be delayed a day
Sent from my HTC One using xda app-developers app
Dude, this recovery is insane! You might have just swayed me from twrp.
Great job!
any update for this sk8?
Note to developers, Philz touch is fully open source. Please feel free to create your own builds. However, this thread is sanctioned officially by Phil. The builds posted here have been built under the conditions set out by Phil. Please do not post your own builds in this thread. I cannot support builds made by other people so please don't use them then post for help here.
Note from the thread author, please note - I am not the developer of Philz Touch. @Phil3759 is. I am merely an avid follower of Philz amazing efforts and the official Nexus 5 maintainer.
Please take a moment to thank Phil for his work by clicking "Thanks" on THIS POST
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please note, USER queries / support for the Nexus 5 should be posted in THIS THREAD, and NOT in the main DEV thread.
I won't be compiling every build. I will skip builds that do not add /alter functionality to the Nexus 5 for obvious reasons.
I will only compile if we have:
New or updated Features relevant to N5
Bug Fixes
Code clean-up or libtouch_gui shouldn't affect the user experience. I don't want to keep bugging Phil to upload trivial builds to goo.im - so please don't get disheartened if not every version number from Philz master thread makes it to N5
Features:
F2FS migration support
Recovery Lock
Root directly from Recovery menu
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
optional reboot after custom backups/restores
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
adb root in recovery: just wait about a minute to activate
Download links
Latest version can be found here:
http://d-h.st/users/rootsu/?fld_id=34576#files
Click to expand...
Click to collapse
Backup versions (updated monthly):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hammerhead
Click to expand...
Click to collapse
*Zip is custom recovery flashable, or you can extract the .img and fastboot flash in the normal way
Please note, not every new version contains commits that benefit every device, so the version in this thread title may not always match the version in the development thread title. Please do not ask for ETA in this thread or the development thread. New versions come as-and-when.
Main thread (device support) + features (extended)
http://forum.xda-developers.com/showthread.php?t=2201860
Please note, USER queries / support for the Nexus 5 should be posted in THIS THREAD, and NOT in the main DEV thread.
{
"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"
}
Nexus 5 known issues / FAQ
Nexus 5 specific changes:
Nexus 5 specific changes are listed below. Please note, not all of these changes were in a single release of Philz. This is a list of changes for the latest version released for the Nexus 5 and all skipped versions released since the previous release for the Nexus 5.
For full change log, please click HERE
Changes between 6.57.9 and 6.57.5
Fixes
-Fix Free Browse mode
Changes between 6.57.5 and 6.50.2
Fixes
-Potential failure to reboot
-Potential failure of TWRP backups
-Regression bug in Advanced menu
-Crash by calling ui_print or LOGE on early recovery init
-Wake-up screen could fail or take a few seconds to reset brightness
-Memory overflow potential issue
Visual
-Group all wipe otions under a same men
-Enhance menu titles
-Keep only mount and storage options in the corresponding menu
-Enhance highlight of virtual keys
-Tweak default recovery keys
-Don't show mount usb storage menu when it is not available
-Always show text in sideload mode
New
-enable screen capture through adb shell
-option to disable md5 from edify restore_rom command line
-support wipe_cache and clear_display edify script commands
Improvements and updates
-SuperSU 2.02
-use built in busybox tar instead of libtar
-drop fb2png binary support
-restore custom rom: preserve selinux attributes
-do not wipe /data/media on wipe_data recovery start command
-do not show mount/unmount /sdcard on /data/media devices …
-support more moint points for /data/media detection
-enhance code to toggle /data/media multi user support
-enhance code to mount auto file system
-do not double confirm formatting /data/media during ext4 <-> f2fs con
-optimize memory resources
-never confirm wipe in ors scripts
-mounts: match aosp sources
Changes between 6.50.2 and 6.47.4
- Various (as yet unspecified) changes
- merge multi stage install packages support from AOSP
- CWM 6.0.5.0
- add option to directly parse time_daemon data files
- refresh current time in menu header after time daemon fixes
- fix first passkey prompt screen did not show proper background under some circumstances
- preserve background icon user settings after sideload, install zip and wipe actions
- use real fstype instead of auto in /etc/fstab when converting between ext4 <-> f2fs using extra.fstab
- recovery lock: support use of virtual / capacitive keys as pass key
Changes between 6.47.4 and 6.47.3
Bugfix version. Fixed adb issue when no keypass set
Changes between 6.47.3 and 6.43.6
See recommendations at the bottom of this post for details on recovery lock...
- add recovery lock with passkey on start (secure your data from recovery intruders)
- fix segfault during shell nandroid backup/restore commands
- enable progress display during "adb shell nandroid backup/restore" commands
- enhance and fix bugs of progress display during install/nandroid... operations
- nandroid restore: fix progress bar animation when md5 verify is enabled
- nandroid md5: fix progress bar was not reset for each file
- nandroid md5: fix .android_secure md5 sum was never generated or checked
this could cause md5 check to fail under some circumstances
- limit logging to console in adb shell nandroid and mount commands
- fix detection of real fstype (pointer to in the scope char array bug)
- disable useless sd-ext warnings and errors
Changes between 6.43.6 and 6.30.1
See recommendations at the bottom of this post for details on F2FS...
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
- f2fs: compile with prebuilt AOSP kernel as provided by @dennes544 - thanks!!!
- allow ext4 f2fs backup data migration in nandroid
- create /data/media/0 after formsat of /data and /data/media
- nandroid backup: fix 'media' exception
- use libtar as default for backup/restore
- Preserve recovery settings after a wipe
- fix save/restore settings menu label
- create /data/media directory after internal storage is wiped
- fix text print colour could persist after md5 check
Bug Fix version 6.30.1
- fix restore of /data: revert to busybox tar and external selinux backup
Changes between 6.26.6 and 6.29.2
- fix potential bug when verifying root and recovery state on exit
- merge "Fix verify_root_and_recovery menu selections
- hide the Go Back button from confirm menu
- add minitar binary to /sbin instead of busybox tar
- minitar: enable more options, enable long options, fix selinux backup/restore, enhance GNU tar compatibility
- enable seamless backup/restore selinux context using minitar binary
- TWRP mode: support backup/restore of selinux context
- confirm cancel nandroid jobs (prompt to press 'Back' twice or resume after 5 secs)
- vibrate after backup/restore operations
- do not consider su symlink in /system/bin as a broken root
Changes between 6.26.1 and 6.26.6
- CWM 6.0.4.8 rebase
- Fixed rootsu error in fstab
- Removed /efs1 and /efs2 from mounts and storage menu
Changes between 6.23.9 and 6.26.1
- fb2png: better error logging
- sort files using case insensitive order
- remove old no more needed md5 check code
- fix successive gestures
- set these default gesture actions:
* swipe left = screen off
* swipe right = increase brightness
* press 1 sec and lift = show log
* press 2 sec and small move = screen shot
- merge "Only init legacy property environment once"
- revert using ntfs module and drop to fuse for complete write support
- use new md5digest code to generate/verify nandroid backups
- bring progress bar during nandroid md5 generation and check
- exclude log and md5 file when regenerating md5 files
- twrp mode: use new md5digest function with status bar during md5 check/create
- twrp mode: fix double md5 verification bug
- fix delete backup menu failed to reopen base backup folder + wired log message
- fix the "umount: can't umount /data: Invalid argument" log message on start when time daemon was loaded
- show "time daemon loading" message on recovery start when we're waiting for the daemon to load
Changes between 6.23.7 and 6.23.9
- Updated time daemon settings to use hammerhead default dir /data/system/time. Time now works (except Daylight Savings - Change Time zone manually for now to get correct time)
Changes between 6.22.7 and 6.23.7
- Better error checking to avoid segfaulting
- really hammer lazy developers (report outdated binary in ui print)
- Use legacy property environment if old update-binary
- fix fb2png flag to be enabled by default
- fix potential unsafe thread code
- Disable gesture actions during md5 checks as they are not thread safe
Changes between 6.21.2 and 6.22.7
-Qualcomm screenshot (fb2png) functionality added
- USB OTG install zip (black screen) Bug fixed
Changes between 6.20.6 and 6.21.2
- add progress bar while reading zip file to compute md5 check
- add color printing during md5sum checks
- (derp) fix color code printing on md5 check disappears after 5 sec (ui_wait_key() screen refresh)
- md5sum check potential bug fixes and optimizations
- libtouch_gui 1.05
Changes between 6.19.7 and 6.20.6
- add md5 sum calculation and toggle verification during install of zip files
- many bug fixes and code cleanups
- libtouch_gui 1.04
Changes between 6.19.3 and 6.19.7
- add /efs backup support*
Note, efs is split over 2 partitions on the N5. Back them both up in custom backup! DO NOT RESTORE EFS BACKUPS ON ANOTHER PHONE!
Changes between 6.15.4 and 6.19.3
- merge "update-binary: Add collect_backup_data function"
- merge "recovery: add overlay interface for recovery mode"
- merge Aroma patches:
- User selectable colorspace added to settings.
- Unmount /system at exit if mounted.
- Some more logging added
- merge remote cm-11.0 changes
- led state in menu
- more comprehensive menu text display for /data/media/0 toggle
- fix potential memory leak in /data/media/0 toggle
- huge cleanup and potential bug fixes
Changes between 6.12.9 and 6.15.4
- update superSU to 1.93
- sync sources
- fix recovery reboot command (adb and shell) by adding the init sys.powerctl property control
- merge "Fix mkfs.f2fs calling in roots"
- fix display current path when navigating backward in folders
- Nandroid Simple Logging: toggle logging of file names during nandroid to keep screen progress while speed up nandroid operations for some devices
- increase NICE_INTERVAL to 300 msec (faster backup/restore on some devices)
- hide unused settings in Nandroid Settings menu (if we disable all progress on screen, hide non valid options)
- re-order nandroid settings menu
- add a toggle for fall back to pre-built update-binary to permit use of older update-binary in zip packages (doesn't persist on reboot).
this will fix the assert errors due to outdate update-binary. It could still be affected by assert error on device name getprop. However, that one is easier to fix by end users by editing updater-script. This is a workaround. The best is to hammer your ROM cooker to update his scripts and binaries
- setting for signature check toggle on zip updates will be now saved on reboot
- Aroma File Manager: mount vold managed volumes on launch from recovery
- Free Browse Mode: make it possible to install from any custom path even ramdisk
- Free browse mode: fix exceptions when setting up custom path
- Free browse mode: mount known volumes during setup
- Free browse mode: better handling of /data/media devices
Changes between 6.12.8 and 6.12.9
- Update to Stock KOT49H kernel to fix Graphical glitches caused by CM 11 kernel
Changes between 6.09.2 and 6.12.8
- time and date menu text formatting and order
- version display edit
- add ntfs write support to devices using kernel modules instead of fuse
- zip installer: update loki binaries for LOKI devices
- zip installer: use new update-binary sources
- manually set time and date in recovery
- support Qualcom time daemon to sync time with main system (credits to dougiebee)
- support RTC offset hack for Qualcom devices without a proper time daemon in system ROM (credits to dougiebee)
- option to drop to system set time and date commands (credits to dougiebee)
- set default nandroid compression level back to low
- roll out exfat-nofuse sources from dorimanx into various kernels from Samsung and other brands
- code fix and cleanup
- update SuperSU to 1.91
- merge android_system_core changes to adb to fix push to extra storage paths
- do not use performance mode during install zip: fixes hang on unmount /system in updater-script when usb cable is connected
- update to CWM 6.0.4.7
- merge "Fix up bu restore"
- ROM Manager: workaround to backup/restore to/from external storage
- enhance touch init (fix touch on some Sony devices)
- really fix reading device max brightness value
- loki: merge "Support Open EU LG Optimus F6 and US Cellular Optimus F7"
- read the device max brightness setting to fix brightness toggle on some Sony devices
- merge: "Populate mount menu with new mount/format matrix" - final version
- merge: "Use cat for adb backup."
- merge: "Populate mount menu with new mount/format matrix"
- do not error on missing sd-ext when wiping dalvik cache
- merge: "su: Update for latest su daemon compatibility"
- merge "Clean up c formatting - 1"
- merge "Remove "Go Back" option from verify root and recovery options"
- merge "Fix potential chmod failures"
- merge: "Add a copy of the updater binary to the recovery resources"
- merge: "install: Support downgrade scenarios"
- merge: "install: Fix possible overflow condition in the updater "scanner""
- merge: "minui: do not use flexible array initialization"
Changes between 6.07.9 and 6.09.2
- TWRP: merge "support use TW_USE_MODEL_HARDWARE_ID_FOR_DEVICE_ID"
- toggle prompt on low free space during backup
- SuperSU update to v1.89
- loki: merge "Support LG Vu 3."
- code cleanup
- gesture action defaults changed
- long press and lift gesture action is now triggered after finger pressed for more than 1 sec
- do not include fb2png on non supported devices
- stop always rebuilding aroma intermediates
Changes between 6.03.5 and 6.07.9
- fix exiting "pause on logs" mode with virtual keys caused erroneous validation
- fix exiting screen off mode with hardware key could cause erroneous validations
- fix some devices could not exit "pause on logs" mode with screen touch
- bring immediate touch responsiveness after exiting screen off mode and "pause on logs" mode
- fix erroneous first menu validation when exiting screen off mode on some devices
- fix long press and move action could be triggered while swiping outside menus and returning to first touched area
- increase threshold for long press and move action for easier triggering
- small touch scroll optimizations
- improve touch responsiveness on low res devices
- code clean-up and optimization
- fix log text could overwrite clock/battery icons on some low res devices
- after successful zip install with sideload, hide the install background icon
- after installing zip with sideload, do not trigger "pause on logs" mode
- loki: sync latest sources (support LG G2 VS98012b)
- better fit text logs on non HD devices: stop slightly overwrite of bottom virtual keys separation bar and clock/battery area
- fix logs overwriting bottom virtual keys and progress bar in sideload mode
- add 5 extra partitions support in nandroid: can be added in fstab and will be auto detected
- custom backup and restore menu: move reboot item to top of partitions list
- custom backup and restore menu: auto hide all unused items
- advanced menu: hide /data/media toggle for non datamedia devices
- sync loki sources: add new LG devices
- SuperSU update to 1.86
- busybox: merge @Chenglu changes to support selinux (no tar --selinux yet)
- huge code clean ups and fixed
- fix twrp backup/restore default mode
- save loki support user setting (default is now disabled)
- add custom backup and restore options to main nandroid menu for each storage volume
- ditch stock cwm limited advanced restore function
- add toggle to switch between TWRP/CWM as default backup mode
- ors: backup mode is now the default backup mode set for all recovery session
- ors: smart restore mode to override main backup mode depending on path we restore from (TWRP vs CWM auto detection)
- backup/restore validation menu moved to top in custom modes
- sanitize rom name for backup: exclude "&" symbol and fix compiler warnings (size_t)
- when deleting backups, do not exit the menu each time
- fix new line in process_volumes()
- merge: "Don't return immediately from reboot commands."
- merge: "Enable incremental builder to find files that moved"
- merge: "Support recoveries without CONFIG_EXT4_FS_XATTR"
Recommendations
Recovery Lock / Passkey
@Phil3759 has implemented a recovery lock with pass key. This means that you can lock your recovery. Providing you keep your bootloader locked and keep an Android ROM Pattern, PIN, Password lockscreen, this will mean that a "recovery intruder" will not be able to use or replace recovery without unlocking yuour bootloader using fastboot (Which wipes the device). Thieves will no longer be able to look through your photos or find files related to banking on your device.
The Lock comes up at recovery boot. There is no GUI or adb access available until the recovery is unlocked. Please note, this is designed to prevent people getting hold of your data, NOT to prevent them wiping your data. If you decided to use this option, you must ensure that you keep your data backed up on an external device. This recovery is not responsible for data wipe prevention or if you somehow manage to lose access to recovery.
To setup the passkey:
Go into Recovery > Philz settings
Setup recovery lock
Change recovery passkey
You will be prompted to set and confirm your passkey. Passkey is a 6 "character" combination of hardware key presses (Vol up, down and power).
Please note, flashing a ROM will remove the passkey, so you will have to set it up again. Passkey is stored in /system/.recovery_key.lok
F2FS
What is it? - Flash-Friendly File System. designed by Samsung to be used spcifically on Flash media. Can increase Read / write speeds, increasing the overall performance of your phone.
Where to use it? - Since not many read / writes happen anywhere except /data, it's best to use it only on the /data partition (including /sdcard)
Do I need anything special? - Yes, you need an F2FS supported kernel
Can you recommend an AOSP Kernel? - Yes, use the AOSP/CAF kernels created by @dennes544 here. If you need something a bit more custom, flash ElementalX afterwards
Any other kernels that work? - I can't say I have tested them all. So far, I haven't managed to get Faux to work. I have used a custom version of Franco however and that worked fine (see link in thread above). I'm not really here to recommend / catalogue kernels though
Any further advice? - It depends on the kernel if it supports other partitions to be formatted as f2fs. For example, some may not allow /system to be formatted as f2fs - but this is not much use anyway, o please stick to just /data and /sdcard
Do I need to keep swapping between F2FS Philz and Standard Philz? - No, it is all one kernel. No need to flash different ones.
How do I use this? - See below
Here are the steps:
- Ensure you have an F2FS kernel (put it on your sdcard now) or have the .img ready on your computer
- Take a full Nandroid backup
- backup your ENTIRE /sdcard to PC (adb pull is as good as the rest - and also a good test that you know what you're doing)
- Flash the updated recovery
- Go to "mounts and storage"
- Press "toggle f2fs ext4 migration"
- Press "format /data and /data/media (/sdcard)"
- Select f2fs and "Yes" - Your /data and /sdcard are now blank
- adb push your clockworkmod folder back to /sdcard (and f2fs kernel if you're using a zip)
- Nandroid restore your /data partition
- Flash your F2FS kernel
- Copy sdcard data back, (using MTP in Android is best) - You may need to boot into Android and reboot the device again before Internal storage shows (Linux only perhaps?)
Notes:
Please note, the migration toggle is disabled again as soon as you leave that menu. The format options will format to whatever each partition is already formatted to whilst the toggle is disabled. So if you previously formatted to f2fs and then reboot recovery and format again, it will continue to format to f2fs until you enable migration and choose the opposite option (ext4).
Also, whilst migration is enabled, you willbe prompted which fs to format to; ext4 formats to ext4, f2fs to f2sf and default to whatever it is already formatted to.
Recommended time settings
Philz Settings > GUI Pref > Time Set up > change date and time
Use the "Time daemon" setting. Set this then boot into rom. Give it a couple of minutes and boot back into recovery.
Please note, qualcomm time daemon always uses UTC (GMT) so you must manually set your time zone in recovery.
Daylight saving is not yet managed by recovery so please alter time zone manually to compensate.
EFS Backup
In custom backup settings, select efs 1 AND efs 2. The N5 splits over both.
Do NOT restore efs on another phone. EFS must be unique on every handset. Restoring efs from another phone will ruin your phone.
md5 verification
If you're moving zips on and off your phone all the time, they can become corrupt during any one of those moves. The new Md5 functionality allows the md5 to be calculated before flashing a zip and shows you on the recovery screen. This means you can read the screen and compare it to a known md5sum for the zip.
There is additionally an md5 verification setting that will only flash the zip if it matches the md5 stored in an md5 file on your memory. I wrote a script to put in the directory with all your zips on your phone that will create an md5 file for you for each zip you have. This way, as you move your zips on and off your memory, you can take the md5 file too and have Philz prevent flashing of those zips if they become corrupt.
Simply unzip the attachment into the directory where you keep all your zips. In terminal emulator, cd to that directory then run the sh file. In this example, all my zips are in /sdcard/AFlash
Code:
cd /sdcard/AFlash
sh md5.sh
Enjoy
Nice one mate.
ZANGETSU786 said:
Nice one mate.
Click to expand...
Click to collapse
It's working well so far. Try it out, let us know how you get on.
Yes!! Was wanting this for my hammerhead. Thanks!!
sent from my HAMMERHEAD neXus
---------- Post added at 10:38 AM ---------- Previous post was at 10:30 AM ----------
Will you be updating this thread with newer versions?
sent from my HAMMERHEAD neXus
CRIME INC. said:
Yes!! Was wanting this for my hammerhead. Thanks!!
sent from my HAMMERHEAD neXus
---------- Post added at 10:38 AM ---------- Previous post was at 10:30 AM ----------
Will you be updating this thread with newer versions?
sent from my HAMMERHEAD neXus
Click to expand...
Click to collapse
I will. Phil will subscribe for support here too. I have made teh thread to his specifications, so do subscribe
Subscribed:thumbup:
sent from my HAMMERHEAD neXus
rootSU said:
It's working well so far. Try it out, let us know how you get on.
Click to expand...
Click to collapse
Everything appears fine.
The time in recovery was at first incorrect for me though. The default for GMT+0 the recovery had was 10 hours behind (or 14 hours ahead) compared to actual time here in UK.
Misc Stuff.
Buttons = Pass
Virtual Buttons = Pass
Brightness setting = Pass
Vibrator Toggle = Pass
Sent from my Nexus 5 using Tapatalk
Good Job! Waited for it! will try after reviews
sewer56lol said:
Everything appears fine.
The time in recovery was at first incorrect for me though. The default for GMT+0 the recovery had was 10 hours behind (or 14 hours ahead) compared to actual time here in UK.
Misc Stuff.
Buttons = Pass
Virtual Buttons = Pass
Brightness setting = Pass
Vibrator Toggle = Pass
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep my time is also an hour or two out..
Thanks sir...
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
icecore said:
Good Job! Waited for it! will try after reviews
Click to expand...
Click to collapse
Well its based on Phil's source, official cwm / cm 11 source using official device tree. Not much to go wrong.
If you've never used Philz recovery, try it. Lack of Philz was my only disappointment moving from s3 to n5...
Now that's resolved
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Wouldn't be surprised if this gets closed down as you're not the developer. I had my 'official' CM 11 thread removed as I wasn't a CM team member last night even thought I used CM's Nexus 4 thread and just updated it...
Thank you rootSU for opening the thread
Time is a Qualcom issue. I will look once to see how to fix it properly along all new qualcomm devices that are affected on ALL recoveries
rootSU said:
Well its based on Phil's source, official cwm / cm 11 source using official device tree. Not much to go wrong.
If you've never used Philz recovery, try it. Lack of Philz was my only disappointment moving from s3 to n5...
Now that's resolved
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
used Philz at SGS2, didn't liked it. was a little buggy with CM.
but i'm believe in improvement by time good luck! and ill try it soon (by now i mean : )
EddyOS said:
Wouldn't be surprised if this gets closed down as you're not the developer. I had my 'official' CM 11 thread removed as I wasn't a CM team member last night even thought I used CM's Nexus 4 thread and just updated it...
Click to expand...
Click to collapse
I'll report it to try and ensure that doesn't happen. The development work is original and opened (and maintained) on the behest of Phil...
Edit > well someones already reported it, but I've re-reported as stated.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Philz's supporter here since SGS2, even donated him too. good to see his work here. and thank you too, rootSU :good:
Just used this to make a backup to my flash drive...nice!
Sent from my Nexus 5 using Tapatalk
btbamzao said:
Just used this to make a backup to my flash drive...nice!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yep. I backed up and restored (and wiped) as a test before posting. Works well. Only the time issue which is non-philz specific right now.
Also obviously it's located in the correct location of /data/media/0 unlike official cwm
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I'll report it to try and ensure that doesn't happen. The development work is original and opened (and maintained) on the behest of Phil...
Edit > well someones already reported it, but I've re-reported as stated.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
Let me know if it gets moved
Many threads were opened by advanced users like you that do provide a great support and help in debugging and releasing things
Without users like you, such projects cannot mature this way. You did a lot when this was first ported to Galaxy S3
I also allowed you to do this to be able to give second line support for advanced tech issues. Most dev threads are cluttered with general/faq questions making support a real full time job
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.
Android Kitkat 4.4.4
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
- After Recovery time to time incorrect capacity of battery
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/PhY11Rvnmq99T
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/xWwb8r3RmpZxK
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
wait before on screen you will see "Partitions had been prepared"
if you have external SD card:
- Back -> Back -> Back -> Mount -> Mount USB storage
On PC you will see SD card mounted, and copy ROM there -> Unmount -> Back
- Install -> choose zip with ROM(mount point /external_sd) -> Swipe to Confirm Flash -> Reboot System
if you have no external SD card
- Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
- Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
- Copy Zip with ROM Internal Storage -> Disable MTP -> Back
- Install -> choose zip with rom -> Swipe to install -> wait for flashing -> Reboot system
Enjoy OMNI!
You can remove installation .zip from Android level by connecting through USB in MTP mode.
TWRP Recovery mode is available using VolUp + End keys
Every next update you can just flash .zip through CWM.
UPDATE from OMNI older that 09.09.2014
- Make backup in TWRP(Backup -> Select Data -> Swipe to backup)
- Flash FOTA and "start" kernel via Multiloader
- Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
- wait before on screen you will see "Partitions had been prepared" -> Back -> Back -> Back
- Mount -> Mount USB storage
- Copy zip with Rom from PC to External SD card -> Unmount -> Back
- Install -> choose zip with ROM -> Swipe to Confirm Flash -> Home
- Restore backup in TWRP (Restore -> Select packge for restore -> Swipe to restore)
- Reboot -> System
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Just reflash bada via Multiloader
CHANGELOG:
26.01.2016 https://yadi.sk/d/lY5ZEJc6noBVH
- Big kernel update from https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/tree/android-5.1
Big thanks to @Coldwindofnowhere
It enable many additional settings in Settings-Performance
Also enabled boost for incall volume in Advanced Settings
- Added Battery saver mode from Omni Gerrit, Experimental- not really tested
- GPS fixes, still we have no A-GPS
11.01.2016 https://yadi.sk/d/pTSrLBykmpVVz
- Omni sources 11.01.2016
- Sensors update and cleanup
- Added Bigmem support in Advanced settings
with default settings we have 270 mb RAM with working 720p video recording
with Bigmem we have 283 mb RAM without working 720p video recording(as was by default in previous versions)
with Max RAM we have 315 mb RAM and camera, video playback and torch is not working at all
- Updated kernel with last omni changes
RIL update 20.12.2014 https://yadi.sk/d/kvYUiq6QdWSdD
- SMS fixes
just flash it via TWRP
11.12.2014 https://yadi.sk/d/80q05wvrdKW3t
- Omni sources 11.12.2014
- Added roaming indication
- Re-worked SMS
- Updated some Zram parameters
maybe something else
25.10.2014 https://yadi.sk/d/qCh-swftcJ7tg
- Omni sources 25.10.2014
- Moved to omni aries kernel
- Updated audio driver
- Updated charger driver
09.09.2014 https://yadi.sk/d/H5lEBmQvbLiSH
- Omni sources 09.09.2014
- New partition layout and new installation procedure(Read carefully! Device will be wiped).
Now you can use android without SD card
- Compass fixed
- Added phone reboot in case of modem crash.
15.08.2014 https://yadi.sk/d/jKCEMrAEZkZGr
- Omni sources 15.08.2014
- Hopefully fixed LCD wake-up bug on wave2, thanks to Blue59 for so many tests
- Corrected voltage for some on-board chips
13.07.2014 https://yadi.sk/d/DoaSRX3EWY9Hk
- Omni sources 13.07.2014
- Fixed updater script
- Fixed power off, thanks to Tigrouzen
11.07.2014
Updated FOTA links
Changed background from white to black
Added start of Bada - Call+End, we can use offline bada charger, in case if battery is fully empty
Added checking kernel size on SD card, sometimes boot.img exist but it is 0mb
04.07.2014 https://yadi.sk/d/Rw2UmkaoVxwdP - forgot to fix updater script, so please re-copy boot.img manually to SD card
- Omni sources 04.07.2014
- Small kernel optimizations
- Bring back Advanced Settings (TVout, vibration intensity and etc )
- Updated framework overlay
- Added OmniTorch
- Added USD OTG support (not tested), based on http://forum.xda-developers.com/showpost.php?p=53803247&postcount=8 Thanks to Tigrouzen
29.06.2014 https://yadi.sk/d/M0XEIgJMVTtCi
- Initial Release
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen, Benzox and many others.
OMNI team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
Reserved
great work and really great rom thanks @volk204
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
nima.yavari said:
i want install rom but no mount sd card on recovery wave 2
full flash bada but again no mount sd card
Click to expand...
Click to collapse
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
volk204 said:
Mount point for SD card is /external_sd
Today Blue59 installed it successfully on Wave2
Also try to catch recovery.log via ADB http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
Click to expand...
Click to collapse
change format sd card fat to fat32 correct
thanks blue59 and volk
Quick Review
USB OTG for badadroid kernel KitKat rom :
https://github.com/Tigrouzen/android_kernel_samsung_wave
This example based on ICZen(ICS) KitKat's very different :
vold.fstab :
Code:
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/s3c_otghcd/usb
init.wave.rc :
Code:
mkdir /mnt/usbdisk 0000 system system
symlink /mnt/usbdisk /usbdisk
storage_list.xml (device/samsung/wave/overlay/frameworks/base/core/res/res/xml/) :
Code:
<storage android:mountPoint="/mnt/usbdisk"
android:storageDescription="@string/storage_usb"
android:primary="false"
android:removable="true"
android:allowMassStorage="true" />
Where is the link for FOTA ??
@Tigrouzen
Can i use Zendrokat FOTA and BOOT?
FOTA SD
couldn't find link for FOTA SD on other forums. can anyone supply?
Ok, it works with Zendrokat fota. But me and my friend (he flash your fota) cant install ROM. Because we have error next to formating. Updating partition details and Failed. How to repair it? ;/
thanks man ...
Hey "wavers" how 'bout the performance ?
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
msprakashmmc said:
I am able to install zendrokat v2.2 but this one is so hard.. Always some error please guys a clear demo or a video on flashing will be very helpful. I really love to try this rom as its very slim.Thanks. B.R:good:
Click to expand...
Click to collapse
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
BenzoX said:
As explained in OP,
-Flash bada 2.0
-Flash BF and Fota (SD fota)
-Put all files on SDcard
-Boot recovery, choose flash zip, go to /external-sd and choose the zip.
-this part is important : "- Wipe -> Advanced wipe -> Check "data" -> Repair or change File Sytem -> Change File System -> Ext4 -> Swipe to change ->Back -> Back ->Back -> Back "
-reboot, enjoy.
if you do this carefully step by step, it will work
Click to expand...
Click to collapse
where's the FOTA SD
Help help help
I have copied kernel and zip
Run recovery
Wipe all complete no error
Try to install zip
Updating partition details
Failed.
What i make wrong?
//
@BenzoX
Thank you. you are the best. Big thanks Bro for help!
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
If i try to go to download moad then it goes but again restarts.
Click to expand...
Click to collapse
If DL Mode not stable... then 2 reasons possible.
With luck only Battery empty.
So charge battery external... or use other battery...
If no luck...
Then Bootloader could be damaged or something else bad...
Best Regards
nileshlog said:
my phone has gone in to boot loop. It starts with samsung 8500 then switches off then again starts and switches off and so on. If i try to go to download moad then it goes but again restarts. I cannot hold on a screen so cant even reflash bada...
Click to expand...
Click to collapse
Battery probably empty, either boot any recovery and let it charge for a while, or plug phone and let charge on bada charge mode, or do it with some wires and a 5v power supply...
Then you should be able to go on DL mode.