[RECOVERY][hydrogen/helium] TWRP 3.1.0-0 for Xiaomi Mi Max

Search This thread

TheStrix

Recognized Developer
May 10, 2014
680
6,374
Mumbai
Team Win Recovery Project



This is a unified build for both the Mi Max (hydrogen) and the Mi Max Prime (helium)

WHAT IS TWRP?

Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

Read more about TWRP here: https://twrp.me/about/

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.

FEATURES:
  • MTP support
  • USB OTG storage support
  • Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
  • f2fs file system support (read, write, format, backup & restore)
  • Covers more partitions for nandroid backup (fstab)
  • ADB root
  • Full SELinux support
  • Built with android 7.1 tree

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]

CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/

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

Contributors
TheStrix
Source Code: https://github.com/TeamWin


Version Information
Status: Stable

Created 2017-03-04
Last Updated 2017-03-12
 

TheStrix

Recognized Developer
May 10, 2014
680
6,374
Mumbai
Reserved

FAQ:

WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?

Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.

WHY DOES F2FS MAKE TWRP SO SLOW?

When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!

HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?

To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log

This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)

If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
 
Last edited:

pawwaap

Senior Member
Dec 4, 2016
402
40
For now, please download the build from:
v3.0.3-rc1: https://www.androidfilehost.com/?w=files&flid=155934
(...)
Last Updated 2017-03-04

You say this unified built for HELIUM & HYDROGEN.
However the very file from this link has name:

"twrp-3.0.3-rc1-hydrogen.img"

and thus it suggests this is HYDROGEN version,
will it work on HELIUM too indeed?

And, BTW, will it work on locked bootloader?

HELIUM 364GB ;) locked BL, Nigel's
[ROM][UNOFFICIAL][7.1.1][HYDROGEN/HELIUM]LineageOS 14.1
 
Last edited:

Voyebanm

Senior Member
Oct 29, 2012
188
31
Ottawa
Unable to flash TWRP

Hi,
can anyone help, I tried installing the new TWRP 3.1 and get the Blank screen. Now the only version that I can install is " TWRP-3.0.3-MROM-hydrogen-002.img " from the Multirom
Anything else Either the screen flashes and then the Phone reboots, but no Recovery

I tried to have Log and None found

C:\Minimal ADB and Fastboot>adb pull /tmp/recovery.log
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb: error: remote object '/tmp/recovery.log' does not exist

I have attached the dmesg.log file

Thanks in advance
 

Attachments

  • dmesg.zip
    98 KB · Views: 31
Last edited:

LiviiYS

Senior Member
Jun 14, 2016
92
11
Does twrp 3.1.0.0 work with 6.0.1 ROMs or only 7+ ROMs?

Sent from my Xiaomi MI MAX using XDA Labs
 

dumbninja

New member
Feb 2, 2017
2
0
Xiaomi Mi 11 Ultra
Unfortunately it seems that it didn't install on my phone even flashing went well
C:\>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19320 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.887s


When trying to boot on recovery I am having this (well known i think) image of a telephone with cable with pcsuite.mi.com written underneath

Any suggestions ?

thanks in advance
PS : My rom is Global Stable - V8.2.1.0.MBDMIDL. Phone is a Mi Max 128
 
Last edited:

fallen_

Senior Member
Unfortunately it seems that it didn't install on my phone even flashing went well
C:\>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19320 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.887s


When trying to boot on recovery I am having this (well known i think) image of a telephone with cable with pcsuite.mi.com written underneath

Any suggestions ?

thanks in advance
PS : My rom is Global Stable - V8.2.1.0.MBDMIDL. Phone is a Mi Max 128
Try another pc

Enviado desde mi Redmi Note 3 mediante Tapatalk
 

tarkzim

Recognized Developer
Feb 11, 2015
2,365
4,840
Kaohsiung
Sony Xperia Z
HTC One (m7)
Unfortunately it seems that it didn't install on my phone even flashing went well
C:\>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19320 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.887s


When trying to boot on recovery I am having this (well known i think) image of a telephone with cable with pcsuite.mi.com written underneath

