yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] ckvisme:
Since my last RUU secondaries have been a PITA also but until a newer build gets posted you can:

clean flash the Rom as primary internal, make a NAND of it. Then you can flash that NAND as a secondary Rom via the MultiRom installer recovery.

Also for a quick fix, if your primary internal Rom uses a similar kernel - flash the Rom as a secondary as you normally would go back into the recovery MultiRom menu and choose 'remove boot.img' . Your secondary will then run on the primary roms boot.img (this usually works for the non-booting secondaries... As long as Rom has no other issues oc ????).

I would recommend the 12-08-15 recovery and MR zip Captain_Throwback posted... You can find it posted in thread on 12/08/15
[One (M8) Android Development] Captain_Throwback:
Here, I just built these - have no idea how they work. Maybe they'll work better than what you were using before?

MultiROM v33 zip:

https://basketbuild.com/filedl/devs...ental/multirom-20160322-v33-UNOFFICIAL-m8.zip

MultiROM TWRP:

https://basketbuild.com/filedl/devs...ery/experimental/recovery_mrom20160323-02.img

I take no responsibility for anything that breaks because of these zips.

EDIT: Updated recovery link - the old one will break some persistent values in the twrp settings. The only way to fix it is to restore Settings to default. Then it will function properly with the new version.
[One (M8) Android Development] Feldroid:
Thanks Captain! I just downloaded. Will be testing these. Much appreciated :svetius:
[One (M8) Android Development] ckvisme:
Nice work Captain, I flashed 2 Rom zips that previously didn't boot past the boot splash as secondaries (AOSP roms)

Also flashed LeeDroid as secondary and booted without issue.

Sense Roms I normally have to install from NAND to boot as secondary.

Thank u very much for the update.

I've tried TWRP 3 but keep flashing back to MultiRom recovery.

#MultiRom-FTW!!!
[One (M8) Android Development] ckvisme:
The advanced kernel logging + history option is a nice touch ?
[One (M8) Android Development] Giblet-dono:
The post you quote contains TWRP version 3 but with multirom added, no need to flash TWRP3 anymore :P
[One (M8) Android Development] nkk71:
Nice :D

How about the new partition selector ;)

Quite true, as of this version, we're working the other way around, as opposed to patching MultiROM TWRP with official TWRP updates, we have in fact rebased upstream to official TWRP code, and add the additional MultiROM functionality into official TWRP.

For those that want a partial changelog for the upcoming release:

Changelog

<tba> MultiROM v33a
=====================
* Updates for Android 6.0 compatibility
* Added no kexec-hardboot workaround
* New kernel logging + history (needs to be enabled in TWRP)

Recoveries:

<tba> dd.mm.yyyy
=====================
* Rebase to TWRP 3.0.0
* Use new stock theme made by @z31s1g - thanks!!!
* New partition selector
* Fix ZIP selector being set to wrong storage after flashing ZIP to a
secondary ROM
* Fixes for 6.0 compatibility
* Fixes for SuperSU compatibility.
* Fixes for several installer scripts using non-conventional methods
when installing systemless root
* Fix inject multriom checkmark not showing on startup
* New option to enable kernel logging + history for multirom
[One (M8) Android Development] MassStash:
update

Alright guys, thank capt and nkk71, got a lot of kill updates and improvements in this one.... nkk71 got a lot of hard work done here, great stuff.

multirom-20160325-v33-UNOFFICIAL-m8.zip

TWRP_multirom_m8_20160325-02.img

multirom_uninstaller.zip

Direct links cuz I likes those sometimes.... But yea, thanks there guys, I didn't have time to help with anything other than building out and uploading lol. Yay me.... not. Go home. Yes sir....
[One (M8) Android Development] ckvisme:
Lol, just updated via the app then I read ur post ?

Thx MashStash

and thx to [MENTION=1162986]Captain_Throwback[/MENTION] and [MENTION=2605798]nkk71[/MENTION] !!!

#multiromordie
[One (M8) Android Development] Giblet-dono:
For me the TWRP url seems dead, updating from the multirom manager app does work however
[One (M8) Android Development] Mjduddin:
Click the link from the first reply. The link has .img.img
[One (M8) Android Development] ckvisme:
MassStash the link really does look dead... So maybe you are gett8ng another ready?

The recovery says 3.0.0-0 instead of 3.0.0-2 like Captains and doesn't look correct... Although I could very well be wrong.

Re-flashed the img file and grabbed a recovery log and last_kmsg fwiw

https://drive.google.com/folderview?id=0B8bG_OajnI4gcmFaaUx3N2xzVms

