Database Info

[NO LONGER MAINTAINED][RECOVERY][E8] TWRP touch recovery

UPDATE: I am no longer maintaining TWRP for devices that I do not possess. I am also no longer posting on XDA.​
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Alternate Installation Method:
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Click to expand...
Click to collapse
Device Changelog
Current version: 3.2.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.2.1:
Code:
[LIST]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)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
Download
Latest Official versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
None
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
TeamWin Recovery Project (TWRP), Tool/Utility for the HTC One E8
Contributors
Captain_Throwback, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2017-12-09
Created 2015-03-20
Last Updated 2018-08-14

Device-Specific Information
Reserved for FAQ (if needed)

Thumbs up, Cap!

Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk

DutchDanny said:
Thanks for the official release.
If you have some spare time, could you consider material design ?
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Use the Materialised theme.
When the stock theme is overhauled (expected with TWRP v3.0), I believe it will include some Material design elements.

@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.

iamsuperuser said:
@Captain_Throwback
I just flashed twrp 2.8.5.0 it's working great thanks.
I always had one problem which is when I press any button in the reboot menu there is a 5 second delay before it reboots.
All the previous versions had the same problem.
Is this permanent or can you fix it in future releases.
And the playstore twrp app doesn't have E8 on its menu, not even a single variant.
Can you please look into that too.
Thanks in advance.
Click to expand...
Click to collapse
The reboot "delay" is normal.
And there is no official TWRP app on the Play Store.

2.8.6.0 has been uploaded.

Captain_Throwback said:
2.8.6.0 has been uploaded.
Click to expand...
Click to collapse
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
EDIT: was using an old theme, after removing the theme, it's working fine now

ghost_razr said:
after updating TWRP to 2.8.6.0, swipe to install function is not working.
anybody else experiencing the same?
Click to expand...
Click to collapse
Update your theme, or remove it.

hi
any chance you can compile twrp for E9 plus?

-=knop=- said:
hi
any chance you can compile twrp for E9 plus?
Click to expand...
Click to collapse
I don't have it, so no.

does this work for m8sw variant? (dual sim - china unicom) ?
UPDATE: I tried it... works great! Thanks

2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.

Captain_Throwback said:
2.8.7.0 is uploaded.
NOTE: If you have already updated to Lollipop, then it's possible the latest version will not work on your device. If you determine that this is the case, let me know - I can upload a beta M8 version that should work on the E8.
Click to expand...
Click to collapse
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix

snoopyhaeckers said:
TWRP 2.8.7.0 has my sd write-protected
tried it with 2 SD cards is effective immediately back on ... and this write protection can be removed by anything neither format or the like can you please fix
Click to expand...
Click to collapse
I think you may be confused by the system read-only prompt. Did you read the change log in the OP? Recovery can't write-protect your device. No kernel changes were made for this device, so it can't be anything the recovery did.

did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .

snoopyhaeckers said:
did it with two different SD cards once I tasted from the sd a zip as supersu 2:46 install this after read-only , 2.8.6.0 no problem working again wonderful, and the system is stock only Xposed framework and super su installed 'm back aud 2.8 . 6.0 thus, the problem for me is first solved .
Click to expand...
Click to collapse
Just disable the read-only option. I don't really understand your issue (language barrier?). If the previous version works fine for you, feel free to continue using it.

Hi, could u make a recovery with f2fs supported for E8? Thank u very much....

schqiushui said:
Hi, could u make a recovery with f2fs supported for E8? Thank u very much....
Click to expand...
Click to collapse
Are there any ROMs that support it? Otherwise it serves no useful purpose.

[TWRP][ Huawei Ascend G620S - TWRP 2.8.7.0][24/01/2016]

