Database Info

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
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.

Changelog: See our website!

FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG06IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG06IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-speedy-1.1.0.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG06IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.

Sweet! First post! Time to get rid of rom manager!
Teleported from my Shifty Speedy using Tapatalk

Nice! Congrats on the release on the evo shift!

Thank you for this amazing recovery teamwin! Way way better then anyone ever expected! CWM will prolly never be used again lol
Supremely Shifted

ZOMFG!!

yeah, i'm pretty sure this is wood i'm sporting

Yeah, been using this since last night, it is awesome. And clockwork did have USB storage mode, its in the advanced settings, not that it matters anymore.

Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk

thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Same thing here.. Had to do a battery pull.
Sent from my PG06100 using Tapatalk

Haha... You can still use RM to reboot to TWRP recovery and when I tried to backup my ROM (through RM) (just to see what would happen) it just sends me to TWRP recovery as well...
from the "CRACKED" Speedy EVO Engine...

thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.

good job man. . .thank you

jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
Not doubting you! But with CWM it took barely a minute.
Teleported from my Shifty Speedy using Tapatalk

jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
I waited a good 5 minutes after the "end" of the progress bar and finally did a battery pull. I was able to fix permissions through terminal, just didn't work through recovery.
Sent from my PG06100 using Tapatalk

noob question but will this also restore backups made from cwm?

hoesnaps said:
noob question but will this also restore backups made from cwm?
Click to expand...
Click to collapse
No. You'll need to make fresh backups
Sent from my PG06100 using Tapatalk

Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium

sparksco said:
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It has the option to partition but I haven't tried it yet... anyone?
Sent from my PG06100 using Tapatalk

[RECOVERY][Epic 4G]TWRP 2.6.3.0 touch recovery [2013-09-16]

Because of the way the recovery is packed into boot, this will not work with all kernels / ROMs. It is known to work with CM7.2 and CM9.1.0. It will probably work with most other MTD-based ROMs and kernels but will not work with any BML ROM or kernel. Use at your own risk! Installing a new ROM or kernel may end up replacing your install of TWRP. Also note that TWRP is *not* compatible with CWM backups. We are not based on CWM, we wrote our own recovery based on AOSP. With that said, I hope that you will get a chance to at least see how fast and easy-to-use TWRP is.
In addition to the on-screen keyboard, TWRP now supports using the hardware keyboard on the Epic 4G. Unfortunately the screen doesn't rotate, but hey, the hardware keyboard does work.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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.
DOWNLOAD:
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.

First. Thanks.
×Marcusant

Sick!!!"
Sent from my SPH-D700 using xda premium

Wow, this looks great, can't wait to try it out. Thanks TeamWin
Sent from my SPH-D700 using XDA

This will probably work on all mtd roms afaik.
×Marcusant

Niiiice

Part of the trick with this build of TWRP is the inclusion of a new utility that I've started working on called injecttwrp. It's a work in progress. I'll be building upon this to inject our recovery ramdisk into existing Samsung boot images so that you can choose to keep TWRP installed as you install new ROMs or kernels regardless of what recovery is included with the kernel or ROM that you are installing.
https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c
Note that this utility is not restricted to just working with TWRP. It could be used to inject any recovery that you wanted.

Awesome, I use this for my Kindle Fire and love it. It also is the only current recovery that works with the new 3.0 kernel, but I think that is mainly a fire issue. I will try it when I get some time!

anyone confirm it works on ics (aokp particularly)?

This looks awesome
Just a thought.. marcusant.. could you build this recovery into nyan for sayyy cm7?
Sent from my SPH-D700 using XDA

Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium

Of course on the day I'm busiest is when this is released lmao. Thanks for the hard work guys, I'll be playing with this tomorrow for sure!
Sent from my SPH-D700 using xda premium

ÜBER™ said:
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The failure was an oddity with the formatting of our flash_image on ics as far as I can tell
×Marcusant

I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.

Dees_Troy said:
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Click to expand...
Click to collapse
I mean it goes through everything but then stops towards the end... write_flash_image has an error and it shows E: /sdcard/goomanager/twrp.zip ... and aborts.. so what marcus said about the flash image.
Sent from my SPH-D700 using xda premium

hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!

pvtjoker42 said:
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
Click to expand...
Click to collapse
........interface similar to Epic CM Team's test touch recovery; will await sign from Dees_Troy + flash again.
.........sent from today's android = 4.0.4

I believe that the zip install should now be working!

Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium

ÜBER™ said:
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I couldn't get it to install on cm7 says error installing blah blah (bad).. tried to download it twice.. both times errors
Sent from my SPH-D700 using XDA

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
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.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the AT&T HTC One X
Contributors
eyeballer, dees_troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16

first
thanks guys

very nice! closed up my unofficial one

Sweet bring on the flash addiction
Sent from my HTC One X using xda premium

I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?