Also screen shots from Captains and today's recovery home screens
[One (M8) Android Development] MassStash:
update

Heeeyyyy, so a few things missed we wanted to get into this correctly = another update.

multirom-20160326-v33-UNOFFICIAL-m8.zip

TWRP_multirom_m8_20160326-01.img

multirom_uninstaller.zip
[One (M8) Android Development] ckvisme:
Thx for the update ?

...check this out, the app says I have 2016-03-26 and the TWRP splash screen also says that... But the header (top left) in the home screen says 2016-03-23...?

Just cosmetic?

I'll grab some logs if u like ?

I updated via the app, I'll try the direct dl
[One (M8) Android Development] ckvisme:
Direct dl yields the same... Duh, why would it. Lol
[One (M8) Android Development] Captain_Throwback:
Restore your default settings in TWRP. That'll fix it.
[One (M8) Android Development] ckvisme:
That did the trick, thx ?

Had some random softboots as soon as android came back up... Maybs unrelated but it happens on internal primary and one secondary... Once I plugged the power in it was all good.

I grabbed the klogs and recovery last log

https://drive.google.com/folderview?id=0B8bG_OajnI4gb1YyN2JfRnlKRXM
[One (M8) Android Development] Captain_Throwback:
Sounds like your don't have a fully compatible kernel.
[One (M8) Android Development] Imotep95:
Awesome job! Thanks to everyone involved in the twrp-multirom project for the M8.
[One (M8) Android Development] ckvisme:
Usually happens to me when I use a sense ROM as primary , probably due to the reason Captain_throwback just listed. Try a different kernel or an aosp rom
[One (M8) Android Development] blackbuffalo:
Awesome job

[IMG="http://xdaforums.com/attachment.php?attachmentid=3699107&stc=1&d=1459168248"]http://xdaforums.com/attachment.php?attachmentid=3699107&stc=1&d=1459168248[/IMG]
[One (M8) Android Development] nkk71:
Could you link me the exact ROM (or just the kernel / boot.img) in question, seems I've finally tracked it down, but could use another kernel to compare
[One (M8) Android Development] nkk71:
[MENTION=7128009]senseye14[/MENTION]

well that boot.img did absolutely nothing for, except a nice bootloop :eek:

(is that a carrier specific ROM?)

anyway, i'm gonna need to add/change some things....
[One (M8) Android Development] nkk71:
fixed

the kernel in question (i was using) was fully GPE

anyway, probably fixed, but you'll have to wait for [MENTION=1238555]MassStash[/MENTION] to release
[One (M8) Android Development] ckvisme:
Sweet , thank u sir :). Can't wait to test it out
[One (M8) Android Development] Dark hanzo:
Good

I have a problem I can not boot in m8, from the external sd roms and partitioning the sd I even changed with a new one where both are sandisk 128 gb where Partitioned 16 gb only rom sd but will not let me earlier if I left not today.

I format my m8 where I did with the internal memory and external sd and I made clean facilities.

main rom I am using viperone m8 android 5.0.2 with 6.

any idea how to fix because I have enough time to be in this situation.

greeting

Enviado desde mi Galaxy Note3
[One (M8) Android Development] ckvisme:
I formatted part of my external SD to ext4 and used this to boot roms from (use could also use ntfs format I believe).

Are you able to boot secondary roms from internal??
[One (M8) Android Development] MassStash:
Alright guys, thank capt and nkk71, got a lot of kill updates and improvements in this one also.... Capt got 3.0.1 twrp merged, and nkk71 a few additions more in the background. This guy is killin it in code land right now, ya'll should be very very thankful we have this guy around working on our device. Not to mention the capt! Would have left sprint a long time ago if not for him... My pocket book thanks him tho really, still on old SERO plan with unlimited data and old employee pricing, not bad haha/

multirom-20160403-v33-UNOFFICIAL-m8.zip

TWRP_multirom_m8_20160403-05.img

multirom_uninstaller.zip
[One (M8) Android Development] Giblet-dono:
[MENTION=2605798]nkk71[/MENTION] [MENTION=1162986]Captain_Throwback[/MENTION] [MENTION=1238555]MassStash[/MENTION] , Thank you all SO much for your continued support on this amazing project! It's truly awesome to see what developers can do to extend the features of a device so far beyond it's "factory limits"!
[One (M8) Android Development] MassStash:
Can't stop won't stop, capt's at it again! Got TWRP 3.0.2 merged, so I build and update like good monkey does.... is the m10 here yet? sheesh...

TWRP_multirom_m8_20160405-03.img
[One (M8) Android Development] xdagee:
thanks for all your time & dedication towards this project... :good::good::good:

btw, the M10 it's on it's way. exactly a week from today we would here all about it.

early birds can have a feel of it just weeks after it will be announced. :fingers-crossed:
[One (M8) Android Development] xdadevelopers-user:
Can someone give my any guidance on how to get multirom to recognize ROMs that are installed to the external sd card?

I've tried installing to both 'SD-Ext' and also to 'Micro SDCard'. In both cases the installs seem to complete OK. In recovery I can 'see' the external ROMs in 'List ROMs' by selecting the storage location where I installed them but when I reboot and choose EXTERNAL it starts looking for an external USB drive. In the past I could just reboot when this happened and I'd then be able to boot to my external ROMs. Any suggestions?

FWIW, I'm running recovery 3.0.2.0_2016-04-05 p2 and my device has the VZW MM firmware.

Thanks,

xdadevelopers-user
[One (M8) Android Development] xdadevelopers-user:
Thank you!

After reviewing the multirom_log.txt I realized that I'm using a different kernel in my primary than I had used when it worked. So, I backed up the boot image of my stock secondary and restored it to primary. That did the trick. Now my external secondaries are showing up.

I'll need to shuffle some ROMs around now that I know why it wasn't working the way I wanted.

Thanks again Captain!

EDIT:

So, the kernel I switched to that allows me to "see" secondaries on the external SD has some other, more serious issues. Can anyone suggest a good kernel/ROM combo for VZW that I can install as primary that will allow me to see my external secondaries.
[One (M8) Android Development] nkk71:
[MENTION=1238555]MassStash[/MENTION] time for a rebuild ;)

Changelog:

* Add progress tracking in multirom 'restore' install

* Updated kernel logging + history

