FORUMS
Remove All Ads from XDA
H10 Turbo

[RECOVERY][Xiaomi Mi Max][hydrogen] TWRP 3.0.2-0 touch recovery

37 posts
Thanks Meter: 40
 
By Abdess76, Member on 28th May 2016, 10:25 PM
Post Reply Email Thread
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.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!

CHANGELOG for 2.8.7.0:

-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)

Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

DOWNLOAD:
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.

BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
The Following 9 Users Say Thank You to Abdess76 For This Useful Post: [ View ] Gift Abdess76 Ad-Free
 
 
31st May 2016, 02:40 PM |#3  
Junior Member
Thanks Meter: 1
 
More
twrp decrypt password?
what is decrypt password?

please help..
The Following User Says Thank You to beaver21c For This Useful Post: [ View ] Gift beaver21c Ad-Free
3rd June 2016, 02:28 PM |#4  
OP Member
Thanks Meter: 40
 
More
Quote:
Originally Posted by Hogyoku

has anyone had the chance to try this out ?

Yes, and it works well.

Quote:
Originally Posted by beaver21c

what is decrypt password?
please help..

It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)

To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it
The Following 4 Users Say Thank You to Abdess76 For This Useful Post: [ View ] Gift Abdess76 Ad-Free
3rd June 2016, 03:13 PM |#5  
Hogyoku's Avatar
Senior Member
Flag Dordrecht
Thanks Meter: 212
 
More
Quote:
Originally Posted by Abdess76

Yes, and it works well.


It's because of the dm-verity protection included in the MIUI firmwares.
To disable it, you have to:
- Format all encrypted partitions on fastboot (fastboot format system; fastboot format userdata;...)
- Boot on TWRP and flash a MIUI recovery image
- Download this patched boot file
- On fastboot flash the patched boot.img (fastboot flash boot boot-patched.img)

To manually remove the protection from a kernel you have to:
- Extract boot.img from a rom/device
- Unpack it, with this tool for example -> mkbootimg_tools
- Search the fstab file (fstab.qcom for example) and remove the "verify" mention and replace all "forceencrypt" mentions by "encryptable"
- Repack it and flash it

Wouldt the latest super su do this already since it repacks the original boot img and patches the dm-verity ?

Thanks for the recovery and boot.img btw !
The Following 2 Users Say Thank You to Hogyoku For This Useful Post: [ View ] Gift Hogyoku Ad-Free
4th June 2016, 01:01 PM |#6  
OP Member
Thanks Meter: 40
 
More
Quote:
Originally Posted by Hogyoku

Wouldt the latest super su do this already since it repacks the original boot img and patches the dm-verity ?

Thanks for the recovery and boot.img btw !

Yes, SuperSu do this already and it works well!

You're welcome.
The Following User Says Thank You to Abdess76 For This Useful Post: [ View ] Gift Abdess76 Ad-Free
5th June 2016, 01:49 AM |#7  
alexecus's Avatar
Senior Member
Thanks Meter: 45
 
More
Just a question though, given that Mi Max has identical hardware to Redmi Note 3 pro, is it possible to use custom roms of the latter ? Or does it require some porting ?
5th June 2016, 11:50 AM |#8  
OP Member
Thanks Meter: 40
 
More
Quote:
Originally Posted by landono5

Just a question though, given that Mi Max has identical hardware to Redmi Note 3 pro, is it possible to use custom roms of the latter ? Or does it require some porting ?

The Mi Max has some similarities with the Redmi Note 3 Pro but it's, unfortunately, not identical. Kenzo roms can't work directly on Mi Max.
5th June 2016, 09:05 PM |#9  
sam razzy's Avatar
Senior Member
Flag Ma sweet home
Thanks Meter: 594
 
More
how to unlock the bootloader on mi max ?
5th June 2016, 09:56 PM |#10  
OP Member
Thanks Meter: 40
 
More
Quote:
Originally Posted by sam razzy

how to unlock the bootloader on mi max ?

Like all Xiaomi phones, here: http://en.miui.com/unlock/

How-to: http://en.miui.com/thread-202290-1-1.html (No need to flash a developer rom before)
The Following User Says Thank You to Abdess76 For This Useful Post: [ View ] Gift Abdess76 Ad-Free
7th June 2016, 02:05 AM |#11  
nijel8's Avatar
Senior Member
All over US
Thanks Meter: 5,069
 
Donate to Me
More
My Mi Max is already waiting for me to get home this weekend... Already got unlock permission from Xiaomi so I am all set for playing with my new toy. I will be unlocking bootloader, flash TWRP and root it.
So few questions... I don't have to worry about all encrypted fs? SuperSu will take care of them? Do I have to fastboot format userdata first? Is the internal /sdcard partition encrypted?
Not very familiar with all this fs encryption thing.
Let's hope we get some good custom ROM for this device soon... AOSP, CM, whatever...
Post Reply Subscribe to Thread

Tags
hydrogen, mi max, mi-max, recovery, twrp, xiaomi

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes