[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5 - Galaxy Note II Original Android Development

[TOOL/UTILITY][TWRP][3.3][RECOVERY] TWRP 3.3.1-0 TeamWin Recovery Project 5/22
[RECOVERY] [5/22/19] TWRP 3.3.1-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.3.1-0 for the Samsung Galaxy Note 2 (International)!
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.
t03g Device Config: https://github.com/TeamWin/android_device_samsung_t03g
Kernel: https://github.com/bigbiff/android_kernel_samsung_smdk4412
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
Please see https://twrp.me for changelog details.
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.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.1
t03g
fix contexts, external storage backing up
t0lte
fix assert
Please note the file name is now t0ltetwrp for now.
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.2.1
t0lte
- fix exfat
2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted
2.7.2.0
All thanks to @Dees_Troy
- fix crash in setting contexts on datamedia
- fix restoring data partition as f2fs after formatting f2fs
- mount data after being formatted
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.2
t0lte and t03g
fix OTG
2.7.0.1
t0lte
fix external_sd backup
fix splitting system
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.2
Add f2fs support
Fix data wiping crash when formatting data
Other surprise stuff that will be in twrp 2.7
2.6.3.1
Update t03g to 2.6.3.1 to support SELINUX kernel and setting contexts properly
Working on t0lte as well.
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
Change to GPL exfat kernel module to work around exfat-fuse bugs
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 Data being listed 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.2
Rename device to t03g from n7100 at goo.im, techerrata.com and build scripts. This is to support ROMs using the t03g product name which is the correct name to use.
2.5.0.1
Fixed encryption
2.5.0.0
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.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.4.1.0
Fix detection of exfat and vfat
Fix formatting vfat past 2GB
2.4.0.1
Revert to using kernel modules for exFAT for performance
2.3.3.2
Uploaded with the following debrick fix courtesy of AndreiLux: https://github.com/AndreiLux/Perseus-S3/commit/54ddcbe7aff1c19c07f76a05ab45f37bcbae2951
2.3.3.1
Updated Kernel due to this recommendation from AndreiLux: http://forum.xda-developers.com/showthread.php?t=2057364
2.3.3.0
Increased Brightness
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
Added ability to backup modem
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
2.3.1.3
Added external SDCARD exfat mounting
2.3.1.2
Added large font
Added code to speed up boot thanks to AndreiLux
2.3.1.1
Fixed keyboard segfault
Handle single LUN file for USB Storage
Handle mounting of slow sdcards
Update USB Mount Code to be more Efficient

FAQ
Q. Are there any themes I can use?
pctv007 has ported some themes for the Note2: http://www.mediafire.com/?34sulxbjxzb34
Q. Can I use Goo Manager to install TWRP if I am not rooted?
A. No, you will not have permissions to access the recovery paritition without a rooted system installed. This gives you the ability to have su installed as SUID root and with Superuser or SuperSu, you can give Android applications root access to use su to access the system as the root user.
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. What happens if I wipe /data?
Good description also here: http://teamw.in/DataMedia
The Galaxy Note 2 is using the fuse filesystem to pretend /data/media is its own filesystem to external computers when you plug the phone into the computer. /data is one partition formatted as ext4. There is a subdirectory for media under /data which is presented as its own block device using fuse. Then mtp responder uses this directory to present the directory to a host computer when plugging in via USB.
Never allow your computer to format this directory in case there is a problem with mtp responder. Also NEVER wipe data under the Wipe menu unless absolutely necessary. This will remove all your files in /data/media.
On the original note, internal SDCARD was a separate file system formatted with the fat32 filesystem but exported directly through UMS.

First !
Envoyé depuis mon GT-N7100 avec Tapatalk

I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?

Great! Now we aren't stuck with cwm anymore!
Thanks!
Edit. Btw, does backup and restore work now?
Sent from my GT-N7100 using Tapatalk 2

""No recoveries were found for your device" - say me GooManager...

xaoc747 said:
I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?
Click to expand...
Click to collapse
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.

Go to the TWRP web site, choose the GT-N7100. Download the Odin flashable .tar file and flash via Mobile Odin.
For themes the HTC Evo themes are the same size 720x1280, but make sure they 2.3 compatible as 2.2 themes dont have some of the options available in 2.3.
Sent from my GT-N7100 using XDA Premium HD app
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
kest874 said:
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.
Click to expand...
Click to collapse
Change the file name to recovery.tar or use the .img file and name it just recovery.img, Mobile Odin will flash then.
Sent from my GT-N7100 using XDA Premium HD app
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
Reb0rn said:
Great! Now we aren't stuck with cwm anymore!
Thanks!
Edit. Btw, does backup and restore work now?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Backups work 100%, just never tested the restore.
Sent from my GT-N7100 using XDA Premium HD app

Backups and restore work fine for me.
Sent from my GT-N7100 using Tapatalk 2
---------- Post added at 04:26 PM ---------- Previous post was at 04:21 PM ----------
xaoc747 said:
I flash it through CWM Recovery, reboot, but Recovery still the same, what's wrong?
Click to expand...
Click to collapse
kest874 said:
I get the same result, also tried the odin method > mobile odin complains that the image is missing. I try PC odin and it blows up when it goes to flash.
Click to expand...
Click to collapse
Download the image (.img) file here:
http://goo.im/devs/OpenRecovery/n7100/openrecovery-twrp-2.3.1.0-n7100.img
Rename it to recovery.img then you'll be able to flash through mobile odin.
Sent from my GT-N7100 using Tapatalk 2

CRudner said:
Change the file name to recovery.tar or use the .img file and name it just recovery.img, Mobile Odin will flash then.
Click to expand...
Click to collapse
Partition could not be found on file - say me Mobile Odin!
recovery.img flashed through mobile odin and I have touch recovery!!! great!!!

Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.

Thanks alot!

Strange, TWRP wont mount my external sd

So does this mean that the Note 2 actually uses the recovery partition, instead of using an initramfs image in the kernel?

bigbiff said:
Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.
Click to expand...
Click to collapse
When will be ready?

mprziv said:
Strange, TWRP wont mount my external sd
Click to expand...
Click to collapse
If you could provide me /tmp/recovery.log I can take a look.

bigbiff said:
Sorry guys I need to fix the zip. Don't use it for now.
Also make sure you guys backup all your partitions just in case.
Luckily the zip is harmless and non damaging. I still recommend using dd to backup your phone but otherwise your fine if you flashed the zip.
Click to expand...
Click to collapse
Flashed it just now.
Works fine 4 me.
What should I be affraid of?

Set backup name, click on the virtual keyboard the program crashes.

Chenglu said:
Set backup name, click on the virtual keyboard the program crashes.
Click to expand...
Click to collapse
I can confirm this issue.
@bigbiff I have attached a link to my log, hopefully it recorded it as it restarts TWRP.http://dl.dropbox.com/u/24188397/recovery.zip
Sent from my GT-N7100 using XDA Premium HD app

Related

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

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

[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Note 3 (Sprint)!
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.
hltespr Device Config: https://github.com/TeamWin/android_device_samsung_hltespr
Kernel: https://github.com/bigbiff/android_kernel_samsung_smn900p
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.
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.1
- Fix writing backups to external sdcard
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.1
Fix splitting system and free space calculation
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.8-4.3-BL
4.3 Bootloader Only
Fix time
2.6.3.7
Fix EFS Backup and Restore
2.6.3.6
Fix USB Storage flags again by adding storage flag
2.6.3.5
Fix USB Storage flags
2.6.3.4
Fix storing SELINUX contexts in backups and restoring them properly
Add fix /data/data SELINUX contexts in Fix Permissions (under Advanced) for applications restoring data without setting contexts correctly
Add EXFAT to kernel
FAQ
How do I fix bootloops?
This has worked for me multiple times to restore from bootloops:
1. Load Odin
2. Download FW for the phone from Sammobile
3. Extract files using 7zip
4. Open Odin
5. Deselect Reboot and Reset Time in Odin
6. Flash the following images one at a time: cache.img, boot.img, system.img
7. Pull the battery and replace
8. Hold home, volume up and then power to boot stock recovery
9. Update.zip will flash
10. Pull the battery and replace
11. Hold home, volume up and then power to boot stock recovery
12. Factory Reset
13. Boot into android and hopefully everything is fixed
Data will be still untouched. Also you have blown the knox fuse and get more knox notifications about applications accessing system.
Very NICE!!
Sent from my SM-N900P using XDA Premium 4 mobile app
---------- Post added at 08:36 PM ---------- Previous post was at 08:26 PM ----------
If choosing to flash in odin, is it the Img.tar file? Do we check the PDA box in odin?
Sent from my SM-N900P using XDA Premium 4 mobile app
Has this been tested to have successful backup Restores? I remember reading something about the SE LINUX needing to be worked out or something to that effect. I'm using twerp 2.6 .3 on the note 2 and everything is Great
Goo manager tells me no recovery found for my device...
Sent from my SM-N900P using XDA Premium 4 mobile app
mrcrptguy said:
Goo manager tells me no recovery found for my device...
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same here
Yeah, goo manager a no go. Has anyone flashed this with success?
The Lawngenie said:
Yeah, goo manager a no go. Has anyone flashed this with success?
Click to expand...
Click to collapse
You have to install via Odin for now. I'm waiting until everything is settled before adding to goo manager.
asacado said:
Has this been tested to have successful backup Restores? I remember reading something about the SE LINUX needing to be worked out or something to that effect. I'm using twerp 2.6 .3 on the note 2 and everything is Great
Click to expand...
Click to collapse
We can restore selinux contexts thanks to Tassadar.
bigbiff said:
We can restore selinux contexts thanks to Tassadar.
Click to expand...
Click to collapse
I quite literally got this phone yesterday so I'm not used to the development phase
bigbiff said:
You have to install via Odin for now. I'm waiting until everything is settled before adding to goo manager.
Click to expand...
Click to collapse
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
asacado said:
I quite literally got this phone yesterday so I'm not used to the development phase
Click to expand...
Click to collapse
It's kind of like Christmas. All developers and testers get in a huge circle and bang heads together to come up with wonderful presents. Analogy of course lol but this will probably get real interesting real fast. Me as a noon figured out boot animations already but that's a small feat to building a recovery or room lol
---------- Post added at 03:11 AM ---------- Previous post was at 03:10 AM ----------
The Lawngenie said:
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
Click to expand...
Click to collapse
U have the tar file. Choose pad and select the tar. Make sure to have the drivers installed and be rooted.
Can we use mobile Odin to flash?
Edit: never mind, device is not supported yet.
Sent from my SM-N900P using XDA Premium 4
Naddict said:
I have made a zip flashable, just to test only as I do not yet have the device.
http://d-h.st/s5z
Not meant to thread hijack, but someone please let me know if it works, if not, the goo manager method certainly will.
Thanks all, and thanks for the latest Note 3 Build to Team Win!
Click to expand...
Click to collapse
I tried the zip and it did not work.
Sent from my SM-N900P using XDA Premium 4 mobile app
smark72 said:
I tried the zip and it did not work.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just use ODIN.. 10 seconds.. Done. But dont use ODIN with the zip he provided. Go to TWRP website.
tandxcstar1 said:
Just use ODIN.. 10 seconds.. Done. But dont use ODIN with the zip he provided. Go to TWRP website.
Click to expand...
Click to collapse
I am just currently without a pc til tomorrow. Thought I might be able to get it done another way.
Sent from my SM-N900P using XDA Premium 4 mobile app
smark72 said:
I am just currently without a pc til tomorrow. Thought I might be able to get it done another way.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am sorry I dont know of any other way.. Maybe re-try downloading zip file he provided and try again.
---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------
The Lawngenie said:
I tried via odin but it didnt see file witj pda checked...do i extract recovery.img? Can u explain?
Click to expand...
Click to collapse
What version of ODIN did you use? I used ver 3.04. I think the previous version 1.85 I couldnt find it. Let me know what version your running. Also no I didnt have to extract IMG file. Just found zip with ODIN ver 3.04 and selected PDA slot. I am sure its safe to extract and use on older version of ODIN.
tandxcstar1 said:
I am sorry I dont know of any other way.. Maybe re-try downloading zip file he provided and try again.
---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------
What version of ODIN did you use? I used ver 3.04. I think the previous version 1.85 I couldnt find it. Let me know what version your running. Also no I didnt have to extract IMG file. Just found zip with ODIN ver 3.04 and selected PDA slot. I am sure its safe to extract and use on older version of ODIN.
Click to expand...
Click to collapse
I figured it out, thanks for all the help
Just flash with Odin 3.07 running a first backup now.
Thank you all for your hard work.
~Bizack
edit: Did a full backup on a extreme 32gb sd card it 4.29gb in 410 sec @ 29mb a sec... Damn this phone flies...

[Hammerhead] [CWM-RECOVERY] PhilZ Touch - 6.57.9 [END OF LIFE]

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

[RECOVERY][ms013g] TWRP 3.0.0 Touch recovery[with EFS/Modem backup][F2FS support]

Team Win Recovery Project 3.0.0.x​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Phone look:
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.
CHANGELOG for 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-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)
CHANGELOG for 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
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-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
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-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
CHANGELOG for 2.8.3.0:
-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
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
ON post #3
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
Team Work Recovery Project, Tool/Utility for the Samsung Galaxy Grand 2
Contributors
aapav01
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2016-02-05
Created 2015-05-13
Last Updated 2016-02-07
Change LOG & Difference
Main Difference From Other TWRP recovery available for ms013g
Changes of 7 feb 2016
Updated to 3.0.0
Changes of 21 September 2015
Updated to 2.8.7.0
Added F2FS support
Changes of 13th May 2015
Updated to 2.8.6.0
MTP support
ADB sideload fixed
EFS backup
Modem backup
DOWNLOADS
Method 1:
Odinmod edit - links removed
1) Install whatever drivers make you happy and make your device connect (i would suggest samsung ones).
2) Reboot your device in download mode you can use adb reboot download or the hardware key combo for your device.
3) Load up Odin and uncheck auto-reboot.
4) Click PDA and select the TWRP tar you downloaded.
5) Connect your device in download mode.
6) Click start.
7) When its finished disconnect your device, pull the battery out.
8) Reinsert the battery and use the hardware keys for your device to power directly into recovery mode (this will bypass install-recovery.sh if you are stock).
9) Enjoy having a custom recovery.
Method 2: IF you are already on anyother recovery
1)Reboot your device in recovery mode you can use adb reboot recovery or the hardware key combo for your device.
2)Now just flash the flashable zip from sdcard or extsdcard you have downloaded
3)Now REboot into recovery and Enjoy ur new TWRP recovery
Downloads
TWRP 3.0.0
mod edit - links removed
TWRP 2.8.7.0 (OLD VERSION)
mod edit - links removed
TWRP 2.8.6.0 (OLD VERSION)
ODIN (Tar file)- mod edit - links removed
Recovery flashable zip -mod edit - links removed
Recovery image - mod edit - links removed
Good work
You are good mr @aapav01 , thz for your hard work!! Your are my best developer!! And waiting your new rom!! I'm a big fan of you!!��������������
But why i can't download your recovery flashable zip(everytime i click on download now it just reload page not download), i can only download only recovery image?
G.NO_BOYz said:
You are good mr @aapav01 , thz for your hard work!! Your are my best developer!! And waiting your new rom!! I'm a big fan of you!!��������������
But why i can't download your recovery flashable zip(everytime i click on download now it just reload page not download), i can only download only recovery image?
Click to expand...
Click to collapse
mod edit - links removed
it working.. try to open in a new tab
aapav01 said:
twrp_2860.zip - 8.72 MB
it working.. try to open in a new tab
Click to expand...
Click to collapse
Thz alot now it working!!
thanks aapav for the new recovery
it works flawlessly
best dev!!
thanks alot:good::good::good::good:
@aapav01 Can I install the themes from this thread? forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
5 Golden Stars for this smart project.
Regards ?
rv5750 said:
@aapav01 Can I install the themes from this thread? forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Yeah it should Work
aapav01 said:
Yeah it should Work
Click to expand...
Click to collapse
it work, i already tried it and it look very cool!!!
installation on cyanogen 12.1
Hey aapav I'm currently using cyanogen 12.1 that is android 5.1.1 And i have cwm recovery installed. Can i install this recovery through cwm if i'm on cyanogen? Or this is only flashable on kitkat?
pradhyumn1998 said:
Hey aapav I'm currently using cyanogen 12.1 that is android 5.1.1 And i have cwm recovery installed. Can i install this recovery through cwm if i'm on cyanogen? Or this is only flashable on kitkat?
Click to expand...
Click to collapse
yes, u can i already do this!!
hit thank if i helped!!
does not work in mine dunnoe y
i am on kitkat 4.4.2 .....was using a custom rom s6styled s5 port by singhking83 .....when i tried installing v3...it stuck on the boot logo of samsung......but then i installed cwm.,..then the rom was installed successfully.....what must be the problem? i relly like the interface of twrp.....
Why does the title say "kitkat only" ? Does that mean I can't use this recovery to flash CM 12.1 ?
Oscuras said:
Why does the title say "kitkat only" ? Does that mean I can't use this recovery to flash CM 12.1 ?
Click to expand...
Click to collapse
No, u can flash it in cm 12.1 , i already did it!!
Click thank if i helped!!
thanks
thk for great rom
I recently flashed this recovery and now while flashing a theme it gives error could not load data/media/0/twrp/theme/ui.zip ...
Sent from my SM-G7102 using XDA Free mobile app
xubairsarwar said:
I recently flashed this recovery and now while flashing a theme it gives error could not load data/media/0/twrp/theme/ui.zip ...
Sent from my SM-G7102 using XDA Free mobile app
Click to expand...
Click to collapse
You don't need to flash theme, u just change (theme name.zip) to ui.zip and copy it in sd card/TWRP/theme if you can't fine theme folder you can make new folder and copy ui.zip in there. After you just go to recovery mode and done!!
Good luck guy!!
Click thank if helped!!

