Develop Bugs

[MOD][FEB 10] MultiROM v33

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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://forum.xda-developers.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
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Tasssadar/android_kernel_google_msm/tree/android-msm-hammerhead-3.4-kk-r1-kexec​
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 ​

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://forum.xda-developers.com/showthread.php?t=2508284
Chaos - http://forum.xda-developers.com/showthread.php?t=2551441
ElementalX - http://forum.xda-developers.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

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​

This looks awesome!!
Sent from My Nexus 5 ?.

Nice job! But why no 3rd-party kernels?
EDIT: I should have read more carefully
Sent from my Nexus 5 using Tapatalk

This looks legit finally multiboot!!
Failed to get root access in multiboot app on cm ROM
Sent from my Nexus 5 using XDA Premium 4 mobile app

I don't see the option to add a zip rom in modified kernel...
Edit : I think I know why, this must be because of my TWRP theme. Will remove it and try, then post a second edit.
Edit 2 : to those who are running a TWRP theme, remove it 'til it gets compatible. Else everything working fine here.
Sent from my Omniromed and Faux kerneled Nexus 5 using Tapatalk

It's like Christmas one week early

Very very nice i waited for this since Nexus4 days. Thx a lot!
Best regards
Craxx
Send from my Nexus 5 with Tapatalk

Thank you for all your hard work !
Envoyé de mon Nexus 7 en utilisant Tapatalk

This goes to show why nexus devices are in a class all of there own.Thanks for this amazing feature.

@franciscofranco already pushed r21 of his kernel with the Kexec-patch included. Nice work!
Sent from my Nexus 5 using Tapatalk

One question... Why do you use a OLD recovery? It is 2.6.3.0 and actual is 2.6.3.4.. Or is only the false version displayed?
Best regards
Craxx
Send from my Nexus 5 with Tapatalk

Excellent! That's what I was looking... now I can check different ROMS. Thank you.

Great to see you here, testing now!
Sent from my Nexus 5 using XDA Premium 4 mobile app

Working fine for me! Thank you so much for this

oh my goodness, i wasn't expecting this coming so early to n5 *-* i used it so much on my ex nexus 4, now gonna use it on my n5!
Sent from my Nexus 5 using XDA Premium 4 mobile app

I asked to merge the Kexec-hardboot patch for Bricked Kernel.

No way.... Been looking for this thread every day for a the last month, can't believe it's here already

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.

[ROM]★[TF300 KitKat 4.4.4][ZOMBi-X OMNI KANG B5[Oct 30]★

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION ENDING IN 27.1 or 27.5 AND TWRP 2.6.3.2+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM base. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
Features and Tweaks
This ROM is based from OMNI AOSP sources
Supports EXT4 and F2FS Data partitions
Based off omni-4.4.4-20141030-zombi_tf300t-KANG source by lj50036/hardslog
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD/DATA2sd/F2FS support
Remixed _thatv11 kernel with OMNI ramdisk - repacked by sbdags/lj50036
Grimlock kernel with OMNI ramdisk and _that init - by hardslog
DPI Size: 213 (TF700 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
Launchers: Omni, Google Experience Launcher, Apex , Nova
Boot Animations: ZOMBi-X, Android-L, Nexus Phase Beam
Gapps (updated by me to Google latest apks and libs)
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, Keyboard Manager
Asus Apps: Compiled by kansasboy001; Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
Tweaks: File system and performance optimised, Init.d support!, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Tip 1: Go to Settings - About Tablet, Click build number 7 times
Now you will see Developer Settings & Performance menus
[*]Tip 2: In Dev Settings, enable advanced reboot & change window animation,
transition animation & animator scales down to 0.2x for extra snappiness
[*]Tip 3: FLOATING WINDOWS: Settings - Interface - more... - Omni Switch
Bug List
[*] Dock works as do most special keys - just no battery available in the system bar
Change Log
20141030 Beta 5 changes
- Merged tinted status bar into ZOMBi
- Tweeked muti-window [issues with tinted window]
- Added SU as a prebuit [updateable from the playstore]
20141006 Beta 4 changes
- FIxed dock battery reporting with app/widget ! Thx @hardslog
20141002 Beta 3 changes
- Added thatv11 to installer
- Added Grimlockv4 to installer
- Fixed BT not turning on without rebooot
- Fixed Bluethooth Share crash on first boot
- Fixed Dock battery reporting (needs an app/widget to work)
- updated dolphin browser to version 11.2.3
- updated google tts to 3.2.12
- updated google music to version 5.6.1523p
- updated google mail to version 4.9
- updated google search to version 3.6.14.1337016
- updated google talkback to version 3.5.2
- updated google play store to version 4.9.13
- updated google core services to version 5.0.89
- updated youtube to version 5.10.1.5
- updated apex launcher to version 2.6.0
- updated adaway to version 2.9.1
20140829 Beta 2 changes
- Fixed issues with Root being lost - reverted to cm11 ramdisks rather than omni as this was causing the issue
- SuperUser and SU Binary updated to version 2.0.2
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
20140826 Beta 1 changes
- New Base - Rebuilt from latest source which has updated bluetooth config - thanks lj50036
- 90% of dock should be working - battery display is not
- Added CM11 Kernel as option in installer - runs well
- Themed framework with a splash of RED
- Final Tweaks to Aroma Theme
- Updated GravityBox to version 3.3.3
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Small changed to aroma themes to fix dark text on dark backgrounds
- Changed the transition config in aroma to see if it fixes screen freezes
- Fixed installer script to allow rom2sd on grimlock kernel install
- Fixed aroma freezes - or reduced them
- Re-themed Zombi-X aroma theme
- Updated performance switch for CPU to allow OC to 1800 on _that's kernel
- Fixed correct rom version in the build.prop
- Updated SU Binary to latest version
- Updated Chrome, Gmail, Google Now, YouTube
- Added Android Terminal to ROM
- New Red Aroma Theme for Zombi-X - requires less memory
- Initial release - omni cromified after source build
- Added SuperUSer and su binary for root capability
- Browser tweaked for speed and touch smoothness
- Added all the CROMBi/CROMi goodness to the base rom
- Aroma tuned for ZOMBi-X
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X/CROMBi-kk ROMS)
@lj50036 - Source Guy (From CROMBi-kk ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
Omni Team - Thanks!
@_that For all the great advice, watching over us and fixing everything we break!!!!!
All the beta testers for your patience and feedback : BxMxK, canito10, duckredbeard, mikew29, nameneeded, cgf, cyberknight2001, Mikey1969, Ozark_8125, tiernan22, boldnuts, tonyh51, Vathan, erisi, Thibor69
To Do
Fix Buetooth and other little bugs
XDA:DevDB Information
ZOMBI-X, ROM for the Asus Transformer TF300T
Contributors
lj50036, sbdags, hardslog, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: bootloader ending in 27.1 or 27.5
Based On: OMNI AOSP
Version Information
Status: Beta
Current Beta Version: 20141008
Beta Release Date: 2014-10-08
Created 2014-09-18
Last Updated 2014-10-02

DOWNLOADS!
UPGRADE INSTRUCTIONS
Steps
1. If you haven’t yet, unlock your TF300 by now following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) 2.6.3.2+ or ClockWorkMod Recovery 6.0.4.6+ Note this ROM will NOT install with older versions of recovery!
OFFICIAL TWRP 2.8.1.0
Flashable zip being made ....
FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
ZOMBi-X ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not
ZOMBi-X Beta 3 Full Mirror 1
ZOMBi-X Beta 3 Full Mirror 2
ZOMBi-X Beta 3 Full Mirror 3
BOTH FILES ARE SIGNED. IF YOU ENABLE SIGNATURE VERIFICATION IN RECOVERY IT WILL VALIDATE THE FILE BEFORE FLASHING.
ASUS APPS DOWNLOAD - Flash from Recovery : Compiled by kansasboy001
Don't forget ROM2SD1.zip / DATA2SD1.zip first if you are not running an internal setup
Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
ROM2SD/DATA2SD USERS PLEASE READ!
ROM2SD only works if you have ZOMBi-X, CROMBi-kk, CROMi-X or miniC flashed on internal with a THATv10+ kernel. Just choose ROM2SD in the installer of ZOMBi-X to flash it to ROM2SD and the installer will do the rest.
- Install ZOMBi-X and choose ROM2SD or DATA2SD install
The ROM2SD1.zip below is only needed if you need to switch your recovery to between normal and rom2sd mode. For Example you want to backup or restore a rom2sd installation. Flash once to go rom2sd and flash again to go back to normal. A reboot always puts you back to normal. Thanks to _that!
ROM2SD1.zip Download Mirror 1
ROM2SD1.zip Download Mirror 2
MD5 Sum: 7b699136d59ea3d5538570ccaf422acf
The DATA2SD1.zip below is only needed if you need to switch your recovery to between normal and data2sd mode. For Example you want to backup or restore a data2sd installation. Flash once to go data2sd and flash again to go back to normal. A reboot always puts you back to normal.
DATA2SD1.zip Download Mirror 1
DATA2SD1.zip Download Mirror 2
MD5 Sum: 9d5e9e2fd32593f981624499b37924b2
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the ZOMBi-X zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
Using GParted to setup a micro SD for ROM2SD or DATA2SD support
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
Note for DATA2SD just do one partition in stead of 2
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android (not needed for data2sd)
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall ZOMBi-X but this time choose the ROM2SD / DATA2SD option

HUGE THX
@spudsmac
@miduku
@robbie888
@lightiv
@Bigred007
@Waldo_
@emfanitek
@rlanza1054
@Unidave199
@Lock-N-Load
@Fear Knot
@lvrijn
@mitsublw
@scouzers
@zdebel
@jhr5474
@Eddie Hicks
@smchadwell
@dladz
@eRPeeX
@LocusofZen
Thx everyone that has donated, if you do not see your user name here and have donated, shoot me an PM and I will add you....
Thx Josh

Reserved!

I have been looking forward to this. nice and fresh.
many thanks to you all =)

