Database Develop

[RECOVERY][tomato] 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.

Device specific page with instructions for a manual install.
Download folder with current and past versions.

Please note: There is a slight flickering of the screen for 1-2 sec on recovery boot up, which is already noted. Do not the fill the thread with post regarding it. The performance of the recovery is nowhere affected by that. Thank you and enjoy

vishal_android freak said:
Please note: There is a slight flickering of the screen for 1-2 sec on recovery boot up, which is already noted. Do not the fill the thread with post regarding it. The performance of the recovery is nowhere affected by that. Thank you and enjoy
Click to expand...
Click to collapse
Plus the backup year being 1970 shouldn't be part of the spam

@Dees_Troy : after few use, flashing process becomes so slow, some times error comes about data partition.
will come soon with logs..

@Dees_Troy : plz update or fix this recovery..
we cant wipe data / factory reset..
after factory reset, we get error that cant mount data.
then after reboot, data is as it is..
also flashing, backing up, wiping cache, wiping system etc are very slow.
plz fix this/.

2.8.5.0 flashable zip : https://www.androidfilehost.com/?fid=95916177934528156
---------- Post added at 03:50 PM ---------- Previous post was at 03:29 PM ----------
@Dees_Troy : still same problem with latest version, even I wipe data / factory reset, it does nothing, after reboot, we can get as it is system with all apps.
can anyone plz confirm this ?
.
.
edit : solved by using rm-rf instead of format in settings.

RohanAJoshi said:
2.8.5.0 flashable zip : https://www.androidfilehost.com/?fid=95916177934528156
---------- Post added at 03:50 PM ---------- Previous post was at 03:29 PM ----------
@Dees_Troy : still same problem with latest version, even I wipe data / factory reset, it does nothing, after reboot, we can get as it is system with all apps.
can anyone plz confirm this ?
.
.
edit : solved by using rm-rf instead of format in settings.
Click to expand...
Click to collapse
hi did all the problem in the previous version are solved the latest version of TWRP
---------- Post added at 09:55 AM ---------- Previous post was at 09:45 AM ----------
the slight flickering of the screen for 1-2 sec on recovery boot up did not solved in the latest version of twrp-2.8.5.0

@Dees_Troy
Though we appreciate the work done by @Santhosh M, is it safe to assume that soon official 2.8.7.0 (or 2.8.6.x) supports YU Yureka on Lollipop bootloader?
:good:

yup requesting official twrp arm64 build thanks in advance

Twrp is not working even in KK ROM. Any one tested twrp in latest yureka phones. i have tested two phones. i just got black screen, only CWM works

Where is the link to 2.8.7?
@Dees_Troy
where is the download link for TWRP 2.8.7.0 for Yu Yureka?
https://dl.twrp.me/tomato/
this link shows 2.8.6.0

Dees_Troy said:
Device specific page with instructions for a manual install.
Download folder with current and past versions.
Click to expand...
Click to collapse
Version 2.8.7.0 is no were to be shown
And finally meeting u for first time
Thanks fr the recoveries for all cel i used
Sent from my AO5510 using Tapatalk

@Dees_Troy looks like the jenkins builds are failing. There is no download there.

Still no download link:banghead:

@Dees_Troy....
MechaDroid said:
....where is the download link for TWRP 2.8.7.0 for Yu Yureka?...
Click to expand...
Click to collapse
jesuinodsa said:
Version 2.8.7.0....
Click to expand...
Click to collapse
abeyhere said:
....the jenkins builds are failing. There is no download there.
Click to expand...
Click to collapse
gulabsameer said:
Still no download link...
Click to expand...
Click to collapse

One Question, I have backed-up my device using CWM recovery will i be able to restore using TWRP if i i flash this recovery

srtsjs said:
One Question, I have backed-up my device using CWM recovery will i be able to restore using TWRP if i i flash this recovery
Click to expand...
Click to collapse
no

