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][d2vzw] 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.

Awesome Work!

Team Win is a pretty fitting name. :good:

Beats the hell out of ClockworkMod.

Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970

Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app

** instructions **
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Things to know:
1. Backup files are accessible through >data>media>TWRP, even though they are on your internal SD card.
2. Zip files you want to flash are also accessible through >data>media, if you first move them to the root of your internal SD card before booting into recovery.
Pj
Phoenix, AZ

For anyone that is having problems backing up to EXTERNAL SD Card please take a look at this: Link
Took me a while to figure out why my 64GB MicroSD wasn't being detected by any recovery and several apps couldn't detect it.

ChuckFarley said:
Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!

pdinphx said:
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Pj
Phoenix, AZ
Click to expand...
Click to collapse
Sorry, but do you need to already be rooted to do this?

d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Of course.

mds96 said:
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!
Click to expand...
Click to collapse
Yup, working great! Nice easy install, too.
Sent from my SCH-I535 using xda app-developers app

jmacko said:
Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970
Click to expand...
Click to collapse
I have the same situation with the time and date, but otherwise appears to be working perfectly. I posted the question on their github site to see if something needs to be done.

d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Is the bug where the backup dates showing 1970 still exist? Something still seems weird regarding the date/time according to the poster above.

I've been able to backup with this recovery, but I have not tried to restore a backup.
Also, I have not been able to flash any zips, as the recovery doesn't allow me to explore either my internal or external sd cards.
What am I doing wrong?
Pj
Phoenix, AZ

will this work for all the other carriers as well? the original TWRP file that birdman posted on rootz he said that it should. i know this is changed but wonder if that still holds true.
would it work with sprint?

Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.

zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Thanks for confirming restore functionality.
Sent from my SCH-I535 using xda premium

zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Where did you put the zip so that this recovery could find it?
Pj
Phoenix, AZ

so you just root, then load goo manager and let goo manager load the recovery right?

[RECOVERY] TWRP 2.8.7.0 touch recovery for KFireHD 7" (ZIP) [06-24 v2.8.7.0]

[ THIS POST IS TEAMWIN'S STOCK TWRP POSTING. USE OF THE WORDS "US" AND "OURS" MEANS "DEES_TROY AND TEAMWIN" NOT HASHCODE ]
*** ALL CREDIT FOR TWRP BELONGS TO DEES_TROY AND TEAMWIN. ***
They do a BANG UP job on making a fantastic customizable touch-based recovery.
SEE BOTTOM OF THIS POST FOR DOWNLOAD / INSTALL INSTRUCTIONS
Donate to TeamWin:
http://www.teamw.in/project/twrp2
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
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.
Tablet look:
CHANGELOG for 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
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.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-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)
CHANGELOG for 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
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-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
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-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
** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **
DOWNLOAD:
[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE.
IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]
You can download a flashable recovery zip and place in your SDCARD area on the device:
ON THE FOLLOWING DEV-HOST LINK
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Mirror 1 : Download recovery zip from Dev-Host
INSTALL INSTRUCTIONS:
While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)
Select "Install"
Navigate to where you placed the file on your device
Select the .zip filename
Swipe to confirm flash
Reboot
KNOWN ISSUES:
[07/08] Disabled the screen blank due to a display issue where screen doesn't come back on well.
BUGS:
First: I'd read through this thread and see if your issue isn't answered.
Second: Try googling for it
Third: If it seems like a Kindle Fire HD issue, then post in the thread.
Lastly: If you have found a bug, please consider posting it to TeamWin's 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 #kindlefire-dev or #twrp on Freenode with your IRC client or just click this link.

error
im ending up with this error when i try to flash

Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?

Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.

Hashcode said:
Can you check the md5sum on that file and make sure it matches 4056520ee7b13be01d42d785cca2b15e?
Click to expand...
Click to collapse
the md5 does match
tried it again and this time it worked thanks hashcode

seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.

Hashcode said:
Yes, I can probably do a .zip update. I'll need a night or 2. Been pretty busy.
Click to expand...
Click to collapse
and how is the kernel goings man?, good job with this

Re: [RECOVERY] TWRP 2.4.4.0 touch recovery for KFireHD 7" [2013-04-02]
seokhun said:
Hashcode, could you please make a flashable .zip file to flash in TWRP? Is this even possible? I'm not well-versed in fastboot and adb stuff (installed your 2nd-bootloader using fireflash). Thanks in advance, you're doing a phenomenal job with the software work on the 8.9, and I'll be waiting patiently for CM10.1 on the 7!
I own a Galaxy S3, and I know that when running ClockworkMod, I can flash to the Touch version's .zip from CWM itself, so I know at least flashing a newer recovery within a recovery is doable, and then simply rebooting recovery through the Advanced submenu.
Click to expand...
Click to collapse
Hey you can install the new version through fireflash also I just did with no problem
Sent from my KFTT using xda premium

As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.

seokhun said:
I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
+1
Sent from my KFHD using xda premium