Does the official TWRP 2.8.0.1 support f2fs on /data?

k-kuchen said:
Does the official TWRP 2.8.0.1 support f2fs on /data?
Click to expand...
Click to collapse
Yes It is working very nicely.. :laugh:
It even has MTP now.... Thx TWRP...
Thx Josh

sneaky buggers
Moar good things are coming

twrp 2.8
Can I just use terminal to install twrp like "dd if=/sdcard/twrp28.blob of=/dev/block/mmcblk0p4" before I install new zombi-x? I renamed file to twrp28.blob already.

xxxericxxx said:
Can I just use terminal to install twrp like "dd if=/sdcard/twrp28.blob of=/dev/block/mmcblk0p4" before I install new zombi-x? I renamed file to twrp28.blob already.
Click to expand...
Click to collapse
I had no idea this would become a TWRP thread... :cyclops:
Take a look here mate TWRP TF300T
Thx Josh

differences between this and the crombi-kk?
how do you get the ES file explorer as pop up?

albyzaf said:
differences between this and the crombi-kk?
how do you get the ES file explorer as pop up?
Click to expand...
Click to collapse
Crombi-KK - Based on CyanogenMod sources
Zombi-X - Based on OmniRom sources and includes some OmniRom specific experimental features that aren't in official nightlies yet (like the floating windows)
If you want floating windows, I suggest activating the "OmniSwitch" app. With this app, if you long press on either the recent apps, or your favourite apps, it will give you the option to "float view"

hardslog said:
Crombi-KK - Based on CyanogenMod sources
Zombi-X - Based on OmniRom sources and includes some OmniRom specific experimental features that aren't in official nightlies yet (like the floating windows)
If you want floating windows, I suggest activating the "OmniSwitch" app. With this app, if you long press on either the recent apps, or your favourite apps, it will give you the option to "float view"
Click to expand...
Click to collapse
It's beem much quieter here than i thought it would be..
I'm just wondering if it would be possible to get some actions on the nav bar for floating window mode. going in through omni switch each time a a bit of a pain. Maybe something like that have done on the katkiss rom?
I'd report more useful stuff like bugs if i had found any =)

I'm just curious if the f2fs and f2fsSD are working in this?

gargash said:
I'm just curious if the f2fs and f2fsSD are working in this?
Click to expand...
Click to collapse
Yep they are. If you mean internal, data2sd and rom2sd.

Nice ROM
Thanks @sbdags, @lj50036, and @hardslog ! You guys still actively working on this? I was wondering if the dock battery status bar indicator would be included in the future.

shawnbrennan55 said:
Thanks @sbdags, @lj50036, and @hardslog ! You guys still actively working on this? I was wondering if the dock battery status bar indicator would be included in the future.
Click to expand...
Click to collapse
Of course we are still working on it. We have just begun. Currently working out other kinks before we try to tackle the dock battery status bar indicator again. Already tried to implement it once but failed miserably.

I can't wait to try this one guys, do you have any idea when it will be out if beta?

robgee789 said:
I can't wait to try this one guys, do you have any idea when it will be out if beta?
Click to expand...
Click to collapse
Don't be afraid of beta. This ROM is awesome combined with an F2FS file system and kernel.

