yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Sick1:
This is the method to edit it.

http://xdaforums.com/showpost.php?p=57211572&postcount=495

Do not copy that to your current script but compare it and soon you see the difference. Its those "endif" an "if" things thst makes it to fail.
[ONE Android Development] beren:
hope this can help:

http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
[ONE Android Development] EdenGottlieb:
I tried to install both Candy5 and Temasek CM 12 and both failed with error "E: error executing updater binary in zip '/tmp/mr_update.zip'"

Is it a problem with my device or with the ROMs? maybe they're just not compatible?

Thanks!

EDIT: OK, so I read a couple of posts back and it seems I'm absolutley not the only one with this problem. Sorry for bothering. You can ignore this post.
[ONE Android Development] freestylejunki32:
Anyone?
[ONE Android Development] newellj79:
Yes. Searching now.
[ONE Android Development] keen36:
you need to edit the updater script for newer lollipop builds to install them as secondary.

temasek has already done this for you, however. you just need to download the modified updater script zip from the same place you downloaded the rom and then replace the one in the rom zip file with it.
[ONE Android Development] EdenGottlieb:
I downloaded the modified updater script but I'm not sure how to put it in the zip so it will work.. Sorry for being such a noob

EDIT: OK, so I changed the updater script and it flashed. I flash franco kernel to main ROM to have kexec boot support, I tried to boot secondary and it didn't work! It said I didn't have kexec support. What should I do?
[ONE Android Development] Sick1:
Sorry for kind of and re-post.

Because there are so many with the issue, and so many still doesnt know what to do about secondary lollipop...

Heres everything i know about it

First:

As an attachement there are 2 updater-scripts, taken from here:

http://xdaforums.com/oneplus-one/development/rom-cm11-temasek-build-t2870743

Other one is original from rom.zip file.

Other one is edited for it to install as secondary.

Compare those 2 files and you see what is the difference between them. Do not copy those to you rom, because it may not work.

Take your updater-script from "RomYouLikeToUse.zip/META-INF\com\google\android" edit it, and put it back there!

Thank [MENTION=3814731]katinatez[/MENTION] and [MENTION=2332422]temasek[/MENTION] ! Im just a messenger, people on there made it happen.

Second thing:

SElinux needs to be permissive at kernel level, for secondary rom to boot, i believe.

So as far as i know, this needs to be reverted:

https://github.com/CyanogenMod/andr...mmit/d3a3a61245d0a12d76be47c61326a7ffbdfa3a5b

I dont know how to build only kernel with that SElinux as permissive, cause ive only built roms with kernel as an "inline build" or something like that.

I like getting private mail, about people asking, "how to boot secondary lollipop" , but i hope this clears the deal?

Please correct me if this is not working. For me it worked like this.

I built cm12 with [MENTION=3685904]ak[/MENTION] kernel for testing purposes about 15 times before i found the commit above :D .

Peace!
[ONE Android Development] katinatez:
To boot lollipop as a secondary rom dev's have to add these four commits into their kernel

https://github.com/KINGbabasula/android_kernel_oneplus_msm8974/compare/CyanogenMod:cm-11.0...cm-11.0

the updater script removes a if statement, and allows to flash correctly,

I don't know about the selinux to boot to second rom, but I reverted to permissive to fix my koush superuser in my rom

hope this clears up alot
[ONE Android Development] Sick1:
Im 99% sure that SElinux needs to be permissive, did alot of tests and booted different roms with boot.img extracted from your .zip :)
[ONE Android Development] EdenGottlieb:
OK, so I changed the updater script and it flashed! Thanks for that. I flashed franco kernel to main ROM to have kexec boot support, I tried to boot secondary and it didn't work! It said I didn't have kexec support. What should I do?
[ONE Android Development] zando2712:
Franco no longer has kexec support.
[ONE Android Development] Crazy-Silver:
Guys there is a way to mod Color OS kernel to support multirom?
[ONE Android Development] xanthrax:
Try out the new multirom recovery, update it through the app manager, L is flashing and booting fine now as secondary

Sent from my Darkside of 1+1
[ONE Android Development] Sick1:
No time to test, but no more tweaking/editing?!?
[ONE Android Development] stab244:
Couldn't get Euphoria to boot on new recovery. And still had issues flashing Temasek without changing install script. Though based on the change log it should work.
[ONE Android Development] Natakranta:
The same for me. SlimLP test build from today flashes as secondary but boot loops. I tried with and without modified upater script.

I/m flashing now previus MultiROM recovery to see if the ROM boots after flashing it in the previus one.

