yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] ph1dft:
Hi,

I tested the TWRP zip, and all installs fine, but I cannot boot a secondary ROM (SultanXDA 6.0) because the option is not given, it still boots the primary ROM (SultanXDA 5.1.1 ROM) and also when I try to boot the secondary ROM via MultiROm Manager it boots the primary ROM.

When I swap the roms, the SultanXDA 6.0 boots up fine, but again I cannot boot the secondary ROM.

When I swap back, my Original 5.1.1 rom bootloops.
[ONE Android Development] ksigit:
Are you on f2fs? That's known issue if you have f2fs on data and cache partition.

Wait a minute, sultan's default kernel does not support Multirom I believe. If you're not on f2fs setup, with Sultan 5.1.1 ROM as primary, you can try flash AK/Tyr/Render CAF 5.1.1 kernel on primary. It should work.
[ONE Android Development] raman41:
Can u give the updated patch link
[ONE Android Development] Natakranta:
Where did you get MultiROM v32L?

MultiROM Manager app shows me only v32k.

I'm still using official MultiROM TWRP and v32k. I can flash Omni MM as secondary (SlimSaber LP primary with stock karnel kexec patched), but it doesn't boot. Stays on OnePlus logo.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] max_aideal:
Here you go: http://xdaforums.com/showthread.php?p=62939052

---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------

Im having the same problem. I've 32L and flashed latest TWRP. My primary is Sultanxda 6.0, secondary is CM12.1 nightly. Primary ROM boots fine, but secondary won't boot at all.
[ONE Android Development] Natakranta:
Thanks!

Does Sultanxda 6.0 karnel (your primary ROM) has kexec hardboot patch for MultiROM? If not, you will not boot any secondary ROM.

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] max_aideal:
Does Sultanxda 6.0 karnel (your primary ROM) has kexec hardboot patch for MultiROM? If not, you will not boot any secondary ROM.

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

I believe it has. This is what it shows in mutlirom manager while I'm on sultanxda 6.0 as primary.
[ONE Android Development] dragsterman:
I have stock COS12.1 with stock KEXEC PATCHED kernel as primary, and Sultan's CM13 (1124) as secondary, and the new patched TWRP (	TWRP_multirom_bacon_20151124.zip).

I'm not sure of 2 things:

1: Can I flash zips (for example: Xposed framework) for my secondary ROM?

2: If I flash Xposed to my secondary Sultan CM13 then I dirty flash a new CM13 build, will be the Xposed working or I have to flash Xposed every time when I dirty flash a new ROM build?
[ONE Android Development] Shadowghoster:
1. Yes

2. you must always flash xposed again when you update the rom.
[ONE Android Development] dragsterman:
Thanx for the help :)

One more thing: when I flash a new ROM build can I flash the Xposed right after that without reboot?
[ONE Android Development] lokesh.3440:
Can anybody tell me why do I always get installation error while flashing cm 13 as a secondary ROM ?

BTW I am using sultan cm 12.1 with ak kernel as primary ROM. One more thing I am using official multirom/recovery using multirom app from play store.
[ONE Android Development] nkk71:
Reading back a few pages wouldn't hurt, you'd come across these posts in particular:

http://xdaforums.com/showpost.php?p=63890359&postcount=2838

http://xdaforums.com/showpost.php?p=63891047&postcount=2840

http://xdaforums.com/showpost.php?p=63958541&postcount=2847

http://xdaforums.com/showpost.php?p=63972714&postcount=2854

this one having the modified recovery to "fix"/remove those hash checks
[ONE Android Development] lokesh.3440:
Sorry for being so lazy. Thanks for pointing me in right direction.
[ONE Android Development] nkk71:
no problem, enjoy flashing

(though you may wanna check the last few pages in any case, I dont even have this device, so there may be other things of interest, just saying :o)
[ONE Android Development] dragsterman:
Could anybody help me with this?

I'm just curious and woluld like to flash a new update as simple as possible.
[ONE Android Development] ph1dft:
Yes I am on f2fs because of the extra high performance.
[ONE Android Development] MMWolverine:
Just wipe cache & dalvik before flashing the ROM, then flash Xposed and reboot.
[ONE Android Development] ksigit:
Could not flash secondary with this version. Weird issue related to zip timestamps? 20151123 works though. Log attached.
[ONE Android Development] davidjumani:
I'm planning on switching to f2fs and I've searched the thread but got conflicting views on whether multirom(or the recovery) supports f2fs or not. Just wondering if it does and on all three or just the data and cache partitions.
[ONE Android Development] ksigit:
I would say "incomplete f2fs support", meaning you can format, read, write into f2fs, but you won't be able to boot secondary if you convert to f2fs. Only primary ROM is able to boot.
[ONE Android Development] davidjumani:
What about with the new recovery posted by amit??
[ONE Android Development] ksigit:
I haven't test it, feel free to test yourself.
[ONE Android Development] danieldmm:
Still issues flashing modem, it won't flash.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] huditama:
Hi,

I'm getting Error executing updater binary in zip '/tmp/mr_update.zip when trying to flash CM11s. Any solutions?

Sorry if this is a repeated question..
[ONE Android Development] Poesini:
Primary is SlimLP CAF and secondary is YoshiShaPow's Omni 6.0 also CAF with /data and /cache f2fs and it does not boot secondary
[ONE Android Development] davidjumani:
I read that with caf as primary, the bootanimation isn't shown. Is it still the case??
[ONE Android Development] Poesini:
Yep, no animation is shown so it straight boots to primary, had to swap ROMs
[ONE Android Development] :
Can confirm that the f2fs patch works.. tried system partition as f2fs, but just got bootloops. f2fs-mixed (data and cache as f2fs) is what I'm going to have to settle with for now. But as said above; you have to swap primary with secondary if you ever want to switch roms. Better than nothing I guess. I was able to get an android 6.0 caf rom with lightning kernel to work with everything f2fs using the latest clockworkmod advanced edition. (v6.59.4 I think?) You have to backup an ext4 rom under clockworkmod, flash twrp, plug it in to your pc and save the backup somewhere on you desktop. (to get access to mtp through twrp I had to enable adb sideload and then disable it for some reason.) Then flash clockworkmod and format everything as f2fs including system partition. Flash twrp again, connect it to your pc, drag the backup in to clockworkmod's backup folder, then flash clockworkmod and restore the backup. For some reason clockworkmod doesn't reformat anything back to ext4 when restoring an ext4 backup. Making everything f2fs. Select roms work with this. Darkoba's rom works great, but android 6.0 isn't a daily driver yet so I had to revert back to f2fs-mixed 5.1.1. I was also getting audio static with viper4android so it's a no go for me right now.
[ONE Android Development] Skandia:
Hi,

As quoted here i am using Unofficial CyanogenMod 12.1 with CAF 3.4.0 kernel from Sultanxda as secondary rom and i having some issues to access to some folders on my storage of my One Plus One.

My primary rom is Stock 44S (with weird issues with latest google play services updates and battery drain and crashes with and without wake up, etc.) so i am trying with the Sultanxda rom as secondary, to be promoted to primary when i have it well customized. But today i get and error, when i tried to restore some apps and confs with titanium backup that showed me that i can't open a lot of folders from storage (titanium backup folder for example)

I can browse some folders (DCIM, and few others) but i can not access to the majority of folders on my storage. I have root and any file explorer that i use can't open a lot of folders (default file explorer, total commander...). It says that i don't have permissions, but i am using the programs with root access. Curiosly the folders that i can open have the SAME permissions as the other that i can't ... i also tried to change/reapply the same permissions to the "blocked" folders.

If i try with any other rom, as secondary (miui V7, Radioactive marshmallow, etc.) i can access without problems to all folders.

I don't know if the problem could be from multirom, but i ask here as quoted in the official sultanxda rom thread.

Thanks in advance.
[ONE Android Development] Skandia:
Thanks to chrismalla here, i found that i can acces to all folders if i go to /data/media/0 instead to go with the default path (as posted in these posts).

But the seconday rom still uses other path where i can not access to a lot of folders. Is there any patch to OnePlus One Multirom as seen in this last post? (The zip url to solve the problema doesn't work).

Thanks in advance.
[ONE Android Development] Spawn_Ishan:
Rom boot error

While booting a rom through multirom i got an error provided in the log file. What should i do to solve the issue.
[ONE Android Development] maxed4901:
[MENTION=5093942]KINGbabasula[/MENTION] [MENTION=3418703]Tasssadar[/MENTION]. I am trying to flash WXL version of the MIUI rom but unfortunately it is not booting. I have tried inject boot also as per your guide. What could be the issue and how can i boot into the rom?

Attached is the log which was copied to /sdcard.

Primary rom is SOKP5.1 and secondary is COS12.1 3JL + MIUI by X_s. A friend recomended to try WXL version so i tried but didnt work out. Please advice
[ONE Android Development] CBpbxEcmecmBeH:
you're advised not to try; ColorOS based ROMs will not work with multirom any time soon ;) enjoy it as it is
[ONE Android Development] starc2k:
if you like to try ColorOS , need to install ColorOS has primary....don´t know if miui work ,but ColorOS yep.----
[ONE Android Development] acuicultor:
But any coloros kernel have kexec hard boot support so you can install in primary slot but cant use secondaries

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] lieuliau:
Can anyone tell me how to run Sultan rom in primary and other roms as secondary please? I can't find any CAF kernel that support multirom. Thank you very much!
[ONE Android Development] duke_mac_l:
The bootmenu is not working but you can use the multirom-app to boot any secondary rom you have installed.
[ONE Android Development] robbieast:
the multirom menu boots up, but some times it is unresponsive...

as in touching the screen does nothing.

any idea why this happen?
[ONE Android Development] maxed4901:
Any one? I am not trying to install ColorOS.. Namely nit even miui.. well the X_s version works.. so i cant understand the fail boot for WXL version. And some one here needs to respond to enquirers like this... or post that the project is abandoned or something. The Dev says to post log.. posting log but not response.
[ONE Android Development] TheQuarterMile:
After flashing this recovery and multiromzip I wanted to unintall it so I flashed the uninstall Multirom zip and flashed TWRP 2.8.6.0 but now when I'm trying to dirty flash my primary ROM zip(wipe system,data,dalvik and cache) I'm getting "error excuting update binary zip"
[ONE Android Development] ksigit:
If you played long enough with multirom, you will know that colorOS-based ROM won't work as secondary. So don't bother install any of them as secondary. Most of the wu-xianlin (WXL) ROMs (are based on ColorOS, so it's no surprise they won't boot as secondary. X_s, in the other hand, built his ROM based on CM, that's the reason it boots fine as secondary. Hope this helps.

Note: if you're insist on installing WXL's ROM on multirom, then you have to switch ROMs (primary <> secondary) to be able to boot, backup and restoring boot partition in the process.

---------- Post added at 19:55 ---------- Previous post was at 19:52 ----------

What ROM you are trying to install? What exact error did you encounter? Care to share the log?

---------- Post added at 19:57 ---------- Previous post was at 19:55 ----------

Install modified multirom v32l built by amit.bhagaria (search this thread). It supposed to fixed multirom boot menu display if primary is CAF-based ROM.
[ONE Android Development] maxed4901:
Bummer--- do you think the 32L version could work to flash colorOS base builds? I understand that it is made for CAF roms. The reaction i havent seen yet on any other rom other than like you said WXL MIUI and yes-TDA MIUI and also colorOS builds.. it ends up reboot showing crash log. I posted my log here.. any guidance links about this occurance? i was able to reproduce the error everytime.. :eek: Thank you for the reply
[ONE Android Development] ksigit:
No, I don't think v32l will work either. It's an issue on the colorOS side.
[ONE Android Development] iruiz2:
Hi guys, is it possible to have kitkat in primary (madhi) and marshmallow on secondary? Any special steps?
[ONE Android Development] silvagroup:
I haven't been able to get any MM ROM to install as a secondary ROM at all. They all fail with a update script error.
[ONE Android Development] ksigit:
Install modified TWRP dated 20151124 (search this thread).
[ONE Android Development] iruiz2:
I did, and got this error. Using multirom 32l. In Sultan's rom thread it says to install cm13 nightly before, but won't that mess with my KK primary?
[ONE Android Development] stab244:
You need to update your firmware. Yes it'll mess up the KK primary. I think there is some way to fix it but I'm not sure.
[ONE Android Development] Mike_1996:
Theoretically you could make use of the custom radio.img feature in the MultiROM TWRP but our phone uses a NON-HLOS.BIN modem and, though many threads suggest simple renaming, I've never actually got it working (ROM boots without signal and showing Unknown as baseband version).
[ONE Android Development] Natakranta:
Yes, it's as simple as renaming NON-HLOS.bin to radio.img. Then you can set it as radio for secondary ROM

The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[ONE Android Development] iruiz2:
So, the idea would be to flash the radio to the secondary MM rom? How could I do that, the creation of the secondary rom fails due to initial firmware checks...

(My primary is Madhi kitkat)
[ONE Android Development] ksigit:
I think the best strategy is to install MM or LP based ROM as primary. This way you can install any ROM, including KK based ROMs, as secondary.
[ONE Android Development] xeph20:
Is this true?

My opo broke and today I received my replacement opo and got my kitkat on nandroid

Is it best to install cm13 nightly? And put the nandroid as secondary and everything will be fine?
[ONE Android Development] Pablo.x:
Seems that lastest nightly with the new firmware and kernel patch it's not working as it should be.

But you can install yesterday's nightly on primary and backup on secundary with no problems.

Remind that primary rom's kernel has to have kexec patch

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] xeph20:
YA I tried anyway with the latest cm nightly and everything went perfect

Cm 13 installed.

Latest AK kernel installed

Multirom installed.

Booted fine

Was able to restore kitkat nandroid as primary and not a single problem.

Just a shame all the media is lost :/
[ONE Android Development] acuicultor:
[MENTION=5093942]KINGbabasula[/MENTION],hi first happy new year, with latest firmware boot menu isn't working anymore and some secondary roms refused to boot that's not a problem to me but I'm wondering if you are aware of that and if you want or need some logs in order to fix that, if this is the case I'll be glad to help you providing what you need. Thanks for your time and work.

Enviado desde mi A0001 mediante Tapatalk
[ONE Android Development] iruiz2:
Can you clarify this a little bit more for me, please?

After having cm13 and ak kernel (I thought he stopped at cm12) and multirom... what exactly did you do?

a) restore kk backup on top of that cm13

b) restore it in a secondary slot and swap them

c) put cm13 as secondary, and them restore kk on primary

Did you flash any radio or proximity fix?

I tried the b) option and had the old proximity sensor bug so it was impossible to make calls properly, for example... I ended up deleting everything and restoring only km on primary, but I would love to try some mm (while keeping kk) rom(s)...
[ONE Android Development] xeph20:
A I guess :P it was a unused phone and with a toolkit I unlocked the bootloader en instantly flashed cm 13 then downloaded multirom and everything I needed and then in TWRP I did the add rom feature from backup and then selected my old kitkat backup and everything went great

No swapping

No modem installed

No fixes

Although I did not call anyone with the phone yet so maybe it will give problems

What problems did it give you? Just not turning on the screen when you called or?
[ONE Android Development] iruiz2:
Ok, I guess you have KK then on the secondary, right? Make a phone call and tell us how it goes, please... In my case screen stays black even if you take it far from u our head, so there's no way to end the call.
[ONE Android Development] paarkhi:
+1
[ONE Android Development] crazydude10:
I have been trying to triboot Android 4.4 (cm nightly) as primary with boeffla kernel, sultan's 5.1 , 6.0.1 as secondaries.

Initially flashed the cm 13 firmware alone from the regular twrp menu. I was then able to install the 6.x rom as secondary.

But the new modem broke 4.4, 5.1 radios. Dirty flashed the entire 4.4 rom, multi-rom files and firmware, 5.1 rom.

Now 4.4 rom is working normally, but the proximity sensor is still broken in 5.1 rom in spite of flashing the proximity fix on secondary 5.1. The display goes blank when a phone call is made even when proximity sensor is not obstructed.

As for 6.x rom, I tried setting the radio image to the NOHS.bin from the Jan 2 nightly without any success in getting the radio to work.
[ONE Android Development] xeph20:
Yeah KK is secondary

I just called my voicemail and have no problems. the screen turns off when holding to ear and goes back on when taking away from ear.

The only problem i encountered is that double tap to wake doesn't work which i miss a bit but is not bad. also when i made a hotspot from my mobile network the signal often stopped

but i never had random reboots like ppl talk about or big problems.

i'm on the version of 30 december 2015 and i'm afraid to update because i might create problems :P
[ONE Android Development] iruiz2:
Did you call with your KK rom? I think you are mixing the behavior of both roms in your message...

I haven't found anybody yet that has managed to have properly working KK and MM roms in multirom.
[ONE Android Development] xeph20:
No I called with my marshmallow rom..

I'm sorry it works fairly well for me :(
[ONE Android Development] iruiz2:
Please, whenever you have time, try making a call from your KK rom and let me know what happens...
[ONE Android Development] xeph20:
Ah yes you are right. I just tried calling on the kitkat rom and same happens as you said. I'm sorry I though you meant calling with marshmallow.

Well I'm not having problems with it cus I will just use marshmallow most of the time.

I just used multirom to see how battery life would be on marshmallow and it's OK so far :)
[ONE Android Development] Champi12301:
Hi all. Before the Cm13 firmware update i had Slimkat KK as primary+RacyanOs(M) secondary,with Cm11 44s módem working all perfect.

But since the firm update all Roms doesnt boot,so i fixed reinstalling the RacyanOs ROM as primary with Radioctaive Kernel (w/ hardboot exec)

Working fine now (the only problem is black screen when i make a call) but now wont be able to boot any other ROM KK in secondary. There is any fix to this ? Thanks...

Tecleado desde mi 1+1.
[ONE Android Development] brisac:
maybe any new unofficial update for new firmware that has come? :P
[ONE Android Development] Champi12301:
Or some fix [emoji28]

Tecleado desde mi 1+1.
[ONE Android Development] xeph20:
2 part question.

Can I nandroid restore only boot and system partition on internal rom?

And would it downgrade the the nightly version I used on the backup or keep the current version?

Thanks
[ONE Android Development] Dr.Now:
[MENTION=6712354]kingbaba[/MENTION]lusa:

Will there be an update of MultiROM to the latest TWRP 2.8.7.0.5 materialised?
[ONE Android Development] Giansi:
Hi guys, sorry for asking but I tryed everything I know.

I'm on a OPO 64gb with Resurrection remix rom and last Boeffla kernel.

I lost my multirom boot flashing the kernel, I imagine. Can happen.

I cannot restore my multirom boot. Always internal rom boots normally.

I tryed to flash again multirom 32k zip and to inject current boot sector many times, using different twrp versions, unistalling and reinstalling through multirom manager or flashing unistaller in twrp, but the result always is nothing.

No more ideas in my brain. Perhaps someone here will be so kind to help me.

Thanks in advance anyway
[ONE Android Development] paarkhi:
Are you on Latest Resurrection Remix? if that's the case then it is using the latest firmware update and MultiROM is not working with the latest firmware update, so as long as [MENTION=5093942]KINGbabasula[/MENTION] doesn't update the MultiROM or you go back to the last firmware, there's no option of MultiROM to work. DON'T WORRY YOU ARE NOT ALONE, IT IS SAME WITH EVERYONE
[ONE Android Development] lieuliau:
I'm using MultiRom 32k and 32l, Primary ROM is Sultan 6.0.1, Kernel is Render R1 has kexec patch, but I can't boot into secondary rom, tried with MultiRom app also but always has error :(
[ONE Android Development] Giansi:
Yes that's my case. Thanks so much for updating me! I feel better now! So if I switch to another firmware based rom as internal rom, and last RR as secondary, it should work?
[ONE Android Development] Tomcar:
Maybe the fix on the Nexus 4 Thread is working. Did work for me with Nexus 4.

http://xdaforums.com/showpost.php?p=63802367&postcount=1391
[ONE Android Development] paarkhi:
Yes, for that you will need to downgrade your firmware and RR should be 17.12.2015 or before
[ONE Android Development] Champi12301:
I think this works only fox Nexus 4 phones, anyway,tried to flash it and didn't working.(error flashing with Twrp)

Tecleado desde mi 1+1.
[ONE Android Development] AYEHAN:
Conformed working Multirom menu on Cm13 6 Jan Nightly

i want a fawkin Mallow
[ONE Android Development] AYEHAN:
It was working with Ak Kernel OPO 311, just changed to Boeffla and Multirom menu gone

i want a fawkin Mallow
[ONE Android Development] Giansi:
Ok so I checked:

- resurrection kernel NO multirom

- boeffla kernel NO multirom

- AK kernel OK multirom but no DT2W

- radioactive kernel OK multirom
[ONE Android Development] Mike_1996:
AK kernel does have DT2W + gesture. Have been using it for more than half a year and no problems as such. People have also reported successful cases on CM13 nightlies but Radioactive is also awesome.
[ONE Android Development] paarkhi:
My 2¢ on Radioactive Kernel

Checked with Radioactive Kernel, although it doesn't show the menu while booting (the menu was showing till I had single ROM as primary but as soon as I flashed RR as secondary ROM, the menu stopped showing) but MultiROM is working, I Switch to ROMs via MultiROM Manager App on android.
[ONE Android Development] nadeem.patel:
Install the latest firmware.. RR v2.7
[ONE Android Development] lieuliau:
Anyone have solution to this problem? Thank you!
[ONE Android Development] paarkhi:
Just for trial/testing purposes change the kernel, if it works then it means that Render Kernel has updated it sources to latest CM and it's breaking the things.
[ONE Android Development] lieuliau:
Render kernel is the only one CAF kernel support kexec as far as I know
[ONE Android Development] paarkhi:
Sorry, didn't know that, probably updated CAF is breaking things,

Now only option for you may be is to flash/install some other ROM as primary and keep Sultan as Secondary.