yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] crazykc:
I tried with new TWRP MultiROM Recovery for F2FS, but its not working :( . Boot sector isn't showing while phone boots up. Phone directly boots in to Primary ROM always. :eek:
[ONE Android Development] NoSpamDan:
Are you sure you flashed the MultiROM zip file on the primary ROM?
[ONE Android Development] crazykc:
Yes... I flashed RR rom after wiping my cache nd data in F2FS. Then only I flashed multirom zip. But It didn't show boot sector after reboot. I tried to boot from multirom app after flashing secondary Rom. But It alwys booted to primary rom only.
[ONE Android Development] NoSpamDan:
Same as with the previous, non-F2FS build?

I'm looking into this, but it may be a little while...
[ONE Android Development] crazykc:
Yes, same as previous non-F2FS build.
[ONE Android Development] NoSpamDan:
Well this is going back to some earlier code, no F2FS at the moment. Everything should be working otherwise. Going to need recovery logs next time around.

This has the same name as the last one but it is indeed different: Flashable MultiROM TWRP v3.0.2-0 Recovery: TWRP_multirom_bacon_20161212-01.img
[ONE Android Development] crazykc:
Thanks for your works for multirom. And Except f2fs, everything is good with last TWRP. I hope more devolopers will try to include 'develops option' patch for mutirom.
[ONE Android Development] Matt07211:
I've just started to follow this thread and planning to port multirom to my low activity device. But I do not know what the "develops option" is, can you elaborate on it please
[ONE Android Development] gkvidhu1979:
He meant Developer Option under setting. It does not work presently.
[ONE Android Development] Matt07211:
Okay. Now I get it. Developer options doesn't work in secondary roms. I thought he ment something under TWRP.
[ONE Android Development] xeph20:
You are a hero!
[ONE Android Development] crazykc:
Does anyone check Tugapower 10 as secondary...? It wasn't booting last time I installed it as secondary ROM.
[ONE Android Development] dragsterman:
[MENTION=4435460]NoSpamDan[/MENTION]

I have only tried your TWRP with fixed fstab (the second version) but unfortunately this has the same bug with No-Kexec: If I would like to boot my primary (after booting the secondary) it can not restore my primary kernel and goes in to the recovery and the log says "Could not find primary kernel".

Do you know what could be the problem? Maybe the new No-Kexec patch would help?

EDIT:

I've found [MENTION=2605798]nkk71[/MENTION] 's fix in his TWRP_3.0.2-6_multirom_pme_20161111-01.img:

*Fix no-kexec restore primary_boot.img on devices with PIN/Pattern/Password encryption

Maybe you did not include this fix in your TWRP that is why it is not working for me?
[ONE Android Development] nkk71:
That "fix" is only a fallback of sorts. As of no-kexec 4.1 it technically shouldn't be needed.

The only reason it would happen: is if due to some reason your secondary ROM cannot decrypt your data partition.

However

this would also mean that the secondary ROM shouldn't even boot up.
[ONE Android Development] dragsterman:
Sorry I mean I have PIN locksreen (first time I thought you mean lockscreen protection under encryption) and my phone is not encrypted at all.

I have Sultan CM13 as primary and RessurectonRemix 7.1.1 as secondary and enabled the No-kexec workaround.

Sometimes (I did not figure out when exactly) after booting my secondary I can not boot my primary: it can not restore my primary kernel and goes in to the recovery and the log says "Could not find primary kernel".

If I restore my boot partition from my primary's Nandroid backup it boots fine.

What do you think?
[ONE Android Development] dragsterman:
[MENTION=2605798]nkk71[/MENTION]

The exact error log text is the following in TWRP: MultiROM NO_KEXEC: ERROR: couldn't find real primary to restore
[ONE Android Development] NoSpamDan:
Gee, thanks, but nope, not me. I am just a regular dude sharing my hobby. :D

FWIW, the OP states that MultiROM doesn't work on encrypted devices. I realize TWRP does support this, and the information may be outdated. I wasn't really planning on making a new thread or project out of this, but it's heading that way it seems.

[MENTION=2605798]nkk71[/MENTION], twas me on IRC, btw. :) I have yet to build twrpdec and strace to test. Maybe this weekend I'll have a chance, but free time these days is a bit sparse.
[ONE Android Development] dragsterman:
BTW I have wrote in a later post that my OPO is NOT encrypted at all. It was a misunderstanding.

