Develop Bugs

TeamWin Recovery Project v2.8.7.0

Latest TWRP version for Optimus G [E975/F180X]
What is new in 2.8.7.0:
Code:
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)
Download:
TWRP v2.8.7.0
How to install:
Code:
- turn your phone into bootloader mode
- connect phone with pc
- using fastboot flash recovery "fastboot flash recovery recovery.img"
- reboot
Screenshot:
Credits:
Omni Team
Kevinjoa
XDA:DevDB Information
TW, Tool/Utility for the LG Optimus G
Contributors
DevSwift1
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Beta
Created 2015-07-18
Last Updated 2015-07-18

good job

Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...

M.M.K said:
Sir Devswift1
I got a problem. I bump philz & cwm for optimus g locked bootloader & go to them easily with hardreset.
But for twrp, every time I try to go to it, it performs a factory reset!
Can you please make one without this problem?
So we can use all kinds of recovery with bump...
Click to expand...
Click to collapse
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working

DevSwift1 said:
This recovery support only unlocked bootloader..
about flash my AOSP rom you can try with cwm but I am not sure if all will be working
Click to expand...
Click to collapse
Actually I have used your twrp. But only with reboot to recovery through running os!
Then it wont perform factory reset. But what if I get bootloop?anytime? Kdz...
I mean thats how G3 users enter to twrp! But we cant!
I hoped you could fix it Please try
Thank you anyway. I'm gonna flash your perfect rom with unlocked boot loader

Try Jollaman twrp.
Also Jollaman twrp is multirom compatible.
Enviado do meu Optimus G através de Tapatalk

Hey im new to this how i install this i used before to unlock boot via freegee?

the download link is broken

mi_guel69 said:
the download link is broken
Click to expand...
Click to collapse
Flashable zip - dont remember who made it sorry
http://www.multiupfile.com/f/02f8982a

Pls, fix link at the top. Thx

this is very old now... use this https://mirrors.c0urier.net/?dir=android/Dadi11/TWRP

[Recovery] [OFFICIAL] TWRP 3.1.0.0 (img)

downloads: https://dl.twrp.me/mocha/twrp-3.1.0-0-mocha.img.html

Could you add to the topic name that this is for mocha aka Mi Pad 1. Cheers mate.
Change log:
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/androidbootablerecovery/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
Click to expand...
Click to collapse

yes, its ONLY for MI Pad 1 (mocha)

What would be the easiest way to flash this though.

Looking for this?
https://twrp.me/devices/xiaomimipad.html
Well... flash via old twrp seems to be the easiest, but I personally in favor of fastboot flash tho.

Official TWRP for mocha is unstable for my MiPAD.
3.0.2 => backup or tar might generate corrupt file ranodomly
3.1.0 => test some backup, work fine now, but tar files in external_sd to external_sd will get I/O error.
for my mipad, the most table twrp is mejor's 3.0.0 version.

unpack and repack official twrp 3.1.0-0 for mocha, replace the kernel in mejor's twrp 3.0.0 (I think this is the global MIUI 7.3 kernel image).
this fix the official twrp's sdcard issue for me.

does reboot to recovery work

Which TWRP is better?
I have a Samsung Galaxy A5 2015 SM-A500FU Model and I want to Flash TWRP with Odin to root my phone. My problem are the different Versions of TWRP. I found "twrp_3.0.2-1_sm-a500.tar" (14,4MB) and "twrp-v3.1.0-0_a500.tar" (14,2MB). These both files have different sizes. The newer one has a smaller size than the older one. Is that normal?
So which one should i install?

CurryPlayer said:
I have a Samsung Galaxy A5 2015 SM-A500FU Model and I want to Flash TWRP with Odin to root my phone. My problem are the different Versions of TWRP. I found "twrp_3.0.2-1_sm-a500.tar" (14,4MB) and "twrp-v3.1.0-0_a500.tar" (14,2MB). These both files have different sizes. The newer one has a smaller size than the older one. Is that normal?
So which one should i install?
Click to expand...
Click to collapse
If it's for your device then it should not create any problem,
Flash any and if you think 3.0.2.0 is better than flash it,

Can we flush this from flashify app ?

skrewie said:
Can we flush this from flashify app ?
Click to expand...
Click to collapse
You can use the official twpr app forma download and install
Enviado desde mi MI PAD mediante Tapatalk

unpack and repack official twrp 3.1.1-0 for mocha, replace the kernel with global MIUI 7.3 kernel image.
this fix the external sdcard issue for me.

Impressive. I will try it later.

working for s4 i9505 ?

[RECOVERY][UNOFFICIAL]TWRP 3.1.0-0 touch recovery For LG G3(D851)-Only [2017-03-16]

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.
SCREENSHOT IS IN ATTACHMENT
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_b...863b15c16949d9 (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
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:
Download TWRP for D851 from here : twrp-3.1.0-0-D851-Unofficial.img
TWRP MATERIAL THEMES :
here => https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584​
CREDIT :
TeamWin Recovery Project
Android Matrix Development [https://web.facebook.com/groups/1024872487548231/]
Obaid Muneer
Nickron Davis
Sandeep Sethi
DroidPeepz_Inc.

Seems to work okay but when I try to use aroma I get a reboot.

cidxtc said:
Seems to work okay but when I try to use aroma I get a reboot.
Click to expand...
Click to collapse
Okay, I will look into it.
Thanks for notifying me

iykeDROID™ said:
Okay, I will look into it.
Thanks for notifying me
Click to expand...
Click to collapse
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.

cidxtc said:
I know that on previous versions I had to use the older cm14 kernel instead of the new for aroma to work.
Click to expand...
Click to collapse
If you don't mind, can you upload that older cm14 kernel?
Thanks

iykeDROID™ said:
If you don't mind, can you upload that older cm14 kernel?
Thanks
Click to expand...
Click to collapse
Everything is on my pc which is dead right now.

cidxtc said:
Everything is on my pc which is dead right now.
Click to expand...
Click to collapse
Sorry about that bro.
Anyway i still try my best

error
Installed but does not start recovery

flako72 said:
Installed but does not start recovery
Click to expand...
Click to collapse
please make sure device is D851

iykeDROID™ said:
please make sure device is D851
Click to expand...
Click to collapse

I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%

RockNRoll Mullet said:
I tried updating twrp and now I lost supersu so I can not reinstall twrp 3.0.2.0. How do I get supersu & twrp installed again? It still boots to RR is just missing SuperSu & twrp. I tried LG newest root method and it fails at restarting. I tried to manually put in download mode and it ends with "failed" I tried to install supersu.apk it says binary not installed. LG Newest root method v03 fails at 45%
Click to expand...
Click to collapse
Do you have any recovery installed?

No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.

RockNRoll Mullet said:
No. I can't reinstall twrp 3.0.2.0 with flashify because is says SuperSU has no binary installed. I lost SuperSU when I use Flashify to install twrp 3.1.0.0 I get error no binary installed. When I try volume & power to start recovery I get LG boot screen then RR 7.1.1 boots. No stock recovery either.
Click to expand...
Click to collapse
I have used the 3.1 twrp and had no issues. Not sure what happened but sounds like you might need to restore a stock rom via tot or kdz files and a pc. Then root and flash twrp.
FYI if your restore to stock all files on internal storage will be deleted so backup any pics/files to your pc before restore.

Witch kdz file should I use. Will down grading from RR 7.1.1 to lollipop or marshmallow be a problem? Will lollipop be be easier to reroot?

I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.

iykeDROID™ said:
I don't know why some other guys are facing my TWRP 3.1.0-0 boot issue.
pls make sure your are on T-Mobile-D851.
Also it uses a Nougat kernel.
Click to expand...
Click to collapse
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.

cidxtc said:
I was thinking the same "make sure you are on T-mobile-d851" also but did not say it because some people here get a little ruffled.
Click to expand...
Click to collapse
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon

iykeDROID™ said:
True though, Thanks :good: for that
Well, am still working of fix for Aroma File Manager as it keeps hanging then reboot to system.
hoping to fix soon
Click to expand...
Click to collapse
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices

cidxtc said:
Are you using a precompiled kernel? If so try the one found here https://github.com/Eliminater74/multirom_g3_devices
Click to expand...
Click to collapse
Thanks.
I compile new kernel for use each time i want to work on it

[TWRP-3.1.1] Unofficial TWRP for the UMI SUPER

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.1.1-0:
-waiting for official docs, looks like any thread has been updated.. Nor official website
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: doc (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
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
Download:
3.1.0: Google Drive
3.1.1: Android File Host
XDA:DevDB Information
Unofficial TWRP for the UMI SUPER, Tool/Utility for all devices (see above for details)
Contributors
joe2k01
Source Code: https://github.com/joe2k01/android_device_umi_SUPER/tree/TWRP
Version Information
Status: Testing
Created 2017-03-19
Last Updated 2017-05-14

Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.

Problem with TWRP
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
Same problem !
any solutions :crying:

Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.

rexbauru said:
Same problem as the friends above @SerialFlasher33 and @gayfagxxx .
I transfer the TWRP successfully via sp flash tool, pore at the time of loading anything on the screen nothing.
Already tried several versions of TWRP.
Here I have android 7 already with update.
Click to expand...
Click to collapse
SerialFlasher33 said:
Same problem !
any solutions :crying:
Click to expand...
Click to collapse
gayfagxxx said:
Flashing said OK in Flash Tool but nothing is different in power+volup or power+voldown.
Using the latest March rom from their forum.
Click to expand...
Click to collapse
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power

could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx

megthebest said:
could you also share this new build here?
https://forum.xda-developers.com/general/general/umi-install-custom-recovery-twrp-cwm-t3385733
any scatter file provided to flash it via Flashtool?
thnx
Click to expand...
Click to collapse
You can use the stock ROM's scatter file

joe2k01 said:
You can use the stock ROM's scatter file
Click to expand...
Click to collapse
I know my friend, it's not for me but for all users that can be in trouble without scatter provided (if they come from stock Umi Super).
So is only a suggestion..
thanks anyway

joe2k01 said:
You must boot in TWRP exactly after flashing it: Flash in SPFT then start pressing volup and then press power
Click to expand...
Click to collapse
Thanks, this worked.
I used the latest march rom on my phone and loaded the scatter from the same rom. I obtained the rom file and the flash tool on the UMi forums.
Then I un-ticked everything and changed the location to the recovery, pressed download, shutdown my phone, waited for it to be done, unplugged it, held volup+power and now it works.

Unfortunately for me it does not work ... I tried to start immediately the phone into recovery but after a short flash the display starts the system stock umi

@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?

joe2k01 said:
@bastard81 can you try to connect your phone(powered on) and from adb type adb reboot recovery ?
Click to expand...
Click to collapse
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support

bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
I guess you some how corrupted recovery partition, try to backup your IMEIs and then try the option format all+reflash on SPFT. You'll lose IMEI

worked well with me (Y)

Hi joe2k01 from the forum 4PDA. Thanks for the work. Put Your TWRP3.1.0 through TWRP3.0.2 and tested on firmware v7.01_20170123. While there are no errors.

Cant Get into Anything But TWRP
I Flashed Twrp, Twrp works fine, just nothing else. Even flashed a rom and have no boot just twrp.
TIA

joe2k01 said:
Team Win Recovery Project 3.x
Click to expand...
Click to collapse
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...

jemmini said:
you ****ing young hacker. you need to make reference to the authors , when you take other people's files...
Click to expand...
Click to collapse
WTF is wrong with you man? You are in the credits list on GitHub. I took only your kernel since you are anti-opensource and don't want to explain how you built it.

bastard81 said:
I tried, but even this system seems to not work. The phone will restart, and for a moment I see the display flashing. After it starts immediately with the system but without going into recovery ...
I do not know what else to try .. From the developer options have also enabled the oem unlock. Also tried without. Reinstalled 3 times with spflashtool and everything works perfectly. But the recovery just does not want to work.
Ps thanks for your support
Click to expand...
Click to collapse
The same for me

Im on stock v3.02_20161121 odex from silent27 had TWRP 3.02 and just flashed TWRP 3.1.1 super img. over and it worked just fine.
On top of that flashed a twrp theme(310x v.2 hdpi light play theme by z31s1g) wich on TWRP 3.02 themes didnt worked for me.

[SHARE] Official TWRP 3.4.0-0 for woods MediaTek (Updated)

. The full changelog
5G
OnePlus 6T
Win a Mi 9
Honor View20
Honor Hub
Android Q
Galaxy Note 9
LG V40
Snapdragon 855
Pixel 3
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
TWRP 3.3.1+ will no longer require installer ZIPs, adds a reboot to EDL mode button, and more
For most users, installing any kind of after-market software modification, whether it be a custom ROM, custom kernel, or other tool, requires the use of a custom recovery like TWRP. TWRP has been around for years as the go-to recovery solution for the XDA community. It’s open source and supports hundreds of devices. It offers features like full backup and restore, ADB sideloading, and much more. Today, the project has been bumped to version 3.3.1-0, bringing many improvements in decryption, new features, and a major change to the way TWRP is installed.
The full changelog outlining the many improvements in TWRP’s decryption support can be found below, but for users, the most important change will be the new way to install the custom recovery. Currently, installing TWRP on a device with A/B partitions requires booting TWRP temporarily and then installing it permanently using an installer script. Going forward, users will be presented with a new “install recovery ramdisk” option in recovery. This means that users can boot TWRP and then install it without downloading a separate ZIP file. XDA Senior Recognized Developer Dees_Troy worked with XDA Recognized Developer topjohnwu to make this possible by adapting Magisk‘s boot image patching for TWRP. Dees_Troy says the team will offer installer ZIPs this time around to give people a chance to update from older versions, but future TWRP releases won’t have separate installer scripts.
The other change that’s most relevant to users is the inclusion of a “reboot to EDL mode” button. Emergency Download mode can help you fully unbrick a device if you have the right tool, but the button combination to enter it isn’t as well known to users as the reboot to recovery method.
Here’s the full changelog for the update:
TWRP 3.4.0-0 Changelog
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 (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP
Developers behind (Dees_Troy with thanks to topjohnwu of course)
Directory Access
https://eu.dl.twrp.me/woods/
https://eu.dl.twrp.me/woods/twrp-3.4.0-0-woods.img
Fair warning don't restore previous backups from other versions of TWRP make a fresh one first[/SIZE]
:good:

Finally,a dev to keep woods alive

Well done good job sir. We support you. Contribute to moto e4 more.

Does it support the official OTA updates?

nabirosama said:
Does it support the official OTA updates?
Click to expand...
Click to collapse
Yes if your previous version is. From official channel

Abish4 said:
Yes it your previous version is. From official channel
Click to expand...
Click to collapse
On my device it is Software Channel "reteu", should be supported?
The original patch level is on my device october 2018, i think we can not expect updates from the manufacturer any longer.

I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
fastboot boot twrp-3.3.1-0-woods.img
downloading 'boot.img'...
OKAY [ 0.509s]
booting...
OKAY [ 0.068s]
finished. total time: 0.577s
Click to expand...
Click to collapse
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762

I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops

Spielmops said:
I never try to boot TWRP with fastboot.I always flash it and everything is good. If you need a backup of the recovery partion, you can do that via adb. Everthing else can be backup'ed by TWRP.
Spielmops
Click to expand...
Click to collapse
The recovery backup would be some kind of a fail save, if twrp will not boot. If the direct boot would work, I had more faith. :fingers-crossed:
How can I backup the recovery over adb?
I found this:
https://android.stackexchange.com/questions/132314/can-we-backup-the-stock-recovery-img-in-any-way
But I still need root and I can not flash magisk without twrp (and system backup).
Update:
However, because it is working by others, i tried flash recovery twrp-3.3.1-0-woods.img (official), it seems to work.
Creating full backup now ...

Have a look here: https://android.stackexchange.com/questions/205354/show-adb-backup-manual

hi, I have the same problem (XT1761), any idea? thank you
maven33 said:
I unlocked my phone, but fastboot boot twrp-3.3.1-0-woods.img is not booting into recovery. After entering the command in fastboot mode, the device is just restarting.
(Device unlocked message appears, so this should not be a problem.)
Source:
https://dl.twrp.me/woods/twrp-3.3.1-0-woods.img
I need to make a full backup before flashing. Is this twrp not working with fastboot boot ... ?
Device Moto E4, woods, XT1762
Click to expand...
Click to collapse

hi, I have the same problem (XT1761), any idea? thank you
Click to expand...
Click to collapse
hi, I have the same advice ...
Spielmops

hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Spielmops said:
hi, I have the same advice ...
Spielmops
Click to expand...
Click to collapse

hitman72 said:
hi, solved (even if I don't know why)...
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
Did you even try to disable verified boot ?
cause thats the almost every time with boot images on newer or updated devices..

The bootloader was unlocked in by activating USB-debugging, EOM-Unlock in the developer settings. In fastboot mode , only "fastboot oem unlock".
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.

dm verity disable
maven33 said:
I used the twrp-3.3.1-0-woods.img on my Moto E4 (XT1762) woods. This version worked, but I could not start twrp without a flashing it.
Click to expand...
Click to collapse
If you are moving from stock rom and locked device u need to unlock with official key or you can just format your device data... DMVERITY must be disabled at all cost or you have to flash entire stock software update to be running.
See or check post relating to disabling verity in FASTBOOT mode (probably zip) also reboot recovery after flashing.
:fingers-crossed:

hitman72 said:
hi, solved (even if I don't know why)...
extracted "boot.img" from "[ROM][STOCK][TWRP] Original Stock Firmware-(woods) - TWRP Restore [ROOTED]"
boot.img link https://mega.nz/#!I9cSQC7D!44B_MFvW1wwB3VSF09P1C4-82dqY2i21INNVICFajac
and flashed it
fastboot flash boot boot.img
THEN flashed recovery (I used twrp-3.3.1-0-woods.img, but no matter what you use)
fastboot flash recovery twrp.img
NOW I am working recovery and just flashed a custom rom
Click to expand...
Click to collapse
The mega link isn't working. Can you please update the link to the file.