robgee789 said:
I can't wait to try this one guys, do you have any idea when it will be out if beta?
Click to expand...
Click to collapse
Nope, but it is mostly a beta because of unimplemented functionality that we want in the future and some very nit-picky things (we all have some form of OCD :laugh
Could always take a nandroid and give it a try :cyclops:

[MOD][UNOFFICIAL] MultiROM v32 [2015.07.06]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Motorola Moto G. 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.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.
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-titan.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_titan_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 - Not available yet
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 - Not available yet
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 - Not available yet
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://forum.xda-developers.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.
Changelog
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* 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:
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.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
Credits :
@Brawn_Sg for multirom falcon port
@Picohackr hackr for the recovery
@tassadar for the entire multirom
@h2o64 for the OP
@luca020400 for helping me with TWRP
DOWNLOADS
Tested Configuration:
Primary Rom: PAC-5.0
Sec. Rom: CM12
Sec. Rom: CM11
Donations (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 v32 Titan, ROM for the Moto G 2014
Contributors
LuK1337, luca020400
Source Code: https://github.com/multirom-titan
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Abandoned
Created 2015-03-03
Last Updated 2016-02-14

Reserved
DOWNLOAD
Bugs:
Sdcard may not work in secondary roms: fix
Your sdcard or USB storage partition must be formatted as EXT4 if you want to store roms on it.
Stock based roms are not supported.
Changelog:
2015-07-06
- Updated MultiROM to the latest source (2.8.7.0)
2015-06-19
- Added support for software encrypted /data (TWRP)
2015-03-30
- Source updated to v32
2015-03-30
- Multirom TWRP now uses LP kernel
2015-03-27
- Updated MultiROM to the latest source (2.8.6.0)
2015-03-15
- Fixed volume keys in boot menu
2015-03-14
- Added sdcard (EXT4) support
2015-03-02
- Initial release
MultiROM:
MultiROM v32
MultiROM TWRP:
MultiROM TWRP 2.8.6.0
KEXEC PATCHED KERNEL:
CM12.1
CM12: LP KK
CM11
Stock 5.0.2
MISC:
UNINSTALLER

It doesn't work for me
But it does for Luk xd
Good flash to anyone hahaha

THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??

deeplyyoung said:
THIS IS IT.....tnks, surely gonna give my full to try right now
Edit: PAC 5 as primary?? Link pls or suggest which one should be primary??
Click to expand...
Click to collapse
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)

LuK1337 said:
Yes, I tested it with PAC which is based on CM12 so I didn't waste my time to flash CM12.
You can use every CM12 based rom (PAC, CM12, etc.)
Click to expand...
Click to collapse
Except roms with supersu ( like aicp and blisspop ) as primary

Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..

ishubhamsingh said:
Can I use cm11 as primary ROM? Please patch a cm11 kernel, so that I can test it..
Click to expand...
Click to collapse
I'll build patched CM11 kernel later.

the best roms can not be primary

Awesome stuff multiboot finally, no more wiping nice setups
Thanks Luk
Sent from my XT1068

Wow....Just tried it....Works great....All I can say is hats of to you Luk

No blisspop as primary

Yuppies
Sent From My XT1068{LP} Using TapatalK

Multibooting cm12 and cm11 possible?

Does multirom doesn't work for other guys ?
Or I'm the only one ...

luca020400 said:
Does multirom doesn't work for other guys ?
Or I'm the only one ...
Click to expand...
Click to collapse
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working

slukk said:
Working perfectly here.
pINKman cm12 and pINKman cm11 are compatible too. So kexec patch implemention is working
Click to expand...
Click to collapse
I said it wasn't working becuase in my device multirom doesn't work
I got it working before ( at the 1st attempt )
But my device ****ed it up ...
That's why I haven't released it ...

Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?

Vidhanth said:
Any kernel with kexec hardboot should work fine right?
And can I keep cm12 as primary and add any stock based kk Rom to secondary Roms?
Click to expand...
Click to collapse
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK

deeplyyoung said:
Cm12 as primary with patched boot.IMG and till now you can't use stock ROM
Sent from my XT1033{LP} using TAPATALK
Click to expand...
Click to collapse
Cm12 as primary with boot.img from OP
And cm11? Is that perfect? How do we switch booting roms?

MultiRom V32 Resurrected [D851] Build:20150717 07/17/2015 (Fix)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for Nexus 7, But Ported over to the LG G3 (D851), It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port.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.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
* Boot from USB drive attached via OTG cable
-=[ Watch Video To See It In Action ]=-
I am not responsible in any way for anything that happens to your device in the process of flashing.
Please familiarize yourself with flashing and custom rom use before attempting to flash the MultiRom & its parts.
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. 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 choosing 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. The LG G3 (D851) Isn't compatible with this app yet.
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.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
Note 2: There have been reports that (not only) MultiROM does not work properly with older bootloaders. Update it to version 4.13 or newer in case you have problems.
MultiROM has 3 parts you need to install:
MultiROM (multirom_vXX_D851-signed.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (TWRP_multirom_D851_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.
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.
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 for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- 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.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
-- Under Construction at this time
​
Source code:
MultiRom: https://github.com/Tasssadar/multirom (Branch Master)
Modified TWRP: https://github.com/Tasssadar/Team-Win-Recovery-Project (Branch Master)
Stock kernel w/ kexec-hardboot patch: Not Ready (Use Released ones)
CM kernel w/ kexec-hardboot patch: CM-HardBoot Kexce patched Kernel (Branch test-2)
Device Tree: https://github.com/Eliminater74/multirom_android_device_lge_d851.git (Branch multiromkk)
HardBoot Kexec Kernel Patch: D851-CM_hardboot_kexec_kernel.patch
777Kernel By @777jon: 777Kernel NOT PATCHED
TootsiePop By @aclegg2011: TootsiePop NOT PATCHED
Note: Patch works on Stock as well. Just make sure you edit kernel config by hand. if used on stock.
Good IRC Clients: HexChat or Mirc
IRC Server:irc.freenode.net or chat.freenode.net
IRC Channels:#ubuntu-touch #multirom #twrp #android-root #android-dev #android #ubuntu #ubuntu+1 #ubuntu-devel #ubuntu-gnome #ubuntu-kernel #ubuntu-motu #ubuntu-offtopic #ubuntu-packag
IRC Server:irc.lightning.net
IRC Channels:#c-64 #warez+
XDA:DevDB Information
MultiRom Resurrected (D851) [Updated: 03/30/2015], ROM for the T-Mobile LG G3
Contributors
Eliminater74, Tasssadar
Source Code: https://github.com/Tasssadar/multirom
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: Android 4.4.X +
Based On: AOSP
Version Information
Status: Stable
Created 2015-03-31
Last Updated 2015-04-06

Please Try and let me know:
- MultiRom Installer: multirom-20150717-v32-unofficial-d851-zip
- MultiRom Installer: Mirror: multirom-20150717-v32-UNOFFICIAL-d851.zip
- TWRP Modified 2.8.6.X: twrp_multirom_2-8-7-x_d851_20150717-signed-zip
- TWRP Modified 2.8.6.X: Mirror: TWRP_MultiRom_2.8.7.x_D851_20150717-signed.zip
- MultiRom UnInstaller: multirom_uninstaller-zip-4f423237-22f2-4fe4-9509-9e52cb3dc3e6
- MultiRom UnInstaller: Mirror: multirom_uninstaller.zip
- Patched Kernel: LP kernel_hardboot_kexec_patch_20150403-signed.zip [Updated To Work Right]
-=[ Patched External HardBoot Kexec Kernels ]=-
-=[ Compiled By Eliminater74, w/permission By Respected Owners ]=-
- Updated 777Kernel: 777Kernel_Hardboot_Kexec_20150515-signed.zip [SaberMod 6.0] [LP 5.1.1]
- TootsiePop - - By @aclegg2011 : LP TootsiePop_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2]
- 777Kernel - - By @777jon : LP 777Kernel_HardBoot_Kexec_20150408-signed.zip [LP 5.0.2 ]
-=[External Patched Kernels ]=-
- Patched Kernel: [AOSP][D851]Rin Kernel 1.6.5[LOLLIPOP 5.0.2 ]
- MultiRom Dev Test:
- MultiRom Dev Test:
--=[ D851 Flashable BootLoaders ]=--​
- D851_BootLoader_10c.zip -
- D851_BootLoader_10m.zip -
- D851_BootLoader_10r.zip -
- D851_BootLoader_20b.zip -
​

Tips & Hints
Code:
MultiROM v32
=====================
* Minor GUI improvements
* Support for device encryption (with Android-based secondary ROMs only). See
FAQ in this device's XDA thread for more info.
* Bunch of ROM compatibility fixes
MultiROM v31
=====================
* Add support for "multimount" fstab (fixes CM12)
* 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
=====================
* Fix freezes in the boot manager
* You can now swipe between the tabs in the boot manager
* Minor UI adjustments
* SailfishOS support (for certain devices)
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
* Misc F2FS fixes
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 v22b
=====================
* Mount the real /data partition to folder /android/realdata in Ubuntu Touch,
enabling sharing data between Android and Ubuntu Touch. See
http://bit.ly/ut_sharing for more info.
MultiROM v22a
=====================
* Fix hardware keys not working for some users
* Update Ubuntu Touch patches
MultiROM v22
=====================
* Fix linux-type ROMs (Ubuntu Touch) failing to boot for some users
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
=====================
* Implement "boot the last ROM" auto-boot type
MultiROM v18
=====================
* Fix silent-but-unpleasant crash with exFAT
MultiROM v17
=====================
* Changes to support MultiROM Manager app
* Add support for exFAT
MultiROM v16a
=====================
* Fix kexec not working on some kernels
MultiROM v16
=====================
* Add overscroll bounceback effect to rom list
* Add support for controling via physical keys
* Bunch of under-the-hood changes for mako and m7 support
MultiROM v15
=====================
* Fix cmdline handling for kexec, doesn't change anything for grouper, just to
have the same version for both flo and grouper (no need to update)
MultiROM v14
=====================
* Find and change correct fstab (fixes freezes on boot)
* Mount /realdata without nosuid (fixes no root on 4.1 and 4.2 ROMs)
* Use libbootimg to work with boot.img files
MultiROM v13
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices
* Add run-on-boot scripts (for advanced users who know linux and bash, see
https://github.com/Tasssadar/multiro...n-boot-scripts)
* Use libbootimg to work with boot.img files
MultiROM v12a
=====================
* Detect kexec-hardboot patch in kernel even if /proc/config.gz is not
available
MultiROM v12
=====================
* Implement screen rotation and 1280x800 theme
* Fix auto-boot option
* Fix listview's fast scrollbar behavior
MultiROM v11
=====================
* Option to hide Internal ROM
* Option to rename Internal ROM
* Support for Ubuntu Touch
MultiROM v10
=====================
* Non-error message boxes aren't red now
* Add possibility to switch between several color themes, go to misc tab and
try it out
* New MultiROM installer format
* Add "discard" option to /data mounting
* Add battery status to misc tab (bottom right corner)
* Add brightness setting
* Implement ADB
MultiROM v9
=====================
* Make it compatible with LZ4 ramdisk compression
* Improve touch-related code. You should not get anymore phantom button
presses nor listview freezes
MultiROM v8
=====================
* Fix kexec-hardboot with new bootloader v4.18
* Search for already present USB drives on start
* Centre "MultiROM" title in main UI
MultiROM v7
=====================
* Correctly boot Ubuntu after recent kernel update. Read this post:
http://forum.xda-developers.com/show...postcount=1031
* Remove specific support for Ubuntu - it is now handled as "generic linux"
(with rom_info.txt file). Nothing should change for the users
* Sort ROMs alphabetically
* Add "progress dots" to USB screen, so that user knows that it is doing
something
* Recovery was also updated, don't forget to flash it
MultiROM v6
=====================
* Properly check for kexec-hardboot patch in kernel
* Internal" is always first in ROM list now, as originally intended
* Much more logging for kexec-related stuff
* Print last 50 lines of klog to "Emergency reboot" screen
MultiROM v5-2
=====================
* Fix ubuntu
* MultiROM still says it's v5. I did not change the version number because it
is literally one character fix.
MultiROM v5
=====================
* Support for ROMs with configuration file. This makes porting
Ubuntu/plasma/webos/anything much more easier. See the third post.
* MultiROM will no longer let you boot Ubuntu ROM if it's name contains
spaces, because the boot would fail.
MultiROM v4
=====================
* Fix GPS on ROMs other than Internal
* Minor UI changes
MultiROM v3
=====================
* Switch to Ubuntu 13.04. Version 12.10 is no longer supported
* Switch to kexec-hardboot based multi-booting. Read the first post.
* Add support for booting from USB drive
* MediaScanner no longer scans /sdcard/multirom, which means no useless
battery drain
* Recovery was updated, make sure to flash it, too.
MultiROM v2
=====================
* Add support for Ubuntu on 3G version of Nexus 7
* Fix some issues with 4.2 ROMs
* Recovery was updated, make sure to flash it, too.
MultiROM v1
=====================
* Initial version
Code:
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.
21.8.2014
=====================
* Remove Ubuntu Touch installation, installing via recovery is deprecated
* Add SailfishOS installation (only for supported devices)
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.
* Fix installation of non-Android systems to USB drives
4.6.2014
=====================
* Fix installation of bigger (>350MB) ZIPs as secondary ROMs
28.5.2014
=====================
* Fix installation of Ubuntu Desktop
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
* Some rendering optimizations, resulting in noticeably higher FPS in recovery
2.2.2013
=====================
* Fix GPG signature verification of Ubuntu Touch installation files
* Add support for mice connected via USB-OTG
* Fixup scrollbar behaviour in file list
24.12.2013
=====================
* Fix installing ROMs to USB drive
* Fix ZIP verification
* Support ZIP verification for secondary ROMs
15.12.2013
=====================
* Support OTA updates on secondary ROMs (tested with omni)
* Add "Swap ROMs" feature
* Implement "boot the last ROM" auto-boot type
* Many bugfixes
10.11.2013 - 01
=====================
* Fix some mounting issues when using ntfs or exFAT
10.11.2013
=====================
* Add exFAT support
* Support system-image based Ubuntu Touch installation
* Support Ubuntu Touch OTA updates, if Ubuntu is installed
via MultiROM manager app
22.10.2013
=====================
* Fix SuperSU reporting "failed" when flashed to secondary ROM
and completely borking the MultiROM part for any subsequent
uses of "Flash ZIP" or "Backup" option
16.10.2013
=====================
* Automatically inject boot sector with MultiROM
after ZIP installation or ADB sideload. Can be
turned off on "confirm flash" or "ADB sideload"
pages.
12.10.2013
=====================
* Support 'adb sideload' when adding ROMs
* Support rotation while using custom recovery theme
5.10.2013
=====================
* Don't display unsupported systems in "Add ROM" menu
23.9.2013
=====================
* Use libbootimg to work with boot.img files
22.9.2013
=====================
* Fix custom theme support
19.9.2013
=====================
* Partial rewrite of the codebase to make it compatible with multiple devices
* Add option to backup secondary ROMs
* Don't show "Flash ZIP" option for Ubuntu Touch ROM, it is not an Android
13.9.2013
=====================
* Update to TWRP 2.6.3.0
* Fix Ubuntu desktop image decompression
30.8.2013
=====================
* Update to TWRP 2.6.1.0
* Temporarily removed Timur's USB kernel, because it is not
4.3-compatible and I can't find sources
25.8.2013
=====================
* Clean rebuild of the recovery, I probably forgot to do that last time
and it wouldn't boot on some tilapia devices. No function changes.
21.8.2013
=====================
* Fix updater-script incompatibilities for some ROMs (e.g. PAC-Man)
27.7.2013
=====================
* Fix deletion of 4.3 ROMs with new SuperSU version installed
24.7.2013
=====================
* Don't ignore format("/system"); when flashing ZIPs to secondary ROMs,
this should fix updating secondary ROMs, particulary from 4.2 to 4.3
* Some fixes for 4.3 ROMs
* Add "remove boot.img" option to Android ROMs
21.7.2013
=====================
* Fix crash when installing Android ROM with kernel sharing enabled
20.7.2013
=====================
* Add rotation option to MultiROM settings
* Properly handle kernel flashing for Android ROMs:
you can now flash kernel via "Flash ZIP" option in "List ROMs" menu,
Aroma installer should work properly
* Fix ZIP flashing for 3G version of Nexus 7
9.7.2013
=====================
* Update to TWRP 2.6.0.0
* Support for screen rotation, Settings -> Screen
* Support for Ubuntu Touch
* Added options from MultiROM v11 to hide or rename Internal ROM
* MultiROM Settings menu was reorganized
* MultiROM options added to landscape layout
* Recovery now has Timur's USB host kernel
16.4.2013
=====================
* Fix "Add ROM" option not properly installing /data partition from
backup, if the backup is bigger than 1.5gb
* Make names of ROMs created from Android Backup prettier
9.4.2013
=====================
* Update to TWRP 2.5.0.0
4.4.2013
=====================
* Add support for MultiROM installer format
* Add new MultiROM settings (brightness, adb)
12.3.2013
=====================
* Updated to TWRP 2.4.4.0
* Add support for LZ4 & LZMA ramdisk compression
* Add some handy buttons to "flash complete" page,
thanks ikslawlok for suggestion
2.3.2013
=====================
* Fix freeze when selecting ROM in "Add ROM" option
in MultiROM menu
1.3.2013
=====================
* Updated to TWRP 2.4.3.0
27.2.2013
=====================
* Fix recovery kernel, so that you can boot linux ROMs even if
kernel in internal memory has older kexec-hardboot patch
* Enable brightness settings from TWRP
26.2.2013
=====================
* Updated to TWRP 2.4.2.0
* Add fast scrollbar to fileselectors
* Voldown to turn off screen ("sleep" mode)
22.2.2013
=====================
* Fix Ubuntu Touch installation with
combination of 4.2 as Internal ROM
21.2.2013
=====================
* Don't copy the ZIP to RAM while flashing ZIPs bigger
than 450 MB (currently only Ubuntu touch) in "Add ROM"
or "Flash ZIP" options. This prevents crash which would appear
due to low memory, but also means that these ZIP files
will be modified, which makes them unusable outside MultiROM
after flashing.
* Add Ubuntu touch support
2.2.2013
=====================
* Update to TWRP 2.4.1.0
* Don't reset ROMs location in "List ROMs" when going back
from managing ROM to the ROM list
* Fix recovery crash when there is too deep directory structure
in /data, thanks rifraf for debugging this
30.1.2013
=====================
* Update to TWRP 2.4.0.0
* Properly disable flash-kernel during Ubuntu installation.
This is important fix, because without it, Ubuntu
can rewrite your boot.img.
* Add option to wipe /data, /cache and dalvik-cache
of secondary Android ROMs
* Use gnutar binary compiled specifically for tegra 3,
means faster installation of Ubuntu
* Add "pressed" effect to all buttons, so that you know
if you pressed it or not.
* When installing Android ROM from ZIP which does not have
boot.img (armoma installer...), try to use current boot sector
instead of boot.img. The ROM may not boot, so you should always
add boot.img which is compatible to the ZIP file.
* Update to keep up with MultiROM v7
20.12.2012
=====================
* Fix "Add ROM" for backups in internal memory
------------------------------------------
* Update TWRP to 2.3.3.0
* Add option to Add ROM from backups
* Should be able to flash ZIP files for both grouper and tilapia
18.12.2012
=====================
* Update to support MultiROM v3
2.12.2012
=====================
* Fix "flash zip" option for ROMs without whitespace in name. I've
accidentally broke it in previous update, sorry :/
29.11.2012
=====================
* Fix "flash zip" option for ROMs with whitespace in name
25.11.2012
=====================
* Add Ubuntu support for Nexus 7 3G
24.11.2012
=====================
* Initial version
Code:
- 04-02-2015: First patched Kernel LP 5.0.2 (Source Directly from CM Github)
- Please understand That not all of the patched Kernels are OverClock.
- All Compiled External Patched Kernels By Eliminater74 W/Permission, Will Not have the kernel Name in the about box.
- If a kernel isnt listed that you would like patched, Please Leave a msg to OP along with Links.
- OP received permission from all external kernel owners which kernels he used for patching.
- If you are owner, And your kernel is listed without Permission, Leave msg to op to have it removed.
-=[ I find the best way to utilize MultiRom ]=-
- Create a 2nd partition on your External sdcard Formated ext2 (maybe 5 gigs, I use 10gb, But I have a 128gb card)
- Keep your main partition exfat or fat32, exfat is better for sdcards.
- Remember to create the 2nd partition as the last part. First partition is the one that gets automounted.
- Use that ext2 partition as your Secondary external rom install location.
- fat32 is limited and slow, exfat is faster then fat32
- Remember that your Primary rom must have a Hardboot Kexec patched Kernel.
- Your Secondary roms dont need to have that patch.
*** Please Read: ***​NOTE: Do to some bug, Do not flash from Internal Memory if your flashing for secondary rom. The bug will always cause it to overwrite primary rom.
So flash from SD Card Always when flashing secondary roms.
-=[ Please Read ]=-
Just to clarify The patched kernel section,
You must have a kexec hardboot Patched Kernel for whatever Android Rom your using,
Example: Stock 4.4.4 Needs a stock based Patched kexec hardboot Kernel
CM 4.4.4 Needs a patched Kernel based off the CM source
You can not have Stock Rom with a patched Kernel from a CM source. and vise versa..
They have to match..
DO to most people running Custom Roms, I was only going to work on CM related kernel patches.
I really didnt think about stock based roms. I hope that maybe someone else could take up that project for me.
Anyone Interested in Porting kexec hardboot
Thats the link for anyone who wants to give that a shot.

Firsttttttt
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
I managed to soft brick my phone twice on Multirom. Than I stupidly somehow made it so the ROMs would ONLY flash from OTG flashdrive and if I pulled it out it would soft brick...
Soooo... Testers? Not I. But thanks brotha

yanowman said:
Firsttttttt
---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------
I managed to soft brick my phone twice on Multirom. Than I stupidly somehow made it so the ROMs would ONLY flash from OTG flashdrive and if I pulled it out it would soft brick...
Soooo... Testers? Not I. But thanks brotha
Click to expand...
Click to collapse
I dont blame you. After that, I wouldnt wanna try anything either...
People that test this out, Must be able to recover from a softbrick just in case.. I wouldnt want anyone that doesnt know how to Recover from a Softbrick to try this.
NOTE: I am not saying this Will Softbrick your phone, What I am saying is: Be Prepare Just in case of the unthinkable happens.

Will give it a try as soon as I get home and have easy access to a PC for recovery, in case anything would go wrong.
Also, I have the previous MultiROM right know, how would I go installing this?
I loved MultiROM on this device, so glad you're bringing the development back.... And just in time for LG LP

Papote3 said:
Will give it a try as soon as I get home and have easy access to a PC for recovery, in case anything would go wrong.
Also, I have the previous MultiROM right know, how would I go installing this?
I loved MultiROM on this device, so glad you're bringing the development back.... And just in time for LG LP
Click to expand...
Click to collapse
Since your version is most likely the older version, Just zap the uninstaller.zip after your take a nandroid backup.
That way, if something messes up, you can boot to recovery and reinstall your original backup..
Thats the main reason, I wanted to make sure the recovery worked. ( I had my finguers crossed when I flashed that) :fingers-crossed:

I can personally verify That MultiRom Resurrected Works......... I did take the time to Flash Compatible patched Kernel and Recovery then MultiRom..
Booted menu and everything worked.
I do need to fix the res on it. Too small. Its just a tw flag or mr flag in boardconfig.mk under device tree..
Now I did compile a 2nd version with a few fixes and patches that I made.. First compile was 100% @Skin1980's source to his device tree..
2nd one is from my patched device tree.
Update: I found out how to fix the small looking boot screen. Will compile fix and re-up it later.
Fix was: MR_DPI_FONT := 350 # Was set at 219, and since 340 would be for a 4.95" screen.. I figure try out 350.

I'm still using the original MultiROM and still have all the files. Couple of questions...
1. Uninstaller. I can use the one I have now or the one you provide (assuming there's some difference).?
2. Can I still use skin1980's kernel or is it preferable to use Rin?
On a related note, there was a time when if a ROM's kernel would crash when flashing a secondary I would go to 777jon kernel (because it was new and cool). After awhile, though, it no longer worked with ROMs released in the past month. Furnace kernel, too, on a few tests. Only the tootsie-pop kernel works for me.
Was just wondering why 777jon worked in the past with this MultiROM but no longer does. Is it the kernel, this aged multirom, or something in newer ROMs.
Fusion ROM is one secondary using 777jon kernel w/out issue. It's from February. Validus includes that kernel but it doesn't work. With tootsie-pop it's A-OK.
Am I rambling.? Sorry. ?
Sent from my LG-D851 using Tapatalk

marcdw said:
I'm still using the original MultiROM and still have all the files. Couple of questions...
1. Uninstaller. I can use the one I have now or the one you provide (assuming there's some difference).?
2. Can I still use skin1980's kernel or is it preferable to use Rin?
On a related note, there was a time when if a ROM's kernel would crash when flashing a secondary I would go to 777jon kernel (because it was new and cool). After awhile, though, it no longer worked with ROMs released in the past month. Furnace kernel, too, on a few tests. Only the tootsie-pop kernel works for me.
Was just wondering why 777jon worked in the past with this MultiROM but no longer does. Is it the kernel, this aged multirom, or something in newer ROMs.
Fusion ROM is one secondary using 777jon kernel w/out issue. It's from February. Validus includes that kernel but it doesn't work. With tootsie-pop it's A-OK.
Am I rambling.? Sorry.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
You experienced kernel panics because of this:
MR_RD_ADDR
This option might not be needed for your device. It sets address in boot.img to unpack ramdisk into, and most devices can handle MultiROM changes even without this option. But, some devices (Nexus 7 and Nexus 4) will panic on boot when the ramdisk is bigger than expected. As to what value to set, well, it's more about guessing than anything else. Look at default ramdisk address in your boot.img and try to use a bit higher address.
I set it too MR-RD-ADDR 0x2500000
I took the ramdisk address of a common boot.img which came out at 0x2200000 So I made it 0x2500000 Should be just the correct size.. If not. I change again.. its more of a guessing game.
You can use any kernel that has the patch.. So yes. and as to uninstall.. I think they are all pretty much the same.. but better use the one that came with your multirom version.. since skin's version. Multirom has changed alot,
but also the uninstaller I have should clean up the older version as well. its all pretty much touch and go kinda thing.

I was one of the testers of the skin1980's multirom port.
Stopped using it since it was not updated and the roms from the last month or so did not boot as secondary.
Now I installed TWRP 2.8.6.1 and deleted all secondary roms.
So now I should use the un-installer from you and then flash the multirom TWRP and the Multirom file?
EDIT: Secondary roms install but when selected during the boot options, only the primary rom boots in its place

Many thanks sir for the quick response. Always fun having something new to try (and break and fix).
Will check this all out tonight.
Sent from my LG-D851 using Tapatalk

Anybody other than me try this?

I used MultiRom for about a month. I had a ball with about half a dozen Lollipop Roms. I even sent a donation . It was fun but now I need the G3 for work and can't take the risk.

arifqur said:
I was one of the testers of the skin1980's multirom port.
Stopped using it since it was not updated and the roms from the last month or so did not boot as secondary.
Now I installed TWRP 2.8.6.1 and deleted all secondary roms.
So now I should use the un-installer from you and then flash the multirom TWRP and the Multirom file?
EDIT: Secondary roms install but when selected during the boot options, only the primary rom boots in its place
Click to expand...
Click to collapse
Can you tell me where you installed secondary rom to, and what file system if other then internal.. also ill check into this.
Im still working on getting the screen in place.. Dont forget you have to inject the multirom into every secondary install.
you might want to reinstall, and make sure that box is clicked. Im not sure, but that could be the problem why its not booting that rom after you install it.
Ill check into it though.

hmm.. There is a problem with the booting of the secondary roms.. It seems to only boot the internal only.
Im looking into this. I got so much going on right now, ill try and see what the problem is and fix it.
Yea, seems to install just fine, and everything works up to the point it only boots the Primary rom and nothing more.
So, could be one of my settings that I added to the boardconfig.mk for ramsize. Ill delete it and recompile and try again.
I did manage to get the screen size correct at least.. dpi set too 430 corrected that..
ramdisk address Ill remove that setting and recompile.
Ill let you know when I get a fix for this.
Update: Booting works when installed on External Drive. If install on Internal It wont work right. Im looking into that.........
But like I said, it worked for me installing it on my external Drive thats 128gb /fat32 ....

Eliminater74 said:
Can you tell me where you installed secondary rom to, and what file system if other then internal.. also ill check into this.
Im still working on getting the screen in place.. Dont forget you have to inject the multirom into every secondary install.
you might want to reinstall, and make sure that box is clicked. Im not sure, but that could be the problem why its not booting that rom after you install it.
Ill check into it though.
Click to expand...
Click to collapse
Eliminater74 said:
hmm.. There is a problem with the booting of the secondary roms.. It seems to only boot the internal only.
Im looking into this. I got so much going on right now, ill try and see what the problem is and fix it.
Yea, seems to install just fine, and everything works up to the point it only boots the Primary rom and nothing more.
So, could be one of my settings that I added to the boardconfig.mk for ramsize. Ill delete it and recompile and try again.
I did manage to get the screen size correct at least.. dpi set too 430 corrected that..
ramdisk address Ill remove that setting and recompile.
Ill let you know when I get a fix for this.
Update: Booting works when installed on External Drive. If install on Internal It wont work right. Im looking into that.........
But like I said, it worked for me installing it on my external Drive thats 128gb /fat32 ....
Click to expand...
Click to collapse
Thanks for your response.
Yeah installed it to my Internal Storage as you mentioned.
Waiting anxiously for a working Multirom.
Good to know that you got the DPI fixed

arifqur said:
Thanks for your response.
Yeah installed it to my Internal Storage as you mentioned.
Waiting anxiously for a working Multirom.
Good to know that you got the DPI fixed
Click to expand...
Click to collapse
Im trying to get a fully working multirom. I would say this is about 75% working...
I did find out that it only boots the first listed on internal rom and first listed on external rom.
Example:
internal storage: 1rimary rom 2: blisspop 3: Nobody would have 3 on their internal I hope.
External SDCard: 1:RR 2:Blisspop 3:Noname
USB Storage: 1:BlissPop 2:RR 3:something
Here is the example in action now:
you get boot menu, now you choose to boot from USB, and you want to boot RR but it boots blispop since its #1
Now again you get to boot menu and you boot from external SD Card: you choose #2 blispop but it boots #1RR
same thing with internal storage..
Now you get it.
But im running test and checking out pluss im on #multirom on irc freenode.. the creator or multirom is there but away from his computer.
Ill talk to him when he gets back. Creator is Tasssadar..

MultiRom Logs:
MultiROM logs everything into kmsg.
Usually, when some error happens during boot, it will create /sdcard/multirom/error.txt file in which is dmesg exported.
If it does not, you can reboot to recovery and get kmesg from last boot from file /proc/last_kmsg. This only lasts through one reboot. All MultiROM's messages are prefixed with multirom, so you can just grep for that.
There is a chance that MultiROM just crashes (you'll know that when Internal ROM boots instead of the ROM you've selected).
In that case, there is message MultiROM exited with status X in the kmesg. If the X is anything else than 0, it has crashed.
Report this to me along with the rest of the log.
Update: I need people who installed this and tried to boot second rom, to drop to shell
and type: dmesg | grep multirom >multirom.txt
connect phone to computer; type adb shell
then cd sdcard
then type: dmesg | grep multirom >multirom.txt
send me the txt file.. I need to check something out.

MultiRom Resurrected Now Fully Works:
After a 20 min talk with Tassadar, Who is the Creator of Multirom, He helped me fix the problem that was keeping Multirom from
running Correctly. It was pretty much a very simple 1 line fix.
So now, Download the New Fixed Version, and Try it out.
I will upload it after I press Submit on this message.. Download it all, Because I fixed everything..
IRC Conversation With Tassadar:
Code:
<Tassadar> <3>[ 14.922921 / 03-02 17:01:51.359] trampoline: MultiROM exited with status code 256!
<Tassadar> it crashed
<Tassadar> https://github.com/Tasssadar/multirom/blob/master/main.c#L42 somewhere around here
<Elimin8er> what would the status code 256 be ? I am kinda new to this.
<Tassadar> that won't tell you much, it's probably segfault
<Elimin8er> Is this going to be a pain in the ass for me to fix? or am I pretty much screwed
<Tassadar> dunno why it would be crashing there. I'd probably just ran it under debugger, which is indeed not easy to set-up if you don't know what you're doing
<Elimin8er> give me a idea on what debugger and how and im sure I can figure out the rest
<Tassadar> hmm, how exactly did you add support for your device into kexec-tools?
<Elimin8er> https://github.com/Eliminater74/multirom_android_device_lge_d851.git <--- do you mean my device tree
<Elimin8er> I didnt do the patch kernel.. I used a already patched kernel
<Elimin8er> rin kernel
<Elimin8er> I pretty much just stuck to your guide on how to build for my device..
<Elimin8er> I used the multiromkk branch.. the master is just the one I got from skin1980 who ported the first one
<Elimin8er> long ago.
<Tassadar> https://github.com/Tasssadar/kexec-tools/blob/master/kexec/arch/arm/mach-hammerhead.c#L185 try adding "d851" into this list (kexec-tools is a folder in the multirom source directory)
<Elimin8er> Tassadar, ok, Now what exacity did you want me to do?
<Tassadar> like explain what is it doing or what are you supposed to do?
<Elimin8er> you said try adding d851 into some list..
<Tassadar> yeah, add it and rebuild it and try if it still crashes
<Tassadar> into the list I linked there
* nkk71 is now known as nkk71__away
<Elimin8er> Tassadar, you mean here: .boardnames = { "hammerhead", "bacon", NULL }, ?? change that or add to it ?
<Elimin8er> sorry im not a pro at this.. im just learning
<Tassadar> change that line to be ".boardnames = { "hammerhead", "bacon", "d851", NULL },"
<Elimin8er> ok I got it.
<Elimin8er> hmm
<Elimin8er> ok done that.. going to try the recompile now.
<Elimin8er> btw, could java version cause any of tht :???
<Tassadar> no
<Elimin8er> just making sure.. and I am compiling on a ubuntu 15.04 system.. but I also build a few roms with no problems on that machine too
<Elimin8er> I compile CM12 and RR for the samsung galaxy S tab 10.5 on that machine. so I know everything needed is there\
<Elimin8er> im going to go get something eat while its compiling still. afk...
* Santhosh_m90 has quit (Remote host closed the connection)
<Elimin8er> Tassadar, system/extras/multirom/kexec-tools/kexec/arch/arm/mach-hammerhead.c:185:51: error: called object '"d851"' is not a function <---- error un multirom_zip
<Tassadar> show me how does the line look like now
<Elimin8er> .boardnames = { "hammerhead", "bacon", "d851" NULL }, <-- I forgot the ,
<Tassadar> yes
<Elimin8er> ok fixed that...
<Elimin8er> I only fixed it locally, if everything works ok, ill push it to my github and just track changes from your main one
<Tassadar> I'll push it to my github if it works for you
<Elimin8er> ohh ok
<Tassadar> there is one other error there, it shouldn't have crash, just tell you that d851 is not supported
<Elimin8er> the device tree is the same one the skin1980 used on an older version of your multirom and it worked ok. Just alot of kernel panics do to the ramdisk address size thing that I read on your guide.
<Tassadar> it got changed
<Tassadar> for v32
<Elimin8er> ok im sending it over.. btw, could a messed up kernel cause any of that? I used a pretty repital kernel well known.. they create for most all G3's
<CaptainThrowback> wait, there was a ramdisk address size change?
<CaptainThrowback> is that why I haven't been able to get anything booted since the encryption merge?
<Elimin8er> No.. im talking about the mr flag
<CaptainThrowback> maybe Tassadar can help me with my mach-m8.c file some day
<Elimin8er> MR_RD_ADDR := 0x82500000 <--- this flag
<Elimin8er> but I used 0x2600000
<Elimin8er> im installing 2nd rom now.. then ill see what happends
<Elimin8er> Tassadar, I think it that worked.. its loading the 2nd rom now..
<Elimin8er> Tassadar, thank you for your help
<Elimin8er> yep, it worked..

[MOD] MultiROM v33b [No Kexec Workaround][2017-02-09]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Wileyfox Swift. It can boot any Android ROM. 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
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
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.
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.
2. Manual installation
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP to flash it.
MultiROM - download the ZIP file from second post 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 MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
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 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 MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash 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 for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- 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.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.​
Source code
MultiROM - https://github.com/multirom-swift/multirom
Modified TWRP - https://github.com/multirom-swift/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/multirom-swift/android_device_wileyfox_crackling​
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiROM, Tool/Utility for the Wileyfox Swift
Contributors
beroid, nkk71
Source Code: https://github.com/multirom-swift
Version Information
Status: Beta
Created 2016-11-23
Last Updated 2017-02-08

Downloads
AndroidFileHost
Changelog
MultiROM
Code:
====================
02-09-2017
====================
* MultiROM v33b
* Fix: sdcard on multirom loader
====================
01-25-2017
====================
* MultiROM v33a
* MultiROMMgr app support
* Patches by nkk71:
* Fix: Update external partitions mount strategy
====================
01-13-2017
====================
* Some fixes
====================
23-11-2016
====================
* Initial release
TWRP
Code:
====================
01-25-2017
====================
* TWRP 3.0.3-0
* MultiROMMgr app support
* Patches by nkk71:
* MultiROM: Create real block device for fake boot.img (fixes long kernel flashes)
* MultiROM: Fix restorecon to use ROM's own binary
* MultiROM: Add failed boot.img injection warning
====================
01-13-2017
====================
* Some fixes
====================
23-11-2016
====================
* Initial release

No-kexec workaround
Mini FAQ:
Q: What is the no-kexec workaround?
A: The no-kexec workaround by nkk71 allows you to use MultiROM without having to flash a kexec enabled kernel.
Please read all things about no-kexec workaround from the author words only, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4

Update
New build is up!
MultiROM+TWRP

Thnx beroid works flawesly on my gm4g

Update
Multirom v33a
Added MultiROM Manager app

Can't boot on ROMs that are installed on sd card

Encrypt ROMs with Multirom for Wileyfox Swift
Thanks a lot Beroid for all your amazing work on the Wileyfox Swift – not only for Multirom, but also for TWRP and crDroid.
I have the WF Swift for two months and I have tried all these achievements: everything works perfectly ! :good:
I have a question about Multirom : is it possible to encrypt one of the ROMs installed ?
Considering this post : https://forum.xda-developers.com/showpost.php?p=34577869&postcount=3 , it seems that it is not possible to encrypt the primary ROM, only the secondary one, but it seems to depend of each device…
Do you think it is possible for Multiron on the Wileyfox ?
Thanks again ^^

10.jear.old.child.alan said:
Can't boot on ROMs that are installed on sd card
Click to expand...
Click to collapse
Thanks, fixed
use multirom manager app to update
Arthury said:
I have a question about Multirom : is it possible to encrypt one of the ROMs installed ?
Click to expand...
Click to collapse
From https://forum.xda-developers.com/htc-10/development/mod-multirom-33a-twrp3-0-2-t3463838
Encrypted devices: Your secondary ROMs do not know your device is encrypted, do not (again: do not) try to encrypt your device while booted into a secondary ROM.
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse

Still says my device is unsupported

Thanks Beroid.
Since v32, MultiROM supports encryption on this device [Nexus 7] (it has to be added for each device separately).
Click to expand...
Click to collapse
Is it envisaged to add this encryption function also in Multirom for Wileyfox Swift ?

10.jear.old.child.alan said:
Still says my device is unsupported
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=69751836&postcount=2
Arthury said:
Is it envisaged to add this encryption function also in Multirom for Wileyfox Swift ?
Click to expand...
Click to collapse
No

@beroid will this twrp ever be updated to support oreo roms?