• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Recovery][Mod][AOSP/SENSE]MultiROM V22 for Droid DNA(Unofficial Port)(Mar 16)

Search This thread

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
Introduction
This is a port of Tasssadar's MultiROM. MultiROM allows you to boot multiple ROMs on the same device (as well as, in theory, Linux distros, if there were any available for our device, or android-based operating systems such as Ubuntu Touch). ROMs are flashed in the modified recovery, and upon booting the phone, you have a boot menu that will allow you to choose which ROM you want to boot. You can also boot ROMs off of a USB drive connected via an OTG cable (**There are some limitations to this, keep reading for details**).

First of all, I would like to thank Tasssadar because this is 100% his work. If you enjoy MultiROM, feel free to donate to him.


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

Sense ROM Support

MultiROM is now able to boot Sense ROMs (as secondary only), but the process is a little more complicated. See second post for step-by-step instructions (Big thanks to vroad for figuring this out).Tested with ViperDNA 3.10 and UnSenseOne.​


Installation


Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).

MultiROM has 3 parts you need to install:
  • MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-dlx.zip)) - download the ZIP file from second post and flash it in recovery.
  • Modified recovery (recovery_mrom_YYYYMMDD.img) - download the IMG file from second post and use fastboot or an app such as FlashImageGUI or Flashify to flash it.
  • Patched kernel - You absolutely MUST have a kernel with the kexec-hardboot patch on the primary ROM for this to work. Look in the second post for my modified version of crpalmer's kernel that has the necesssary patch, as well as a patched stock CM11 kernel. The post will be updated accordingly for any more kernels that have the necessary patch.
You current rom will not be erased by the installation.
Download links are in the second post.

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 and proceed with the installation.

Note: In theory, FAT32, EXT4, and NTFS partitions should all be supported. However, using a FAT32 partition resulted in a failed flash for me. I have not tried NTFS. If you want to boot off of your USB drive, I recommend putting a dedicated EXT4 partition for booting ROMs. Also, I was unable to boot off of a thumb drive without sharing a kernel with the primary ROM or using a patched kernel on the secondary ROM. So if you are going to do this, any ROM you want to boot off of the USB drive ALSO needs a patched kernel.

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.
  • In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.

Explanation of recovery menus

Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download a kernel which is distrubuted as whole boot.img, you have to use this option on it, otherwise you would lose MultiROM. (You will likely not need to use this option on the DNA)
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.

Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.

Source code

Donate to Tasssadar:
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris

Thanks to all donors, it is much appreciated

XDA:DevDB Information
MultiROM for Droid DNA, a Tool/Utility for the HTC Droid DNA

Contributors
jamiethemorris

Version Information
Status: Stable

Created 2014-01-28
Last Updated 2014-03-16
 

Attachments

  • screenshot.jpg
    screenshot.jpg
    59.8 KB · Views: 106
  • screenshot_09.jpg
    screenshot_09.jpg
    49.9 KB · Views: 104
  • screenshot_11.jpg
    screenshot_11.jpg
    71.8 KB · Views: 103

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
Downloads