Any suggestions ?

thanks in advance
PS : My rom is Global Stable - V8.2.1.0.MBDMIDL. Phone is a Mi Max 128

after the first time you flashed this,
you have to boot into recovery directly when you type fast reboot, that's means you have to hold Volume-UP while you typing that.
if you don't, then original recovery will be installed again.
 
  • Like
Reactions: nxgar

dumbninja

New member
Feb 2, 2017
2
0
Xiaomi Mi 11 Ultra
after the first time you flashed this,
you have to boot into recovery directly when you type fast reboot, that's means you have to hold Volume-UP while you typing that.
if you don't, then original recovery will be installed again.

Thanks for tip.
I followed your operations: booting into recovery works correctly,TWRP shows up. But when booting on the system I'm stuck with the MI Logo and nothing happens.....
Any additional help ?
Thanks
 

Rockworld02

Senior Member
Mar 19, 2012
148
16
NoiDa
please help me my MI max 32Gb has been brick its stuck and restarting at Mi logo (vibration) please help me someone to unlock my mi max bootlader so that i can complete flash the whole firmware in MiFLASH . i have tried to flash the rom through Miflashing tool (download mode) but still it stuck and restarting at Mi logo.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Team Win Recovery Project



    This is a unified build for both the Mi Max (hydrogen) and the Mi Max Prime (helium)

    WHAT IS TWRP?

    Oh come on, you know what it is - don't try to fool me!
    In case you're serious, though...

    Team Win Recovery Project is a custom recovery for Android devices.
    It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

    Read more about TWRP here: https://twrp.me/about/

    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.

    FEATURES:
    • MTP support
    • USB OTG storage support
    • Hardware Qualcomm-based full-disk encryption support ( ext4 & f2fs )
    • f2fs file system support (read, write, format, backup & restore)
    • Covers more partitions for nandroid backup (fstab)
    • ADB root
    • Full SELinux support
    • Built with android 7.1 tree

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.[/QUOTE]

    CONTRIBUTIONS:
    Gerrit for TWRP: http://gerrit.omnirom.org/
    Gerrit for officially supported devices: http://gerrit.twrp.me/

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

    Contributors
    TheStrix
    Source Code: https://github.com/TeamWin


    Version Information
    Status: Stable

    Created 2017-03-04
    Last Updated 2017-03-12
    3
    Reserved

    FAQ:

    WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?

    Be patient, wait another 8 hours.
    Just kidding, try this while stuck on the loading screen:
    adb shell wipe_misc; adb shell reboot recovery
    Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
    This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
    Personally, I'd have tried this after 15 minutes.

    WHY DOES F2FS MAKE TWRP SO SLOW?

    When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!

    HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?

    To get logs while in TWRP, you should connect your device to your PC and use adb.
    adb pull /tmp/recovery.log
    adb exec-out dmesg > dmesg.log

    This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)

    If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
    adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
    3
    no version for helium?

    Title:
    [RECOVERY][hydrogen/helium] TWRP for Xiaomi Mi Max

    Second OP line:
    This is a unified build for both the Mi Max (hydrogen) and the Mi Max Prime (helium)
    1
    no version for helium?
    This is a unified build for both the Mi Max (hydrogen) and the Mi Max Prime (helium)
    1
    Unfortunately it seems that it didn't install on my phone even flashing went well
    C:\>fastboot flash recovery recovery.img
    target reported max download size of 536870912 bytes
    sending 'recovery' (19320 KB)...
    OKAY [ 0.772s]
    writing 'recovery'...
    OKAY [ 0.113s]
    finished. total time: 0.887s


    When trying to boot on recovery I am having this (well known i think) image of a telephone with cable with pcsuite.mi.com written underneath

    Any suggestions ?

    thanks in advance
    PS : My rom is Global Stable - V8.2.1.0.MBDMIDL. Phone is a Mi Max 128

    after the first time you flashed this,
    you have to boot into recovery directly when you type fast reboot, that's means you have to hold Volume-UP while you typing that.
    if you don't, then original recovery will be installed again.