I'll report soon.

Edit:

It boot loops on previous MultiROM recovery as well. Can be on ROM side. Back to testing. Tomorrow. Almost 1am here.
[ONE Android Development] dbaler:
Its booting for me. Have AK39 on top of k900s latest. For main.

Latest SlimLP from Fusion is booting for me. I have it as secondary. I also dirty flashed.
[ONE Android Development] gqukyo:
Candy5 and BlissPop work fine for me as secondary roms using AK's 50 kernel. LiquidSmooth doesn't even install.

Oops, spoke too soon, BlissPop installs ok but I'm stuck at the boot animation... it's been more than 10m...
[ONE Android Development] tilaksidduram:
To Boot any lollipop ROM as Secondary ROM on your Oneplus One using Multirom you need to have Selinux set to Permissive. If it is set to Enforcing then the secondary rom wont boot, will be stuck in the Boot logo.

I have created a new "Boot.img" kernel file from the Stock CM sources (CM-12.0 Branch) with Selinux set to Premisssive. After i flashed this new kernel i am now able to boot into my PA ROM that i have installed as secondary.

Download the new Boot.img file from below

Steps to replace the Boot.img

1. copy the new Boot.img file to you phone sdcard.

2. Boot into Multirom recovery

3. click on Advanced -> Multirom - List Rom -> select the Secondary Rom and click on remove Boot.img

4. again click on the secondary rom and select Add Boot.img. select the Boot.img file that you copied earlier.

5. reboot the phone once the boot.img file is copied into the installed secondary rom.
[ONE Android Development] xanthrax:
With the above boot.img bliss is booting fine, only chose the ROM, remove boot.img and added the modified one though Vanir didn't need that

Sent from my Darkside of 1+1
[ONE Android Development] choosymoron:
A quick Q.. Can I use Stock Kernel of CM11S 44S for MultiRom setup? I had initially setup multi rom but that changed my kernel to AK, now I want to use the stock kernel and multirom. I can't find stock kernel with the patch anywhere. Can anyone please guide me with links. Thanks.
[ONE Android Development] keen36:
i think franco's kernel is not multirom compatible anymore... i am not sure about this, though. maybe try ak?
[ONE Android Development] choosymoron:
What you could do is have the Internal OS with modified AK kernel and have other OS installed as ROM's via MultiROM Manager thus having easy franco kernel :)

Even I wanted modified franco on internal but I gave up on the process. Now I'm trying to get original Kernel of CM11s 44s with the patch for MultiRom.
[ONE Android Development] Sick1:
Confirming that secondary rom (Temasek Cm12) doesnt flash without editing the updater-script even after updating to new Multirom TWRP
[ONE Android Development] KINGbabasula:
I'm working on a little patch that sets selinux permissive automatically while booting secondary ROMs
[ONE Android Development] KINGbabasula:
Updated MultiROM to v30a, now SElinux is set to permissive on secondary ROMs boot to let them boot
[ONE Android Development] Schrotty35:
Which themes can i use with the twrp from here? Can i use this twrp without multirom and is efs backup now aviable?
[ONE Android Development] xanthrax:
Confirmed, it works!

Thanks mate!

Sent from my Darkside of 1+1
[ONE Android Development] Rycon33:
Got notification for v30b already, so fast update. I wonder what's the issue on 30a.
[ONE Android Development] `SBR`:
V30b works good... Aicp booted in secondary room
[ONE Android Development] Schrotty35:
I have now install only twrp from here and cm11 not boot. Also efs backup is not include. Return to working twrp.
[ONE Android Development] KINGbabasula:
Not really an issue, you can see the changelog in the app, it's just a check to see if selinux is already permissive instead of setting it always
[ONE Android Development] xanthrax:
It is not related to recovery or multirom, bootloop it is kernel related

And the efs you do it once, you don't need to backup it every time

I've successfully Booted a cm 11 as secondary with ak kernel

Sent from my Darkside of 1+1
[ONE Android Development] Schrotty35:
Ok but the persist partition is related i think?
[ONE Android Development] xanthrax:
This is opo related, for some reasons it happens, have you flashed it?

