[MOD][FEB 10] MultiROM v33

Search This thread

dsr13

Senior Member
May 22, 2012
82
35
using multi ROM, Franco r21 boots but will not allow the multirom interface to load... It just boots into the primary rom. Flashing the kexec kernel from the op fixed the issue. I reported it on the Franco thread s well.

Sent from my Nexus 5 using Tapatalk
 

Tasssadar

Inactive Recognized Developer
Dec 31, 2010
818
6,128
Brno
tasssadar.github.com
What data directories do roms you dual boot share? Does it create a partition for each rom, or do they share app data like if I have nova launcher on two roms will it save changes I make to my homescreen it will change on other roms I have running nova launcher? Or what about general files like DCIM or downloads, will they be consistent?

If this is a dev thread only and there exists a FAQ thread please forward me, I couldn't find one.

ROMs are stored in /data/media/0/multirom/roms (which is only accessible as root to prevent MediaScanner from entering it). ROMs only share /data/media (also known as /sdcard), nothing else.

Something about MultiROM is on github wiki, but it needs expanding: https://github.com/Tasssadar/multirom/wiki

using multi ROM, Franco r21 boots but will not allow the multirom interface to load... It just boots into the primary rom. Flashing the kexec kernel from the op fixed the issue. I reported it on the Franco thread s well.

Sent from my Nexus 5 using Tapatalk

It works for me. If you flashed the boot.img via fastboot, you need to go to recovery and do Advanced -> MultiROM -> Inject curr. boot sector. Part MultiROM is stored in boot.img, so flashing a different one will remove it.
 

AndroidGaalaxy

Senior Member
Nov 8, 2012
143
55
Paris
using multi ROM, Franco r21 boots but will not allow the multirom interface to load... It just boots into the primary rom. Flashing the kexec kernel from the op fixed the issue. I reported it on the Franco thread s well.

Sent from my Nexus 5 using Tapatalk

Download application from playstore https://play.google.com/store/apps/details?id=com.tassadar.multirommgr

Follow the instructions (Do no install kernel), the phone should reboot into recovery...

After MultiRom installation, install Franco Kernel

Go to Recovery ==> Advanced ==> MultiROM

Enjoy ^^
 

aeppacher

Senior Member
Apr 14, 2012
795
777
ROMs are stored in /data/media/0/multirom/roms (which is only accessible as root to prevent MediaScanner from entering it). ROMs only share /data/media (also known as /sdcard), nothing else.

Something about MultiROM is on github wiki, but it needs expanding: https://github.com/Tasssadar/multirom/wiki



It works for me. If you flashed the boot.img via fastboot, you need to go to recovery and do Advanced -> MultiROM -> Inject curr. boot sector. Part MultiROM is stored in boot.img, so flashing a different one will remove it.

Bummer, this is making me start to regret the 16GB instead of the 32GB...

---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------

Also is there any uninstall method/procedure?
 

rum0s

Senior Member
Dec 22, 2007
525
73
Wow cool m8te! I'm trying right now. BTW, donation is on it's way ;) Thanks for sharing!!!
 
Last edited:
  • Like
Reactions: Citizen_Snips

bigdog_nick

Senior Member
Jun 19, 2010
266
36
Orange County
I just died a little. Been using MultiRom with my N7 since the early days. I'm excited for this, gonna test out later today or tomorrow. :highfive:
 

ewalk4866

Senior Member
Aug 13, 2010
536
426
chicago
Great job OP Thanks but I do have one question. You say that its TWRP 2.6.3.4 in the OP but after install its twrp 2.6.3.3 am I over looking something?
 

pandacookie

Senior Member
Sep 5, 2011
1,278
314
Quincy
Okay. So I am gonna do this MultiROM thing. Let's just say I change my mind later. What are the steps to get out of the MultiROM environment?

Sent from my Nexus 5 using Tapatalk
 

pandacookie

Senior Member
Sep 5, 2011
1,278
314
Quincy
In the OP there is a flash able zip that you flash through recovery and that will remove MultiROM

Sent from my Nexus 5 using Tapatalk

Heh. I didn't see that. Thank you. I need to break this habit of reading and running...

