yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] glyrakos:
Hello guys,

I'm planning to test some nougat roms (one at a time) besides my primary unofficial cyanogen 13.0 (6.0.1) with kernel 3.4.0 from sultanxda which is rock stable. Is it better to flash any of the kernels AK or Furnace on my primary? (Because sultanxda says that the him kernel is the best for this rom.) Or should I place it as secondary in order not to change kernel? Does anybody of you have as primary sultanxda's rom 13.0 and which rom has as secondary?

Thank you.
[ONE Android Development] musklor:
My conf : slimsabber (omnirom based) 6.0.1 on primary.

Nitrogen os 7.1 on secondary.

On primary : kernel lightning for omnirom

On secondary : kernel lightning cm14

All is alright but I have an error 7 when I want to flash the last build of nitrogen os on secondary.
[ONE Android Development] sujonjul:
There are many 7.1 roms work with secondary

I have tested :

N1 to N6

Jgcaap 7.1 up to the latest build

Purenexus up to the latest version

Cypher

Nitro up to the latest version
[ONE Android Development] 15H44N:
Can we run 2 nougat roms side by side? I mean like cm14.1 on primary and n7 on secondary ?
[ONE Android Development] Syaani:
Do they work without editing updater-scrips or such?
[ONE Android Development] sujonjul:
Yes. I've tested 6, 7 and 7.1 worked

7 and 7.1 also worked vice versa

I haven't test without revised script
[ONE Android Development] Morning000:
Can you share this script?

Edit

TugaPower n6 don't have this "abort"...
[ONE Android Development] musklor:
With nitrogen os (last build) I had to fix updater script. (secondary ROM)
[ONE Android Development] sujonjul:
Sure.. Below link

https://drive.google.com/file/d/0B-7jFMe6VP0Vc1NyelRrVmFkdk0/view?usp=drivesdk

I used zarchiver apk to replace the updater script within the rom first before flash.. :)
[ONE Android Development] sujonjul:
Last build shall be fine though
[ONE Android Development] danieldmm:
Already told you guys so many times, rom side its full multi rom compatible, kernel, update-script, if it fails it's because multi rom have problems with second rom on Android 7.1 , it's the only explanation can see.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Morning000:
Thanks. Good to know. I'll try to flash it as primary :)
[ONE Android Development] Morning000:
Hi there! For those of you who want to use TugaPower N6 with multirom and can't handle it - I have the instruction:

0. Optional - make a backup of all roms (in case something goes wrong)

1. Make a backup of primary rom (can be a backup, but you can also move/copy primary rom to secondary)

2. Flash TugaPower Recovery (in recovery: Install > Flash image)

3. Flash TugaPower (and stuff that you want; for this step use the TugaPower installation instruction)

4. Boot TugaPower (it may reboot a few times)

5. Install Multirom Manager app and flash recovery an multirom zip through it

6. Done!

