• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[deprecated] [RECOVERY] [new|old bl] TWRP 2.6.0.0 touch recovery [2013-07-23]

Status
Not open for further replies.
Search This thread

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
- - - - - -​



TWRP
- Team Win Recovery Project -

Attention:
You can find the updated TWRP recoveries by @DJNoXD in his thread here!

Remember that you can donate to TWRP here: http://www.teamw.in/project/twrp2


This thread is deprecated.
Old content:

I have been asked to create an own thread for the TWRP recovery I compiled for the new bootloader, so here you go.
Personally I prefer TWRP over CWM, but that's for everybody to choose on their own.
We got official TWRP support for the Optimus 2x - but only for the old bootloader. You can use the GooManager app to flash the recovery (see below).

I adapted and compiled TWRP for the new bootloader and tested it for quite a while without a single problem.
Additionally I added a flashable zip recovery installer for the old bootloader if someone prefers that over the use of GooManager.

TWRP is NOT my work, but the work from TeamWin under the lead of Dees_Troy.
If you like TWRP you can donate to TeamWin here: http://www.teamw.in/project/twrp2



Bugs?:

If you have any issues grab a log, it's really easy: Advanced -> Copy Log to SD. It will copy the log to your external sdcard.
You can post it in here, then I'll review it and forward it to Dees_Troy if it contains an error.
Or contact TWRP directly via their contact form: http://www.teamw.in/contact

I'm not interested in any complaints or bug reports that do not contain a log! Seriously, just don't.
Remember: I'm compiling this for my personal use and am sharing it with you. I don't care if you use it or not, you're free to use CWM or whatever other recovery is out there.​






Installation:

These files are flashable zips, just flash them with your current recovery.

If you want to flash the recovery manually, extract the img files from the zips, push it to the SDCard, open the Terminal Emularot and type:

old bootloader:
Code:
su
dd if=/sdcard/openrecovery-twrp-oldbl-p990.img of=/dev/block/mmcblk0p7

new bootloader:
Code:
su
dd if=/sdcard/recovery-TWRP-newbl.img of=/dev/block/mmcblk0p8


Team Win Recovery Project 2.3, 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:



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.

CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!

-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations

CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking

CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting

CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements

CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)

CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!

DOWNLOAD:
The fastest and easiest way to install TWRP [tonyp note: for the old bootloader version!] 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:

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
TWRP does support a great theme engine, see here: http://www.teamw.in/project/twrp2themers
If you know of nice themes for our HDPI (480x800) device or created your own please post them here :)


Personally I'd love to get the Holo Theme by thecoby xdhpi theme to get ported to our hdpi device:
http://forum.xda-developers.com/showthread.php?t=1942309
I don't have time to do that at the moment, so I'm posting it here if someone is interested in doing it.
If not I'll do it once I find the time.


Thanks to aldyu we do have the Holo Dark Theme now fully functional for our device! :)
Check out his post here and don't forget to press thanks!

Installation:
Download the theme, rename it to ui.zip, create the folder /TWRP/theme at the internal SDCard and put the zip into it.

Preview:
7x3951exvdy4qoyqg6dn.png
 
Last edited:

C0D3N1N3R

Senior Member
Aug 27, 2011
304
97
New Delhi
Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.

TWRP Theme - Holo Light
 

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
Thanks, didn't see it. Although it's not finished yet according to the posts in the thread it does look nice :)

Thanks for the awesome recovery port!
The button between home and back broke the recovery (or was it the theme?). After I pressed the button and pulled the battery the TWRP screen kept on flashing and never entered the recovery (or let me boot the phone). I had to NVFlash to get my device back. Flashed it again same problem. Deleted TWRP folder, now it works flawlessly.

TWRP Theme - Holo Light

Eh, certainly not TWRP's fault. Maybe the themes. Or no idea what you did :D
The button is for displaying the recovery log, pressing it again will remove the log again.
I've been using this quite often when I was testing every aspect of the recovery to ensure it's safe.
 

Garfields 2X

Senior Member
Apr 10, 2012
106
19
Wiesbaden
you have to set the time manually in settings?! ;)

btw tony thanks a lot - really appreciate your work! i waited so long for TWRP on new bootloader! everything works great so far! you are such a huge WIN for all p990 owners!

THANKS
 
  • Like
Reactions: tonyp

SWTR

Senior Member
Jan 2, 2012
635
197
Cham
AW: [RECOVERY] [new|old bl] TWRP 2.3.3.0 touch recovery [2013-01-19]

Why can' t I see the batterystatus?

Gesendet von meinem LGP990 mit CM10.
 

I.m.Tuga

Senior Member
Jun 20, 2012
518
286
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]

I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!


Sent from my LG-P990 using xda app-developers app
 

MetaIIica

Senior Member
Aug 30, 2012
1,568
2,619
Saarbrücken
I'm sorry for the noob questions but i have lots of backups from CWM, does those backups work on TWRP?
Really interested in using this recovery (no more button mashing) and the possibility to rename the backups is awesome.
Thank you very much Tony!!


