Database Info

[RECOVERY][d2vzw] TWRP 3.1.1-0 touch recovery [2017-05-19]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Backups will now include adopted storage keys (Dees_Troy)
-Fixed an adb restore issue (bigbiff)
-Fixed rebooting when no OS is present (Dees_Troy)
-Fixed line wrapping in the GUI terminal (_that)
-Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
CHANGELOG for 3.1.0-0:
-vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
-adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
-tweak MTP startup routines (mdmower)
-support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
-support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
-better indicate to users that internal storage is not backed up (Dees_Troy)
-improve automatic determination of TW_THEME (mdmower)
-minimal getcap and setcap support (_that)
-try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
-shut off backlight with power key (mdmower)
-timeout during FDE decrypt (Dees_Troy and nkk71)
-support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
-boot slot support (Dees_Troy)
-TWRP app install prompt during reboot (Dees_Troy)
-support for AB OTA zips (Dees_Troy)
-support new Android 7.x log command (Dees_Troy)
-update recovery sources to AOSP 7.1 (Dees_Troy)
-numerous bugfixes and improvements by too many people to mention
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Awesome Work!

Team Win is a pretty fitting name. :good:

Beats the hell out of ClockworkMod.

Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970

Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app

** instructions **
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Things to know:
1. Backup files are accessible through >data>media>TWRP, even though they are on your internal SD card.
2. Zip files you want to flash are also accessible through >data>media, if you first move them to the root of your internal SD card before booting into recovery.
Pj
Phoenix, AZ

For anyone that is having problems backing up to EXTERNAL SD Card please take a look at this: Link
Took me a while to figure out why my 64GB MicroSD wasn't being detected by any recovery and several apps couldn't detect it.

ChuckFarley said:
Installed like a boss. Backed up and ready to go.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!

pdinphx said:
For dummies like me ...
Download the GooManager App ... direct download or Play Store produce the same results -- GooManager 2.1.1. If you direct download, scroll to the bottom of the page for the most recent version.
Once you have GooManager installed, open it and go to Menu>Install OpenRecoveryScript>Yes. GooManager will automatically find and install the most recent recovery for your phone. In our case, this is TWRP 2.2.
To confirm installation, push Reboot Recovery from GooManager's main screen.
Pj
Phoenix, AZ
Click to expand...
Click to collapse
Sorry, but do you need to already be rooted to do this?

d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Of course.

mds96 said:
So this working perfect for you then? I might have to switch over to this recovery cause it looks badass!
Click to expand...
Click to collapse
Yup, working great! Nice easy install, too.
Sent from my SCH-I535 using xda app-developers app

jmacko said:
Well done! Installs and backs up fine.
What's with the clock though in Recovery? Is the system time not available? Seems to think that it's back at the start of the unix epoch
If you go Advanced -> Terminal Command - > Select -> Type "date" -> press enter
Date returns : Wed Jan 7 15:21:55 EST 1970
Click to expand...
Click to collapse
I have the same situation with the time and date, but otherwise appears to be working perfectly. I posted the question on their github site to see if something needs to be done.

d1ez3 said:
Sorry, but do you need to already be rooted to do this?
Click to expand...
Click to collapse
Is the bug where the backup dates showing 1970 still exist? Something still seems weird regarding the date/time according to the poster above.

I've been able to backup with this recovery, but I have not tried to restore a backup.
Also, I have not been able to flash any zips, as the recovery doesn't allow me to explore either my internal or external sd cards.
What am I doing wrong?
Pj
Phoenix, AZ

will this work for all the other carriers as well? the original TWRP file that birdman posted on rootz he said that it should. i know this is changed but wonder if that still holds true.
would it work with sprint?

Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.

zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Thanks for confirming restore functionality.
Sent from my SCH-I535 using xda premium

zeddicus225 said:
Just wanted to say I've created a backup and successfully restored. I was also able to flash a different boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=1756885.
The only issue is with the date/time with the backup, but not a big deal.
Click to expand...
Click to collapse
Where did you put the zip so that this recovery could find it?
Pj
Phoenix, AZ

so you just root, then load goo manager and let goo manager load the recovery right?

[RECOVERY][OFFICIAL] TWRP for HTC One Dual SIM (802W, 802D and 802T variants)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our NEW website!
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.

Reserved

