yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] ¿GotJazz?:
I am running MultiROM on my OPO, and have a secondary ROM installed.

Question: If I am running vXXX of my secondary ROM, and a vYYY update to that ROM is released, can I upgrade my existing vXXX MultiROM installation, or do I need to start from scratch with a new vYYY installation?

If I can upgrade, do I just install the newer vYYY ROM with the "Flash ZIP" button after selecting the vXXX ROM?

Thanks,

¿GJ?
[ONE Android Development] OmegaBlaze:
Correct. Go to recovery, advanced, multirom, FLASH ZIP, choose the rom you want to update, and update.
[ONE Android Development] xanthrax:
Can someone confirm me if there is a 0 folder root /data /media /0 ?

Sent from my Darkside of 1+1
[ONE Android Development] fredzen14:
Yes it is.
[ONE Android Development] xanthrax:
Thanks because for some reasons I can't boot any L ROM from secondary

Sent from my Darkside of 1+1
[ONE Android Development] fredzen14:
Running great here with F2FS mod. Im still dont know why some people got problems with that issue. Cant help u bro.
[ONE Android Development] jcespi2005:
Can't boot CM12 ROMs from day 22 or later...

Sent from my OnePlus One ;)
[ONE Android Development] xanthrax:
Yes, exactly the same

I guess we need to format the sdcard...

Sent from my Darkside of 1+1
[ONE Android Development] jcespi2005:
Please, elaborate this ;) you mean de sdcard? The 56Gb full of things sdcard? OMG

Sent from my OnePlus One ;)
[ONE Android Development] xanthrax:
Sadly yes... I'll do it tomorrow, I'll let you know

Sent from my Darkside of 1+1
[ONE Android Development] dansou901:
You mean we need another file system? Or the partition got corrupted?
[ONE Android Development] xanthrax:
I think it is related to files system,

Can you post a recovery log after an unsuccessful boot of L as secondary that I can compare it to mine?

Re-flashing of the normal twrp and re-installing multirom didn't help either

Sent from my Darkside of 1+1
[ONE Android Development] stab244:
What kernel are you using on your primary? The kexec patch has to be updated to let L based ROMs boot on multirom. I know ak has the patch on his CM 12 kernel.

Sent from my bacon
[ONE Android Development] xanthrax:
Using ak as always... Maybe it's a good idea to try an earlier version, v 14 maybe

-=-=-

I think I've found the problem

I've flashed ak v10 and L Booted just fine as secondary

I'll speak to ak

Thanks for the tip [MENTION=2222926]stab244[/MENTION]

Allright, flashed v21 on top of v10 and all good now [emoji12]

Sent from my Darkside of 1+1
[ONE Android Development] jcespi2005:
Nice, but seems doesn't work with every >22 day version, installed temasek CM12 (http://xdaforums.com/oneplus-one/development/rom-cm11-temasek-build-t2870743) with or wothout AK v010 CM12 but no luck.

Sounds to me like something is wrong in my SD...
[ONE Android Development] xanthrax:
Look, delete the secondary L

Flash ak 10, boot primary, go to recovery and flash L second, boot L

If all good then flash whatever kernel as primary you want and then all L roms work fine

I'll try temashek later

Sent from my Darkside of 1+1
[ONE Android Development] jcespi2005:
Thanks fot the tip, but can't flash AK 10 CM12 on my CM11s primary ROM. Don't think you mean flash CM12 kernel on CM11s ROM, right?

I can flash later CM11s AK kernel on primary and give a try.
[ONE Android Development] xanthrax:
Oh sure, you need a cm 11s based kernel on cm 11s

For cm 11/AOSP from v 10 onwards all are working

Sent from my Darkside of 1+1
[ONE Android Development] lucap00:
I don't understand, it's safe to flash cm12 as secondary ROM or not?
[ONE Android Development] xanthrax:
Sure it is, if doesn't boot, that's it, nothing wrong happens