z28james said:
I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?
Click to expand...
Click to collapse
Flash it then go to advanced and "copy recovery.log to sdcard" then get me the log. Ideally come to #twrp on freenode and pastebin it for us there - webchat link in OP if you don't know how to use IRC.

z28james said:
I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?
Click to expand...
Click to collapse
seems to be scripting problem
chainfires superSU flashes fine..

Tried usb mount, but no go..

me too
stuck..

No usb is a known issue listed on our website...

seems adb is not working...

niceppl said:
seems adb is not working...
Click to expand...
Click to collapse
yup, same issues as mine, no usb storage or adb... working on it!

niceppl said:
seems adb is not working...
Click to expand...
Click to collapse
Known problem
Sent from my HTC One X using XDA

designgears said:
yup, same issues as mine, no usb storage or adb... working on it!
Click to expand...
Click to collapse
thanks,
well if adb is working...usb is not that important...

good
very nice！

Very interesting and intriguing, but I have a few questions:
1) does it charge the battery when in the recovery (I think CWM doesn't?)
2) are you planning on fixing the two issues listed, including compatibility with CWM backups?

fixed adb access!
unofficial build: http://www.gigashare.in/3fbf1

designgears said:
fixed adb access!
unofficial build: http://www.gigashare.in/3fbf1
Click to expand...
Click to collapse
So I just flashed this and I still have no adb. Any ideas?

androidoholic said:
So I just flashed this and I still have no adb. Any ideas?
Click to expand...
Click to collapse
try flashing it again, make sure you have adb drivers installed as well.

Zarboz said:
seems to be scripting problem
chainfires superSU flashes fine..
Click to expand...
Click to collapse
I woldnt be quick to call it a scripting problem because its the identical script to my other ICS ROMS that DO work on twrp (Rezound and Evo 3D).
But who knows, I could be wrong. But generally speaking, if it works on one Recovery and not another then I would think the Recovery would be the issue and not the script.
I will flash this and test it myself and see what the deal is. The scripting I use with my ROM is pretty basic.
Format, mount, extract, symlink, unmount. Nothing fancy there.
I'll join IRC channel after I have to time to play to help T/S if OP wants?
EDIT: BTW: I love twrp and its always been my recommended recovery. I have been bugging Con24 who ported twrp to Rezound to do this for us so I am really happy to see twrp here!!!!!!

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
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.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the HTC One S
Contributors
Dees_Troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16

You guys are doing an amazing job, ROM will come these days!

Well, this is version 2.2.1 but wheres the changelog for it ?
I installed it anyway, but I like to see what changed :-3
EDIT:
Nevermind, this is for S3 >.<

Love it! Glad to see s3 getting some love too!
Sent from my HTC VLE_U using Tapatalk 2

Yeaaaaaaaaaah! Yes! Yes! Yesssss! Yeeees! Thank you million times!

Fantastic!

@Dees_ Troy
I seemed to find a little bug. The battery in recovery always shows 66%.

Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium

dsellers2 said:
Hmmm. Using twrp I can't flash kernels unless I use Fastboot but others can. This isn't my first rodeo, and I'm able to flash roms fine. Actually I flah a rom with a stock boot.img in it and it still keeps the old kernel that I fast booted days before. Anyone know what this may be? Or of there is something I can do to correct this? I've tried unlock and relock. I've tried reinstalling twrp. I tried erasing boot but was unable to do so assuming cause I don't have s- off. I'm out if ideas.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Yeah I've learned that yesterday that this is a well known issue with some of the htc. There is two waya,one you have described to flash it manually in fastboot and the other is a workaround that twrp supports. It is called HTC dumlock,just search on their official page how to use it.
Sent from my HTC One S using xda app-developers app

Thank dev. For S3 development.
Sent from my HTC One S using xda app-developers app

I got my Villec2 Unlocked with htcdev.com site
but i can't flash any recovery, Why?
I found that this recovery works on my hts one s (my i mean villec2)
i tried to do it couple of times with cmd and fastboot, and then with HTS ONE S AIO KIT
every time it says that sending is ok, and writing i ok... but can't go into recovery got only htc sentence...
Do you guys got any solution? whey on that threat above some people with s3 says that they flashed recovery and i can't do it?

Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP

Wyall said:
Download GooManager at Playstore and then use it to "Install OpenRecoveryScript" That will install TWRP
Click to expand...
Click to collapse
I tired that method also without any progress,
GooManager downloaded img then i saw little box that recovery installed successfully, But unfortunately still cant use recovery

Do you have root? And did you use the Reboot to Recovery Option in GooManager?

Wyall said:
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
Click to expand...
Click to collapse
I just got unlocked Phone with htcdev, i thought that i need to Flash Recovery before i can Flash superSu like i saw in torxx guide. Can i Flash superSu like i try to Flash Recovery? Which one shall i choose?
With GooManager i restart to Recovery, the result was the same....
And still i count on your help in flashing Recovery on my HTC
Regards in advance

