yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] KINGbabasula:
Oh I see, when you flash a zip the rom starts using non shared kernel, so to workaround this issue until I fix kexec you should reboot recovery > advanced > multirom > list roms > choose rom > remove boot.img.

For bootanimation not showing, I have that issue since I flashed ak 30, with ak 20 it's ok, so not my fault
[ONE Android Development] skydayzer:
This is it
[ONE Android Development] xperiatomaja:
I get this error when flashing multiroom, as I fix it?
[ONE Android Development] bud77:
I don't see "fastboot devices" in the commands you typed

If you see a serial number, then it's fine, and issue is somewhere else :(

[MENTION=5093942]KINGbabasula[/MENTION] : Ohhh so before flashing a zip, I must remove boot.img, and restore it afterwards ?

(Anyway, I swapped ROMs, and 2nd rom (now 1st) is running fine, so the flash is working fine
[ONE Android Development] Tzfardaya:
My guess is use a kernel without ram disk compressed with lz4...
[ONE Android Development] KINGbabasula:
No, I meant, you flash the zip, reboot recovery, remove boot.img option
[ONE Android Development] bud77:
[MENTION=1418453]xperiatomaja[/MENTION] You are not using the modified TWRP, are you ?
[ONE Android Development] xperiatomaja:
Yes

EDIT: I've already managed to install multiroom, was because I was using the kernel furnace
[ONE Android Development] bud77:
"Yes" would mean you are not using the TWRP in the OP ... (and the look of your TWRP is definetly not the provided one)

Then you have to flash that TWRP in order

If you are using the proper TWRP, then what kernel are you using ?

Only AK and the kernel in OP works
[ONE Android Development] hamzahrmalik:
THANK YOU

SO SO SO SO MUCH

For the boot menu :)

Now I can boot aosp in seconds! (Rather than go the long way round)
[ONE Android Development] skydayzer:
Very strange am the only one not getting the Advance options....:confused::confused::mad::mad:
[ONE Android Development] davidwilson83:
I don't know what the heck I'm doing wrong but I can't for the life of me get this mod to work. I did have it on my previous device which was an S4 I9505 and it worked perfectly. Now nothing that I do will work.

I have downloaded the MultiROM app from Play Store and installed both MultiROM and modified TWRP. I am running Dirty Unicorns v8.2 as my Primary ROM and no matter what I try to install as second ROM, I either can't get it to boot or I can't boot back into primary ROM or both. I have tried with a couple of different 5.0 ROMs but nothing seems to want to work.

What am I doing wrong? Please advise.

Sent from Nexus 7 running Yukkipoop
[ONE Android Development] tobitege:
Have you already tried it with an "ak" kernel flashing on top of your secondary rom?
[ONE Android Development] Rycon33:
^^First thing, what's your phone's kernel on the primary? And what does it say on the Multi-ROM app? Kernel: has kexec-hardboot patch?
[ONE Android Development] davidwilson83:
No I haven't tried ak kernel because it is for CM or AOSP ROMs, but Dirty Unicorns is based on Omni.

The stock kernel that came with the ROM does not say that it is kexec-hardboot patched. I tried to use the app to install the patch but it keeps messing up the base ROM and I have to restore backup to get it to boot. Does anyone know of a kernel that supports Omni which is kexec-hardboot patched?

Dirty Unicorns OnePlus One
[ONE Android Development] Rycon33:
That's the first requirement if you want to have a working secondary ROM.

If you can't find any kernel that has kexec-hardboot patch for your primary ROM, then you're out of luck.
[ONE Android Development] dev-DaT:
*DELETE* found my problem already
[ONE Android Development] blak24:
Ok guys I've read the latest few pages of the thread, but I wasn't able to understand why most of the Lollipop ROMs don't boot as secondary ones. I'm using latest MultiROM with latest TWRP with the patched CM11 kernel installed through the MultiROM app. My primary ROM is CM11s, don't know if it matters.
[ONE Android Development] beany>:
Or just make DU secondary and ensure the primary has kexec. You can always change the boot order. AK and Boeffla both make great primary kernels if your ROMs kernel is not kexec.

---------- Post added at 10:52 PM ---------- Previous post was at 10:48 PM ----------

Some now do flash as secondary. Those that don't need their updater-script changing or flash as primary and swap or move to secondary as desired.
[ONE Android Development] bud77:
Sensei Kernel is supposed to work with Omni, and it's based off AK

So this should work on your setup :)
[ONE Android Development] davidwilson83:
That is a great idea. The dev for DU is trying to merge the 4 commits from the 2nd post of this thread into this kernel so I'll see if he can and then I'll flash that. Failing that, I will probably use your suggestion. Thanks a lot. :good:

