[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:

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
Bucharest
Tried to flash PG86IMG.zip via bootloader. "Model ID incorrect" or something. I'm S-OFF`ed (by Revolutionary, of course).

Tried to flash the .img via fastboot & it worked. I still miss 4EXT Touchcovery :( .

Thanks or this, though. Better than killing the volume buttons! :)

It's nice to see they didn't turn their backs to the GSM.
 
  • Like
Reactions: sakarka1

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
Bucharest
Thanks alot for this :D

edit:does it have a charging bug too?

Sadly, yes.

RED LED lights on for 3 seconds, then goes on, so forth, so forth...

Back on CWM Revolutionary 4.0.1.4. With it, at least it's charging (RED LED lights up, then goes off for a couple of seconds, but then comes back up and doesn't dissapear anymore).
 
Last edited:

habitat22

Senior Member
Jan 8, 2011
445
515
25
If I understand it right, the "HTC Dumlock" is for HTC unlocked bootloaders and with it you can install boot.img because the recovery.img is flashed a second time into boot? And this is only enabled after the installation of the Dumlock?
But with the S-OFF Revolutionary bootloader we can flash boot.img from recovery.
So S-OFF users can install the TWRP recovery without installing the Dumlock feature and everything will work? And it isn't flashed to the boot partition?
 
Last edited:
  • Like
Reactions: sabbath88

kjames2001

Senior Member
Oct 22, 2011
381
66
If I understand it right, the "HTC Dumlock" is for HTC unlocked bootloaders and with it you can install boot.img because the recovery.img is flashed a second time into boot? And this is only enabled after the installation of the Dumlock?
But with the S-OFF Revolutionary bootloader we can flash boot.img from recovery.
So S-OFF users can install the TWRP recovery without installing the Dumlock feature and everything will work? And it isn't flashed to the boot partition?

Yes, I guess you are right, at least that's how I understand it too.

I think most of us need after s-off is just a charging recovery!

But this will obviously benefit those with s-on. Thanks for the hard work tho!

Sent from my HTC EVO 3D X515m using Tapatalk
 

jamesclinton

Senior Member
Sep 22, 2009
889
1,718
Android Jungle
I think it does charge, the only problem is the red light keep blinking non stop when device is off and no red lights on when in recovery and the battery stays 66% :confused:

Sadly, yes.

RED LED lights on for 3 seconds, then goes on, so forth, so forth...

Back on CWM Revolutionary 4.0.1.4. With it, at least it's charging (RED LED lights up, then goes off for a couple of seconds, but then comes back up and doesn't dissapear anymore).
 
  • Like
Reactions: Bling

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
Bucharest
Backup with CWM Revolutionary 4.0.1.4 : 1 GB required.
Backup with TWRP 2.0 : 1.8 GB required.

:(
 
Last edited:

jamesclinton

Senior Member
Sep 22, 2009
889
1,718
Android Jungle
Reports after abt 1hr in recovery only

First of all i´ll like to thank the team for all the effort invested in this and to let you know that is highly appreciated :D

After testing for abt 40mins this are the things i´ve noticed

1. Flash and boot into recovery red light did not on or blinks, after setting the time zone i noticed the time and battery percentage freez but when i click the setting button and then click the back button the time and batt % start working again.

2. After 30min reboot into recovery the red comes on.

3. After charging batt from 99% to 100% (i guess) the batt % disappeared but the red light stays red and after abt 5mins the batt% comes back to 99%

4. Shutdown device the red light keep blinking (known bug)

"All this test was performed inside recovery"

edit: i copied the logs to sd but i don´t know the default folder

THANK YOU ONE MORE TIME :D
 
Last edited:
  • Like
Reactions: Bling

Formhault

Senior Member
Jun 10, 2011
11,517
4,581
Bucharest
It doesn't really matter if the LED lights up or not when it's in Recovery, if it IS charging.

Also, it doesn't really matter if it blinks or stays lit when it's off & plugged in, as long as it is charging...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 37
    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
    Updated to 2.2.2.0!
    4
    Charging & battery percentage are fixed thanks to helicopter88. The light still blinks, but it is charging now.
    4
    Updated to 2.3.0.0!
    4
    Updated to 2.3.1.0