This is great! Whenever i plugin my charger once my battery drained, unlike before, it doesnt boot to recovery with unresposive touch anymore.. good job @bgcngm!
Sent from mobile

Thanks for the feedback.
By the way, you can use TWRP Materialised theme, to get an even nicer UI.

@bgcngm This is great job! Thank you.
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
EDIT:
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?

J_M_V_S said:
You think it would be possible to solve the /data/preload problem when wiping from TWRP?
Click to expand...
Click to collapse
I think so, should be possible to preserve /data/preload during a factory reset. I can't try right now because my phone is *again* at the repair center for camera replacement.
MTP seems to be working great! I do see MicroSDcard and SD-Ext plus USB OTG. What would be SD-Ext for?
Click to expand...
Click to collapse
SD-Ext is if you have your SDcard partitioned with an EXT2/3/4 partition. I think that is not so used anymore.

TWRP v2.8.4.0 is out.

TWRP v2.8.5.0 is out.

Do you have any mirror? I cannot download from homepage. Always stuck at 99.99%

No, I don't. That's the official link to the website. Try again later if server is down / overloaded.

TWRP v2.8.6.0 is out.

Help
bgcngm said:
TWRP v2.8.6.0 is out.
Click to expand...
Click to collapse
Hi, thanks for the TWRP but do you have the stock recovery file for HTC One M7 802dwg? I want to revert back to stock recovery to get the OTA updates which i'm not being able too install by TWRP or CWM. I'm on Hboot 2.49, Bootloader unlocked, Rooted, S-On, M7 802dwg.
Thanks in advance.

If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.

Any help??
angusc said:
If you still have a copy of the last OTA that you applied, you can get the recovery from within that file.
Click to expand...
Click to collapse
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??

[email protected] said:
Hi, thanks i got the stock kitkat recovery and flashed it and then updates by OTA to 4.4.3 but then again after downloading Lollipop OTA i am not being able to update!!! I tried to extract the recovery file from the Firmware.zip from within the OTA.zip
but it gives me an error. I can't open the firmware.zip. Any idea where can i get the stock lollipop recovery image file for 802dwg??
Click to expand...
Click to collapse
I have the same problem, plz help, i stuck in bootloop on HTC one 802d

sekilo004 said:
I have the same problem, plz help, i stuck in bootloop on HTC one 802d
Click to expand...
Click to collapse
For now restore from a nandroid or TWRP backup...and update upto 4.4.3 unless there is a copy of the lollipop stock recovery.

Could you guys stop spamming this thread with off-topic? If you didn't yet realize, this thread is related to TWRP only. You have already been told how to get the stock recovery.

sorry for my bad english and still noob,..
I flashed twrp-2.8.7.0-m7cdwg.img for my HTC m7 802d..
after booting on twrp, I'm looking on system/lib/modules, but not found. there is only BIN folder
anyone suggest or modify twrp to make it possible that directory, system/lib/modules are avalible on twrp?
thank in advance

What exactly are you trying to do? Maybe you have to mount system first...

[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.

[RECOVERY] [20.11.2016] Unofficial TWRP for Ulefone Metal - 3.0.2-0

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Unofficial TWRP 3.0.2-0 for Ulefone Metal
Mirror 1
MD5 - 10286EE1255C8371A2E5F720896D02C2
SHA-1 - E6C0875ADA34EB1CDE5D5A648D3F8B9AC883EFDA
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
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, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
XDA:DevDB Information
RECOVERY] Unofficial TWRP for Ulefone Metal, Tool/Utility for the Android General
Contributors
Jonny
Source Code: https://github.com/JonnyXDA/android_device_ulefone_metal/tree/Omni
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-11-20
Created 2016-10-31
Last Updated 2016-11-20

FAQ:
- None yet!
DEVICE-SPECIFIC CHANGELOGS:
3.0.2-0:
-Fully built from source for Ulefone Metal
Current TWRP "bugs" for Ulefone Metal:
NONE

Thanks for your work.
Recovery not mounting sd card.
Here is log:

Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:

dropbear2 said:
Internal build from ulefone forum works.
Mounting sd card works.
Thanks.
here is log:
Click to expand...
Click to collapse
Internal? You mean the build I posted there this morning?

Jonny said:
Internal? You mean the build I posted there this morning?
Click to expand...
Click to collapse
Yes, build posted this morning.