Sent from my Darkside of 1+1
[ONE Android Development] Schrotty35:
I use cm11 and cm12.
[ONE Android Development] gqukyo:
I searched but doesn't seem as if someone has already asked this... my auto boot option keeps getting unselected/unchecked from time to time whenever I check it options. Think I'm OCD or something... no idea why I always check options whenever I'm in recovery... lol... but anyways, every time I check it auto boot is unchecked. Minor thing but just thought I'd bring it up and ask about.
[ONE Android Development] stab244:
Still unable to boot any L based ROMs as secondary even with 30b. Tried Euphoria, SlimSaberLP, Daleski daily builds, and lollinaro. All with stock kernels and Euphoria also with ak 50. My internal CM11 nightly ROM is using Sensei 18 but also flashed ak50 to see if it made a difference and it didn't. MultiRom Log

What happens is that it gets to the usual 1+ boot logo (and then the ak logo if I'm on ak kernel), but doesn't reach boot animation. The phone just reboots again and goes back to internal boot then secondary ROM boot and repeats if I don't choose a different ROM (I use auto boot). All my KK based secondary works (slumber and CM11S). Don't think the log is that helpful since its not crashing on boot. It's crashing after but before the boot animation.

Sent from my bacon
[ONE Android Development] stuckmoto:
+1

I have pretty much the same configuration as the previous post. I'm wondering if having KK(CM11) as primary is holding it back.
[ONE Android Development] fredzen14:
+100
[ONE Android Development] tobitege:
Have you guys checked that your installed kernel does have Kexec Hardboot support at all?

Running crDroid (CM12) as primary, SlimSaber (CM12) and Mahdi (KK) as secondaries without issues.
[ONE Android Development] stab244:
Ak kernel (and thus Sensei) has kexec. Multirom app says kernel has support. So it's not kernel it seems.
[ONE Android Development] fredzen14:
Come on....

Did you update your recovery and Multirom v30b to the latest one through the app?
[ONE Android Development] laulau42400:
hi

blizzpop and resurrection remix starts in second rom.:good:
[ONE Android Development] tobitege:
Started with MultiRom v30 on Friday and flashed v30b earlier today through the app, yes.
[ONE Android Development] fredzen14:
How about the latest 2.8.2.0 Multirom Recovery ? Did you update that also?

And have you try to install any Lollipop Roms AFTER the update ?

Because the roms I installed before the update still working, only the one after the update couldn't even though there is no error when installing.
[ONE Android Development] tobitege:
For recovery I have to admit that I may have started with an earlier version, but now I do have "TWRP_multirom_bacon_20141206-00.img" on the phone and that's the only one I got on HD drive (can't remember if/when I had older version removed locally).

So you may be quite right that I might not have installed additional ROM afterwards, but if it helps, I'll try it out for you.

Edit: correction: I do have TWRP_multirom_bacon_20141213-00.img on phone's sdcard and had flashed that already.
[ONE Android Development] Schrotty35:
With 30 and 30a work and with 30b not work???
[ONE Android Development] tobitege:
[MENTION=5736293]fredzen14[/MENTION]: I just installed another Lollipop ROM as secondary without problem (Resurection).
[ONE Android Development] stab244:
Couldn't get resurrection remix to work either. Same issue as before. Latest multirom and twrp. I guess it is because my primary is KK based.
[ONE Android Development] Schrotty35:
Have install also now latest multirom and twrp version and DarkoBass also not work with secondary. I can not install.
[ONE Android Development] fredzen14:
You might be so lucky pal.
[ONE Android Development] tobitege:
I haven't tried yet the "Swap ROM" feature... would that be an option for you - in case you'd already have a Lollipop ROM - to swap your KK with the L one?

If not, sounds like you'd have to make a backup and install your L rom fresh as primary and restore your KK rom as secondary. Shouldn't take more than an hour to set up, I guess. ;)

If there's anything I can help with, let me know.
[ONE Android Development] fredzen14:
You mention it, I did all of them.

But to no avail.

Can you try install Temasek?
[ONE Android Development] tobitege:
Yikes. :(

Sure, just downloaded 2.5.2. Right now I could add it as secondary rom if that's enough for you, but I guess it will work fine with my current setup just as with Resurrection an hour earlier. Will get back to you on this in a bit... ;)

---

Edit: getting error "executing updater binary in zip /tmp/mr_update.zip" with temasek 2.5.2 :(
[ONE Android Development] fredzen14:
Replace the updater-script first provided in the same folder of the Temasek CM12 Roms at androidfilehost.
[ONE Android Development] tobitege:
Ok, Temasek flashed fine as secondary, booted up nicely and works (edit: after having replaced updater script in zip from AFH).
[ONE Android Development] newellj79:
Slim saber fine as secondary.
[ONE Android Development] xanthrax:
Oh my... What a mess!

Sent from my Darkside of 1+1
[ONE Android Development] Schrotty35:
Temasek also not work with secondary, only work with new update script.
[ONE Android Development] nirmik379kale:
Does Franco kernel work with multirom?

I tried with cm12 as secondary rom but it says the kernel needs the support thing... The AK kernel in latest build of multirom turns the screen yellowish... So i want to use franco, but cant get the secondary rom to boot with it...

Please help! ?
[ONE Android Development] tobitege:
No (not anymore), iirc.

Eeek! :eek: Yellowish??? Certainly not an AK issue...
[ONE Android Development] Rycon33:
As far as I know, Franco latest version doesn't have the Multi-ROM patch(kexec-hardboot). His previous ones has I think.

Regarding [MENTION=3685904]ak[/MENTION] kernel being yellowish, you must use Universal Kernel Manager and Synapse app to set Gamma to 1 then it will be like stock color.
[ONE Android Development] Schrotty35:
Set gamma to +1 and you see no more yellow.
[ONE Android Development] nirmik379kale:
Oh god...

Okay.. Thanx...

One more thing, if AK does support multirom, which version should i install?

I see link to cm12 ak kernel in op of ak...

M on cm11s stock ( only rom)

Could you guide me to the correct download of ak for me?

Thankyou!
[ONE Android Development] tobitege:
Just use the download link in AK's thread which will point you to his site where current version is 0.50.

However, I ditched the stock/CM11 rom and replaced it with a L rom before starting with MultiRom. Other users may have info on CM11 for that.
[ONE Android Development] nirmik379kale:
The synapse app says no uci support detected... For ak kernel.. As well as for franco :(

---------- Post added at 11:57 PM ---------- Previous post was at 11:56 PM ----------

Okay that booted but still the yellow tint.. Trying the other ways others have mentioned.. Thanks :)

---------- Post added 15th December 2014 at 12:31 AM ---------- Previous post was 14th December 2014 at 11:57 PM ----------

Synapse app says no uci support :(

Not able to change gamma values?

Also, franco v33 also not supporting multirom...

Please help!
[ONE Android Development] Natakranta:
Last SlimLP flashes fine as secondary and boots. No need to modify updater script any more.

30b + TWRP Dec.13

Primary: last SlimSaber 4.4.4

Thanks!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] stab244:
What do you have for your primary ROM?
[ONE Android Development] dems86:
Latest Candy5 flashed and booted fine as a secondary for me too, just thought I'd toss that out there also.
[ONE Android Development] Rycon33:
Nice, latest update confirmed working on secondary ROM without altering the updater-script.

:good::)
[ONE Android Development] j.a:
CrDroid 5.0.1 working great as secondary. Thanks!
[ONE Android Development] Schrotty35:
Temasek? Not here. Clean install only work with update script.
[ONE Android Development] Rycon33:
Nope, other ROM. But I'm guessing for every ROM, it should work already.

Are you on latest v30b of Multi-ROM? And twrp dated 13-Dec?
[ONE Android Development] stab244:
For all of you who have secondary L ROMs working, what is your primary ROM? I know one of you have a L based ROM for primary. Dunno about the rest.
[ONE Android Development] gqukyo:
I've used both L and KK roms and both worked fine. LiquidSmooth would work from a restore backed up prior to me going back to multirom but would not flash any more as secondary so I'm using that as primary and pushed my stock cm11s rom to secondary from primary. Pretty sure it's the kernel that really matters and not the rom although I may be wrong since there's talk about some selinux permissive thing...
[ONE Android Development] Natakranta:
30b + TWRP Dec.13

Primary: last SlimSaber 4.4.4

Secondary:

SlimSaber LP Dec.13

SlimLP Dec.13 and my build Dec.14

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] Schrotty35:
Yes use latest too.
[ONE Android Development] rajibb:
Can you please let me know how to navigate to this folder??
[ONE Android Development] Silverquark:
This is not necessary anymore, because now the Multirom App works on the oneplus. Just download it from Google Play
[ONE Android Development] nirmik379kale:
Cannot Boot Lollipop Roms!! :confused:

I have installed the multiBoot recovery, custom AK kernel ( provided by mr ) + UKM special edition kernel for AK kernel and Stock CM11s rom.

I tried installing SlimLP , Unofficial stock cm12 as secondary roms but they dont boot! goes in a boot loop and returns to multiboot menu.

