Develop Bugs

[RECOVERY][otter] TWRP 3.1.0-0 touch recovery [2017-03-10]

[RECOVERY][otter] TWRP 3.1.1-0 touch recovery [2017-05-19]
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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 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.
CHANGELOG for 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
CHANGELOG for 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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
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.

id love to try this out, but from the comments on the site, it appears that the commands listed do not work... also i have a mac so its probably different.

Sweet! I'll have to try this out!

I just gave the new version a quick run around the block...
PROS: The distribution is no longer a boot image that forces a flash of the old FFF 1.0 along with TWRP. It's now an actual recovery image that can be flashed through fastboot like... "fastboot flash recovery twrp-fire-2.1.0.img"
CONS: Even though there are some more reboot options in this new version, they are all still broken. Just as in 2.0.0, none of the reboot options (system, recovery, bootloader... I'm assuming the last one is supposed to boot into fastboot mode) will reset the bootmode accordingly before the device is restarted. That makes these options pretty useless as the device will still continue to boot in the previous bootmode. So, the TWRP bootloops will continue to plague new users who have no idea how to get it to boot to the system.... bummer.

I love that we got this! Buuuuttttt I like 2.0 just fine. Its stable. It works. love to see progress though.
Sent from my Kindle Fire using XDA

its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium

smirkis said:
its great to see progress, but as kinfaun said reboot is still broken.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
thats a deal breaker for me... thanks for the update tho

I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium

smirkis said:
I spoke with deestroy n were gonna try to get it resolved. yay lol
they don't have our device so its hard to know what doesn't work. looking forward to testing the update
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Sweet id switch back if it was fixed i like how its skinable

i cant install any zip files i get unknown md5 error just rooted tonight

nckfrs said:
i cant install any zip files i get unknown md5 error just rooted tonight
Click to expand...
Click to collapse
I just tried playing around with the new version some more and I can confirm the above...
Here's what I get from TWRP's Install section for the few ROMs I tried to test flash.
Code:
-- Verify md5 for /sdcard/update-cm7-wipeall.zip
-- No md5 file found, ignoring
-- Installing /sdcard/update-cm7-wipeall.zip ...
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
* Verifying partition sizes...
Error flashing zip '/sdcard/update-cm7-wipeall.zip'
This version is really not ready for use. Hang on to your version 2.0.0 for at least a little while longer.

While I agree its not ready it did work for me to make a back up and then install Hashcode's test rom and restore a back up another user posted for us.

Reboot to system works perfectly fine for me, and has in previous versions as well.

Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah it will, until you assign the bootmode outside of using the power button from firefirefire (in other words, use fastboot, adb or 'reboot recovery' from a rom to set the bootmode) the reboot wrappers won't set it back. It is actually a relatively simple solution and Smirkis' is familiar with what's required if he is talking to the OP I would expect a solution for this.

treUse said:
Reboot to system works perfectly fine for me, and has in previous versions as well.
Click to expand...
Click to collapse
dw9906 said:
Reboot to system works fine for me to. Always has.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
If you used the power button to get into recovery while FFF was loading, reboot to system will work fine. That's not what's being discussed here.
If you got to recovery that way, the bootmode was never changed and stayed (presumably) on 4000. So, hitting the reboot from within TWRP will continue to boot in normal mode and it "seems" to work fine.
Try setting the bootmode to recovery (5001) and restart the device to get to TWRP. Then if you try rebooting into the system, it will go back into TWRP because TWRP does not change the bootmode back to normal (4000) before attempting to reboot into the system.
The same problem exists for all the reboot options in 2.1.0... whether normal, recovery, or bootloader, it will not change the bootmode to the appropriate value before restarting the device. As a result, the device will just reboot using whatever bootmode is already set.
EDIT: What Sblood86 said above... I'm just longer winded.

I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2

dw9906 said:
I knew what you meant, but that's not what you explained in your first post. Had you been this specific in your initial post then this conversation would have never happened.
On another note, this recovery might as well be forgotten about. Doesn't seem like they are ever going to fix it completely.
EDIT: Didn't mean for that to sound like i was being rude to kinfauns. That's not how i meant it to be.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't offended by your post, so you shouldn't take this post that way either... but I don't think you read the thread very carefully before you posted. I think I was fairly clear about what the problem entailed in my first post of this thread. I made it a point to mention that TWRP does not set the bootmode properly before rebooting. In addition, smirkis noted that he's gotten the developer's ear in getting some problems fixed, so things are looking up in terms of getting past these issues.
Furthermore, TWRP can't simply be "forgotten about" because the super majority of articles on the Internet detailing steps in modifying the Kindle Fire mention TWRP. New users will continue to use TWRP just for the fact that it's simply the more recognized recovery program of the two we have available.
FWIW, I'm more hopeful than ever TWRP will get fixed and continued to be developed.

I really do hope it gets fixed. I really like the themeing capabilities. It's a great recovery, just doesn't seem to have much support.
Sent from my LG-P999 using Tapatalk 2

clockwork recovery ftw.

[RECOVERY][toroplus] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.
CHANGELOG for 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!
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.
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.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.

Nice. Had this on my nexus s 4g and loved it.
Sent from my Galaxy Nexus using xda premium

Will nandroids from other recovey work??
GNEX

Definitely will be keeping an eye on this. Great work.

I can stand bugs, but taking a full minute may be a but much, considering how often I am in recovery. I'm really happy to see it here, though, and can't wait for a more finished product.

fcisco13 said:
Will nandroids from other recovey work??
GNEX
Click to expand...
Click to collapse
From past experience, no. Different file format used in the backup from this recovery and clockwork.

gunna give this a shot. TWRP was awesome on my E3D
EDIT: Working good so far. Screen formatting is a little odd, but not a big deal. The 60 second boot up was a little odd too, but worth it.

Back up in 76 seconds!! File manager!! Win!!
GNEX

I'll definately be following this. I use Boot Manager so I'm only in CWM if a rom wont boot. Once the 60 second issue is fixed, this will be a daily recovery for me. Thanks!
Sent from my Galaxy Nexus using Tapatalk

Using this now and even with the bugs it kicks ass, thanks!
Sent from my Galaxy Nexus using XDA

same here once the 60 secs is gone this will be my new recovery!

For whatever reason, mine didnt take 60s to come up. I wasnt timing it but it was a reasonable amount of time.

Thanks Dees_Troy and the rest of the TeamWin team, I've been hoping to get a chance to try out TWRP, it sounds very promising! I'm looking forward to future releases that iron out the kinks. Thanks again!

What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.

weirddan455 said:
What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.
Click to expand...
Click to collapse
The interface is 100x better.... And are you in such a hurry that you can't wait a minute to boot into recovery? It's not that serious.
I've never liked CWM so this is a no brainer for me. Plus CWM Touch is just the standard CWM with added touch. Seems cheap to me. TWRP 2 is a completely touch orientated recovery, built from the ground up to do so.
Sent from my Galaxy Nexus using Tapatalk 2

weirddan455 said:
What does it do that clockworkmod doesn't? Except take forever to load. No one's gonna wait 60 seconds to go in recovery. Booting all the way into Android doesn't even take that long. And clockworkmod touch has been around for a while so get that if you want the touch feature.
Click to expand...
Click to collapse
Ummm..
Que files to flash.
Half the time (if not faster) to backup/restore.
That alone does it for me.
GNEX

Proper working builds (no more preview build) are now available!

Sweet thanks!
Sent from my Galaxy Nexus using Tapatalk 2

Every zip that I try to flash errors out and fails. Using a verizon gnex.
*update* I flashed the recovery through fastboot and it works fine now. Not sure if something is up with your recovery zip.

There were a few problems with installing zips on the builds I uploaded earlier. If you aren't sure, go ahead and re-update just in case. Sorry.

[RECOVERY][toro] TWRP 3.0.0-0 touch recovery [2016-02-06]

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.
CHANGELOG for 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!
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.
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.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.

I really love this recovery.

This recovery kicks burt
Sent from my Galaxy Nexus using xda premium

Thank you much. Love having touch again

did 2.1.2 add any thing that makes it worth flashing form 2.1.1?
i guess the major reason for it was the sprint phone?

gi812 said:
did 2.1.2 add any thing that makes it worth flashing form 2.1.1?
i guess the major reason for it was the sprint phone?
Click to expand...
Click to collapse
Bug fix. Apparently 2.1.1 would only back-up and not restore
Sent from my Galaxy Nexus using XDA

This recovery is working flawlessly
Sent from my Galaxy Nexus using Tapatalk 2

cowsquad said:
This recovery is working flawlessly
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Except for it refuses to flash pure aosp build 5
Sent from my Galaxy Nexus using xda premium

I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.

zedorda said:
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus

zedorda said:
I had to switch back to CWM bc I ran into too many ROMs refusing to flash. Hope this issue can be remedied soon.
Click to expand...
Click to collapse
Same here. Would really like to be able to use this recovery. Hopefully it will be good to go soon.

PacerguyDon said:
Same here. Would really like to be able to use this recovery. Hopefully it will be good to go soon.
Click to expand...
Click to collapse
I've been using this recovery without issues.
Sent from my Galaxy Nexus using Tapatalk 2

I hope the dev didn't drop working on this one for the sprint version. I really hate the CWM recovery and would love to be able to count on this one but it still fails to flash most of the ROMs I have tried.

Yes.... I have had this problem as well and have switched back to CWM.
Sent from my Galaxy Nexus using Tapatalk 2

zedorda said:
I hope the dev didn't drop working on this one for the sprint version. I really hate the CWM recovery and would love to be able to count on this one but it still fails to flash most of the ROMs I have tried.
Click to expand...
Click to collapse
Sprint sucks anyways lol jk mine works very well on VERIZON NEXUS
Sent from my Galaxy Nexus using Tapatalk 2

Loving this recovery, the zip queue is awesome!

tacosrdelicioso said:
This recovery kicks burt
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Who's burt
Sent from my Galaxy Nexus using xda premium

BlackHoleSlam said:
Who's burt
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Duh!!! "Smokey and the bandit" "Cannonball run"
GNEX

crimson12 said:
Loving this recovery, the zip queue is awesome!
Click to expand...
Click to collapse
What is zip queue btw? What does it do?
Sent from my Galaxy Nexus using Tapatalk 2

fcisco13 said:
Duh!!! "Smokey and the bandit" "Cannonball run"
GNEX
Click to expand...
Click to collapse
oh my bad where are the themes for twrp
Sent from my Galaxy Nexus using xda premium

[RECOVERY][geehrc4g] TWRP 2.8.6.0 touch recovery [2015-03-26]

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:
Tablet look:
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:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our NEW website! NOTE that the 2.8.6.0 version is ONLY available on our new site and is not available on our other, older mirrors!
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.

Reserved.

This worked awesome. The install directions r very easy and now I'm ruining the latest version. Thank u

Praise the TWRP Gods! Official support. Works great.
EDIT: I had the other TWRP thread closed, and i had the same question about compression and if it was fixed.

Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
Anybody know if we can use compression now?
Sent from my LG-LS970 using xda premium

Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
Left the recovery on for 5 mins to check for heat and it's cool to the touch! It also goes on standby where u swipe to unlock. Very nice!
Sent from my LG-LS970 using xda premium

Dees_Troy, what device name are you using for this? (We are trying to standardize geehrc4g_spr/geeb_a/geeb_bell/geeb_rgr, etc).

Just did a full backup in TWRP.. including the new EFS1, EFS2 and EFS3 options. Used the compression option just to test.
Backup completed in 96 seconds. Wiped phone. Restored the compressed backup... system, data, cache, boot, efs1, efs2 and efs3 were all restored in 59 seconds. Rebooted system... all is good. Everything restored just fine it seems. I was not aware of any previous compression issues(I dont use the setting normally) so I'm not sure if there is some other compression bug in existence or what.. but things seem to be working.
And since people always want a flashable zip version of recovery I'm attaching the zip to this post. I will *try* to keep it updated with the latest version.

has anyone tried flashing the Jelly Bean port with this?
I had to switch to CWM to flash it and want to go back to TWRP as soon as there's a compatible build.

Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
So much happening! Official support for OG, jelly bean ota. Good day for Optimus G users.
Is this something where I should have a full battery before flashing? I'm too excited to charge my phone up.
Sent from my LG-LS970 using xda app-developers app

Its a great day for america everybody

Installed via Goo, rebooted into new TWRP and performed a backup using compression. During the backup I noticed the screen saver kick in. Unlocked the screen and let it continue to backup. After a minute I looked back at the screen and noticed it had turned off. The battery charging symbol appeared on screen (not sure if this occurred before or after I attempted to power up the phone). Anyhow, the LGOG failed to boot and instead went to a blank screen and began flashing the red notification light.
I had over 50% charge on the battery and the phone was plugged in while I was attempting to make a backup when this happened. Anyway, I had to open the phone up and detach and re-attach the battery connector in order to get it to boot up. This has happened a lot with my phone (the whole crash/power off in recovery), but usually only when flashing roms, never during a backup before. I'm not sure if it's my phone, the battery, or TWRP (haven't used CWM much, but it hasn't happened with it). I've had a ton of problems with my LGOG when it comes to flashing, LGNPST restore, etc. so who knows what's going on. Just wanted to share my experience.

Has the date/time stamp on the backups been fixed on this update?

just installed it through goomanager, about to try it out! hopefully it will make trying my test builds alot easier!

ok so i made a full backup including compression of every partition except cache and recovery. when i did this it took a while which i suppose is understandable considering how much music i have in google music anyway, the phone got hotter than it had ever gotten before and i literally almost burned myself on it. then i put it in the freezer and took it out when it was finished backing up. so just a warning to everyone who has a lot of data. hopefully this will be fixed now relatively soon now that there is official support

Oh my. I just installed this from goo manager and it seemed my phone is hard bricked after trying to get into recovery. Perhaps it's just me?
Method:
Lg Lifeless Rom -> LGNPST to ZV9 -> Root with engine95's method -> Install Goo -> Install OpenRecovery -> Restart trying to go into recovery -> Phone unresponsive. Won't turn on, won't light up when plugged in, just stays completely black with no lights.
Any idea what could have happened? The Goo Manager method may not be so safe.
Edit: Seems to have started up again with a factory reset when I held power for 5 minutes. Held the power that long and it randomly lit back to life. The LGNPST finished and the phone was reset several times, so not sure what happened.

[RECOVERY] TWRP 2.4.3.0 touch recovery [2013-03-01]
I suspect that overheating issues are related to the fact that the Optimus G like the Nexus 4 doesn't have any built-in thermal management. On Nexus 4 I switched to using show-p1984's Bricked kernel that has built-in thermal management to prevent overheats. Until we can come up with a similar solution on the Optimus G it is recommend that you NOT use compression in your backups.

Were the Goo instructions taken down on purpose due to WASSHOI's problem?

Shelnutt2 said:
Dees_Troy, what device name are you using for this? (We are trying to standardize geehrc4g_spr/geeb_a/geeb_bell/geeb_rgr, etc).
Click to expand...
Click to collapse
For the Sprint version we're using geehrc4g.

does anybody have a flashable zip for TWRP 2.4.3?

[RECOVERY][gardalte] TWRP 2.8.4.0 touch recovery Samsung Galaxy Light [2015-1-28]

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:
Tablet look:
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.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
CHANGELOG for 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
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 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
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. 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
DOWNLOAD:
* Unified support for MetroPCS and T-Mobile Versions
TWRP Builds
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.

Latest Windows adb drivers required for sideload
HERE
Latest Linux adb drivers required for sideload compiled from android source
HERE
To install unzip and open terminal in root of folder
Code:
sudo cp adb fastboot /usr/bin

Awesome!

Unjustified Dev said:
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:
Tablet look:
CHANGELOG for 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
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 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
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. 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
DOWNLOAD:
* Unified support for MetroPCS and T-Mobile Versions
TWRP Builds
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.
Click to expand...
Click to collapse
Thank you for posting this. I'm trying to find out how to install this on my Samsung Galaxy Light phone after I've already rooted it and if that's even safe. Can someone please let me know?
Thanks so much.

GalaxySmokes said:
Thank you for posting this. I'm trying to find out how to install this on my Samsung Galaxy Light phone after I've already rooted it and if that's even safe. Can someone please let me know?
Thanks so much.
Click to expand...
Click to collapse
You can use flashify to install the image if your already rooted.

TWRP Updated to 2.8.2.0 compiled from the android 5.0 branch
This release allows for 3 different ways of installation
openrecovery-twrp-2.8.2.0-gardalte.tar.md5 - installs through odin v3.09
openrecovery-twrp-2.8.2.0-gardalte.img - installs with flashify or dd command you must be rooted
openrecovery-twrp-2.8.2.0-gardalte.zip - installs through previous recovery
Before installing be aware that this release supports none of the previous cyanogenmod builds as of yet and if you plan on using the sideload command you must use the lastest adb drivers linked in the second post. ENJOY!!
Changelog
* Updated to latest release
* Removed custom mtp path - fixes mtp
* Removed large font size
* Removed unsupported misc partition and usb mounts
* Remove screen timeout - if the option appears go to settings > and restore defaults

Wow, thanks for supporting this device! Using one as a temp fix and this is a help!

TWRP Updated to 2.8.4.0
This release allows for 3 different ways of installation
openrecovery-twrp-2.8.4.0-gardalte.tar.md5 - installs through odin v3.09
openrecovery-twrp-2.8.4.0-gardalte.img - installs with flashify or dd command you must be rooted
openrecovery-twrp-2.8.4.0-gardalte.zip - installs through previous recovery
Changelog
Listed on first page as always kanged from Dees_Troy threads

Thanks for posting this. I experienced 1 small bug. When I select anything from the Reboot Menu in TWRP (System, Power Off, Recovery, Bootloader, Download), the phone freezes for about 2 minutes before proceeding. The phone doesn't respond to any inputs after I make a selection. After 2 minutes the phone will proceed with the selection I made. So it works, but lags on that menu. Minor inconvenience.
Edit: I discovered the Reboot Menu responds instantly (no lag) if I wait 1-2 minutes before making a selection. For example: I open the Reboot Menu and let phone (untouched) sit for 1-2 minutes. Phone will instantly respond to menu selection. Weird.