[TOOL/UTILITY][TWRP][3.0][RECOVERY] TWRP 3.0.2-0 TeamWin Recovery Project 4/5

Search This thread

Helios909

Senior Member
Jan 12, 2011
104
24
I don't know if anyone else is having these issues, but with 2.7.1.0 I have tried flashing the ZIP, and downloading the TAR with ODIN and as soon as this is flashed, I get a continuous bootloop and cannot even get into recovery. With 2.7.0.0 both the ZIP and the TAR work and I can boot into recovery, but TWRP doesn't function properly - it can't restore as it seems to reboot TWRP, it can't wipe data as it does the same thing, and it fails installing ZIPs. The only thing it can do is MAKE a backup. For now I have gone back to 2.6.0.0 and 2.5.0.0 and to install newer 4.4.3+ ROMs I flash CWM. Anyone have a solution to this? I tried someone's suggestion to flash the stock samsung recovery and do a wipe/reset with it, and then put TWRP back on - but it had no effect.
 

Helios909

Senior Member
Jan 12, 2011
104
24
I don't know if anyone else is having these issues, but with 2.7.1.0 I have tried flashing the ZIP, and downloading the TAR with ODIN and as soon as this is flashed, I get a continuous bootloop and cannot even get into recovery. With 2.7.0.0 both the ZIP and the TAR work and I can boot into recovery, but TWRP doesn't function properly - it can't restore as it seems to reboot TWRP, it can't wipe data as it does the same thing, and it fails installing ZIPs. The only thing it can do is MAKE a backup. For now I have gone back to 2.6.0.0 and 2.5.0.0 and to install newer 4.4.3+ ROMs I flash CWM. Anyone have a solution to this? I tried someone's suggestion to flash the stock samsung recovery and do a wipe/reset with it, and then put TWRP back on - but it had no effect.

Just to note, I installed gimmeitorilltell's version of 2.7.1.0 and it works perfectly. Guess he's got it figured out.
 
You mind testing an official version for me? He has limited time for testing.







I don't know if anyone else is having these issues, but with 2.7.1.0 I have tried flashing the ZIP, and downloading the TAR with ODIN and as soon as this is flashed, I get a continuous bootloop and cannot even get into recovery. With 2.7.0.0 both the ZIP and the TAR work and I can boot into recovery, but TWRP doesn't function properly - it can't restore as it seems to reboot TWRP, it can't wipe data as it does the same thing, and it fails installing ZIPs. The only thing it can do is MAKE a backup. For now I have gone back to 2.6.0.0 and 2.5.0.0 and to install newer 4.4.3+ ROMs I flash CWM. Anyone have a solution to this? I tried someone's suggestion to flash the stock samsung recovery and do a wipe/reset with it, and then put TWRP back on - but it had no effect.







Just not part of the official build process.
Finally tried. I received the same results as Helios909 with a boot loop. (Panicking) :eek: . Flashed working recovery via Odin :sly:. Reflashed gimmeitorilltell's version 2.7.0.0. :D



Sent from my SAMSUNG-SGH-I717
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,245
Finally tried. I received the same results as Helios909 with a boot loop. (Panicking) :eek: . Flashed working recovery via Odin :sly:. Reflashed gimmeitorilltell's version 2.7.0.0. :D



Sent from my SAMSUNG-SGH-I717

Yes, I still would need to make the test build for you to try...
 

skyungjae

Senior Member
Dec 5, 2006
304
24
California
2.7 & 2.8 have been giving me boot loop issues regardless of install method.

Edit: I flashed 2.6 via Odin and zip installed gimmeitorilltell's 2.8, and it works fine.

Hmmm... I'm curious what's causing my issue.
 
Last edited:

youngunix

Senior Member
Jun 6, 2012
118
37
everywhere
goo.gl
Okay, it seems that everyone (myself included) is having issues with TWRP causing infinite boot-loops.
ISSUE = "caused the boot-loop"
First, flashed TWRP 2.8.0.0 using TWRP 2.7.0.0, $ISSUE.
Second, used odin to flash CWM then flashed TWRP 2.8.0.0, $ISSUE.
Third, did the same thing but this time I flashed TWRP 2.7.1.0, $ISSUE.
Fourth, flashed both TWRP 2.7.1.0 & 2.8.0.0 using Odin, $ISSUE.