After doing this you have a working TugaPower (as primary) and previously used secondary roms (they don't wipe while switching recovery). You can safely move Tuga to secondaries and restore primary
[ONE Android Development] sujonjul:
I don't have problems flashing 7.1 directly as my secondary rom though. And yes the developer option won't be able to to work on the secondary.

2 style which i applied :

1. Updating the script

2. Updating the boot image
[ONE Android Development] cosminnn:
Can you elaborate on your method?
[ONE Android Development] msri3here:
Flashed CM14.1 nightly as secondary rom.

Any fix or workaround for getting Developer options to work on this?

flashing super su causes the device to get stuck on 1+ logo
[ONE Android Development] sujonjul:
Sure..

Any rom 7 to 7.1 which build close to aosp branches i go along and revised the script.

Any rom 7 to 7.1 which build using CM branches i revised the script and boot image.

Since i flash alot I forgot the source of the boot image.. Yet it work

You may find it here, ive extracted for you..

https://drive.google.com/file/d/0B-7jFMe6VP0VZUp6dTVoeTh0bFE/view?usp=drivesdk

You may consider to flash the older version of rom first to see if it works... You can delete it afterwards..
[ONE Android Development] msri3here:
anyone?

any ideas?
[ONE Android Development] nkk71:
read back a few pages, someone mentioned this
[ONE Android Development] danieldmm:
Interesting, maybe it's the problem of people getting stuck on my rom as secondary since rom flash SuperSU at the end of Rom flash. How you guys flash SuperSU on Multirom on secondary roms?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Claudiosvs:
Hi folks, I was under the impression from the OP that all secondary ROMs use the primary ROM's kernel, and therefore need kexec patch (using lightning in my case). I have gotten kwoktopus' ROMs to work, but not PA 6.0.1, despite my primary ROM being jgcaap CM14 + Lightning Kernel (which is based off AK, so has the kexec patch). The other ROMs that work don't show Lightning as the kernel in device info...which is very strange based on my understanding. What am I missing here?
[ONE Android Development] venky716:
Every rom uses it's own kernel.

Primary rom kernel doesn't need kexec patch anymore.
[ONE Android Development] xeph20:
i'm still not sure how this works?

so if i flash the IMG you shared i can directly flash cm 14.1 nightly and tugapower as secondary rom?
[ONE Android Development] sujonjul:
I used this boot image to revised the stock. Once it's revised i flashed it by twrp through add rom button.

I haven't flashed nightly version though. And tuga yes I've flashed up to the latest build directly goes as my secondary.

---------- Post added at 03:15 AM ---------- Previous post was at 03:02 AM ----------

Ive flashed tuga without my method which resulted is errors 7

Then i revised the script it booted.

I forgot which version of your n rom is.. But the revising script is no longer applicable..

I combined the revised script and boot.. It works.

All the test were using flashing rom only.. No gapps no super su

All the test resulted in fc in development.

And it occurs both in N rom tuga and jgcaap as well.

All test were taken prior 1511 versions built. And it surely had implemented new Google security patch..
[ONE Android Development] robbie_67:
Can Ubuntu Touch be installed from MultiROM in November 2016

Can Ubuntu Touch be installed/used as secondary boot from MultiROM on a OnePlus One as of November 2016?

I've managed to get MultiROM installed on the (rather outsized) OnePlus One phone, and I can seem to install Ubuntu Touch as an alternative boot image, but selecting it at boot time just gives me a boot loop. I've tried version 307 devel-proposed, devel_stable and stable, but no luck. Am I doing something wrong, or this method obsolete now? Anything I need to add to clarify or something I should check? Thanks.

MultiROM v33b

Recovery 2016-04-17 (1)

Kernel has kexec-hardboot patch
[ONE Android Development] sujonjul:
You need to have a workaround if you desire to have Ubuntu flash within multi rom. Use the stable 15 along with February recovery works for me. Let see if it also works for you.
[ONE Android Development] danieldmm:
But my rom have SuperSU included, how could you say you test without SuperSU? You did changed the update-script? When you say revised image its what?
[ONE Android Development] sujonjul:
Yes mate. That's why i didn't flash supersu. I only flash your rom.

And yours supersu included.

Not all roms bundled with supersu as per my understanding so flashers flash supersu separately.
[ONE Android Development] musklor:
Nitrogen os and omnirom 7.1 are the only ROM that work on secondary without modification.
[ONE Android Development] xeph20:
I'm sorry man I still don't understand :(

Can you maybe make a video of you doing it step-by-step?

Would appreciate it.

Thanks
[ONE Android Development] robbie_67:
Thanks! That was it

I downloaded the modified Recovery TWRP from 2016-02-21 from the page referenced in the 2nd post of this thread and flashed this in fastboot and this solved the "not booting" problem with stable 15 and also rc-proposed 400. That would not have been my first guess as to the nature of my problem . . . MultiROM keeps tempting me to upgrade this version, but for now I know better.
[ONE Android Development] sujonjul:
Glad if it works man.. :good:
[ONE Android Development] Firewalker1980:
[MENTION=5093942]KINGbabasula[/MENTION] I've seen a post on Google+ that a version of MultiRom support Android Nougat has been released for the Moto G. Are you planning to work on a new version supporting N with an up-to-date TWRP recovery? Would be awesome.
[ONE Android Development] msri3here:
Well, I only need to activate root from developer options.

So, I achieved this by doing this.

From my Primary (rooted) rom, I copied /data/property/persist.sys.root_access and copied it to secondary rom folder - /data/media/0/multirom/roms/<romname>/data/property/

just FYI, for "Apps and ADB", this file should have entry "3" (without quotes)

reboot to secondary rom and enjoy root :D
[ONE Android Development] dragsterman:
I have got a big problem.

I have the latest MultiROM/MultiROM TWRP.

Primary: COS 12.1 with kexec hardboot patch.

Secondary: Sultan CM13 latest

I have flashed the Omni 7.1 darkobas ROM to secondary (third ROM) and after that the Sultan CM13 doesnt boot just shows the Cyanogen logo. My primary and the 7.1 Omni is also working.

Before flashing the 7.1 everything was fine.

What could be this problem?
[ONE Android Development] xeph20:
Hello,

It says i don't have permission to download.

Can you upload the boot image and script somewhere else or give permissions and URL?

Thank you
[ONE Android Development] sujonjul:
You can use below link mate.

https://drive.google.com/file/d/0B-7jFMe6VP0VV0JZZW1yR0N4d2c/view?usp=drivesdk

https://drive.google.com/file/d/0B-7jFMe6VP0VOWotWnktNjdXWFE/view?usp=drivesdk

https://drive.google.com/file/d/0B-7jFMe6VP0VSTl4YjNYdGxOeFE/view?usp=drivesdk

I also upload zarchiver apps within the link. I usually used this apps to alter the revised files within the zips. Hope it helps.

Below is the link to updater script

https://drive.google.com/file/d/0B-7jFMe6VP0Vc1NyelRrVmFkdk0/view?usp=drivesdk
[ONE Android Development] xeph20:
Thank you very much
[ONE Android Development] BigWaxx:
Can confirm it is not working as of November.

I've tried the february multirom, which allows for the twrp script to run, but I am still stuck in boot when I try to switch to it. Tried all branches too to no luck. Tried different kernels as well.
[ONE Android Development] Jeryhho:
I am sorry, but this is urgent. I flashed android 7.1 as second rom and i can't boot primary rom how can I fix it super fast??
[ONE Android Development] Deftonekid:
Help?!?!

Hey guys, I'm running Dirty Unicorns on my Oneplus One and have multirom set up...my problem is that when trying to boot any secondary ROM I get the 'multirom shut down to avoid data corruption' message...PLEASE HELP! I'm desperate to get to the bottom of this
[ONE Android Development] sujonjul:
What rom of 7.1?

What twrp you currently have?

---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------

If you desire to install Ubuntu then you may see this

the modified Recovery TWRP from 2016-02-21 from the page referenced in the 2nd post of this thread and flashed this in fastboot and this solved the "not booting" problem with stable 15 and also rc-proposed 400. That would not have been my first guess as to the nature of my problem . . . MultiROM keeps tempting me to upgrade this version, but for now I know better.[/QUOTE]
[ONE Android Development] Deftonekid:
In reply to it question I'm running multirom twrp 3.0.2

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

[/QUOTE]
[ONE Android Development] xeph20:
Now the install goes correctly. But cm nightly and also nitro rom freeze on opo boot logo for over half an hour.

Anyway to solve this? I use latest multirom TWRP
[ONE Android Development] sujonjul:
Shut down when its over 10 minutes.. It may overheating the battery.. Mind if you share what cm and Nitrogen built date is?..

I may going to check whether thw same issue is occurred with my device
[ONE Android Development] xeph20:
Latest cm nightly and 17th Nov nitrogen.

Am downloading latest now. But i don't think it's the builds. Because nobody complains about the builds

Edit: Latest Nitrogen seems to boot fine. (it's now on Nitrogen logo not opo logo)

Is it possible due to low free storage? because i just removed a few GBs before flashing the latest Nitrogen. Will try latest CM again soon

Editedit: I think i cheered to early on. it has now been 20 minutes on the Nitrogen bootlogo :( shutting it down now

Editeditedit: I tried cm and still nothing. But the strange thing is the log stops at injecting boot.img but it says succeeded and gives me the options to reboot etc. I also tried manually injecting the boot image in twrp rom settings but same happens.

After reflashing nitro without gapps it booted normally an after first boot in flashed gapps.

So maybe something with boot image is wrong from cm? I used yours. But previous nitrogen did the same thing and was with original boot image
[ONE Android Development] sujonjul:
I've tested. The workaround for this is flashing cm 14.1 as primary. Prior to do so. Move your current primary within swap tab. Do the clean flash wipe in primary then flash cm 14.1. Just flash originals without revised boot img. Afterwards you can move it to secondary though.

As for Nitrogen i assume no issues found flashing it as secondary.
[ONE Android Development] BigWaxx:
I tried all combinations you listed as I previously said. It only helped me to finish the install, not boot in the system.
[ONE Android Development] xeph20:
The problem is that my storage is full and my TWRP OTG doesnt work so i can't backup my primary and to move i also need a lot of free storage :/

Which is why i hoped your method with the script and image worked.

Thanks for all the help though
[ONE Android Development] ninad1234:
AICP 12.1 nightly ROM is not installing via Multiorm v33b as a Secondary ROM

hi guys,

I tried to install AICP 12.1 nightly on my OPO using Multirom v33b as a secondary ROM. But it failed.

I read all the above post related to problems installing Android N ROM as secondary ROM, thnx for posting your solutions regarding this issue.

but can anyone tell when Multirom team will update their modified TWRP Recovery to become compatible to install Androind N roms as secondary ROM.

Also i am attaching SS regarding this issue below.
[ONE Android Development] musklor:
Be careful with gapps.

I had issues with slim revisited.

I had to clean system, data, flashed cm nightly and the last open gapps. Cm nightly 14.1 started now. (Primary)

Do you use cyandelta or cm downloader?
[ONE Android Development] glyrakos:
Hello,

I tried to make multirom working with Tuga N7 as primary flashing multirom app, the twrp for multirom and without flashing kernel because it doesn't support nougat and also tuga developer states that it is ready for multirom. Is it possible to have primary the N7 and secondary 6.0.1 from sultan or I have to flash it vice versa? If I must do so the kernel for 6 from multirom app is merged with kernel from sultan or ovewrites sultan kernel? Will it work?

Thank you
[ONE Android Development] dragsterman:
I flashed OMNI 7.1 to secondary (third ROM, and working fine) but my secondary Sultan CM13 stopped working (stuck at CM logo animation). My primary is working.

This happened the second time, very frustrating though I have backup.

What could be the problem?
[ONE Android Development] tilaksidduram:
Boot into your multirom twrp recovery and go to the 2nd rom (Sultan CM13) and click on run restorecon once its complete next reboot out of recovery and boot into your Sultan CM13 rom, it should now boot successfully. This issue happens only when you have a Nougat rom as secondary installed.
[ONE Android Development] dragsterman:
I have also did a restorecon(just forgot to write it here) with no success.

I have restored my Sultan CM13 and working fine. Strange.

What is your setup in MultiROM? How many ROMS do you have?
[ONE Android Development] dragsterman:
I have flashed Ressurection Remix 7.1 as primary, check the No-Kexec patch (only if needed) and none of my secondaries (COS12.1 and Sultan CM13) booting even though I have run restorecon on both of my secondaries.

Very-very frustrating. :crying: :(
[ONE Android Development] MMWolverine:
Using MR in this state is a nightmare. I sent KINGbabasula a message, hope he'll have time to fix this.
[ONE Android Development] NoSpamDan:
I have built a version that seems to have eliminated the restorecon issue, but still can't boot an N ROM as secondary... I'm still looking into it when I have time.
[ONE Android Development] tilaksidduram:
In your custom build are you getting the multirom boot menu when you try to toggle between roms ?

I have a custom build of TWRP and multirom that allows me to boot into any rom but the only down side is I don't get the multirom rom boot menu so I have to boot into the primary rom and then use the multirom mgr app to boot into my secondary roms. So what I have done is installed the multirom mgr app on all of my secondary roms so when I wan to boot into any of the roms I just open the app and perform a boot into that rom.
[ONE Android Development] CBpbxEcmecmBeH:
has anyone tried EFIDroid yet?

http://xdaforums.com/showthread.php?t=3447466
[ONE Android Development] musklor:
Me but I can't find the ROM file.

I took procedure for the fairphone 2 with no success.

We have to wait atm, work in progress.
[ONE Android Development] xeph20:
Which custom versions do you have? And can you directly boot cm14. 1 nightlies as secondary rom with it?
[ONE Android Development] Hkpatel111:
[MENTION=4139665]martinusbe[/MENTION]

thanks for update...

just flashed latest Multirom twrp &

Multirom.zip using same twrp & installed Latest Multirom manager apk

Flashed latest Resurrection Remix + Gapps + Lightning kernel + MoaAB + SuperSu (as Primary)

successfully booted.. No problem so far.. thanks again..

btw..

>twrp is showing TWO Cache partition in

twrp>wipe>advance wipe menu

>During boot Multirom boot menu>misc(bottom) still showing v33b as well as Multirom manager (i think it should show Multirom v33e)

here is SS

sorry for my english _/\_
[ONE Android Development] tilaksidduram:
Yes I can boot any Android N Rom as secondary. I have built the latest TWRP recovery from the sources. Only issues with MM roms. Restorecon will help boot MM roms.
[ONE Android Development] xeph20:
Where can I find it? Or can you upload your built?

Thanks
[ONE Android Development] musklor:
Yes and it works!

Cm (infernal) and the second ROM RR 7.1

Reboot on recovery and go to multiboot/média/0/

Install ROM and gapps

Reboot and choose your ROM.
[ONE Android Development] Akhil916:
Idk what happened but all of a sudden I can't boot into secondary ROMs. It just happened after I updated one of my other ROMs. Now, it directly boots into internal ROM without asking me. I still can tinker through the recovery, though.
[ONE Android Development] Hkpatel111:
solution:

flash Multirom.zip again

care:

dont flash rom.zip with open Recovery script in future
[ONE Android Development] NoSpamDan:
Browser derp - duplicate post
[ONE Android Development] NoSpamDan:
Hopefully [MENTION=5093942]KINGbabasula[/MENTION] won't mind my sharing here. You can thank [MENTION=4139665]martinusbe[/MENTION] as well for much of this.

Flashable MultiROM TWRP v3.0.2-0 Recovery: TWRP_multirom_bacon_20161212-01.img

Flashable MultiROM ZIP: multirom-20161206-v33e-UNOFFICIAL-bacon.zip

Flashable MultiROM Uninstaller ZIP: multirom_uninstaller.zip

Dark-themed MultiROM Manager App: MultiROMMgr-GZR-TBO.apk

Sorry, support is limited, but I'll try to help if needed. I didn't want to start up a new thread at this time, especially since everything here is so nicely explained and laid out...

I too have reached out to [MENTION=5093942]KINGbabasula[/MENTION] some 2-3 weeks ago, but haven't heard back from him.

Have fun, and enjoy!

EDIT: My recovery is swapped with Martin's here since mine had duplicate fstab entries.

EDIT2: My updated recovery with fixed fstab is linked above now. :)

EDIT3: Updated TWRP recovery again, this time for F2FS.

EDIT4: Another spin, for now no F2FS... Need to sort out what this does.

EDIT5: FYI I have made a new MultiROM thread, per the request of [MENTION=5093942]KINGbabasula[/MENTION]:

https://xdaforums.com/oneplus-one/orig-development/mod-multirom-v33e-nougat-friendly-t3555311

Please direct further discussion regarding my or [MENTION=4139665]martinusbe[/MENTION]'s updated versions to this new thread going forward!

Thanks!
[ONE Android Development] dragsterman:
Thank you for your work I'll try these at the weekend. :good:

Does this new MultiROM version allow to flash AND run any Nougat ROM without problems?

Does the no-kexec patch work without bugs? I'm just asking because with the previous MultiROM TWRP I have a bug that it could not restore my primary kernel after running a secondary ROM.
[ONE Android Development] NoSpamDan:
I believe the no-kexec patch needs to be reverted in order to run as a secondary now. I did this in my Slim 7 build and it flashes/boots as a secondary.

Again, special thanks to [MENTION=4139665]martinusbe[/MENTION] for pointing me in the right direction, and for patching up some source to get this working!
[ONE Android Development] Hkpatel111:
thanks for update..

>New twrp showing TWO cache partition & TWO internal storage partition...

how to choose correct one (to wipe & to install rom..)??

>Ubuntu touch as secondary not working...

(installation successful but bootloops at oneplus logo)

>Multirom manager still showing Multirom v33b
[ONE Android Development] mustang_ssc:
Yep, 1st problem here aswell, when doing a backup and wiping.
[ONE Android Development] NoSpamDan:
I've changed the link to the recovery to Martin's build for now.

TWRP_multirom_bacon_20161206-02.img
[ONE Android Development] Hkpatel111:
already checked before.... same problem...
[ONE Android Development] NoSpamDan:
Ugh.. OK

Same source, really, so It makes sense.

I have an idea what It might be, but I'm mobile for several hours...
[ONE Android Development] Akhil916:
Yeah, the problem was just with the new zip file. I tried booting with another secondary ROM and it started working.
[ONE Android Development] Hkpatel111:
dont flash rom.zip using kernel auditor Or any other app.

just flash zip manually in twrp...
[ONE Android Development] NoSpamDan:
I updated my original post to include this fixed version of TWRP MultiROM. The partitions list should now be fixed. Have fun!

Flashable MultiROM TWRP v3.0.2-0 Recovery: TWRP_multirom_bacon_20161210-02.img
[ONE Android Development] sebincsebastian:
No Multirom option in advance menu TWRP

I cant find any multi rom related settings in advance menu in TWRP. I have done everything as discussed here.
[ONE Android Development] crazykc:
Thanks [MENTION=4435460]NoSpamDan[/MENTION] for updated zip and recovery. I tried it with some N nd M roms with ext4 partition and it is working great. I think it won't support f2fs partitions. Boot sector is not showing even after injecting the boot sector from recovery. I tried reflashing the zip but no effect at all.
[ONE Android Development] nkk71:
Click the icon in the top right corner
[ONE Android Development] crazykc:
I tried roms like XenonHD, jgcapps CM 14.1, slimrom 7.1.1 etc on secondary. Everything except 'developers option' work. TugaPower N9& N10 installed successfully but not booting up.
[ONE Android Development] NoSpamDan:
OK, I have updated the fstab again for /data and /cache formatted as f2fs. Give it another shot if you can to see if this fixes f2fs.

Updated TWRP MultiROM Recovery for F2FS: TWRP_multirom_bacon_20161212-01.img

Well, supposedly this is needed to fix the Developers Options FC: https://review.slimroms.org/#/c/22989/

If you are using my DEV-DM build of Slim 7.1 (or 7.1.1), this should be included. Otherwise, the ROM in question may need this.
[ONE Android Development] Hkpatel111:
TWO data & TWO cache Partition again in Latest build.