yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Natakranta:
That's stock 44S - it's karnel doesn't have kexec hardboot patch which is necessary on primary ROM for secondary ROMs to be booted.

If you flash it as secondary and then you move it to be primary, you need to flash on it a karnel with kexec hardboot patch, like AK karnel.

I've got a feeling you are making the whole process harder than it actually is.

Let's start from scratch.

What is your current ROM?

What you want to have as primary and what as secondary/ies?

I'll try to help with easiest setup.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] david72262:
You have the exact set up I'm looking to do been a slim user for over a year but brand new to multi rom. Do the slim roms work out of the box with multi rom or do they need a different kernel and if so what one or ones do you use? Thank you for your help.

I went in to your profile and followed your posts and got my own answer ak thank you
[ONE Android Development] Funk Wizard:
Wow thanks you so much for taking out your time to help me out, that to on the 31st when everyone is getting ready to party :D :good:

Now My current setup is Blisspop 1.5 29/12 Built + AK 070

I would like to make 11s 44s stock rooted as my Primary and Blisspop or Temaseks 5.0.2 versions as secondary option.

As i keep dirty flashing Blisspop due to almost daily builds, i do not want to keep that as my primary.

It looks like its a lot harder to get back to stock 44s, i think i rather Flash Mahdi 2.9 + AK as a secondary and then move it to primary via Multirom.

Just missing xposed and CM theme engine so i thought better have a Primary ROM which offers these 2 and secondary L Roms.

What do you suggest:confused:
[ONE Android Development] Natakranta:
SlimSaber 4.4.4 has kexec hardboot patch implemented, but it will not be updated any more. Both Fusionjack and kantjer deleted their KitKat sources. Last one I still have on SD and was using as primary for last month is

SlimSaber-bacon-4.4.4-20141126

With it and latest MultiROM 30b and MultiROM TWRP Dec.13 I can straight forward install Robbie's SlimLP builds (no updater script modification necessary since 30b) or Fusionjack's and kantjer's SlimSaber LP builds.

Yesterday I clean flashed SlimKat 9 as my primary. I couldn't boot my secondary ROMs as it appeared official SlimKat 9 karnel doesn't have the kexec hardboot patch necessary for secondary ROMs to boot.

I flashed latest AK 72 on it and it runs great (Slim karnel runs great as well) and allows to boot secondary ROMs.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.

---------- Post added at 03:54 PM ---------- Previous post was at 03:41 PM ----------

Then it's very simple. Install MultiROM manager app from Play and let it install MultiROM v30b and Recovery 2014-12-13 (which is MultiROM custom TWRP 2.8.2.0). It will ask you to reboot to recovery to finish the install, allow it. Notice you don't need to install karnel through MultiROM Manager app as the AK 70 you have has already the kexec hardboot patch for MultiROM. See me screen.

Go back to recovery and make a nandroid backup of your current ROM (blisspop with AK70) and make a clean flash of calculin' stock rooted 44S. Flash latest greatest AK 72 on it - necessary to have patched karnel on your primary ROM.

Boot it and setup.

Boot back to recovery. Go to MultiROM menu and add ROM. As a source, instead of zip, chose backup and your blisspop nandroid. Now you have it as secondary ROM. If you want to update it with new nightly go to MultiROM menu in TWRP, tap the ROM and n you will see different options, like wipe cache, wipe dalvik, flash - that's where you flash update for this specific secondary ROM. Here flash as well gapps of you need and SuperSU or any other zip you flash with your ROM.

Edit

If you use materialised theme on TWRP you need to change it from standard to MultiROM version, otherwise you will not see MultiROM menu in TWRP.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] david72262:
Thank you this sure is going to be a lot easier than flashing setting up playing for a while backing up then flashy my backup of slimkat all the time
[ONE Android Development] Funk Wizard:
Many Thanks for your advise, i shall proceed accordingly :o