Sent from my Nexus 5 using Tapatalk

---------- Post added at 01:38 PM ---------- Previous post was at 01:35 PM ----------

Ahhh now I see why I didn't see it. It's in the second post. Not the first.

Sent from my Nexus 5 using Tapatalk
 

Grondinm

Senior Member
Feb 18, 2008
1,567
1,564
40
Moncton
Great job OP Thanks but I do have one question. You say that its TWRP 2.6.3.4 in the OP but after install its twrp 2.6.3.3 am I over looking something?

Mine says 2.6.3.0...installed using Multirom manager app....it might be a theme issue...

edit: not a theme issue but a variable definition issue...

https://github.com/Tasssadar/Team-Win-Recovery-Project/blob/master/variables.h

I am not sure tho that it can be fixed as i think this same branch is used to build for more then one device maybe...but i could be wrong
 
Last edited:

maamdroid

Senior Member
Jun 6, 2013
360
101
Installed using the App. Said it had to reboot and it did, though now when I boot, it just gets stuck at a black screen.
My guess is a kernel issue, so all I would need to do is install a different kernel from twrp?


Yep, I did from recovery:

adb push latesfrancokernel.zip /sdcard/Download/

Then installed that zip. Reboot system and I am not back in my original rom (Beanstalk unofficial)
 
Last edited:

Tasssadar

Inactive Recognized Developer
Dec 31, 2010
818
6,128
Brno
tasssadar.github.com
I've made flashable ZIPs with stock ROMs again. These are made from 4.4.2 KOT49H factory images, no changes, no root, no anything. They install just like any other ROM here on XDA though, which means you can use it to flash stock as secondary ROM in MultiROM. They can also be used to upgrade existing stock 4.4.x ROMs.

http://goo.im/devs/Tassadar/stock_zips/kot49h_hammerhead.zip

As for the recovery - it is 2.6.3.4, it just doesn't show it - I would have to edit variables.h for each device separately, which means I wouldn't be able to use script to build TWRP and MultiROM for all devices at once. And, besides that, most of the time I have no idea what was changed in .x versions of TWRP - this version number is device-specific, and more often than not, there is no changelog available. I know what was changed in 2.6.3.4 by pure luck, as it was discussed on #twrp IRC channel.
 
Last edited:

Grondinm

Senior Member
Feb 18, 2008
1,567
1,564
40
Moncton
I've made flashable ZIPs with stock ROMs again. These are made from 4.4.2 KOT49H factory images, no changes, no root, no anything. They install just like any other ROM here on XDA though, which means you can use it to flash stock as secondary ROM in MultiROM. They can also be used to upgrade existing stock 4.4.x ROMs.

http://goo.im/devs/Tassadar/stock_zips/kot49h_hammerhead.zip

As for the recovery - it is 2.6.3.4, it just doesn't show it - I would have to edit variables.h for each device separately, which means I wouldn't be able to use script to build TWRP and MultiROM for all devices at once. And, besides that, most of the time I have no idea what was changed in .x versions of TWRP - this version number is device-specific, and more often than not, there is no changelog available. I know what was changed in 2.6.3.4 by pure luck, as it was discussed on #twrp IRC channel.

You should almost change variables.h to not list a version number to make it less confusing for users or avoid questions...something like

#define TW_VERSION_STR "MultiRom Version"

Altho i am not sure how well that would fit on some screens....Maybe omit the word version...
 

sarun_biotech

Senior Member
Jan 12, 2012
212
112
Bangalore
Thanks a ton for bringing this to N5.
Installed a secondary rom without any issues.
One prob though. Under swap roms option, i dont see the secondary rom listed so that i can choose it for swap.

Sent from my Nexus 5 using XDA Premium 4 mobile app
 