Team Win Recovery Project !​​​​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Permanent TWRP Recovery 2.8.7.0
Huawei Ascend G620S
Changelog :
Code:
What’s new in 2.8.7.0:
[LIST]
[*] 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
[*] 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)
[/LIST]
What’s new in 2.8.6.0:
[LIST]
[*] Fix daylight savings time rules for USA and Europe (_that)
[*] Allow mulitple overlays for popup boxes (Dees_Troy)
[*] Add pattern style password entry for decrypt (Tassadar)
[*] Keyboard improvements (_that)
[*] Update AOSP base to 5.1 (Dees_Troy)
[*] Reduce theme count to 5 and rely on scaling (Dees_Troy)
[*] Various scaling improvements (Dees_Troy)
[*] Improved handling of resources in the GUI (_that)
[*] Make scroll bar size proportional to list size (_that)
[*] Allow scoll lists to render without a header (_that)
[*] Make console scroll per pixel with kinetic scrolling (_that)
[*] Support styles in XML to reduce XML size and improve consistentcy (Dees_Troy)
[*] Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
[/LIST]
What's new in 2.8.1.0 :
[LIST]
[*] MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
[*] TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
[*] Temperature support - thanks to bigbiff
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.8.0.0 :
[LIST]
[*] Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
[*] Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
[*] Add support for color in the console and give error, warning, and highlight lines different colors
[*] Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
[*] Improve handling of /misc thanks to mdmower
[*] Improve setting of time on Qualcomm devices thanks to [NUT]
[*] Allow using images on slidervalue GUI objects thanks to Tassadar
[*] Allow using variables and addition and subtraction in variables for easier theming
[*] Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
[*] Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
[*] Other minor fixes and improvements
[/LIST]
What's new in 2.7.1.0 :
[LIST]
[*] Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
[*] Various bugfixes to backup and restore
[*] Improvements to USB storage handling
[*] Added a class to search for files to make finding the correct brightness file automatic in most cases
[*] Various other bugfixes and tweaks
[/LIST]
What's new in 2.7.0.0 :
[LIST]
[*] Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
[*] Allow sideloading from /tmp on encrypted devices
[*] Check for a crypto footer before asking for a password to prevent user confusion
[*] Additional checks for validity to auto generated backup names
[*] Text wrap in the console output
[*] Proper caps lock support in the keyboard
[*] Mouse support via USB OTG for devices with a broken digitizer
[*] Improve scanning of storage locations for OpenRecoveryScript
[*] Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
[*] Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
[*] Update SuperSU to 1.93 and improve installation process
[*] Added selinux contexts restoration to fix permissions
[*] Load RTC offset on Qualcomm devices to fix the date/time in recovery
[*] USB Mass Storage fixes Add SELinux support checking
[*] Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
[*] Add 4.4 AOSP decrypt support
[*] Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
[*] Various SELinux fixes and bug fixes
[/LIST][CENTER][/CENTER]
Downloads :
Code:
[CENTER]
* New Update : [URL="http://forum.xda-developers.com/showpost.php?p=64952135&postcount=20"]TWRP 2.8.7.0 [/URL]
* [URL="https://www.androidfilehost.com/?fid=23991606952615091"]openrecovery-twrp-2.8.6.0.img[/URL] md5 : 842c13cefe34632cdf4def386cc6dc62
[/CENTER]
Installation :
Code:
[CENTER]
* [FONT="Arial Black"]Your Device Must Have A Unlock Bootloader ![/FONT]
*[FONT="Arial Black"] Image File ( openrecovery-twrp-2.8.6.0.img ) :[/FONT]
[LIST]
[*] boot your device in bootloader mode by :> adb reboot bootloader
[*] flash custom recovery :> fastboot flash recovery openrecovery-twrp-2.8.6.0.img
[*] reboot your device :> fastboot reboot
[/LIST]
[/CENTER]
Boot into TWRP :
Code:
[CENTER]
* > adb reboot recovery
* keep pressing at the same time : power off button and volume up about 10 sec. - as soon at your device vibrate , please relase power off button and keep pressing volume up -> your device will enter very soon into TWRP recovery !
[/CENTER]
Source :
Code:
[CENTER]* [URL="https://github.com/TeamWin/Team-Win-Recovery-Project/tree/twrp2.7"]TeamWin GitHub[/URL] !
* G620S-TWRP : [URL="https://github.com/surdupetru/g620s_twrp"]Github[/URL] ;
[/CENTER]
Credit :
Code:
[CENTER]* [URL="http://teamw.in/project/twrp2"][B]Team[COLOR="RoyalBlue"]Win[/B][/COLOR][/URL]
* [URL="http://forum.xda-developers.com/showthread.php?t=1943625"]Dees_Troy[/URL]
* [URL="http://forum.xda-developers.com/member.php?u=4878287"]_that[/URL]
* EloYGomeZ, [URL="http://forum.xda-developers.com/member.php?u=5091734"]dianlujitao[/URL]
[/CENTER]
FAQ :
Code:
[CENTER]
* please perform a Backup with this version of TWRP - after that, you'll be able to restore successfully !
* do not perform a Restore from a Backup performed with other version of TWRP - your device will end with boot loop into TWRP !
[/CENTER]
​
regards,
Surdu Petru

Unlock Bootloader : Huawei Ascend G620S
First method ;
The second method :
- send a e-mail to Huawei ( [email protected] ) , usually you'll receive the unlock code in a day !
Best regards !

Update TWRP !
Hello !
Right now pushed a new update : openrecovery-twrp-2.8.6.0 .
Included : fix sometimes issues, regarding device boot loop into TWRP recovery !
For developer : you can check my github , all fixes are already pushed .
Best regards !

With your version of twrp-2.8.6.0 I was getting constant bootloops into recovery.
Using the twrp-2.8.6.0 from dianlujitao I am not getting any bootloops but unfortunately there are some major issues with registering touches. It looks like it works ok though.

grayden said:
With your version of twrp-2.8.6.0 I was getting constant bootloops into recovery.
Using the twrp-2.8.6.0 from dianlujitao I am not getting any bootloops but unfortunately there are some major issues with registering touches. It looks like it works ok though.
Click to expand...
Click to collapse
i had same problem i had to restore stock rom and replace recovery with B256 one then i could get a working device.
i reinstalled twrp 2.8.6.0 and last cm and for now i have no problem...
but may be twrp should be updated version is 2.8.7.0 now or more?

twrp update_2.8.7.0
i made a little twrp update i made two days ago from omnirom there is new feature like read only
i wanna share it here... until now i have no reboot into recovery. and all seem to work fine.

Hi sir may i ask if you will provide twrp update with 3.10.49 kernel with f2fs support?
i tried but i had no success. The fact is that with 3.10.49 kernel recovery is booting but there is no display... compiled with omni rom.
thanks

