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.

DOWNLOADS
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:
TWRP for Infinix Hot 2

Credits
@MSF Jarvis
@Nonta72
@Dees_troy
@jcadduono

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.

XDA:DevDB Information
[OFFICIAL][TWRP][d5110] TeamWin Touch Recovery, Tool/Utility for the OEM Cross Device Development

Contributors
HostZero, MSF Jarvis, Dees_troy
Source Code: https://github.com/TeamWin/android_device_infinix_d5110

Version Information
Status: Stable

Created 2016-06-09
Last Updated 2016-06-08

Sent from my GT-I9500 using XDA-Developers mobile app

For everyone who has lost his ThreemaID because of damaged phone, here is my solution.
All you need is an old TWRP/Nandroid backup that contains the data partition of your phone (you should have installed Threema before you backed up the data :p ) and a software like 7Zip (on Windows) or tar (on Linux).

1. Copy the TWRP/Nandroid files to your computer. On my XPeriaZ5 they are named from data.ext4.win000 to data.ext4.win006. These files are normal ".tar.gz" files. Rename them to data.ext4.win000.tgz … data.ext4.win006.tgz.
2. Use 7Zip or tar to browse the archive and navigate to "/data/data/ch.threema.app/files/".
3. Inside this directory, you will find a file named "idbackup.txt".
4. Extract and open this file. It contains your ThreemaID in plain text format.
5. Start Threema on your new (unrooted) phone and tell Threema to restore your ID from text.
6. Enter the long code you found in idbackup.txt (you will be asked for your password)
7. Feel happy

Pls help me

I disabled accidently google app service in my lg g2 with cyanogenmod 13 and I got a bootloop now.:(

I am pretty sure that the reason of this is exactly disabled google app. (not google play service).

I have access to TWRP but how could I re-enable it from TWRP/ file manager? Maybe all what is needed is just edit one single file ?

Thanks

CHANGELOGS :

[B]TWRP 3.0.2.0
E670 Recovery

How to install ? :

1. Extract The Zip File
2. Open Extracted folder and hold shift and right click and select "Open command window here"
3. Then connect your device to the System and make sure you have USB debugging enabled.
4. Type "adb devices" to check if the device is connected.
5. You will get a prompt in your device asking permission to allow USB debugging just click OK and allow.
6. Type "adb devices" again to see if ur device is connected or not and if its connected it will show something like this:

6. Make sure recovery.img is in the same adb and fastboot folder
7. Type "adb reboot bootloader" to boot into fastboot mode.
8. Use this command to flash the recovery:

You will get something like this:

9. Boot into the system by using this command:
"fastboot reboot"

10. To boot into TWRP using adb use this command:
"adb reboot recovery"

11. If you wanna use hardware button combination :

a. Power Off your device
b. Press and hold volume UP + Power button till you see the PHICOMM Bootlogo and leave power button while keep holding the volume UP button till you boot into TWRP.
12. Download SuperSU.zip and flash it on TWRP to root your device
Sources
– android_device_phicomm_e670-android-5.1

Bugs ?
– MTP doesn’t work

I have merged the latest CM-13.0 ROM with my Omni Google Pixel C Tree. Compiled with 5.1 Omni Sources

Quick Credits:
@ggow – for 3.10.x kernel

I am not going to reveal the device tree, because of safety reasons.

Pleas Test this Recovery. If its working, i will make it official by taking to senior twrp developers.

twrp-3.0.2-0-dragon.img

XDA:DevDB Information
[TWRP][dragon] TWRP 3.0.X Testing – Need help of Pixel C people, Tool/Utility for the Google Pixel C

Contributors
HostZero

Version Information
Status: Testing

Created 2016-06-09
Last Updated 2016-06-09

Thanks!

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.

DOWNLOADS
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:
TWRP for Redmi Note 3 MTK

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

XDA:DevDB Information
[OFFICIAL][TWRP][hennessy] TWRP for Redmi Note 3 – MTK, Tool/Utility for the Xiaomi Redmi Note 3

Contributors
HostZero, jcadduono, Dees_troy, MSF Jarvis

Version Information
Status: Stable

Created 2016-06-10
Last Updated 2016-06-10

All I wanted to do was to install CM12.1 ROM on my Note 3 Exynos. I was on stock Lollipop 5.0., rooted.

To start I had installed TWRP Recovery Manager from Google Play Store according to the instruction on the first page of the CM12.1 ROM thread. Then opening the app it asks me to install BusyBox (which I hit OK but nothing seems to be happening). Then on the very first screen I selected my phone model, then below I hit Install Recovery, which it did and report it was successful. Then it asks if I wanted to boot into recovery and I hit yes, and since then I have been stuck in a bootloop.

So I’m sure that I messed something up, but I’m not sure how to get out. I have searched through the forums and see multiple ways but I’m afraid to do anything in fear that I might damage the device any further. I am aware that one of the best solution is to flash the device back to stock ROM, however I have some data on this device that I want to keep, if that is possible.

Thank you very much for you help.

i need to flash a twrp or cwm based recovery on amigoo R300 with Lollipop 5.1. Can someone make a custom recovery for me?

The orignal recovery is stored on

https://mega.nz/#!vJkAXQRZ!7MgA5ryog…sU8x0L06sw0dz0

thnaks

Last night I installed Apps2sd. When I first opened the app it mentioned that my SD card was not setup and I would need to run some "sd fix". I accepted, the phone rebooted and then when it came back up, its as if my SD card was blank. Not only blank, but after connecting phone to the PC, both my phone and card show but are empty. The SD card displays as -1376256 bytes free of -1376256 bytes. The phone shows 127mb free of 128mb.

I also made the mistake of uninstalled apps2sd after my phone booted up and I noticed the issue. Wasnt very smart of me as I can not seem to install it or anything back. Most apps including google play just crash when trying to load. When vieiwng files under My Files, basically everything is empty. If I try using FX file manager then most things say I dont have access.

Now when I first turn on phone and I boot into safestrap TWRP, I can go through and view files and I See all my stuff on my SD card and phone. I can even copy files from my SD card and place them in other directories (tried to copy the apps2sd apk onto phone to reinstall) but just cant ever see any of it when the phone is booted.
Also under TWRP, If I go to backup or anything for example, It lists Micro SD as 2132mb and Internal Storage as 3436mb. So im guessing apps2sd created a partition of some sort?

What have I done? What did my stupid ass do and is there any way to fix it?

tl;dr: Installed apps2sd, clicked things I shouldnt click. Cant view any files on phone or when connected to USB but can see everything under TWRP.

Any and all help is greatly appreciated!!

Last night I installed Apps2sd. When I first opened the app it mentioned that my SD card was not setup and I would need to run some "sd fix". I accepted, the phone rebooted and then when it came back up, its as if my SD card was blank. Not only blank, but after connecting phone to the PC, both my phone and card show but are empty. The SD card displays as -1376256 bytes free of -1376256 bytes. The phone shows 127mb free of 128mb.

I also made the mistake of uninstalled apps2sd after my phone booted up and I noticed the issue. Wasnt very smart of me as I can not seem to install it or anything back. Most apps including google play just crash when trying to load. When vieiwng files under My Files, basically everything is empty. If I try using FX file manager then most things say I dont have access.

Now when I first turn on phone and I boot into safestrap TWRP, I can go through and view files and I See all my stuff on my SD card and phone. I can even copy files from my SD card and place them in other directories (tried to copy the apps2sd apk onto phone to reinstall) but just cant ever see any of it when the phone is booted.
Also under TWRP, If I go to backup or anything for example, It lists Micro SD as 2132mb and Internal Storage as 3436mb. So im guessing apps2sd created a partition of some sort?

What have I done? What did my stupid ass do and is there any way to fix it?

tl;dr: Installed apps2sd, clicked things I shouldnt click. Cant view any files on phone or when connected to USB but can see everything under TWRP.

Any and all help is greatly appreciated!!