Sent from my Darkside of 1+1
[ONE Android Development] lucap00:
And about format sd, file system corrupted? I don't want to format my sdcard
[ONE Android Development] xanthrax:
there's nothing wrong with it, it is ok, you just flash a RoM which can work or not

you can delete it easier

you need a kexec patched kernel on primary

read the first post

sent from my Darkside of Nexus 7 LTE

---------- Post added at 06:20 PM ---------- Previous post was at 06:09 PM ----------

I can't see any temashek cm 12 there, I flashed the 11 as second and it works ok, with ak 21 in it

sent from my Darkside of Nexus 7 LTE
[ONE Android Development] jcespi2005:
No way, AK v75 CM11s on primary ROM, but still secondary L don't wanna boot :(

Something must be wrong on my SD though...

I'll make a clean install including SD.

Thanks

Sent from my OnePlus One ;)
[ONE Android Development] xanthrax:
From v10 ak has applied a commit for L roms to work so you may try a ROM with goes well with ak 10 as primary

Don't rush

Try tema 11

Sent from my Darkside of 1+1
[ONE Android Development] jcespi2005:
You can grab the CM12 builds from this link https://www.androidfilehost.com/?w=files&flid=21644

taken from the singnature ;)

Perhaps i didn't explain too much clear, i have no problem installing any CM11 as secondary, just CM12 builds after 22Nov. I tested this one from 21Nov and works assecondary, but after that, no one works...
[ONE Android Development] xanthrax:
Yes, what I am thinking of is that, to fix the boot for a L, a newer than 22/11 is to flash ak 10 on primary

At least this way worked for me

-=-=- [MENTION=281521]jcespi2005[/MENTION]

i flashed temashek cm12 as secondary , is working fine , thanks for the link btw

do what i said and it will be fine

Sent from my Darkside of 1+1
[ONE Android Development] Astagar:
I'm wondering why the Franco kernel in version 33 doesn't support kexec? That's what the multirom app says me.

On older version it never was a problem?
[ONE Android Development] Tzfardaya:
Search this thread for kexec... It's been answered before
[ONE Android Development] pippoaacc:
Just an information about the permissions given to zips when flashing a rom as secondary. I'm planning to flash coloros and subsequently swap it with my primary rom. I'm aware that I will not be able to boot my secondary roms cause coloros kernel doesn't have the kexec init. What I don't understand is: since the coloros zip modifies the partition structure of the phone, does this modification still occur when flashing as secondary, or all the partitioning features are inhibited by multirom when flashing a zip as secondary?
[ONE Android Development] MAX 94:
Followed your posts and in particular this mini-tutorial, but Lollipop still dosen't boot even with ak10 on primary. The Lollipop version i've tried is this http://www.reddit.com/r/oneplus/comments/2moqig/cm12_nonscheduled_builds_discussionupdate_thread/ (version r10 - Nov 25 2014), and others but with no luck. I don't know why
[ONE Android Development] xanthrax:
Ok, maybe some more...

Uninstall multiboot recovery from the application, this will erase all secondaries

Flash normal twrp

Reboot the recovery

Flash ak

Back into the system and reinstall multiboot

Boot into recovery and reboot recovery

Try a L...

I was stuck like you but now it's working, I've got 3 different L's, I'll try k900 as well

Sent from my Darkside of 1+1
[ONE Android Development] pippoaacc:
For example: coloros zip says it flashed a logo partition and a modem partition when installed as secondary, but actually my logo is still white and baseband the same as before: did it REALLY modify modem and logo partition, or those function are actually inhibited even if they show up in the log?
[ONE Android Development] Sick1:
Tried and confirming this is workin! And i thank you very much. Stilk dont know hiw its possible to have it working this way :D
[ONE Android Development] xanthrax:
If I well recall, this is what I've done...

I updated cm 12 of 19th Nov to 22nd on a secondary

