[MOD][UNOFFICIAL] MultiROM v33 for onyx

[martinusbe]

Here is log from recovery. Please have a look at your leisure time https://gist.github.com/ukanth/480dcca12b96c14c3c92a9a5582a9d49

what happened?
anyway, all those loop1, loop2,.. shouldn't mount

 

[taaeem]

I tried installing Sailfish OS as secondary ROM. Installation was finished without any problems but when trying to boot the OS I get this error:
http://hastebin.com/xisexogipi
I disabled kexec hardboot and even flashed blu_spark since i know that blu_spark doesn't support kexec.

 

[matwaking]

I tried installing Sailfish OS as secondary ROM. Installation was finished without any problems but when trying to boot the OS I get this error:
http://hastebin.com/xisexogipi
I disabled kexec hardboot and even flashed blu_spark since i know that blu_spark doesn't support kexec.

Yep and neither OOS boots up as secondry os, have you tried making sfos as primary?

 

[ksigit]

I doubt sultan's kernel has kexec patch/hardboot. I will try with eng.stk kernel and report it back here. Thanks again for your work ! Is there any way to pull out log from multirom twrp ?

I'm in the same boat, with sultan's ROM as primary, no boot menu has shown. Did you manage to try eng.stk kernel? Does it worked? Maybe we could try switching ROMs as well (primary<>secondary).

Sent from my ONE E1001 using Tapatalk

 

[taaeem]

I'm in the same boat, with sultan's ROM as primary, no boot menu has shown. Did you manage to try eng.stk kernel? Does it worked? Maybe we could try switching ROMs as well (primary<>secondary).

Sent from my ONE E1001 using Tapatalk

Maybe try to inject boot sector again

 

[chwiejak]

Guys I used "remove boot.img" on second rom settings. I was sure that it will remove boot logo but now after booting it goes to recovery not for imsge. Now I see add boot logo but i do not know which I should indicate there. Please help me. It is cm13

Sent from my ONE E1001 using XDA-Developers mobile app

I am ok now

 

[ksigit]

Maybe try to inject boot sector again

Re-inject boot sector didn't work.
So, I tried the followings:
1. Swapped primary (sultan) with secondary (pa), at least boot menu shown up this time (with no timeout showing), but cannot boot to main (pa>>it reboots to recovery after showing oneplus logo) nor secondary (sultan>>it bootlooped after showing oneplus logo)
2. Installed TypsyOS as primary (erasing pa), boot menu shows up (correctly with timeout this time). It can boot to primary, boot to secondary still the same symptoms.
3. Installed XOSP as secondary, it can't boot into system, goes back to recovery after showing oneplus logo.
4. Installed DU as secondary, it boots fine

So, seems like some ROMs won't work as primary or secondary, Sultan's ROM for instance. I guess this is due to Sultan's specific kernel.

I must say this is major breakthrough and very promising. Very well done devs!
I will continue testing ROMs combination on primary/secondary, and report back.

 

[ukanth]

I'm in the same boat, with sultan's ROM as primary, no boot menu has shown. Did you manage to try eng.stk kernel? Does it worked? Maybe we could try switching ROMs as well (primary<>secondary).

Sent from my ONE E1001 using Tapatalk

You are right. It worked with eng.stk's kernel on Sultan's ROM. Good job on comparing primary/secondary rom testing !

 

[taaeem]

@martinusbe Does this mean that Sailfish can only be booted on kexec-based systems?
So it won't work with the no-kexec workaround? If so I would really appreaciate if kexec could be fixed. I don't know much about how MultiRom works otherwise I would do it myself.

EDIT: There is a defconfig: CONFIG_PROC_DEVICETREE=y
I suppose that while the Multirom loader is shown the recovery kernel is used? If so maybe it would help if that config would be set, its part of your kexec hardboot patch which you probably not applied or reverted due it not working. So it would be awesome if you could build a recovery with that conf set, i can test that then if you want

 

[andip71]

Thank you for the wonderful work Sir !
I would request @Lord Boeffla and @eng.stk to revert the kexec patch from their kernels.
The only method working as of now is via enabling no-kexec workaround from Multirom settings.

Just released my CM13 and OOS kernels for OnePlus-X without kexec hardboot patch.

I anyways never use it myself, it was not fully working + I never liked it.

So, enjoy.

Andi

 

[mijorus]

New TWRP 3.0 Updated!

Multirom v33 is coming

Ma zitto

 

[chwiejak]

Hello,

It is possible to install cm14 as second rom on opx?

 

[gouthamgoumi]

Hello,

It is possible to install cm14 as second rom on opx?

Yes.. Installed it on SD card working fine

Sent from my ONE E1003 using Tapatalk

 

[chwiejak]

I tried to install on internal memory but there is some problem.

 

[sheldorteconquor]

new community oos rom support?

 

[umpalumpa1799]

I tried to install on internal memory but there is some problem.View attachment 3879244

Same error here

Sent from my ONE E1003 using XDA-Developers mobile app

 

[sheldorteconquor]

Nope, no support for new bootloader anyone have a fork of this and the bluespark recovery?

Or is it my device?

Also I think error 7 is from the device name not being correct between the zip and the phone, I don't have this problem installing the zip though, only the recovery was broken. (although I did get error 7 from the uninstaller)

 

[umpalumpa1799]

Yes.. Installed it on SD card working fine

Sent from my ONE E1003 using Tapatalk

what's your primary rom and which baseband are you using?

 

[chwiejak]

Just for info
I have multirom twrp 3.0.2 and cm13 as base rom.
I am not able to install cm14 (dev stage)

 

[gouthamgoumi]

what's your primary rom and which baseband are you using?

I'll on cardinal with starkiller kernel..

Sent from my ONE E1003 using Tapatalk