I tried R77 Sensei kernel (which is the only one that didn't say CM11 or CM12) but I got into a bootloop after flashing. I asked in the thread but no one answered me so oh well. And the only ak kernels I could find were all CM so they wouldn't have worked. Thanks for trying though :)

Dirty Unicorns OnePlus One
[ONE Android Development] bud77:
CM12 version is supposed to work with all (CM11+12, omni (&DU) )

But yeah, the best thing to do would be to use a CM11/12 based rom on primary and DU on secondary
[ONE Android Development] blak24:
Sorry but I think I didn't understand. What should I do? Flash the Lollipop ROM as primary and then swap ROMs? (so the Cyano44S comes again as primary and the L rom as secondary)
[ONE Android Development] beany>:
If you want LP as secondary and it won't flash, yes you can move the existing primary to secondary, then wipe and flash LP to primary and if you want then swap the LP primary with what was your existing ROM.
[ONE Android Development] blak24:
Ok, now it's clear. And if I want LP as primary I can easily flash it to primary ROM after moving KK (for example CM11S) to secondary?
[ONE Android Development] tobitege:
Yes, afaik. Also, you can add secondaries anytime from nandroids, not only clean installs.
[ONE Android Development] blak24:
Ok thank you everybody. Just one more question: If I use a LP ROM as primary should I install first a compatible CM12 kernel from the MultiROM app? (or any other CM12 compatible kernel from TWRP) Will it work with KK ROMs? Because I can't found anymore the "sharing kernel" option while installing secondary ROMs from TWRP. I've just tried installing LP as primary after moving KK to secondary, then swapping ROMs, but I got a non-bootable LP rom and a not-working Cyano11S (I had to reflash it since it broke the radio part, both wifi and SIM service).
[ONE Android Development] tobitege:
You might need to use TWRP -> Multiboot to inject the boot sector again, but maybe somebody else can definitely answer that.
[ONE Android Development] beany>:
In primary install ROM, gapps, supersu if needed and a kernel such as boeffla or AK. Those kernels are compatible. You can use whatever appropriate kernel you like for your secondaries, as they aren't shared and don't need kexec patch.
[ONE Android Development] blak24:
This configuration is referred to LP as primary and any other secondary ROM? (both KK and LP)

EDIT: and obviously CM12 version of the Boeffla and AK
[ONE Android Development] tobitege:
Whichever you installed first is primary, also main TWRP buttons for install/backup etc. exclusively work on that rom. All ops for secondary roms go through the Multirom menu.
[ONE Android Development] blak24:
Yes I know this, I was asking for that specific configuration of LP/KK ROMs since I don't want to mess up everything just like I did yesterday :D
[ONE Android Development] cd69:
Should not be an issue. I had kk as primary and 2 lp roms as secondary. Now I have lp as primary and one kk and another lp as secondary.

Oneplus Nexus 5
[ONE Android Development] beany>:
Agreed - they work in any combination of lp/kk. You just have to make sure the primary has kexec patched kernel and lp roms in secondary that wouldn't flash in secondary won't update in secondary (unless the dev changes the updater-script) - so you would swap with primary, update and swap back.
[ONE Android Development] blak24:
I don't know what I'm doing wrong.. Just flashed Boeffla kernel for CM11s which is my primary ROM, then flashed as secondary the ResurrectionRemix LP 5.0.1, but it doesn't boot. It stays for a while with the 1+ logo and then reboots again.
[ONE Android Development] fredzen14:
Uninstall the multirom and install it again.
[ONE Android Development] nutij3:
If i don't use patched kernel, in which problem i can occur? For now the primary ROM with stock cyano work fine without patched kernel, but i have a secondary ROM top and before to try to boot it i want to ask in thos thread. Thank you for the answer and sorry for my bad english

Inviato dal mio A0001
[ONE Android Development] sathish804:
Hi All,

Can anyone please tell me how to restore my Nandroid backup as secondary ROM on MultiROM?

Thanks and Regards,

Sathish.
[ONE Android Development] tobitege:
First, you need a MultiRom-enabled TWRP. In there go to Advanced, MultiRom and Add Rom. To work on an existing rom go there to List Roms and pick your secondary rom, from there you can call all the ops TWRP offers on normal roms, too.

Download themed TWRPs for MultiRom from [MENTION=3306843]kantjer[/MENTION] (dated Dec 15, 2014) here:

https://www.androidfilehost.com/?w=files&flid=19381