It was fine, Booted but I wasn't happy with the dirty flash and I've performed a clean flash, as secondary as well but, didn't boot

After few tries I've decided to swap the non bootable cm 12 with my working primary, cm 11 CyanHacker

None of them were booting up even though the primary cm12 had a patched kernel, latest ak

I swapped back, cm11 primary, cm12 second and dirty flash primary because of a tone of FC

Since then, no L was working until I've done as above

Now is good, k900 Booted fine as secondary

Sent from my Darkside of 1+1
[ONE Android Development] xanthrax:
I'm afraid that you misunderstood something

MultiROM doesn't mess with partitions, it just creats a new folder in root /data/media /0 with a new os from where is booting up using the patched kernel

It doesn't flash the radio, the ROM is using the radio you've got in the primary ROM, sharing it

And if there is a new radio, there is one, it has the same name /numbers as the first radio for opo, there are small changes visible in the radio zip if you check the git

Boot animation doesn't go in a particular partition, is just part of the ROM you boot

The rom just can be erased at any time from multirom manager or manually using a file Explorer, won't affect any partition

Sent from my Darkside of 1+1
[ONE Android Development] pippoaacc:
Thanks, but I know that, in fact i'm talking about the logo partition which contains the bootloader logo, not the bootanimation. Anyway, my question is: so, when a ROM zip TRIES to flash a modem or a recovery, does multirom INHIBITE that? I'm asking because in the log it states that a new modem HAS BEEN FLASHED. Is this just a dummy message?
[ONE Android Development] xanthrax:
Recovery log?

Sent from my Darkside of 1+1
[ONE Android Development] pippoaacc:
Extracting /modem...done
[ONE Android Development] fredzen14:
Did you managed to flash color os?
[ONE Android Development] pippoaacc:
Not at the moment. It does not boot even as primary
[ONE Android Development] xanthrax:
Is it a flashable zip?

Sent from my Darkside of 1+1
[ONE Android Development] pippoaacc:
Yes
[ONE Android Development] xanthrax:
May I have a link?

Sent from my Darkside of 1+1
[ONE Android Development] beany>:
I'm not seeing these issues. My primary is Bliss with Bliss kernel (although I have swapped back and forth with other ROMs being primary).

I can get bpears, k900, robbiel etc all to run as secondary with either clean or dirty flashes for each. Sometimes however it will not boot first time. I can leave it 20+ minutes and it not complete booting but a forced reboot often brings it to life. There do sometimes seem to be issues if you try and flash anything other than ROM, GApps and SuperSU on first boot eg TBO or TiBa update zip. However, if you flash something like TBO Keep when there is a remnant of google Keep or Thyrus' dark material that is at the wrong level then it can fail to boot or if it boots and errors it seems incredibly difficult to correct.

So my method is:

Dirty: back up; dirty flash ROM + SuperSU; boot; back up; flash apps.

Clean: back up existing; Add ROM; flash GApps (minimal) +SuperSU; boot; back up; flash apps.

(OK sometimes I don't do the back up, but usually regret it at some point lol)
[ONE Android Development] MAX 94:
Thank you thank you thank you very much! I followed your steps and i worked very well mate! Thank for your help, i really appreciate it and a thank also to [MENTION=5942667]beany>[/MENTION] for his help for future flash :D
[ONE Android Development] xanthrax:
and AK as from v20 is working on cm 11s as well

sent from my Darkside of Nexus 7 LTE
[ONE Android Development] Natakranta:
Hi guys, just to report. I installed MultiROM yesterday on my OPO. I used to use it few months ago on my Nexus 5 (currently my wife's) so I'm familiar with the routine.

[MENTION=3306843]kantjer[/MENTION] made some nice repacks for MultiROM TWRP, his post with links to downloads.

There are cool MultiROM themes for MultiROM TWRP, downloads here.

I'm using SlimSaber-bacon-4.4.4-20141126 as primary, karnel is patched for MultiROM.

And Robbie's Slim-bacon-5.0.alpha.0.4-UNOFFICIAL-20141126-0138 as secondary with PA micro gapps and SuperSU 2.35.

All good :D

Thanks [MENTION=5093942]KINGbabasula[/MENTION]!

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] House.m.d:
I´m new on Opo. I flashed Multirom yesterday. CM12 Temasek prev.4 as Primary with AK 024, CM11 Temasek 162.1 as second and finally Stock CM11 11.0-XNPH38R with AK 077 as third.

My Question: Can I update Stock to XNPH44R only with wiping dalvik and cache?
[ONE Android Development] xanthrax:
Yes, you can, from multirom list roms, flash zip, after flashing wipe cache

Sent from my Darkside of 1+1
[ONE Android Development] dave5777:
Thanks, finally got it working with liquid smooth 4.0 and cm12 ak kernel on primary, on my secondary I have cm11 nightly with ak.
[ONE Android Development] kantjer:
I will be adding more colour versions today to match [MENTION=2719389]z31s1g[/MENTION] TWRP theme colours.
[ONE Android Development] iscraigh:
I seem to only be able to flash newer android L roms as primary. Up until the 27th I was able to have Mahdi as primary and a couple of android L roms as secondary's. The only way I was able to get 27th/28th L roms to flash was by swapping them as primary roms then flash ( haven't tried swapping back and seeing if they still boot). I would get an error about not being able to execute the update script. Any one else finding this? BTW running ak20 first then 24 cm12 kernel on internal rom.

Thanks

Craig
[ONE Android Development] xanthrax:
Yes, it is a known issue... Unfortunately

Sent from my Darkside of 1+1
[ONE Android Development] scott62185:
Yeah, same here. Slim Saber works though.
[ONE Android Development] Andypandiiee:
Hey, im using CM11 as my secondary rom, but when I try to boot to it, it says "Ketec not found". So i read the forums and they said to flash Franco Kernel or the AK Kernel, and so i did. After flashing them both, they dont work. If anyone could help me, that would be so awesome! Thanks :)
[ONE Android Development] fredzen14:
Flash AK kernel on Primary Rom
[ONE Android Development] bud77:
Reflash your rom kernel (or the whole rom, it's easier) then flash AK kernel

Edit : On you primary rom I meant
[ONE Android Development] galza:
i cant seem to mount my 2 otg devices in the latest twrp for multirom.when i go to mount it does not see any of my devices only internal storage.what is the problem?

when i try to go to multirom options it sees something but i cant see the content of the otg only internal storage and i cant change storage.

thanks
[ONE Android Development] ravvio:
kexec-hardboot patch! Franco

I want to use Multirom and keep cm11s with Franco kernel as my primary rom. But multirom says my franco kernel is missing kexec-hardboot patch. I have a paid version of FK r33 latest version and i want to get a kexec-hardboot patched franco kernel to do this. Can i please get a link to download if one is available ?
[ONE Android Development] jcespi2005:
Flash R32

Sent from my OnePlus One ;)
[ONE Android Development] laulau42400:
R31 and multirom OK, R32 no good.

OnePlus one et Tapaltak
[ONE Android Development] jcespi2005:
Ops, sorry for the mistake, R31 then ;)

Sent from my OnePlus One ;)
[ONE Android Development] jcespi2005:
OP, Could be possibly to implement the backup part for the recovery to work as the unofficial TWRP to allow backup efs and persist partitions. I miss this two options while using multirom...

Thanks ☺

Sent from my OnePlus One ;)
[ONE Android Development] choosymoron:
I'm on Stock 44S OnePlus One with Root and default kernel and stuff. Thought of giving this a try today so just went to the playstore and downloaded Multirom manager. It downloaded 3 files and installed it and then rebooted to the TWRP. Took around 15min for installing the Kernel as I was on the original Kernel. I did panic as my phone just switched off but after restarting the phone I could see the MultiRom screen and everything is fine.

