[RECOVERY][oxygen][unofficial] TWRP 3.1.1-0 touch recovery [2017-08-07]

Search This thread

iscle

Senior Member
Apr 19, 2014
236
541
24
Barcelona
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.

IF YOU ARE USING STOCK MIUI ROM, THIS RECOVERY WILL BE OVERWRITTEN BY MIUI RECOVERY ON THE FIRST ROM BOOT! MAKE SURE YOU INSTALL ANOTHER ROM LIKE XIAOMI.EU BEFORE REBOOTING.
If you are using the STOCK MIUI ROM, you will need to remove the file "/system/recovery-from-boot.p" using the file manager inside TWRP or otherwise it will get replaced with the stock MIUI recovery.

Features:
This is the stock TWRP recovery without modifications.
It's ported from the Xiaomi Redmi Note 4 to our device. It doesn't have any changes apart from the necessary to make it work in the MI MAX 2.
Contrary to the one made by xuefer (the one I used until I compiled my own), this one doesn't ask you for the language every time you start it up, just like an official version of TWRP.

If you have any questions, leave them in a comment. Thanks!

Donations are welcome!

If you like my work, please consider donating to my paypal account: [email protected]
or by using this link: https://paypal.me/SelePDF

Thanks!

home.png
backupname.png


CHANGELOG for 3.1.1-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_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

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

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.

INSTRUCTIONS:
You can watch a video tutorial I did here: https://www.youtube.com/watch?v=xo2BPhw9qnM
OR:
1) Download the latest version from the download section below.
2) Make sure you have ADB and fastboot installed in your computer.
3) Put your phone into fastboot mode (Power off, then press POWER + Vol. down until the fastboot screen appears).
4) Connect the phone to your computer and open a command line.
5) Type the following commands (replace "recovery.img" with the path to your recovery.img file downloaded from below):
Code:
fastboot flash recovery recovery.img
fastboot reboot recovery
6) Done.
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 the download section below.
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
6) Done.

DOWNLOAD:7
If you are using the STOCK MIUI ROM, you will need to remove the file "/system/recovery-from-boot.p" using the file manager inside TWRP or otherwise it will get replaced with the stock MIUI recovery.
Mega: https://mega.nz/#!AfxWEa5L!DgxoCsgkoH3jS1o-FVHhe8HGsbZ5es6v4Szr3pmrQl0

BUGS:
N/A

XDA:DevDB Information
TWRP, Tool/Utility for the Xiaomi Mi Max 2

Contributors
iscle
Source Code: https://github.com/Iscle/android_device_xiaomi_oxygen_twrp


Version Information
Status: Beta
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-08-07

Created 2017-08-07
Last Updated 2017-08-19
 
Last edited:

fendetestasxx

Senior Member
Sep 21, 2012
89
29
Galicia
ZTE Axon 30
I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?
 

iscle

Senior Member
Apr 19, 2014
236
541
24
Barcelona
I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?

try to "fastboot boot recovery recovery.img" and then copy the recovery.img file to the sdcard and flash the recovery from twrp. Make sure you are replacing the "recovery.img" with the proper file location and name!!
 
Last edited:
  • Like
Reactions: Benoît Lagasse

ashwaa

Senior Member
Jun 10, 2008
927
91
mumbai
I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

I need help:

I already have the bootloader open, drivers installed and usb debugging enabled.

Fastboot devices: I recognize it
Fastboot flash recovery.img: ok in less than a second

Restart in recovery mode and I get the recovery of Miui.

Any idea what's going on?
The command is
Fastboot flash recovery recovery.img
 

ashwaa

Senior Member
Jun 10, 2008
927
91
mumbai
Did u unlock ur device
Is ur usb debugging enabled
Does ur adb detect ur device
What is the name of the recovery image
Ie is it twrp.img or recovery.img
Pls specify
If u r unlocked uur adb detects device then
fastboot flash recovery recovery.img or twrp.img should work
Open adb command in the folder where ur recovery image and fastboot exe is ie ur minimal adb folder
 

fendetestasxx

Senior Member
Sep 21, 2012
89
29
Galicia
ZTE Axon 30
Did u unlock ur device
Is ur usb debugging enabled
Does ur adb detect ur device
What is the name of the recovery image
Ie is it twrp.img or recovery.img
Pls specify
If u r unlocked uur adb detects device then
fastboot flash recovery recovery.img or twrp.img should work
Open adb command in the folder where ur recovery image and fastboot exe is ie ur minimal adb folder

Yes to everything. The bootloader unlocked yesterday, after waiting 72 hours. As you can see in the image of the previous post says to everything ok. I use the image of this post. But nothing.

My rom is Miui 8 Global 7.7.20 Beta.
 
Last edited:

2nutz4u

Member
Sep 1, 2009
12
2
Yes now. From here I entered TWRP and I was able to do everything. Thank you very much.
:eek:

I have the same issue but confused with the instruction. Do I open command prompt and type in fastboot boot twrp.img? If so won't this command just boot into twrp? I am trying to install twrp. Are these instruction for upgrading twrp?
 

zost

Senior Member
Sep 30, 2006
190
7
Yes, I can enter in TWRP that way (boot xxx.img etc...) but after reboot to system (Global developpers ROM) from TWRP it still boots in MIUI main menu.
So, I repeat the question of 2nutz4u: Is this TWRP and all assoiciated instructions for upgradingto another TWRP. Or more simple: is there a way to make it boot in iscle TWRP?
 

iscle

