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

[RECOVERY][OFFICIAL][Lenovo K4][A7010a48] TWRP 3.2.3.0 Touch Recovery [2019-03-30]

Was this recovery helpful?

  • Yes

    Votes: 11 91.7%
  • No

    Votes: 1 8.3%

  • Total voters
    12
  • Poll closed .
Search This thread

mohancm

Inactive Recognized Contributor
May 14, 2016
1,075
3,615
bengaluru
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.
kHQgwnV.png


TWRP 3.2.3-0 Released

What's new in 3.2.3-0:

* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files

What's new in 3.2.1-1:

* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

What's new in 3.2.0-0:

* Allow restoring adb backups in the TWRP GUI (bigbiff)
* Fix gzip backup error in adb backups (bigbiff)
* Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
* Better support for installing Android 8.0 based zips due to legacy props (nkk71)
* Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
* Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
* Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
* v2 fstab support (Dees_Troy)
* Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
* Various other minor bugfixes and tweaks

CHANGELOG for 3.1.1-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.


What's new in 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)Updated TWRP source code to AOSP 7.1.2

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.

DOWNLOAD:

Downloads:
Twrp-3.0.2-0
Twrp-3.1.1-0
Twrp-3.2.1-0
Twrp-3.2.3-0 (Latest)

#Improvements:
  • ! Faster and Smoother than before
  • ! Build from source
  • ! supports Android 7.1.1
  • ! MTP Supported
  • ! Usb OTG supported
  • ! Android 8.1.x Supported

Credits: :)
-TWRP Team
@Dees_Troy
@sevenmax
@Deepflex
@mohancm

BUGS:
Not yet found

Screen shots are Attached:

If you liked My developments Hit like :good:
 
Last edited:

nikkali25

Senior Member
Jan 11, 2014
639
296
philippines
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.


CHANGELOG for 3.0.2-0:

-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.

CHANGELOG for 3.0.1-0:

-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements

CHANGELOG for 3.0.0-0:

-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks

WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

CHANGELOG for 2.8.7.0:

-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

DOWNLOAD:

#link:
Twrp-3.0.2-0

#Improvements:
! Faster and Smoother than before
! Build from source
! supports Android 7.1.1
! MTP enabled
! Usb OTG supported


Creadits: :)
-TWRP Team
@Dees_Troy
@jonnyxda
@deepLex
@leskal
@mohancm
@[email protected]
-AMT

BUGS:
Not yet found

Screen shots are Attached:

If you liked My developments Hit like :good:
Thank you bro
 
D

dg28gadhavi

Guest
No bugs no issues TWRP is working great also the theme zip is working fine and it is themable. Finally a committed Dev for our k4 is here thnx @mohancm

Sent from my Lenovo Vibe K4 Note using XDA Labs
 
Last edited:

mohancm

Inactive Recognized Contributor
May 14, 2016
1,075
3,615
bengaluru
I do agree with you @mohancm ...

Just to enlightenment and help...

sorry .. my bad :(

like instructions (read post #01)... @gabriel_agra

installations with others twrp compilations are NOT DEV's responsability ... but It theirs builders ...

I'm using @mohancm 's twrp and It works fine ... no lags or issues

best regards folks


---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------

[/COLOR @mohancm Should Do I "edit" the external links?


No worries, any recovery can be used.
I should tell that I am not helping for other recoveries,if you come out with bugs.
Good luck
 
  • Like
Reactions: smartdetodos

smartdetodos

Senior Member
Dec 18, 2011
139
60
Rio de Janeiro
@mohancm I do really appreciate your work...

Google+ Lenovo A7010 Brazilian Community'users had installed a lot your ROMs and twrp... and ... lol ...

they are very anxious for new builds... nougat and lineage ...

I realize that xda is more technician and there a basic support ... different audiences and public ...

but if a Brazilian user report anything there I will quote here ... with your permission of course...

Best regards and "valeu!!!" ...

PS. "valeu" is a brazilian expression like ... "yeah ... thanks Its cool man!!!" :)
 

mohancm

Inactive Recognized Contributor
May 14, 2016
1,075
3,615
bengaluru
@mohancm I do really appreciate your work...

Google+ Lenovo A7010 Brazilian Community'users had installed a lot your ROMs and twrp... and ... lol ...

they are very anxious for new builds... nougat and lineage ...

I realize that xda is more technician and there a basic support ... different audiences and public ...

but if a Brazilian user report anything there I will quote here ... with your permission of course...

Best regards and "valeu!!!" ...

PS. "valeu" is a brazilian expression like ... "yeah ... thanks Its cool man!!!" :)

Sure , I will be with them ;)
 

