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

Search This thread

Lyuu

Senior Member
May 1, 2016
274
970
0
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

Code:
-- 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:

Code:
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
 
Last edited:

jer194

Senior Member
Feb 23, 2014
1,001
722
133
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.
 

jer194

Senior Member
Feb 23, 2014
1,001
722
133
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:
Code:
fastboot boot recovery.img
 
Last edited:
Jan 3, 2016
6
0
0
Ujjain
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:
Code:
fastboot boot recovery.img

Thanks! Would definitely try out this twrp!
 

ebol94

Senior Member
Aug 10, 2011
227
96
58
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

Senior Member
Feb 6, 2012
2,003
5,715
203
Colchester, VT
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.
 

_nomercy_

Member
Apr 28, 2017
8
2
13
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.
 
  • Like
Reactions: BeadyBead

Top Liked Posts

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

    Code:
    -- 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:

    Code:
    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
    6
    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.
    5
    Do you plan on making TWRP 3.4?

    I have compiled (and tested) twrp-3.4.0-0_athene-arm64.img, using Lyuu's device tree.

    UI doesn't seem to be very different, nevertheless: changelog
    Timestamp for backups seem to be fixed (was always wrong in my previous version).

    A word of caution: at the end of compilation it said
    Code:
    error: +Android/Build/Out/twrp-9.0/target/product/athene/recovery.img too large (16795648 > 16777216)

    To try it out, this should be safe enough (while in bootloader):
    Code:
    fastboot boot twrp-3.4.0-0_athene-arm64.img
    4
    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.
    2
    Sorry, guys, can anyone point me to the arm-Version? Following the download link in the OP I can only find the arm64 version. (Screenshot attached)
    Thanks and stay healthy!

    https://androidfilehost.com/?a=show&w=files&flid=303150
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone