Database Info

[RECOVERY][skyrocket] TWRP 3.1.0-0 touch recovery [2017-03-10]

[RECOVERY][skyrocket] TWRP 3.1.1-0 touch recovery [2017-05-19]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 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.
CHANGELOG for 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
CHANGELOG for 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!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
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.

will try, thanks!

I missed twrp from my evo days
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I had a chance to work with Dees_Troy on this. It's easily the best recovery ever made. The touch interface is second to none.
Sent from my Skyrocket

It won't flash on top of CWM 5.0.2.7 because the assert will fail. If the board checked for MSM8660_SURF, I think it would work on both hercules and skyrocket.
Edit: this will flash on top of CWM 5.0.2.7. I'm not sure about 5.8.1.3 touch or 5.5.0.4 touch. Removed for now.

cant find it in goomanager

romracer said:
It won't flash on top of CWM 5.0.2.7 because the assert will fail. If the board checked for MSM8660_SURF, I think it would work on both hercules and skyrocket.
Edit: this will flash on top of CWM 5.0.2.7. I'm not sure about 5.8.1.3 touch or 5.5.0.4 touch.
Click to expand...
Click to collapse
Zip updated to MSM8660_SURF.

tjsooley said:
cant find it in goomanager
Click to expand...
Click to collapse
Same here

just search for twrp and download the skyrocket zip

You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA

iandr0idos said:
You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Four... 5.5.0.4 touch, 5.8.1.3 touch, 5.0.2.7 original and now this one. I've not used TWRP before but it seems pretty nice from the poking I've done so far.

iandr0idos said:
You've got to be kidding me... we have THREE different recoveries now! O.O
This would have been simply absurd from the old Aria days...
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yeah, but the other 3 recoveries lack WIN! >_>

I've never considered the two touch recoveries to be different recoveries... but okay.
I did a successful backup and restore. So at least that is working.
Sent from my SAMSUNG-SGH-I727 using XDA

romracer said:
Four... 5.5.0.4 touch, 5.8.1.3 touch, 5.0.2.7 original and now this one. I've not used TWRP before but it seems pretty nice from the poking I've done so far.
Click to expand...
Click to collapse
Five if you count 5.0.2.6 separate from 5.0.2.7. So, will TWRP eliminate the need to do multiple wipes/clears/partition formats now? (since our current recoveries were T989 based).

DoctorQMM said:
Five if you count 5.0.2.6 separate from 5.0.2.7. So, will TWRP eliminate the need to do multiple wipes/clears/partition formats now? (since our current recoveries were T989 based).
Click to expand...
Click to collapse
That would be great!

Everything works great except i can't browse the sdcard. When i click emmc it goes to the internal and when i click sdcard it goes to internal. Anyone else having this issue?

Use the mount menu to change from internal to external.

Thanks,trying now

Dees_Troy said:
Zip updated to MSM8660_SURF.
Click to expand...
Click to collapse
you updated the file and placed it in the "stingray" folder, not skyrocket. im sure all the people with xooms are confused by that as well....

Thanks that fixed it. Im so used to cwm, but this is way better!

[RECOVERY][ONE-X/EVITA] TWRP 2.5.0.0 Touch Recovery! [2013-4-9]

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.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.1:
-Added USB OTG support
-Updated kernel from HTC (may result in short lag when rebooting out of recovery and a color shift when using aroma)
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!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
CHANGELOG for 2.3.2.0:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
CHANGELOG for 2.3.1.0:
-Unmount system after boot to prevent some status 7 symlink failed errors on zip install
-USB Mass Storage code improvements
-Better handling of mounting storage during boot for some devices
-Fixed a problem with sizes of images (boot & recovery) after resetting defaults
-Fixed size errors during backup for some devices on recovery, etc.
-Fixed a problem with restoring backups when multiple archives were present
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
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!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 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 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.
XDA:DevDB Information
[RECOVERY][ONE-X/EVITA] TWRP 2.5.0.0 Touch Recovery! [2013-4-9], a Tool/Utility for the HTC One S
Contributors
eyeballer, dees_troy, bigbiff
Version Information
Status: Testing
Created 2013-09-16
Last Updated 2013-09-16

do stuffs here one day

This is awesome thank you.sucks that it won't restore cwm backups through.because I have three back ups of different roms
sent from a guy living in a van down by the river