[RECOVERY][ms01lte] TWRP 2.8.7.0 touch recovery[with EFS/Modem backup][F2FS support]

Team Win Recovery Project 2.8.7.x​
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Phone look:
CHANGELOG for 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-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)
CHANGELOG for 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
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-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
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-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
CHANGELOG for 2.8.3.0:
-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
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
DOWNLOAD:
ON post #3
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
Team Win Recovery Project Grand 2 LTE, Tool/Utility for the Samsung Galaxy Grand 2
Contributors
aapav01
Version Information
Status: Stable
Created 2015-09-22
Last Updated 2015-09-22
Reserved
changelog for device specific:
initial relesased
DOWNLOAD
Method 1:
Odin http://shabbypenguin.com/?developer=Tools
1) Install whatever drivers make you happy and make your device connect (i would suggest samsung ones).
2) Reboot your device in download mode you can use adb reboot download or the hardware key combo for your device.
3) Load up Odin and uncheck auto-reboot.
4) Click PDA and select the TWRP tar you downloaded.
5) Connect your device in download mode.
6) Click start.
7) When its finished disconnect your device, pull the battery out.
8) Reinsert the battery and use the hardware keys for your device to power directly into recovery mode (this will bypass install-recovery.sh if you are stock).
9) Enjoy having a custom recovery.
Method 2: IF you are already on anyother recovery
1)Reboot your device in recovery mode you can use adb reboot recovery or the hardware key combo for your device.
2)Now just flash the flashable zip from sdcard or extsdcard you have downloaded
3)Now REboot into recovery and Enjoy ur new TWRP recovery
Downloads
TWRP 2.8.7.0
https://basketbuild.com/devs/aapav01/ms01lte/TWRP
ZIP FILE
TAR (uploading soon)
IMG(uploading soon)
Reserved Post
Reserved Post 3
Hello,
Should I use this recovery instead of CWM recovery to flash motion rom S5 mini port rom? Will i brick my phone if I use Cwm to flash your 5.1.1 rom?
I am not familar of TWRP because hard key doesnt works (・ิω・ิ)
Thank you @aapav01 for your generosity at making tools for ms01lte even though you dont have the model ٩(♡ε♡ )۶ (>ω<)
Sent from my SM-G7105 using Tapatalk
Yuen.Jason22 said:
Hello,
Should I use this recovery instead of CWM recovery to flash motion rom S5 mini port rom? Will i brick my phone if I use Cwm to flash your 5.1.1 rom?
I am not familar of TWRP because hard key doesnt works (・ิω・ิ)
Thank you @aapav01 for your generosity at making tools for ms01lte even though you dont have the model ٩(♡ε♡ )۶ (>ω<)
Sent from my SM-G7105 using Tapatalk
Click to expand...
Click to collapse
even twrp is more stable+user friendly.yes,you can flash any rom with any recovery.
Thanks for your work
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
Thanks for your work
Bro why the time in twrp didn't match the timezone i'm in or the phone time? And if i reebot to twrp it took some times to open the menu sometimes i had to push the power button to get into menu?
yerrie said:
Bro why the time in twrp didn't match the timezone i'm in or the phone time? And if i reebot to twrp it took some times to open the menu sometimes i had to push the power button to get into menu?
Click to expand...
Click to collapse
you have to set the time manually to your timezone in settings-timezone.
if you see some delay in recovery,try out some cool twrp theme here(i use play).remember to use 1280×720 and uss 2870_v1(or something like that)(method for installtion given there).
Can i use this for garnd 2 g7102? If i can please help me. For getting it
abhayparmar said:
Can i use this for garnd 2 g7102? If i can please help me. For getting it
Click to expand...
Click to collapse
this is for G7015,search for G7102 in android development section.
http://forum.xda-developers.com/showthread.php?t=2798433
[TWRP][SM-G7102] Unofficial TWRP Recovery
http://forum.xda-developers.com/showthread.php?t=3107535
[RECOVERY][ms013g] TWRP 2.8.7.0 touch recovery[with EFS/Modem backup][F2FS support]
Links to 7102 TWRP thread
Sent from my SM-G7105 using Tapatalk
@aapav01 can you please update TWRP to 3.0.0????????? I am willing to be tester
Yuen.Jason22 said:
@aapav01 can you please update TWRP to 3.0.0????????? I am willing to be tester
Click to expand...
Click to collapse
it'd be awesome [emoji32]
Sent from my SM-G7105 using Tapatalk
fufle said:
it'd be awesome [emoji32]
Sent from my SM-G7105 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...recovery-twrp-2-8-6-0-touch-recovery-t3107535
[email protected] said:
http://forum.xda-developers.com/gal...recovery-twrp-2-8-6-0-touch-recovery-t3107535
Click to expand...
Click to collapse
I just tried it today, and my phone got bricked... I had to reinstall the rom again.. lol, but thank you
Sent from my SM-G7105 using Tapatalk
fufle said:
I just tried it today, and my phone got bricked... I had to reinstall the rom again.. lol, but thank you
Sent from my SM-G7105 using Tapatalk
Click to expand...
Click to collapse
I realized I'm sorry
[email protected] said:
I realized I'm sorry
Click to expand...
Click to collapse
It's Okay ?
Sent from my SM-G7105 using Tapatalk
Can this be flash over stock revovery

Categories

Resources