dropbear2 said:
Yes, build posted this morning.
Click to expand...
Click to collapse
Cool, I'll update this thread with it in a bit.

This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img

dropbear2 said:
This build twrp in downloads (2016-11-02 16:29) does not work.
Is not the same as the build in ulefone forum.
This twrp works: http://ota.cm.mkoas.de:8080/job/TWRP Ulefone Metal/ws/recovery.img
Click to expand...
Click to collapse
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy

Jonny said:
I know, I said I would get round to updating this post as well, I haven't been able to yet as I've been busy
Click to expand...
Click to collapse
sorry,
I thought that you replaced.

Thread updated with the new links (eventually!).
Apologies for the delay

Hey,
i've flashed TWRP and when i boot it, the phone just shows the ulefone logo and then restarts..
I tried to flash with flashtools and via fastboot flash recovery...
Its possible to flash custom rom, which works quite nice, but TWRP won't come up so i can't root phone or do nandroid backups.
Any help? Any idea how to get logs of what happening?
BTW: reflashed offical stock does the same, displays ulefone logo and reboots..
EDIT:
Flashed recover as boot, and boot as recovery:
Normal boot (should start TWRP now) reboots all the time.
Recovery boot (should boot normal boot.img now) works and boots the System..
So there has to be a problem with the downloaded TWRP/Recovery Image not working on my phone..
It's normal Ulefone Metal don't know why it doesn't work.. wpuld like so see some logs or something
Edit2:
Flashed twrp-3-0-2-4es-by-mdsdev from needrom,
which worked.. don't know why any other one didn't...

I can not find the scatter mentioned in the post. I tried to install it with another scatter or another TWRP, but when I try to run the recovery it simply restarts.

Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.

sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.

sinrequilorios said:
Regards, I inform you that I have been doing a series of tests on my mobile, to try to flash some existing roms. For now the following happens: The official firmware from the 20160912 and lower version do not work (I still have to try the 20161019 version), the 20161024 and 20161117 versions work correctly.
Another error, for now the one that has me more restless is the following: The only functional recovery is the TWRP of the user hanuma50 that has incompatibility with certain roms, the other versions of TWRP available do not work, when trying to install it using SPFT , Flashify or from the same TWRP are installed correctly, but at the time of running it simply restarts the mobile and starts the system normally.
I'm thinking because it is because there is surely a new batch of mobile with changes to the hardware, but I do not know, Do you know anything about it?
Another thing, if the darksense kernel flashed the mobile stops working (it enters an infinite loop with the Ulefone logo), it was tested in stock rom and in the Eragon rom.
Click to expand...
Click to collapse
Jonny said:
It is not my fault if existing ROM's don't flash properly, we faced this problem on Elephone P9000, it is because the people who develop the ROM's don't use the proper mount points, if they did, it would flash. Instead, they use the mount points for the ported recoveries which are not correct.
End of story, not my fault and I will not support the people that this happens to.
Click to expand...
Click to collapse
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.

DerTeufel1980 said:
I think here's some confusion. As far as I understand it, it's not a problem of neither the recovery, nor wrong mount points.
There's just a newer revision of the model it seems. This newer models only work with recovery, built against stock pre-built kernel (aka ports).
Our rom is built for being flashed by this recovery, because this recovery is the only compiled one. Unfortunately, there's nothing which can be done without ulefone updating the kernel source code.
Click to expand...
Click to collapse
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...

Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Ug..
GPL source code is provided on our Metal thread...
https://github.com/MediatekAndroidDevelopers/android_kernel_ulefone_metal
Cheers
M.A.D. Team

Jonny said:
Provide me with the device source to build this recovery from then, instead of hiding your source in a private bit bucket repo. I'm Jonathon Fitch, the guy who's source you probably based yours on. The least you could do is share...
Click to expand...
Click to collapse
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk

DerTeufel1980 said:
Of course we didn't build upon your kernel. Why should we have done this?
We are using your recovery, or more detailed, we are suggesting to use your recovery.
What's your problem? We did not disrespect you in any way.
Sent from my Thor using Tapatalk
Click to expand...
Click to collapse
^^ THIS

