yashsingh1/xdaforums huggingface dataset:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Yep,

RC2 is the currently active (and supported) TWRP_MultiROM_Edition as well multirom itself.... why else would I have uploaded it?

RC -> Release Candidate, so all previous versions have been deprecated, and if I didn't have a "little disagreement" with the App earlier today, I would have uploaded all current builds for the M7, M8, M9(hima), 10(pme)

11/11/2016 18:07 4,362,114 multirom-20161111-v33e-UNOFFICIAL-hima.zip
11/11/2016 16:05 5,503,966 multirom-20161111-v33e-UNOFFICIAL-m8.zip
11/11/2016 16:44 9,834,352 multirom-20161111-v33e-UNOFFICIAL-pme.zip
11/11/2016 16:12 3,847,587 multirom-20161111-v33h-UNOFFICIAL-m7univ.zip
11/11/2016 16:36 1,706,558 multirom_uninstaller-hima.zip
11/11/2016 16:12 1,623,363 multirom_uninstaller-m7univ.zip
11/11/2016 16:06 1,623,369 multirom_uninstaller-m8.zip
11/11/2016 16:44 1,706,840 multirom_uninstaller-pme.zip
11/11/2016 16:36 23,433,216 TWRP_3.0.2-0_multirom_hima_20161111-01.img
11/11/2016 16:11 13,629,440 TWRP_3.0.2-0_multirom_m7univ_20161111-01.img
11/11/2016 16:05 20,170,752 TWRP_3.0.2-0_multirom_m8_20161111-01.img
11/11/2016 16:44 26,316,800 TWRP_3.0.2-6_multirom_pme_20161111-01.img

[MENTION=921816]ljjehl[/MENTION] has confirmed M7 and M8 builds
[MENTION=1162986]Captain_Throwback[/MENTION] has confirmed earlier builds on M8 and 10

At least I think they did :o

But, I have a small issue with the app atm, and though it's only a personal build, I don't like it, it's just the usual:

"// FIXME: not good in here"

... so, long story short:

upload will commence tomorrow at 20GMT (not that those versions have not already been uploaded, just wanna see if I can get rid of my "disagreement" with the app)

;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Hey my friend. Back again with some (most likely dumb questions). I have been reading the OPs for awhile now and confused about how to get CM working properly as a secondary ROM. Reading the part more closely about boot.imgs, I feel I may have been doing things wrong from the get go. I am confused about this part:

"So how do we deal with booting any ROM if we can't use the proper kernel for the ROM?

Easy :

Upon selection of the ROM during MultiROM boot menu, we do the following:

"flash" secondary boot.img to primary partition slot

initiate a full reboot (secondary boot.img is in primary slot)

let the ROM auto-boot up on second boot"

(I know it says easy, don't kill me please, lol)

So, since I have all Sense ROMs, I flashed Viper for primary ROM. and for my 2 Sense ROM secondaries in TWRP I went to add ROM and flashed the ROM and booted up no problem. Reading the above:

question 1) should I be "flashing" the secondary ROMs boot.img to primary, even with other Sense ROMs that I haven't had any issues with. most likely haven't had issues because they are using the same or a very similar boot.img that works on all my ROMs?

and the more important question that has been stumping me is 2) CM as secondary ROM. I am reading of others having no issues getting the CM ROMs to boot on Verizon, so I know I am doing something wrong.

I get confused by the above when it says "flash" secondary boot.img to primary partition slot, initiate a full reboot

-- am I doing a reboot of the primary ROM or the secondary ROM? and when do I flash the boot.img? before I flash the secondary ROM?

Then I also get confused about this "let the ROM auto-boot up on second boot"

-- again primary or secondary? and auto-boot is confusing as I have it set to boot the last ROM that was booted, so I know I need to stop it and choose which ROM, just not sure which one lol

am I way over thinking this, and just need to flash the CM boot.img then flash the CM ROM as a secondary ROM, and then make sure to choose it in the multirom menu as I changed it to last ROM to boot

