• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[OFFICIAL] TeamWin Recovery Project [TWRP] [3.1.0]

Search This thread

DroidThug

Senior Member
Jul 6, 2015
53
101
Bangalore, India
droidthug.me
http%3A%2F%2Fwww.aftvnews.com%2Fwp-content%2Fuploads%2F2016%2F02%2Fteamwin-recovery-project-twrp-logo.jpg




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. It allows you to back up and restore your data, flash custom ROMs and zips to your device, repair broken file systems, and root your device.



CHANGELOG for 3.1-0:
TWRP 3.1.0-0 is out now for all currently supported devices.

What's new in 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


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


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 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​

XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the LeEco Le 1S

Contributors
DroidThug, lbule
Source Code: https://github.com/TeamWin


Version Information
Status: Stable
Current Stable Version: 3.1.0
Stable Release Date: 2017-03-06

Created 2016-12-28
Last Updated 2017-03-15
 
Last edited:

DroidThug

Senior Member
Jul 6, 2015
53
101
Bangalore, India
droidthug.me
Known Bugs
Battery stats miscalibrated at 50% (capacity files are getting reset)


NOTE:
The block files are located at:
Code:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/$insertwhateverblockyouwant
 
Last edited:
  • Like
Reactions: Zamasu

Nameless One

Senior Member
Mar 24, 2013
296
134
Tasmania
Samsung Galaxy A21s
A quick note that this will fail to install the 20161127 Resurrection Remix ROM (and possibly the CM ROM also by Bule), aborting with "error: 7"
This is due to the fact that the RR (and probably CM) ROM was badly constructed, it makes TWRP think that it is being installed on the wrong device.
To fix this follow the instructions here:

http://forum.xda-developers.com/showthread.php?t=2522762

You need to delete the first line in the file "META-INF/com/google/android/updater-script", the one starting with "assert(" and ending with a semicolon (as each full line of code in the file does, using an editor that recognises non-windows end of line characters is advised for clarity).
This line is supposed to prevent bricking a device by preventing flashing a ROM for a different device that is not listed in the file, Bule (or whoever created the custom TWRP) seems to have produced a broken TWRP that ignores this important error to flash a broken ROM .zip, edit the updater-script file in the ROM and it flashes just fine with official TWRP.
 
  • Like
Reactions: ||-E-M-I-N-E-M-||

sscsps

Senior Member
Nov 17, 2013
618
186
delhi
I'm sorry if this question is stupid, but
Does this work with all variants of 1s? Like x500, x507,x509 and more that there are.
Because i have x509 and of like to know if there's a problem with that...
 

tejus

Senior Member
Apr 25, 2014
270
159
22
New Delhi
Bro Mine device is not rooted and M running eui5.8.019s
While installing TWRP through fastboot it doesn't require unlocked bootloader ?
 

sscsps

Senior Member
Nov 17, 2013
618
186
delhi
I successfully unlocked bootloader by
Fastboot oem unlock
But problem is that now when i use fastboot flash command there's written unable to flash (will tell u exact error today )
Okay, I'll try to help. :)
For me, i followed the steps on the device page on twrp site and it worked fine.
When I executed flash command, it first unlocked tge bootloader abd then flashed the recovery and then when I executed reboot command, it locked the bootloader by itself.
 
  • Like
Reactions: tejus

tejus

Senior Member
Apr 25, 2014
270
159
22
New Delhi
Okay, I'll try to help. :)
For me, i followed the steps on the device page on twrp site and it worked fine.
When I executed flash command, it first unlocked tge bootloader abd then flashed the recovery and then when I executed reboot command, it locked the bootloader by itself.

i dont know why it didnt worked on window 7 but worked on ubuntu
and also i installed every drivers still but now success on ubuntu
 
Last edited:

sumitgp

Senior Member
Mar 10, 2017
221
49
If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us

Requriemt
1. Download telegram from play store
2. Just click below link

https://telegram.me/LeSuperGroup

Thanks all of u
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    http%3A%2F%2Fwww.aftvnews.com%2Fwp-content%2Fuploads%2F2016%2F02%2Fteamwin-recovery-project-twrp-logo.jpg




    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. It allows you to back up and restore your data, flash custom ROMs and zips to your device, repair broken file systems, and root your device.



    CHANGELOG for 3.1-0:
    TWRP 3.1.0-0 is out now for all currently supported devices.

    What's new in 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


    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


    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 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​

    XDA:DevDB Information
    TeamWin Recovery Project, Tool/Utility for the LeEco Le 1S

    Contributors
    DroidThug, lbule
    Source Code: https://github.com/TeamWin


    Version Information
    Status: Stable
    Current Stable Version: 3.1.0
    Stable Release Date: 2017-03-06

    Created 2016-12-28
    Last Updated 2017-03-15
    1
    Known Bugs
    Battery stats miscalibrated at 50% (capacity files are getting reset)


    NOTE:
    The block files are located at:
    Code:
    /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/$insertwhateverblockyouwant
    1
    The new recovery TWRP 3.2.1-0X3 has already been published, for our LeEco S1 X500 device