mohancm

Inactive Recognized Contributor
May 14, 2016
1,075
3,615
bengaluru
what is the best procedure to permanent unlock bootloader and how to flash TWRP via SPFlash without unlocking bootloader in ADB because i always unlock my boot after the twrp gone when i going to stock rom after bricked

No permanent method of unlocking bootloader, once you flashed stock rom via so flash tool.again you need to unlock bootloader with fastboot.
Many guides are Thier on XDA unlocking and installing twrp.
You can choose whichever you prefer :)
Good luck
 
  • Like
Reactions: edarick

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    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.
    kHQgwnV.png


    TWRP 3.2.3-0 Released

    What's new in 3.2.3-0:

    * Fix automatic installing of OTA zips on encrypted devices
    * Remove SuperSU from TWRP
    * Support both md5 and md5sum file extensions when doing MD5 checking for zip files

    What's new in 3.2.1-1:

    * minui fixes (cryptomilk)
    * Better android-8.0 compatibility in ROM trees (Dees_Troy)
    * Fix missing library in android-8.0 (nkk71)
    * Fix inconsistent SDCard naming (DevUt)
    * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

    What's new in 3.2.0-0:

    * Allow restoring adb backups in the TWRP GUI (bigbiff)
    * Fix gzip backup error in adb backups (bigbiff)
    * Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
    * Better support for installing Android 8.0 based zips due to legacy props (nkk71)
    * Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
    * Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
    * Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
    * v2 fstab support (Dees_Troy)
    * Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
    * Various other minor bugfixes and tweaks

    CHANGELOG for 3.1.1-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.


    What's new in 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)Updated TWRP source code to AOSP 7.1.2

    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.

    DOWNLOAD:

    Downloads:
    Twrp-3.0.2-0
    Twrp-3.1.1-0
    Twrp-3.2.1-0
    Twrp-3.2.3-0 (Latest)

    #Improvements:
    • ! Faster and Smoother than before
    • ! Build from source
    • ! supports Android 7.1.1
    • ! MTP Supported
    • ! Usb OTG supported
    • ! Android 8.1.x Supported

    Credits: :)
    -TWRP Team
    @Dees_Troy
    @sevenmax
    @Deepflex
    @mohancm

    BUGS:
    Not yet found

    Screen shots are Attached:

    If you liked My developments Hit like :good:
    9
    TWRP 3.1.1-0 Released​

    TWRP 3.1.1-0 is out now for all currently supported devices.

    What's new in 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)Updated TWRP source code to AOSP 7.1.2

    changelog:
    OTG Bug fixed

    Download link : TWRP-3.1.1
    8
    TWRP 3.2.3-0 Released

    What's new in 3.2.3-0:

    * Fix automatic installing of OTA zips on encrypted devices
    * Remove SuperSU from TWRP
    * Support both md5 and md5sum file extensions when doing MD5 checking for zip files

    download links:
    Twrp-3.2.3
    6
    TWRP 3.2.1-0 Released

    What's new in 3.2.1-1:

    * minui fixes (cryptomilk)
    * Better android-8.0 compatibility in ROM trees (Dees_Troy)
    * Fix missing library in android-8.0 (nkk71)
    * Fix inconsistent SDCard naming (DevUt)
    * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

    What's new in 3.2.0-0:

    * Allow restoring adb backups in the TWRP GUI (bigbiff)
    * Fix gzip backup error in adb backups (bigbiff)
    * Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
    * Better support for installing Android 8.0 based zips due to legacy props (nkk71)
    * Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
    * Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
    * Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
    * v2 fstab support (Dees_Troy)
    * Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
    * Various other minor bugfixes and tweaks

    our changelog:

    • Android 8.1 Support

    Download Links:
    Twrp-3.1.2-0

    Note:
    This recovery is based on Marshmallow kernel , so it works only on Stock rom , older nougat roms , and future oreo roms
    Dont flash it this recovery on Nougat roms like: RR-5.8.5, DotOS Nougat
    4
    Now its official.

    Twrp recovery is officially supported for our device.

    K4 Note site: https://twrp.me/lenovo/lenovok5fpr.html
    New build is available when a newer version comes up. we can download either from twrp website or twrp app from play store.

    note: This recovery works only for stock roms or marshmallow kernel based roms.
    caution: Don't try this recovery on my Resurrection remix nougat.

    Good day:good: