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

Search This thread

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,562
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.
 
Last edited:

runhopskipjump

Senior Member
Dec 20, 2010
208
45
I also am enjoying this. No issues to report. I am waiting for some loving for my xoom. Great job guys!
 

stevey5036

Senior Member
Nov 10, 2008
50
7
Flashed yesterday, no problems throughout the day.. Now my phone is shutting down and rebooting into recovery immediately after turning it on.. Any fix?
 

stevey5036

Senior Member
Nov 10, 2008
50
7
False alarm.. The OTA was pushed to my phone (again) and would reboot the phone to try to install via stock recovery but it obviously wasn't there. Sorry.
 

droid future

Senior Member
Feb 3, 2011
81
20
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.

Sent from my rabbit hole using my carrotbolt.
 

Kalico

Member
Dec 23, 2009
19
46
Colorado
I flashed this recovery yesterday and everything works fine. I love the touch screen working so great. Only one issue. I'm unable to mount usb storage through recovery nor my ROM. I'm currently running gingeritis 3D and also tried with ICS MIUI, I couldn't mount on either one. I'm wondering if there is anything I can do to get my computer to recognize my phone. Thank you in advance.

Sent from my rabbit hole using my carrotbolt.

Just shooting in the dark here, but have you tried a different kernel?

USB Mass Storage works for me with TWRP2 & LiquidSmooth 3.2.
 

Droid0351

Senior Member
Aug 4, 2010
489
68
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.

Sent from my ADR6400L using Tapatalk
 

Kalico

Member
Dec 23, 2009
19
46
Colorado
What if I want to go back to CWR, do I just use rom manager and reflash the recovery again. Can I restore a nandroid from CWR with twrp 2.0. This looks awesome. Like to try it only if I can back to CWR.

Sent from my ADR6400L using Tapatalk

I used ROM Manager to reflash CWM.

The way TWRP backs up the rom seems to be different than CWM (hooray compression!), so you can't restore a CWM Nandroid directly. At least, not that I've noticed.
 

GatoEnFuego

Senior Member
Aug 27, 2010
72
4
So i may have bricked my phone...

Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?
 

Droid0351

Senior Member
Aug 4, 2010
489
68
I just flashed this. It worked for me. Did u make sure you renamed the zip and put it root of sdcard. This recovery has potential. I do like using the touch screen instead of my hardware, especially if volume keys are not responsive.

Sent from my ADR6400L using Tapatalk
 

GatoEnFuego

Senior Member
Aug 27, 2010
72
4
So i may have bricked my phone...

Flashed TWRP without a rom installed. So it rebooted to the white HTC screen and obviously just hung there. Pulled the battery, removed the IMG file from my SD card using my computer card reader, put the card back in, put the battery back in and now it won't turn back on, dead. So uhhh was that a cardinal sin or is my phone salvageable?

So the twrp IRC chat was extremely helpful in getting my phone working again. Great group of guys! Lesson learned, if you're going to flash a new recovery make sure you have a working ROM installed or else you can get caught in a bind if you pull the battery during the white HTC screen.

And if you do, make sure you lick your terminals... ;)
 

Boostjunky

Senior Member
Jun 18, 2010
577
367
I really like the concept of this recovery (touchscreen instead of hardware keys), but I feel it still needs some work to become "idiot proof", and needs to be more thorough.

For example, I decided to try restoring a backup of Skyraider Zeus, coming from Gingeritis1.1. After it completed and I rebooted into the system, there were all sorts of "leftovers" from the Gingeritis ROM packed in with Skyraider Zeus.

In other words, the recovery doesn't format the partitions prior to restoring the backup. This could lead to some serious issues for people when restoring backups of one ROM from another without manually formatting everything first.

Sent from my ADR6400L using XDA App
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    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.
    5
    [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]
    4
    [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]
    4
    [RECOVERY] TWRP 2.5.0.0 touch recovery [2013-04-09]