desalesouche said:
Hi sir may i ask if you will provide twrp update with 3.10.49 kernel with f2fs support?
i tried but i had no success. The fact is that with 3.10.49 kernel recovery is booting but there is no display... compiled with omni rom.
thanks
Click to expand...
Click to collapse
Today I saw new @dianlujitao TWRP release - HERE
And MEGA mirrors - HERE for update via recovery, HERE via fastboot..
As we see, the recovery is called twrp2.8.7.0_cherry_cn_f2fs .. I really, really hope that G620s kernel will support F2FS someday, because in my previous phones I used this file system in custom roms, and it is way faster and better than EXT4 ..
So .. finger crossed .. :fingers-crossed:
PS: Other thing is that in the name of recovery there is "cn", which I think mean China.. Is it compatible with our G620s-L01 or this recovery is just for UL00 - China Honor 4 Play .. dual sim.. ?

bmasgone said:
Today I saw new @dianlujitao TWRP release - HERE
And MEGA mirrors - HERE for update via recovery, HERE via fastboot..
As we see, the recovery is called twrp2.8.7.0_cherry_cn_f2fs .. I really, really hope that G620s kernel will support F2FS someday, because in my previous phones I used this file system in custom roms, and it is way faster and better than EXT4 ..
So .. finger crossed .. :fingers-crossed:
PS: Other thing is that in the name of recovery there is "cn", which I think mean China.. Is it compatible with our G620s-L01 or this recovery is just for UL00 - China Honor 4 Play .. dual sim.. ?
Click to expand...
Click to collapse
cn means it has a Chinese ui
I released a English version yesterday: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-7-0-touch-recovery-t3199386
F2FS works well

@surdu_petru @dianlujitao
I have heard that twrp compiled with omni sources is more stable, may be worth to compile it with omni sources?
thanks

desalesouche said:
@surdu_petru @dianlujitao
I have heard that twrp compiled with omni sources is more stable, may be worth to compile it with omni sources?
thanks
Click to expand...
Click to collapse
Fake
And isn't it stable now? How to make it "more stable"?

dianlujitao said:
Fake
And isn't it stable now? How to make it "more stable"?
Click to expand...
Click to collapse
Thank for your answer...
for the moment i have no the reboot in recovery as i had by the past.
But here is the problem i have with your latest recovery: http://forum.xda-developers.com/showpost.php?p=62810651&postcount=2

I tried unlock bootloader but in last step its refer me to a chines web site that needs chines tell number for registration.
Could you please help me to unlock this phone?

I successfully bricked my G620S. In TWRP I accidentally installed the TWRP image file, and after that, I stuck in a boot loop: the phone always boots into TWRP. I tried restoring old and stable backups. I tried installing all of surdu_petru's roms. I tried this (it didn't work because it couldn't find the files... maybe because I wiped the internal storage?). I tried reistalling TWRP via usb (fastboot from command prompt). Nothing worked and I'm all out of ideas. I can't find any solutions on the internet neither. Any help is appreciated.
Edit: I'm trying to reinstall the original firmware, maybe that will help.
Edit: I can't install a new firmware, I tried with this software, but it says that the file size is too big (the firmware I found has a system.img that is more than a gigabyte big)
Edit: solved it by flashing recovery.img and boot.img by hand.

Hey, so I've got quite a problem..
I've been running 12.1 Nightly for a couple of months now with great success - after installing the phone worked great, best experiance I've ever had.
Until today - I was listening to spotify and tried to play a song on soundcloud both of them started playing at the same time, the screen went blank and even if i pluged out the headphones it would still play through the speaker.
I rebooted by volume up + power and it rebooted into TWRP 2.8.6.0. Now it won't boot back to system. Every time it boots into recovery. I already restored factory, wiped everything, reflashed the rom, reinstalled the TWRP, and have no idea where to go from here...
you guys are kinda my only hope - did I somehow brick my phone?

arekceg said:
Hey, so I've got quite a problem..
I've been running 12.1 Nightly for a couple of months now with great success - after installing the phone worked great, best experiance I've ever had.
Until today - I was listening to spotify and tried to play a song on soundcloud both of them started playing at the same time, the screen went blank and even if i pluged out the headphones it would still play through the speaker.
I rebooted by volume up + power and it rebooted into TWRP 2.8.6.0. Now it won't boot back to system. Every time it boots into recovery. I already restored factory, wiped everything, reflashed the rom, reinstalled the TWRP, and have no idea where to go from here...
you guys are kinda my only hope - did I somehow brick my phone?
Click to expand...
Click to collapse
Nop, not bricked your device ! ... you only need to flash stock Huawei recovery via fastboot ( fastboot flash recovery recovery.img and reboot : fastboot reboot ) , your device will enter on stock recovery , from here just shut down device - now press at the same time power and volume down to enter in bootloader ... right now reinstall TWRP recovery ... and flash your rom - your issue must be fixed .

surdu_petru said:
Nop, not bricked your device ! ... you only need to flash stock Huawei recovery via fastboot ( fastboot flash recovery recovery.img and reboot : fastboot reboot ) , your device will enter on stock recovery , from here just shut down device - now press at the same time power and volume down to enter in bootloader ... right now reinstall TWRP recovery ... and flash your rom - your issue must be fixed .
Click to expand...
Click to collapse
Thanks for the reply! I tried to do that, flashed a huawei stock recovery.img I found (https://www.androidfilehost.com/?fid=23252070760973625) but now the phone only boots into "FASTBOOT&RECOVERY MODE" and adb doesnt detect it anymore so I cant flash TWRP
edit: managed to flash it through fastboot, flashing rom right now
edit2: flashed TRWP, flashed the rom...still stuck on recovery loop :/
edit3: JESUS F. CHRIST ALL I HAD TO DO IS UPDATE TWRP, works like a charm now, though all my data is gone :<

arekceg said:
Thanks for the reply! I tried to do that, flashed a huawei stock recovery.img I found (https://www.androidfilehost.com/?fid=23252070760973625) but now the phone only boots into "FASTBOOT&RECOVERY MODE" and adb doesnt detect it anymore so I cant flash TWRP
Click to expand...
Click to collapse
First, adb will not work on fastboot mode ( bootloader ) , second - we are here on G620S device, why you flashed a TWRP for Huawei Ascend P6
Right now , please use and flash a stock Huawei recovery for Huawei Ascend G620S in this way :
Code:
> fastboot flash recovery recovery.img
Good luck !
Edit :
You should try to flash : stock boot.img, recovery.img and also system.img from a Stock Huawei UPDATE.APP ! After your device will boot up , please reinstall TWRP and your custom rom !
You can use HuaweiUpdateExtractor, to extarct boot, recovery and system image from UPDATE.APP !
Flash boot & system in the same way like recovery : fastboot flash boot boot.img & fastboot flash system system.img !

surdu_petru said:
First, adb will not work on fastboot mode ( bootloader ) , second - we are here on G620S device, why you flashed a TWRP for Huawei Ascend P6
Right now , please use and flash a stock Huawei recovery for Huawei Ascend G620S in this way :
Code:
> fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I was kinda desperate so I flashed first recovery I could find...
I managed to solve it by simply flashing the newest version of TWRP!
Thank you for all your help men, people like you is why I love the android community!

New Update to TWRP 2.8.7.0 !
Hello !
New UI 6.0 - TWRP 2.8.7.0 , released right now for G620S !
Should be working also on other Huawei msm8916 devices .
Build compiled on CM-13.0 with the last source updated from OmniROM ( /bootable/recovery )
Downloads :
1° TWRP-2.8.7.0.zip md5 : 3e6b66db7190e97a3cc112ab284e183d
2° openrecovery-twrp-2.8.7.0.img md5 : 1b969bd9da5bdd52982e7d96c7ea186b
Installations :
1° like as any other rom, no wipe required
2° fastboot flash recovery openrecovery-twrp-2.8.7.0.img
Bug :
to fix "adb" you should switch MTP to disable/enable under Mount menu !
Screenshots :
Best regards !

[RECOVERY][k2cl] TWRP Touch Recovery

Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option -- more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
CHANGELOG for 2.8.6.0:
-Fix daylight savings time rules for USA and Europe (_that)
-Allow mulitple overlays for popup boxes (Dees_Troy)
-Add pattern style password entry for decrypt (Tassadar)
-Keyboard improvements (_that)
-Update AOSP base to 5.1 (Dees_Troy)
-Reduce theme count to 5 and rely on scaling (Dees_Troy)
-Various scaling improvements (Dees_Troy)
-Improved handling of resources in the GUI (_that)
-Make scroll bar size proportional to list size (_that)
-Allow scoll lists to render without a header (_that)
-Make console scroll per pixel with kinetic scrolling (_that)
-Support styles in XML to reduce XML size and improve consistency (Dees_Troy)
-Various other fixes and improvements (mdmower, bigbiff, codelover, etc)
CHANGELOG for 2.8.5.0:
-Scale the GUI - TWRP can read the theme's resolution and scale it up or down to fit the theme to your screen's resolution
-Backups can now be cancelled while the backup is in progress (does not include restore because we don't want to leave your device in a bad state)
-Improve thread handling and move input handling into the main rendering thread to improve stability
-Make MTP work even if unplugged and plugged back in
-Unify scrollable list code and make kinetic scrolling feel more natural
-Fix handling of mapped zip files for OTA updates (CM12 updater)
-USB keyboards should now work on all devices that support USB host mode via a USB OTG cable
-Other small fixes and improvements
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
NOTE: ONLY AOSP/GPE decryption is supported!! TWRP CANNOT (currently) decrypt HTC Sense ROMs!!
DOWNLOAD:
You can find more information and download links on our website!
Also, see attachments below for latest recovery image and device tree.
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Version Information
Status: Stable
K2CL OS: 4.2.2
Current Stable Version: 2.8.7.0
Stable Release Date: 2015-07-05
Current Beta Version: 2.8.7.0-K2CLB
Beta Release Date: 2015-07-17
Beta Patch Link: [WIP] gui: stock theme rework
Created: 2015-07-05
Last Updated: 2015-07-17
Source: Omnirom 5.1.1

Thanks for your work
Are there a stable version 2.8.7.0 twrp for k2u?

degerli43 said:
Thanks for your work
Are there a stable version 2.8.7.0 twrp for k2u?
Click to expand...
Click to collapse
If you are on 4.2.2 then send me your stock recovery and I can make it happen.

How to install it, pls?

itskapil said:
How to install it, pls?
Click to expand...
Click to collapse
If you are rooted and S-Off or using a custom kernel with write protection removed then download and install terminal emulator from the play store.
Download and unzip recovery image on internal sdcard. Rename it to twrprecovery.img for simplicity sake.
Open up terminal then enter the following:
Code:
su
Code:
dd if=/sdcard/twrprecovery.img of=/dev/block/mmcblk0p21
Otherwise, boot up to bootloader by powering off then pressing and holding the volume down key and power key.
When you see your HBoot select fastboot then plug your device to your computer.
Using fastboot type and enter:
Code:
fastboot flash recovery twrprecovery.img

SHM said:
Otherwise, boot up to bootloader by powering off then pressing and holding the volume down key and power key.
When you see your HBoot select fastboot then plug your device to your computer.
Using fastboot type and enter:
Code:
fastboot flash recovery twrprecovery.img
Click to expand...
Click to collapse
Thanks!
That's what I thought.
Was confused by the other file, device_htc_k2cl_twrp.zip, what's the use of this one?

itskapil said:
Thanks!
That's what I thought.
Was confused by the other file, device_htc_k2cl_twrp.zip, what's the use of this one?
Click to expand...
Click to collapse
Lol, no worries. The other attachment is the Device Tree used in conjunction with the Omnirom Open Source to build TWRP for the k2cl variant. If you do not know how to build TWRP or are unfamiliar with Open Sources then it won't pertain to you and you can just delete it. It's mainly there for any other Developers who wish to have it.
Currently using Omnirom 5.1.1 to make my builds.

@SHM Got it. Thanks a lot for help!

@degerli43, click here for k2u/ul TWRP Recovery.

OP updated with a Beta TWRP build using a reworked stock theme by @z31s1g. Version is 2.8.7.0-K2CLB. Below images will give you an idea of what it looks like. I am currently using this build for myself as I personally enjoy the new look and feel.
Device Tree has been reuploaded after being updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my C525c using Tapatalk

In the past TWRP for this device never included the option to backup your /efs. Typically this is where your imei and other such info is stored. By backing this up using my builds and should you lose such information some how down the road, you can simply restore /efs within twrp and all should be well again with your device.
Sent from my C525c using Tapatalk

Removed by me - wrong thread

[NO LONGER MAINTAINED][RECOVERY][aca] TWRP touch recovery

UPDATE: I am no longer maintaining TWRP for devices that I do not possess. I am also no longer posting on XDA.​
Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
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.
Click to expand...
Click to collapse
Images
Installation instructions
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot download
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
Code:
fastboot reboot
Alternate Installation Method (requires prior TWRP installation):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select recovery from the partition list and swipe to flash
Click to expand...
Click to collapse
Device Changelog
Current version: 3.2.1-0:
Code:
[LIST]Initial official release[/LIST]
Older Device-specific versions:
Code:
[LIST]N/A[/LIST]
Click to expand...
Click to collapse
TWRP Official Changelog
Current version: 3.2.1:
Code:
[LIST]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)[/LIST]
Older versions:
Code:
[SIZE="4"][COLOR="Green"]3.2.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.1.1:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[SIZE="4"][COLOR="Green"]3.1.0:[/COLOR][/SIZE]
[LIST]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 [URL="https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9"]here[/URL] (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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.3:[/COLOR][/SIZE]
[LIST]Partial release to help support the release of the [URL="https://www.xda-developers.com/team-win-releases-their-first-official-twrp-app-in-the-play-store/"]Official TWRP app[/URL][/LIST]
[SIZE="4"][COLOR="Green"]3.0.2:[/COLOR][/SIZE]
[LIST]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.[/LIST]
[SIZE="4"][COLOR="Green"]3.0.1:[/COLOR][/SIZE]
[LIST]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[/LIST]
[SIZE="4"][COLOR="Green"]3.0.0:[/COLOR][/SIZE]
[LIST]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[/LIST]
[U]Additional Notes[/U]
[LIST]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 updated 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![/LIST]
[SIZE="4"][COLOR="Green"]2.8.7.0:[/COLOR][/SIZE]
[LIST]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)[/LIST]
[U]Additional Notes[/U]
[LIST]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 [url]https://jenkins.twrp.me[/url] and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at [url]https://gerrit.twrp.me[/url] to help us keep devices up to date and working.[/LIST]
Click to expand...
Click to collapse
Downloads
NOTE: Read the FAQ from Post #2 to ensure that you're installing the correct version of TWRP!!
Download
Latest Official versions
Sources
Device tree
Click to expand...
Click to collapse
FAQ - Post #2
Known Issues
Reboot recovery option doesn't work - device will only reboot to system (needs custom-built kernel to fix)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Click to expand...
Click to collapse
XDA:DevDB Information
Team Win Recovery Project (TWRP), Tool/Utility for the HTC Bolt
Contributors
Captain_Throwback, OMJ, nkk71, Dees_Troy, bigbiff, _that
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 3.2.1-0
Stable Release Date: 2017-12-09
Created 2016-12-14
Last Updated 2018-03-07

Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
With Marshmallow devices, HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents." Additionally, see this thread.
2. Which version of TWRP am I supposed to use?
The best version to use is 3.2.3-0, the latest official version from twrp.me.
3. Why is there a "System" backup option and a "System Image" backup option now?
The "System" option is the standard tar backup. "System Image" is a dd backup of the entire system block device (/dev/block/bootdevice/by-name/system). The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
NOTE: You only need to choose ONE of these options when making a backup!!
[*]NOTE 2: If you are using a FAT32-formatted card, a "System Image" backup may fail (depending on your variant), due to the 4GB file limit on that format. For a successful System Image backup, internal storage or NTFS/exFAT-formatted external storage must be used (either SD card or USB-OTG)
4. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled in ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img.
5. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
[*]NOTE 2: It is possible to install an OTA without using stock recovery (i.e. installing it with TWRP). TWRP will not flash the firmware.zip included in an OTA file. Please see here for a detailed description of the process.
Reboot to system, install OTA.
6. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
7. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
8. After I restored my Data backup and boot back to Android, I'm entering the correct PIN/password, but it's telling me the password is wrong. What happened, and how do I fix it?
It appears that sometimes after restoring a backup of Data where security was enabled (such as a PIN or password lock), the device does not recognize the correct password. There are two ways to avoid this issue:
Disable security in Android before making a backup of data.
After restoring Data, while still in TWRP, use the TWRP File Manager to navigate to /data/system and delete all the locksettings.* files (such as locksettings.db, etc). When you reboot, the password will be gone.

u da man @Captain_Throwback!

Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.

Captain_Throwback said:
Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.
Click to expand...
Click to collapse
you are the man for sure, i still like the idea of a unencrypted device and glad its a option but im more happy knowing that twrp is now able to support both options!
Thanks bro, know you have been working hard for people who dont necessarily effect you. thanks man!

Had to update TWRP as I forgot that gunzip isn't working on builds from the 7.1 tree. Using a pre-compiled busybox binary in TWRP as a workaround. 3.0.2-2 now available on Downloads tab with this fix included.

Uploaded new version to Downloads Tab. Just some code cleanup mostly and a version bump that coincides to the release of the Official TWRP app.

Can someone test whether this TWRP build boots?
«link removed»
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
EDIT: @OMJ confirmed. Official support should *hopefully* be coming soon!

Captain_Throwback said:
Can someone test whether this TWRP build boots?
http://build.twrp.me/twrp/twrp-3.0.3-0-aca.img
That's from the official TWRP Jenkins. It won't decrypt currently, but I really just want to confirm it boots. Thanks!
Click to expand...
Click to collapse
yes, it boots, and as u said, doesn't decrypt

Can someone please confirm whether this TWRP boots/works/functions properly? Thanks!
https://forum.xda-developers.com/devdb/project/dl/?id=23498
EDIT: @OMJ tested that one and it didn't boot. Updated the link to a new version. I need a log from a ROM flash where the ROM zip includes a root zip to confirm it's getting extracted correctly.

3.1.0 Official is out.

Captain_Throwback said:
Alright, against my better judgement I decided to post this thread. Based on @OMJ's testing, TWRP is working properly with decryption. The only remaining bug I'm aware of is that the "Reboot Recovery" option doesn't work, because of how I hacked the kernel to enable touch. I'm working on an alternative method to get around that, but since I can't test on the device, not sure how that will go.
Make a note of what it says in the OP under "BUGS" because if you report one without a log, it will be ignored! I hope everyone with this device enjoys this "unofficial" version of TWRP.
Click to expand...
Click to collapse
Sir, you mentioned that you hacked the kernel to enable touch in recovery can you share how to did that and did you modify the kernel source code or hacked the kernel without the source code as even other htc devices are having this issue and I can see commit in source codes that'll enable touch in recovery but what if there is no kernel source any hack for that? Thanks in advance.

M.A.P said:
Sir, you mentioned that you hacked the kernel to enable touch in recovery can you share how to did that and did you modify the kernel source code or hacked the kernel without the source code as even other htc devices are having this issue and I can see commit in source codes that'll enable touch in recovery but what if there is no kernel source any hack for that? Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.

Captain_Throwback said:
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.
Click to expand...
Click to collapse
Thank you sir will check that out but why is htc doing this? I mean even some devices running 4.2.2 are having touch disabled and mine is 620g and is disabled too.

M.A.P said:
Thank you sir will check that out but why is htc doing this? I mean even some devices running 4.2.2 are having touch disabled and mine is 620g and is disabled too.
Click to expand...
Click to collapse
Well, touch isn't needed in stock recovery, so it's really just a way to save power while booted into that mode. Only custom recoveries like TWRP require working touch, so that's why we have to hack the kernel if source isn't available.

Captain_Throwback said:
Well, touch isn't needed in stock recovery, so it's really just a way to save power while booted into that mode. Only custom recoveries like TWRP require working touch, so that's why we have to hack the kernel if source isn't available.
Click to expand...
Click to collapse
Oh. but still it is difficult for devices with no kernel source. Will try the hack sir it's night yesterday.
---------- Post added at 09:50 AM ---------- Previous post was at 09:33 AM ----------
Captain_Throwback said:
https://forum.xda-developers.com/de...esire-530-guide-to-root-t3410015/post70697756
Similar procedure to that, only difference is that you don't have to deal with vmlinux since the kernel binary is simply gzip compressed.
And if dtb is combined, you'll need to extract it from the original kernel and re-append it to the modified binary.
Click to expand...
Click to collapse
Sir, can you explain it a bit more as I'm newbie in kernel stuff. I'm having boot.img for my phone and the kernel inside it can you help me how to hack the kernel sir? Thanks in advance

M.A.P said:
Oh. but still it is difficult for devices with no kernel source. Will try the hack sir it's night yesterday.
---------- Post added at 09:50 AM ---------- Previous post was at 09:33 AM ----------
Sir, can you explain it a bit more as I'm newbie in kernel stuff. I'm having boot.img for my phone and the kernel inside it can you help me how to hack the kernel sir? Thanks in advance
Click to expand...
Click to collapse
Your question doesn't belong in this thread. It belongs in Q&A.

TWRP 3.2.0-0
Download
Changelog

i flashed the latest twrp in download and said succes but cant get into it just htc and red letters did i miss somthing

Is the device tree mentioned in the post sufficient to build a lineage based rom ?

[TWRPv3.x.x]Tank Xtreme Pro Recovery

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Screenshots attached below.
TeamWin Touch Recovery for BLU Tank Extreme Pro
Code:
* [U][B]Disclaimer[/B][/U]
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Older Version
CHANGELOG for 3.1.1-0:
TWRP 3.1.1 is Out, Brings Minor Fixes
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)
FEATURES
Backup & Restore fully functional
Micro SDcard and USB OTG storage support
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Full SELinux support
Built with android-7.0 TWRP tree
CHANGELOG for 3.2.0-0:
TWRP 3.2.0 is now out
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.2.2-0:
TWRP 3.2.2-0 brings ADB fixes and improvements to OTA updates
adb backup fixes
OTA style update zips will now install automatically without prompting for decrypt
minor tweaks to handling date/time on Qualcomm devices
updates to some language translations
CHANGELOG for 3.2.3-0:
TWRP 3.2.3-0 is out now for most currently supported devices.
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
BUGS:
MTP NOT Recognize Driver--So No mtp connection-- work-around for this now, is to use "mount as USB drive", this will allow similar function as MTP, but only for your micro-SDcard
SUPPORT: Post your questions below. I'll answer whenever I get time.
INSTALLATION
Most devices can be updated quickly and easily within TWRP if you already have version 3.x.y-z or higher installed
1) Download the latest version from DOWNLOAD TAB
2) Copy that file to your sdcard
3) Reboot to TWRP
4) Hit INSTALL and tap the "Images..." button in the lower right
5) Browse to the location of the TWRP image (recovery.img) on your device and select it
6) Select RECOVERY from the PARTITION list and swipe to flash
7) Go to Menu: Reboot recovery
If First time install
You can install with spft as described in following link BUT FIRST NEED unlock bootloader.
Instructions for Flash stock recovery or Custom recovery MEDIATEK devices only
You can also install with fastboot commands after unlocking bootloader.
****UNLOCKING BOOTLOADER WILL CAUSE WARNING ON SCREEN WHEN POWERING ON****
****WARNING WILL PAUSE THE BOOT PROCESS FOR % SECOND DELAY , Not big problem****
BOOTLOADER UNLOCK
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
RECOVERY INSTALL
1. make sure developer options is enabled
1). open settings
2). scroll to about phone
3). tap "Build number" 7 -8 times
4). go back, now you have new menu option"Developer options
5). open and make sure "off" switch at top is slid to right to turn on
5). slide switches for OEM unlocking and ADB debugging
6). Now connect usb cable from PC to Phone
7). phone should have popup window asking for authorization to connect with ADB
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the 3.2.0 version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/twrp-3.2.0-recovery.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
adb reboot bootloader
fastboot flash recovery Desktop/twrp-3.2.0-recovery.img
fastboot boot Desktop/twrp-3.2.0-recovery.img
adb wait-for-device
adb reboot recovery
ROOT
If your device haven't ROOT:
Thanks to @Chainfire for the file!
Rooting instructions: put the SuperSu...zip on sdcard. Go to TWRP and tap INSTALL. Search the zip file and select. Swipe to install. Reboot system.
Dowload: SuperSU V2.82
DOWNLOADS In Download Tab
SCATTER File
Stock boot ----- Stock recovery
TWRP 3.1.1 ------ TWRP 3.2.0 ------ TWPR 3.2.1 ------ TWPR 3.2.2-0 (based in stock V7.0.04.04_GENERIC 24-05-2018)
-----Added--TWRP 3.2.2-0(repacked)Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.
TWRP 3.2.3-0 [Has ro.secure=0; ro.adb.secure=0; to allow adb while data is wiped.] (based in stock V7.0.04.05_GENERIC 06-08-2018) download in post#2
Note:
After TWRP3.2.2 the partitions for the backup save have been modified to: /dev/block/platform/mtk-msdc.0/by-name/
So if you have a version older than TWRP3.2.2 you should copy the
Root [Internal Storage or MicroSD] / TWRP/ BACKUPS / VCIBIZMR7HT8GES8 / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
folder to the new one folder
Root [Internal Storage or MicroSD] / TWRP / year-month-date-hour-minute-second_BLU_T0010UU_V70040x_GENERIC_dd-mm-yyyy
of the version TWRP3.2.2 or last.
We've added the partition for internal storage if you want to create a backup of it. But keep in mind that the more files there are in the internal storage, the larger the size of the backup made and this will depend on your choice and how you can save it to other larger storage capacity.
So be more careful!
Contributors
@lopestom
@Dees_Troy
@teamwin
@vampirefo
Version Information
Status: Beta
Current Beta Version: 3.2.3-0-20181013
Beta Release Date: 2017-12-24
XDA:DevDB Information
Tank Xtreme Pro Recovery, Tool/Utility for all devices (see above for details)
Contributors
mrmazak, lopestom, vampirefo
Version Information
Status: Beta
Created 2017-12-08
Last Updated 2018-10-13