WoW, this looks so ugly But working rly fine so far. I like it.
good work guys!
cheers

Midian666 said:
WoW, this looks so ugly But working rly fine so far. I like it.
good work guys!
cheers
Click to expand...
Click to collapse
Haha good thing its themable
sent from a guy living in a van down by the river

Will Aroma Installer work with this recovery?
Sent from my HTC VLE_U using Tapatalk 2

Pretty awesome change from cwm, I like it. Going to install on my gtablet tonight.
Sent from my HTC VLE_U using xda premium

Mathato said:
Will Aroma Installer work with this recovery?
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
Does not work

Dimson75 said:
Does not work
Click to expand...
Click to collapse
That's a deal breaker for me
sent from a guy living in a van down by the river

Yepp i really like that recovery, but without aroma support. No thanks!

Since none of us in TeamWin actually own this device we need logs to help debug issues you may hit.
If you find a bug or other error, do not just post saying "X doesn't work" - please pull a recovery.log and pastebin it along with what you were trying to do. If the device has usb/adb working, then "adb pull /tmp/recovery.log" alternatively, go to the Advanced menu and copy log to sdcard.

v2.1.7 is live, with working adb.
We need some logs from aroma installs..
EDIT: scratch that, pulled the downloads for a second to fix an issue.
EDIT2: DL link is back up, please test adb

Great work! I used TWRP on my HP TouchPad so far and really loved it. Was hoping you guys would have a One S version out soon -- thanks!!!

Development is booming now.
I missed TWRP had it on my Amaze.

So has anyone had issues with Aroma & this recovery ??
Dont suppose the Mount USB Storage option works either does it ??
My phones in the repair centre, So cant test........And before you all ask, Its not bricked Just a faulty antenna

Incredible work guys! Toast has been a part of every phone I've had since my Hero, glad that can now continue....
Edit: I've always had problems getting CM9/AOKP to run on my device. I installed this, flashed AOKP and it booted first try without a problem.....NICE! Don't know what the difference would be with CWM, but there is something.

eyeballer said:
v2.1.7 is live, with working adb.
We need some logs from aroma installs..
EDIT: scratch that, pulled the downloads for a second to fix an issue.
EDIT2: DL link is back up, please test adb
Click to expand...
Click to collapse
Thanks it worked with the Aroma instaler

Tried restoring a backup it looked like all went well till after boot. Got a "Process system is not responding" error and it freezes with no touch input.
Here is a logcat hopefully just before error shows.
http://pastebin.com/embed_js.php?i=aBCGSF3C
Edit: I don't think it's restoring the boot.img. I had it checked to back up, but coming from AOKP to a sense nandroid it wouldn't boot all the way until I reflashed the sense Kernel. Just FYI, thanks for this!

So does this backup and restore boot.img like cwm does kind of a big deal for us s-on people
sent from a guy living in a van down by the river

I should have made a follow up post, sorry. It is working well. I only had problems with my first rom that I restored with CWM then backed up with TWRP. Haven't had a problem since with roms I flashed with TWRP.

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

[RECOVERY] [4/5/16] TWRP 3.0.2-0 - TeamWin Recovery Project
TeamWin is proud to present TWRP 3.0.2-0 for the Samsung Galaxy Tab Pro 8.4/10.1/12.2!
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.
mondrianwifiue Device Config: TBD
Kernel: TBD
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

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-2
Add F2FS back to samsung kernel
TWRP 3.0.0-1
Fixed MTP
TWRP 3.0.0-0
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.1
v2wifixx-
Use new kernel for booting properly on v2wifxx device
mondrianwifiue -
add f2fs to TWRP
mondrianlte -
add f2fs to TWRP
vienaltexx -
Fix brightness path
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.2
picassowifi
- fix build
2.8.1.1
mondrian3g
- Revert changes to exfat-fuse to fix writing to external sdcard as exfat
mondrianwifiue - 12/9/2014
- Revert changes to exfat-fuse to fix writing to external sdcard as exfat
picassowifi
- add encryption support
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.1
mondrianwifiue only
- Disable Secure Erase to increase wiping speed
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.1
v2wifixx only
- fix contexts restore of backups
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.1
picassowifi
Fix ramdisk for booting
2.7.0.1
mondrianwifiue and mondrianwifilte
Add Qcom time fix
2.7.0.1
Galaxy Tab Pro 8.4:
Update theme thanks to nrage123 and Gunthermic to proper 1600x2560 (will submit to gerrit)
Update system splitting to fix issues with symlinks being counted as the target
Update size to not show /data/media for /data parition
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.