* No-Kexec Workaround version 2 (but you shouldn't be using that anyway) :D

:p
[One (M8) Android Development] MassStash:
Coming right up!

---------- Post added at 04:48 PM ---------- Previous post was at 03:54 PM ----------

What he said

multirom-20160409-v33-UNOFFICIAL-m8

TWRP_multirom_m8_20160409-01

multirom_uninstaller.zip
[One (M8) Android Development] xDaaexplorer8:
can i install a sense rom a secondary rom on my m8 gpe
[One (M8) Android Development] xdagee:
Spotted an update.
[One (M8) Android Development] xdagee:
*deleted*
[One (M8) Android Development] Captain_Throwback:
What?

AROMA works fine in MultiROM....:confused:
[One (M8) Android Development] xdagee:
Well :confused:

Maybe I might have been doing it wrongly, because anytime I flashed an aroma installer, I ended up flashing wiping the internal ROM.

Following the same procedures to flash a secondary ROM. Add ROM->Internal Storage->Install Zip.
[One (M8) Android Development] Captain_Throwback:
I've never heard of such a thing.

But perhaps you were using an old version. Updates and improvements are constantly being made.
[One (M8) Android Development] xdagee:
I am on the latest updated version v33. Maybe I might not be doing something right. am currently on sense8 (internal ROM), Downloading GPE.H12. I would flash as a secondary ROM and I would be back with feedback. Thank you
[One (M8) Android Development] Captain_Throwback:
What you're talking about is a function of TWRP, not the MultiROM version. So v33 doesn't actually tell me anything. You have been updating TWRP as well, right? And there are multiple v33 releases. Make sure you're on the latest one.
[One (M8) Android Development] xdagee:
sorry if you didn't get the version i was on. Here is a screenshot of it.
[One (M8) Android Development] Giblet-dono:
No problems using Aroma in combination with multirom (or secondary roms) here!
[One (M8) Android Development] Captain_Throwback:
Where did that version come from?
[One (M8) Android Development] xdagee:
got that yesterday when Multi-ROM manager checked for update.
[One (M8) Android Development] nkk71:
Seriously? Please report this post, cause you're "information" (or lack thereof) is so bad, i dont even know where to start.
[One (M8) Android Development] dopy25:
I haven't used MultiRom in awhile (had to stay complete stock for reasons) but when I did, if you installed a secondary rom through an aroma installer AND LET THE AROMA REBOOT (without exiting aroma) it would not remount the partition correctly and would boot the rom you installed no matter which (primary or secondary) rom you chose to boot. That is because it would not remount the partitions correctly. All you had to do at that point I think was to re flash the MR zip.

This is old news as far as I know but it was still only if you let the aroma reboot instead of exiting and allowing MR to unmount the secondary. It was only on some ROMs as far as I remember as well, but then again there weren't many that used an aroma at that time. Also, it would NOT erase your primary, it would only appear to do so.

To reiterate, the proper steps to install a secondary using an aroma USED TO BE

1 add rom using zip

2 complete aroma and do not let it reboot, choose exit aroma without rebooting.

3 reboot through TWRP after MR unmounts.

This happened to me a few times back then, but that was almost a year ago now. I think it has been fixed.
[One (M8) Android Development] dopy25:
I see at this time, this is the most recent on you've posted here. Should we be using this on or the one in the MR app? Or are they the same and only have a different date due to the upload to the app?

This post has 4-9-2016 whereas the MR app has 4-19-2016
[One (M8) Android Development] MassStash:
App and links dropped here are same files, I just didn't feel like posting for the latest update. Go to app for most current, figured if someone complained about not having a direct link here then I would find the time to make a post with the links.
[One (M8) Android Development] dopy25:
No complaints, I just wanted to make sure there was nothing funky going on with the app.
[One (M8) Android Development] MassStash:
Totally bro, wasn't trying to come at ya, using 'complain' in a general non derogatory sense of just mentioning something not available or working 'correctly' haha. We good. So, show of hands, does anyone need direct links or just chill for next time maybe? Few updates recently so I do plan to post another update sometime soon. Oh time.... Where beith you?
[One (M8) Android Development] blackbuffalo:
materialized inverted theme repacked for Multirom TWRP

http://xdaforums.com/htc-one-m8/themes-apps/twrp-3-0-2-multirom-m8-inverted-t3367787
[One (M8) Android Development] MrTheenD:
Trying to boot to secondery rom (official GPE) and stuck on htc logo for about half an hour, what did I do wrong?
[One (M8) Android Development] Kazuma29:
Wont boot secondary roms

So my M8 is rooted, s-on and currently running a marhsmallow gpe rom as the internal rom with a twrp multirom recovery. I'm using the latest version of the recovery and multirom. I've been trying to install a secondary rom for two days now with no luck. When I add a rom, two different events happen. Either it finishes the installation in aroma but don't boot or aroma stops and the screen flashes while in recovery.

For example: S.ROM, the latest version with Sense 8 JW, finishes installing but when booting it just goes back into recovery.

Android Revolution gets to 30% and the screen flashes in recovery. However, it appears in the multirom rom selector menu as if everything finished. Doesn't boot.

An earlier version of S.ROM based on Sense 7 finishes as well and just stays booting up with no sign of ever finishing.

Needless to say it causes some frustration, and I've installed secondary roms before on the earlier version of multirom. the one with the 2.8.7.0 version of twrp recovery. You guys have any solutions or ideas as to why this is happening?

Thanks in advance
[One (M8) Android Development] blackbuffalo:
For your information:

S.TEAM both JW and S.ROM version use stock kernel, it not support multirom, that why you got bootloop and back to recovery. Try TWRP(Not multirom twrp), flash S.TEAM rom then flash a kernel support multirom such as beyondstock kernel sense version. After that, you flash multi TWRP, flash multi rom and add secondary rom. It work fine

I'm running primary rom is latest JW version with secondary rom is DirtyUnicorns and Broken rom without any issue

Things issue with stock kernel. Try another kernel compatible with multi rom
[One (M8) Android Development] Captain_Throwback:
Come on, guys. You can't post problems without logs and complete details about your device variant, firmware, and whatever else you can think of. Posts without logs and complete device details are just going to be ignored because we don't have enough information to go on to try and predict what went wrong in your process. That's why the logs exist.
[One (M8) Android Development] Captain_Throwback:
With the no-kexec workaround, a supported kernel is no longer necessary - however in my testing I have found some issues with secondary kernels without kexec and dtb truncation, but that's another story....
[One (M8) Android Development] blackbuffalo:
Thanks for your information. I missed that
[One (M8) Android Development] Kazuma29:
But I want to keep my primary rom with GPE, isnt there another way?

I have an AT&T Unlocked HTC ONE M8, with GPE 6.0 Rom running latest twrp multirom recovery.
[One (M8) Android Development] Captain_Throwback:
"latest" doesn't mean anything to me. There's a reason we have version numbers....
[One (M8) Android Development] Kazuma29:
TWRP 3.0.2.0
[One (M8) Android Development] Captain_Throwback:
That's not a full MultiROM TWRP version number.
[One (M8) Android Development] Kazuma29:
Where do you check the full multirom twrp version number then? If you can tell me.
[One (M8) Android Development] Captain_Throwback:
If it's not right at the top of the main screen in TWRP, then you are in fact NOT using the "latest" version.
[One (M8) Android Development] Kazuma29:
3.0.2-0_2016-04-19 p2 That's what appears at the top.
[One (M8) Android Development] Mjduddin:
It's been my experience it requires some hackers of sorts. Requiring normal twrp, multirom, cm or aosp based rom with Kexec built in. I normally have to install normal twrp, then sense based rom, make nandroid, flash multirom (reboot recovery) and kexec kernel rom. Restore nandroid as secondary. I may have missed a step, but hopefully that will get you going.

It's a bit much I know,
[One (M8) Android Development] Mjduddin:
That's what I have to do to get the sense rom to boot/flash (as secondary) if it doesn't work/flash in the secondary ROM slot
[One (M8) Android Development] nkk71:
read my signature, thank you
[One (M8) Android Development] ckvisme:
Update through the app is my vote, I get notified and self updated auto-magiclly ...its just beautiful

♡(∩o∩)♡

Oh and [MENTION=1162986]Captain_Throwback[/MENTION] I haven't been on XDA much lately but it looks like congrats are in order judging by ur "new" title RD ... That wasn't there b4 this year... Correct?
[One (M8) Android Development] Captain_Throwback:
Thanks, yes that's a very recent change (it's only been a couple of weeks).
[One (M8) Android Development] dopy25:
Has anyone successfully flashed a sense or GPE rom to a secondary slot while using TWRP 3.0.2-0_2016-04-19 P2 and V33 from 4-19-2016?