Wishing you a Happy New Year 2015, i shall get back to you from now on for any assistance :good:
[ONE Android Development] gqukyo:
I just took out Liquid Smooth from primary to BlissPop for primary with custom kernels to boot my secondary roms. Since all the LP roms are basically still in beta, I'm just testing them all with multirom and so far BlissPop is my preferred choice with SlimSaber as a close second. I do have a stock rooted cm11s as secondary but the only thing I miss from that are the xposed modules...
[ONE Android Development] tobitege:
[MENTION=5180758]Natakranta[/MENTION]: your above post #1685 should be added to the OP as a tutorial post, great writeup!
[ONE Android Development] skodaslx:
I read, that the new cm12 roms only work with the new modem from the lollipop alpha from oneplus.

And all other roms still need old modems. What does this mean for multirom? No more multirom for old and new roms as primary and secondary?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] tobitege:
Yes, that could be annoying when switching between roms, especially KK, to reflash modems. Maybe it's time to stick with one rom. :)
[ONE Android Development] mak725:
I have a question:

You can change the ROM of secondary to primary? :confused:
[ONE Android Development] tobitege:
Yes, look for "Swap ROMs" in MultiRom menu, which offers all related options.

In any case, whichever rom you will end up with as the primary rom, it must have a kernel that has kexec_hardboot patch for MultiRom to work correctly. After a swap open the MultiRom app in your primary rom and it will tell you if the kernel supports it and display an appropriate message.
[ONE Android Development] KINGbabasula:
Updated MultiROM TWRP to 2.8.3, I don't really know what changed, there are a lot of commits, but it seems to be working well, you can update through the app :D
[ONE Android Development] `SBR`:
how to wipe System in MultiRom and how to restore only the selected items like (System, Data) in Multirom. ?

this can be done in Primary Rom, but in Multi-rom i can't find the options. Please suggest any workaround
[ONE Android Development] tobitege:
[MENTION=2477260]`SBR`[/MENTION]: you can't do that, correct. You'd need to swap your secondary to primary and then use the default TWRP actions for that.

---------- Post added at 17:01 ---------- Previous post was at 16:58 ----------

Thank you, was looking forward to this! Will you let us know when you uploaded the recovery? The 2nd post links point to previous version still.
[ONE Android Development] KINGbabasula:
It was meant to be updated from the app, but I'll update the link tomorrow anyway
[ONE Android Development] tobitege:
Wonderful, I'll get it via the app then and grab it from partition, thank you!
[ONE Android Development] KINGbabasula:
I have updated the link to download directly the recovery https://www.androidfilehost.com/?fid=95887005526787273
[ONE Android Development] Natakranta:
Thank you for your continues support for OPO, much appreciated!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] ¿GotJazz?:
I would like to retain the v4.4.4 CM11S and install the new official v5.0.1 pre-release OPO CM12.

I have a few questions (I'm assuming that having different versions of Android isn't a problem):

Can either the OPO CM11S or the pre-release CM12 be my "primary" ROM?

Do I need to install a specific kernel with the MultiROM Manager? I see options for both CM11/CM11S/AOSP and CM12, and a ROM based on each will be installed.

Thanks!
[ONE Android Development] Hoka-Hey:
the new official v5.0.1 pre-release OPO CM12 Install fine as a secondary rom

You do not need to install a different kernel for it to work
[ONE Android Development] skodaslx:
Wich rom do you use as primary?

Also a CM12 based rom or a CM11/android 4.4.4 rom? And if you use a 4.4.4 which modem are you using?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] Hoka-Hey:
My primary is stock CM11S without any modifications
[ONE Android Development] skodaslx:
Sorry, but I have to ask more.

As you are running 4.4.4 as primary and you flashed the 5.0. as secondary your modem must be still an "old" modem, not the new one from CM12. Do you have no problem with the CM12 because of your old modem?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] Hoka-Hey:
No problems, but I always thought that the modem was contained in the Rom
[ONE Android Development] skodaslx:
You have only one modem for all roms.

