• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

Acery

Member
Jan 28, 2013
33
5
I flashed the new version with the ZIP through the existing twrp. The only hiccup I see is if I select reboot from within TWRP and then select Power Off I will reboot into TWRP after powering back up instead of into my ROM.

The only way I can boot back into my ROM is if I select "System" in the Reboot menu within TWRP.

Is this normal or do I have some strange boot loop with the Power Off option?
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,856
7,057
I flashed the new version with the ZIP through the existing twrp. The only hiccup I see is if I select reboot from within TWRP and then select Power Off I will reboot into TWRP after powering back up instead of into my ROM.

The only way I can boot back into my ROM is if I select "System" in the Reboot menu within TWRP.

Is this normal or do I have some strange boot loop with the Power Off option?

I am looking into the issue.
 

zodduska

Senior Member
Jan 12, 2010
98
22
Same problem trying to flash cleanrom and cm. I'm not sure whether my sd card is exFat or not but I formatted it with the phone if that helps.

Log was too big to paste, find it attached
 

Attachments

  • recovery.zip
    132.9 KB · Views: 10

bhp117

Senior Member
Oct 22, 2011
505
48
los angeles
Just wondering if anyone can add ' slots ' functionality to twrp?
Before I got the vzw note 2 I have a droid bionic for over a year.
Even though it have a locked bootloader but the devs did some amazing work in creating roms and recovery.
I was using a recovery called safestrap that have twrp integrated to it and it have slots function.
Basically what the slot function do is let you create up to 4 slots so you can flash any roms you like into any slots and still have the stock rom.
The cool thing is you can switch between slots/roms within secs without having to flash your previous backup to restore which ever rom you want to use.
That makes it so much easier for you to try/test a rom you like.
For example
When I was using the bionic with safestrap I created 2 slots. 1 slot I have a jellybean rom . Another slot I have a ics rom. Also I still have the stock ota ics blur
I'll be testing the jellybean rom but its not dd for me so I switch back to the ics rom as dd whenever I goto to work. Switching between the 2 roms just tskes seconds
I dont have to full wipe then reflash/restore anything so its more convenient.

Sorry for the long post but hope someone can figure out how to add that function to twrp so we can have multiple roms available to switch with instead of doing backups and restore all the time

Thanks for reading my blabbing
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,856
7,057
Same problem trying to flash cleanrom and cm. I'm not sure whether my sd card is exFat or not but I formatted it with the phone if that helps.

Log was too big to paste, find it attached

Code:
minzip: mmap(995551968, R, FILE|SHARED, 17, 0) failed: Out of memory

It's running out of memory. I will try to step through your procedures in the log and see if I can reproduce. Thanks so much for the log.

Also if you are good with ADB, I can use your help testing.
 
Last edited:

WyoSi

Senior Member
Jan 26, 2012
214
71
Re: [RECOVERY] TWRP2.4.1.0 TeamWin Recovery Project 2/1

Just wondering if anyone can add ' slots ' functionality to twrp?
Before I got the vzw note 2 I have a droid bionic for over a year.
Even though it have a locked bootloader but the devs did some amazing work in creating roms and recovery.
I was using a recovery called safestrap that have twrp integrated to it and it have slots function.
Basically what the slot function do is let you create up to 4 slots so you can flash any roms you like into any slots and still have the stock rom.
The cool thing is you can switch between slots/roms within secs without having to flash your previous backup to restore which ever rom you want to use.
That makes it so much easier for you to try/test a rom you like.
For example
When I was using the bionic with safestrap I created 2 slots. 1 slot I have a jellybean rom . Another slot I have a ics rom. Also I still have the stock ota ics blur
I'll be testing the jellybean rom but its not dd for me so I switch back to the ics rom as dd whenever I goto to work. Switching between the 2 roms just tskes seconds
I dont have to full wipe then reflash/restore anything so its more convenient.

Sorry for the long post but hope someone can figure out how to add that function to twrp so we can have multiple roms available to switch with instead of doing backups and restore all the time

Thanks for reading my blabbing

Someone in the Dev forum has been working on a multi boot version of TWRP. It seems to be non trivial to make work. I asked about it earlier too as I can from a bionic.
Hopefully they can make it work

Sent from my Galaxy Note 2 using Tapatalk 2
 

zodduska

Senior Member
Jan 12, 2010
98
22
Code:
minzip: mmap(995551968, R, FILE|SHARED, 17, 0) failed: Out of memory

It's running out of memory. I will try to step through your procedures in the log and see if I can reproduce. Thanks so much for the log.

Also if you are good with ADB, I can use your help testing.

No problem. Unfortunately I'm not very familiar with ADB and for some reason my home PC (windows 8) sees multiple android devices when I connect my phone, I was unable to use Casual or Odin because of this.. had to do the unlock on my work pc.
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,856
7,057
No problem. Unfortunately I'm not very familiar with ADB and for some reason my home PC (windows 8) sees multiple android devices when I connect my phone, I was unable to use Casual or Odin because of this.. had to do the unlock on my work pc.

Created https://github.com/TeamWin/Team-Win-Recovery-Project/issues/101 for your issue. I will be testing the fix soon to see if it works.

I replicated this way:
1. Backup Boot/System/Data
2. Factory Reset
3. Install Cleanrom 4.5

The way I am trying to solve this is to have linux drop file cache after creation of the tar files to give memory back to the mmap call in minzip.
 
  • Like
Reactions: zodduska

zodduska

Senior Member
Jan 12, 2010
98
22
Seems to be working well for me so far!

Quick question.. I've installed AOSPA and I'm trying to get my SD card to FAT32 without an sd card reader, I'm assuming Wipe External Storage formats to exFat? I'm having the same ASOP SD issues after trying it.
 

crl95

Member
Dec 17, 2012
48
1
for some reason when im trying to update the recovery in goo manager it is telling me my device is not supported. I am running Rootbox does anyone have any idea wat the problem here may be?
 

gchild320

Senior Member
Feb 17, 2012
1,319
1,686
Terre Haute
Re: [RECOVERY] TWRP2.4.2.0 TeamWin Recovery Project 2/25

for some reason when im trying to update the recovery in goo manager it is telling me my device is not supported. I am running Rootbox does anyone have any idea wat the problem here may be?

Getting the same notice running PAC man. Using goo is so convenient, guess I'll use adb

Sent from my SCH-I605 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 46
    [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 2 (Verizon)!



    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.

    t0ltevzw Device Config: https://github.com/TeamWin/android_device_samsung_t0ltevzw

    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
    13
    I had the same problem, except what was weird about it was that it backed up slimrom to extsd just fine but when I switched to beans 25 and tried to back up, no cigar

    Will build 2.7.01 tonight to fix that issue.
    11
    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.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

    3.0.0.1

    -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.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.2.1
    - fix formatting emmc partitions

    2.7.2.1
    - fix formatting emmc partitions

    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.1
    Update with fix for 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

    2.6.3.1
    Add SELINUX support

    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
    Move exfat to GPL kernel module for bugs with exfat-fuse

    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.1
    Fix decryption of encrypted devices.

    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 exfat and vfat detection
    Fix formatting vfat past 2 GB

    2.4.0.1
    Revert to using kernel modules for exFAT for performance

    8
    twrp rocks...can't wait to use for kitkat...if u needs more testers im down...if not i will patiently wait. :)

    Will be up soon on goo and techerrata.
    6
    I saw a post online that the new 2.7 version was release, but when I go to the official pages, or through goo.im, its still 2.6.3. Is there an updated link anywhere for the latest?

    Working on it still, adding to my todo list, must of missed building.