Sent from my LG-P990 using xda app-developers app
No, you can not use it.

The best option was i missed in CWM is flash in Batch-Mode. But the clock and the battery status are a funny gimmick. Nice but not important.
 
  • Like
Reactions: I.m.Tuga

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]

Okay, as promised another post about the new twrp version.

The v3.3.0.0 version for the new bootloader has unfortunately been compiled exactly at the time pengus kernel source had the rare ext4 race bug.
So I'd recommend everyone on the new bootloader to update to the new version asap.
If you think you got errors then just do a backup, format /system, /data and /cache, then restore. Most people, including me, shouldn't be affected though.

The new kernel should be absolutely stable, it's based on Kowalski kernel 011p4 (which is like p3 but with the shutdown bug fuxed). This one is completely stable again. (remember, even cwm is using the cm kenel which I'd consider less stable than pengus one).

I had planned to update TWRP during this weekend anyways as twrp 2.4.0.0 got released.
Now cm10.1 users can safely use twrp as well!

Lol, while heading to the twrp website I noticed it got a new update today.
So expect a twrp 2.4.1.0 release tomorrow :)


What's new in 2.4.0.0:
Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
Support for exFAT formatted sdcards (also thanks to bigbiff)
Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
Added wipe cache and dalvik after ADB Sideload
Replaced many system calls with their native C counterparts
Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
Fixed AOSP recovery commands to run after decryption on encrypted devices
Improvements for building TWRP in CM10.1
Other minor bugfixes and improvements




Sent from my LG-P990 using xda app-developers app
 

I.m.Tuga

Senior Member
Jun 20, 2012
518
286
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]

Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...

Sent from my LG-P990 using xda app-developers app
 

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
Re: [RECOVERY] [new|old bl] TWRP 2.4.0.0 touch recovery [2013-02-01]

Did try twrp, made a backup with it and tried to restore from that backup but the backup folder was empty, am i missing something...

Sent from my LG-P990 using xda app-developers app
I did plenty of backups with twrp, always worked like a charm.
In twrp you can choose the backups location (internal or external sdcard).
So check if it's on the other partition.

Speaking about TWRP.
Please read my update in the twrp thread.
You can wait till tomorrow with updating twrp though, I will push version 2.4.1.0 tomorrow.



Sent from my LG-P990 using xda app-developers app
 

tonyp

Inactive Recognized Developer
Feb 3, 2011
5,022
34,905
Okay, about version 2.4.1.0:
My self-built newbl build had already been at version 2.4.1.0 :)
I was in a little hurry and confused myself with the 2.4.0.0 version for the oldbl lol :cyclops:
Now the official build reached 2.4.1.0 as well: http://teamw.in/project/twrp2/65
I downloaded it and zipped it into a flashable zip again, download at the OP.

To avoid confusion I uploaded "recovery-TWRP-2.4.1.0-newbl-20130201.zip" file as well - but it's exactly the same recovery as the previous one.
If you downloaded the "recovery-TWRP-2.4-newbl-20130201.zip" file you already got the newest version and don't have to reflash it it.


2.4.0.0 and 2.4.1.0 changelog:
What's new in 2.4.1.0:
  • Fixed a problem with mkdosfs that formatted sdcards to 2GB
  • Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
  • Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
  • Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
What's new in 2.4.0.0:
  • Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
  • Support for exFAT formatted sdcards (also thanks to bigbiff)
  • Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
  • Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
  • Added wipe cache and dalvik after ADB Sideload
  • Replaced many system calls with their native C counterparts
  • Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
  • Fixed AOSP recovery commands to run after decryption on encrypted devices
  • Improvements for building TWRP in CM10.1


2.4.0.0 is a big update. If you want to read more details about the meaning of the above lines in the changelog I'd suggest to read the following post which explains them in more details:
http://rootzwiki.com/news/_/article...dated-to-240-big-changes-under-the-hood-r1360