Sorry for this massive amount of information and questions, I am loving multirom and just want to use it to its full potential.

thank you for all you do, and also for dealing with noobs like myself.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
I'll need to read that on a pc, can't make see the whole picture / question here.

But looks like you're confusing some of the "information of how things work" as opposed to what you need to to do. (the information is just so people know how it works)

In either case, you do not need to do anything manually, the "modifications" needed are taken care of by the MultiROM Recovery, and MultiROM itself

... Basically, you add a secondary ROM, and boot it. Nothing to be done manually, everything should be taken care
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Appreciate the quick response.

I'll try that again, but it hasn't been working. If not, I'll make backups of all, run RUU and see if it boots then.

Edit: I flashed the ROM like I have all other ROMs in the past and let it sit for about 30 minutes and it is just doing the ROMs boot animation the entire time. I have since flashed Leedroid ROM and it is at the app optimization so I know that I am adding ROMs correctly. When I add a ROM, it will always boot to the multirom menu and I choose the ROM I flashed (as I set it up to boot to last ROM booted), then it will boot and the boot animation starts then it will always do a reboot again real fast and then start the boot animation again and eventually the app optimization. Leedroid booted successfully. I thought I noticed this, I checked again and it isn't doing that with CM, not sure if this is related to CM or if this information can be of any use. Again thank you very much for all the help!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
I got it working i have rr as my primary and cm as my secondary.heres everything i did step for step.before flashing rom i injected boot.img flashed my secondary rom injected boot.img again before booting i moved my secondary rom to my primary rom because i couldnt figure out how to flash gapps.once moved to primary i flashed my gapps and booted the phone for the first time.i set it all up then moved my primary back to my secondary and both boot the way they should rr is my primary rom(internal) cm is my secondary rom (sd card) the reason i injected the boot.img twice was i was trying to do it off memory.i also flashed the multi twrp through regular twrp.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Okay, that's just a description how to no-kexec vs kexec-hardboot works... it's mostly a description of how I get around having to use a "kexec hardboot" enabled kernel.

It's nothing ROM and/or user related, it's just a detailed explanation of what is "happening", nothing needed by the user.

RUU seems overkill, you did say that both your firmware and MultiROM is "up-to-date" right? is the CM build you're testing confirmed to be working for your device?

Please upload recovery.log after flashing the ROM, and after trying to boot it,

the multirom-klogs folder; zip all of them up and upload so we can take a look.

Why all the injections, and the swapping? That shouldn't be necessary.

Granted some gapps packages (pure and banks or something like that would give an error, and I'm not sure if that commit is in RC2)

Sorry for the delays, but I found a huge blarf, so I need to fix that before I can upload new version; well updated TWRP MultiROM edition isnt affected by that, so you can test it if you like EDIT: test builds can now be found of androidfilehost

Changelog as per post #3

TWRP_3.0.2-6_multirom_pme_20161111-01.img
=====================
* Fix restorecon for secondary ROMs
* Rebased on android-7.0 branch
* Preliminary support for Android 7 (Nougat)
* Fix no-kexec restore primary_boot.img on devices
with PIN/Pattern/Password encryption
* Fix flashing of certain gapps zip's which are
missing the updater-script file
[STRIKE]* Add warning on failed injection[/STRIKE]
* Minor code cleanup
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Thank you for the update, no need to ever apologize for delays in my book, this is done in your free time. :)

Yea.. RUU would have been a bit much. Once a month I do a backup of all files, so I don't really worry about losing anything.

100% confirmed that others on the same Verizon firmware (most up-to-date 1.85.605.8) have gotten this ROM (ResurrectionRemix) to boot.

Here are the logs.

--Thank you for your time looking at them. :cool:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
[MENTION=2605798]nkk71[/MENTION] all the flashing and swapping was i was trying to do it off memory in my car and the swapping was because i didnt know how to add zips in the secondary rom but my bud Andybones told me how but other then that im on vzw 1.85 and have no issues.thanks for the hard work
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Thanks for the logs, I'm noticing I need to rewrite that, it's no longer reliable :crying::crying::crying::crying::crying:

it cuts the part I want to see, i'm sure it's doing it on purpose :rolleyes:

from the brief look, the flash looks fine as well as first reboot, but of course second boot log is cut -_-

Lemme check them again tomorrow
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
ty,

it should be simply "TWRP->MultiRom->Add ROM->Zip", other than that if you run into problems lemme know, the last recovery I posted should take care of flashing gapps issues, I still have to fix multirom and "some" installer scripts (though I haven't seen any one of those "mrom-offences" in quite a while)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
I got it all figured out my friend running rr as primary and cm as secondary.thanks
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] drocny87:
im finally back on track with multirom set up! viper as primary and cm as secondary.

i have to download superSu from the play store on my secondary rom. after the install it says to update the binary in recovery? which is the easiest way of doing that? my primary supersu is fine.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] andybones:
Happy multirom user here.

Also on Verizon. Can confirm with [MENTION=7771872]MrRob0t[/MENTION] that adding a known working CM ROM will not boot when adding as a secondary ROM like normal. I tried with the recent new multirom twrp recovery you just posted as well.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
Thats why i swapped the primary and secondary and booted cm rom from primary.i guess i just got lucky.lets see what op says
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Off the pc for today, but I fixed my huge blarf earlier, if you want to test early releases send me a pm, and I'll link you in

Unfortunately, I have too many things hanging in the wild, so it is difficult to consolidate and test all of them.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Hey guys, I've uploaded current

test

builds to afh here

Could you elaborate what exactly happens?

Is it a problem with the flash (recovery.log would help), or actual booting (multirom-klogs folder would help, but you need to enable kernel logging in TWRP->MultiROM->Settings->Kernel logging).

Can you also please send me the link to the thread and ROM in question.

Thanks
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Updated everything multirom that you posted today, thank you very much!

I tried flashing as a secondary again, and same result, here are the logs.

Everything flashes fine IMO.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Thanks for the logs, unfortunately the logging feature has some restrictions, I'm hoping to improve on that, but it's going to be a while before I rethink that.

From the logs, I can see / assume that mrom_klog_0_1970-07-17-161542.txt is when you tried booting into cm-13.0-20161115-UNOFFICIA

The logs, only get copied at a specific time, so could I please ask you to do the following:

1- go to TWRP

2- delete the entire multirom-klogs folder

3- reboot system

4- try booting cm-13.0-20161115-UNOFFICIA

5- if it just hangs again, force a reboot

but

not to bootloader ... either by using "adb reboot" (if that works, not sure it does on that build of CM), or using the power+voldown+volup keys, but let it go to reboot not bootloader or download mode

6- repeat steps 4 and 5, once more

7- now enter recovery, and get the multirom-klogs folder
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] MrRob0t:
Thank you for your time on this.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Well the log I was looking for is in there, it's "last_kmsg_1_1970-07-17-175429.txt" ... as usual, barely (aka not) readable, but are you sure that boot's "normally" in primary slot?

There is a lot (and I mean

a lot

) of stuff broken in there, which does not seem multirom related, tbh
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
Theres a bug in the latest multi that doesnt allow kernel flashing errors out and says unsupported device
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] andybones:
stealin my thunder eh?

lol just playin
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
I think i wrote that before i asked you lol
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Yep, my bad (had a small leftover some from other testing), uploaded TWRP_3.0.2-0_multirom_pme_20161116-01.img

that should fix it.

PS: next time, please attach a recovery.log, thanks
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] gillim74:
Cant flash gapps when flashing secondary rom on the new release.tried for the log said it saved but when i went to post it wasnt there
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
No log and no link to whatever you're flashing.... I can't guess. I need at least one of them, and preferably both. As mentioned in the FAQs.

And you can just "adb pull /tmp/recovery.log" it's really that simple ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] remix92:
is it possible to make a secondary rom as a primary rom ?

I installed RR Rom.