https://s.basketbuild.com/devs/kantjer/bacon/TWRP repack/TWRP MultiRom
[ONE Android Development] sathish804:
You mean I can add the Rom from my Nandroid by Just selecting the Nandroid folder from the Add ROM option in Recovery?
[ONE Android Development] tobitege:
Yes. It allows you to choose directly there to add a ROM from either installing from ZIP or an existing backup.
[ONE Android Development] xanthrax:
Without a parched kernel you can't boot into a secondary ROM, that's it

Sent from my Darkside of 1+1
[ONE Android Development] Rycon33:
The OP clearly states all the information needed already. And yet we get this questions over and again, LoL.
[ONE Android Development] Tzfardaya:
That's because they can't be bothered to do their own RESEARCH (read op, last few pages of thread, use the sites search feature, use google site search feature).. They expect us to answer their questions no matter how many times it's been asked/answered already....
[ONE Android Development] NoSpamDan:
Is it just me, or does Basketbuild not show time stamps? Kinda sucks
[ONE Android Development] tobitege:
They are all from Dec. 15, I think.
[ONE Android Development] kantjer:
There all up to date, MultiRom app shows the recovery source date.
[ONE Android Development] beany>:
And driving good devs away :( Its a shame there isn't a down-vote; the only other tool is reporting to mods. /ot
[ONE Android Development] vikas44493:
help please

i m not able to boot my secondary rom i have blisspop 1.3 with ak .077 cm11 kernel as primary

when i select secondary rom to boot it boot again into rom selecting menu i tried 2 roms-darkobass and temasek latest version for secondary rom to check and none of them is working please someone help in this problem
[ONE Android Development] tobitege:
[MENTION=5036687]vikas44493[/MENTION]: in recovery MultiRom menu you have to inject the current boot sector again. This gets overwritten (I think) when a new kernel gets installed separately.

Also, are you using a KK kernel with a Lollipop rom? That doesn't work... download AK 0.65 fresh from his site and flash that one (afterwards might again need to inject boot sector).
[ONE Android Development] vikas44493:
that .065 is not latest right? and what is that unified mean in .065 kernel? is that for both cm11 and cm12?

or should i flash any other latest kernel?
[ONE Android Development] beany>:
Interesting. I've never needed to inject the boot sector; I'll keep an eye out next time I flash a kernel.
[ONE Android Development] tobitege:
It might well be user error from me, of course. But I had this morning totally derped my setup by wiping /data as I thought I had everything on external SD card - thinking of my LG G3 - and big facepalm after that. :silly: So in the process of getting my 4 secondaries back, I had rebooted/restored/flashed kernels for multiple roms and eventually the MultiRom boot menu did not show up and after injecting the boot sector that was fixed.

So, if that happens, the injection resolves the boot menu issue. *life lesson* :D
[ONE Android Development] vikas44493:
hey thanx man

i was little confuse about kernel version so it finally worked after reinstalling multirom and then flashing .065 kernel and again inject boot sector and then voila !
[ONE Android Development] Andypandiiee:
Long story short, I tried to backup a secondary ROM (CM11), then I wiped System, Cache, Dalvik Cache and then flashed CM12, then rebooted to be approached by this picture. Does anyone know what I can do to resolve this? Cheers.

-edit-

swapped Secondary ROM (CM11) and Primary ROM (CM12) and now it is working. I think it wasn't working was due to not having a kedex kernel on CM12.
[ONE Android Development] BlakeSm:
My secondary ROM is not booting anymore. It is stock CM11s with stock kernel. My primary ROM is Euphoria with AK v68. I've tried searching and injecting the curr. boot sector to no success. Is there a solution? Using MultiRom 30b. Thanks :)
[ONE Android Development] srikanth_s:
I am guessing U must have flashed some ROM/Mod zip ove that secondary ROM.
[ONE Android Development] tobitege:
Reflash the latest version of that CM11s rom in your MultiRom menu and see if that repairs it.
[ONE Android Development] BlakeSm:
:good:
[ONE Android Development] venky61:
HI,

Does changing kernel effect the multi rom or the secondary rom??

and what exactly does "Inject curr. boot sector" do? When should I do that.

I recently flashed AK kernel and it was showing the inject boot sector after flashing. I did not click it as I was not aware of it. But the secondary Rom was running normally.

Thanks in advance.
[ONE Android Development] tobitege:
The option to inject on both the Install (primary) or Flash (MultiRom) screen should be checked/on for normal usage, it then avoids any manual injection.

If you'd be using F2FS, then it may become necessary to explicitly flash a kernel with F2FS-support directly after the rom (personally using Tyr kernel by [MENTION=4804871]DerRomtester[/MENTION]). If the rom does not support this scenario, phone will only show the 1+1 logo and stay there because in the background it was not able to mount partitions.

HTH. :)
[ONE Android Development] Poser:
Has a multiROM enabled 2.8.3.x twrp image been compiled?