MultiROM TWRP can not restore my primary kernel using No-Kexec workaround that's the biggest problem for me.
[ONE Android Development] Jeryhho:
How can i prepare my device to : 6.0 first rom and 7.1 second rom without any problems?

Wysłane z mojego A0001 przy użyciu Tapatalka
[ONE Android Development] Hkpatel111:
Flash Latest Multirom.img

go to recovery

wipe>advance wipe>system+data+cache+dalvik

install Android_6.0.zip in secondary & copy it to primary

install Multirom.zip + kernel/gapps/supersu/MoaAB..(in primary)

install Android_7.1.zip in secondary

install kernel/gapps/supersu/MoaAB..(in secondary)
[ONE Android Development] effry:
maybe this is the solution for f2fs. look in comments

https://www.reddit.com/r/oneplus/comments/4gmn64/multirom_problems_multiboot_menu_not_showing_need/
[ONE Android Development] NoSpamDan:
Will take a look, thanks
[ONE Android Development] nkk71:
Sorry can't resist, that is funny :good::good:
[ONE Android Development] effry:
[MENTION=4435460]NoSpamDan[/MENTION] did you tried the solution posted above? if you can point me to tutorial on how to build multirom i could try by myself
[ONE Android Development] NoSpamDan:
Sorry, I don't think removing the errors flag is a solution. I haven't spent any further time on it, since what I posted from both [MENTION=4139665]martinusbe[/MENTION] and I works, and since I haven't been using f2fs. :angel:

You can find building instructions in Tassadar's multirom Git, as well as every proper fork of it.
[ONE Android Development] elna.nitz:
I run on my device rom Stock cos 13 + xposed framework.

How do I install Multirom then install second custom Rom second base nougat 7.1.1 (Resurrection Remix rom), And still stay with xposed on the main rom ?

Thank you!
[ONE Android Development] MMWolverine:
It shouldn't be a problem running xposed on primary. I have COS13.1.2 + xposed 86.2 & RR nougat as secondary. Just install MR v33e and latest Twrp posted a few pages back.
[ONE Android Development] dragsterman:
Did you find maybe what can cause my problem?

So as I wrote have Sultan's CM13 on primary and No-kexec patch enabled and RR 7.1.1 Nougat on secondary and sometimes (for example if I flash an update to the secondary, or modify some system setting) I can not boot the primary it goes straight to the recovery and the recovery log says: "MultiROM NO_KEXEC: ERROR: couldn't find real primary to restore"
[ONE Android Development] Syaani:
Is the two cache & data partition issue fixed in the latest twrp version by [MENTION=4435460]NoSpamDan[/MENTION] ?
[ONE Android Development] NoSpamDan:
Technically yes, but under the hood, to work around it, there are no F2FS mount lines in the fstab, which makes it not actually "fixed".
[ONE Android Development] Syaani:
Alright
[ONE Android Development] :
Do you think it will be possible to use f2fs with /data and /cache on multirom in the future? Or is it not possible to create mount lines for it.
[ONE Android Development] abdullah.ibn.umar:
How to fix developer option dude ??
[ONE Android Development] Syaani:
ROM needs this patch

https://github.com/multirom-htc/multirom/commit/35a149a034b9fb6fe23d9f49f10ee03dfd5f2a43
[ONE Android Development] abdullah.ibn.umar:
After rename internal rom. Why bootloop ?
[ONE Android Development] MetalmanIX:
Am still on a Lollipop Rom do you guys think I can multiboot with Nougat Resurection Remix?
[ONE Android Development] Bigabu23:
Please let me know.. I am on Nougat Resurection Remix right now.
[ONE Android Development] crazykc:
I think it may not work. I tried to flash Darkobas CM(Marshamallow) with No spamdam's build once. But got an error. Then I downgrade the MultiROM TWRP with 3.0.0.0. It worked. But for Installing nougat roms I had to get back to No SpanDan's TWRP. :) . Try your Luck :fingers-crossed:
[ONE Android Development] nkk71:
[MENTION=4435460]NoSpamDan[/MENTION]