bigbiff said:
reserved
Click to expand...
Click to collapse
reserved

this is so awesome. finally. can we flash with flashily or is there a way without a computer. I'm not near one. stock recovery doesn't seem to flash zips. been awhile since i did it without a computer. donate will be sent. did i say how awesome this is lol. forget it. flashed the img file with flashify. works perfect. screen isn't full size but i think i read that you were aware of that. thanks again.

You might want to have the site admins fix the typo if you can: "Samsung Galaxy Tab Pro 8.1" should say 8.4. Kind of confused me at first.

The Theme is from a device that is 1200 x 1980. Ours is 1600 x 2560. I got a theme almost done but ran into issues I could not fix. The themes are pretty complicated for a xml noob like me. Bigbiff does not have the time to make one which I can tell you takes a lot of work. Hopefully someone with some xml talent will take up the cause. I asked a couple of TWRP themers from other devices but they are all busy with other things. Also this is the only device thus far with this portrait resolution. I tried to flash the zip file but that failed. The Odin method works perfectly.

nrage23 said:
The Theme is from a device that is 1200 x 1980. Ours is 1600 x 2560. I got a theme almost done but ran into issues I could not fix. The themes are pretty complicated for a xml noob like me. Bigbiff does not have the time to make one which I can tell you takes a lot of work. Hopefully someone with some xml talent will take up the cause. I asked a couple of TWRP themers from other devices but they are all busy with other things. Also this is the only device thus far with this portrait resolution. I tried to flash the zip file but that failed. The Odin method works perfectly.
Click to expand...
Click to collapse
Thanks for posting, saves me from posting it.
I am unable to do the theme because I don't have any devices with a higher resolution then 1080p. We mostly need the keyboard xml layout done so that the keyboard object knows the pixels to look at when a key on the image being rendered is pressed. Please PM me if you would like to help.
nrage23: did you flash 2.7 odin img and it worked, but the zip didn't?

bigbiff said:
Thanks for posting, saves me from posting it.
I am unable to do the theme because I don't have any devices with a higher resolution then 1080p. We mostly need the keyboard xml layout done so that the keyboard object knows the pixels to look at when a key on the image being rendered is pressed. Please PM me if you would like to help.
nrage23: did you flash 2.7 odin img and it worked, but the zip didn't?
Click to expand...
Click to collapse
I tried flashing the zip in the 2.6 build you had done and it said failed after trying to flash. So I booted to DL mode and Odin version worked just fine.

nrage23 said:
I tried flashing the zip in the 2.6 build you had done and it said failed after trying to flash. So I booted to DL mode and Odin version worked just fine.
Click to expand...
Click to collapse
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar

bigbiff said:
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar
Click to expand...
Click to collapse
Sorry it was the 2.7 .zip file I flashed via recovery that did not work and then I used Odin to get 2.7 .tar to work properly.

nrage23 said:
Sorry it was the 2.7 .zip file I flashed via recovery that did not work and then I used Odin to get 2.7 .tar to work properly.
Click to expand...
Click to collapse
I need to create an zip file for it tonight.

<deleted don't want borks on non 8.4 gtabpro> Also can you guys get me build.prop for the 10.1/12.2?
Thanks!

bigbiff said:
If you guys are willing you should be able to boot this on the other Galaxy tab pros. Also can you guys get me build.prop for the 10.1/12.2?
Thanks!
Click to expand...
Click to collapse
The others are all Exynos 5 based like the Note 10.1 2014 you made. The 8.4 is Qualcomm.

bigbiff said:
If you guys are willing you should be able to boot this on the other Galaxy tab pros. Also can you guys get me build.prop for the 10.1/12.2?
Thanks!
Click to expand...
Click to collapse
Build.prop from my rooted 10.1 is attached.
Not sure if I have the nerve to be the first to Odin the 8.4 recovery onto my 10.1.

smalis said:
Build.prop from my rooted 10.1 is attached.
Not sure if I have the nerve to be the first to Odin the 8.4 recovery onto my 10.1.
Click to expand...
Click to collapse
Do not do so. It is very different hardware.