Instructions to unlock and relock bootloader
Instructions to unlock and relock bootloader soo... :silly:
https://youtu.be/5ZVW-XzPCXE
https://youtu.be/Zf6hMqGbC_4

With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
With older version TWRP, does MTP work? I see you list it not working on 3.2.
MTP to me is more important than version of TWRP used.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.

mrmazak said:
No, mtp not working at all on this device. The recovery that I used to port older version is yours from life Max. Boh of these on this thread came from lopestom.
Suspect something in kernel, like touch on life Max was problem in kernel. As of last time I checked, sources we're not published from blue yet.
Click to expand...
Click to collapse
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Ok, thanks I will compile a recovery for Tank, see if I have any better luck with it.
I suspect it's the recovery looking for MTP in the wrong place, Android 6 and 7 access to MTP would be different.
Blu Life Max is Android 6, so MTP would be in platform, while tank is Android 7 so would be in virtual.
Click to expand...
Click to collapse
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs

lopestom said:
@mrmazak tested some TWRP and we have same issue with driver mtp in PC/laptop like Indisponible driver so the device is recognized but cannot open mtp. If we boot ROM so that's recognizing and open.
I tried with libtwrpmtp.so from sbin folder: replacing from other, open to know if need more informations and compared with same lib name of Android 6 as I have mtp working..... So no luck!
Remember: TWRP3.1.1 and 3.2.0 from me is based in Android 7 Nougat TWRP base x32.
As I'm no good with programming to open libtwrpmtp.so to see if have or need specific info so... I hope that you can help better on it...
Congrats and enjoy...
Sent from my BLUBOO Xtouch using XDA Labs
Click to expand...
Click to collapse
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
I don't know about your 3.2 recovery, mrmazak used my Blu Life Max recovery, I told that recovery to look in platform for MTP, that's why I suspect my Blu Life Max recovery is the problem.
If I am correct, just rebuilding a new recovery telling it to look in virtual for MTP should work, if I am wrong it won't, doesn't hurt to try.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I assume you already looked, but, the recovery log shows mtp error , over and over again.
Code:
E:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] got unsupported command UNKNOWNE:[MTP] response write returned -1, errno: 5, exiting MtpServer::run loop
I:[MTP] MtpServer::run fd: 22
pretty sure it happens with all versions