I'd recommend https://github.com/multirom-htc

TWRP MultiROM Edition: https://github.com/multirom-htc/Team-Win-Recovery-Project/tree/android-7.1-mrom

MultROM: https://github.com/multirom-htc/multirom/tree/master

I also have them on my own github https://github.com/nkk71 , but the "usual procedure" I use is to update my github, and if everything is tested and okay, I push them to multirom-htc.

So right now my TWRP-MROM is slightly ahead of the one in multirom-htc because I merged the latest commits from official twrp repo, but haven't tested any of them (not that I think anything is wrong with them).

It's really up to you which one to fork / cherry pick / etc. but the commits on multirom-htc can be considered stable and well tested.

As for the log I saw in your other thread, it shows a very old tag, the current one would show up as: "NO_KEXEC(4.1): ...." in the logs.
[ONE Android Development] NoSpamDan:
Thanks, when I'm home from work in some 10 hours, I'll try to review my manifest and diff to see what's up...
[ONE Android Development] NoSpamDan:
OK [MENTION=2605798]nkk71[/MENTION], I took a quick look, and for multirom, I'm using https://github.com/MR-op3/multirom . There's not a huge difference when I diff them, some icons were added and it actually pulls from a fork of Tassadar's kexec-tools repo:

This led me to wonder about the actual kexec-tools used, so I diffed those too. Not much there except the addition of some device types (which have been tested before I added A0001 for bacon):

Finally I diffed TWRP, and there were a boat load of differences. I'm not sure if it's because of a version bump or not...

View attachment 4005510

So, in summary, it's not clear to me where the older no-kexec tools version is coming from. I may kang the multirom-htc manifest and try building with it and my device stuff added in, depending on your response.

Thanks
[ONE Android Development] nkk71:
That multirom git looks fine to me, so it should have be working properly. Recommend someone does a fresh install of a "problematic" ROM to secondary, and confirm the logs show NO_KEXEC(4.1) in there.

As for TWRP, no big deal, I've just merged with 7.1 (the currently active official TWRP branch), but the changes are relatively minor as far as MultiROM is concerned.
[ONE Android Development] effry:
Sry to join like this, but multirom is still not working on f2fs formatted phones.