crpalmer said:
Do not do so. It is very different hardware.
Click to expand...
Click to collapse
Thanks very much, I will wait.

nrage23 said:
The others are all Exynos 5 based like the Note 10.1 2014 you made. The 8.4 is Qualcomm.
Click to expand...
Click to collapse
Bah guess I should of looked Edited post above about trying to boot. I will download the exynos kernel and rebuild for 12.2 and 10.1.

bigbiff said:
Can you try the 2.7 files? If anyone has issues please use http://techerrata.com/bigbiff/mondrianwifue-recovery.img.tar
Click to expand...
Click to collapse
Okay that link I flash gives me 2.6.3.2.
I have tried flashing the one from TWRP site and it doesnt' flash it.
Might I make a small suggestion to in OP write instructions to flash/odin it..

Gunthermic said:
Okay that link I flash gives me 2.6.3.2.
I have tried flashing the one from TWRP site and it doesnt' flash it.
Might I make a small suggestion to in OP write instructions to flash/odin it..
Click to expand...
Click to collapse
We have flashing instructions for each device on the website. Which file did you flash that didn't work. The zip is broken, but people here say the tar works.

bigbiff said:
We have flashing instructions for each device on the website. Which file did you flash that didn't work. The zip is broken, but people here say the tar works.
Click to expand...
Click to collapse
odin openrecovery-twrp-2.7.0.0-mondrianwifiue.img.tar
Edit: After odin'ing 2.6.3 and doing 2.7 again it now shows.
1. Why does it only take 3/4 of screen?
2. What does the tab report that (in first screen) the recovery is not selinux enforcing?

[RECOVERY][GT-I9105/P] TWRP 2.8.1.0 touch recovery [OFFICIAL]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.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
CHANGELOG for 2.8.0.2:
-Removed reboot download button (it wasn't working)
-Fixed double "Data" partitions
-Factory reset now is not formatting internal sdcard
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 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
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. 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
CHANGELOG for 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.
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
DOWNLOAD:
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
Sources:
- Device tree for s2ve
- Device tree for s2vep
- Kernel for s2ve & s2vep

Nice. Can i restore my backups what i made with cooldevs twrp if i use this version?
Sent from my GT-I9105P using XDA Premium 4 mobile app

rs tony said:
Nice. Can i restore my backups what i made with cooldevs twrp if i use this version?
Sent from my GT-I9105P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think you can

LuK1337 said:
I think you can
Click to expand...
Click to collapse
Yes, It works! Thanks!
Sent from my GT-I9105P using XDA Premium 4 mobile app

:deleted:

Hi
Thanks!
(Stupid)Questions:
Are CWM backups compatible?
Which filesystems get repaired?
Do flashable aroma filemanage work?
I flashed CWM by Odin; is it re-flashabel by TWRP (with some zip package)?

Publiuss said:
Hi
Thanks!
(Stupid)Questions:
Are CWM backups compatible?
Which filesystems get repaired?
Do flashable aroma filemanage work?
I flashed CWM by Odin; is it re-flashabel by TWRP (with some zip package)?
Click to expand...
Click to collapse
1. Probably no
2. EXT2-4, F2FS, FAT, exFAT
3. Yes
4. You can flash zip via CWM

Uploaded new TWRP with USB OTG support.

Hi,
On v2.7.1.0 I can't mount the SD on my PC (windows) ! ( using the build from the 08.08 )
when I reboot to android - I got no problem mounting the SD externally. ( MTP)

gps3dx said:
Hi,
On v2.7.1.0 I can't mount the SD on my PC (windows) ! ( using the build from the 08.08 )
when I reboot to android - I got no problem mounting the SD externally. ( MTP)
Click to expand...
Click to collapse
Yeah I know that but I don't have idea how to fix it.

TWRP 2.7.1.0 working nicely on my gf's 9105p!
Thanks for your support of this device LuK!

USB storage
USB storage doesnt work on Windows 8.1. Solution?

skljsklj1 said:
USB storage doesnt work on Windows 8.1. Solution?
Click to expand...
Click to collapse
No solution, it simply doesn't work.

Uploaded new build for s2ve & s2vep.

Twrp is same for all devices?

anastasiszn said:
Twrp is same for all devices?
Click to expand...
Click to collapse
No. But u can use s2ve's recovery on s2vep.

why does the filename say 4.2.2 recovery? can it be used with a 4.4.4 ROM?
I'm using CM11 M9 which is 4.4.4.
also, can I use it to change the file system to f2fs, since the next snapshot of CM11 might natively support it?
the description isn't very clear on that.

karamancho said:
why does the filename say 4.2.2 recovery? can it be used with a 4.4.4 ROM?
I'm using CM11 M9 which is 4.4.4.
also, can I use it to change the file system to f2fs, since the next snapshot of CM11 might natively support it?
the description isn't very clear on that.
Click to expand...
Click to collapse
There's 4.2.2 in name cuz it's for 4.2.2 bootloader. You can use f2fs now, just install TWRP and convert rom using my tool.

Thanks for the new build!

So TWRP is now officially supported and has fixed MTP. Actually TWRP Manager doesn't work for s2ve/p I need to contact author.

[RECOVERY][PYRAMID] TWRP 2.8.1.0 touch recovery

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its 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.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
CHANGELOG for 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
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 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. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. 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
CHANGELOG for 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.
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
DOWNLOAD:
1. Download recovery from [removed]
2. Flash recovery:
a) Using Flashify app
b) Using Fastboot ( fastboot flash recovery recovery_2.8.1.0.img )
3. Done
Sources:
- Device tree
- Kernel
XDA:DevDB Information
[RECOVERY][PYRAMID] TWRP 2.8.1.0 touch recovery, Tool/Utility for the HTC Sensation
Contributors
LuK1337
Version Information
Status: Stable
Current Stable Version: 2.8.1.0
Stable Release Date: 2014-11-01
Created 2014-11-01
Last Updated 2014-11-01

