yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] dopy25:
Nope, apparently I misunderstood. I took it to mean enable it (it was just by chance I clicked adv and saw that it was selected as when needed, I thought that was enough).

And yup, that's what happens when I don't listen. I seriously thought there was a difference for it being enabled. It boots now.

Man I feel like an idiot. Especially after going back to your post and seeing that it says "forcing"
[One (M8) Android Development] Captain_Throwback:
Here's a post by [MENTION=2605798]nkk71[/MENTION] with full info about the no-kexec workaround options:

http://xdaforums.com/one-m9/orig-development/mod-multirom-v32a-beta1-t3268122/post64248526

[MENTION=5676253]fizbanrapper[/MENTION] [MENTION=1238555]MassStash[/MENTION] maybe one of you can add these contents to the first page?
[One (M8) Android Development] dopy25:
I see there is an update in the app. What's different about it from what CPTB posted last? I don't know what I'm missing but I can't install bad boyz or ICE as secondary. I can post a log later but here's a screen shot of the installation error. I'm using the files CPTB posted last (a couple posts back, 5/2/16)

Any thoughts?
[One (M8) Android Development] CrackUK:
Actually the latest GPE flashable zips by graffixnyc all use system image and I'm having a hard time installing as secondary in sd-ext without wiping my primary system.
[One (M8) Android Development] Captain_Throwback:
[MENTION=2605798]nkk71[/MENTION]
[One (M8) Android Development] nkk71:
Hmm, guess need to revisit that part... Maybe even add some "protection" to primary partition

Think much of the code could be used from block image update
[One (M8) Android Development] nkk71:
well, it works... though happened to run across something else wrong (which would probably crawl up sooner or later)

sorry for the delay, but it's not ready, this doesn't look right, as is
[One (M8) Android Development] nkk71:
Give this one a try, I tested it, but not extensively, other than bringing TWRP up to date with the latest official commits (Commits up to Jun 9, 2016)

It adds support for scripts with:

package_extract_file("system.img", "/dev/block/platform/msm_sdcc.1/by-name/system");
[One (M8) Android Development] son_91:
I can't dual boot gpe and sense rom. I am using M8 sprint HK. Any suggestions? Thanks
[One (M8) Android Development] nkk71:
Works fine here (GSM M8), but you need to provide more details if you need help, the above statement doesn't give any information.... also make sure the ROMs you are flashing are compatible with Sprint M8.
[One (M8) Android Development] son_91:
I can not inject boot sector after flash any base-Sense Rom.
[One (M8) Android Development] CrackUK:
It works perfectly, many thanks. It requires more free space while installing, presumably to create "fake" system.img? I now successfully installed GPE as secondary into sd-ext without wiping primary Sense.
[One (M8) Android Development] nkk71:
Yes it does need more space on internal memory. It uses the same technique as

block_image_update

, which needs to create a fake system partition the same size as your real system partition, so in the case of the M8:

I:Creating image with cmd: make_ext4fs -l [B][COLOR="Blue"]2720M[/COLOR][/B] -a "/system" -S /file_contexts [B][COLOR="Blue"]"/realdata/media/0/multirom/system.img"[/COLOR][/B]

Recovery will give a warning/error if the space isn't available.

After installation into the fake system partition, the files get copied to "normal" multirom folder, and the fake system partition is then deleted.

(The same applies to ROMs that use block_image_update in their updater-script)
[One (M8) Android Development] Dragon3011:
Multirom