Could you take a look in this too?
[ONE Android Development] nkk71:
MultiROM works with f2fs, it does however need both primary ROM's and secondary ROMs' kernel to support f2fs, and the appropriate lines in fstab (or mrom.fstab depending how it's built)
[ONE Android Development] effry:
i don t know the problem with bacon, but the actual multirom version installs fine and installs rom (i tried with f2fs supported rom) but when you boot the phone the rom selection screen doesnt show up and the phone goes straight to primary rom. so its not working
[ONE Android Development] NoSpamDan:
The problem with bacon is that with both ext4 and f2fs fstab lines, the /data and /cache entries in the TWRP wipe menu are duplicated. There's no distinction as to which file system the entries represent.

The f2fs lines are currently commented out until I (or someone) can spend some time to figure it out.
[ONE Android Development] nkk71:
Why do you need to change the twrp fstab?
[ONE Android Development] NoSpamDan:
It was the only way to remove the dual entries, in the limited time I spent on it...

[MENTION=2605798]nkk71[/MENTION] have you got any ideas why this would be happening? I may try to look at this later tonight (4-5 hours, my time).
[ONE Android Development] nkk71:
Maybe I'm not really understanding the issue, but you can try something like this

TWRP/recovery fstab has nothing to do with mrom fstab (if that's the problem you are referring to), that's why MultiROM has the ability to use it's own fstab.
[ONE Android Development] NoSpamDan:
Hmm thanks, I'll scope that out later too. I can't remember which fstab it was, and I'm at work here.

All I remember was I killed all partitions in my MultiROM TWRP when I changed an fstab around... and has to push recovery back with ADB after.
[ONE Android Development] nkk71:
That's a very very old commit, so I wouldn't use it either, it's just a small hint :rolleyes:
[ONE Android Development] nachomagic:
Hi again mates

I've been reading the latest post and sincerely I'm quite confused :)

At this moment I'm with Android 6 as primary and Android 6 as secondary but I would like "jump" to Android 7 as primary and ANdroid 6 as secondary or the other way around, depends on the Android 7 Rom stability.

AFAIK the official multirom recovery don't support this combinations so [MENTION=2605798]nkk71[/MENTION] and [MENTION=4435460]NoSpamDan[/MENTION] are developing an alternative version, HUGE THANKS!!!!!!

To solve it you have to install this TWRP and Multirom zip with f2fs limitation

https://xdaforums.com/oneplus-one/development/mod-multirom-v26-t2835738/post70008281#post70008281

Is that right?

Thanks in advance
[ONE Android Development] crazykc:
Yes dude.. I am using RR(7.1.1) in Primary and Jgcaap's CM13 on Secondary:highfive:. Both ROMs are working great without any problems. If there is not any developer side patch, You can't access 'Developer options' in Secondary Nougat ROMs.
[ONE Android Development] nachomagic:
Great mate!!!

I'm using gcaap's CM13 as primary at this time ans my intention in move it to secondary.

RR(7.1.1) is one of the ROMs I'm thinking in test, so great :) Do you think is the best nougat ROm at this moment? may I PM you to ask you some ROM questions?
[ONE Android Development] player594:
A feature I would like to see is completely separate partitions for each rim so they aren't sharing same sd card. But thats probably not possible.
[ONE Android Development] NoSpamDan:
My commit to comment out f2fs temporarily is here:

https://github.com/MR-op3/device_oneplus_bacon/commit/1dc22b4f5aa7ff4e76ec24e8fb53253fcf39f1c8

I am not sure why I am seeing two /data and two /cache partitions if I allow those f2fs lines in the mrom.fstab... Ideas?
[ONE Android Development] dharmabm:
Unless I'm mistaken, there is technically no "official" multirom for this device as it is unsupported by the original developer. :silly:
[ONE Android Development] crazykc:
I can't say which Rom is best..! Every Rom has its own advantages and disadvantages. Most of the nougat Roms are stable now. It depends on your taste. I use RR rom because of its Pixel interface and customization. Also I think its stable enough for daily use. But I don't like CM HAL. RR uses CM HAL. So It depends on your need and what you expect from a ROM. As you are using multirom you can test multiple Roms and stay with whichever you like.:o
[ONE Android Development] nkk71:
It's because you're using the same fstab for both recovery and multirom. The whole point of being able to use a different fstab for multirom is so they don't "conflict" with the each other.

TWRP:

So keep the twrp fstab for twrp, no double definititions are needed for twrp, even if the fstab used by twrp says the default type is ext4, twrp will detect what kind of filesystem it's currently formatted as.

# Recovery
[STRIKE]#TARGET_RECOVERY_FSTAB := $(PLATFORM_PATH)/multirom/mrom.fstab[/STRIKE]
TARGET_RECOVERY_FSTAB := $(PLATFORM_PATH)/rootdir/etc/fstab.bacon

using a normal twrp (no f2fs) fstab.

Or alternatively get rid of that completely and use "recovery.fstab"; from makefile, if TARGET_RECOVERY_FSTAB is not defined, then it will use

ifdef TARGET_RECOVERY_FSTAB
recovery_fstab := $(TARGET_RECOVERY_FSTAB)
else
[B]recovery_fstab := $(strip $(wildcard $(TARGET_DEVICE_DIR)/recovery.fstab))[/B]
endif

fstab used by recovery should

not

include:

...
/dev/block/platform/msm_sdcc.1/by-name/userdata /data f2fs noatime,nosuid,nodev,rw,inline_xattr
/dev/block/platform/msm_sdcc.1/by-name/cache /cache f2fs noatime,nosuid,nodev,rw,inline_xattr
...

MultiROM:

MR_USE_MROM_FSTAB := true
MR_FSTAB := $(PLATFORM_PATH)/multirom/mrom.fstab

This fstab should contain

both

ext4 and f2fs.

For example from my HTC 10 MultiROM:

BoardConfig: https://github.com/nkk71/android_device_htc_pme/blob/android-6.0-mrom/BoardConfig.mk#L112

recovery.fstab (used by TWRP only, no f2fs!): https://github.com/nkk71/android_device_htc_pme/blob/android-6.0-mrom/recovery.fstab

mrom.fstab (used by multirom boot): https://github.com/nkk71/android_device_htc_pme/blob/android-6.0-mrom/multirom/mrom.fstab

yes I have f2fs disabled for the 10, but uncommenting that line in mrom.fstab, will allow MultiROM to use f2fs.

So long story short: use a normal fstab for TWRP, and multiline fstab for mrom, not the same for both.

PS: if you're also building the kernel / boot.img / rom (that you want to support both ext4 and f2fs) using those device files, then use recovery.fstab instead of fstab.bacon.
[ONE Android Development] NoSpamDan:
Wow, thanks for the comprehensive reply. I am at work but will definitely look at this tonight.
[ONE Android Development] NoSpamDan:
[MENTION=2605798]nkk71[/MENTION], so does this make sense?:

Remove lines 8 and 10 here (which specify f2fs) from fstab.bacon:

https://github.com/MR-op3/device_oneplus_bacon/blob/mr/rootdir/etc/fstab.bacon#L8-L10

Return the fstab.bacon line here, and remove the mrom.fstab one:

https://github.com/MR-op3/device_oneplus_bacon/blob/mr/BoardConfig.mk#L158-L160

I don't have a recovery.fstab, but if I do build MultiROM TWRP in-line with a ROM, can I use this as a guide (minus the ExternalSD etc. stuff)?:

https://github.com/nkk71/android_device_htc_pme/blob/android-6.0-mrom/recovery.fstab
[ONE Android Development] nkk71:
If you're going to build the ROM (including the boot.img) using those device files, then

1) keep fstab.bacon with dual ext4 and f2fs, so that the ROM/boot.img can support them