edit: I stopped sucking at life...and found my own answer. A true christmas miracle.
[ONE Android Development] solar666:
Don't catch your point here. Can you explain better?
[ONE Android Development] bidi1985:
anyone here able to boot Coloros rom with Cm12？
[ONE Android Development] gerciolisz:
dont think so:p if you find out how to do it you will be saviour of mankind:D
[ONE Android Development] tobitege:
Be careful with ColorOS, there have been some reports that it caused permanent issues after regular install and required a full format of everything when going to other rom. Just saying (use search in forum, don't have it at hand).
[ONE Android Development] sathish804:
ROM SWAP Issue

I have CM11S as my Primary ROM and Bliss POP as Seconday ROM.

I swapped the Bliss Pop ROM to Primary and CM11S as Secondary, it was successful and I was able to boot both the ROMS.

Later I Swapped the ROMS to make CM11S as my Primary and Bliss POP as seconday but this time when I selected the CM11S it was not booting and device was powered off instead of booting and no issues with the BlissPOP. I eveb tried the Inj.Cur.boot sector option from recovery but no luck.

Please can anyone tell me what I was doing wrong here?
[ONE Android Development] tobitege:
Keep as primary a(ny) Lollipop rom with MultiRom-compatible kernel (supporting kexec_hardboot); KitKat roms as primary seem to be an issue with MultiRom.
[ONE Android Development] sathish804:
I don't see the problems with KK rom as Primary unless I swap it to secondary and re-swap it to Primary.
[ONE Android Development] tobitege:
Ok, then why swap at all? ;) Just set the default boot in MultiRom to either fixed rom or 3 seconds, just saying.
[ONE Android Development] sathish804:
LOL!! I switched to LP as my Primary ROM but later I decided to switch back to CM11S for a while as Primary rom then I found the issue with CM11S which was not booting.
[ONE Android Development] kennonma:
does anyone know how to add the colorOS for sec rom?

i tried to change to update-script file, but not work.

its worked on me for cm11 for pri rom and cm12 for sec rom,
[ONE Android Development] tobitege:
[MENTION=5286554]sathish804[/MENTION]: have you tried to just dirty flash your CM11S again while primary (afterwards inject boot sector, too)?
[ONE Android Development] sathish804:
No I didn't tried it..
[ONE Android Development] magnamentis:
i've seen close to nothing which supports that statement. i'm on cm11 primary and bliss secondary which logically is the way most people go when slowly and carefully getting a feel for LP coming from KK and i encounter not the slightest problems. works perfectly well in that config.

---------- Post added at 05:26 PM ---------- Previous post was at 05:22 PM ----------

why swap, are you trolling or just not thinking before posting ? someone who comes from KK to LP will first have LP secondary and when he feels the the time has come will probably switch and eventually abandon KK the and perhaps try other LP roms out on secondery or higher posititon.

so this guy asked a very valid question and got only this in return? better say nothing than BS, while your most recent reply finally made sense. just seen it now.

there are many reason to swap sooner or later, last but not least the backup and restore function is easier on internal than on multirom, while the idea of setting secondary as fixed or on a short fuse is IMO a good interim solution for transition

unfortunately i'm not ready to be of much help either because my LP config is not ready as a DD, still too many bugs and things i don't like the way they look so i did not swap and therefore cannot help. it could be a kernel issue BTW because if you inject it will inject current which after the swap might be the wrong one but as i said, not there yet, just trying to give a hint to possible direction.
[ONE Android Development] tobitege:
[MENTION=5372360]magnamentis[/MENTION]: calm down, the "wink" smiley is clearly there and was meant kiddingly and if the issue wasn't solvable right away, just stay with the config that works, that's what I thought at least would transpire.

Do I look like I'm intending to troll around with my replies to help in several threads? Jeez.
[ONE Android Development] Tzfardaya:
Yes. :P

Oh wait... That's me...
[ONE Android Development] Poser:
Instead of asking for an answer...I took the time to thoroughly research and find it for myself..."teach a man to fish..." :good:
[ONE Android Development] kennonma:
i tried to add rom for sec rom, and the installation the completed,

but go for reboot is blank screen only... @@~

helps....

v.2.0.40