I promise u it works will post a video of proof by about 12 tonight if everyone would do this and leave hash code alone about petty crap maybe we would have cm 10.1 and custom kernel by :screwy:
Sent from my LG-E970 using xda premium

Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app

mrkhigh said:
Respectfully disagree,
If people start bricking their devices because of unnecessary flashes, the threads will be overwhelmed with people griping and begging for help...
Personally I am waiting for cm10 as well and have not even installed recovery yet on my device due to this..
But I do understand that twrp allows a proper backup and honestly is something all android devices should have installed
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.

Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
:good:+1

Jester6 said:
Unnecessary flashes? I don't see how having a custom recovery is unnecessary if you want to install any kind of custom rom, if you want to install CM10 when/if it's ready for prime time you're going to have to have TWRP installed anyway so why wait? If you brick by simply flashing a zip made for the device in question and have at the least a rudimentary understanding of the system then you clearly did something else wrong somewhere along the line. In conclusion updates are not unnecessary, quite the opposite in some cases.
Click to expand...
Click to collapse
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app

jailuis said:
You got wrong what he said. The user above stated that we're wasting hashcode's time by making him do zip updates for twrp (instead of flashing them), and he (the one you quoted) added that is better to update twrp with ZIPs since its less risky.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Either way, it makes little to no sense. I understand that hashcode has a lot on his plate but update zips are a simple enough process and take a small amount of time/work, now I don't know that about twrp as its not officially supported (to my knowledge) but an update zip for a ROM is a very easy process, I'm sure there's a bit involved in making twrp work for the kfhd but I don't imagine its crazy.

Thank You Hashcode for your efforts. An update zip would be sweet. Keep up the great work!
This is a Kinology HD using XDA Premium

video with instructions and proof of concept
seokhun said:
As in, plugging in the .img recovery file Hashcode provided, leave everything else blank and just flash? Are you sure? Seems a little risky to me. If someone else can verify that, I'll do it, but I'm willing to wait for Hashcode's .zip, no offense.
Click to expand...
Click to collapse
yes that's correct i need no one else to verify this but there's a video on my channel here>http://www.youtube.com/user/choppedncut79cutlass/videos <as for the rest of these space wasting comments i reply in the morn nite all work in the morning

So I got brave and decided to work with fastboot, and I can flash with the standard platform-tools procedure. I know I have fastboot using Hashcode's "getvar product" command, and booted into fastboot successfully. However, I don't know how to flash using the "fastboot -i 0x1949" command. Do I first CD to the folder that the file is placed in? A little help for a noob will be greatly appreciated, Hashcode, or anyone else well-versed in fastboot. Thank you!
I'd also like to know if the standard procedure will also work here. In other words, if I place the file in \platform-tools and ran the "fastboot flash <filename>.img", would it work? I'm afraid it would fail because of the Kindle's locked bootloader and how we're working with a 2nd one. Sorry, I'm very new to this whole bootloader thing and willing to learn.

Where ever fastboot is, I think.
This is a Kinology HD using XDA Premium

[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]

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:
-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!
CHANGELOG for 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
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.
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.

DOWNLOADS:
twrp-3.0.2-0-shieldtablet.img Android M (Nvidia version 4.x) devices ONLY.
twrp-3.0.0-0-shieldtablet.img Android M (Nvidia version 4.x) devices ONLY.
twrp-2.8.7.1-shieldtablet.img Android L (Nvidia version 3.x) devices ONLY.
ISSUES:
Touchscreen sometimes doesn't work, to fix it just wait 10-20 seconds and it will catch up. I can't tell if this is a TWRP issue or input driver issue.
ZIPs that check what model of the device they are installing on might not work. You can remove the check manually from the update script to work around this. (Any recent one should work, though.)

well, it loads.....
but it is upside down , and touchscreen doesnt work - like the others

minieod said:
well, it loads.....
but it is upside down , and touchscreen doesnt work - like the others
Click to expand...
Click to collapse
I can fix rotated screen just need someone to join me on hangouts

I will be forever grateful once this gets to full functionality. Mines upside down as well. Tbh though I prefer it this way. Not sure what Nvidia was thinking then they made the charger port on the top of the device and not the bottom.
You guys are doin' a great job at bringing these recoveries and ROMS to the SHIELD.

abnormaIity said:
I will be forever grateful once this gets to full functionality. Mines upside down as well. Tbh though I prefer it this way. Not sure what Nvidia was thinking then they made the charger port on the top of the device and not the bottom.
You guys are doin' a great job at bringing these recoveries and ROMS to the SHIELD.
Click to expand...
Click to collapse
Yes, I was focusing on attracting someone who could help. As before they do offer USB mouse and keyboard (I believe) support and I'm sure many people have those. Let me know if you want to help get this going

Unjustified Dev said:
I can fix rotated screen just need someone to join me on hangouts
Click to expand...
Click to collapse
The flag for screens mounted backwards?
Sent from my OtterX using Tapatalk

joshuabg said:
The flag for screens mounted backwards?
Sent from my OtterX using Tapatalk
Click to expand...
Click to collapse
Only works on twrp the same code on other recoveries makes it layout wrong graphics are stretched to one side of the device. You can look at team regular on twrp branch.

Unjustified, your are the man. I will try this out as soon as I get my replacement. (I was told on Sunday that the new units were almost here) I will be buying you devs a beer or two soon.

markymark567 said:
Unjustified, your are the man. I will try this out as soon as I get my replacement. (I was told on Sunday that the new units were almost here) I will be buying you devs a beer or two soon.
Click to expand...
Click to collapse
i'd suggest to read the rest of the thread

minieod said:
i'd suggest to read the rest of the thread
Click to expand...
Click to collapse
Uh yeah you mean read the other 8 posts?? Not sure what the hell your trying to accomplish with that post but you've made yourself look like an idiot in my eyes.

markymark567 said:
Uh yeah you mean read the other 8 posts?? Not sure what the hell your trying to accomplish with that post but you've made yourself look like an idiot in my eyes.
Click to expand...
Click to collapse
i was pointing out that if you try this build when you get your new device, that it will not work, it will be upside down and non-responsive to touch
why are you acting like a child here and calling me an idiot? please grow up. you also mention other 8 posts, but there are only 5 between my first post, and your first post. read between the lines.

minieod said:
i was pointing out that if you try this build when you get your new device, that it will not work, it will be upside down and non-responsive to touch
why are you acting like a child here and calling me an idiot? please grow up
Click to expand...
Click to collapse
Your really think I didn't realize that? Its the only thing being discussed in this thread (all 10 posts ?). I just try to make it a point to thank developers ESPECIALLY for devices like this with smaller communities. I've seen devs terminate all their work because no one appreciated it. I realize that it's a work in progress and I plan to help debug when I get a device that I can unlock.

Will take a look into this in a week or two, busy times just now but very interested in getting this device
Edit: it looks like touchscreen on TWRP may never work on this tablet, I have spend some time on it and it isnt looking good

Has anyone who has tested this? Know if this recovery is fully functioning??

wrong post ;0

If there's ever gonna be a version for WiFi+LTE Shield, I'm more than willing to test it, device incoming tomorrow.

Hope development continues because I'm planning on getting the 32GB LTE version.

no v2.8.1.0 for SHIELD?

*$M3RT$* said:
no v2.8.1.0 for SHIELD?
Click to expand...
Click to collapse
I don't plan on compiling anything until they release new kernel source.

[RECOVERY][OFFICIAL] TWRP for HTC One Dual SIM (802W, 802D and 802T variants)

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:
-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!
CHANGELOG for 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)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
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.
DOWNLOAD:
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 NEW website!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be 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 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.

Reserved

This is great! Whenever i plugin my charger once my battery drained, unlike before, it doesnt boot to recovery with unresposive touch anymore.. good job @bgcngm!
Sent from mobile

Thanks for the feedback.
By the way, you can use TWRP Materialised theme, to get an even nicer UI.

@bgcngm This is great job! Thank you.
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
EDIT:
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?

J_M_V_S said:
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
Click to expand...
Click to collapse
I think so, should be possible to preserve /data/preload during a factory reset. I can't try right now because my phone is *again* at the repair center for camera replacement.
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?
Click to expand...
Click to collapse
SD-Ext is if you have your SDcard partitioned with an EXT2/3/4 partition. I think that is not so used anymore.

TWRP v2.8.4.0 is out.

TWRP v2.8.5.0 is out.

Do you have any mirror? I cannot download from homepage. Always stuck at 99.99%

No, I don't. That's the official link to the website. Try again later if server is down / overloaded.

TWRP v2.8.6.0 is out.

Help
bgcngm said:
TWRP v2.8.6.0 is out.
Click to expand...
Click to collapse
Hi, thanks for the TWRP but do you have the stock recovery file for HTC One M7 802dwg? I want to revert back to stock recovery to get the OTA updates which i'm not being able too install by TWRP or CWM. I'm on Hboot 2.49, Bootloader unlocked, Rooted, S-On, M7 802dwg.
Thanks in advance.

If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.

Any help??
angusc said:
If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.
Click to expand...
Click to collapse
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??

[email protected] said:
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??
Click to expand...
Click to collapse
I have the same problem, plz help, i stuck in bootloop on HTC one 802d

sekilo004 said:
I have the same problem, plz help, i stuck in bootloop on HTC one 802d
Click to expand...
Click to collapse
For now restore from a nandroid or TWRP backup...and update upto 4.4.3 unless there is a copy of the lollipop stock recovery.

Could you guys stop spamming this thread with off-topic? If you didn't yet realize, this thread is related to TWRP only. You have already been told how to get the stock recovery.

sorry for my bad english and still noob,..
I flashed twrp-2.8.7.0-m7cdwg.img for my HTC m7 802d..
after booting on twrp, I'm looking on system/lib/modules, but not found. there is only BIN folder
anyone suggest or modify twrp to make it possible that directory, system/lib/modules are avalible on twrp?
thank in advance

What exactly are you trying to do? Maybe you have to mount system first...