I have tried CPTB's GPE from the Sprint thread and S-Rom and they both reboot once, (and it goes through a complete boot, MR select screen and all) and then it sits at the white HTC screen with the red letters for up to 10 minutes (at which point I force restart it). Am I not waiting long enough? It seems like it should do something else.

I will let it sit a little longer and then look for the TWRP log and post it. Any tips as to where the log is and if I should post anything else?
[One (M8) Android Development] nkk71:
Enable kernel logging in TWRP - > MultiROM - > Settings
[One (M8) Android Development] Captain_Throwback:
Try forcing the no-kexec workaround and see if that gets it working.
[One (M8) Android Development] dopy25:
One more thing, I thought I should try and make a backup to restore to a secondary position (so I could have the same rom I use as a primary but in a secondary slot so I didn't lose anything) I backed up the boot, the data and the system. I tried to restore it and it failed. Here is the log after that, once again, I am not sure about the MR log because it will not open but here is the TWRP log. If anyone can tell me how to open the log or how to get a valid one, I would be glad to post that too.

PLEASE SEE ATTACHED TXT. The log was too long to paste as code.

Holy cow, it's too big to attach or to pastebin. I guess open the zip? That or I can break it up on pastebin or in a text file. Someone let me know what you prefer if this doesn't help.
[One (M8) Android Development] dopy25:
Can anyone say which kernels work with MM sense/GPE and multi ROM? The only kernels in the app say 5.0.2 and 5.1.

I want to try a different kernel for the issue I've been having.

On another note, in the previous logs I posted seem to also point to a backup issue. The backups I made don't want to restore as a secondary, but I haven't tried to restore in general. Has anyone else? I can give that a shot but it still won't give any leads to installing a secondary sense or gpe ROM.
[One (M8) Android Development] Captain_Throwback:
On the off chance that the issues people are experiencing are firmware related, I decided to build a MultiROM TWRP and zips from M source. Maybe these will work better for you?

I'm using them with the no-kexec workaround enabled with no issues thus far.

P.S. These will obviously only work if you're on Marshmallow firmware.
[One (M8) Android Development] dopy25:
Well I updated to these and still don't seem to have any luck. I flashed the updated TWRP, rebooted to recovery, uninstalled MR (I didn't have any roms anyway, just wanted a fresh start), reboot to recovery, flashed updated MR, reboot to recovery.

After that I flashed another ROM as secondary (the AOSPB from before) and it is still just stalling on the white HTC boot splash. Do you think it could be kernel related? I only flashed BB rom from here and no different kernel, but I thought you had an input on that and it is kexec enabled. Is it not? Do you recommend any other kernels? I don't seem to see any updated ones from you for MM so I wasn't sure if your older beyondstock kernels would work.

I can provide another recovery log if you want. As soon as I give in and reboot from this stalling for so long, I will post it here anyway.

I used the TWRP and MR files you posted in my quote of you. Also with the no Kexec workaround (set to use when needed)
[One (M8) Android Development] Captain_Throwback:
I suggested FORCING the no-exec workaround, i.e. using it at ALL times. Did you not try that?