PA based on 4.4.4 works, but no lollipop roms are booting! Helop Please!! :(
[ONE Android Development] tobitege:
Several people are having issues with the primary rom being a KK rom when trying to install an L rom as secondary.

Try installing a L rom as primary and restore your KK one as secondary.
[ONE Android Development] Rycon33:
Not sure if it has something to do with the ROM being block-based(at least the unofficial stock CM12 is).

Other builds aren't following the new block-based and sticks with the old type ROM zip format because of some limitations that block-based currently presents.
[ONE Android Development] nirmik379kale:
I did get the stock cm12 to boot only once last night! No success ever since :(

only once i could boot... I dont know how that happened!
[ONE Android Development] DooshPastesh:
"DELETE ME"
[ONE Android Development] stab244:
So I did a bit of experimenting to hopefully find out what's going on. I'm currently using multirom 30b and the latest multirom TWRP. Kernel on primary is Sensei 18 with CM 11 nighties.

I remembered that there was an older build of K900 that worked so I went back and r4 of his builds worked with this setup. Then I went to his latest r15 build (from here) and that didn't boot (reboot after 1+ logo like with all other L ROMs). So I went back and tried every build between r4 and r15 to see when it broke. Fortunately I didn't have to go very far and it broke at r7. I also tried r8 just in case but that was broken too. So I looked at the change log and couldn't find anything that stuck out to me that would break multirom booting. Unfortunately I didn't have much more time to test since I have finals this week. Perhaps looking through the CM github for changes around that time to see what might've broken it. That build was from 11/20 I believe. Hope this is helpful.
[ONE Android Development] iscraigh:
Is this not just the same problem as most cm12 roms with the update file? Euphoria should work, Temasek's will work if you replace the update file in the rom with the modified one he supplies. Other roms have modified update files posted in there forums. The other option is to install cm12 as primary then use the swap function to move it to secondary.

Craig
[ONE Android Development] fredzen14:
Im not sure what is wrong with this, but I couldn't stand it no more. So what I did is, SUPER DUPER Clean Flash. Which mean, I wipe everything, yes, everything and start all over again which resulting a good return until now . I know it's crazy, but deep down in my heart, I feel happy to see my phone as a cute little newborn baby again. :silly:
[ONE Android Development] stab244:
If it was an update file issue it would flash at all. This is a bit different. The update script between all the K900 builds is the same anyways.

I could do that I guess. But not time to set things back up. Maybe just uninstalling and reinstalling multirom will be enough.

Sent from my bacon
[ONE Android Development] fredzen14:
Done that my friend, otherwise i wont wipe everything.
[ONE Android Development] stab244:
Darn. But it worked though?

Sent from my bacon
[ONE Android Development] rajibb:
Here is my setup that is working fine. I have stock as internal.
[ONE Android Development] marcowind80:
Do you have a modify script for each one
[ONE Android Development] rajibb:
Yes I just edited out the if condition in the updator scripts

Sent from my A0001
[ONE Android Development] philippas:
One question : I get errors while trying to install coloros as secondary rom. Any ideas?

Sent from my One+ One
[ONE Android Development] xanthrax:
it just doesn't work, that's it, there's nothing to do

sent from my Darkside of Nexus 7 LTE
[ONE Android Development] savahu:
I'm looking forward to having MIUI v6 with Multirom
[ONE Android Development] skydayzer:
Boot menu is working... But in recovery->Advanced the rest does not show..-> MultiROM -> Add ROM

Anything am doing wrong
[ONE Android Development] bud77:
You didn't flash the provided TWRP (find it in OP)
[ONE Android Development] skydayzer:
I did 3times and still the same
[ONE Android Development] bud77:
You must flash 3 things to get it working :

Modified TWRP

Multirom zip

Modified kernel (AK)

TWRP must be flashed via fastboot mode
[ONE Android Development] skydayzer:
Just finished with AK now.. let me check:fingers-crossed::fingers-crossed:

:Edit: Still the same
[ONE Android Development] bud77:
You are doing something wrong then (and I'm pretty sure you didn't flash the good TWRP using fastboot)

---------- Post added at 06:15 PM ---------- Previous post was at 06:12 PM ----------

@KINGbabasula : I'm pretty sure there is something wrong when you flash any zip on secondary roms

I just tried to flash minimal gapps, and I'm having the same problem as with titanium zip

But this time, I had several things installed, and I couldn't make a backup, since kernel must be shared with secondary roms

Also, another small issue I found, the bootanimations are missing like 5 seconds

The screen is totally black while bootanimation starts, but is not displayed
[ONE Android Development] skydayzer:
I did.. the one in the second post...
[ONE Android Development] bud77:
Reflash and post screenshot of flash result