now i installed MuliTom and want ot use Viper as Primary Rom and RR as secondary Rom ( for now my primary rom is RR and i don't want to install it again ..)

Can i install Viper Rom now as secondary and later use it as primary ?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
yes, there's an option for "swapping" or "copying" ROMs (but that currently only works for Internal Storage (both source and destination), and alternatively, you can always use "Install from Backup" for a secondary ROM.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Snah001:
Did I read correct in the changelog that preliminary support for Nougat is present in your TWRP version?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ali nz:
It can't decrypt nougat

Captain and nkk71 are working on it!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Nosferatu.:
so has anyone been the guinea pig and flashed the Viper Nougat ROM? From what I'm reading there's plenty of disclaimers with issues. I'm certainly not going to be the one to try but if anyone has do report results. :cool::good:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
For flashing them to secondary slots, yes.

It wont help you with decryption if you flash primary N (with encryption), and it wont work if you update your firmware.... it's based on the official TWRP, so same restrictions.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Though always make backups, just in case ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] ali nz:
I'm not one of them too...it's been told on viper rom that it is based on beta version of nougat...i prefer to wait at least one month...because there is no major different between nougat and MM in my opinion
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
1-

do not

update firmware

2-

do not

flash ROM as Primary,

only as secondary

3- boot it

4- hope nothing breaks

;)

EDIT: or run your device without encryption (but the firmware part is still true)

EDIT2: I don't have the Viper version posted, the screenshot above is from an earlier test version

I'll see when I have a chance to test it fully, and confirm
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] 5m4r7ph0n36uru:
Viper is based on 2.28.401.8 which is in fact the same version number as the - today - released Nougat update for US unlocked, which is 2.28.617.8. The difference in MID is just showing WWE vs. US unlocked IMHO. So maybe the beta isn't a beta but already the RC candidate. We'll see in a few days I guess.

[MENTION=2605798]nkk71[/MENTION] sorry for the short OT mate. Couldn't resist.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
No problem, off topic is nice from time to time.... i can't see the diff between IsheCreamSandwich and Noughat either :p

Yeah, flashed beta and preview (to secondary), MultiROM held up just fine, at least so far, granted, root didnt work properly, but I'm not the first to report that (MultiROM or not)!

BTW: this is MultiROM it's a HUGE HACK, very unstable, very unreliable

dont like it

dont want test

->> do not use it

I personally like it (which is why I keep working on it, yet hardly ever use it), but it's no wonder i don't push it a little bit more.

Basically, YOU are telling me and every other person "developing" "anything" on xda -> YOU test, YOU make sure it works, the I WILL "try" it :rolleyes:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Haldi4803:
Well... Nr4 failed ^^

I had 1.98.709.5 Stock, and use moded with magisk 1.98 as secondary as Daily Rom.

Flashed Viper 4.0 Beta from the Homepage as secondary.

Didn't Boot. Stuck at HTC logo with red text.

Then I tried to boot daily ROM. Same issue. So I ran a restorecon, daily ROM booted but launcher somehow got broken ^^ had to install Nova.

I'm currently in holidays and don't have time to properly test, so I didn't even take logs....

But yeah, if no one else has issue then it's probably due to a failed download... Limited to 1mbps WiFi in my Hotel ~.~
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Sorry to hear that, I flashed Viper10 4.0.0 directly to secondary had (possibly) something not install properly (saw a magisk error), but the flash went fine, as did the boot.

Nothing "overflowed" into primary and it stayed fully intact.

Buy just fyi, the boot of secondary Viper10 took quite a while, and the "no boot" has been reported in the beta chat (for a regular install, they dont use multirom), as well as the "sometimes not working root".

I'll do more checking, had a busy day...

So if you guys prefer, wait for an updated version
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Nosferatu.:
Agreed. Thanks OP for testing the build. I was reading into it more. It's still flakey even as the one solo ROM as TWRP isn't happy with Android N. . There's also no Xposed yet for N. I guess it'll be a wait and see. :good:
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Well, I did flash it fine directly to secondary, even if some scripts didn't do their job, Viper10 4.0.0 beta, booted just fine.

