[MOD] MultiROM v33

Search This thread

Wimmme

Senior Member
Nov 9, 2012
494
272
Please do,I miss MR....Im not encrypted anyway..

Well, I have MultiROM TWRP fully working! I also have MultiROM's menu displaying and functioning on both encrypted and unencrypted devices.

The issue lies in that post hardboot, the system hangs at the Google logo. Then after being force powered off, the kexec'd kernel and system boots up! But it hangs at the bootanimation eternally, as sensorservice dies in loop (plus a few smaller issues). As always, test builds @ ods.ninja/Server/Android/angler/MR/

I have no further ideas, so, if anyone has ideas or can help, let me know.

I'm sorry, cannot help you with that :(

But a release of the version working fully with 7.1.1 for non-encrypted devices would be awesome :fingers-crossed:
Encryption is nice for a stock device, but encryption is a PITA for all tinckering and tweaking stuff, so i simply don't use it, and I guess a lot of users with me.
 

JPREMEEE

Senior Member
Aug 11, 2016
120
20
DALLA$
Has anyone gotten this to work by downgrading to 6.0.1 and then putting a nougat ROM in the secondary slot I'm not sure if some of these comments are concept or actual experience it will be great if someone can shed a little light on the most operational set up if someone has one.

Sent from my Nexus 6P using Tapatalk
 

xSilas43

Senior Member
Jun 25, 2013
1,705
1,224
Has anyone gotten this to work by downgrading to 6.0.1 and then putting a nougat ROM in the secondary slot I'm not sure if some of these comments are concept or actual experience it will be great if someone can shed a little light on the most operational set up if someone has one.
yes someone mentioned earlier in the thread they did that.
 

shadowstep