I don't know exactly what's the problem with the latest TWRP but hope it gets fixed.
 

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,245
Okay, it seems that everyone (myself included) is having issues with TWRP causing infinite boot-loops.
ISSUE = "caused the boot-loop"
First, flashed TWRP 2.8.0.0 using TWRP 2.7.0.0, $ISSUE.
Second, used odin to flash CWM then flashed TWRP 2.8.0.0, $ISSUE.
Third, did the same thing but this time I flashed TWRP 2.7.1.0, $ISSUE.
Fourth, flashed both TWRP 2.7.1.0 & 2.8.0.0 using Odin, $ISSUE.

I don't know exactly what's the problem with the latest TWRP but hope it gets fixed.

You will have to use the unofficial until (or if ever) we get the updates from @gimmeitorilltell into the teamwin codebase.
 

egandt

Senior Member
Mar 25, 2008
444
151
Verbose debugging and logging, how do I enable something like this

I'm encountering many-many issues flashing zips, for instance nothing happens, I'm sure that TWRP is hung somewhere, but I need a way to see what is happening, how do I enable verbose logging so that I can attempt to debug what is going wrong with the flash. In one case the flash of a 233meg zip (which tested fine) took 20+ minutes until I was forced to hard reset the phone, at which point System was corrupted as a result. Normally the first thing I'd do is enable verbose debugging and monitor what is happening, but after a number of Google searches I can not locate any way to enable such logging.

Thanks,
ERIC
 
I'm encountering many-many issues flashing zips, for instance nothing happens, I'm sure that TWRP is hung somewhere, but I need a way to see what is happening, how do I enable verbose logging so that I can attempt to debug what is going wrong with the flash. In one case the flash of a 233meg zip (which tested fine) took 20+ minutes until I was forced to hard reset the phone, at which point System was corrupted as a result. Normally the first thing I'd do is enable verbose debugging and monitor what is happening, but after a number of Google searches I can not locate any way to enable such logging.

Thanks,
ERIC

Did you read the above posts. This is official TWRP. This does not work at present on quincyatt devices. It says to use gimmeitorilltell's version. If you indeed understood that and used that version then you are reporting your problems in the wrong forum thread. Just pointing this out because most people having problems are using the wrong versions of recovery not realizing there are different builds available. Just search for unofficial twrp quincyatt.

Sent from my SAMSUNG-SGH-I717
 
Last edited:

bigbiff

Senior Recognized Developer
Jun 8, 2010
6,964
7,245
I'm encountering many-many issues flashing zips, for instance nothing happens, I'm sure that TWRP is hung somewhere, but I need a way to see what is happening, how do I enable verbose logging so that I can attempt to debug what is going wrong with the flash. In one case the flash of a 233meg zip (which tested fine) took 20+ minutes until I was forced to hard reset the phone, at which point System was corrupted as a result. Normally the first thing I'd do is enable verbose debugging and monitor what is happening, but after a number of Google searches I can not locate any way to enable such logging.

Thanks,
ERIC

adb pull /tmp/recovery.log in TWRP
 

Top Liked Posts

  • There are no posts matching your filters.
  • 94
    [RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project

    TeamWin is proud to present TWRP 3.0.2-0 for the Galaxy Note (ATT)!



    Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo

    Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2

    Introduction:

    Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.

    Key Features:

    Touchscreen driven with real buttons and drag-to-scroll
    XML-based GUI that allows full customization of the layout true theming!
    Settings are saved to the sdcard and persist through reboots
    Ability to choose which partitions to back up and which to restore
    Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
    Onscreen keyboard
    Decryption of /data
    Easy selection of internal/external storage
    See changelog below for new features

    In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.

    We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

    Source Code:

    GitHub - https://github.com/omnirom/android_bootable_recovery

    Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me

    Gerrit Instance - http://gerrit.omnirom.org

    If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.

    quincyatt Device Config: https://github.com/TeamWin/android_device_samsung_quincyatt

    Kernel: https://github.com/bigbiff/i717-GB-Kernel

    DOWNLOAD:

    All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.

    http://twrp.me


    Support:

    Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
    20
    Changelog

    3.0.2-0
    - Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
    - Add Greek translation to some builds.

    3.0.1-0

    -support new CM 13.0 pattern encryption (sultanqasim)
    -fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
    -libtar updated to latest upstream and fixes (jcadduono)
    -fixes for loading custom themes (_that)
    -TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
    -translation updates - added Italian, Czech and Polish and significant updates to Dutch
    -progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
    -fix input box text display (Dees_Troy)
    -reboot option after zip install complete (bigbiff)
    -other mostly invisible bug fixes and improvements

    TWRP 3.0.0-0 is out now for all currently supported devices.

    What’s new in 3.0.0-0:

    Completely new theme - Much more modern and much nicer looking (by z31s1g)
    True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    SuperSU prompt will no longer display if a Marshmallow ROM is installed
    Update exfat, exfat fuse, dosfstools (by mdmower)
    Update AOSP base to 6.0
    A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    You can track the progress of builds here

    Head over to the devices page to find install instructions and download links.
    TWRP 3.0.0-0 is out now for all currently supported devices.

    What’s new in 3.0.0-0:

    Completely new theme - Much more modern and much nicer looking (by z31s1g)
    True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    SuperSU prompt will no longer display if a Marshmallow ROM is installed
    Update exfat, exfat fuse, dosfstools (by mdmower)
    Update AOSP base to 6.0
    A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    You can track the progress of builds here

    Head over to the devices page to find install instructions and download links.
    2.8.7.0

    - Initial ground work for software drawn keyboard (_that)
    - Fix handling of wiping internal storage on datamedia devices (xuefer)
    - Allow DataManager to set and read values from the system properties (xuefer)
    - Fix crash when taking screenshots on arm64 devices (xuefer)
    - Fix error message after an ORS script completes (Dees_Troy)
    - Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
    - Add system read only option - more details below (Dees_Troy)
    - Add resize2fs and GUI option to run resize2fs (Dees_Troy)
    - Fix crash loop caused by empty lines in AOSP recovery command file (_that)
    - Prevent duplicate page overlays such as multiple lock screens (mdmower)

    System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

    resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

    This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.


    2.8.6.0

    - Allow mulitple overlays for popup boxes (Dees_Troy)
    - Add pattern style password entry for decrypt (Tassadar)
    - Keyboard improvements (_that)
    - Update AOSP base to 5.1 (Dees_Troy)
    - Reduce theme count to 5 and rely on scaling (Dees_Troy)
    - Various scaling improvements (Dees_Troy)
    - Improved handling of resources in the GUI (_that)
    - Make scroll bar size proportional to list size (_that)
    - Allow scoll lists to render without a header (_that)
    - Make console scroll per pixel with kinetic scrolling (_that)
    - Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
    - Various other fixes and improvements (mdmower, bigbiff, codelover, etc)

    2.8.5.0
    - Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
    - Improve thread handling and move input handling into the main rendering thread to improve stability
    - Make MTP work even if unplugged and plugged back in
    - Unify scrollable list code and make kinetic scrolling feel more natural
    - Fix handling of mapped zip files for OTA updates (CM12 updater)
    - USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
    - Add Cancel Backup capability
    - Other small fixes and improvements

    2.8.4.0
    - MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    - Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
    - Fix some MTP related crashes and bugs
    - Eliminate TWRP toggling USB IDs during boot if MTP is enabled
    - Fix various adb sideload issues
    - Improve threading of actions
    - Eliminate separate thread for screen timeout
    - Update libblkid to 2.25.0
    - Use power button as back button on watch themes for easier navigation
    - Add mutex locking to data manager
    - Improve custom theme handling on encrypted devices
    - Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens

    2.8.3.0

    - MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    - MTP will now tell the host PC that storage is removed instead of disabling MTP completely
    - MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
    - Update and improve fix permissions and make fixing contexts optional
    - Update SuperSU in TWRP to 2.40 and update install process
    - Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
    - Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
    - Fix kernel panic during MTP start on some devices
    - Support unicode fonts on devices with True Type Font support
    - Fix slider value not showing sometimes (vibration settings page)
    - Toggle MTP off during adb sideload to set correct USB IDs
    - Reduce library requirements for 5.0 L decrypt
    - Other minor fixes and improvements

    2.8.1.0
    - MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
    - TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
    - Temperature support - thanks to bigbiff
    - Various other bugfixes and tweaks

    2.8.0.0
    - Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
    - Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
    - Add support for color in the console and give error, warning, and highlight lines different colors
    - Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
    - Improve handling of /misc thanks to mdmower
    - Improve setting of time on Qualcomm devices thanks to [NUT]
    - Allow using images on slidervalue GUI objects thanks to Tassadar
    - Allow using variables and addition and subtraction in variables for easier theming
    - Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
    - Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
    - Other minor fixes and improvements

    2.7.1.0
    - Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
    - Various bugfixes to backup and restore
    - Improvements to USB storage handling
    - Added a class to search for files to make finding the correct brightness file automatic in most cases
    - Various other bugfixes and tweaks

    2.7.0.0:
    -Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
    -Allow sideloading from /tmp on encrypted devices
    -Check for a crypto footer before asking for a password to prevent user confusion
    -Additional checks for validity to auto generated backup names
    -Text wrap in the console output
    -Proper caps lock support in the keyboard
    -Mouse support via USB OTG for devices with a broken digitizer
    -Improve scanning of storage locations for OpenRecoveryScript
    -Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
    -Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
    -Update SuperSU to 1.93 and improve installation process
    -Added selinux contexts restoration to fix permissions
    -Load RTC offset on Qualcomm devices to fix the date/time in recovery
    -USB Mass Storage fixes Add SELinux support checking
    -Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
    -Add 4.4 decrypt support
    -Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
    -Various SELinux fixes and bug fixes

    Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.

    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

    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

    2.6.0.1
    Fix showing data twice in advanced wipe

    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.

    2.5.0.0
    Fixed Device Configs for booting TWRP
    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
    Fixed a problem with directory permissions on split archive backups
    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

    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

    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
    Fix Military Time setting persisting

    2.4.2.1
    Fix screen timeout by adding correct brightness config file to BoardConfig.mk

    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

    2.3.3.0
    Added better handling of wiping on /data/media devices with Android 4.2 to help prevent multiple upgrades of the file system for multiple users
    NOTE: It is not recommended to jump back and forth between 4.1 and 4.2 ROMs. If you do, this may trigger additional upgrades and you will have to manually move your files back to the "single user" layout when going back to 4.1.

    Fixed renaming of backups when a space is present
    Added decrypt button to mount page if you cancel decryption during boot
    Added ignore blkid flag support
    Fixed handling of MTD partitions during mount
    Fixed some keyboard mapping issues on 800x1280 layout

    2.3.2.3
    Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see http://teamw.in/androidmultiuser)
    Fixed a bug with deleting a backup with a space in the name
    Added highlights on keyboard key presses
    Updates to Fix Permissions

    10/18/12

    Fixed keyboard segfault
    Handle single LUN file for USB Storage
    Handle mounting of slow sdcards
    Update USB Mount Code to be more Efficient

    10/13/2012
    Many, many updates. See https://github.com/TeamWin/Team-Win-Recovery-Project/commits/jb-wip/ for detailed commits.

    8/25/2012
    Device ID Sanitization - doesn't affect the note
    1920x1200 theme - not for note
    320x480 theme - not for note
    /data/media issues for other devices fixed - not for note
    Fix keyboard issues for 800x1280 and small ui tweaks
    Fix some mount error messages
    SD-EXT Improvements
    Unmount before formatting (if mounted)
    Fix Umask for JB builds (this version is still built in CM9/ICS)
    Change initial logging fo TWRP startup (include version field)
    Kinetic Scrolling improvements

    7/17/2012
    Fixed backup duplicate name checking
    Added checking to see if boot is 0 size and remove from backup menu
    Fixed a bug with android secure backup using ORS
    Fixed a bug with backup naming when using ORS and backup name is
    Slight tweaks to 800x1280 layout

    7/12/2012
    New release 2.2. See OP for details on changelog. Please leave any feedback in the thread.

    6/14/2012
    Added the ability to backup /efs when backing up and restoring. It will tar the files instead of using dd so the filesystem isn't formatted.

    6/11/2012
    Fixed dual mount for USB. You will now see your internal and external sdcards as Windows drives in recovery!
    Fixed md5 checking parsing filenames with apostrophes.
    Added reboot to download mode in Reboot page
    New support for updater-binary included in TWRP. (Don't currently implement this for the SGH-I717
    If no OS installed, reboot buttons won't show. Fixes bricking in some devices but doesn't seem to affect SGH-I717.
    Added support for partitions greater than 2 GBs.

    5/23/2012
    Updated ui.xml to make bigger console space
    Worked with Dees_Troy to get flash zip in place working. Are ROMs were getting to big and were being copied to /tmp. With the ROMs and RADIOs we overwhelmed recovery. Now your ROM should flash with no issues because we are extracting from storage now.
    Dees_Troy fixed a graphics bug which the recovery was still doing work but the GUI said successful.
    Update is at teamw.in or goo manager.

    5/11/2012
    Fixed ui.xml to fix Mount Page for external and internal sdcards
    Updated filename on TWRP device page to have proper version in filename
    Updated img for GooManager to have proper version in filename
    13
    FAQ

    Q. How do I see/use/change between internal and external SDCARD?

    A. Please use the Mount page to change between using internal and external. Click Using internal sdcard will allow you to use your internal sdcard to install ROMs. Click Using external sdcard will allow you to use your external sdcard to install ROMs. Please dont use the file browser to find the mounts as this is done for you automatically when you change options and navigate back to the Install page.

    To be clear this works as follows:
    1. internal emmc sdcard mounted on /emmc
    2. external sdcard mounted on /sdcard
    3. You can choose what storage you want to use on most screens by selecting "Use external SD" or "Use internal storage"
    4. Otherwise you can browse to the appropriate directories

    Q. Are TWRP backups compatible with CWM and vice versa?
    A. You cannot flash a CWM backup in TWRP and vice versa. Please flash appropriate recovery to restore your backup. You can restore the backup, flash back to your wanted recovery, then make a backup in that recovery for later use.

    Q. Can I have TWRP and CWM installed at the same time?
    A. There is only one recovery partition that can hold a specific version of recovery. CWM, TWRP2, and Samsung 3e are able to be flashed to recovery, but none can coexist.

    Q. Does USB mounting work in recovery?
    A. Sorry haven't updated this. It works with internal and external sdcard.

    Q. Where is the "Delete battery stats opton?"
    A. We removed this option in 2.1. Please see https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT as reference.

    Q. Installing Roms
    A.All ROMs should be able to be installed.

    Please post in this thread if you have any issues flashing.

    Q. How does MD5 checking work?
    A.To create a md5 for a rom perform the following steps:
    1. Open a terminal emulator or use adb and cd to the directory your file is located.
    2. Execute busybox md5sum rom.zip > rom.zip.md5 where rom.zip is the file you want to create a md5 for. Make sure that the md5 file has the same prefix as your original file with md5 appended with a period.
    3. Check force checking of md5 in Settings in TWRP or after the Install file selector page to check the md5.

    Q. I can't name my backups.
    A. Make sure to hit enter on the keyboard and not the back button to accept the name.

    Q. What's next?
    A. Fixing bugs.
    10
    For those of you wondering, 2.5.0.0 does not have the screen timeout issue that affected some people. The new timeout is pretty slick actually.

    Thanks to ClosedEyesSeeing for testing all day on IRC! Without his help you wouldn't have this update.
    8
    TWRP 2.3 is hot off the presses. Let me know if you see any issues because we have had a major code rewrite into C++.