Related
[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Galaxy Note (ATT)!
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
quincyatt Device Config: https://github.com/TeamWin/android_device_samsung_quincyatt
Kernel: https://github.com/bigbiff/i717-GB-Kernel
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Changelog
3.0.2-0
- Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
- Add Greek translation to some builds.
3.0.1-0
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Head over to the devices page to find install instructions and download links.
2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
2.8.6.0
- Allow mulitple overlays for popup boxes (Dees_Troy)
- Add pattern style password entry for decrypt (Tassadar)
- Keyboard improvements (_that)
- Update AOSP base to 5.1 (Dees_Troy)
- Reduce theme count to 5 and rely on scaling (Dees_Troy)
- Various scaling improvements (Dees_Troy)
- Improved handling of resources in the GUI (_that)
- Make scroll bar size proportional to list size (_that)
- Allow scoll lists to render without a header (_that)
- Make console scroll per pixel with kinetic scrolling (_that)
- Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
- Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
2.8.5.0
- Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
- Improve thread handling and move input handling into the main rendering thread to improve stability
- Make MTP work even if unplugged and plugged back in
- Unify scrollable list code and make kinetic scrolling feel more natural
- Fix handling of mapped zip files for OTA updates (CM12 updater)
- USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
- Add Cancel Backup capability
- Other small fixes and improvements
2.8.4.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
2.8.3.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
- Other minor fixes and improvements
2.8.1.0
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.0
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
2.7.1.0
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
2.6.3.0
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
2.6.1.0
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
2.6.0.1
Fix showing data twice in advanced wipe
2.6.0.0
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
2.5.0.0
Fixed Device Configs for booting TWRP
Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
Fixed a problem with directory permissions on split archive backups
Fixed a problem with md5 verification of backups
Added a search function to libtar (thanks to kokotas)
Improve handling of XML errors (fix permissions)
Fixed handling of subpartitions
Improvements to recovery.fstab flags
Fixed a problem with decryption not being able to locate the decryption key in some situations
2.4.4.0
Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
More fixes for the file selector
Switched from using busybox md5sum to a direct C function call
Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
Update exFAT to latest commits
Added a build flag to disable using the ioctl for screen blanking
2.4.3.0
Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
Added a scroll bar to file selectors and listboxes courtesy of Tassadar
Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
Added a screen dim effect 2 seconds before screen off on some devices
Finally fixed file selector crash (one of the joys of working with multi-threaded software)
Fixed loading of screen timeout setting during startup
Improvements and bugfixes to screen timeout code
Fix Military Time setting persisting
2.4.2.1
Fix screen timeout by adding correct brightness config file to BoardConfig.mk
2.4.2.0
Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
Add a brightness setting (requires device specific setup and only some devices have been added)
Add a root checker and offer to install SuperSU if the device isn't already rooted
Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
Check and offer to fix root permissions if broken
Add an option for a 24 hour clock display instead of AM/PM (aka military time)
Move stock recovery reflash check to occur during the reboot cycle
Add support for some MTK6xxx devices
Change libtar to vfork to help prevent memory problems
Add a "clicked" effect to most buttons, file selector, and listbox
Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
Other minor bugfixes and improvements
2.3.3.0
Added better handling of wiping on /data/media devices with Android 4.2 to help prevent multiple upgrades of the file system for multiple users
NOTE: It is not recommended to jump back and forth between 4.1 and 4.2 ROMs. If you do, this may trigger additional upgrades and you will have to manually move your files back to the "single user" layout when going back to 4.1.
Fixed renaming of backups when a space is present
Added decrypt button to mount page if you cancel decryption during boot
Added ignore blkid flag support
Fixed handling of MTD partitions during mount
Fixed some keyboard mapping issues on 800x1280 layout
2.3.2.3
Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see http://teamw.in/androidmultiuser)
Fixed a bug with deleting a backup with a space in the name
Added highlights on keyboard key presses
Updates to Fix Permissions
10/18/12
Fixed keyboard segfault
Handle single LUN file for USB Storage
Handle mounting of slow sdcards
Update USB Mount Code to be more Efficient
10/13/2012
Many, many updates. See https://github.com/TeamWin/Team-Win-Recovery-Project/commits/jb-wip/ for detailed commits.
8/25/2012
Device ID Sanitization - doesn't affect the note
1920x1200 theme - not for note
320x480 theme - not for note
/data/media issues for other devices fixed - not for note
Fix keyboard issues for 800x1280 and small ui tweaks
Fix some mount error messages
SD-EXT Improvements
Unmount before formatting (if mounted)
Fix Umask for JB builds (this version is still built in CM9/ICS)
Change initial logging fo TWRP startup (include version field)
Kinetic Scrolling improvements
7/17/2012
Fixed backup duplicate name checking
Added checking to see if boot is 0 size and remove from backup menu
Fixed a bug with android secure backup using ORS
Fixed a bug with backup naming when using ORS and backup name is
Slight tweaks to 800x1280 layout
7/12/2012
New release 2.2. See OP for details on changelog. Please leave any feedback in the thread.
6/14/2012
Added the ability to backup /efs when backing up and restoring. It will tar the files instead of using dd so the filesystem isn't formatted.
6/11/2012
Fixed dual mount for USB. You will now see your internal and external sdcards as Windows drives in recovery!
Fixed md5 checking parsing filenames with apostrophes.
Added reboot to download mode in Reboot page
New support for updater-binary included in TWRP. (Don't currently implement this for the SGH-I717
If no OS installed, reboot buttons won't show. Fixes bricking in some devices but doesn't seem to affect SGH-I717.
Added support for partitions greater than 2 GBs.
5/23/2012
Updated ui.xml to make bigger console space
Worked with Dees_Troy to get flash zip in place working. Are ROMs were getting to big and were being copied to /tmp. With the ROMs and RADIOs we overwhelmed recovery. Now your ROM should flash with no issues because we are extracting from storage now.
Dees_Troy fixed a graphics bug which the recovery was still doing work but the GUI said successful.
Update is at teamw.in or goo manager.
5/11/2012
Fixed ui.xml to fix Mount Page for external and internal sdcards
Updated filename on TWRP device page to have proper version in filename
Updated img for GooManager to have proper version in filename
FAQ
Q. How do I see/use/change between internal and external SDCARD?
A. Please use the Mount page to change between using internal and external. Click Using internal sdcard will allow you to use your internal sdcard to install ROMs. Click Using external sdcard will allow you to use your external sdcard to install ROMs. Please dont use the file browser to find the mounts as this is done for you automatically when you change options and navigate back to the Install page.
To be clear this works as follows:
1. internal emmc sdcard mounted on /emmc
2. external sdcard mounted on /sdcard
3. You can choose what storage you want to use on most screens by selecting "Use external SD" or "Use internal storage"
4. Otherwise you can browse to the appropriate directories
Q. Are TWRP backups compatible with CWM and vice versa?
A. You cannot flash a CWM backup in TWRP and vice versa. Please flash appropriate recovery to restore your backup. You can restore the backup, flash back to your wanted recovery, then make a backup in that recovery for later use.
Q. Can I have TWRP and CWM installed at the same time?
A. There is only one recovery partition that can hold a specific version of recovery. CWM, TWRP2, and Samsung 3e are able to be flashed to recovery, but none can coexist.
Q. Does USB mounting work in recovery?
A. Sorry haven't updated this. It works with internal and external sdcard.
Q. Where is the "Delete battery stats opton?"
A. We removed this option in 2.1. Please see https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT as reference.
Q. Installing Roms
A.All ROMs should be able to be installed.
Please post in this thread if you have any issues flashing.
Q. How does MD5 checking work?
A.To create a md5 for a rom perform the following steps:
1. Open a terminal emulator or use adb and cd to the directory your file is located.
2. Execute busybox md5sum rom.zip > rom.zip.md5 where rom.zip is the file you want to create a md5 for. Make sure that the md5 file has the same prefix as your original file with md5 appended with a period.
3. Check force checking of md5 in Settings in TWRP or after the Install file selector page to check the md5.
Q. I can't name my backups.
A. Make sure to hit enter on the keyboard and not the back button to accept the name.
Q. What's next?
A. Fixing bugs.
flashing now!
flashed
Works well, only issue does not mount to pc in recovery, not sure if that is recovery issue or "leaked" ICS issue.
Works Great!!!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
bigbiff said:
Default [RECOVERY] [5/9/12] TWRP 2.1.2 - TeamWin Recovery Project
TeamWin is proud to present TWRP 2.1.2 for the Galaxy ATT Note!
Special credits:
Dees_Troy for a lot of porting help.
braway for helping me to get recovery image to init.
BLOWNCO for helping test
agrabren for writing the initial TWRP GUI code.
AssassinsLament and Dees_Troy for initial TWRP code
Shift and racks for graphics help on default theme
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.1, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
What's new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.1.0 now features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
In the future we will be working hard to make TWRP easier for other developers to compile. We eventually plan to get a gerrit instance running to let anyone submit patches to the project. We may be looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
Zip files that install more data than free space is available will crash or hang recovery (AOSP issue)
No reboot to recovery
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Just choose the device in the dropdown.
http://teamw.in/project/twrp2
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Click to expand...
Click to collapse
heard great things about this recovery
Sent from my SAMSUNG-SGH-I717 using xda premium
external sd not working?
how to install from external sd and backup to external sd?
assaace said:
external sd not working?
how to install from external sd and backup to external sd?
Click to expand...
Click to collapse
You can change that option in the mount page to use external sd on the install page. This recovery can also be installed by goomanager from the market.
do we have to remove cwm to install this?
does it become your default recovery when you install it?
thanks
wase4711 said:
do we have to remove cwm to install this?
does it become your default recovery when you install it?
thanks
Click to expand...
Click to collapse
Yes you cannot have more than one recovery installed. You can always reflash cwm if you need to with TWRP.
so, what is the recommended procedure to uninstall CWM, and install TWRP?
when you flash twrp, does it ask you if you want to uninstall CWM?
thanks
Looking good man. Installed from goo.im with no issues. Except even after mounting sd/ext, the external is blank?
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope this is a sign of other things to come
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Actually I discovered when selecting internal vs external, they are reversed
Sent from my SAMSUNG-SGH-I717 using xda premium
Backup rom with cmw it takes more than 5minutes.
When i use this twrp2 it only takes few seconds, is it normal?
Sent from my SAMSUNG-SGH-I717 using xda premium
wase4711 said:
so, what is the recommended procedure to uninstall CWM, and install TWRP?
when you flash twrp, does it ask you if you want to uninstall CWM?
thanks
Click to expand...
Click to collapse
Flashing the zip through CWM overwrites the recovery partition with TWRP2. It's like installing a ROM that overwrites /system.
dsmitty166 said:
Looking good man. Installed from goo.im with no issues. Except even after mounting sd/ext, the external is blank?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
bigbiff said:
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
Click to expand...
Click to collapse
Yeah man, just looked again
select use internal...and only see external
select use external...and only see internal
Sent from my SAMSUNG-SGH-I717 using xda premium
bigbiff said:
Try going in and out of the Install page. I noticed a refresh bug sometimes happens after changing from internal sd to external sd and vice versa.
EDIT:
Just read your next post. You are saying that the internal and external cards are reversed? Can you verify this for me? I didn't have this issue.
Click to expand...
Click to collapse
assaace said:
Backup rom with cmw it takes more than 5minutes.
When i use this twrp2 it only takes few seconds, is it normal?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
There is a GUI bug that sometimes shows successful but the console will still show that its running. We are looking into this issue. Make sure to pay attention to the console if this bug happens and please send me a copy of /tmp/recovery.log. You can used the Advanced Page to copy the logfile to sdcard.
Source: http://forum.xda-developers.com/showthread.php?t=1620255
This is a script to create a backup of our rom "online", without access to recovery.
ameer1234567890 said:
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. For me, this has been a killer as I do regular nandroid backups. Having to reboot in recovery and finding missed calls, sms from my wife and friends is totally not accepatable for me. So, I set to develop an online nandroid backup tool, namely Online Nandroid, which can do nandroid backups without switching off my phone.
Today, I am releasing it to public, as it may serve good for some others too. Originally I developed Online Nandroid specifically for Xperia devices, but now I am releasing it for all android devices.
This tool, eventhough called "Online Nandroid", does not upload/save backups to any online/cloud services. Online here means that it does backup while phone is live or still running Android.
The short name onandroid is meant to be pronouced as o-nandroid or o'nandroid and NOT on-android.
{
"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"
}
Online Nandroid backups the below partitions to /sdcard/clockworkmod/backup directory.
mmcblk0_start (for Acer devices)
boot
recovery
wimax (for Samsung devices)
appslog (for HTC and Sony (Ericsson) devices)
system
data
cache
datadata (for Samsung devices)
efs (for Samsung devices)
.cust_backup (for Huawei devices)
flexrom (for Acer devices)
(cp)uid (for Acer devices)
.android_secure
sd-ext
The date format used for folder name is the same used by CWM itself and nandroid backups created with Online Nandroid can safely be restored using CWM.
Feedback (especially ideas to improve) are most welcome.
Requirements:
1. Rooted android phone
2. A terminal emulator installed on phone
3. Latest version of Busybox
4. A working CWM based recovery installed
5. Some patience
Installation:
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash
4. Reboot
Usage:
1. Open terminal emulator
2. Type su to obtain root
3. Type onandroid
4. Wait and watch
[HIGHLIGHT]If you are getting error mkyaffs2image not found in path, try fix tool in this post.[/HIGHLIGHT]
.
[HIGHLIGHT]If you are getting error dedupe not found in path, try dedupe tool in this post.[/HIGHLIGHT]
.
[HIGHLIGHT]If Online Nandroid is failing to find boot and recovery partitions, flash the zip file for your device from here. If your device is not on the list, post a comment there or post a reply in this thread with your device model.[/HIGHLIGHT]
The behaviour of Online Nandroid can be adjusted by using command line flags, some of which are described in detail below. Each command line flag has its longer counter-part and both forms can be mixed. For a complete list of command line flags and short descriptions, you can type:
Code:
onandroid -h
OR
onandroid --help
Custom Backup Name:
* Example:
Code:
onandroid -c NAME
OR
onandroid --custom NAME
* Please be careful not to include characters not allowed in filenames.
Timezone modifier:
* Example: Use phone timezone for backup file name
Code:
onandroid -p
OR
onandroid --phone
* Example: Use UTC (default) for backup file name
Code:
onandroid -u
OR
onandroid --utc
* Note: UTC is used as default (if no timezone modifier is passed). This is to comply with CWM nandroid backups.
Backup Modes:
* Good old backup mode (default).
* Example:
Code:
onandroid -o
OR
onandroid --old
* Note: This is the most commonly known, default backup format.
* Split backup mode (CWM6+ only).
* Example:
Code:
onandroid -l
OR
onandroid --split
* Note: This is specifically useful if you have partitions which are over 2GB in size. Use this only if you have CWM 6+.
* CWM6 style incremental / dedupe backup mode.
* Example:
Code:
onandroid -i
OR
onandroid --incremental
* Garbage collect. For incremental backups (used for cleanup after deleting incremental backups).
* Example:
Code:
onandroid -gc
OR
onandroid --garbagecollect
* Advanced / Selective backup mode. For backing up only specific partitions.
* Example:
Code:
onandroid -a PARTITIONS
OR
onandroid --advanced PARTITIONS
* Partition letters / names can be found by typing onandroid -ah
Replace Older Backups (with same name) - used with custom backup names:
* While using custom backup names, Online Nandroid will not allow an already existing backup name to be specified, by default. Trying this will return an error and halt backup. If you want to replace the older backup with a new backup, by using the same custom backup name, you can specify the below command line flag.
* Example:
Code:
onandroid -c MyBackup -r
OR
onandroid --custom MyBackup --replace
* Note: This will only work with custom backup names and is not a true replace per se. Online Nandroid will first delete the old backup folder and create a new folder. Thus, if backup halts in the middle of it, for whatever reason, the backup may not be usable at all. So be careful about this flag.
Change Log:
Code:
v1.0 - Initial release.
v1.1 - Bug Fix: incorrect implementation of help command.
v1.2 - Bug Fix: changed script permissions from 777 to 755
Improvement: changed elapsed display of seconds only to minutes & seconds.
v1.3 - Bug Fix: error if /sbin/sh is not present.
v2.0 - Fixed: various bugs and re-organized script.
Added: timezone modifier.
Improved: usage instructions screen.
Added: su detection.
v2.1 - Bug Fix: .android_secure partition not being backed-up correctly.
v2.2 - Bug Fix: size calculation of .android_secure partition.
v2.3 - Improvement: size calculation in .android_secure partition.
v3.0 - Bug Fix: unknown uid 0 (incorrect detection of root).
Added: sd-ext backup.
Added: battery level check.
Added: SD card check.
Improved: .android_secure backup.
Fixed: various bugs and re-organized script.
v3.1 - Bug Fix: SD card not found error on some devices.
Re-organization of script and removal of bloat code.
v3.2 - Bug Fix: Incorrect detection of root.
Added: New logging mechanism.
v3.3 - Bug Fix: Incorrect sdcard mounting.
Bug Fix: Various fixes for busybox conflicts.
Improvement: Logging mechanism.
v3.4 - Bug Fix: Empty md5sum.
Bug Fix: Size calculation of sdcard.
Bug Fix: Script exiting before sd-ext and .android_secure partitions backed-up.
v3.5 - Bug Fix: Busyboxed 'which' command.
Removed some log lines for cleaning-up.
v3.6 - Removed: mount format detection bloat due to non-busyboxed version.
v3.7 - Busyboxed "cat" commands.
Added: Battery level detection for Xperia X10.
Re-positioned root detection.
v4.0 - Added: LED and vibrate notification on backup completion.
Bug Fix: Minor bug in "tar" detection.
Bug Fix: Cannot create log file.
v4.1 - Bug Fix: Corrected size checking of .android_secure partition.
v4.2 - Added: md5sum verification.
Improved: md5sum generation.
v5.0 - Added: Backup of boot, recovery, wimax and appslog partitions.
Added: Proper sdcard detection.
Added: Detailed error logging.
Added: Cleaning-up temp mounts upon exits.
Added: LED notification for Xperia U.
Added: Version number to log.
Added: ext2/3/4 and rfs file system support.
Added: Avoid mkyaffs2image detection if device does not have a yaffs2 partition.
Added: Force remounting and unmounting.
Added: system, data, cache, datadata and .android_secure partition detection.
Improved: sd-ext detection.
Improved: sd-ext backup.
Improved: md5sum generation and validation.
Improved: sd-ext detection.
Improved: Usage instructions screen.
Improved: Battery level detection.
Improved: LED and vibrate notification.
Increased safety space from 7MB to 10MB.
Code clean-up and re-organization.
v5.1 - Bug Fix: Minor bug in sd card detection when device has internal storage and an external sd card mounted.
Bug Fix: Bug in .android_secure backup.
v5.2 - Bug Fix: SD Card detection in Jellybean devices.
Bug Fix: boot partition detection in devices with sboot partition.
Added: /efs partition backup (for Samsung devices).
Increased: Safety size from 10 to 12.
v5.3 - Added: Partition detection via part_detect_tool.
Bug Fix: boot, recovery, wimax and appslog partition backup for non-mtd devices.
Bug Fix: boot, recovery, wimax and appslog partition detection (Exact partition names).
Improvement: Busyboxed some cut and grep commands.
Removed: Some unwanted code in partition detection.
v5.4 - Bug Fix: Error logging of partition layout.
Bug Fix: sd-ext detection bug.
Improvement: Logging of required space.
v5.5 - Bug Fix: SD Card detection.
Bug Fix: sd-ext detection.
Bug Fix: sd-ext backup method.
Bug Fix: boot, recovery, wimax and appslog partition size calculation.
Bug Fix: socket ignored error by tar.
Bug Fix: /data/media included in /data partition backup.
Bug Fix: sd-ext included in /data partition backup for app2sd, link2sd, etc... setups.
Bug Fix: Eliminate /data/media while calculating used size of /data partition.
v5.6 - Bug Fix: basename error on some devices.
Bug Fix: md5sum spitting an error if .android_secure not backed-up.
Bug Fix: Fixed regression bug in sd card and sd-ext detection.
v5.7 - Bug Fix: partition detection.
Bug Fix: sd card space calculation on some devices.
Improvement: some busyboxing.
v5.75 - Bug Fix: partition detection. (bug introduced in v5.7)
v5.8 - Bug Fix: partition detection.
v5.9 - Added: /.cust_backup partition backup (for Huawei devices).
Bug Fix: Partition detection.
Bug Fix: Include sd-ext folder in data partition while skipping it's contents.
v6.00 - Added: CWM 6 style incremental backups.
Added: Garbage cleaning for incremental backups.
Added: Advanced backup / Selective backup.
Added: Long arguments for timezone.
Added: Setting alternate storage media via command line flag.
Added: Setting sd-ext path via command line flag.
Added: Battery level checking for HTC One X.
Added: Split backup mode (CWM 6+ only).
Added: Backup mode detection via .default_backup_format file (used by CWM).
Added: Advanced backup mode detection via .advanced_backup_partitions file.
Added: /flexrom and mmcblk0_start partitions backup (for Acer devices).
Added: Revamped and more useful progress indicators.
Added: Na Rnfgre Rtt.
Added: Replacing named backups with command line flag.
Added: Disabling notifications with command line flag.
Added: Setting progress indicator type with command line flags.
Added: Trapping exit/kill signals and cleaning up before exiting.
Added: Prompt whether to replace if backup name exists.
Added: BusyBox version checking.
Removed: Partition skip messages for device specific partitions.
Removed: Safety pin size adjustment.
Improved: Size calculation of /data partition if /data/media exists.
Improved: Battery level checking.
Improved: Code used for processing arguments.
Improved: .android_secure detection.
Improved: .android_secure size calculation.
Improved: Help screens.
Improved: Detection and backup of /.cust_backup partition.
Improved: Size calculation in all partitions.
Improved: SD Card detection and automatic selection of external SD Card.
Improved: Logging in log file.
Improved: Some more busyboxing.
Changed: Argument for setting timezone. (-p for phone timezone instead of -h)
Changed: Minor version numbers to 2 digits.
Re-organisation of code.
v6.01 - Bug Fix: sdcard detection in some devices using native app2sd.
v6.10 - Bug Fix: Actually fixed the bug mentioned in v6.01 changelog.
Added: HP Touchpad boot partition backup. (Partition letter p)
Bug Fix: mkyaffs2image requirement detection
BugFix: Removed disk dump of boot partition for Acer devices and HP Touchpad.
v6.11 - Bug Fix: Filesystem detection in data partition for incremental backups.
Bug Fix: wrong partition detected as sd-ext in some devices.
v6.12 - Bug Fix: filesystem detection in data partition on some devices.
v6.13 - Bug Fix: .android_secure detection when an alternate storage media is selected.
Bug Fix: Remount error in AROMA terminal.
Bug Fix: Avoid clearing log file while checking the version number only.
v6.14 - Bug Fix: Busyboxed ls command in md5 verification.
Bug Fix: Added some detailed error logging for could not change to path errors.
Bug Fix: Could not change to path errors.
Twitter: @OnlineNandroid
Source: http://bit.ly/OnlineNandroid
Issue Tracker: http://bit.ly/OnlineNandroid-issues
Older Versions: http://bit.ly/OnlineNandroid-downloads
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showthread.php?t=1620255
Thread closed as it's already visible to all members in the General Android forums so doesn't need to be reposted in device forums. I know your intentions were good, it just causes less clutter without duplicating threads.
Thanks
AvRS
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
{
"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"
}
About Theme
Recovery gone App.
This is a heavily modified version of the theme by thecoby.
Simple and intuitive.
Port the theme as much as you like.
You use this theme at your own risk.
Compatibility
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
Theme will work on any device with a resolution of 1080x1920.
MultiROM theme requires MultiROM recovery.
How to use:
Download the theme of your choice and rename it to "ui.zip".
On internal SD card, open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Download:
Dropbox Folder
Changelog:
10.09.2014
Themes updated for TWRP 2800
Added support for color in console
Added support for backup / restore progress
Sliders for screen / vibration settings now use images (thanks to Tasssadar)
Revised script for color changing mechanism (thanks to Modding.MyMind)
Added "Decrypt Data" button to mount page (was missing since forever...)
Added "enable / disable MTP" buttons to mount page
Added "refreshfilesystem" page
New .dat fonts with latest version of Roboto
Changed font size for rendered labels of main buttons
Fixed some minor quirks
04.07.2014
All themes updated
enabled screenshot support (vol- & power)
fixed file names not changing when queued zips are flashed
reduced font size for text box on "flash image" page for 720/768/800x1280
03.07.2014
All themes updated
Implemented ability to flash .img files directly from the install page (thanks to @osm0sis for the Flashify script and his help polishing this feature)
Reworked color changing mechanism on black/dark/light (thanks to @DSM_ for the idea and the zip binary)
Added 3 more highlight colors to black/dark/light
Restored default file list behaviour, bookmark function is now optional (enable it in Holofied Settings > Misc)
Fixed overlapping text on wipe page (occured on M8 and Skyrocket)
Fixed overlapping actionbar buttons on black/dark/light for some resolutions
Old Changelog:
05.06.2014
All themes updated for compatibility with TWRP 2.7.1.0
added "repair/change file system" pages to wipe section
optimised theme chooser code
14.05.2014
All themes updated
added theme chooser to holofied settings
moved holofied settings into seperate menu (play, xda)
fixed position of progress bar on wipe pages (play)
04.05.2014
All themes updated
Added themed keyboard
Fixed "download" button
Fixed actionbar buttons overlapping on black/dark/light for some resolutions
22.04.2014
All themes updated
Black/Dark minimal released
Added actionbar button for changing font size of file lists
Fixed "refresh sizes" function on backup page
Fixed layout for "partition sd card" page
Fixed typo for "chmod 755" button and added "chmod 644" button
Fixed keyboard layout on 1200_multirom
A lot more fixes and improvements to the xml that I forgot to write down...
30.03.2014
All themes updated
Added bookmark function to filelists on "install" and "add zip to queue" pages - default path is set to \sdcard\Download for both lists (all)
Added "default settings" icon to actionbar on "settings" and "theme settings" pages (all)
Added confirmation dialog for resetting defaults and changing bookmarked folders (all)
Added "refresh storage" icon to actionbar on "backup" page (all)
Added setting to apply highlight color to progress bar (helps with visibility if highlight color is applied to actionbar/actionabr stripe) (all)
Added setting to use old progress bar (below console) (all)
Added setting to use light statusbar (matches overall backgroud color) (play)
Color of action bar labels changes to white when highlight color is applied to actionbar (light)
Color of action bar icons changes to light grey when highlight color is applied to actionbar (black, dark, light)
Fixed some dividers not showing on "advanced" page for certain devices (black, dark, light, xda)
Fixed some dividers not showing on multiple pages (multirom play)
12.03.2014
Black, Dark and Light updated
fixed an issue with text input, where the backspace button would not work when placing the cursor anywhere in the written text but the end
08.03.2014
All themes updated for TWRP 2.7.0.0.:
Added vibration settings page (time zone setting moved to actionbar) - ALL
Added capslock support to keyboard - ALL
Increased spacing for partition lists on "wipe page" and "mount page" - ALL
Changed color of console to match overall background color - ALL
Added option to center clock in statusbar - ALL
Added option for using Aroma File Manager instead of TWRP file manager (big thanks to @nijel8 for the idea) - ALL
HOW TO USE AROMA FM:
Download this flashable zip.
Flash the zip in recovery.
It will copy the flashable Aroma FM package to \TWRP\aromafm.
Go to "settings" and tick the option to use Aroma FM.
Profit.
Complete rework of Holofied Black, Dark and Light:
NOTE: The size of the XMLs for these themes has quadrupled, thus the themes need longer to load when entering the recovery.
Font size of tab labels reduced
Font color of main buttons changed from white to a light grey - BLACK, DARK
Lighter colors for actionbar and background - LIGHT
Added theme settings:
Added option to choose between nine highlight colors
Added options to independently apply chosen highlight color to statusbar, navbar buttons and actionbar
Added option to switch position of back button in navbar
14.12.2013
Added "up" functionality to labels in action bar (works like home button)
Fixed behaviour of mount USB-storage page (for good)
07.12.2013
Added info on "mount usb-storage" page if device not compatble (all)
Removed highlight images for main buttons (all)
Folder / File icons enlarged (all)
Black / Dark KK theme released
24.11.2013
Added "Restart System" button to restore/wipe/backup/*anyotheraction*_done pages
18.11.2013
Black, Dark, Light, Play and XDA now with dynamic battery/clock alignement (will change for 24h or AM/PM clock)
17.11.2013
Black, Dark, Light and Play completely revised (mostly code, some images as well)
all themes now use the select storage list, toggles are removed
XDA released
28.09.2013
added "append date" button to backup page (all)
added "cancel" button to all pages with text input (all)
deleted "fix su" page (all)
removed deprecated settings (all)
changed slider back to holo design, but colo(u)r now matches corresponding page (play)
changed progress bar, colo(u)r now matches corresponding page (play)
fixed "delete backup" page calling "wipe action" page instead of "delete backup action" (play)
minor changes here and there
18.09.2013
fixed a bug which prevented using "blank" for backup naming (all)
fixed "delete backup" not working (all)
14.09.2013
Added cancel button to ADB Sideload page (all)
05.09.2013
Holofied Play released (please give feedback)
04.09.2013
added password promt pages for restoring encrypted backups (all)
21.08.2013
Backup page: renamed option "Save Backup to USB-OTG" to "Save Backup to Micro SD"
15.08.2013
Black, Dark and Light released (please leave feedback)
Available for:
Galaxy Nexus
Nexus 4
Nexus 5
Nexus 7
Nexus 7 2013
Galaxy Note 2
Galaxy Note 3
Galaxy S3
Galaxy S4
One X
One
FAQ
THEME FAQ
What's the difference between the dark and the dark_minimal theme?
The minimal themes only have one highlight color (dark holo blue).
The main advantage of the minimal themes is their reduced boot time compared to the multicolor versions.
They're ment to be used as base for porting or creating other single color versions.
Can I use this theme on my *devicename*?
Most likely yes. The themes can be used on any device with the screen resolution the filename of the theme suggests.
For example, the "1080_*variant*.zip" can be used on any FullHD device.
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app. For instance, ES File Explorer's build-in downloader has proven to be unreliable for the dropbox links I provide.
I like what you did there, but can I has more/other colorz?
Colors are a matter of personal preferrence. I try to keep the themes neutral, and the colors used are (mostly) in accordance with android design guidelines.
For other colors, you'll have to modify the theme yourself. I will gladly provide the source file for the images to everyone interested.
Will you make a dark/black Play theme?
No, because I don't want to maintain more versions of the theme. But everybody is welcome to contribute to the thread...
Will you help me to port my favourite other theme to device XY?
No. But this guide provides insight on how you can do it.
RECOVERY REPACK FAQ
What version of TWRP is the repack?
Always the latest available for a certain device.
As I don't keep track of all TWRP threads, please remind me if there was an update for your device.
I'd like a repack for *devicename*, how do I make one?
Download and unpack Android Image Kitchen.
Unpack the zip.
Download the zip containing the custom curtains (splash images).
Get the recovery image you want to modify from the TWRP download site.
Copy the recovery image to the Image Kitchen folder.
In windows explorer, drag & drop the recovery image on the "unpackimg.bat".
Unpacking will create two new folders (ramdisk and split_image).
Rename the splash of your choice to "curtain.jpg" and drop it into /ramdisk/res/images.
Hit "repackimg.bat".
This will create a "image-new.img", which you can then flash away using your preferred method.
My preferred method for installing the recovery is GooManager, so how do I flash this .img thing?
Use the theme. It now supports direct image flashing from the install page.
Via Fastboot. Most useful to know how to (especially in case things go sideways).
Via app. For a variety of devices, Flashify has proven to be a good app for flashing recovery images. It's under (very) active development and I highly recommend to give it a try.
Alternative apps (can be device specific): SGS4 Flasher, ... (please help me to populate this part)
AROMA FM
The theme has an option to use the Aroma File Manager as the default recovery file manager.
Download this flashable zip.
Flash the zip in recovery.
It will copy the flashable Aroma FM package to \TWRP\aromafm.
Go to "settings" and tick the option to use Aroma FM.
Profit.
REPACKED TWRP RECOVERIES FOR G900F klte
These are repacked with a curtain to match your theme. Thanks to @Al Asmi for providing the repacks.
Download:
Download from his original post and don't forget to thank him...
Screens:
Source:
Inkscape SVG
Un/Repacking the recovery image:
Use this marvelous .img editing tool by @osm0sis.
REPACKED TWRP 2700 RECOVERIES FOR G900F-klte
inspired by the work of @z31s1g and thanking him for the guidelines on how to repack your own recovery with desired curtain, I introduce to you the repacked TWRP recoveries for the Galaxy S5 tested on my own device G900F.
These are repacked recovery img files with a curtain to match your theme. you can simply use Flashify from Google Play to flash those easily.
Available Curtains: Black, Dark, Light, Play and XDA.
Download:
BOX Folder-G900F
Screens:
All themes updated
All themes updated
added theme chooser to holofied settings
moved holofied settings into seperate menu (play, xda)
fixed position of progress bar on wipe pages (play)
How to use the theme chooser:
copy all themes to your device (use internal storage if you have a device with micro sd)
in holofied settings, go to "swap theme" page, browse to the theme.zip and select it
confirm your selection (recovery will now copy the zip to the correct folder, rename it to ui.zip, then reload the theme)
NOTE 1: Reloading the theme will set all theme settings to default. Recovery settings will persist.
NOTE 2: Reloading the theme will sometimes trigger a recovery reboot (appeared randomly on Galaxy S3).
I tried the Play theme and now im stuck in a recovery bootloop. I pulled battery and waited a bit, every time i attempt to power on the phone it wants to boot into recovery and gets stuck in the loop. Is there anything i can do besides Odin back to stock?
fknfocused said:
I tried the Play theme and now im stuck in a recovery bootloop. I pulled battery and waited a bit, every time i attempt to power on the phone it wants to boot into recovery and gets stuck in the loop. Is there anything i can do besides Odin back to stock?
Click to expand...
Click to collapse
First try to ODIN to stock recovery, boot to recovery and wipe cache. It should boot back into system afterwards. I've had this problem on the S3 with the light theme (and only with the light theme), so I'd be interested if you can fix it that way, and if the problem persists after you've redownloaded the theme and tried again (recovery bootloops might also be caused by a faulty download, but then you should still be able to boot into system....)
So plaese let me knoe how it goes...
EDIT:
I was searching for a standalone stock recovery to flash, but can't find any.
As the CF-Autoroot package also contains the stock recovery, you can try to flash this one via odin, or you just take the recovery.img and flash it via fastboot...
z31s1g said:
First try to ODIN to stock recovery, boot to recovery and wipe cache. It should boot back into system afterwards. I've had this problem on the S3 with the light theme (and only with the light theme), so I'd be interested if you can fix it that way, and if the problem persists after you've redownloaded the theme and tried again (recovery bootloops might also be caused by a faulty download, but then you should still be able to boot into system....)
So plaese let me knoe how it goes...
EDIT:
I was searching for a standalone stock recovery to flash, but can't find any.
As the CF-Autoroot package also contains the stock recovery, you can try to flash this one via odin, or you just take the recovery.img and flash it via fastboot...
Click to expand...
Click to collapse
I Odin'd recovery and booted system back up. Flashed the repacked recovery for the new curtain. Going to attempt theme again. Should I use the 1080 or multirom version?
EDIT: nvm, I got it working. I used the 1080Play.zip and it worked now. Thanks!!! I was getting tired of the old look. Love it!
fknfocused said:
I Odin'd recovery and booted system back up. Flashed the repacked recovery for the new curtain. Going to attempt theme again. Should I use the 1080 or multirom version?
EDIT: nvm, I got it working. I used the 1080Play.zip and it worked now. Thanks!!! I was getting tired of the old look. Love it!
Click to expand...
Click to collapse
Good, glad you brought it back to life again. The MultiRom versions can currently only be used on Nexus 5 and HTC One. It requires a modded recovery which allows you to install multiple roms. It's a nice feature for the restless flasher but not available for the S5 (yet).
How come my TWRP dark doesn't have any blue in it like in the OP?
Joe0113 said:
How come my TWRP dark doesn't have any blue in it like in the OP?
Click to expand...
Click to collapse
Tap on the pen icon in the action bar. Select the highlight color you want. Blue1 is the one from the OP.
All themes updated
All themes updated for compatibility with TWRP 2.7.1.0
added "repair/change file system" pages to wipe section
optimised theme chooser code
Feedback needed
Okay, so here are two new versions to test. If you do, please give feedback.
The only change is the way the color changing is handled. So please change the colors back and forth and report any oddities (or if it's working).
To change the color, the ui.zip will be unpacked, the image set with the selected highlight color will be copied to the folder that is used by the recovery, and a search and replace operation will alter color definitions in the xml file. Then everythig is zipped again and copied to the theme folder.
This means:
The color change will no longer happen "on the fly". The recovery needs to reboot for the change to take effect.
The xml file is no longer 25k lines long, but 10k lines (like current minimal themes). Once you have set up the theme, the time to boot to recovery should decrease significantly (compared with the current multicolor versions).
If this works on all devices, there will be no more need for the minimal themes (good for me).
The shortened xml gives room for new features without pushing boot time above 10 seconds (good for all).
Download:
1080_black
1080_dark
All themes updated
03.07.2014
All themes updated
Implemented ability to flash .img files directly from the install page (thanks to @osm0sis for the Flashify script and his help polishing this feature)
Reworked color changing mechanism on black/dark/light (thanks to @DSM_ for the idea and the zip binary)
Added 3 more highlight colors to black/dark/light
Restored default file list behaviour, bookmark function is now optional (enable it in Holofied Settings > Misc)
Fixed overlapping text on wipe page (occured on M8 and Skyrocket)
Fixed overlapping actionbar buttons on black/dark/light for some resolutions
About image flashing
The feature is tested on Galaxy Nexus, Nexus 5 and Nexus 7 (grouper and flo)
It allows to flash .img files from recovery without the need for a flashable zip
Supported types are "boot", "recovery" and "radio / modem"
The install page now has a toggle to switch between zip files and images (see screenshots)
Simply choose the image, then select the image type and flash away
Also read the "about" text box before flashing :good:
The script works only on devices with standard "by-name" partition naming, thus it will not work on all devices the themes are available for
If your device is among the unsupported ones, the script will bail and wont flash the image - instead it will tell you you need to continue to use zips or apps
All themes updated
04.07.2014
All themes updated
enabled screenshot support (vol- & power)
fixed file names not changing when queued zips are flashed
reduced font size for text box on "flash image" page for 720/768/800x1280
z31s1g said:
THEME FAQ
...
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app. For instance, ES File Explorer's build-in downloader has proven to be unreliable for the dropbox links I provide.
Click to expand...
Click to collapse
Ok, makes sense, I used ES before reading this part. But now my S5 won't boot to anything other than recovery, and it "bootloops". I've taken the battery out twice, and it's still booting into recovery automatically. Probably because I told TWRP to reboot to recovery after I renamed the file to ui.zip, so it's saved in /cache to "boot recovery" and won't be cleared until something boots to clear it...
I've tried booting into the bootloader (which works), but apparently the bootloader doesn't clear the "boot recovery" flag, so I end up right back in the "bootloop" after another reboot.
Ideas?
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
z31s1g said:
First try to ODIN to stock recovery, boot to recovery and wipe cache. It should boot back into system afterwards. I've had this problem on the S3 with the light theme (and only with the light theme), so I'd be interested if you can fix it that way, and if the problem persists after you've redownloaded the theme and tried again (recovery bootloops might also be caused by a faulty download, but then you should still be able to boot into system....)
So plaese let me knoe how it goes...
EDIT:
I was searching for a standalone stock recovery to flash, but can't find any.
As the CF-Autoroot package also contains the stock recovery, you can try to flash this one via odin, or you just take the recovery.img and flash it via fastboot...
Click to expand...
Click to collapse
.... I should read before I post. lol
Also, a simple "adb reboot" worked too. Apparently it's just the UI that loops, the system underneath is running fine.
All themes updated
10.09.2014
All themes updated for TWRP 2800
Added support for color in console
Added support for backup / restore progress
Sliders for screen / vibration settings now use images (thanks to Tasssadar)
Revised script for color changing mechanism (thanks to Modding.MyMind)
Added "Decrypt Data" button to mount page (was missing since forever...)
Added "enable / disable MTP" buttons to mount page
Added "refreshfilesystem" page
New .dat fonts with latest version of Roboto
Changed font size for rendered labels of main buttons
Fixed some minor quirks
Updated REPACKED TWRP 28.0.1 RECOVERIES FOR G900F-klte
Inspired by the work of @z31s1g and thanking him for the guidelines on how to repack your own recovery with desired curtain, I introduce to you the repacked TWRP recoveries for the Galaxy S5 tested on my own device G900F.
These are repacked recovery img files with a curtain to match your theme. you can simply use Odin or Flashify from Google Play to flash those easily.
Available Curtains: Black, Dark, Light, Play and XDA.
Download:
REPACKED TWRP 2.8.0.1 RECOVERIES FOR G900F-klte
Screens:
@z31s1g please update
Al Asmi said:
...
Click to expand...
Click to collapse
Thanks for providing these again. [emoji106]
Link updated.
z31s1g said:
Thanks for providing these again. [emoji106]
Link updated.
Click to expand...
Click to collapse
You are all welcome.
Real Thanks to you @z31s1g for providing the most awesome TWRP themes.
Note: This is mainly a copy/paste from philz's thread for this device, I merely added support for the vs985, disabled overlays so aroma looks perfect, and bumped it, enjoy! ^^
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
Download
https://www.androidfilehost.com/?fid=95916177934532230
Note: It is an IMG file, so use flashify
PhilZ Touch Features:
touch interface:
- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate, SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- basic scroll kinetics for faster scrolling on demand
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- pause on logs mode: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 5 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- capture recovery screen shots with a gesture action (only some devices)
- basic theme support
- one file to save all settings
- backup and restore settings file
- backup and restore only GUI settings
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, there is a minimal small delay (0.5 sec) to validate on next touch. This is by design and not a bug. It is there to limit erroneous validation while scrolling
- true JB 4.2 migration: toggle between /data/media and /data/media/0
- Secure recovery lock with passkey
- 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
- exFAT, NTFS and Ext4 support in recovery for external storage through kernel modules for many devices for faster write speed
- 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...
- support .android_secure backup/restore from external storage
- optional reboot after custom backups/restores
- sd-ext support (ext4)
- nandroid backups support /preload in backup and restore jobs (custom and stock modes)
- nandroid backups support /misc in backup and restore jobs (custom mode)
- devs: 5 extra optional partitions supported in nandroid operations by editing recovery.fstab
- 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
- cancel 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 auto-renamed 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 (include modem and efs)
- backup/restore EFS in both tar + img formats, now with time tags for both tar and .img
- 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 backup/restore in stock clockworkmod or TWRP modes
- advanced power options menu
- detailed build info in About menu
Credits
To ALL people who help in porting device sources and give feedback for debugging
A special thank also to the below, and ALL who I do not mention but did contribute a lot with their efforts
Phil3759 for opensourcing this recovery <3
Koush for having created and maintaining cwm
Cyanogenmod for making all this possible
Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
Dees_Troy from TWRP team for pigz source and many great ideas in their recovery + source for backups compatibility
Chenglu for his unpacking tools and porting i9505: Huge credit
kbc-developers for the base semi-touch code and much more
[email protected] for his great job / support
sk8erwitskil for his recovery source, a great place to start learning
shoe63 for his help from the start across many devices
DooMLoRD for his work and help with Sony
[NUT] for his ports to Sony
wanam for compiling sensors-free kernels for N71xx/i317M, i9500 and i9505 to fix boot delay for custom kernels, exfat support and much more
dougiebee for his work on fixing time on many Qualcom devices
ausdim for all the support in developing kernels for i9505
dr.ketan for his precious help in porting to the N7000 & N7100 (I don't own one) and all the support in threads
Chainfire for his support (stock recovery flash) and all his work for the Android community
XDA:DevDB Information
[Recovery][VS985][2/20/15]CWM 6.0.5.1 - PhilZ Touch 6.59.0, Tool/Utility for the Verizon LG G3
Contributors
HolyAngel
Source Code: https://github.com/holyangel/philz_touch_cwm6
Version Information
Status: Stable
Created 2015-02-20
Last Updated 2015-02-20
phil's recovery?
Is this Bumped?
Did you read the red "note"?
PubStar2011 said:
Is this Bumped?
Click to expand...
Click to collapse
Of course its bumped
Haha lol yea just seen that sorry about that and the download link is not working
PubStar2011 said:
Haha lol yea just seen that sorry about that and the download link is not working
Click to expand...
Click to collapse
Fixed! Thanks for letting me know ^^
lmao, I was rolling...I'm like ITS THE FIRST THING ON THE PAGE!! haha
I can't wait to use this though, Love me some Philz Bumped head recovery
HolyAngel said:
Fixed! Thanks for letting me know ^^
Click to expand...
Click to collapse
Everything works great loving it thank you so very much
Ok, so this may be a dumb question, but I gotta ask since it is one of the main reasons I used CM when I do. Anyways, I don't suppose this will work w/ automatically updating CM12 nightlies, correct?
ohlin5 said:
Ok, so this may be a dumb question, but I gotta ask since it is one of the main reasons I used CM when I do. Anyways, I don't suppose this will work w/ automatically updating CM12 nightlies, correct?
Click to expand...
Click to collapse
Yeah its same as twrp in that respect, will use the same scripts to apply updates no problem.
HolyAngel said:
Yeah its same as twrp in that respect, will use the same scripts to apply updates no problem.
Click to expand...
Click to collapse
TWRP no longer works....the past few weeks they changed something in the recovery script causing you to have to do manual dirty flashes.
Ah wasn't aware of that, this one should still work with it. I haven't tested it tho
HolyAngel said:
Ah wasn't aware of that, this one should still work with it. I haven't tested it tho
Click to expand...
Click to collapse
Yeah mega disappointment when I found that out haha....aight sounds good. Thanks!
Will have an update for this this weekend. I noticed backups to external sdcard are quite slow, and it may not be grabbing the context files so it's missing like 40mb or so. I haven't had an issue restoring but still ^^
OK, scratch the missing 40mb's thing, looks like thats always been a thing or its just reporting wrong. So all that needs fixed as far as I can tell is the super slow backup time to external sdcard, going to try to do so today if I have time before I get off work or if i can sync all the source I need at home tonight/tomorrow. Other than that its all good. Just would recommend backing up to internal for the time being.
ohlin5 said:
TWRP no longer works....the past few weeks they changed something in the recovery script causing you to have to do manual dirty flashes.
Click to expand...
Click to collapse
This recovery will work the same as TWRP? Or is this one better?
Paul
prosaschi said:
This recovery will work the same as TWRP? Or is this one better?
Paul
Click to expand...
Click to collapse
"Better" is in the eye of the beholder - it's personal preference unless this one does indeed worth with the nightly install scripts (I haven't tried it so I can't be sure).
prosaschi said:
This recovery will work the same as TWRP? Or is this one better?
Paul
Click to expand...
Click to collapse
As @ohlin5 says. They all have their advantages and disadvantages.
Sent from my VK810 4G
Awesome!
This recovery works great. No issues and flashify worked great to put it on my phone. I haven't tested if cm12 likes it but i run slimrom alpha 1 right now.
roirraW "edor" ehT said:
As @ohlin5 says. They all have their advantages and disadvantages.
Click to expand...
Click to collapse
I wish I understood what the advantages of this recovery are over TWRP. From the features list, I can't really tell.