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

Version 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
  

Version 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

Version 2.6.0.0

Note spéciale: Si vous utilisez un thème personnalisé, quelques-uns des changements de la version 2.6.0.0 ne sera probablement pas visible sans une mise à jour du thème.

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

Version 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
  
• Added official theme for 1080x1920 portrait devices (HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
  
• 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
  
• Special Note: If you are running a custom theme, the changes in 2.5.0.0 will likely not be compatible with your theme.
  

Version 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
  

Version 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
  
• Fixed persistence of the 24 hour / military time setting