First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/

Wyall said:
First you need to unlock, then you can root and after that install a Custom Recovery
To Root your device, follow that guide: http://www.modaco.com/topic/355509-testing-villec-superboot/
Click to expand...
Click to collapse
So now i got root (method from link above) and i got custom recovery installed with gooManager method. Sweet. i for other users it's very important to got root first

Updated to 2.2.2.0!

Dees_Troy said:
Updated to 2.2.2.0!
Click to expand...
Click to collapse
Hi!! Has full wipe partitions in this recovery?
Thanks?

Do it work with S4 or just only S3? Thanks

[RECOVERY][Unofficial][Epic4G] TWRP 2.6.3.0 touch recovery [2014-02-11]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Phone look:
Tablet look:
CHANGELOG for 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
CHANGELOG for 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
CHANGELOG for 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.
DOWNLOAD:
Latest Builds Here
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.[/QUOTE]

Links are up enjoy the light show
Twrp now has haptic feedback.
edit: This is untested.

Wow, finally no more empty zips that bricks the phone. Downloading.

Finally the 2.6.3.0 version
Waited for long time for this
Sent from my Nexus 5 using xda app-developers app

Does this work with all partitions?
Sent from my SPH-D700 using Tapatalk 2

DaKillaWilla said:
Does this work with all partitions?
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Yes , it was confirmed working.

Hello all,
I flashed TWRP 2.6.3.0 and now any ROM I try to flash getting FAILED message. Am I missing something...
Thx in Adv

FerociousAndroid said:
Hello all,
I flashed TWRP 2.6.3.0 and now any ROM I try to flash getting FAILED message. Am I missing something...
Thx in Adv
Click to expand...
Click to collapse
Give more info what rom? What recovery etc.
Sent from my SPH-D710 using Tapatalk

Unjustified Dev said:
Give more info what rom? What recovery etc.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Fashed from CMW 5.0.2.7 to Twrp_6.3_Unofficial_20140211_d700.zip. Then tried installing any of the following:
cm-7.2.0-epicmtd.zip
cm-10.1.3.1-epicmtd.zip
Try to go back to cwm-5.0.2.7-epic4g.zip
ThePeoplesROMv2.22_BML.zip
ThePeoplesROMv2.22_MTD.zip
I odin back to "pit & Deodexed-FC09.zip" and then installed CMW 5.0.2.7. I'm on CM10.x. Didn't bother with TWRP. I could be have been the new Samsung 4GB micro SD card I was using who knows.
Thx any way.

FerociousAndroid said:
Fashed from CMW 5.0.2.7 to Twrp_6.3_Unofficial_20140211_d700.zip. Then tried installing any of the following:
cm-7.2.0-epicmtd.zip
cm-10.1.3.1-epicmtd.zip
Try to go back to cwm-5.0.2.7-epic4g.zip
ThePeoplesROMv2.22_BML.zip
ThePeoplesROMv2.22_MTD.zip
I odin back to "pit & Deodexed-FC09.zip" and then installed CMW 5.0.2.7. I'm on CM10.x. Didn't bother with TWRP. I could be have been the new Samsung 4GB micro SD card I was using who knows.
Thx any way.
Click to expand...
Click to collapse
I second this, my backups & flashable zips that worked fine with 2.6.0.0 are no longer working in this TWRP version, even though the md5 checks out. There is a problem with this new release, imo, as this was an occurrednce with both of my Epics.

Luthiensdad said:
I second this, my backups & flashable zips that worked fine with 2.6.0.0 are no longer working in this TWRP version, even though the md5 checks out. There is a problem with this new release, imo, as this was an occurrednce with both of my Epics.
Click to expand...
Click to collapse
Probably because of the updates etc that were done. I can't guarantee older backups will be compatible.

Unjustified Dev said:
Probably because of the updates etc that were done. I can't guarantee older backups will be compatible.
Click to expand...
Click to collapse
I don't think that's the case, the problem occurs when flashing ROM & kernel zips too, not just when attempting to restore existing backups. I re-downloaded a couple (& checked md5) again to confirm this. (Of course, I also checked md5 for this new recovery prior to installing it)

Luthiensdad said:
I don't think that's the case, the problem occurs when flashing ROM & kernel zips too, not just when attempting to restore existing backups. I re-downloaded a couple (& checked md5) again to confirm this. (Of course, I also checked md5 for this new recovery prior to installing it)
Click to expand...
Click to collapse
Well sorry I guess this won't be fixed because I quit developing. I can do no more than answer questions.

flash off of CWM and now I got stuck on the Samsung screen. any help?

Nexus11 said:
flash off of CWM and now I got stuck on the Samsung screen. any help?
Click to expand...
Click to collapse
Give me some time to compile a new one I have to update both epic 4g and epic 4g touch.