If you let the CM11S as primary untouched and flashed the CM12 as secondary, then you still have the modem from CM11s also for your secondary rom CM12. And I'm curious to know if you have any problems with CM12 because in every thread about CM12 they are talking about that the CM12 will only work to 100% (like proximity sensor) with the new modem.

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] sozofriend1234:
I just installed CM12 as secondary rom over the stock 11s and it is not booting up. It shows an error in the multirom boot window that the custom kernel is needed with certain K something support from the first post.

Could you please elaborate how you installed the cm12 as secondary with cm11s and made it work.
[ONE Android Development] tobitege:
Install a CM11-compatible custom kernel with kexec_hardboot patch like ak kernel over your primary rom then it should boot secondary as well.
[ONE Android Development] magnamentis:
sorry to see that you got a wrong advice first while [MENTION=4877142]tobitege[/MENTION] is absolutely right. for the future to make it easier for you, you can check your configuration and what's missing in the multirom app when you open it you should see a status page which indicates what's missing and/or available updates. like that you have less to trust differing opinions but get the right information from the dev of multirom via his app. hope this is helpful
[ONE Android Development] skodaslx:
Sorry, I didn't get what you mean.

The first post you quoted was mine about the modem.

So in future the app will tell me what modem I have and which rom (CM11 or CM12, which needs the alpha modem) I can flash because of the modem?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] magnamentis:
sorry, quoting error, my bad, has been corrected.

by the way, the modem works very well with cm11 latest nightly and boeffla kernel ( just to name my config while the kernel should not be relevant )

i'm on primary bliss rom with boeffla beta3 and on secondary cm11 latest nightly with boeffla beta2

so should you feel like upgrading to newest modem, don't worry, in most cases radios are backwards compatible, which is often not the case with bootloaders. often these two things are brought together in threads upon releases, but modems are not so much API sensitive.
[ONE Android Development] skodaslx:
So you are using as primary a 5.0. rom and as secondary a 4.4.4 rom and you have the alpha modem from the CM12 running? And no problem with the 4.4.4 rom (proximity sensor)?

Gesendet von meinem A0001 mit Tapatalk 2
[ONE Android Development] magnamentis:
exactly, just try to quote or mention because albeit i felt it's for me i have to look back in the thread to make sure if there is no quote or mention.

no critizism, just a little request for convenience.

config mentioned above it correctly posted and runs great. just don't forget to: "Inject curr. boot sector" after flashing.
[ONE Android Development] rifraf1:
Anyone in here use Temasek Rom? It was loading fine as a secondary, with modified script, up until the last few versions. I keep getting the binaries error message, tried it with both the 20141213 and the latest 20150105 recoveries.
[ONE Android Development] tobitege:
It's working just fine. Do not use the updater script zip from [MENTION=3814731]katinatez[/MENTION]'s download folder "as-is" since that is fairly outdated compared to current builds.

Instead, edit the original, current updater-script from the current build and only copy over exactly lines incl. 12 - 24 lines from k's modified script (or see below code for commented out lines, which makes the changes clearer).

That basically changes the original "if" condition to just execute the commands of the "else" part for the OTA sig check (original: lines 18-23).

The above method has worked for me for a couple of weeks across several builds.

Below are the changed lines incl. 12-24 with the only changes being lines commented out by a hash at line start:

#if is_mounted("/data") then
#package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
#package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
#set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
#run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
#else
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
#endif;
[ONE Android Development] ek69:
I had no idea

Maybe this should be pointed out in the thread [MENTION=3814731]katinatez[/MENTION] ? I've been using the outdated updater-script file lol

Sent From Lollipopified Bacon Goodness!
[ONE Android Development] rifraf1:
I was doing those exact updates to the included updater script and it was not working. But your response led me to the answer.

I was changing this line of code :

run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

to

run_program("/tmp/otasigcheck.sh") != "0" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");

just like [MENTION=3814731]katinatez[/MENTION]'s original modified script, but now by leaving it alone the install goes through successfully.

Happy flasher again, thank you. :D
[ONE Android Development] tilaksidduram:
the easiest way is to use the multirom manager app from the playstore, this app will install the multirom recovery, Multirom bootloader and a custom kernel with kexec hardboot. once all of this has been installed you can then boot into ur multirom recovery and flash CM12 as secondary.