It work for s5 au SCL23 ?
[One (M8) Android Development] Knightofrepublic:
I'm trying to run Viperone 6.1 in multirom as a secondary , in internal memory(not on external SD card) ,turns out it can't boot at all, it reboots 2 times than on third reboot goes into recovery .flashing as primary works fine but I lose multirom.(tried to find massstash's kernels but can't download it as though he removed the download page .I've previously downloaded his kernels, so I know what I am talking about.).i desperately want to try mm sense but not at the expense of multirom capability, can anyone help me?

Device -sprint HTC One m8 non-hk

Firmware-6.20.651.8

S-off

Rooted

Multirom v33

Recovery -TWRP_3.0.2-0_multirom_m8_20160715-02
[One (M8) Android Development] nkk71:
I dont have the ROM and it would take quite a while to download, just to check the scripts, so instead, can you upload compress and upload everything in the rom.zip

[B]/META-INF/com/google/android[/B]

that has the updater script, and the .sh files they use, i know on one version of their ROM on the M9, one of the shell programs does something not compatible with MultiROM
[One (M8) Android Development] Knightofrepublic:
OK here goes.

And I appreciate your works for multirom man, thanks a lot for this little baby, which keeps excitement on par with just being able to flash a single rom at a time.
[One (M8) Android Development] nkk71:
I see the problem, same/similar as on the HTC 10 which I've already fixed. I'll need to rebuild for the M8.... maybe later today
[One (M8) Android Development] Maraudeur:
No success? :(
[One (M8) Android Development] nkk71:
Nah, works just fine, tested it myself, and works as expected (it's even in the 10 changelog :o)

Had hoped for "the nicer" solution, but havent had time to code that, and currently doing some changes on multirom and the app too, as soon as the remaining changes are ready, i'll build for the M8 as well.

Probably by the weekend ....... (no official eta though ;))
[One (M8) Android Development] Knightofrepublic:
What would the "nicer" solution be [MENTION=2605798]nkk71[/MENTION] ? Just curious

Eagerly waiting the next release,

BTW just wanted to report that not just Viperone but 6.20.651.3 ruu is having problems With multirom too. don't have any more sense based roms, but booting with multirom installed is not possible in those two, where as with normal twrp everything works as expected,would that be the same issue as this?
[One (M8) Android Development] nkk71:
Nicer would be to have the new contexts properly added/excluded. But the hooks do just nicely.

What do you mean about the RUU? I know ViperOne (depending on phone and version), have some issues (not sure if other ROMs as well), due to their particular installer approach, it will get addressed in due time.

But I don't understand what you meant about the RUU.
[One (M8) Android Development] Knightofrepublic:
That would mean, black screen after-

1.running sprint HTC ruu 6.20.651.3

2.installing normal twrp and super SU latest

3.flashing clumsy / massstash's elementalX port for sprint

3.installing multirom twrp inside recovery itself or via fastboot, either

4.flashing multirom v33

5.restart

6.as stated black screen :(
[One (M8) Android Development] nkk71:
And that kernel/boot.img is compatible with 6.20.651.3 ? (dont see any links, so hard for me to find the thread and particular version you're referring to)
[One (M8) Android Development] Knightofrepublic:
ElementalX-Port-m8-7.00.1-Sense-05-08-2016-13-29

This version of massstash's

And

Clumsy kernel 2.30

I thought that was latest and multirom app said kernel "has kexec hardboot patch"

Did I miss something obvious?
[One (M8) Android Development] Captain_Throwback:
He's asking you if the kernels are updated to work with the RUU/firmware you're currently on. You don't need to flash any custom kernels to use MultiROM, so your best bet it to try it with the stock kernel instead of the custom kernel and see if it works. Then you'll know if the issue is with MultiROM or if it's something else.
[One (M8) Android Development] Knightofrepublic:
I didn't know without kexec patch it was possible.

I never tried before without kexec kernels so I wouldn't know, I will do that and report back
[One (M8) Android Development] Captain_Throwback:
Use the latest files listed here and it *should* work fine.
[One (M8) Android Development] Knightofrepublic:
Thanks again cap

How come I never seen those files? Does posts about those updates get posted somewhere else? It looks like I'm missing something obvious again.or not maybe? Hopefully?
[One (M8) Android Development] Captain_Throwback:
Because that's not an official release channel. When there's an official release it'll be posted here. Stuff is still being updated right now.
[One (M8) Android Development] Knightofrepublic:
That explains it

I'll report back as soon as I return home and have a chance to run ruu again
[One (M8) Android Development] Knightofrepublic:
Reporting in

Sorry cap ,but after various tries ,I couldn't make multirom to make stock kernel / stock ROM combo to boot up ,with no-kexec workaround ,even as primary,no secondary ROMs booted up,either with or without kexec kernels,(but that's irrlevent in secondaries right?)

Sometimes they just hang on HTC logo,other times they get stuck at booting in multirom.

1 more thing,in multirom miscellaneous menu,no button worked.reboot,shutdown,reboot to recovery,reboot to bootloader,nothing.(this with kexec workaround enabled). So far I've tried 3 options in adv.

1.use kexec workaround whenever needed

2.but also ask for confirmation

3.ask whether to use kexec or non-kexec

Haven't tried force enable or whatever it was .

How do I find logs for this ,I did enable adv kernel logging option,but got confused about location of them.(does copy logs button , in recovery is for it)but I did capture 2 different errors on camera.hope they are useful.

All of this done on 2016-09-29 version

Haven't got around to check 2016-07-15 version

Thought I should first report in and get clear about logs.

1 last thing.if created twrp backup exceed 4096 MB, will a fat32 formatted memory card restore it as secondary ROM,on SD card that is.
[One (M8) Android Development] Captain_Throwback:
It's very possible those versions aren't the "best". The ones from the app should work fine, though, and I believe they support no-kexec. Screenshots in recovery are Power+Volume Down, btw. And there's an option in recovery under Advanced to Copy a recovery log so that you can upload it. That contains more details than a screenshot will provide.
[One (M8) Android Development] nkk71:
unofficial leak

(before i decided that the code doesn't look nice and needs better indentation)

so at your discretion

unzip the attached file, then

flash TWRP (either using TWRP itself, or using fastboot flash recovery

using TWRP install multirom.zip\

btw it's [MENTION=921816]ljjehl[/MENTION] that leaked that not me :)
[One (M8) Android Development] ljjehl:
If I'm getting blamed for this, might as well add this :

We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.

So there....... :laugh::good::good:
[One (M8) Android Development] migascalp:
I tried quickly just to see if MultiROM Manager (from your work on pme) can see the rom on ext4/µSD partition

it works. This is the first time for me than MultiROM Manager supports this feature on my m8

Thank you :good:
[One (M8) Android Development] WoBble12:
OK guys... here is the problem...

I tried installing multirom and thought it worked as expected, but it didn't ( first rom I tried to install as secondary was the CM14.1, and I thought the error 7 I got came from here, so I tried other roms, but they boot loop.. So I finally tried re-installing multirom zip and showed me error 7, now I can't flash anything as it is always the message I get :/.

Attached the recovery log trying to install multirom as you can see, I still get the multirom menu on boot so that's weird, but no way I can flash anything in TWRP multirom
[One (M8) Android Development] nkk71:
... MultiROM Recovery version: 2016-05-07 p2 ... :rolleyes:

.

You should consider updating (like 3 post above)

.

Your boot.img (in that particular flash) is just too big
[One (M8) Android Development] WoBble12:
I updated the twrp image, then tried to install the new multirom zip and it again showed an error 7 :/.

Want a log of that recovery session too?

My build prop shows : "ro.product.device=htc_m8"

while the updater script of multirom zip says assert is just "m8"

The updater script of dirty unicorns says htc_m8 , even though I didn't try to install it, maybe it would return an error too
[One (M8) Android Development] nkk71:
No need, it's point 3 above [MENTION=1162986]Captain_Throwback[/MENTION] can elaborate on that more than I.

I have it on some to do list, but it's a rather rare problem, so not high up.. Haven't even looked at how to warn about that.
[One (M8) Android Development] WoBble12:
So I should change my kernel for another one smaller with kexec?

Or RUU my phone and start over again?
[One (M8) Android Development] Captain_Throwback:
You don't need a kexec kernel.
[One (M8) Android Development] ljjehl:
That's the beauty of this MR recovery version. No kexec required anymore. :)
[One (M8) Android Development] wasim9283:
I'm s-on, on s.Rom, installed multirom apk from playstore, shall I need something or just click install?
[One (M8) Android Development] WoBble12:
Do not install the kernel he says you, it is a lollipop kernel and I suppose you're on M
[One (M8) Android Development] wasim9283:
Yes I flashed mm ruu before already, in on mm, now on s.Rom ,so

I should untick kernel option, other two keep tick ?, right?
[One (M8) Android Development] WoBble12:
Yes as far as I know, not that much into multirom as you can see before in the two pages, only got problems with it I don't know why, but it works with others Don't worry.
[One (M8) Android Development] nkk71:
Please leave the "attitude" at the door, thank you.
[One (M8) Android Development] WoBble12:
Was that against me?

I really wasn't trying to be aggressive to you or your work, I just got errors with multirom the first time I installed it, now I suppose it is because I tried installing cm14, and I fixed it tonight, now Mr works really well for me too!

Really, I wasn't mad... in my head it was almost humour, irony because I didn't know how I broke it...

I'm really sorry and apologize if I sounded rude to you ..
[One (M8) Android Development] nkk71:
Nope, it was not "against you" at all, or anyone for that matter.

However, I'm known not to be subtle very frequently, because I keep asking for logs, and detailed yet concise information... Which it seems is hard (very hard) to get, unfortunately.

Anyway, please do not feel offended, the "comment" was not directed at you, but rather at myself.

I should not "keep" promising "stuff", that I have not fully tested on at least 4 devices.
[One (M8) Android Development] wasim9283:
Oh then it's for me?

I read my comments again and again, I think there is no "attitude" in that, even if you felt something, id say "sorry" for that.

And

I asked for initial information before flashing anything to avoid problems, so no logs possible at this stage :D
[One (M8) Android Development] WoBble12:
OK so now guys, what is the app / apps you use to keep your SMS through all your ROMs?

Because at the moment I have two ROMs and if I boot the second of course SMS will come to it and I will never have them on my primary rom [MENTION=2605798]nkk71[/MENTION] from what I am reading, your leak one page before makes it possible for us to flash a 7.x rom as secondary? That's cool!
[One (M8) Android Development] lmentor:
The aokp(Android 7.1) can boot as secondary rom with multirom,but CM14.1 can't boot.that's why?
[One (M8) Android Development] WoBble12:
I myself can't get to boot dirty unicorns marshmallow as secondary rom :/
[One (M8) Android Development] lmentor:
yes,dirty unicorns can't boot too.

---------- Post added at 10:14 PM ---------- Previous post was at 09:56 PM ----------

I didn't try DU lollipop at all.and so many roms can't boot as secondary rom.
[One (M8) Android Development] WoBble12:
Sad... I thought every rom was compatible with multiboot :/
[One (M8) Android Development] nkk71:
Something not working, or you need help debugging

Please provide the following information:

a detailed explanation of the problem

.

the recovery.log (found in /tmp/recovery.log or by copying it to the sdcard and then copying it to PC)

.

the logs from /sdcard/multirom-klogs (zip those up, before uploading). that option needs to be enabled in TWRP->MultiROM->Settings

.

the link to the thread

and

name of file (+ which version) you are having problems with

.

due to the large size of some of these ROMs, I may not have time to download and test them, so please also upload the updater-script (found in ROM.ZIP under /META-INF/com/google/android/)
[One (M8) Android Development] xdagee:
Hey, where can I get aokp Nougat build, link please
[One (M8) Android Development] lmentor:
thanks,I am m8 Verizon.

CM 14.1 download link https://www.androidfilehost.com/?fid=529152257862680832

aokp download link

https://www.androidfilehost.com/?w=files&flid=126686
[One (M8) Android Development] nkk71:
from the brief look

<3>[ 3.565571] c1 289 multirom: Modifying fstab: fstab.qcom
<3>[ 3.567716] c1 289 multirom: Failed to mount /realdata/media/0/multirom/roms/cm-14.1-20161112-UNOFFICIA/cache to /cache (2: No such file or directory)

it was fixed here

thought that was included in the previous build, but can't be sure, sorry.

I need to fix other stuff before being able to upload a new version, i have a major blarf in there :(

... well good news it's fixed, bad news, i have to recompile and test :eek:

EDIT: THANK YOU for providing a detailed log, easily readable :good::good:
[One (M8) Android Development] nkk71:
Works as expected, so I guess my previous build didnt have the 7.x fixes
[One (M8) Android Development] WoBble12:
I'm a little ashamed to ask this, but did you release this build :confused:
[One (M8) Android Development] nkk71:
No sorry, but I thought it was included in the last upload.

That was today's test build after I fixed a few very messy bugs.

As I mentioned somewhere, I only work on this in my free time, and I'm already 3 days behind schedule. So... Since I missed my own deadline, because of a big blarf, guess we can wait another day or two
[One (M8) Android Development] WoBble12:
No worries, we all have a life ;) but I thought as there is an update for me on the MR app, suppose I already missed a version :p

Will upload today or tomorrow my logs etc when trying to boot DU 6, so that you never get bored ^^.
[One (M8) Android Development] nkk71:
Ah, nope the links provided by the app are way out of date, and I have no idea when or if they will get updated, as I am currently using a different version of the app.

I can update the links to the recovery and MultiROM for the official app, but you won't have the extended app capability, and updating all the manifests, links etc. Is just a waste of time for me at this point.

In time... Hopefully...

But for now you will need to stick with manually flashing the release candidates... Technically they're not leaks
[One (M8) Android Development] WoBble12:
Yeah, I thought about it too, well I'm going to flash the one you will be releasing in a few days I think ^^.

Thank you for all these quick answers, it's really cool :D
[One (M8) Android Development] nkk71:
Decided to upload the test builds anyway, so you guys can give them a try and let me know if / what's wrong with them.

All M8

Test Builds

will be on androidfilehost
[One (M8) Android Development] mszain:
Hi i'm new to multirom and neep some help. I installed multirom on cm14.1 that has kexec hardboot patch so then i tried to add miui 7 as my secondary rom. I didnt do any wipe just install the rom via mulirom twrp recovery, then when i boot into the rom(miui not cm) it booted into the system but the screen still display htc splash screen logo, did i do something wrong?.
[One (M8) Android Development] WoBble12:
Did both your roms boot? If yes, then it is OK, HTC splash screen logo can't be changed like that just with a rom. The bootanimation will change but not the splash screen ;).

And after you choose the rom you're gonna boot in the multirom bootloader it does shutdown the phone once and then boots on the rom you choose.
[One (M8) Android Development] mszain:
I mean to say that ive booted into miui (i can take screen shots, i hear miui sound effects) but all i can see is only never ending splash screen but i do can touch the screen its just the splash screen wont disappear (no ui just htc splash screen)
[One (M8) Android Development] WoBble12:
http://xdaforums.com/htc-one-m8/development/multirom-v28-unofficial-port-t2884413/post69606865

Try to do this and send it all in a new post, not enough experienced to read a log but [MENTION=2605798]nkk71[/MENTION] will look into the errors eventually
[One (M8) Android Development] nkk71:
Enable No-Kexec Workaround

Set it to either option 3 or 4, and use NO-KEXEC to boot the ROM, see if that works out for you.
[One (M8) Android Development] WoBble12:
I'm reporting a bootloop of the dirty unicorns rom with everything you said you needed. For this try I didn't flash gapps but this should not be the problem. [MENTION=2605798]nkk71[/MENTION]

https://download.dirtyunicorns.com/m8/Official/

So, I downloaded the latest build from here. (V10.6)

http://xdaforums.com/htc-one-m8/orig-development/rom-dirty-unicorns-v10-4-6-0-1-official-t3414268

This was the xda thread but it was closed.

And attached is a zip file with the recovery log, the files from multirom klogs (only the ones created after I tried booting DU, there were two other files before, if you need them ask me I will add them ;).

And inside there is also the DU updater-script
[One (M8) Android Development] nkk71:
will check a bit later, i forgot to mention, when getting the logs, you need to try to boot several times, because the last_kmsg logs, will only get backed up on the next reboot, so in

mrom_klog_1_2016-11-19-134907.txt -> you tried booting DU

but there's no last_kmsg following that particular one, you only

last_kmsg_1_2016-11-19-134906.txt

and I would need one with a timestamp just after 13:49:07 ;)

anyway, i'll check it a bit later, but thanks for being so thorough, much appreciated :good:
[One (M8) Android Development] nkk71:
[MENTION=7232733]WoBble12[/MENTION]

yep, it's a strange one, everything is getting mounted read-only, which means the /data cannot be written to and you'll end up with nothing, i'll need to debug this...
[One (M8) Android Development] WoBble12:
Well, yes, that's wierd :confused: do not know anything more than what I read here about MR, but this has to do with MR "adding" partitions I suppose, so it's funny it only happens with one rom in fact... eventhough I'm not a dev for the moment, so can't look into it myself :/ ( just learning some bits of Java since September, but not full time studies, kinda annoying lol)

So do you still want me to try and boot it again for the last log or is it enough for you to debug it?
[One (M8) Android Development] nkk71:
No need, thanks, i have it flashed and have it working (with yet another hack :p), but can you tell me which previous version of DU was working properly... I'd like to see what they changed, to be able to figure out more properly the why/what/when/how, etc ;)
[One (M8) Android Development] WoBble12:
Wow, man you're a beast, everything we throw at you you just debug it in less than 24hrs!

Well, I tried booting v10.4 but bootlooped too, did not go further and flashed the lollipop version :p. I'm not sure if anyone ever booted marshmallow DU as secondary in fact.. might download and flash every of their official versions starting with the first official release to see if this one booted, and report to you ;)
[One (M8) Android Development] nkk71:
7 mins, not 24hours :p

it's somewhat of a conflict, you can have one but not the other, .... actually they're both broken :rolleyes:

... or maybe you can ;)