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

DamBadz

Senior Member
Mar 10, 2012
1,049
171
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

Thx for this mate:)

Sent from my HTC Butterfly using xda premium
 

DamBadz

Senior Member
Mar 10, 2012
1,049
171
Re: [RECOVERY] TWRP 2.4.2.0 touch recovery [2013-02-25]

It had something wrong with the resolution? Sorry for my bad english^^

Sent from my HTC Butterfly using xda premium
 

fastcx

Senior Member
Jun 9, 2010
1,017
195
Puchong
resolution is indeed smaller than 1080p, thats why whole screen isnt occupied, perhaps next release can fix this?
 

PG101

RC-RT Liaison Admin - Devil's Advocate
Staff member
Aug 12, 2008
14,050
15,683
goo manager says invalid MD5 checksum... on X920D
 

SamePaul

Senior Member
Sep 22, 2010
270
98
there is mistake on the site, it calls X920d as dlxu and X920e as dlxub1, whereas it is the opposite.

I looked at the theming guides and I missing something very fundamental - where to put theme? o_O does anyone know?
 

PG101

RC-RT Liaison Admin - Devil's Advocate
Staff member
Aug 12, 2008
14,050
15,683
So which one should we download? for x920D... dlxu or dlxub1?
 

SamePaul

Senior Member
Sep 22, 2010
270
98
So, does anyone know where to put theme files for this recovery? :) I'm tired of this quarter-screen GUI.
 

PG101

RC-RT Liaison Admin - Devil's Advocate
Staff member
Aug 12, 2008
14,050
15,683
Is there an explanation of exactly what all functions of wipe there are? For e.g. if I wipe data.. what does it wipe? System? Etc..
 

ccombe

Member
Nov 15, 2010
27
0
Nashville
wipe dalvik cache (in advanced) doesn't work for me...

does anyone else have this issue? I click on the option and then it reloads the same menu over and over again.
 

SamePaul

Senior Member
Sep 22, 2010
270
98
I experience very odd problem with TWRP.
Tried M7 ROM yesterday and realized that there is no much gain, but lot of small and annoying bugs. So I decided to restore my stock ROM from backup. So much surprise I couldn't do that! After restore my phone stuck on boot screen. No logcat, no shell. So I have no slightest idea what happens with phone.
My first guess was "same story as on Desire S - htcdev unlock doesn't let flash boot from recovery!".
There is no S-OFF yet for Butterflies, so I decided to flash boot myself. And again unpleasant surprise - TWRP backup is in unknown format (.win) and there is no way to fetch boot.img file...
So I had to flash killx kernel, but I hate do things that I didn't plan to do.
I still want to recover my old boot.
Is there way to do that?
Is there way to fetch other files from recovery (data, system, etc)?

[NOSTALGIC_HOWL]So pity there is no 4EXT recovery for Butterfly. It is sooo good[/NOSTALGIC_HOWL]
 

Dees_Troy

Senior Recognized Developer
Mar 31, 2008
1,705
13,582
KC MO
www.teamw.in
Re: [RECOVERY] TWRP 2.4.4.0 touch recovery [2013-03-12]

I experience very odd problem with TWRP.
Tried M7 ROM yesterday and realized that there is no much gain, but lot of small and annoying bugs. So I decided to restore my stock ROM from backup. So much surprise I couldn't do that! After restore my phone stuck on boot screen. No logcat, no shell. So I have no slightest idea what happens with phone.
My first guess was "same story as on Desire S - htcdev unlock doesn't let flash boot from recovery!".
There is no S-OFF yet for Butterflies, so I decided to flash boot myself. And again unpleasant surprise - TWRP backup is in unknown format (.win) and there is no way to fetch boot.img file...
So I had to flash killx kernel, but I hate do things that I didn't plan to do.
I still want to recover my old boot.
Is there way to do that?
Is there way to fetch other files from recovery (data, system, etc)?

[NOSTALGIC_HOWL]So pity there is no 4EXT recovery for Butterfly. It is sooo good[/NOSTALGIC_HOWL]

boot.emmc.win is a boot.img with a different file name.
 

SamePaul

Senior Member
Sep 22, 2010
270
98
boot.emmc.win is a boot.img with a different file name.

Thank you for reply

Should I flash whole file as is or drop first 256 bytes?
I compared boot.img from Killx
Code:
ANDROID!ЂЭ:..Ђ`Ђ©ъ...Ђ*Ѓ......PЃ..`Ђ............................
console=ttyHSL0,115200,n8 androidboot.hardware=dlxub1 user_debug=31.
with boot.emmc.win
Code:
DЊ.€0.ЈЁoќb-ЛрvЁ§EљУ[ѓ†›aэAKФK.ЖR.ыМявK‡EЗ.ђ]’w^Џ.ѓЪд.Џ.€ЂЯѕџе›.ЖД›±.®“6ГА…/$4ѓluҐkBiтљA.]Aшgtк.љЁылLџЉ.$Ю}Ђ.Ѕ.&«S*UЂ*r.ющXWТш.ХK·№ЫЃлДт._$nуБГ†/Ё.Ъ0‘ЮјJА·ЕЭ..Ч..ю©‰.Й..b.ЛGQФ“;ІІI>3Ј°n‘.µfд..$~ЙЮHн:ѕ1»ЅщФL..Nфъ.G.ќЗkюпњ±.Ц.D.Иґ«SЭЏЫjшЛ·‡.я1?Љ8Ћ+1•CБE†tћ-®
ANDROID!ёуM..Ђ`Ђфу...Ђ*Ѓ......PЃ..`Ђ............................
console=ttyHSL0,115200,n8 androidboot.hardware=dlxub1 user_debug=31.
first 256 bytes is something completely different, but then continues pretty similar stuff.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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.
    3
    Looks like I forgot to change the resolution flag on dlxub1, so there's a new 2.5.0.1 build for dlxub1 now with the correct resolution. Sorry about the trouble.
    2
    So which one should we download? for x920D... dlxu or dlxub1?

    get into bootloader. On the top is written what type you have dlxu or dlxub1. And download image that matches your device