Forum Moderator
Staff member
  • Jun 6, 2014
    5,050
    10,047
    30
    Ambala
    OnePlus 5
    Bro are you encrypted or have to remove encryption to use dual boot patcher ??. The reason i asked is because am encrypted and i have bin flashing secondary rom on it an its just not booting.

    I was running unencrypted at that time with ext4. Now, I'm no longer running the patch and I'm still running unencrypted, but on f2fs. :)
     

    bkkzak

    Senior Member
    Sep 19, 2015
    447
    125
    Montana
    I've been insanely busy, but have recently gotten in contact with some other people working on MR for SD810 devices.

    I'll be trying to reboot this project one more time in June.

    Believe me when I say, I have the threads closed on projects which I no longer maintain (or plan on maintaining).

    I know you're busy and I'm not asking for ETA's, just info.

    I'm on RR 7.1.2 and want to test other 7.1.2 roms without commitment until I find one that is snappy but has the features I require.
    1. Am I right in understanding that at this point, MR does not support 7.x.x and I should not flash it?
    2. Are there any other options I can use to "browse" other roms?

    Thanks
    (And Btw I remember seeing your name all over the VZW S4 forums; you're obviously a very talented dev)
     

    ab7casper

    Senior Member
    I know you're busy and I'm not asking for ETA's, just info.

    I'm on RR 7.1.2 and want to test other 7.1.2 roms without commitment until I find one that is snappy but has the features I require.
    1. Am I right in understanding that at this point, MR does not support 7.x.x and I should not flash it?
    2. Are there any other options I can use to "browse" other roms?

    Thanks
    (And Btw I remember seeing your name all over the VZW S4 forums; you're obviously a very talented dev)


    Answer to your questions...

    1. Correct, it is not supported.


    2.
    I've been using Dual Boot Patcher (available here) and it's been working great for me. :)
     

    npjohnson

    Recognized Developer
  • Here's the deal:

    What is Going on? Why don't we have 7.x support yet?

    I'm way overdue talking about this project, and have been putting off doing so as I have always had the intention of rebooting it.

    I became swamped with university and my studies, and didn't have time to finish the bring-up necessary to get 7.x support running on the 6P. I intended to do it over the summer, when I had time (as I've previously said in this thread).

    So did you finish the bring-up over the summer?

    Mostly. As always, my work is on our repo, and a mostly accurate local manifest can be found here.

    The repos still build and work in an Omni-6.0 tree if you use the android-6.0 branches, and build (note the lack of the word work) fine if you use Omni-7.1 and the android 7.1 branches.

    So, the 7.1 builds build but don't work?

    I say that, but in actuality, they are painfully close to working. MR-TWRP boots, we can add a secondary ROM, the MR menu shows up (even if encrypted), and we can Kexec Hardboot to the secondary kernel, but for some reason, there is consistently some issue actually booting the new kernel (whether it panic, hang at aboot's loading of the kernel into memory, or try to boot but not recognize half the hardware). I've often wondered if the something about our Kexec hardboot patch was broken by a 7.x kernel change, but never had the time to look.

    Can you fix it?

    Honestly, if I had time, I believe I could, but here's where the larger problem comes in, I don't have my 6P anymore as of last week. My 6P's power button had become mushy (from all those MR cold-boots/reboots to change ROM's, amirite? lol), so I contacted Google. They offered me a Pixel XL free of charge, granted I had Nexus Protect, but that is still amazing service on their part, and I am extremely thankful they were so helpful and generous!

    Even if I were to think I figured out the issue, I'd have no way to test, and MR isn't a product that is conducive to having an external party test it for you. I have a complicated UART setup to get logs pull from my device, and I just wouldn't want to go through all the back and forth that would require.

    So, the project is discontinued?

    Not really. MultiROM is still going strong. The awesome guys over at MultiROM-Dev on GitHub are currently adapting MultiROM to Android 8.0's changes, and SDCardFS's mandatory inclusion/enablement on 8.0 devices is proving hard for them to deal with, though I am certain they'll be able to given time and help.

    As for the 6P port, I won't close the thread, or delete the work, or even the current builds, as they will always be good reference points. I just won't be contributing to the code anymore (except for maybe some goodbye cleanup of the repos this weekend).

    I think I can fix the issues! Can I release builds on XDA?

    I honestly don't know if I can stop you with the way MultiROM is licensed (or really, the lack of a license), but what I can say is, please don't release unofficial builds. Instead, pull request your changes to the repo's I linked above, and I'd be happy to review them, merge them, and send out a new build via the official MR app, and if you consistently contribute, I'll add you to the GitHub organization so you can update MR yourself.

    What I will say is that if you release unofficial builds and cause headache PM's/confusion for me, I won't be apt to help you merge the changes you made and get official builds rolling out.

    I'm more than willing to hand the project off, I just need to be sure it is in capable hands, and that the code (which serves as important reference) doesn't get messed up/deleted.

    I will be leaving this thread open for discussion about MR, MR development, or really anything relating to it.

    Why say this now?

    I feel it is important to clearly mark the end all things that have run their course, or in this case, are no longer feasible.

    I'm tying up loose ends on my personal projects because my family was recently heavily impacted by Hurricane Irma, and as such, I likely won't be able to work on many of these projects for some time.

    For those wondering the extent we got hit where I am at, our street flooded, our septic system overflowed, shingles were torn off, power lines (and their poles) taken down by winds, insulation ripped out of attics around us and thrown everywhere, roofs around us are missing, the power has been (and still is) out, many don't have running water, standing water is everywhere, and sand/garbage covers the town. It's sad to see, but I know the community will pull through it.

    I've never been one to beg for donations on my projects, but if anyone is feeling generous or helpful, you can donate to the link in my XDA profile, or here. I will be putting the money towards my family's Irma recovery, and then back into my schooling once the university I attend reopens.

    I'd like to thank everyone who contributed to the project, and would like to wish everyone a blessed life.

    Tl;DR: It has been a fun ride, but due to lack of a 6P, I won't be actively updating the project. GitHub PR's are still open, and if you contact me/are reputable, I can help with getting started, or (later down the line) handing the project off. All donations from here on out will be going to help my family and those around us recover from Hurricane Irma.
     

    Lughnasadh

    Senior Member
    Mar 23, 2015
    2,011
    1,316
    Google Nexus 5
    Huawei Nexus 6P
    Here's the deal:

    I'm tying up loose ends on my personal projects because my family was recently heavily impacted by Hurricane Irma, and as such, I likely won't be able to work on many of these projects for some time.

    For those wondering the extent we got hit where I am at, our street flooded, our septic system overflowed, shingles were torn off, power lines (and their poles) taken down by winds, insulation ripped out of attics around us and thrown everywhere, roofs around us are missing, the power has been (and still is) out, many don't have running water, standing water is everywhere, and sand/garbage covers the town. It's sad to see, but I know the community will pull through it.

    I've never been one to beg for donations on my projects, but if anyone is feeling generous or helpful, you can donate to the link in my XDA profile, or here. I will be putting the money towards my family's Irma recovery, and then back into my schooling once the university I attend reopens.

    I'd like to thank everyone who contributed to the project, and would like to wish everyone a blessed life.

    Tl;DR: It has been a fun ride, but due to lack of a 6P, I won't be actively updating the project. GitHub PR's are still open, and if you contact me/are reputable, I can help with getting started, or (later down the line) handing the project off. All donations from here on out will be going to help my family and those around us recover from Hurricane Irma.

    Thank you for everything and I wish you and your family the best through these hard times...
     

    mattwheat

    Senior Member
    Oct 25, 2012
    1,143
    581
    BIRMINGHAM
    Here's the deal:

    What is Going on? Why don't we have 7.x support yet?

    I'm way overdue talking about this project, and have been putting off doing so as I have always had the intention of rebooting it.

    I became swamped with university and my studies, and didn't have time to finish the bring-up necessary to get 7.x support running on the 6P. I intended to do it over the summer, when I had time (as I've previously said in this thread).

    So did you finish the bring-up over the summer?

    Mostly. As always, my work is on our repo, and a mostly accurate local manifest can be found here.

    The repos still build and work in an Omni-6.0 tree if you use the android-6.0 branches, and build (note the lack of the word work) fine if you use Omni-7.1 and the android 7.1 branches.

    So, the 7.1 builds build but don't work?

    I say that, but in actuality, they are painfully close to working. MR-TWRP boots, we can add a secondary ROM, the MR menu shows up (even if encrypted), and we can Kexec Hardboot to the secondary kernel, but for some reason, there is consistently some issue actually booting the new kernel (whether it panic, hang at aboot's loading of the kernel into memory, or try to boot but not recognize half the hardware). I've often wondered if the something about our Kexec hardboot patch was broken by a 7.x kernel change, but never had the time to look.

    Can you fix it?

    Honestly, if I had time, I believe I could, but here's where the larger problem comes in, I don't have my 6P anymore as of last week. My 6P's power button had become mushy (from all those MR cold-boots/reboots to change ROM's, amirite? lol), so I contacted Google. They offered me a Pixel XL free of charge, granted I had Nexus Protect, but that is still amazing service on their part, and I am extremely thankful they were so helpful and generous!

    Even if I were to think I figured out the issue, I'd have no way to test, and MR isn't a product that is conducive to having an external party test it for you. I have a complicated UART setup to get logs pull from my device, and I just wouldn't want to go through all the back and forth that would require.

    So, the project is discontinued?

    Not really. MultiROM is still going strong. The awesome guys over at MultiROM-Dev on GitHub are currently adapting MultiROM to Android 8.0's changes, and SDCardFS's mandatory inclusion/enablement on 8.0 devices is proving hard for them to deal with, though I am certain they'll be able to given time and help.

    As for the 6P port, I won't close the thread, or delete the work, or even the current builds, as they will always be good reference points. I just won't be contributing to the code anymore (except for maybe some goodbye cleanup of the repos this weekend).

    I think I can fix the issues! Can I release builds on XDA?

    I honestly don't know if I can stop you with the way MultiROM is licensed (or really, the lack of a license), but what I can say is, please don't release unofficial builds. Instead, pull request your changes to the repo's I linked above, and I'd be happy to review them, merge them, and send out a new build via the official MR app, and if you consistently contribute, I'll add you to the GitHub organization so you can update MR yourself.

    What I will say is that if you release unofficial builds and cause headache PM's/confusion for me, I won't be apt to help you merge the changes you made and get official builds rolling out.

    I'm more than willing to hand the project off, I just need to be sure it is in capable hands, and that the code (which serves as important reference) doesn't get messed up/deleted.

    I will be leaving this thread open for discussion about MR, MR development, or really anything relating to it.

    Why say this now?

    I feel it is important to clearly mark the end all things that have run their course, or in this case, are no longer feasible.

    I'm tying up loose ends on my personal projects because my family was recently heavily impacted by Hurricane Irma, and as such, I likely won't be able to work on many of these projects for some time.

    For those wondering the extent we got hit where I am at, our street flooded, our septic system overflowed, shingles were torn off, power lines (and their poles) taken down by winds, insulation ripped out of attics around us and thrown everywhere, roofs around us are missing, the power has been (and still is) out, many don't have running water, standing water is everywhere, and sand/garbage covers the town. It's sad to see, but I know the community will pull through it.

    I've never been one to beg for donations on my projects, but if anyone is feeling generous or helpful, you can donate to the link in my XDA profile, or here. I will be putting the money towards my family's Irma recovery, and then back into my schooling once the university I attend reopens.

    I'd like to thank everyone who contributed to the project, and would like to wish everyone a blessed life.

    Tl;DR: It has been a fun ride, but due to lack of a 6P, I won't be actively updating the project. GitHub PR's are still open, and if you contact me/are reputable, I can help with getting started, or (later down the line) handing the project off. All donations from here on out will be going to help my family and those around us recover from Hurricane Irma.

    Thanks buddy. My thoughts and prayers are with you and your family. Good luck.

    By the way I'm on the pixel XL also. I power on my 6p when ever I'm having withdrawals from root and unlocked bootloader's. LMAO. Yes I'm on VZW.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 89
      TLDR:

      This project is no longer actively maintained, see explanation here.

      1: MAKE A BACKUP. Seriously.
      2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
      3: Any issues: please report at https://github.com/multirom-nexus6p/multirom/issues I won't be reading this thread very often.

      35yghmf.png
      Introduction

      This is a port of Tassadar's MultiROM, a multi-boot mod for Nexus 6P. 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 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 thoroughly tested with the most popular ROM's for the 6P.

      Make backups. Seriously. Please.

      Features:
      * Multiboot any number of Android ROMs
      * Restore nandroid backup as secondary ROM
      * Boot from USB drive attached via USB-C OTG cable

      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
      We have a custom built MultiROM Manager .apk in the downloads section, feel free to try it! (somewhat untested, please report, even if install doesn't work, ROM name customization, etc. should work fine)
      1. Via MultiROM Manager app
      This is the easiest way to install everything MultiROM needs. Install the app found in the next post, 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 - 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.
      Accept any Super User request prompts.

      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 (TWRP_multirom_angler_YYYYMMDD.img) - 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 ZIP file and flash it in recovery.
      • MultiROM (multirom-YYYYMMDD-vXX-angler.zip) - download the ZIP file from second post and flash it in recovery.


      Your current rom will not be erased by the installation.

      Adding ROMs
      1. Android
      Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.​


      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)
      • 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-nexus6p/multirom/tree/master (branch master)
      Modified TWRP - https://github.com/multirom-nexus6p/Team-Win-Recovery-Project (branch android-6.0) -- Includes the awesome new Material Dark TWRP theme by @daveyannihilation ! Go thank him, or get his Blackout Domination Layers or CMTE (yes, there are free versions on the Play Store, but you can find those yourself, or donate to a hard worker :) ).
      Kernel w/ kexec-hardboot patch - https://github.com/multirom-nexus6p/android_kernel_huawei_angler/tree/mm -- use angler_defconfig
      Device tree: https://github.com/multirom-nexus6p/TWRP-android_device_huawei_angler/tree/android-6.0-mrom

      Thanks

      This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.

      Issues

      - None that are known. 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 here.

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

      Please report any unlisted issues to the GitHub bug tracker at https://github.com/multirom-nexus6p/multirom/issues . You'll get faster response if you post there instead of in this thread

      Changelog
      Here

      Downloads
      Downloads
      v33 -- Stable 7:

      MR Installer App: Play Store Link


      MR-TWRP: mr-twrp-recovery-20160528-05-STABLE7.img

      MultiROM Installer Flashable ZIP: multirom-20160514-v33-UNOFFICIAL-angler-STABLE7.zip

      Stock HardBoot Enabled Kernel Flashable ZIP (only your Primary ROM needs this): kernel-hardboot-stock-angler-6.0.1-20160514

      MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip

      NOTE:
      Third party kernels with kexec-hardboot support (can be flashed to primary ROM):

      ElementalX
      FrancoKernel
      AK
      PureNexus
      (Alert me if I've missed any!)

      Extra Information
      Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error

      Also, due to recent events on other projects of mine, you are welcome to fork our Github repositories, and use them to port MR to new devices, and as a reference, but, I ask that no one build targeting the 6P using our source and post it publicly (of course you can build for personal use, but distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!

      The only acceptable releases based on our source for the 6P is recovery/multirom themes, though, I strongly ask you tag me so I can note the themed version in the OP.

      XDA:DevDB Information
      MultiROM for Nexus 6P, Tool/Utility for the Huawei Nexus 6P

      Contributors
      npjohnson, 500 Internal Server Error
      Source Code: https://github.com/multirom-nexus6p/


      Version Information
      Status: No Longer Updated
      Current Stable Version: v33-05282016-STABLE7
      Stable Release Date: 2016-05-28

      Created 2016-02-12
      Last Updated 2017-09-17
      41
      UPDATE: I've got all the necessary repos brought up to building in a 7.1.1 tree! For those that don't know what that means, It means that MR is functioning on 7.1.1!

      Unfortunately, I've run into an issue. TWRP is unable to bind certain mounts (the most important of which being that even though /data decrypts fine, /data/media/0's bind to /sdcard/ fails for reasons I can't comprehend). This messes up everything else. Hours of debugging have yielded no results, so, I have reached out to some other developers I know in an effort to solve the problem.

      If anyone is able to help me solve the TWRP mounts issue, or wants to update multirom_adbd to 7.1.1 (an optional task which I've opted not to spend my time on), they can build In a Lineage/CM 14.1 tree. For those who can help, but don't have the resources to build, my personal builds can be found here: ods.ninja/Server/Android/angler/MR/

      I WARN those who opt to use builds from the above, I have intentionally*disabled multiboot functions in them (in essence making multirom useless so the average user doesn't use them). These are only to be used if you are able to help work out current TWRP issues.

      Thanks to all, and happy new year.
      34
      I will be updating this soon.

      I've got most of MultiROM's issues worked out, and was planning on waiting until I had it all fully building with clang/7.1.1 sources, but, I'll concede that those things aren't /that/ useful to the end user.

      As of this next release, the recovery will be built in a CM 7.1 tree, and everything else in an Omni 6.0 tree.

      If you don't know what any of the above means... you don't need to. Just know that within the next few weeks I'll be posting a new build.
      22
      I think StarShoot97 is testing the official version of TWRP.

      It has recently been released on TWRP's website: https://dl.twrp.me/angler/twrp-3.0.3-0-angler.img.html

      As for Multirom, I don't know, but there are some new commits on npjohnson's fork: https://github.com/npjohnson/Team-Win-Recovery-Project

      Yup. We have 3.0.3-0 working, with a usable theme (like we had previously), and, N-Block encryption (like on the 6P) works, but, we are still working on FBE support for those on the 6P using the option in developer settings, and Pixels... (hint hint).

      The MultiROM repo is also brought up to support N.

      All that is left is updating multirom_adbd to 7.1.1 so we can get ADB working on the MultiROM boot selection screen, updating Kexec-Tools (and remerging DTB support), then just updating the build system (branches, dependencies, etc.).
    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