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

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,536
0
KC MO
www.teamw.in
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
 
Last edited:

v3n3

Senior Member
May 31, 2012
316
130
0
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 >.<
 
Last edited:

dsellers2

Senior Member
Dec 10, 2007
854
80
0
Erlanger
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
 

qzem

Senior Member
Jun 23, 2010
1,594
1,030
0
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
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
 

majcher3310

Member
Mar 23, 2009
14
0
0
Koszalin
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?
 

majcher3310

Member
Mar 23, 2009
14
0
0
Koszalin
Do you have root? And did you use the Reboot to Recovery Option in GooManager?
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 :D
Regards in advance :)
 
Last edited: