[RECOVERY][UNOFFICIAL][EFS][ARM/ARM64][3.3.1-0] Team Win Recovery Project

[Lyuu]

Team Win Recovery Project 3.3.1-0​

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.

Features

-- build 5 --
* ARM build
* Encryption blobs from OPJ28.111-22

-- build 4 --
 * Removed busybox until is officially added into twrp

-- build 3 --
 * Added system_image
 * Added busybox

-- build 2 --
 * Fixed encryption
 * Rebased tree, cleaned it up
 * Removed Treble

-- build 1 --
 * EFS backup (fsc, fsg, modem, persist in one option)
 * Treble support (mount /oem as /vendor)

Flashing guide

In bootloader/fastboot mode:

fastboot flash recovery <recovery_name.img>

Downloads

Here

XDA:DevDB Information
Team Win Recovery Project, ROM for the Moto G4 Plus

Contributors
Lyuu
Source Code: https://github.comLyuu17/android_device_motorola_athene

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x

Version Information
Status: Stable

Created 2018-09-15
Last Updated 2019-11-04

 

[GuestK00473]

ha ha, first reply

 

[rahulsj92]

Can we flash non-treble ROMs or do we have to revert to previous non-treble recovery?

 

[jer194]

Can we flash non-treble ROMs or do we have to revert to previous non-treble recovery?

I'd say you have all options, no need to go back.

If you flash a non-treble ROM, it will contain a boot.img which boots the old way, without dependency on the vendor.img.
If you flash a treble ROM, you need to have flashed a specific treble boot.img plus a vendor.img before you reboot.

 

[Kartik Shankhavaram]

Is it as stable as a non-treble recovery or it has some bugs?

 

[jer194]

Is it as stable as a non-treble recovery or it has some bugs?

Afaik: Super-stable, nothing to worry about.
It just adds the option to flash to certain partitions (Vendor or OEM), and to backup those.
otherwise there is nothing specific for treble.
About bugs: for sure it has bugs, like any piece of software (nothing significant that I am aware of though).

You can try it without flashing. In fastboot mode, do this:

fastboot boot recovery.img

 

[Kartik Shankhavaram]

Afaik: Super-stable, nothing to worry about.
It just adds the option to flash to certain partitions (Vendor or OEM), and to backup those.
otherwise there is nothing specific for treble.
About bugs: for sure it has bugs, like any piece of software (nothing significant that I am aware of though).

You can try it without flashing. In fastboot mode, do this:

fastboot boot recovery.img

Thanks! Would definitely try out this twrp!

 

[arun4777]

great work
all the best for treble

 

[alvintimothyjr]

Has anyone successfully installed a treble based rom with this recovery?

 

[mannered_hooligan]

I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??

 

[Lyuu]

I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??

Both ways

 

[mannered_hooligan]

Both ways

Thanks .. I'll try this recovery and ArrowOS after my exam

 

[guillaumedsde]

Hey, so I'm not sure if decryption is working in this recovery? I tried decrypting my data partition (encrypted from lineageOS 14.1) but it claims the password is incorrect (despite the fact that the same password decrypts the partition OK with shreps' TWRP) does decryption work for anyone?

 

[alvintimothyjr]

I guess this recovery can be installed through Rajat's twrp or is it necessary to install through PC??

Yup. Generally, recovery versions overwrite your current version.

 

[ebol94]

Could anybody help me? I'm facing the following issue:


E:\XT1641\Flashear\root\twrp-3.2.3-0>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (15390 KB)...
OKAY [ 0.493s]
writing 'recovery'...
(bootloader) Image not signed or corrupt

OKAY [ 0.123s]
finished. total time: 0.621s

 

[Jleeblanch]

Could anybody help me? I'm facing the following issue:


E:\XT1641\Flashear\root\twrp-3.2.3-0>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (15390 KB)...
OKAY [ 0.493s]
writing 'recovery'...
(bootloader) Image not signed or corrupt

OKAY [ 0.123s]
finished. total time: 0.621s

The (bootloader) Image not signed or corrupt message is nothing to worry about. At that point, you should just need to choose to reboot to recovery from the bootloader menu and all should be ok.

 

[Ekaksh Janweja]

ETA?

 

[corlatemanuel]

ETA?

Trolling 100

 

[_nomercy_]

Does somebody else also has wrong date/time set in this TWRP version? I'm at the typical 1970/01/01 date.

I found Issue 640 in the official TWRP Github project itself - sorry I cannot post external links due to restrictions - but its rather old from 2016 although people have still reported this as being an issue last year. Actually I cannot imagine that this is (still) a problem for everyone though this issue is still open.

 

[[email protected]]

987654