I'll address it in the next release, I have a few ideas, that will

hopefully

permanently, get rid of those for problems for MultiROM.

I am however currently addressing/trying other issues, so MultiROM will have to wait a bit....

btw: I'm currently on Viper10 4.0.0 beta/preview with 2.28.401.6 firmware ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Nosferatu.:
so as long as a Nougat ROM isn't a primary it'll play nicely with MutliROM TWRP and I can still run "as usual"

Can you "flash" zips to the secondary Nougat ROM? I'm sure you remember the fiasco I had with MultiROM a few weeks ago I'm a little cautious about flashing Nougat haha!
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] grega_slo:
I just did it.

Works fantastic :D
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] myheroduane:
So your on N firmware with N ROM on secondary.... I thought firmware breaks recovery?
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Yes it definitely does break it, but you didnt read my post fully:

which would refer to this http://xdaforums.com/showpost.php?p=69837886&postcount=769
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] myheroduane:
Thank you for the clarification. And all of your hard work for the community.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] 5m4r7ph0n36uru:
[MENTION=2605798]nkk71[/MENTION] still using your mod and all's fine. I just got a little OT question to you. As mine is quite slow, may I ask which micro SD card you're using as extSD to flash your secondary ROMs? Just want to by myself a new one, and as there are so many to choose of, I'd be happy for a hint of yours.

Thanks a million

- SG -
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
To be perfectly honest, I can't (personally) make much difference between them... I have a "supposedly" very high-speed (both r/w) 128GB Lexar (I think this one )

but I'm currently using a 200GB SanDisk

And even though the Lexar is supposed to be rated higher, I can't tell the difference.

Granted that the actual installation/flashing to external SD card is a lot slower than internal, I've noticed that once the ROM is fully booted, I have no issues regarding speed... the only difference I notice is during installation, once it's up and running it feels smooth as normal.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] 5m4r7ph0n36uru:
Great thanks for pointing this out for me. Problem is, that the ROMs on secondary are quite laggy in my case, as I'm definitely not owing such a good micro SD. So will take a look at those two and decide which one to by afterwards.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Personally, I would go for neither lol

Paid a hefty amount for each of them, and to be honest, I'm quite disappointed if it comes to price/performance... I do realise where you buy them and when makes a big difference, but doesn't make much sense to me when 2 people buy the same card, one for 30 the other guy for 230...recommended you do some research as I am sure there are better cards at better prices. I'm really not the person to ask about those :o
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] kewlpanda:
Any updates on multirom
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
Nope.

You may have noticed that we're kinda busy working on normal TWRP at the moment.

That being said:

However, just because MultiROM-TWRP works, doesn't mean MultiROM will, because the method currently used for decryption will not work for the boot menu.

As mentioned previously, I recommend you stay on 1.xx.xxx.x firmware, use the current builds (the ones on AFH), with a Marshmallow ROM as primary.

And you can flash whatever you like (including N based ROMs) as a secondary ROM.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Nosferatu.:
How do you flash an N based ROM. I've tried Viper 4.0 and Viper 4.2 they won't boot as secondary. 1.9.x firmware and Viper 3.5 as primary ROM (Marshmallow). I'm using TWRP 3.0.2-6multirom_pme_20160917-02 if that matters.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
How about you try the versions I mentioned in my previous post, then let me know if they don't work.

As to why those versions exist in that particular place and why they are called what they are called... Read the OP ;)
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] Haldi4803:
But it looks like the 3way Carrier aggregation is Firmware based :(

At least I didn't see any speed improvement in LTE with N ROM on MM firmware.

Try Leedroid, works flawless for me.
[HTC 10 ROMs, Kernels, Recoveries, & Other Developm] nkk71:
You'll have to wait till we finish normal TWRP, then I'll take a look at MultiROM. But there are a few obstacles due to the new decryption method we're using.