http://xdaforums.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853/page18#post57829297
[ONE Android Development] Neuer_User:
Sorry, if this is a stupid question, but where do I find the "share kernel" option?

I searched through every option, but seem to be too stupid to find it...

Thanks.
[ONE Android Development] kreumadragon:
i think this Option is removed in this version but if you remove the Boot.img in your ZIP it works like share kernel;)

Kreumadragon
[ONE Android Development] Kartik pat:
Can anyone tell me how can i backup my stock kernel?

Thanks :)
[ONE Android Development] kreumadragon:
If you don't have it as secondary ROM you can backup it via the normal TWRP.

Or simply click Backup and only choose boot(this is the full kernel).

They re saved in /sdcard/TWRP/BACKUPS/(there is only one folder but don't know name atm )

There are your backups;)

Kreumadragon
[ONE Android Development] sathish804:
Try the Rashr app which will help you to back up your Kernel and Recovery.
[ONE Android Development] gqukyo:
Anyone have any issues w/ the 12/29 BlissPop LP build as a secondary rom? I can't get it to boot as a secondary rom on both dirty and clean flashes. The previous build on 12/27 worked fine. Dev stated there was a lot of new commits that may have broken the multirom compatibility...
[ONE Android Development] NikoZBK:
I'm able to boot the 12/29 build of blisspop as a secondary. It takes a little longer than usual though.
[ONE Android Development] gqukyo:
I actually fell asleep last night after an hr or so, it was still bootlooping... lol so it didn't work for me. What kernel are you using?
[ONE Android Development] NikoZBK:
I can't remember if I immediately flashed boeffla kernel after flashing or if I booted up with the stock kernel.. so perhaps you can try both methods. I added the 12/29 build as a new secondary rom instead of dirty/clean flashing it over the same rom slot.
[ONE Android Development] gqukyo:
Yeah I added a new rom slot as well and it still didnt work, tried the Ak .70 kernel but no go either. Going to try as a primary rom now.
[ONE Android Development] beany>:
Blisspop 29/12 with Boeflla fine as secondary and moved to primary and still OK.
[ONE Android Development] gqukyo:
Set to primary rom and it works but random reboots with ak .70... I'll try boeflla
[ONE Android Development] sathish804:
For me also it bootlooped.. Dirty flashing the 1.4 over 1.5 has fixed the issue on Secondary ROM.
[ONE Android Development] Funk Wizard:
I am on Blisspop 29/12 build with AK(without Multirom), going to try MultiRom now, have a few questions:

1. Can i keep a 4.4.4 Rom and a 5.0.2 Rom together as primary and secondary?

I miss xposed and the CM theme engine so can i keep 11s 44s stock/Mahdi with xposed & AK as one rom @ Blisspop/Temasek as the other.

Thanks
[ONE Android Development] sathish804:
The latest build of BlissPOP rom i.e 1.5 - 29/12 was not working as Secondary ROM on MultiROM, to get it worked you need to dirty flash the 1.4 version of BlissPOP once you have flashed the 1.5 build.

You can ise CM11s 44S as Primary ROM and BlissPOP as secondary ROM.

For Temasek you need to check their thread to see the MultiROM support.
[ONE Android Development] Funk Wizard:
Thanks for a prompt response.

What if i use Blisspop 29/12 as primary and CM11s 44s as secondary will that be ok.

Just asking as i am on 29/12 + AK 070 right now and if i cant set it as primary i have to go to stock 44s image first and then again try 1.5/1.4 as secondary so it would be a long process.
[ONE Android Development] sathish804:
I have not tried BP 29/12 as my Primary ROM on MultiROM..But you can give it a try (after nandroid), If it is not booted you need to dirty flash the BP 1.4 build. Once it is booted you can add CM11S as secondary ROM.

I also faced the issue with CM11S when I swapped it from Secondary to Primary, which will not boot the CM11S as Primary if you swap it from Secondary.
[ONE Android Development] Natakranta:
Any ROM with AK72 should work as primary.

Easiest way would be to make CM11S 44S nandroid backup (maybe you have one already), flash Blisspop with AK72. Install MultiROM Manager from Play. Let it install MultiROM. Go to recovery - MultiROM menu and install secondary 44S from your nandroid, or clean flash it if you don't have nandroid.

Currently I have SlimKat 9 as primary and 2 secondary SlimLP ROMs.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] Funk Wizard:
So what i have decided is to install the multirom from play and flash 44s from here as secondary:

http://xdaforums.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551

once it works fine ill move that to the primary and keep blisspop or other L roms as secondary to keep dirty flashing them.

Hope this works, Thanks again for your advise.