[RECOVERY][Hiae] TWRP touch recovery

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
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 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
Click to expand...
Click to collapse
Device Changelog
Current version: 3.5.1_9-0:
Initial official release - no device-specific changes
Click to expand...
Click to collapse
Older Device-specific versions:
3.3.1-1:
Update prebuilt kernel to support both stock and LOS decryption
3.2.0-1:
[Fix] Re-sync build tree so recovery boots
[Update] Source-built kernel with f2fs/ntfs/exfat support
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Downloads
Download
Latest Official versions
Latest Unofficial versions
Sources
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
N/A
TWRP Upstream
Encrypted backups are broken - DO NOT USE THIS FEATURE!!
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. 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

TWRP Official Change Log
Current version: 3.5.1:
TeamWin has prepared a mini release before Android-11 support.
Android 9 Branch only:
Build fixes in 7.1 tree - CaptainThrowback
SAR Update script name for clarity - CaptainThrowback
SAR: Don't follow symbolic links for block devices - bigbiff
Android 9 and Android 10 Branches:
Wrappedkey support running only on FBE devices - CaptainThrowback
TWRP App log information reduced - epicX67
Refresh details after system wipe and adb sideload - AdrianDC
Chinese translation updates - betaxb
Support keymaster 2 - PeterCxy
add tzdata to TWRP for timezones - CaptainThrowback
ParitionManager: support delayed adopted storage mount - PeterCxy
Support to start terminal from file manager directory - AndroiableDroid
Nano support - nebrassy
Add nano support to open files from file manager - CaptainThrowback
Include new magisk apk support to be installed by TWRP - ianmacd
Add support to change directory name where TWRP stores backups - epicX67
Add bash support - not the default shell - DarthJabba9
ORS support to format data - AdrianDC
Add support to flash both slots when flashing an image - epicX67
NL translation updates - ianmacd
Cleanup
Installation cleanup - remove dupe PackageExtractFn - klabit87
Remove logd-reinit service - CaptainThrowback
Fixes
Restore system root context - bigbiff
Only include keymaster 2 if tree supports it - CaptainThrowback
Strip lines containing '--' in language_helper.py - ianmacd
Unlocalized string fix - ianmacd
Click to expand...
Click to collapse
Older versions:
3.5.0:
For this release we are breaking down new support for devices based on android trees and device compatibility. For Pie and earlier devices, they will be built out of the android-9.0 branch. For devices that
are released with Android Version 10, they will be supported under the android-10 branch. The separation became apparent when a lot of functionality was dropped in the android-10 release last year.
You will notice a new version scheme. Devices that are built in the android-9 tree will be suffixed with 3.5.0_9.
Devices built in the android-10 tree will be suffixed with 10 like 3.5.0_10. Each device tree update will have a
final suffix for any updates made for the device like 3.5.0_10-1.
Android 9 only
Fix building in android-5.1 trees - CaptainThrowback
New QTI Haptics Support - AndroidableDroid
New TSPDriver Haptics Support - LameMonster82
Selinux restore issues - AndroidableDroid
OEM build fixes - Fighter19
More file extension support in Gui file selector - Mauronofrio
FBE Fixes - CaptainThrowback
Ozip Decryption - Mauronofrio
Don't use persist for recovery logs - bigbiff
Delay touch startup if necessary - bigbiff
Spanish translation Updates - R0rt1z2
Fix cache wiping on Slot A only devices - AndroidableDroid
Exclude dumpsys directory from backups - DarthJabba9
Gerrman translation Updates - 4ndyZ
HW Rotation during runtime (does not affect touch panel) - webgeek1234
API 24 fixes - AndroidableDroid
vold_decrypt error on unmount - CaptainThrowback
Multiuser - warn when users are not decrypted - noahajac
FDE encryption fixes - CaptainThrowback
Crypto state fixes - nebrassy
Chinese translation Updates - Whyle
Theme updates to match android-10 release: CaptainThrowback
Move TWRP App install to Advanced page - Dees_Troy
Update Russian Translation - f2065
Android 10
Omni 10 minimal support: CaptainThrowback
General Bringup: Bigbiff, Mauronofrio, AndroidableDroid, CaptainThrowback, ianmacd, DarthJabba9
Encryption support: Bigbiff, Mauronofrio, CaptainThrowback
Fastbootd support: Bigbiff
Install Support: Bigbiff, CaptainThrowback
Magisk Support: Bigbiff
Backuptool Support: Chaosmaster
Apex support: Bigbiff
Dynamic Partition Support: Bigbiff
3.4.0:
System As Root (SAR)
Fix backup and restore using SAR - dianlujitao
System mount point - Chaosmaster
ORS - Chaosmaster
Zip install - Chaosmaster
system_root bind mount to /system - Chaosmaster
Autodetection of SAR - Chaosmaster
Digest
fix creation of digests for sub-partitions (was bugfix applied to many devices since last year) - Bigbiff
Encryption
ext4Crypt Wrapped Key Update - Peter Cai
Fix upgrading encryption key if export fails - Peter Cai
Fix wrapped key support for devices without metadata partition - mauronofrio
Don't skip decryption when using block map file in order to write to /data in ORS - CaptainThrowback
FDE - Decrypt master key first - AndroidableDroid
vold_decrypt - set Android version and patch level automatically - CaptainThrowback
Set wrapped decrypt support by twrp flag - Peter Cai
Don't try wrapped support unless needed - mauronofrio
restore ext4 policy on /data/cache - Bigbiff
multiuser decryption - Noah Jacobson
FDE retry - AndroidableDroid
TWRP App
unmount system after checking for app - Bigbiff
Prebuilt updates
[email protected] - cryptomilk
Compilation Fixes
TW_EXFAT_FUSE compilation fixes - Bigbiff
libuuid - cryptomilk
'system/etc/ld.config.txt' not found error - Martin Dünkelmann
Language Updates
Portugal - Vasco Machado
Dutch - Ian Macdonald
Turkish - Fatih Fırıncı
Localisation of Backup_Tar - Ian Macdonald
ld.config.txt
updates for 8.x trees - CaptainThrowback
fix search path for /sbin - CaptainThrowback
/sbin should come first in search path - Ian Macdonald
General Bugs
Fix persistent log storage - SyberHexen
Compress Persistent Logs - Bigbiff
FB2PNG compilation errors - Bigbiff
exclude per_boot from backups - Darth9
Unmount all directories that point to same block device - AndroidableDroid
Blank screen fixes - Sean hoyt
Toolbox is default on android-9+ - mauronofrio
Cleanup
Typo fix in comment - VDavid003
newlines in ext4crypt - CaptainThrowback
TW_OEM_BUILD compilation issue - Patrick Zacharias
Fix Dependency requirements - Dees_Troy
Fix Symbolic links for BB and Toolbox - Dees_Troy
Bootloader Message
cleanup - Alessandro Astone
add configurable offsets
Error Cleanup
uevent errors and decryption error - mauronofrio
using copy_file to copy files from /etc - CaptainThrowback
ueventd access to /acct - early directory creation in init - cryptomilk
Haptics
TSP Driver - LameMonster82
QTI Input - AndroidableDroid
update_engine
read all asserts - Hernán Castañón
Resetprop
Add Resetprop from Magisk - CaptainThrowback & mauronofrio
compile from source - Chaosmaster
fix for android-7 and earlier - Chaosmaster
cleanup for spaces in properties - AndroidableDroid
Properties
Add Property override - Chaosmaster
Backuptool
mount system and vendor for A/B installs for backuptool - Chaosmaster
twrpTar
fix backup freezes when pigz and openaes are used - Fabrice Bellet
Zip Installs
Info for A/B zip installing to inactive slot - Chaosmaster
Reboot to system button now allows to be rebooted to different partitions after zip install
progressbar rework - Chaosmaster
Magisk updates
update binaries from source - AndroidableDroid
A/B Updater Zip Template
rewrite A/B installer zip from scratch using a new generic template and latest magiskboot - osm0sis
installer zip support for recovery_a/recovery_b partition ramdisks on newer 2SI SAR A/B devices - osm0sis
generate installer zips for all prod A/B devices - bigbiff
improve installer zip dump/write speed and add more error catching - arter97 & osm0sis
OZIP Encryption Support
add OZIP encryption - mauronofrio
File Selector
Support for more extensions in File Selector - mauronofrio
3.3.1:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
3.3.0:
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (nijel8, CaptainThrowback)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
3.2.3:
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
3.2.2:
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
3.2.1:
minui fixes (cryptomilk)
Better android-8.0 compatibility in ROM trees (Dees_Troy)
Fix missing library in android-8.0 (nkk71)
Fix inconsistent SDCard naming (DevUt)
Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
3.2.0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
3.1.1:
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)
3.1.0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
3.0.3:
Partial release to help support the release of the Official TWRP app
3.0.2:
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.
3.0.1:
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
3.0.0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Additional Notes
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!
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)
Additional Notes
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.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Had to recreate this thread as the original version got lost when the forum got flattened.

Here is my log, could you check it please?
h**ps://www.filedropper.com/recovery_4
I had to slightly modify the link to be able to insert it.
Thanks
@Captain_Throwback
I forgot, when he created the log the usual errors appeared even if he says created successfully ..

fabulas_ said:
Here is my log, could you check it please?
h**ps://www.filedropper.com/recovery_4
I had to slightly modify the link to be able to insert it.
Thanks
@Captain_Throwback
I forgot, when he created the log the usual errors appeared even if he says created successfully ..
Click to expand...
Click to collapse
Please don't post pictures of your phone screen. The recovery log is sufficient. If you feel like you really have to give me a screenshot, please use Power+Volume Down to capture a proper screenshot.
As I told you in the other thread, to use the "Copy Log" feature, you need to switch the storage to your SD card first, since your "regular" storage isn't working properly.
Please try the TWRP linked below and let me know if you still see errors. If you do, please attach another recovery log, and also provide the output of
Code:
adb logcat > logcat.txt
https://drive.google.com/file/d/1VcYhdSIuX-8OazWcpP3JVXgpYezHo0OY/view?usp=sharing
Thanks.
P.S. Please provide recovery log even if it's working, actually.
P.P.S. Also, there's no need to mention me, as you're posting in my thread so I will be notified.

Captain_Throwback said:
Please don't post pictures of your phone screen. The recovery log is sufficient. If you feel like you really have to give me a screenshot, please use Power+Volume Down to capture a proper screenshot.
As I told you in the other thread, to use the "Copy Log" feature, you need to switch the storage to your SD card first, since your "regular" storage isn't working properly.
Please try the TWRP linked below and let me know if you still see errors. If you do, please attach another recovery log, and also provide the output of
Code:
adb logcat > logcat.txt
https://drive.google.com/file/d/1VcYhdSIuX-8OazWcpP3JVXgpYezHo0OY/view?usp=sharing
Thanks.
P.S. Please provide recovery log even if it's working, actually.
P.P.S. Also, there's no need to mention me, as you're posting in my thread so I will be notified.
Click to expand...
Click to collapse
It is not clear to me how to mount the microsd as internal memory ....
I go to Mount, in the screen that appears which folders should I select? microsd card and cache are selected by default.
the check on "Mount system partition read-only" I leave it?
and then I tap on "Mount Usb Storage"?
another question the recovery you gave me should I load it and try it only after loading the usb as internal memory?
I'm sorry for the many questions but I would like to avoid making mistakes otherwise the problem becomes even more complicated.

fabulas_ said:
It is not clear to me how to mount the microsd as internal memory ....
I go to Mount, in the screen that appears which folders should I select? microsd card and cache are selected by default.
the check on "Mount system partition read-only" I leave it?
and then I tap on "Mount Usb Storage"?
another question the recovery you gave me should I load it and try it only after loading the usb as internal memory?
I'm sorry for the many questions but I would like to avoid making mistakes otherwise the problem becomes even more complicated.
Click to expand...
Click to collapse
I didn't say to mount the SD card as internal memory - I just said to select it as default storage, as in Mount -> Select Storage -> choose "Micro SD Card" -> click OK. When you do that, TWRP will copy logs to the card instead of the broken internal storage. You don't need to touch anything else.
It doesn't matter whether you do that before or after flashing the new TWRP. Please just flash it and provide the recovery log.

Captain_Throwback said:
I didn't say to mount the SD card as internal memory - I just said to select it as default storage, as in Mount -> Select Storage -> choose "Micro SD Card" -> click OK. When you do that, TWRP will copy logs to the card instead of the broken internal storage. You don't need to touch anything else.
It doesn't matter whether you do that before or after flashing the new TWRP. Please just flash it and provide the recovery log.
Click to expand...
Click to collapse
I did exactly as you said
> Select Storage -> choose "Micro SD Card" -> click OK.
and then I went back without tapping on Mount usb storage. I tried to create the log always with the twrp I had and always the same errors it gives me ...
Then I put your TWRP, always done Mount> Select Storage -> choose "Micro SD Card" -> click OK. and then I created the log and it always gives me the same errors
Here is the log
h**p://www.filedropper.com/recovery_5
I didn't understand how to retrieve the logcat.txt file

fabulas_ said:
I did exactly as you said
> Select Storage -> choose "Micro SD Card" -> click OK.
and then I went back without tapping on Mount usb storage. I tried to create the log always with the twrp I had and always the same errors it gives me ...
Then I put your TWRP, always done Mount> Select Storage -> choose "Micro SD Card" -> click OK. and then I created the log and it always gives me the same errors
Here is the log
h**p://www.filedropper.com/recovery_5
I didn't understand how to retrieve the logcat.txt file
Click to expand...
Click to collapse
You have to use adb (from your PC) to retrieve the logcat, using the command I gave you.
But after looking at your log, it seems that you need to Format Data in TWRP. Wipe -> Format Data -> type "yes". Then reboot into Android and back to TWRP. Please let me know if that resolves your issue.

Captain_Throwback said:
You have to use adb (from your PC) to retrieve the logcat, using the command I gave you.
But after looking at your log, it seems that you need to Format Data in TWRP. Wipe -> Format Data -> type "yes". Then reboot into Android and back to TWRP. Please let me know if that resolves your issue.
Click to expand...
Click to collapse
I made a format data and I solved the errors .. now he doesn't make them + ... and this is already a very important first step .. I was sure that with you I would have solved it since you are the leader of the experts.
The weird thing I am wondering is when flashing the RUU doesn't it automatically do a format data? because the RUU I flashed it I don't know how many times and this problem was always present.
I'll put here a log made now after making the format data
http://www.filedropper.com/recovery_6
Still need the logcat file?
Now the famous screen that appeared to me every time whether to allow changes to the file system or keep read-only has also disappeared, and every time I selected "keep read-only" now it is not appearing +.
Now what do I do, I put Magisk v21 on sd and then from TWRP I install it? when I installed it yesterday, as I told you, it gave me the usual errors on the Twrp during installation even if he had installed Magisk Manager but the root was not done. checking the SafetyNet also the basic integrity was false as well as the CTS ... now I hope that installing it there are no errors, I assume not, and that the SafetyNet at least the basic integrity does not become false otherwise Magisk hide does not work for me ... and I'm interested in being able to use the banking apps .. I'm waiting for your message so I proceed based on what you tell me to do.
If you prefer we can return to the other thread.
thanks a lot

fabulas_ said:
I made a format data and I solved the errors .. now he doesn't make them + ... and this is already a very important first step .. I was sure that with you I would have solved it since you are the leader of the experts.
The weird thing I am wondering is when flashing the RUU doesn't it automatically do a format data? because the RUU I flashed it I don't know how many times and this problem was always present.
I'll put here a log made now after making the format data
http://www.filedropper.com/recovery_6
Still need the logcat file?
Now the famous screen that appeared to me every time whether to allow changes to the file system or keep read-only has also disappeared, and every time I selected "keep read-only" now it is not appearing +.
Now what do I do, I put Magisk v21 on sd and then from TWRP I install it? when I installed it yesterday, as I told you, it gave me the usual errors on the Twrp during installation even if he had installed Magisk Manager but the root was not done. checking the SafetyNet also the basic integrity was false as well as the CTS ... now I hope that installing it there are no errors, I assume not, and that the SafetyNet at least the basic integrity does not become false otherwise Magisk hide does not work for me ... and I'm interested in being able to use the banking apps .. I'm waiting for your message so I proceed based on what you tell me to do.
If you prefer we can return to the other thread.
thanks a lot
Click to expand...
Click to collapse
Yes, you can flash Magisk from TWRP, and then when you boot into Android, you have to open Magisk Manager settings and enable MagiskHide if you want to pass SafetyNet.

Captain_Throwback said:
Yes, you can flash Magisk from TWRP, and then when you boot into Android, you have to open Magisk Manager settings and enable MagiskHide if you want to pass SafetyNet.
Click to expand...
Click to collapse
Installed Magisk did not give me errors on Twrp, I checked the root with Root Checker and it is done ... the big problem is that as I expected now the Safetynet as basic integrity gives me "false" while before installing Magisk it gave me " true "checked with the" SafetyNet attest "app ... even the CTS is false, in this way I don't do anything about the root since I can't deprive myself of the various banking apps ... but how is it possible that the basic integrity before installing Magisk is okay and then after installing it does not pass the check? ....

fabulas_ said:
Installed Magisk did not give me errors on Twrp, I checked the root with Root Checker and it is done ... the big problem is that as I expected now the Safetynet as basic integrity gives me "false" while before installing Magisk it gave me " true "checked with the" SafetyNet attest "app ... even the CTS is false, in this way I don't do anything about the root since I can't deprive myself of the various banking apps ... but how is it possible that the basic integrity before installing Magisk is okay and then after installing it does not pass the check? ....
Click to expand...
Click to collapse
Did you enable MagiskHide like I said?

Captain_Throwback said:
Did you enable MagiskHide like I said?
Click to expand...
Click to collapse
sorry I had tapped on magisk hyde in the home and I thought it was that ... now I have activated it in the settings and redone the check and everything went ok ... I thank you immensely for helping me solve the problem.
so in the end I didn't have the damaged memory but a farmat data was enough ... as TWRP I can leave the one you gave me equally true?

fabulas_ said:
sorry I had tapped on magisk hyde in the home and I thought it was that ... now I have activated it in the settings and redone the check and everything went ok ... I thank you immensely for helping me solve the problem.
so in the end I didn't have the damaged memory but a farmat data was enough ... as TWRP I can leave the one you gave me equally true?
Click to expand...
Click to collapse
Yes, you can keep the one I gave you. It has some updates that won't be merged until the next official version, so enjoy!

Captain_Throwback said:
Yes, you can keep the one I gave you. It has some updates that won't be merged until the next official version, so enjoy!
Click to expand...
Click to collapse
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?

fabulas_ said:
Ok perfect .. very kind. Thanks.
Before unlocking the bootloader and then doing the root I had a space problem as the internal memory is only 16gb ... now since the phone is still fine I wanted to find a solution.
And I saw that through the Link2SD app I can move some apps to the microsd (maybe the apps I use less), to do this I read that you have to make a partition in the microsd so that you can move the apps and that it is seen as "an extension of the internal memory" ... so I should connect the microsd to the pc to create the partition ... then there is another way which is to format the microsd as internal memory but this is not recommended ... while instead do as I wrote before a partition in the microsd and use it as an "extension of the internal memory" do you think it is a good solution to solve the app space problem? because I only have the apps in the internal memory ... the media are automatically saved on microsd ... so in theory by making a partition in the microsd the partition is an extension of the internal memory and the non-partitioned part should be used by the camera to save photos and videos .. do you think it's feasible?
One last thing as an app to remove the various system apps that I don't use like some Google apps, now that I have root I can do it ... which app do you recommend to do this?
Click to expand...
Click to collapse
Titanium Backup or Oandbackupx.

My phone keep restarting after install twrp.

@andmars
I saw your post in the LOS thread and I believe several people have reported that 3.5.0 is the last version that boots for you. I just reset the device tree back to that version to see whether it's something I did that broke it (although I'm not sure how that's possible). So the below link is a test version I just built that resets things back to that point. I saw only one flag that was changed, but it's not one that should be relevant to the device booting or not. But if this works, I'll have to re-evaluate. Please try it at your earliest convenience, and if you know anyone else with the same issue, please direct them here to test as well.
twrp-3.6.0_9-0_CPTB-20211226-01-hiae.img
drive.google.com

Captain_Throwback said:
@andmars
I saw your post in the LOS thread and I believe several people have reported that 3.5.0 is the last version that boots for you. I just reset the device tree back to that version to see whether it's something I did that broke it (although I'm not sure how that's possible). So the below link is a test version I just built that resets things back to that point. I saw only one flag that was changed, but it's not one that should be relevant to the device booting or not. But if this works, I'll have to re-evaluate. Please try it at your earliest convenience, and if you know anyone else with the same issue, please direct them here to test as well.
twrp-3.6.0_9-0_CPTB-20211226-01-hiae.img
drive.google.com
Click to expand...
Click to collapse
Ahoi Captain,
I tested you version of 3.6.0 and it didn't boot. I get the red warning text, then a few seconds of blank screen after which it boots into normal os.
Greets
A