Could not believe it was so simple to install MultiRom on my OnePlus One, Thanks to XDA on YouTube for posting this video on how to install MultiRom.
[ONE Android Development] Enea307:
Does Color Os work as second rom? Thnx
[ONE Android Development] fredzen14:
no.
[ONE Android Development] chikimonke:
Does anyone have any insight as to why I get the error in the attatched screen shot? I've tried searching and haven't found anything yet. I flashed a previous version of the ROM and it worked fine, but now this new version won't flash. I'm trying to help [MENTION=4911350]RobbieL811[/MENTION] test his alpha builds of SlimLP and I'm using SlimKat 8.16 with AK kernel v30 as my primary ROM. Any insight would be much appreciated.
[ONE Android Development] matius44:
Have you tried to mount system before flashing? Had similar error when I tried flashing SuperSU in a setup similar as yours.

In the main menu of the MultiROM custom TWRP go to mount and tick system, then try flashing again. That fixed it for me.
[ONE Android Development] scott62185:
So please correct me if I'm wrong but, right now, the only rom that can be flashed directly to a secondary spot is Slim Saber? Thanks
[ONE Android Development] xanthrax:
I'm not sure if only slim saber but what I know is that for the past few days CM 12 can't be flashed directly as secondary due to the updater script modifications

The only solution is to revert the structure of the script or to use the swap roms function through multirom by flashing cm 12 as primary

Sent from my Darkside of 1+1
[ONE Android Development] Kingzak34:
The primary kernel is the only one that must be kexec patched.

Secondary can be too but it's not necessary.

I tell this for official multirom. Maybe this one must have both kernel patched.

Tapatalké depuis mon OnePlus One MIUI !
[ONE Android Development] KINGbabasula:
Finally the boot menu is working :victory:

Download:

http://goo.im/devs/KINGbabasula/OneplusOne/multirom-20140817-v27-UNOFFICIAL-bacon.zip
[ONE Android Development] eugenioxx:
Wow you are awesome! Many thanks !

Testing right now!:D

EDIT:

I've flashed the zip but I was not able to see the menù also when I change the main rom or kernel (with the patch of course) and select "Inject MultiRom after installation" or use the button Advance->MultiRom->Inject curr. boot sector the phone stuck in oneplus logo. Unchecking it return to normal use with primary rom installed.

I'm on stock cm11s plus Ak 30 stable (with patch) and as secondary rom I have used Slimkat 7.2.1 with Ak 30 (aosp version)stable
[ONE Android Development] KINGbabasula:
Cm11s is always outdated, you should use the nightlies. Anyway I'll check tomorrow for this problem.
[ONE Android Development] eugenioxx:
Yea many thanks anyway

I will try with other aosp/cm nighty later XD

One more question:

We have to flash always a kernel (in primary and secondary ROM) to make it works? Or only in primary and the other rom don't need to have the patch?

Many thanks!
[ONE Android Development] KINGbabasula:
I have to fix a thing in kexec to make it working without kexec patched kernel in secondary rom. For now you can multiboot only with share kernel option
[ONE Android Development] gulp79:
The option to have two separate kernel is working in the new update? In this case would be possibile to install cm11 & coloros or cm11S right?
[ONE Android Development] dansou901:
Read the post above yours, the answer is there...
[ONE Android Development] eugenioxx:
Yes I have read the OP but the developer have release an update and I don't know if the OP referst to the previous version or the new one of today. So I've asked.

Now I know exactly with the new version released today how it works.
[ONE Android Development] bud77:
I'm having a little bug with v27

I added a secondary rom (PAC), and shared kernel with internal

The 2nd rom booted fine at this time

I rebooted and installed a zip (titanium) using twrp >advanced > multirom > list roms> select 2nd rom > flash zip

But now I can't boot on 2nd rom, everytime I select it in the boot menu, screen stays black for 1-2 minutes, and reboots by itself
[ONE Android Development] KINGbabasula:
I guess that zip messed it up. Don't you have another way to restore apps? Try nandroid manager
[ONE Android Development] bud77:
Internal ROM still boots fine

And 2nd ROM had nothing installed

The ZIP is created by titanium backup and only contains itself as a ZIP (easier than an apk)

Sent from my One A0001
[ONE Android Development] KINGbabasula:
Then reflash 2nd Rom and install titanium backup as an apk
[ONE Android Development] skydayzer:
Let me get this clear.. I have to use the kernel you provided.. [MENTION=5093942]KINGbabasula[/MENTION]
[ONE Android Development] KINGbabasula:
Otherwise what happened? I'm using ak kernel and it's working perfectly
[ONE Android Development] skydayzer:
Grazie.. just wanted to know because am on FrancoKernel.. and am not sure if he has kexec merged...
[ONE Android Development] KINGbabasula:
You are on cm11s then, I suggest nightlies because cm11s has outdated things. At least until I fix last things in kernel
[ONE Android Development] skydayzer:
No am on Mahdi:cowboy::cowboy:
[ONE Android Development] KINGbabasula:
Sorry, I thought franco kernel was only for cm11s. Anyway franco kernel still hasn't kexec
[ONE Android Development] skydayzer:
Then it's either AK or your Kernel..
[ONE Android Development] chikimonke:
Unfortunately that's not it for this. [MENTION=4911350]RobbieL811[/MENTION] thinks it's the updater script and that seems to be confirmed by [MENTION=3946657]xanthrax[/MENTION]
[ONE Android Development] scott62185:
I know I read about this swapping method in some thread but can't remember which. Can you link me to that? Thanks!
[ONE Android Development] xanthrax:
There are 2 ways

Either backup your primary and most used ROM and then restore it as secondary

Then just flash cm 12 as primary, you'll have your favorite ROM as secondary but to access it you need a patched kernel on the primary, like ak

Other way is to go in multirom recovery and swap the primary ROM with secondary from the dedicated option

Then flash a cm 12 as primary

The second one sometimes will give errors for the second ROM, happened to me reason why I used the backup option

Sent from my Darkside of 1+1
[ONE Android Development] fredzen14:
Take this and replace.

https://mega.co.nz/#!ZAoGiDLI!zOLzimSadl_OvgPVxocAQ6cUDNOVQdYKleth67rVeFA
[ONE Android Development] stuckmoto:
A SLIM updater script will work on any ROM? Guess I'll try :p
[ONE Android Development] fredzen14:
No and dont.
[ONE Android Development] stuckmoto:
Ok. Only good for Robbie's ROM I take it?
[ONE Android Development] fredzen14:
This is for current SlimLP by RobbiesL811.
[ONE Android Development] scott62185:
So are you saying (with the first option) that by having that CM 12 rom as a primary (with AK kernel) will allow me to flash any newer CM 12 roms to secondary going forward? Or do I need to do that each time I want to flash a new rom? I don't actually use my primary rom (it's an old CM 11 based rom) so it doesn't really matter which one I have where. Sorry for my ignorance :)
[ONE Android Development] xanthrax:
no, I wasn't clear enough sorry...

this will allow you to have a fully functional and stable RoM on secondary and on primary CM12

but also you can swap the primary CM12 afterwards with your second

sent from my Darkside of Nexus 7 LTE
[ONE Android Development] iscraigh:
The newest Temasek cm12 is multirom compatible as a secondary.

Craig
[ONE Android Development] fmotta:
Could you please point out the Temasek link? I tried one but it doesn't install as secondary. Thanks
[ONE Android Development] Crazy-Silver:
Hi guys. I want to mount Color OS on primary rom. Where can I find Color OS zip? Which kernel with MultiROM support should I flash?