Does the power off charging works in this version for Pyramid?

01 Vlatce said:
Does the power off charging works in this version for Pyramid?
Click to expand...
Click to collapse
I don't have my own pyramid, can u test it for me?

LuK1337 said:
I don't have my own pyramid, can u test it for me?
Click to expand...
Click to collapse
I'd love to try it, but the last twrp we had on sensation caused a hard brick for a lot of users including me, so I actually fear to try it

Dead system partitions bug
Does this bug had been solved since TWRP 2.7.1.0 that made shantur?
Anyone tried this?

Sajito said:
I'd love to try it, but the last twrp we had on sensation caused a hard brick for a lot of users including me, so I actually fear to try it
Click to expand...
Click to collapse
Really? I didn't known that.
My 2 friends are using my recoveries since 3 months and no brick.

Hard brick bug
Guys, bug is still there. Do not use TWRP, use 4ext instead
Wiping partitions causes breaking partitions and thats all. (data partition wipes more than 5 minutes and than any partition cant mount)
J_Livingston from 4pda tryed this one and got brick :/

Daniiiik49 said:
Guys, bug is still there. Do not use TWRP, use 4ext instead
Wiping partitions causes breaking partitions and thats all. (data partition wipes more than 5 minutes and than any partition cant mount)
J_Livingston from 4pda tryed this one and got brick :/
Click to expand...
Click to collapse
Ok, so I removed down link.

LuK1337 said:
Really? I didn't known that.
My 2 friends are using my recoveries since 3 months and no brick.
Click to expand...
Click to collapse
While TWRP 2.7 was latest we had a twrp version by shantur and one by dexter93. While with that problem never occured, in shanturs build there was a problem that while wiping it burks the emmc chip for some reason.
Might be kernel related, but I don't know for sure.
I'd like to use twrp though, since I think it's much better than 4ext, plus it supports f2fs

Sajito said:
While TWRP 2.7 was latest we had a twrp version by shantur and one by dexter93. While with that problem never occured, in shanturs build there was a problem that while wiping it burks the emmc chip for some reason.
Might be kernel related, but I don't know for sure.
I'd like to use twrp though, since I think it's much better than 4ext, plus it supports f2fs
Click to expand...
Click to collapse
Maybe BOARD_SUPPRESS_EMMC_WIPE := true will fix it or smth.

LuK1337 said:
Maybe BOARD_SUPPRESS_EMMC_WIPE := true will fix it or smth.
Click to expand...
Click to collapse
Maybe, but since it causes a hard brick it's hard to test. If that's not the fix, there might be some more bricks.

Is anyone here who has an old htc sensation and wants to try twrp with the flag mentioned by luk1337, but always with the risk it might not be the fix for the issue?