The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.

mrmazak said:
The stock boot img has "init.usb.configs.rc"
in this file it sets usb_gadget # for mtp.
there is nothing that I find similar in the twrp.
I am thinking to add this rc file to twrp and import it with the init.rc to see if it changes anything.
***UPDATE*** No change with adding this configfs file
Attached is a listing of all mentins of "mtp" in the stock boot.img ramdisk
this link is in Russian , but google translate helps.
posts #1354 and 1355 reference the same error I see in the recovery log. Also mention addressing the usb_gadget #
.
Click to expand...
Click to collapse
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.

vampirefo said:
Oh, well if MTP doesn't work it doesn't work, I compiled my own today, removed MTP tab and just use Mount USB Storage instead, works fine for micro sdcard. I compiled mine using TWRP 8.1 source, and uploaded it to needrom.
Click to expand...
Click to collapse
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.

mrmazak said:
I just gave this a try, I have noticed something, could be intentional , not sure.
On your other recovery you could flash system as image, this one you cannot.
Click to expand...
Click to collapse
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab

vampirefo said:
Correct something I don't use, that's controlled by recovery.fstab
just use this recovery.fstab if you want that option, unpack recovery and replace recovery.fstab
Click to expand...
Click to collapse
thanks, is it ok to add this version to the downloads of this thread?

mrmazak said:
thanks, is it ok to add this version to the downloads of this thread?
Click to expand...
Click to collapse
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk

vampirefo said:
Thanks fine with me.
Sent from my Tank Xtreme Pro using Tapatalk
Click to expand...
Click to collapse
I've added you as contributor and added your version, with the fstab that has system_image and also cache enabled (because of an error message in recovery.log that stated could not mount cache)

sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6

gabmika69 said:
sorry for asking,, can i use this recovery into blu tank xtreme 5.0??
im looking everywhere the method how to root blu tank xtreme 5.0 android 6
Click to expand...
Click to collapse
No!
Each device should have the own Custom Recovery.
Sent from my BLUBOO Xtouch using XDA Labs

Please HELP!
Was hung on boot with TWRP installed. Fixed the problem by installing SuperSU to unlock the bootloader. No help needed.