Senior Member
Apr 19, 2014
236
541
24
Barcelona
Yes, I can enter in TWRP that way (boot xxx.img etc...) but after reboot to system (Global developpers ROM) from TWRP it still boots in MIUI main menu.
So, I repeat the question of 2nutz4u: Is this TWRP and all assoiciated instructions for upgradingto another TWRP. Or more simple: is there a way to make it boot in iscle TWRP?

I just replied to you in the other thread, but anyway hahaha i will reply here again just so that it might be useful for other people. If you have stock miui rom it will be overwritten by the stock recovery for some reason, so you might want to use xuefer build if you are not using a custom rom like xiaomi.eu or lineage os.

EDIT: Quick fix: Remove the file "/system/recovery-from-boot.p" using the file manager inside twrp.
 
Last edited:

zost

Senior Member
Sep 30, 2006
190
7
The same is with xuefer buid - no TWRP after reboot - just MIUI menu.
And there is no recovery-from-boot.p file in system folder.
 

iscle

Senior Member
Apr 19, 2014
236
541
24
Barcelona
The same is with xuefer buid - no TWRP after reboot - just MIUI menu.
And there is no recovery-from-boot.p file in system folder.

Then the only option is to either flash another rom like xiaomi.eu (works very well) or just boot the recovery using the PC every time you want to use it...
 

tom.android

Senior Member
Jul 12, 2016
1,188
372
For Missing TWRP

1. fastboot flash recovery twrp.img
2.fastboot boot twrp.img
(waiting)
twrp running
From Menu: Wipe--->format data--->yes----Then reboot to recovery again.
3. you will find it.
 

Top Liked Posts

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

    IF YOU ARE USING STOCK MIUI ROM, THIS RECOVERY WILL BE OVERWRITTEN BY MIUI RECOVERY ON THE FIRST ROM BOOT! MAKE SURE YOU INSTALL ANOTHER ROM LIKE XIAOMI.EU BEFORE REBOOTING.
    If you are using the STOCK MIUI ROM, you will need to remove the file "/system/recovery-from-boot.p" using the file manager inside TWRP or otherwise it will get replaced with the stock MIUI recovery.

    Features:
    This is the stock TWRP recovery without modifications.
    It's ported from the Xiaomi Redmi Note 4 to our device. It doesn't have any changes apart from the necessary to make it work in the MI MAX 2.
    Contrary to the one made by xuefer (the one I used until I compiled my own), this one doesn't ask you for the language every time you start it up, just like an official version of TWRP.

    If you have any questions, leave them in a comment. Thanks!

    Donations are welcome!

    If you like my work, please consider donating to my paypal account: [email protected]
    or by using this link: https://paypal.me/SelePDF

    Thanks!

    home.png
    backupname.png


    CHANGELOG for 3.1.1-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_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

    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

    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.

    INSTRUCTIONS:
    You can watch a video tutorial I did here: https://www.youtube.com/watch?v=xo2BPhw9qnM
    OR:
    1) Download the latest version from the download section below.
    2) Make sure you have ADB and fastboot installed in your computer.
    3) Put your phone into fastboot mode (Power off, then press POWER + Vol. down until the fastboot screen appears).
    4) Connect the phone to your computer and open a command line.
    5) Type the following commands (replace "recovery.img" with the path to your recovery.img file downloaded from below):
    Code:
    fastboot flash recovery recovery.img
    fastboot reboot recovery
    6) Done.
    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 the download section below.
    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
    6) Done.

    DOWNLOAD:7
    If you are using the STOCK MIUI ROM, you will need to remove the file "/system/recovery-from-boot.p" using the file manager inside TWRP or otherwise it will get replaced with the stock MIUI recovery.
    Mega: https://mega.nz/#!AfxWEa5L!DgxoCsgkoH3jS1o-FVHhe8HGsbZ5es6v4Szr3pmrQl0

    BUGS:
    N/A

    XDA:DevDB Information
    TWRP, Tool/Utility for the Xiaomi Mi Max 2

    Contributors
    iscle
    Source Code: https://github.com/Iscle/android_device_xiaomi_oxygen_twrp


    Version Information
    Status: Beta
    Current Beta Version: 3.1.1-0
    Beta Release Date: 2017-08-07

    Created 2017-08-07
    Last Updated 2017-08-19
    2
    Can you please add that after you flashed the recovery you have to flash no-verity-opt-encrypt in twrp or else the phone won't boot? I couldn't find anything in your post nor in the comments.

    you shouldn't need to do so unless you write something in the /system partition. It's a known MIUI "feature/bug/however you want to call it"
    2

    Screenshots are already there... Anyway, it's just stock TWRP, so what else do you want to see?
    1
    I need help:

    I already have the bootloader open, drivers installed and usb debugging enabled.

    Fastboot devices: I recognize it
    Fastboot flash recovery.img: ok in less than a second

    Restart in recovery mode and I get the recovery of Miui.

    Any idea what's going on?

    ---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

    I need help:

    I already have the bootloader open, drivers installed and usb debugging enabled.

    Fastboot devices: I recognize it
    Fastboot flash recovery.img: ok in less than a second

    Restart in recovery mode and I get the recovery of Miui.

    Any idea what's going on?

    try to "fastboot boot recovery recovery.img" and then copy the recovery.img file to the sdcard and flash the recovery from twrp. Make sure you are replacing the "recovery.img" with the proper file location and name!!
    1
    First of all: use this: fastboot boot twrp.img
    then Wipe--->format data--->yes----reboot
    Now You're good to go