2) use MR_FSTAB := $(PLATFORM_PATH)/multirom/mrom.fstab (which also contains dual ext4 and f2fs lines)

3) either

* change TARGET_RECOVERY_FSTAB := $(PLATFORM_PATH)/rootdir/etc/fstab.bacon to some custom fstab

or

* get rid of it completely, and make a recovery.fstab

^^ this third fstab used for TWRP, should only contain the ext4 lines an no duplicate f2fs lines
[ONE Android Development] NoSpamDan:
Test for F2FS

For those interested in F2FS MultiROM TWRP recovery compatibility, try this version of TWRP MultiROM out.

While I didn't change my /data to F2FS (yet), I was able to successfully change my /cache partition to F2FS with it.

Let me know how it goes. Cheers!

TWRP_multirom_bacon_20170121-04.img
[ONE Android Development] crazykc:
I think Its not working :rolleyes: . It didn't show the "boot sector" even after injecting manually.:eek:. I can see Secondary Rom in Multirom App. But can't boot in to it. It always booting in to Primary:( .
[ONE Android Development] NoSpamDan:
Are you sure that you flashed this MultiROM zip in your primary ROM?

https://www.androidfilehost.com/?fid=385035244224404012

Also, try running restorecon on the secondary ROM.
[ONE Android Development] crazykc:
Yes.. I am sure about that.. I didn't tried to restorecon though.. I will try it next time. ;)
[ONE Android Development] Rodny9:
Hi, I'm trying to install RR as secondary but after "patching system image inconditionally" i have 2 line of: "E:unknown command [log]", then "E1001: Failed to update system image" one other unknown command and "Updater process ended with ERROR: 7" ended with failed to install zip. Help please.

I've tryed removing the assert row form the install script but don't change, and i've tryied with other nougat roms too but i have the same problem.
[ONE Android Development] crazykc:
Have you tried NospamDan's multirom.zip and Twrp recovery..? Original Twrp is having prblm with nougat Roms.
[ONE Android Development] Rodny9:
Thanks! It worked!!
[ONE Android Development] abdullah.ibn.umar:
Why media forces close after reboot in nougat ROM ??
[ONE Android Development] MMWolverine:
I've had this media fc problem a while now with RR nougat as secondary. Even sent a logcat to dev, supposedly caused by Viper, but it happens even on clean install.
[ONE Android Development] abdullah.ibn.umar:
I flash multirom uninstaller, media still force close
[ONE Android Development] NoSpamDan:
So something in your primary ROM setup? With MultiROM uninstalled, you should always be booting into the same, primary ROM...
[ONE Android Development] abdullah.ibn.umar:
How to fix ?
[ONE Android Development] crazykc:
Which Rom are you using in Primary..? I am using RR as Primary and Jgcaap cm 13 nd official lineage os in secondary. No problems to me.
[ONE Android Development] abdullah.ibn.umar:
All nougat roms
[ONE Android Development] NoSpamDan:
If you only have one ROM installed, and no MultiROM, then it has to be your primary ROM.

Try my Slim7 DEV-DM build as primary.
[ONE Android Development] st0wz:
I cant uninstall multirom, when i flash multirom_uninstaller.zip, its error: 7

plz help me!
[ONE Android Development] abdullah.ibn.umar:
Ok i try
[ONE Android Development] NoSpamDan:
Disable zip signature verification in TWRP, if it's not already disabled.
[ONE Android Development] JT1510365:
Can someone please tell me how to boot both PAC ROM Lollipop and Sultan XDAs CM13 ROM on my one plus one? I need detailed steps as i can't get the secondary rom which is the cm13 rom to boot.
[ONE Android Development] jhedfors:
Has anyone been successful with using Android Pay on a secondary ROM?

I add a secondary ROM from a backup of a CM13 ROM where Android Pay works (as primary). My OnePlus One's primary ROM is LOS14.1 nightly. This secondary just gives the standard failure (because rooted, or....etc).
[ONE Android Development] JT1510365:
I am done using this mod its so sad that it doesnt even work right. I installed all the files for multirom correctly i know that for sure and then i added Ressurection Remix ROM in multirom twrp as secondary then flashed gapps and then flashed supersu v2.65 and now only the primary will boot. I have a feeling this mod never worked in the first place. Might as well close or delete this thread if it doesnt work properly no one can help me out its sad that no one helps each other out anymore on xda as they used to:( And yes i tried running restorecon several times:)
[ONE Android Development] IamsKs:
You should not say crap of others work just because no one replied to you. It is because these developers we are able to use our phone as we want and try out various mods and roms rather then stucking with stock firmware.

As for your problem you should use primary rom with kernel which supports kexec patch. For lollilop i used A.K kernel, see if that supports pac rom. I only used euphoria as primary rom with ak kernel. See if this helps and please be thankful for developers and dont say any bad for them, this is the reason y many devs leaving opo. Hope u understand.thanks
[ONE Android Development] JT1510365:
I am not saying bad things about the dev or his work if you actually read what i said correctly i have flashed a kernel for my cm13 primary rom that supports the kexec patch which was lightning kernel and it still doesnt work. I have tried everything and unfortunately the reason people are leaving the opo threads and forum are because the people here arent very kind and helpful and they blame you for everything even your honest opinion or suggestion they get triggered and upset about it:(
[ONE Android Development] IamsKs:
You said crap of mod which has worked for many users including me. Anyway I always used this mod with euphoria as primary. Did u flash the multirom recovery. I installed multirom app from playstore and then downloaded all required files from app itself. See if it helps. Hit me [MENTION=5840274]IamsKs[/MENTION] on telegram if any problem.