MultiROM Zip: http://www.androidfilehost.com/?fid=23329332407579376
Modified TWRP Recovery: http://www.androidfilehost.com/?fid=23329332407579377
My kernel w/ kexec-hardboot patch (based on crpalmer's kernel): http://forum.xda-developers.com/showthread.php?t=2627113
crpalmer's kernel w/ kexec-hardboot patch: http://forum.xda-developers.com/showthread.php?t=2559529
Stock CM11 Kernel w/ kexec-hardboot patch: http://www.androidfilehost.com/?fid=23329332407567343


Uninstaller: http://www.androidfilehost.com/?fid=23329332407579378
Mount Disabler (for Sense ROMs, see instructions below): http://www.androidfilehost.com/?fid=23329332407579371




FAQ and other notes

About security
In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​

What do the ROMs share?
All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​

How many ROMs can I have?/Where are the ROMs stored?
You can have as many ROMs as you can fit in your /sdcard (good thing HTC gave us a WHOPPING 16 gigs). All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.

Can I have different versions of Android working alongside
Yes. As long as you select "Don't share kernel" when installing the secondary ROM, the systems are separated.​

My secondary ROM doesn't boot if I share the kernel with the primary ROM.
Reinstall the secondary ROM, don't share the kernel this time, and flash the kernel you want to use to that ROM.​

How to use Sense with MultiROM


Using Sense with MultiROM is complicated for a few reasons:
-The MultiROM boot menu doesn't show up with Sense ROMs for some unknown reason.
-Most Sense ROMs can't be flashed via the MultiROM menu because they mount partitions by explicitly using the mmc block. This causes the ROM to be partially install over the primary ROM. vroad has a pretty good explanation of why this happens:
Some users have already reported that ROMs with certain kind of updater-script will format system/data/cache of primary ROM slot, and overwrite to them, even though they have tried to flash onto secondary slot.
This is because these updater-script mount partitions with the name of block device(such as /dev/block/mmcblk0p34), not with mount points(such as /system).
updater-script in Team Blackout's ROM doesn't have this problem.

-Sense ROMs also try to mount /system and /cache on boot, so the mount disabler zip is required for the ROM to boot properly.
To boot a secondary Sense ROM:
1. If you have an AOSP ROM already installed as your primary ROM, first go to Advanced > MultiROM > Swap ROMs and choose "move primary ROM to secondaries."
2. Install your Sense ROM as a primary ROM, just as you would with standard TWRP.
3. Go back to the Swap ROMs menu:
-If you had a previously installed AOSP ROM, choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
-Otherwise, choose "move primary ROM to secondaries"
4. Flash the Mount Disabler Zip to your secondary Sense ROM.
5. Insure that the primary AOSP ROM has a kernel with kexec-hardboot support as well as the MultiROM zip installed.

To update the secondary Sense ROM
1. Go to Advanced > MultiROM > Swap ROMs and choose " swap primary (Internal) ROM with secondary" and choose the Sense ROM you want to update.
2. Flash the ROM update to the primary ROM slot (just as you would with standard TWRP)
3. Go back to the Swap ROMs menu, and choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
4. Flash the Mount Disabler zip to your secondary Sense ROM.

If you do not follow these instructions properly, you will end up with a corrupted, half-Sense half-AOSP primary ROM and a secondary ROM that doesn't boot.

Kitk-Kat only. JB Sense ROMs most likely will not work.
 
Last edited:

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
What do you mean by don't share the kernel?

Sent from my HTC6435LVW using Tapatalk

Multi ROM has an option to share the kernel of the primary ROM with any other roms. Does that make sense? So if you have my kernel installed on the primary ROM you can let another ROM installed use it instead of having to install it separately on that ROM.

Sent from my Droid DNA using Tapatalk
 

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
@jamiethemorris,

If you want to submit a pull request to my kernel for the changes (and they don't look dangerous, which I don't expect them to), I'll merge them in for you.

OK cool, I'll do that. BTW do you think the patch will be drastically different when we move to msm8960 (other than the file structure being different)?

Sent from my Droid DNA using Tapatalk
 

mr4r4n

Senior Member
Apr 3, 2008
632
176
NY
Multi ROM has an option to share the kernel of the primary ROM with any other roms. Does that make sense? So if you have my kernel installed on the primary ROM you can let another ROM installed use it instead of having to install it separately on that ROM.

Sent from my Droid DNA using Tapatalk

Yes it does all the stuff given to me at the hospital may have slowed down my thought process temporarily... Lol, thanks bud

Sent from my HTC6435LVW using Tapatalk
 

crpalmer

Inactive Recognized Developer
Mar 25, 2011
2,999
8,279
OK cool, I'll do that. BTW do you think the patch will be drastically different when we move to msm8960 (other than the file structure being different)?

Sent from my Droid DNA using Tapatalk

It will not likely be very different, but I wouldn't worry too much about the new kernel just yet as we have at least one hard problem to solve before then. After that, adapting this patch will be simple...
 
  • Like
Reactions: jamiethemorris

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
It will not likely be very different, but I wouldn't worry too much about the new kernel just yet as we have at least one hard problem to solve before then. After that, adapting this patch will be simple...

OK. I've been wanting to learn some coding to make this stuff easier... Where would you recommend starting? I don't really have time to take a c or c++ class right now, but some tutorials online would be helpful.

EDIT: Also, how do I do a pull request for only the kexec-hardboot commit? I don't see an option for it.

Sent from my Droid DNA using Tapatalk
 
Last edited:

rootMBX

Member
Feb 9, 2009
39
14
Sense

This is pretty sick. Thanks for finally bringing this to the DNA!

Couple of things.

TAP2WAKE?:

The recovery, based on TWRP's beta, has a bit of a lag sometimes when performing operations right before the operation is complete. Giving the screen a couple taps (away from where the tiles will appear) will bring up the "Back" or "Reboot System" tiles instead of it being stuck with the twirling bar. This is not really related to MultiROM.

What is a new issue/feature with the modified recovery is that when the display timeouts, a simple press of the power button does not turn it back on. A single tap on the display does, though. It brings up the Swipe to Unlock screen. Is this intended?

SENSE:

Also, I've tried 5 different Sense ROMs. No kernel sharing of course. They all flashed "successfully", except for the complete, newest stock (failed), but none of them booted. I got a black screen after the initial HTC bootloader screen.

AOSP ROMs work great though! Have tried a couple with/without sharing the kernel. When/If Sense gets worked out, this will be a great way to quickly switch for use with an MHL adaptor for HDMI output.

THEME BOOT SELECTION SCREEN:

I do like the retro boot selection screen, but what are the possibilities of being able to theme it? Maybe even as simple/clean as a couple of custom icons on a black background for ROM selection?
 

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
This is pretty sick. Thanks for finally bringing this to the DNA!

Couple of things.

TAP2WAKE?:

The recovery, based on TWRP's beta, has a bit of a lag sometimes when performing operations right before the operation is complete. Giving the screen a couple taps (away from where the tiles will appear) will bring up the "Back" or "Reboot System" tiles instead of it being stuck with the twirling bar. This is not really related to MultiROM.

What is a new issue/feature with the modified recovery is that when the display timeouts, a simple press of the power button does not turn it back on. A single tap on the display does, though. It brings up the Swipe to Unlock screen. Is this intended?

SENSE:

Also, I've tried 5 different Sense ROMs. No kernel sharing of course. They all flashed "successfully", except for the complete, newest stock (failed), but none of them booted. I got a black screen after the initial HTC bootloader screen.

AOSP ROMs work great though! Have tried a couple with/without sharing the kernel. When/If Sense gets worked out, this will be a great way to quickly switch for use with an MHL adaptor for HDMI output.

THEME BOOT SELECTION SCREEN:

I do like the retro boot selection screen, but what are the possibilities of being able to theme it? Maybe even as simple/clean as a couple of custom icons on a black background for ROM selection?

I don't know if the power button thing is intended or not. I've noticed it too. I've also noticed this recovery, as well as the twrp beta, taking a really really long time to do certain things, I think it's just a shared bug...

About sense Roms, I think we're going to need to need a patched kernel for those as well. If one of our sense kernel devs doesn't get around to it than I can do it. Supposedly we also need the newest hboot also, I'm going to play around and see if I can get anything to work. If you look through the htc one multirom thread you well see that only certain configurations of dual booting sense with aosp work. That was actually the original reason I was inspired to port this to the DNA.

I don't know how to do anything with the boot menu besides just change the colors because I don't really know how any of that works.

Anyway I'm excited about these new sense Roms too and I want to dual boot them with aosp as bad as anyone else so I'll be working on it.

Sent from my Nexus 7 using Tapatalk
 

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
I just tried flashing UnSense 1.0. It flashes fine, but doesn't boot. As soon as I switched to TWRP 2.6 beta, it booted without me needing to reflash or anything. So it's detecting something about the recovery on boot that it doesn't like.

I will try doing a cm10.2 based version of it and hopefully that will solve the problem.
 
Last edited:

KyJelly69

Senior Member
Apr 26, 2010
828
208
Indianapolis
Can I use the twrp recovery without flashing multirom first and use it as my regular recovery? Then sometime later when I'm ready flash multirom?

Sent from my HTC6435LVW using xda app-developers app
 

jamiethemorris

Senior Member
Jan 7, 2013
1,851
803
I've made some progress with getting sense booting. I patched the 4.4 kernel and was able to get unsense to boot as a secondary ROM. What's weird is when it booted it was using all my data from my main ROM, and had messed everything up on both roms by combining the sense and aosp data. Makes absolutely no sense (pun not intended). But hey, it's progress... I'm going to contract dees_troy to ask how he built the 2.6.3.x twrp beta so that hopefully I can get this and twrp 2.7 booting sense normally

Sent from my Droid DNA using Tapatalk
 
  • Like
Reactions: Rnt12296 and shnyps

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Introduction
    This is a port of Tasssadar's MultiROM. MultiROM allows you to boot multiple ROMs on the same device (as well as, in theory, Linux distros, if there were any available for our device, or android-based operating systems such as Ubuntu Touch). ROMs are flashed in the modified recovery, and upon booting the phone, you have a boot menu that will allow you to choose which ROM you want to boot. You can also boot ROMs off of a USB drive connected via an OTG cable (**There are some limitations to this, keep reading for details**).

    First of all, I would like to thank Tasssadar because this is 100% his work. If you enjoy MultiROM, feel free to donate to him.


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

    Sense ROM Support

    MultiROM is now able to boot Sense ROMs (as secondary only), but the process is a little more complicated. See second post for step-by-step instructions (Big thanks to vroad for figuring this out).Tested with ViperDNA 3.10 and UnSenseOne.​


    Installation


    Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).

    MultiROM has 3 parts you need to install:
    • MultiROM (multirom-YYYYMMDD-vXX-UNOFFICIAL-dlx.zip)) - download the ZIP file from second post and flash it in recovery.
    • Modified recovery (recovery_mrom_YYYYMMDD.img) - download the IMG file from second post and use fastboot or an app such as FlashImageGUI or Flashify to flash it.
    • Patched kernel - You absolutely MUST have a kernel with the kexec-hardboot patch on the primary ROM for this to work. Look in the second post for my modified version of crpalmer's kernel that has the necesssary patch, as well as a patched stock CM11 kernel. The post will be updated accordingly for any more kernels that have the necessary patch.
    You current rom will not be erased by the installation.
    Download links are in the second post.

    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 and proceed with the installation.

    Note: In theory, FAT32, EXT4, and NTFS partitions should all be supported. However, using a FAT32 partition resulted in a failed flash for me. I have not tried NTFS. If you want to boot off of your USB drive, I recommend putting a dedicated EXT4 partition for booting ROMs. Also, I was unable to boot off of a thumb drive without sharing a kernel with the primary ROM or using a patched kernel on the secondary ROM. So if you are going to do this, any ROM you want to boot off of the USB drive ALSO needs a patched kernel.

    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.
    • In some cases, you might need to flash patched kernel - get coresponding patched kernel version from second post and flash it to the secondary ROM sama way you flashed ROM's ZIP file.

    Explanation of recovery menus

    Main menu
    - Add ROM - add ROM to boot
    - List ROMs - list installed ROMs and manage them
    - Inject boot.img file - When you download a kernel which is distrubuted as whole boot.img, you have to use this option on it, otherwise you would lose MultiROM. (You will likely not need to use this option on the DNA)
    - Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
    - Settings - well, settings.

    Manage ROM
    - Rename, delete - I believe these are obvious
    - Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
    - Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.

    Source code

    Donate to Tasssadar:
    I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris

    Thanks to all donors, it is much appreciated

    XDA:DevDB Information
    MultiROM for Droid DNA, a Tool/Utility for the HTC Droid DNA

    Contributors
    jamiethemorris

    Version Information
    Status: Stable

    Created 2014-01-28
    Last Updated 2014-03-16
    2
    Downloads

    MultiROM Zip: http://www.androidfilehost.com/?fid=23329332407579376
    Modified TWRP Recovery: http://www.androidfilehost.com/?fid=23329332407579377
    My kernel w/ kexec-hardboot patch (based on crpalmer's kernel): http://forum.xda-developers.com/showthread.php?t=2627113
    crpalmer's kernel w/ kexec-hardboot patch: http://forum.xda-developers.com/showthread.php?t=2559529
    Stock CM11 Kernel w/ kexec-hardboot patch: http://www.androidfilehost.com/?fid=23329332407567343


    Uninstaller: http://www.androidfilehost.com/?fid=23329332407579378
    Mount Disabler (for Sense ROMs, see instructions below): http://www.androidfilehost.com/?fid=23329332407579371




    FAQ and other notes

    About security
    In order to make multi-booting possible, MultiROM has to sacrifice some security measures. Firstly, on secondary Android ROMs, /system is not mounted read-only. While there are other things preventing malicious software from messing with /system, this might potentialy make it easier for such software to attack that system.
    Next, MultiROM doesn't work with /data encryption. Not many people who use custom ROMs also use encryption anyway, so that isn't much of a concern.​

    What do the ROMs share?
    All ROMs are separate, except /sdcard, which is shared between all Android ROMs.​

    How many ROMs can I have?/Where are the ROMs stored?
    You can have as many ROMs as you can fit in your /sdcard (good thing HTC gave us a WHOPPING 16 gigs). All the ROMs are stored in /sdcard/multirom/roms or on an USB drive. This folder is unaccessible in Android, to prevent mediascanner from scanning it. You can either in recovery, or obtain root and go to /data/media/0/multirom/roms.

    Can I have different versions of Android working alongside
    Yes. As long as you select "Don't share kernel" when installing the secondary ROM, the systems are separated.​

    My secondary ROM doesn't boot if I share the kernel with the primary ROM.
    Reinstall the secondary ROM, don't share the kernel this time, and flash the kernel you want to use to that ROM.​

    How to use Sense with MultiROM


    Using Sense with MultiROM is complicated for a few reasons:
    -The MultiROM boot menu doesn't show up with Sense ROMs for some unknown reason.
    -Most Sense ROMs can't be flashed via the MultiROM menu because they mount partitions by explicitly using the mmc block. This causes the ROM to be partially install over the primary ROM. vroad has a pretty good explanation of why this happens:
    Some users have already reported that ROMs with certain kind of updater-script will format system/data/cache of primary ROM slot, and overwrite to them, even though they have tried to flash onto secondary slot.
    This is because these updater-script mount partitions with the name of block device(such as /dev/block/mmcblk0p34), not with mount points(such as /system).
    updater-script in Team Blackout's ROM doesn't have this problem.

    -Sense ROMs also try to mount /system and /cache on boot, so the mount disabler zip is required for the ROM to boot properly.
    To boot a secondary Sense ROM:
    1. If you have an AOSP ROM already installed as your primary ROM, first go to Advanced > MultiROM > Swap ROMs and choose "move primary ROM to secondaries."
    2. Install your Sense ROM as a primary ROM, just as you would with standard TWRP.
    3. Go back to the Swap ROMs menu:
    -If you had a previously installed AOSP ROM, choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
    -Otherwise, choose "move primary ROM to secondaries"
    4. Flash the Mount Disabler Zip to your secondary Sense ROM.
    5. Insure that the primary AOSP ROM has a kernel with kexec-hardboot support as well as the MultiROM zip installed.

    To update the secondary Sense ROM
    1. Go to Advanced > MultiROM > Swap ROMs and choose " swap primary (Internal) ROM with secondary" and choose the Sense ROM you want to update.
    2. Flash the ROM update to the primary ROM slot (just as you would with standard TWRP)
    3. Go back to the Swap ROMs menu, and choose "swap primary (Internal) ROM with secondary" and choose the AOSP ROM that you want to move to primary.
    4. Flash the Mount Disabler zip to your secondary Sense ROM.

    If you do not follow these instructions properly, you will end up with a corrupted, half-Sense half-AOSP primary ROM and a secondary ROM that doesn't boot.

    Kitk-Kat only. JB Sense ROMs most likely will not work.
    2
    I did not have success installing it as primary either. I will be updating as soon as I have a chance. For the time being, if you want to use multirom with Lollipop, install your ROM with the latest TWRP from mdmower, reflash multirom, and move it to a secondary ROM (multirom zip will not install over a LP ROM, so it cannot be used as a primary if you want to multiboot).
    2
    Actually, after looking at mdmower's device tree for unsocial twrp, I have an idea...

    Sent from my Droid DNA using Tapatalk
    2
    I've made some progress with getting sense booting. I patched the 4.4 kernel and was able to get unsense to boot as a secondary ROM. What's weird is when it booted it was using all my data from my main ROM, and had messed everything up on both roms by combining the sense and aosp data. Makes absolutely no sense (pun not intended). But hey, it's progress... I'm going to contract dees_troy to ask how he built the 2.6.3.x twrp beta so that hopefully I can get this and twrp 2.7 booting sense normally

    Sent from my Droid DNA using Tapatalk