FYI, stable TWRP v2.8.7.0 built by @vishal_android freak is here: Mod EDIT, link pointed to site that needs registration
Applicable for both Yureka & Yureka Plus.

Cannot Find the download link in this post for TWRP v3.0.2 tomato. Please Help.

[RECOVERY] [F2FS/exFAT/NTFS] [UNOFFICIAL] TWRP 3.1.0-0 [tomato] [20170311]

[RECOVERY] [F2FS/exFAT/NTFS] [UNOFFICIAL] TWRP 3.1.0-0 [tomato] [20170311]
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.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 (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
DOWNLOADS: twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot -i 0x1ebf flash recovery twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.1.0-0-20170311-UNOFFICIAL-tomato.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod
@h2o64 [for base twrp tree]
@HridayHS [for instant help]
ashishrocks, anupamdmoran, Vams, Abhiram Shibu, vjs pranav & Mr. Wolverine [for testing all older builds].
XDA:DevDB Information
[RECOVERY] [F2FS/exFAT/NTFS] [UNOFFICIAL] TWRP 3.1.0-0 [tomato] [20170311], Tool/Utility for the YU Yureka
Contributors
darshan1205
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: twrp-3.1.0-0-2017031
Stable Release Date: 2017-03-11
Created 2016-06-15
Last Updated 2017-03-11

SOURCES:
Device Tree
Kernel Source
SCREENSHOTS:

reserved

whats the difference between unofficial and official?????

gourabpa said:
whats the difference between unofficial and official?????
Click to expand...
Click to collapse
I built it before official but didn't posted on XDA ...
Sent from my Mi 4i using Tapatalk

darshan1205 said:
I built it before official but didn't posted on XDA ...
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
ok thanks for ur hard work......
but bro don't feel me wrong.......if the official TWRP is released then everyone known all will download the official build only......
but if u add some new/extra features....in this UnOfficial build.......then almost everyone will download.....ur build....u can understand what i am telling....

gourabpa said:
ok thanks for ur hard work......
but bro don't feel me wrong.......if the official TWRP is released then everyone known all will download the official build only......
but if u add some new/extra features....in this UnOfficial build.......then almost everyone will download.....ur build....u can understand what i am telling....
Click to expand...
Click to collapse
Official one doesn't detects SD card which is formatted as internal but this recovery detects it ....[a user said this on YU Forums]
Sent from my Mi 4i using Tapatalk

darshan1205 said:
Official one doesn't detects SD card which is formatted as internal but this recovery detects it ....[a user said this on YU Forums]
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
Using Official build in my Yureka plus model it shows the SD Card when its formated properly as Internal.....i think that user properly not formated his SD Card thats why the problem appears......

gourabpa said:
Using Official build in my Yureka plus model it shows the SD Card when its formated properly as Internal.....i think that user properly not formated his SD Card thats why the problem appears......
Click to expand...
Click to collapse
Keep using it [emoji106]
Sent from my Mi 4i using Tapatalk

darshan1205 said:
Keep using it [emoji106]
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
by the way thanks for ur hard work..........

Dear Darshan Can you try to get OmniRom on yuyureka

TWRP Updated to v3.0.3-0
Download Link: https://www.androidfilehost.com/?fid=529152257862692928

any bugs so far?

darshan1205 said:
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.
DOWNLOADS: twrp-3.0.3-0-20160604-UNOFFICIAL-tomato.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot -i 0x1ebf flash recovery twrp-3.0.3-0-20170104-UNOFFICIAL-tomato.img
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp-3.0.3-0-20170104-UNOFFICIAL-tomato.img > Select it & Swipe to Flash
CREDITS:
TeamWin
CyanogenMod
@h2o64 [for base twrp tree]
@HridayHS [for instant help]
ashishrocks, anupamdmoran, Vams, Abhiram Shibu, vjs pranav & Mr. Wolverine [for testing all older builds].
XDA:DevDB Information
[RECOVERY][F2FS][UNOFFICIAL] TWRP 3.0.3-0 for YUREKA/YUREKA PLUS [tomato] [20170104], Tool/Utility for the YU Yureka
Contributors
darshan1205
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: twrp-3.0.3.0-2017060
Stable Release Date: 2017-01-04
Created 2016-06-15
Last Updated 2017-01-04
Click to expand...
Click to collapse
@darshan1205 TWRP is not detecting my internal memory. And while taking backup, it says "failed to mount /data (invalid argument)". What should I do to make my both internal & external memory to work?

BuntyS5 said:
@darshan1205 TWRP is not detecting my internal memory. And while taking backup, it says "failed to mount /data (invalid argument)". What should I do to make my both internal & external memory to work?
Click to expand...
Click to collapse
Take a backup on OTG drive or PC & wipe everything once
Sent from my YU5010 using Tapatalk

Again same error while formatting everything.
darshan1205 said:
Take a backup on OTG drive or PC & wipe everything once
Sent from my YU5010 using Tapatalk
Click to expand...
Click to collapse
Bro, Again I'm getting the same error while wiping data. It is showing mounting error in TWRP. What to do? Plz help. :crying:

New Build is up!
TWRP 3.1.0-0 for YUREKA/YUREKA PLUS
Device Specific Changelog:​
Added EFS backup option (requested by [email protected])
Added NTFS support [not tested] (requested by @nitesh9)
Added exFAT support [not tested] (requested by Abhiram Shibu)
TWRP Changelog:​
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 (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
Thanks to wolfie616 & [email protected] for testing.
Download Link: https://www.androidfilehost.com/?fid=529152257862709397​

There will be an update based on twrp changes twrp changes & kernel changes

Earlier was using the latest official recovery for my Yureka and was facing Error 7 issue. Now installed the latest 3.1.0.0 version from here and I am able to install the custom 7.1 Lineage RoM. @darshan1205 please update the TWRP here to the latest version if possible. Thanks for the work!!

[RECOVERY][kenzo/kate] TWRP 3.1.0-0 for Xiaomi Redmi Note 3

Team Win Recovery Project
This is a unified build for both the Redmi Note 3 (kenzo) and the Redmi Note 3 SE (kate)
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
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.
FEATURES:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
Built with android 7.1 tree
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Redmi Note 3, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-03-04
Last Updated 2017-03-21

FAQ:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar

Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?

i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it

fardeenah said:
i did a few benchmark on f2fs, but didnt notice a major difference on kenzo, is it really the case? or is F2Fs really worth it
Click to expand...
Click to collapse
With latest lineage os and Radeon kernel I get 89500 with Antutu. Changing to f2fs gets me 91500. 1 would say a 2000 Antutu increase is pretty impressive.

Antutu don't test disk-speed! So your 2000 extra points have another reason, maybe media-indexing at phone-start etc...ext4 is best filesystem for your phones because it is fast in ALL cases and rock solid!

D4xel said:
Is this TWRP able to flash official ROM and incremental OTA also without any workaround, like TWRP zcx does?
Click to expand...
Click to collapse
I'd like to know this as well, as i'm expecting a Kate device soon.

Thanks! It also prompt you to install the twrp app. Working well for now (Only flashed and wiped stuff)

Hey guys I converted data & cache from ext4 to f2fs (backup data>wipe dalvik+format cache f2fs+format data f2fs>restore data backup with rm-rf) and internal storage was wiped in the process. I don't remember wiping internal storage and can anyone help me check whether I was careless or it is a bug.

With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'

when i did clean wipe & give reboot to recovery phone start on system not going to recovery.
I have to press vol+ & power for 10 sec to go to recovery.
Please fix it.
Note: Its only happen while clean wipe.

So using f2fs is better than ext4?

gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Btw ext4 is compatible with more stuff as you might face issues flashing zips to f2fs partition (which I haven't faced yet).

jianwen03 said:
Lot's of devs say no. I can't feel the difference overall but opening Settings>Apps in f2fs is a whole lot faster than in ext4 for me.
Click to expand...
Click to collapse
Same

Awesome thanks for sharing

Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
'
Click to expand...
Click to collapse
The error probably arose due to this being a unified TWRP for Kenzo and Kate . Apparently, this TWRP is able to differentiate between Kenzo and Kate devices, and has assigned a specific flag to each identification. Thus , Kenzo is ID'd as a Kenzo , and Kate is ID'd as a Kate.
This is actually very bad news for Kate users. If you look around Note 3's ROM scene, every single custom ROM is named as a Kenzo release and is keyed for Kenzo. The only reason kate users were able to install these Roms was because they were using Kenzo TWRPs. Despite being Kate, the TWRP fooled the ROM into thinking it is Kenzo and then allowed the installation.
In every ROM and in some other zip installs, there's a file called updater.script. This file, actually the first lines of the file, is where the ROM performs its only device check.
So how does a Kate user bypass this ERROR 7? Well, there are many ways:
1. Change the two mentions of "Kenzo" on the first lines of the ROM 's updater.script to "Kate", then flash like before,
2. Or, urge the op to make a Kenzo-only TWRP, and flash.that,
3. Or beg the op to modify the TWRP to forgo this updater.sfript check.
Personally, I'd just stay away from Kate or Kenzo/Kate unified TWRPs. Changing update.script on every ROM you want to flash can become very tedious.
It's a lot easier being a fake Kenzo, then a real Kate.

gaurav1902 said:
So using f2fs is better than ext4?
Click to expand...
Click to collapse
I am using f2fs for 2 days now and it is definitely snappier when it comes to multitasking. On ext4, the recents button was a bit slow for me, pressing and showing up the recents sometimes took a good half second, was unsure if I even pressed it but then oh look it appeared. No such issue for f2fs, everything is happening as I'm pressing buttons.

Draygon said:
With the latest version, I'm not able to install kenzo custom roms to my kate phone.
Getting following error, tried different roms:
"This package is for device: kenzo; this device is kate.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/Nitrogen-OS-kenzo-20170304.zip'
Click to expand...
Click to collapse
Did you install Kate's TWRP or Kenzo's one?

@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
edit: found out that it might be a problem with latest AGNI kernel: I unbricked and reinstalled (CM13), and my problem seems to be reproducable with latest releases - radon works however..

schmanto said:
@TheStrix
System won't boot after changing from M4 recovery to this one..
but this time, I'm even unable to revert back to M4 -> system not booting, just mi logo > reboot
m4 recovery also wouldn't boot
so now I'm completely stuck (given my limited capabilities).
btw: I actually wasn't able to change to another recovery since I changed to f2fs on M4 (tried zcx, dad1, ... )
logs are here: https://drive.google.com/open?id=0B9NuN8yWvpeZQzFDVGF4UTREWnc
Click to expand...
Click to collapse
If you are able to boot into recovery, format partitions as ext4 and flash recovery of your choice.

[RECOVERY][sirius] TWRP 3.1.1-0 Touch Recovery [2017-07-23]

TWRP 3.1.1-0​
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.
Based on latest Omni, rcstar6696 and LineageOS sources.
CHANGELOG for 3.1.1-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)
Download:
TWRP-3.1.1-0
BUG REPORTING:
Please reply to this thread stating what is wrong and I will look into it. Bugs must be reproducible.
Logs:
To get logs there are two ways (if something is broken):
Code:
adb pull /cache/recovery/last_log
adb shell dmesg > dmesg.txt
Flashing:
Code:
fastboot flash recovery recovery.img
Source Code:
https://github.com/omnirom/
https://github.com/rcstar6696/
https://github.com/LineageOS/
https://github.com/Sony-Lineage-3.4/

Reserved

If this version of recovery suitable for official carbon rom ?

My Z2 has BU and Abricot v8.1 kernel (twrp 3.0.2 or something like that), so can I flash this twrp?
Thanks in advance dude

Adriano-A3 said:
My Z2 has BU and Abricot v8.1 kernel (twrp 3.0.2 or something like that), so can I flash this twrp?
Thanks in advance dude
Click to expand...
Click to collapse
I believe your device isn't D6503 is it?
If not you can try out.

aboodyaiman said:
I believe your device isn't D6503 is it?
If not you can try out.
Click to expand...
Click to collapse
D6543 (Brazilian model)
I'll try later and return with results

tayct said:
If this version of recovery suitable for official carbon rom ?
Click to expand...
Click to collapse
Yes.

Doesn't work with adoptable storage, but I don't expect that to work :/
Despite that, everything working fine on D6543, thank you!
Enviado do meu Xperia Z2

FellipeSilvaRJ said:
Doesn't work with adoptable storage, but I don't expect that to work :/
Despite that, everything working fine on D6543, thank you!
Enviado do meu Xperia Z2
Click to expand...
Click to collapse
0 step - Backup boot partition
Dude just boot into any custom recovery (Abricot v8.1 kernel has twrp 3.0.2, flash it using Flashtool), go to Install, navigate to the twrp-3.1.1.img directory and select some option kind "Image file" or something like that, then you can see it, so flash it.
TWRP 3.1.1.img worked fine to me, but the Android doesn't boot up. Only twrp works. So you can use twrp 3.0.2 to flash 3.1.1, flash anything you want, and then restore boot partition (twrp 3.0.2) to get Android booting up again.
Hope I've helped you
Whatsapp group for Z2/Z3 Br https://chat.whatsapp.com/BTxS0jezN8yE6r5g9Vnu20
If there any wrong or missing word above, the fault is of Cabraaaaaal.

can i flash it to recovery fota >>> dose it supported ?
I am using stock .291 with twrp 3.0.2.0 in fotarecovery

matrix2012xman said:
can i flash it to recovery fota >>> dose it supported ?
I am using stock .291 with twrp 3.0.2.0 in fotarecovery
Click to expand...
Click to collapse
Try it out and report back.

aboodyaiman said:
Try it out and report back.
Click to expand...
Click to collapse
Ok I will do and report that

Missing some backup option on 3.1.1 like:
- Recovery
- Trim
Did they removed it for Z2?

aboodyaiman said:
TWRP 3.1.1-0​
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.
Based on latest Omni, rcstar6696 and LineageOS sources.
CHANGELOG for 3.1.1-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)
Download:
TWRP-3.1.1-0
BUG REPORTING:
Please reply to this thread stating what is wrong and I will look into it. Bugs must be reproducible.
Logs:
To get logs there are two ways (if something is broken):
Code:
adb pull /cache/recovery/last_log
adb shell dmesg > dmesg.txt
Flashing:
Code:
fastboot flash recovery recovery.img
Source Code:
https://github.com/omnirom/
https://github.com/rcstar6696/
https://github.com/LineageOS/
https://github.com/Sony-Lineage-3.4/
Click to expand...
Click to collapse
Nevermind - i got it - just another method to call recovery now if somebody has same problem :
power off device wait 5 seconds
than hold vol down and power button
when screen flickers release power button -e voila thanks for upload

h3llfire said:
TWRP 3.1.1-0
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.
Based on latest Omni, rcstar6696 and LineageOS sources.
CHANGELOG for 3.1.1-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)
Download:
TWRP-3.1.1-0
BUG REPORTING:
Please reply to this thread stating what is wrong and I will look into it. Bugs must be reproducible.
Logs:
To get logs there are two ways (if something is broken):
Flashing:
Hi There , flashed the recovery.img but twrp says its 3.0.2.0 ?
i flashed the file with recovery its self and other tried it with the twrp app ?
Dont Know whats wrong?
Click to expand...
Click to collapse
TWRP app will flash 3.0.2 ones, make sure you flash stock rom first and then flash boot.img of your custom ROM + Recovery