Top Liked Posts

  • There are no posts matching your filters.
  • 425
    vh3puLb.png
    Introduction

    MultiROM is one-of-a-kind multi-boot mod for Nexus 5. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that 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 and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.

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

    You can also watch a video which shows it in action.



    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
    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 - 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:
    • MultiROM (multirom-YYYYMMDD-vXX-hammerhead.zip) - download the ZIP file from second post and flash it in recovery.
    • Modified recovery (TWRP_multirom_hammerhead_YYYYMMDD.img) - download the IMG file from second post and use fastboot or Flashify app 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.
    You current rom will not be erased by the installation.
    Download links are in the second post.



    Adding ROMs
    1. Android
    Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 4.2 after first boot (with dalvik cache generated and connected to google account) takes 676mb of space.​

    2. Ubuntu Touch
    Use the MultiROM Manager app to install Ubuntu Touch.

    Ubuntu Touch is in development - MultiROM will have to be updated to keep up with future changes in Ubuntu, so there's a good chance this method stops working after a while and I'll have to fix it.

    3. Firefox OS
    Firefox OS is just another Android ROM from MultiROM's point of view, so grab the ZIP file from Firefox OS' thread and add it as if it were Android​

    4. SailfishOS
    • Download CyanogenMod and SailfishOS ZIP as described on Sailfish wiki page. You need alpha2 (20140810) or newer!
    • Put both CM and SailfishZIP on your device.
    • Reboot into recovery
    • Advanced -> MultiROM -> Add ROM
    • Choose "SailfishOS" as ROM type. Installation to USB drive is not supported, so leave install location as is. Click Next.
    • Choose first CyanogenMod ZIP and then SailfishOS ZIP. Click install.
    Head to SailfishOS thread for more info: http://xdaforums.com/google-nexus-5/development/rom-sailfish-os-alpha-t2841266



    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.



    Source code



    Donations
    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 :)
    169
    Downloads

    1. Main downloads

    MultiROM: multirom-20160207-v33-hammerhead.zip
    Modified recovery (based on TWRP): TWRP_multirom_hammerhead_20160210.img
    MultiROM Manager Android app: Google Play or link to APK

    Kernel w/ kexec-hardboot patch (Stock 4.4): kernel_kexec_hammerhead_440.zip
    Kernel w/ kexec-hardboot patch (Stock 4.4.1 and 4.4.2): kernel_kexec_hammerhead_441.zip
    Kernel w/ kexec-hardboot patch (Stock 4.4.3 and 4.4.4): kernel_kexec_hammerhead_443.zip
    Kernel w/ kexec-hardboot patch (Stock L preview): kernel_kexec_hammerhead_L.zip
    Kernel w/ kexec-hardboot patch (Stock 5.0 preview (LPX13D)): kernel_kexec_hammerhead_50_lpx13d.zip
    Kernel w/ kexec-hardboot patch (Stock 5.0 and 5.0.1): kernel_kexec_hammerhead_50_final.zip
    Kernel w/ kexec-hardboot patch (Stock 5.1): kernel_kexec_hammerhead_510.zip
    Kernel w/ kexec-hardboot patch (Stock 5.1.1): kernel_kexec_hammerhead_511-2.zip
    Kernel w/ kexec-hardboot patch (Stock 6.0 and 6.0.1): kernel_kexec_hammerhead_601.zip
    Kernel w/ kexec-hardboot patch (CM 11 (4.4 - 4.4.2)): kernel_kexec_hammerhead_cm11-9-3d91a2d569.zip
    Kernel w/ kexec-hardboot patch (CM 11 (4.4.3 - 4.4.4)): kernel_kexec_hammerhead_cm11-12-7d4eef09ee.zip
    Kernel w/ kexec-hardboot patch (CM 12.0): kernel_kexec_hammerhead_cm12-1-10f4294a6b.zip
    Kernel w/ kexec-hardboot patch (CM 12.1): kernel_kexec_hammerhead_cm121-01-47b35a93b8.zip
    Kernel w/ kexec-hardboot patch (CM 13.0): kernel_kexec_hammerhead_cm13-01-2c39db662.zip
    You need to have kernel with kexec-hardboot patch only in your primary ROM!

    Mirror: http://d-h.st/users/tassadar

    2. third-party kernels with kexec-hardboot patch
    franco.Kernel (r21 and newer) - http://xdaforums.com/showthread.php?t=2508284
    Chaos - http://xdaforums.com/showthread.php?t=2551441
    ElementalX - http://xdaforums.com/showthread.php?t=2519607

    Nicely ask your kernel developer to merge kexec-hardboot patch.​

    3. Uninstaller

    MultiROM uninstaller: multirom_uninstaller-hammerhead-2.zip
    Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.

    4. Flashable factory images ZIPs
    I usually release flashable ZIP files based on new factory images from Google, so that you can have clean stock ROM as a secondary system in MultiROM. They are not rooted, no anything, except for occasional small tweaks to make rooting with SuperSU possible. You can find them in this folder on basketbuild or dev-host.


    Changelog
    Code:
    MultiROM v33
    =====================
    * Updates for Android 6.0 compatibility
    
    MultiROM v32c
    =====================
    * Add support for Android M preview (MPZ44Q). SuperSU 2.46 doesn't work on M
      and breaks boot - don't flash it!
    
    MultiROM v32b
    =====================
    * Fix pattern encryption password incorrectly reporting "invalid password"
      when the pattern overlaps itself
    
    MultiROM v32a
    =====================
    * Fix support for separate radio.img with secondary kitkat ROMs
    
    MultiROM v32
    =====================
    * Minor GUI improvements
    * Support for device encryption (with Android-based secondary ROMs only, for
      AOSP encryption only - does not work with CAF-based CyanogenMod as primary
      ROM). See FAQ in this device's XDA thread for more info.
    * Bunch of ROM compatibility fixes
    
    MultiROM v31
    =====================
    * Add support for "multimount" fstabs
    * Support interlaced PNGs (fixes wrongly rendered icons in boot manager, e.g.
      the L icon)
    
    MultiROM v30
    =====================
    * Fix logs generated by the "emergency reboot" screen, they were incomplete
    
    MultiROM v29
    =====================
    * Implement "autoboot if no key pressed" mode - the boot manager won't show up
      unless you hold down a volume down button during boot. Must be enabled in
      recovery.
    * Android 5.0 preview related tweaks
    
    MultiROM v28
    =====================
    * You can now swipe between the tabs in the boot manager
    * Minor UI adjustments
    
    MultiROM v27a
    =====================
    * Fix freezes in the boot manager
    * Add support for SailfishOS
    
    MultiROM v27
    =====================
    * Redesign the boot manager GUI. Looks much better now.
    * Fix separate radio.img not working on Android L preview ROMs
    * Fix issues with unaccessible /sdcard on Android L preview. Do NOT run
      restorecon manually on /data/media, ever - it breaks MultiROM!
    * Workaround bug which caused franco.Kernel on N5 to break secondary ROM's
      boot
    * Update Ubuntu Touch init scripts
    * Use power+volume down (you have to press power first!) to save screenshots.
      They are now PNG images and are saved to /sdcard/Pictures/Screenshots/.
    
    MultiROM v26
    =====================
    * Fix boot into secondary ROM from the MultiROM Manager app broken in v25
    
    MultiROM v25
    =====================
    * Add support for the Android L preview
    
    MultiROM v24
    =====================
    * Add F2FS support
    * Show icons in ROM list, configurable via MultiROM Manager app
    * Improve compatibility with different ROMs and kernels when booting a ROM
      from the Android app
    
    MultiROM v23
    =====================
    * Fix compatibility with Ubuntu Touch rev 290 and higher. If your Ubuntu
      installation won't boot, go to recovery and use "Re-patch init" option in
      Advanced -> MultiROM -> List ROMs -> *ubuntu*.
    
    MultiROM v22c
    =====================
    * Fix graphics corruption with some custom kernels
    
    MultiROM v22b
    =====================
    * Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
      enabling sharing data between Android and Ubuntu Touch. See
      [url]http://bit.ly/ut_sharing[/url] for more info.
    
    MultiROM v22a
    =====================
    * Add support for ROMs with DTB only as separate blob in boot.img (AOKP)
    
    MultiROM v22
    =====================
    * Fix Ubuntu Touch boot taking long time
    * Fix Ubuntu Touch freezing on Google logo for some users
    
    MultiROM v21a
    =====================
    * Add support for testing builds of Ubuntu Touch (see XDA thread, post #323)
    
    MultiROM v21
    =====================
    * Revert "mount /system in secondary ROMs read-only" - if done so, SuperSU
      breaks the boot.
    
    MultiROM v20
    =====================
    * Support booting ROMs directly from Manager App
    * Fix FCs on CyanogenMod-based ROMs
    * Fix support for USB drives formatted with NTFS, broken in v17
    * Mount /system in secondary ROMs read-only
    
    MultiROM v19
    =====================
    * Initial version


    Recoveries:
    Code:
    10.2.2016
    =====================
    * Fix ZIP selector being set to wrong storage after flashing ZIP to a
      secondary ROM
    
    9.2.2016
    =====================
    * Update to TWRP 3.0.0 (big thanks to nkk71 for doing most of the work)
    * Use Material theme made by z31s1g - thanks!
    * Fixes for 6.0 compatibility
    * Fixes for SuperSU compatibility. Use BETA 2.67-20160203160253 (
      [url]http://bit.ly/m_su[/url] ) or newer!
    
    30.6.2015
    =====================
    * Update to TWRP 2.8.7
    * Add option to duplicate secondary ROM into "Swap ROMs" section
    
    10.4.2015
    =====================
    * Fix Ubuntu Touch installation broken in previous update
    
    6.4.2015
    =====================
    * Fix support for SuperSU 2.47 Beta and higher
    
    28.3.2015
    =====================
    * Update to TWRP 2.8.6
    * Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
      should be used to fix broken SELinux contexts, which can be causing
      bootloops of secondary ROMs
    * Bunch of ROM compatibility fixes - recovery now uses entirely new way to
      inject ZIP installation files, which should be much more robust and reliable
    * Big ZIPs (> 450MB) are no longer permanently modified when flashed as
      secondary ROMs
    * Fix sideloading of big ZIP files (> 450MB) into secondary ROMs
    
    12.2.2015
    =====================
    * Update to TWRP 2.8.5
    * Fix support for ROMs containing a supersu.zip in their installation file
      (e.g. AICP)
    
    15.1.2015
    =====================
    * Fix "Swap ROMs" feature after the last update
    
    14.1.2015
    =====================
    * Update to TWRP 2.8.4
    * Lots of ZIP compatibility fixes (e.g. for CM 12)
    
    15.11.2014
    =====================
    * Support for ZIP files which are using the new 'block_image_update' command
      (e.g. SimpleAOSP ROM)
    
    29.10.2014
    =====================
    * Update to TWRP 2.8.1
    
    21.10.2014
    =====================
    * Update autoboot settings for MultiROM v29
    
    14.9.2014
    =====================
    * Update with changes from 2.8.0.1 upstream version: fix a bug that causes
      weird graphics glitches and touch issues
    
    11.9.2014
    =====================
    * Update to TWRP 2.8.0
    * Fix adding ROMs from backup to a FAT32 USB drives
    * Remove "share kernel with internal?" from "Add ROM" page, there is usually
      no reason to use it anymore and it might be confusing to figure out what it
      actually does. You can still get the same behavior by clicking "Remove
      boot.img" on the List ROMs -> *rom name* page.
    
    12.8.2014 - 1
    =====================
    * Fix 'Flash ZIP' function for Android ROMs, broken by a typo in previous
      version
    
    11.8.2014
    =====================
    * Remove Ubuntu Touch installation, installing via recovery is deprecated
    * Add SailfishOS installation
    
    8.8.2014
    =====================
    * Show secondary ROM's name in the title bar while executing it's script (e.g.
      during OTA update)
    * Update Ubuntu Touch updater
    * Fix failure to swap ROMs if it contains filenames starting with a dot
    * Fix add ROM from a backup producing unbootable ROM with Android L preview
    * Add option to remove radio.img from secondary ROMs
    * Add config options for MultiROM v27
    
    5.6.2014
    =====================
    * Update to TWRP 2.7.1
    * Hide misleading "Mount: Unable to find partition for path '/data'" message
      which appeared during secondary ROM installation, it is not _actually_ an
      error.
    
    4.6.2014
    =====================
    * Fix installation of bigger (>350MB) ZIPs as secondary ROMs
    
    12.5.2014
    =====================
    * Fix crash during settings loading, causing a bootloop with certain settings
    
    11.5.2014
    =====================
    * Add F2FS support
    * Add tool to switch F2FS<->ext4 to Advanced menu
    * Fix problems with backups introduced by TWRP 2.7.0
    
    8.3.2014
    =====================
    * Update to TWRP 2.7.0
    * Remove "save" button from MultiROM settings page, it is saved automatically
      now
    
    27.2.2014
    =====================
    * Support for system-image based (from the Manager app) Ubuntu Touch
      installation
    * Fix time in recovery
    * Some rendering optimizations, resulting in noticeably higher FPS in recovery
    
    4.2.2014
    =====================
    * Update to support latest Ubuntu Touch testing builds
    * Fix date and time in recovery
    * Add support for mice connected via USB-OTG
    * Fixup scrollbar behaviour in file list
    
    26.1.2014
    =====================
    * Fix radio in Ubuntu Touch
    
    24.12.2013
    =====================
    * Fix installing ROMs to USB drive
    * Fix ZIP verification
    * Support ZIP verification for secondary ROMs
    
    15.12.2013
    =====================
    * Initial hammerhead release
    110
    FAQ and other notes
    Device encryption
    Since v32, MultiROM supports encryption on this device (it has to be added for each device separately). It works only with Android-based secondary ROMs and the secondary ROMs don't know the device is encrypted, so they would allow you to encrypt the device again - do not do that. If you're using password, pin or pattern for the encryption, MultiROM will ask you for the password on boot. If you're booting the primary ROM, then Android will ask you for the password _again_ - unfortunately, there is no way for me to pass the "unencrypted" status to Android. If you're booting secondary ROM, MultiROM will ask you for the password again after the reboot - that's because I have to unencrypt the /data partition after the ROM's kernel is loaded.

    I could omit the second password prompt when booting secondary ROM by temporarily saving the password somewhere, but that's obviously unsafe. So is using encryption with unlocked device though, so I might add this later.​

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

    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. 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 shere kernel" when installing the secondary ROM, the systems are separated.​

    MultiROM recovery says it's 2.6.3.0. Why isn't it updated to 2.6.3.*highernumber*?
    It is, it just shows wrong version.​

    The menu with all the ROMs won't show up during boot, how to fix it?
    Either re-flash the MultiROM zip or go to recovery, Advanced -> MultiROM -> Inject curr. boot sector.

    The reason for this is that something rewrote your boot.img, which happens for example when you flash a kernel. MultiROM's boot menu is part of the boot image, so it has to be added into it again.


    Will you port MultiROM to device X?
    No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'd like to support more devices, but it is also very unsatisfying to work on code for device I don't have - I invest hours upon hours of time for free into it, and then I can't even see it running on the device, so...why..bother..?
    I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
    But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
    87
    MultiROM v25 adds support for the Android L preview. I've also made flashable ZIP images which you can use to flash the preview as secondary ROM to MultiROM. These are also slightly modified to fix SuperSU - you still have to flash it separately (the zip is not pre-rooted), but it will work. You also need SuperSU 2.00. Also, the first boot takes ages because ART.

    The Android L preview is not as smooth as current stable 4.4.4. I'm not sure if it is because it is preview or because MultiROM is messing up something - can somebody who installed it without MultiROM confirm or deny that? Thanks.

    The MultiROM Manager android app doesn't work on the L preview because of the SELinux changes - I know about it and will fix it...soon.

    MultiROM v25: http://tasemnice.eu/multirom/multirom-20140627-v25-hammerhead.zip
    Flashable ZIP with Android L (LPV79): https://mega.co.nz/#!ZgU1EQBI!czQcw5k_eHWfq7ylEFCivdRNTnRceSX_gM1yjNh1AFM

    GoddammitbothdevhostandgooimarenotworkingsoIhavetousemega.
    56
    The L image was released. I'm working on it, if anybody else releases ZIP first, DO NOT FLASH IT TO MULTIROM, booting it will break stuff. Link this post to anybody who seems like he wants to flash the L to multirom.