[MOD] [hydrogen] TWRP 3.1.0 + MultiROM v33 (NO-KEXEC) [UNOFFICIAL]

Search This thread

jackeagle

Forum Moderator- Rec Dev - Dev Relations.
Staff member
  • Apr 11, 2013
    3,384
    9,015
    XDA
    vh3puLb.png

    Note : Not Tested on Helium hence not supported
    Introduction

    MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi Max (Hydrogen). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.​

    This is still very experimental!

    This has been tested with most popular Rom's of Xiaomi Mi Max (Android MM and N based).

    *Please, keep in mind that if you've updated to latest N firmware in your primary ROM, you won't be able to boot MM as secondary any more. If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N. If you are on N Firmware then only ROMs built with N blobs will work in MultiROM.

    Make backups. Seriously. Please.

    Features:
    * Multiboot any number of Android ROMs
    * Restore nandroid backup as secondary ROM
    * Boot from USB drive (Not yet implemented)

    Warning!

    It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​

    Installation
    1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
    This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
    Press "Install" on the Install/Update card to start the installation.

    2.Manual installation
    Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.

    MultiROM has 3 parts you need to install:

    • Modified recovery - download the IMG file from second post and use fastboot to flash it.
    • Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the boot.img and flash it in recovery by selecting image flash and flash it to boot parition. This can be avoid using no-kexec workaround in latest MultiROM versions.
    • MultiROM - download the ZIP file from second post and flash it in recovery.


    Your current ROM will not be erased by the installation.

    Adding ROMs
    Android
    • Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
    • Once Installation is complete. Go to MultiRom --> List Rom's --> Select the installed secondary Rom --> Remove Boot.img
    • Done!


    Using USB drive
    During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
    If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
    If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
    Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
    Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​

    Updating/changing ROMs

    1. Primary ROM (Internal)

    • Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
    • Flash Kexec-hardboot patched kernel (either the kernel linked in second post or any third party kernel which supports kexec-hardboot (NOT needed when using no-kexec workaround in TWRP -> MultiROM Settings)
    • Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
    2. Secondary Android ROMs
    If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:

    • Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
    • Select "Flash ZIP" and flash ROM's ZIP file.

    Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.

    Source code
    MultiROM - https://github.com/multirom-hydrogen/multirom
    Modified TWRP - https://github.com/multirom-hydrogen/Team-Win-Recovery-Project
    Kernel w/ kexec-hardboot patch - https://github.com/multirom-hydrogen/kernel_xiaomi_msm8956
    Device tree - https://github.com/multirom-hydrogen/android_device_xiaomi_hydrogen

    Credits
    • This work is based on the hard work of @Tassadar (MultiROM), @nkk71 (no-kexec), 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, @jackeagle, Hashbang173, and many others. Thank you.
    • My Team mates @k2wl @Rohan purohit @TechExhibeo @Vatsal. (Thank you very much guys! :))

    Issues
    • MIUI is not supported (You should be able to boot MIUI as secondary with latest release if you're still using a MM firmware in your primary ROM).
    • USB OTG Support is not yet Implemented and will be done in future releases. (It should work in latest releases)

    - If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it on the specific repo in question.

    - IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.

    NOTE:
    Third party kernel developers if you have merged Kexec-hardboot support kindly PM me linking to your kernel sources with confirmation about the working. So that I can add your kernel here in supported kernel list :)

    Extra Information

    I ask that no one build targeting the Xiaomi Mi Max using our source and post it publicly ( distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!

    XDA:DevDB Information
    MultiRom-Xiaomi Mi Max (Hydrogen), Tool/Utility for the Xiaomi Mi Max

    Contributors
    jackeagle, BitOBSessiOn
    Source Code: https://github.com/multirom-hydrogen


    Version Information
    Status: Stable
    Current Stable Version: Stable 1
    Stable Release Date: 2016-12-20
    Current Beta Version: NO-KEXEC version
    Beta Release Date: 2017-01-14

    Created 2016-12-20
    Last Updated 2017-03-25
     

    jackeagle

    Forum Moderator- Rec Dev - Dev Relations.
    Staff member
  • Apr 11, 2013
    3,384
    9,015
    XDA
    Changelogs

    Changelogs

    Code:
    [COLOR="Blue"]
    [SIZE="4"]24/03/2017
    - Updated TWRP to 3.1.0 Release
    -  MultiROM and TWRP Upstream Updates
    - [URL="https://forum.xda-developers.com/showpost.php?p=71576938&postcount=40"]More info about release![/URL]
    
    02/03/2017
    - Finally fixed Lockscreen security bug fixed
    - MultiROM and TWRP Upstream Updates
    - [URL="https://forum.xda-developers.com/showpost.php?p=71254611&postcount=24"]More info about release[/URL]
    
    19/01/2017
    - MR Upstream Updates merged
    - Merged with latest TWRP Changes
    - Updated MR TWRP to 3.0.3-1 Release
    
    15/01/2017
    - Added MIUI Support (Limited Support kindly read OP and Release notes for further details)
    - Updated to Latest MR No Kexec v33
    - Updated MR TWRP to 3.0.3 Release
    - Fixed USB OTG Support
    - Added Minimal Tree
    
    
    20/12/2016
    - Initial Release
    [/SIZE][/COLOR]
     
    Last edited:

    BitOBSessiOn

    Senior Member
    TWRP 3.0.3 + MultiROM v33 (NO-KEXEC) Available

    Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.

    You can download latest releases from here.

    NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.

    If you are still using MM firmware on primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).

    This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.

    Thx to @TechExhibeo and @jackeagle for their support.

    Feedback welcome.
     
    Last edited:

    TechExhibeo

    Recognized Contributor
    Sep 8, 2012
    1,269
    1,436
    25
    Ropar
    hybrideon.com
    Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.

    You can download latest releases from here.

    NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.

    If you are still using MM firmware in primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).

    This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.

    Thx to @TechExhibeo and @jackeagle for their support.

    Feedback welcome.

    Good Job Sir.

    Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
    If you are on N Firmware then only ROMs built with N blobs will work in MR
    You cannot boot different firmware ROMs in MR to boot :v
    ^ NON-KEXEC Multrirom

    Thank you.
    -TechExhibeo
     
    • Like
    Reactions: BitOBSessiOn

    BitOBSessiOn

    Senior Member
    Good Job Sir.

    Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
    If you are on N Firmware then only ROMs built with N blobs will work in MR
    You cannot boot different firmware ROMs in MR to boot :v
    ^ NON-KEXEC Multrirom

    Thank you.
    -TechExhibeo

    Thx for clarification, OP updated :) :good:
     

    BitOBSessiOn

    Senior Member
    TWRP 3.0.3-1 + MultiROM v33 (20170118)

    Downloads:
    • TWRP 3.0.3-1 available here.
    • MultiROM v33 (20170118) available here.

    Changelog:

    Code:
    commit 53f72b7563c6cf358c5088246ad3af0899327df5
    Author: bigbiff bigbiff <[email protected]>
    Date:   Thu Dec 8 21:21:17 2016 -0500
    
        TWRP device version string
        
        For building through jenkins. Export a variable to the shell
        so that we don't monkey patch variables.h and keep the git tag
        clean in the version string.
        Jenkins will export the variable TW_DEVICE_VERSION=n where n > 0.
        The makefile will use this variable to show the device string
        in twrp startup. For mass production builds, omit the
        environment variable to default to 0.
        
        Change-Id: I0d6eb764255d7069c0fb4a378522a009cfe4054f
    
    commit 94e5a23dd2f12c2cfca8beb9dadbde92820b1d55
    Merge: 78f6699 7dde36d
    Author: nkk71 <[email protected]>
    Date:   Sat Jan 14 16:13:41 2017 +0200
    
        Merge remote-tracking branch 'upstream/android-7.1' into android-7.1-mrom
    
    commit 7dde36df119a1ed0089b999641b27dc2c2a5280d
    Author: sndnvaps <[email protected]>
    Date:   Tue Oct 4 18:09:37 2016 +0800
    
        updater: link libcrypto_utils_static if it exist
        
        Change-Id: I9bf238a3e29d88850a6cc69f07954949722c35d7
        Signed-off-by: sndnvaps <[email protected]>
    
    commit 1c28904749f5d0ae58b113b5b59901f7fc3731f6
    Author: D. Andrei Măceș <[email protected]>
    Date:   Fri Dec 16 16:01:56 2016 -0500
    
        libtar: Use relative path for crypto/ext4crypt include
        
        Don't assume path to be bootable/recovery (i.e., support CM's
        RECOVERY_VARIANT).
        
        Change-Id: Ib53cc919c5a9beb3beee71d7227a7c957a24b601
    
    commit 1021edf17ed57f193724a953dd159e7717e9553a
    Author: nailyk-fr <[email protected]>
    Date:   Sun Dec 18 14:32:25 2016 +0100
    
        bootloader_message: Allow TWRP to ignore wipe-data command into misc
        
         * Rebase of https://gerrit.omnirom.org/#/c/20750/ patch-set 3
         * Original commit message:
        
        fix: recently a change in AOSP causes a bootloop to TWRP
        (and therefore all ROM's based on it)
        Reason: AOSP enables use of /misc partition and normally the fstab in
        TWRP will not have /misc added. The problem is now when Android writes
        a wipe command to /misc it will force TWRP to boot but TWRP will do
        nothing - leaving the cmd in /misc. This results in a bootloop to TWRP.
        Solution: I added a new var TW_IGNORE_MISC_WIPE_DATA which can be
        set to "true" in Boardconfig.mk of a device requiring this which then
        ignores /misc commands like it would be when /misc would be just not in
        fstab BUT with this change TWRP clears the bit in /misc so a normal boot
        can happen.
        Besides that if the device do not have an own recovery key combo and
        /misc is enabled we want to open TWRP after walking through the factory
        reset screen - without actually doing a factory reset.
        kudos to nailyk (and DevUt) for the help with the C++ code!
        
        Change-Id: If6fed5872015f1a66304e3edbdb787c507236f69
    
    commit dcd1e440e009b7861f09e2b718ea489bdcea34b5
    Author: James Christopher Adduono <[email protected]>
    Date:   Sun Nov 6 13:17:34 2016 -0500
    
        Support theme width and height offsets
        
        Current use condition is LG V20, where the secondary screen is
        actually just a corner chunk of the main screen.
        In this case, we need to shift the UI down some pixels in order
        to see it all, but just using Y offsets resulted in losing
        the rest of the GUI below.
        
        Example in BoardConfig.mk:
          # Shift TWRP off the secondary screen
          TW_Y_OFFSET := 160
          TW_H_OFFSET := -160
        
        Change-Id: I5a06638ba0d05e5b9fd8a6245c630d6ea3394f78
    
    commit b29a5e27c33291f8134ea5f28e84e672a3c25199
    Author: D. Andrei Măceș <[email protected]>
    Date:   Thu Dec 22 06:19:44 2016 -0500
    
        build: Consolidate the crypto_utils presence tests
        
        No point checking filesystem repeatedly/check may change in future
        
        Change-Id: I0413b07b850f785eb5150c6ed18836cc56e94d6f
    
    commit 4767caf1f4cd08cdc7d58476bc017dca17870112
    Author: Ethan Yonker <[email protected]>
    Date:   Wed Jan 11 10:45:04 2017 -0600
    
        Fix compile error on 4.4 tree
        
        Change-Id: Id85fdf0f4dee02f8ee3ae50ec42423c6a154a3eb
     

    Rohan purohit

    Senior Member
    Mar 25, 2014
    661
    2,409
    Pune
    Downloads:
    TWRP 3.0.3-1 available here.
    MultiROM v33 (20170118) available here.


    Changelog:
    Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9

    https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c

    Secondly ,
    Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine
     
    • Like
    Reactions: sky1994 and paarkhi

    BitOBSessiOn

    Senior Member
    Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9

    https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c

    Secondly ,
    Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine
    Interesting, I will revise. Thx!
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 16
      vh3puLb.png

      Note : Not Tested on Helium hence not supported
      Introduction

      MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi Max (Hydrogen). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.​

      This is still very experimental!

      This has been tested with most popular Rom's of Xiaomi Mi Max (Android MM and N based).

      *Please, keep in mind that if you've updated to latest N firmware in your primary ROM, you won't be able to boot MM as secondary any more. If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N. If you are on N Firmware then only ROMs built with N blobs will work in MultiROM.

      Make backups. Seriously. Please.

      Features:
      * Multiboot any number of Android ROMs
      * Restore nandroid backup as secondary ROM
      * Boot from USB drive (Not yet implemented)

      Warning!

      It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​

      Installation
      1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
      This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
      Press "Install" on the Install/Update card to start the installation.

      2.Manual installation
      Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.

      MultiROM has 3 parts you need to install:

      • Modified recovery - download the IMG file from second post and use fastboot to flash it.
      • Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the boot.img and flash it in recovery by selecting image flash and flash it to boot parition. This can be avoid using no-kexec workaround in latest MultiROM versions.
      • MultiROM - download the ZIP file from second post and flash it in recovery.


      Your current ROM will not be erased by the installation.

      Adding ROMs
      Android
      • Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
      • Once Installation is complete. Go to MultiRom --> List Rom's --> Select the installed secondary Rom --> Remove Boot.img
      • Done!


      Using USB drive
      During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
      If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
      If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
      Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
      Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​

      Updating/changing ROMs

      1. Primary ROM (Internal)

      • Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
      • Flash Kexec-hardboot patched kernel (either the kernel linked in second post or any third party kernel which supports kexec-hardboot (NOT needed when using no-kexec workaround in TWRP -> MultiROM Settings)
      • Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
      2. Secondary Android ROMs
      If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:

      • Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
      • Select "Flash ZIP" and flash ROM's ZIP file.

      Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.

      Source code
      MultiROM - https://github.com/multirom-hydrogen/multirom
      Modified TWRP - https://github.com/multirom-hydrogen/Team-Win-Recovery-Project
      Kernel w/ kexec-hardboot patch - https://github.com/multirom-hydrogen/kernel_xiaomi_msm8956
      Device tree - https://github.com/multirom-hydrogen/android_device_xiaomi_hydrogen

      Credits
      • This work is based on the hard work of @Tassadar (MultiROM), @nkk71 (no-kexec), 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, @jackeagle, Hashbang173, and many others. Thank you.
      • My Team mates @k2wl @Rohan purohit @TechExhibeo @Vatsal. (Thank you very much guys! :))

      Issues
      • MIUI is not supported (You should be able to boot MIUI as secondary with latest release if you're still using a MM firmware in your primary ROM).
      • USB OTG Support is not yet Implemented and will be done in future releases. (It should work in latest releases)

      - If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it on the specific repo in question.

      - IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.

      NOTE:
      Third party kernel developers if you have merged Kexec-hardboot support kindly PM me linking to your kernel sources with confirmation about the working. So that I can add your kernel here in supported kernel list :)

      Extra Information

      I ask that no one build targeting the Xiaomi Mi Max using our source and post it publicly ( distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!

      XDA:DevDB Information
      MultiRom-Xiaomi Mi Max (Hydrogen), Tool/Utility for the Xiaomi Mi Max

      Contributors
      jackeagle, BitOBSessiOn
      Source Code: https://github.com/multirom-hydrogen


      Version Information
      Status: Stable
      Current Stable Version: Stable 1
      Stable Release Date: 2016-12-20
      Current Beta Version: NO-KEXEC version
      Beta Release Date: 2017-01-14

      Created 2016-12-20
      Last Updated 2017-03-25
      5
      Downloads

      Downloads (NO-KEXEC)

      MR Installer App: Play Store Link
      (Still Not Supported for Hydrogen, working on it...)

      TWRP 3.1.0 (MultiROM modded): Latest here

      MultiROM v33 Installer Flashable ZIP: Latest here

      MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip
      5
      TWRP 3.0.3 + MultiROM v33 (NO-KEXEC) Available

      Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.

      You can download latest releases from here.

      NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.

      If you are still using MM firmware on primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).

      This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.

      Thx to @TechExhibeo and @jackeagle for their support.

      Feedback welcome.
      4
      Changelogs

      Changelogs

      Code:
      [COLOR="Blue"]
      [SIZE="4"]24/03/2017
      - Updated TWRP to 3.1.0 Release
      -  MultiROM and TWRP Upstream Updates
      - [URL="https://forum.xda-developers.com/showpost.php?p=71576938&postcount=40"]More info about release![/URL]
      
      02/03/2017
      - Finally fixed Lockscreen security bug fixed
      - MultiROM and TWRP Upstream Updates
      - [URL="https://forum.xda-developers.com/showpost.php?p=71254611&postcount=24"]More info about release[/URL]
      
      19/01/2017
      - MR Upstream Updates merged
      - Merged with latest TWRP Changes
      - Updated MR TWRP to 3.0.3-1 Release
      
      15/01/2017
      - Added MIUI Support (Limited Support kindly read OP and Release notes for further details)
      - Updated to Latest MR No Kexec v33
      - Updated MR TWRP to 3.0.3 Release
      - Fixed USB OTG Support
      - Added Minimal Tree
      
      
      20/12/2016
      - Initial Release
      [/SIZE][/COLOR]
      4
      MultiROM Update

      Downloads:
      • TWRP 3.1.0-0 available here.
      • MultiROM v33 (20170324) available here.

      Changelog:
      Official TWRP Changelog - Here
      MultiROM and TWRP Upstream Updates

      Big thanks to:

      - @BitOBSessiOn for building and working hard on MultiROM
      - TeamWin and especially to Abdessamad Derraz (@Abdess) <[email protected]>
      for initial TWRP support and Parth Bhatia (@TheStrix) <[email protected]>
      - Vojtěch Boček (@Tasssadar) <[email protected]> for MultiROM
      - @nkk71 for NO-KEXEC support

      Thank you
      -TechExhibeo