aboodyaiman said:
TWRP app will flash 3.0.2 ones, make sure you flash stock rom first and then flash boot.img of your custom ROM + Recovery
Click to expand...
Click to collapse
i know that thx anyway i mean i used the image procedure from app where you can point to an existing img file (and the 3.1.1 was dl to internal storage and so i flashed it )
but i dont know that the 3.1.1 has a new handling to come up with 3.0.2 and older i must press the vol rocker down fastly till the led flashs purple but on 3.1.1 the method is to shut down device and wait for a couple seconds and than press and hold power + volume down . thats i wrote it says 3.0.2 cause in the rom was i using is a root kernel and this has 3.0.2 in it but now im knowing to show up the 3.1.1 build so forget my post i didnt knew it greets

can i use this in existenz mm? flash it through flashtool, right?

Can you update it to 3.2.0 please :fingers-crossed: ?

any 3.2.1.0 update?

Hafyzy said:
any 3.2.1.0 update?
Click to expand...
Click to collapse
Will update it within a month, got finals these days.

[RECOVERY] unOfficial twrp recovery support decryption data

TWRP 3.3.1-0 redmi note 7 (lavender)
All function like normal TWRP
Multi-language support
Supports MTP
Support decrypt /data whitout any problem
Changelog
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
erge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP..
Added the ability to return encryption data to any firmware
Mod edit: links removed.

parsvbulletin said:
TWRP 3.3.0-0 realised for redmi note 7
Changelog
erge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP..
Click to expand...
Click to collapse
waaaait, official?
WOAH HAHA CAN I HAVE THE LINK?

parsvbulletin said:
TWRP 3.3.0-0 realised for redmi note 7
Changelog
erge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP..
Click to expand...
Click to collapse
Where is the download link?

This is spam... No official TWRP recovery for lavender.
https://twrp.me/Devices/Xiaomi/

file not upload and not attach compelet . i retry upload it in extrnal upload center and put in first post...

25 May 2019
Not TWRP Official for Lavender yet!

hugomoya said:
25 May 2019
Not TWRP Official for Lavender yet!
Click to expand...
Click to collapse
official creat for redmi note 7 pro and i change it to redmi note 7

parsvbulletin said:
official creat for redmi note 7 pro and i change it to redmi note 7
Click to expand...
Click to collapse
I'm not trying to be a d1ck or anything but it's not official still unless you got team win support / approved?
Edit: I do appreciate for your work but still....​

parsvbulletin said:
official creat for redmi note 7 pro and i change it to redmi note 7
Click to expand...
Click to collapse
How is this one different from Isaac Chen's TWRP 3.3.1 build?

Can u guys just appreciate him works.
Thank u op

Have anyone tried this? Is there any bug?

Nice, third development comes official
Edit: if developer upload it to official website, please quote this post to let me know. Thanks

hrmmm....link to source please

Deleted.

Lineage os user said:
Have anyone tried this? Is there any bug?
Click to expand...
Click to collapse
please test it ..work like charm...all thing work very well..data decrypt work very well ...

DarthJabba9 said:
How is this one different from Isaac Chen's TWRP 3.3.1 build?
Click to expand...
Click to collapse
in my recovery all option work like official twrp...data decrypt work first one ...please test bro and after test send your comment...:good:

Please someone test it and leave a comment here, cz mine bootloader still unlock and have to wait 166h before it unlocked. Thanks

What's that mean "support decryption data" ?

M7mD.Sa3eD said:
What's that mean "support decryption data" ?
Click to expand...
Click to collapse
when you install new rom. you can unwipe data and new rom boot white older rom data .

parsvbulletin said:
when you install new rom. you can unwipe data and new rom boot white older rom data .
Click to expand...
Click to collapse
Great, gonna try now