:)
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 122
    - - - - - -​



    TWRP
    - Team Win Recovery Project -

    Attention:
    You can find the updated TWRP recoveries by @DJNoXD in his thread here!

    Remember that you can donate to TWRP here: http://www.teamw.in/project/twrp2


    This thread is deprecated.
    Old content:

    I have been asked to create an own thread for the TWRP recovery I compiled for the new bootloader, so here you go.
    Personally I prefer TWRP over CWM, but that's for everybody to choose on their own.
    We got official TWRP support for the Optimus 2x - but only for the old bootloader. You can use the GooManager app to flash the recovery (see below).

    I adapted and compiled TWRP for the new bootloader and tested it for quite a while without a single problem.
    Additionally I added a flashable zip recovery installer for the old bootloader if someone prefers that over the use of GooManager.

    TWRP is NOT my work, but the work from TeamWin under the lead of Dees_Troy.
    If you like TWRP you can donate to TeamWin here: http://www.teamw.in/project/twrp2



    Bugs?:

    If you have any issues grab a log, it's really easy: Advanced -> Copy Log to SD. It will copy the log to your external sdcard.
    You can post it in here, then I'll review it and forward it to Dees_Troy if it contains an error.
    Or contact TWRP directly via their contact form: http://www.teamw.in/contact

    I'm not interested in any complaints or bug reports that do not contain a log! Seriously, just don't.
    Remember: I'm compiling this for my personal use and am sharing it with you. I don't care if you use it or not, you're free to use CWM or whatever other recovery is out there.​






    Installation:

    These files are flashable zips, just flash them with your current recovery.

    If you want to flash the recovery manually, extract the img files from the zips, push it to the SDCard, open the Terminal Emularot and type:

    old bootloader:
    Code:
    su
    dd if=/sdcard/openrecovery-twrp-oldbl-p990.img of=/dev/block/mmcblk0p7

    new bootloader:
    Code:
    su
    dd if=/sdcard/recovery-TWRP-newbl.img of=/dev/block/mmcblk0p8


    Team Win Recovery Project 2.3, 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:



    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.

    CHANGELOG for 2.5.0.0:
    Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!

    -Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
    -Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
    -Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
    -Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
    -Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
    -Fixed a problem with md5 verification of backups
    -Added a search function to libtar (thanks to kokotas)
    -Improve handling of XML errors (fix permissions)
    -Fixed handling of subpartitions
    -Improvements to recovery.fstab flags
    -Fixed a problem with decryption not being able to locate the decryption key in some situations

    CHANGELOG for 2.4.4.0:
    -Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
    -More fixes for the file selector
    -Switched from using busybox md5sum to a direct C function call
    -Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
    -Update exFAT to latest commits
    -Added a build flag to disable using the ioctl for screen blanking

    CHANGELOG for 2.4.3.0:
    -Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
    NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
    -Added a scroll bar to file selectors and listboxes courtesy of Tassadar
    -Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
    -Added a screen dim effect 2 seconds before screen off on some devices
    -Finally fixed file selector crash (one of the joys of working with multi-threaded software)
    -Fixed loading of screen timeout setting during startup
    -Improvements and bugfixes to screen timeout code
    -Fixed persistence of the 24 hour / military time setting

    CHANGELOG for 2.4.2.0:
    -Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
    -Add a brightness setting (requires device specific setup and only some devices have been added)
    -Add a root checker and offer to install SuperSU if the device isn't already rooted
    -Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
    -Check and offer to fix root permissions if broken
    -Add an option for a 24 hour clock display instead of AM/PM (aka military time)
    -Move stock recovery reflash check to occur during the reboot cycle
    -Add support for some MTK6xxx devices
    -Change libtar to vfork to help prevent memory problems
    -Add a "clicked" effect to most buttons, file selector, and listbox
    -Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
    -Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
    -Other minor bugfixes and improvements

    CHANGELOG for 2.4.1.0:
    -Fixed a problem with mkdosfs that formatted sdcards to 2GB
    -Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
    -Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
    -Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)

    CHANGELOG for 2.4.0.0:
    -Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
    -Support for exFAT formatted sdcards (also thanks to bigbiff)
    -Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
    -Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
    -Added wipe cache and dalvik after ADB Sideload
    -Replaced many system calls with their native C counterparts
    -Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
    -Fixed AOSP recovery commands to run after decryption on encrypted devices
    -Improvements for building TWRP in CM10.1
    -Other minor bugfixes and improvements
    NOTE: 2.4.0.0 is, as always, still compatible with your older backups!

    DOWNLOAD:
    The fastest and easiest way to install TWRP [tonyp note: for the old bootloader version!] 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.
    43
    TWRP does support a great theme engine, see here: http://www.teamw.in/project/twrp2themers
    If you know of nice themes for our HDPI (480x800) device or created your own please post them here :)


    Personally I'd love to get the Holo Theme by thecoby xdhpi theme to get ported to our hdpi device:
    http://forum.xda-developers.com/showthread.php?t=1942309
    I don't have time to do that at the moment, so I'm posting it here if someone is interested in doing it.
    If not I'll do it once I find the time.


    Thanks to aldyu we do have the Holo Dark Theme now fully functional for our device! :)
    Check out his post here and don't forget to press thanks!

    Installation:
    Download the theme, rename it to ui.zip, create the folder /TWRP/theme at the internal SDCard and put the zip into it.

    Preview:
    7x3951exvdy4qoyqg6dn.png
    29
    TWRP 2.6.0.0

    I've just compiled and uploaded TWRP v2.6.0.0.
    And as always I created the flashable zip installer for the oldbl.
    Download is up at basketbuild.

    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.
    24
    I updated the OP with a bugs section and instructions how to flash the recovery manually (instead of using the flashable zips).

    Oh and I'll compile a new TWRP v2.5.0.0 in the coming days, whenever I get some free time.
    21
    TWRP 2.5.0.0

    Okay, I just compiled TWRP v2.5.0.0 for the newbl and zipped the flashable zip installer for the oldbl.

    Download and changelog in the OP.

    Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!