if you already installed multirom recovery and multirom boot loader manually, then just download the AK kernel from the XDA and flash it on the primary rom once that is done, reboot back into recovery and flash ur secondary roms.
[ONE Android Development] ghismo83:
no usb otg support with last recovery :(
[ONE Android Development] magnamentis:
confirmed, but was not working on last version as well. it recognizes the stick but it does not appear in the menu to backup, restore, etc.
[ONE Android Development] Natakranta:
I've just checked and confirm. Storage options show only internal memory, it doesn't show my microSD mounted through Meenova adapter. [MENTION=5093942]KINGbabasula[/MENTION] I'd appreciate if you could take a look at it.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] giaur:
I would like to install CM12 nightly as primary and ColorOS on USB as secondary. Is it possible?
[ONE Android Development] Bunglemat:
OK I'm lost and really interested in this.

I'm running pa latest and installed this through multirom app from play store.

I'm looking to install the unofficial pa lollipop as secondary and it fails every time. It also states I can do this but I have to unshared the kernel for this to work I cannot find this option and if there is something else I'm doing work can you explain.

Thank you in advance this has baffled me
[ONE Android Development] beany>:
If you are saying it falls to install is it saying it can't flash to secondary? This is due to updater-script. there is an option Swap ROMs where you can move the primary to secondary, then I usually wipe dalvik/cache/system/data and install the ROM as primary. You can then swap them round if you want. If the secondary doesn't boot due to no kexec patch then you need to flash a suitable custom kernel on your primary (or do it from the multirom app) ak and Boeffla kernels highly recommended have this.
[ONE Android Development] hamdimo:
what am i doing wrong?

i can't boot up any cm12 rom ( latest official nightlies and also blissROM 1.4 and 1.5) my primary rom is CM11S 44S. the kernel is the latest AK v.080.

as a secondary rom i have official Paranoid 4.6 which boots up.

when i choose a lollipop rom, the phone hangs on the boot logo then restarts again to the multirom list of roms!!!!!

i wanna keep CM11S as primary

what the hell am i doing wrong??????

AHHHHHHHHHHHHH i'm pulling my hair out here :mad:
[ONE Android Development] stab244:
I had to uninstall multi ROM then reinstall multi ROM for L based ROMs to work. You lose all your secondaries this way so back them up first.

Sent from my bacon
[ONE Android Development] hamdimo:
Ok i'll try this.

thanks for ur reply
[ONE Android Development] hamdimo:
Yaaaay, I'm typing this from CM12 :) thanks lot buddy. [MENTION=2222926]stab244[/MENTION]
[ONE Android Development] mani0008:
CM12 nightlies are still not working for me even after reinstalling multirom and some other ROM are also not working, they all stuck at boot animation and restarts the phone. But Blisspop working fine as secondary ROM.
[ONE Android Development] venky61:
Hi,

If we delete a secondary Rom which was installed via Multirom, what all data will be deleted other than the apps itself?

Will the pics, messages, songs and media from chat clients copied or stored during the usage of that secondary rom will also be deleted.
[ONE Android Development] tobitege:
[MENTION=5735467]kandalamv[/MENTION]: your regular data on internal sd card (where pictures/music/movies is located) is untouched by MultiRom and shared between all roms. It'll be just fine.
[ONE Android Development] venky61:
Awesome...Thanks

No need to worry exploring more Roms for short period of time then :D
[ONE Android Development] booyou:
I had the same after removing and installing. I got it working after a few reboots...

Remove multirom with multirom app.

Reboot phone.

Reboot into recovery.

Reboot to normal Rom.

Install multirom from app, including recovery (even though it's not needed).

Reboot phone.

Reboot into recovery.

Install cm 12 nightly and gapps.

Remove boot.img (not sure if needed, but that's what I did). Reboot into normal primary Rom.

Reboot to cm.

Sent from my Oneplus One
[ONE Android Development] venky61:
I was trying to install Color OS as a secondary Rom on my OPO. It showed rom successfully installed but I cannot load into the OS. The screen goes off after 1+ logo. Seems like a soft brick. I restarted and entered my other Roms. After searching, came to know that Color Os cannot be used as secondary. Can anyone please through a light on this and tell will it be possible atleast in near future??
[ONE Android Development] eminence84:
Hi, I'm using MultiROM with CM11s as primary ROM. I managed to install the latest CM12 nighlty with the AK kernel (without it I got bootlocks). The only remaining problem was the proximity sensor, so I flashed the CM12 alpha modem. First I flashed it inside the secondary CM12 ROM, but the proximity sensor still didn't work. Then, after reading this thread, I flashed the modem "globally". Now the good thing is that the proximity sensor works on CM12, but on CM11s it doesn't. So I'm guessing the modem is not backward compatible? Is there anything I can do to make them both work? If not, how can I revert to the old modem? Because I'm sure there will be other bugs in the nightlies which will make me want my stock ROM back.

Thanks!
[ONE Android Development] magnamentis:
same here, you can download the old modem 44s from xda or from my dropbox, here is the link: https://dl.dropboxusercontent.com/u/46421818/XNPH44S-modem-flashable.zip

EDIT: and of course you have to flash the two modems back and forth each time you change from KK to LP and vice versa. i don't do that because i don't use the LP rom as

a daily driver and the OPO not as a phone really, but if it's your main or only device i recommend to change modem upon each rom change. further i doubt that it's possible

to flash a modem for only one of multiple roms, modems are device wide as far as i know
[ONE Android Development] Natakranta:
read my post here

and other here with link to CM radio
[ONE Android Development] tobitege:
One weird observation: I had flashed CM-12 as a secondary rom and although there was no error in TWRP the modem baseband did not change.

Only when I flashed it as primary rom the new baseband showed up (.3.xxx). Wondering if anyone else had this occur as that was a new one for me?
[ONE Android Development] xanthrax:
The secondary ROM doesn't touch /change your modem and boot partition, this is the way it works

Only the primary ROM has these "rights", this is why you need a kexec patched kernel on primary

Sent from my Darkside of 1+1
[ONE Android Development] davidjumani:
Hey guys, I have a few doubts so any help will be appreciated

1. Do I need to install a custom recovery before installing multirom or just only root my phone and download multirom from the play store and install everything via the app without modifying the stock recovery??

2. Can I install a lollipop rom while the stock rom I installed multirom on is just 4.4.4??

Thanks :)
[ONE Android Development] venky61:
Hi,

1. Yes, you need to install a custom recovery. The playstore app is mainly to install the pre-requisites.

2. Yes, you can install the lollipop rom with primary rom as 4.4.4 but the kernel need to be changed in case it does not support (this is easy).

Cheers. :)
[ONE Android Development] davidjumani:
So I have to root my phone, install a custom recovery like twrp and then install multirom which uses its own modified twrp.

Also what are the sizes of the /data and /system partitions that are created when you install a new rom??

Thanks :)
[ONE Android Development] venky61:
Yes. You need to root the phone. Without rooting the phone you cant install any Rom.

And about the sizes, am not sure. Never checked them. Should be the regular sizes they take in a normal installation. May be the OP can throw some light on this.
[ONE Android Development] KINGbabasula:
1. The app will install the recovery, so no need to install any before

2. Yes, you can
[ONE Android Development] Natakranta:
Good to see you :)

Did you have a chance to check USB OTG in last OPO MultiROM TWRP 2.8.3.0? It is not showing external storage it used to.

Is it something you could fix? Or is it up to TWRP?

Thanks for your continues support!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] kantjer:
TWRP 2.8.4.0 is released, haven't seen a change log but maybe it's fixed.
[ONE Android Development] davidjumani:
Sorry but I'm a little confused. Someone else said that I have to install a custom recovery before installing multirom. So should I flash the twrp recovery and then install multirom or just install it after rooting my phone on stock recovery??
[ONE Android Development] Natakranta:
Check out who is the OP in this thread ;)

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.