yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Captain_Throwback:
Are you sure you have a full download of the ROM? Because I know that Viper is way bigger than 400MB. That's probably your problem, then. I assume you already confirmed the checksum of your file?
[One (M8) Android Development] whytry23000:
I just double checked. The file is around 2 gigs and the md5 matched.
[One (M8) Android Development] Captain_Throwback:
Does the file flash as a primary?
[One (M8) Android Development] whytry23000:
Just tested it, and it does.
[One (M8) Android Development] TarekElsakka:
Did anybody have any luck installing the latest "[ROM][OFFICIAL] CyanogenMod 13.0 Nightlies for the HTC One m8" as a secondary in MultiROM?

I was able to install the unofficial one as a secondary by removing some lines in the updater-script but it doesn't seem to work for the official one.

Any ideas?
[One (M8) Android Development] nkk71:
doesnt seem like you removed the lines, the log still shows the check, which fails, and therefore considers the whole installation as a fail:

...
Verifying the updated system image...Verifying the updated system image...
script aborted: system partition has unexpected contents after OTA update
system partition has unexpected contents after OTA update
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
rm: can't remove 'META-INF/com/google/android': No such file or directory
Failed to install ZIP!
...
[One (M8) Android Development] TarekElsakka:
That's odd, because I'm pretty sure I removed it.

Check the attached screenshot.
[One (M8) Android Development] nkk71:
That looks OK, maybe you forgot to replace it back into the original ROM.ZIP before copying it to the phone?
[One (M8) Android Development] TarekElsakka:
Well I always used to edit it inside the zip file itself and then save (usually worked), but I'm going to try extracting the file, editing it, and adding it to the ZIP file once again.
[One (M8) Android Development] ssojyeti2:
I got it to work by also removing the line

mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");

EDIT: NVM didnt work :'(((
[One (M8) Android Development] nkk71:
it's due to the variant_script.sh

we have that fixed in one of our experimental builds, but until the devs decide to push it out,

you can do the following modification in variant_script.sh (located in ROM.zip -> /install/bin/variant_script.sh):

at the very end:

umount /firmware/radio
exit 0

to

busybox umount /firmware/radio
exit 0

PS: whenever an installation fails, you should always pull the recovery.log (in /tmp/recovery.log) to see what failed
[One (M8) Android Development] bazzi12:
Does this work with marshmallow because I keep getting booted back to recovery when I flash the zip in this OP.. Also multirom manager doesn't seem to work either..can't download multirom from there
[One (M8) Android Development] nkk71:
We'll need more detailed information about that; what's the error what ROM, etc.

Due to a change in "thought", the devs have decided to enlarge the community, which can only bring more benefits in the future, imho, but which also led to the M8 links being broken (for the time being, hopefully they'll be up soon); you can download them from here manually:

M8 - MultiROM 32 Installer ZIP

"md5": "d590075b216a70d4ad215f18513c6dc3"

M8 - MultiROM TWRP Recovery 20150923

"md5": "911b2ccee9f399a1752554820485f45a"
[One (M8) Android Development] dopy25:
I think there is an issue that a lot of roms are checking the MID and possibly the system partition. Neither of which work as a secondary. I have a screenshot and a recovery log posted in this thread, I thought it was an issue with a rom doing a check, but once I looked at the script for that rom it looks like it is necessary for the carrier specific stuff.

I'm not sure if anyone can take a look at this or knows what it says. But I flashed the rom from the thread linked. AICP as a secondary. I was initially able to flash CM13 as secondary after deleting the system block check, but it looks like there is a new process in some if not all (AOSP?) MM roms. I have been able to flash a few MM stock roms (GPE A9 Port) as secondary so I think it might be AOSP. Let me know if anyone wants any other logs or information.

Sprint HK edition, latest FW from 4.25.654.18.

S-ON. And as far as I know I have the same MR and recovery files flashed that you linked.
[One (M8) Android Development] Captain_Throwback:
Yes, there are some experimental versions that fix the error you're referring to. [MENTION=2605798]nkk71[/MENTION] just linked the latest release versions from the app so that people can retrieve them since the app isn't working right now.

Once the updated code has been more thoroughly tested, I'm sure the guys will release some teaser versions for you to try out. I hear there's even some workaround for kernels that don't support kexec-hardboot (!), compliments of [MENTION=2605798]nkk71[/MENTION] ;).
[One (M8) Android Development] nkk71:
Teaser? me? :silly::p

Of course I already did ;)
[One (M8) Android Development] dopy25:
Good stuff. I'm just glad it wasn't something easy enough to fix (edit for the common user)
[One (M8) Android Development] Giblet-dono:
I have both MM GPE and MM Sense running, neither needed to edit scripts, as such they work "out of the box"

MM Sense: Skydragon seems to work fine for me: http://xdaforums.com/htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062378

MM GPE: Stock MM GPE form here: http://xdaforums.com/showthread.php?t=2708589

I Guess Skydragon GPE MM should also work, same team as sense MM, so probably same updaterscript: http://xdaforums.com/showthread.php?t=2706391

These work as secondary roms for me, but mind you, for GPE the "switch" trick is needed as always

Backup primary, install GPE as primary, switch primary to secondary and put backup from primary back
[One (M8) Android Development] bazzi12:
I was on stock rooted gpe 6.0 rom. Every time I flashed the multirom from the OP I would get booted back to recovery . Basically I could never boot into the rom, I just got sent back to recovery. I'll flash the one you attached and report back
[One (M8) Android Development] Captain_Throwback:
Okay, so don't tell anyone, but I decided to build a super-secret test version of MultiROM with the fix for the variant-script.sh and the no-kexec-hardboot kernel workaround from [MENTION=2605798]nkk71[/MENTION]. But since I'm (supposedly) not actively developing on this anymore, I didn't think I should post it, especially since the changes are all experimental. But I figured some of you brave souls would want to try it anyway, so here are some super-secret links, lol ;):

multirom-20151208-v32-UNOFFICIAL-m8.zip

TWRP_multirom_m8_2.8.7_20151208-01.img

BEWARE OF DRAGONS - THIS IS ALL VERY MUCH STILL IN THE EXPERIMENTAL PHASE, so don't be surprised if there are issues. I recommend backing up any data you don't want to lose before using any of the above files.

But, feel free to report back if every works ;).

EDIT: Also note these potential issues (taken from the code on [MENTION=2605798]nkk71[/MENTION]'s github) -

Potential problems resulting in lingering primary_boot.img:
[LIST=1][*]Reboot from secondary to recovery, flash new primary ROM/kernel (this may be fixable in inject.c, but my first attempt had unexpected results)
[*]Reboot from secondary, then fastboot flash boot boot.img
[*]While in secondary, use an app (MultiROM, Flashify, etc), which dd's the boot.img
[*]Others??[/LIST]
[One (M8) Android Development] nkk71:
What build... I have no idea what you're talking about or where to even find that IF it exists :)

NICE, lurking in the shadows? ;)

and Gremlins, they are nasty to get rid off once hatched

In short, do NOT try to mess/flash/etc your primary kernel if the last ROM you had booted was a secondary.

Feedback is always welcome.

Thanks [MENTION=1162986]Captain_Throwback[/MENTION]

.
[One (M8) Android Development] dopy25:
Yes, gremlins. Don't feed them after midnight for sure.

The files you posted, CPTB, work like a champ. I flashed the MR zip, then the recovery, rebooted and installed AICP just fine. No issues at all. (I don't have any storage when booted into the rom, but that may be ROM side) If not and someone thinks it's MR related, let me know and I can try for a log.
[One (M8) Android Development] Captain_Throwback:
Nope, not MR related, That's a CM upstream problem right now.
[One (M8) Android Development] Captain_Throwback:
Well, seeing as though [MENTION=1588500]dopy25[/MENTION] is the only one that actually tested this version, I'm kind of happy I moved on :rolleyes:.
[One (M8) Android Development] dopy25:
Haha, yes. But I am very happy for that build. No issues yet with it. I even just installed a sense MM as Secondary and am using it now.

EDIT: Wow, it does only show one download... I wonder what happened to the MR users.
[One (M8) Android Development] Jbb3393:
I have downloaded and installed both your updates and no problems here... but I haven't flashed anything either hence why I haven't felt worthy enough to mention it. I'll flash a secondary for fun and report back
[One (M8) Android Development] fizbanrapper:
In case anyone is having trouble with the MR app updating, download this modified apk:

MultiROM Mgr APK
[One (M8) Android Development] EthanG_1988:
I have installed both experimental updates. Everything seems to be running very well. I installed the latest build of AICP MM as a secondary, and it seems to be running really smoothly.

I have been using Multirom for about a year or so on the M8 (verizon variant).
[One (M8) Android Development] Giblet-dono:
I also tested it!

I just didn't encounter any problems that weren't described yet!
[One (M8) Android Development] Kazuma29:
Full wipe

While adding a secondary rom, does a full wipe affect the primary rom? Does it delete anything on the phone?
[One (M8) Android Development] Jbb3393:
From my experience a full wipe via aroma installer into the secondary slot does not effect the primary.
[One (M8) Android Development] shasen1235:
Thank you CPTB!

My multirom stopped to work after upgrading to MM

Hope this will make it work again

By the way, does multirom support rom zip contains .img instead of folders?

I found it when I flash a img rom zip it will install to primary no matter where I choose
[One (M8) Android Development] Kazuma29:
Mobile data

Thanks for answering my doubt earlier. I have a question, I installed a secondary rom but then after I booted the primary rom, mobile data doesn't wanna work anymore. It worked on the secondary rom and on the primary before I booted again the primary
[One (M8) Android Development] Captain_Throwback:
Image? I'm not sure what you mean. Why would a rom zip be installing an image? You mean sparse_dat?
[One (M8) Android Development] Giblet-dono:
I think he refers to a rom zip which includes files like system.img and uses dd if/of commands to install it

Or a zip including a boot.img
[One (M8) Android Development] Captain_Throwback:
Every ROM zip includes boot.img, so that's obviously not the issue here. It's this system.img that concerns me. MultiROM is definitely not set up to handle such a thing. Tell the ROM chef to use sparse_dat - that should work fine.

---------- Post added at 09:18 AM ---------- Previous post was at 08:34 AM ----------

[MENTION=1662843]Giblet-dono[/MENTION]

Where did that rom zip you're referring to come from?
[One (M8) Android Development] shasen1235:
Ah yes!

That's what I mean

Sorry for confusing

I do mean the rom zip contains system.img and data.img...etc

Now not much dev are cooking in this way, but some still are

I was curious to know if multirom supports img zip and now it is clear

I think we should note this in OP so others might not accidentally have their primary pasted over?:D
[One (M8) Android Development] Giblet-dono:
It came from one of the early GPE leaks

The thread was closed a while back and most files were deleted BUT!

I uploaded the file I have here:

- DELETED URL -

Let me know when you have it so I can delete it again
[One (M8) Android Development] Captain_Throwback:
Where are these ROMs? ROMs should not be flashed using this method. Take that up with the ROM chefs. Can someone link me to one of these so I can see the updater-script for one of them?

Image files should be flashed via fastboot, so I'm very confused by what you're describing. I downloaded that GPE ROM and it didn't include a system image, so I'm curious to know the source of these zips.

---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------

So the solution here is simple - delete the old zip and download a new (correct) one. There's no reason MultiROM should support an old hacked rom zip.

P.S. I'm not going to download that, so feel free to delete it from your Dropbox and anywhere else you may have it.
[One (M8) Android Development] Giblet-dono:
Don't worry I wasn't using it anymore, but I know some roms still use this method, though I at the moment I cannot find any other for you to test.

But the method used in the other roms is the same used in the one I linked above, so for "research" or "debug" purposes it should work just as well
[One (M8) Android Development] Captain_Throwback:
If you can find me a current ROM that uses this method, I'll look into it. I'm not going to look at an old zip that was hacked together from a leak. I truly hope no ROM is still using this method.
[One (M8) Android Development] shasen1235:
Right there the A9 port S.Rom is using img for system and data

http://xdaforums.com/htc-one-m8/development/romthe-worlds-first100-m9-port-m8upload-t3064838

And if you want to see just the script,here it is

ui_print("---------S.ROM ROM Android M Sense7----------");
ui_print("----------------S2 2.0.8-X-------------------");

ui_print(">> Wiping system");
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/platform/msm_sdcc.1/by-name/system");

ui_print(">> Wiping cache");
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/platform/msm_sdcc.1/by-name/cache");

ui_print(">>> Flashing System");
package_extract_file("system.img", "/dev/block/platform/msm_sdcc.1/by-name/system");

ui_print(">>> Flashing kernel");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

ui_print("S.ROM By Sun Dream");
ui_print("Zip repacked by @topjohnwu");

unmount("/system");
ui_print(" ");
ui_print("Done!");
set_progress(1.0);

I personal don't think this is a good way for flashing

Not easy to edit and may cause problem for like multirom

But if the dev prefer using this way,there's not much I can(should) complain
[One (M8) Android Development] Captain_Throwback:
So it's not using dd either. Wow, that's just a horrible idea. If the ROM is going to be provided as image files, then they should be flashed via fastboot, not custom recovery. I reemphasize that this needs to be fixed by the ROM maintainer. They should be using sparse_dat, not a full system image. That's why it's breaking stuff.
[One (M8) Android Development] taingster:
Hello. I full converted my htc m8 to gpe 6.0. Can I use multirom on it....or do I need to convert back to sense first? Ultimately I want to dual boot gpe 6.0 and sense 6.0 because fm radio doesn't work on gpe but does on sense. Thanks.
[One (M8) Android Development] tsukasayeo:
I am on marshmallow sense rom with elementx kernel, and has problems to flash any secondary rom.

Always respnse "E:Error executing updater binary in zip"

Attach is full recovery log.

has tried wipe cache and dalvik_cache, and system partition is unmount

Did anything I miss?
[One (M8) Android Development] Makerrr:
same here
[One (M8) Android Development] Captain_Throwback:
Yes, you missed the test version of MultiROM TWRP I posted that fixes this.

[MENTION=5676253]fizbanrapper[/MENTION] maybe you can add the test versions to the OP somewhere?
[One (M8) Android Development] tsukasayeo:
I find it, flash 20151208 TWRP/Multirom, and everything works great!
[One (M8) Android Development] bbgreen:
I was able to flash bliss mm as a secondary with jw srom as primary. Thanks captain for the test builds working with no problems.

Verizon S-OFF
[One (M8) Android Development] thekwijibo:
I've been running MultiROM 2.8.7_20151203 for a while without success. A few times, I managed to dual-boot to another ROM, but large sections of the touchscreen were "dead zoned". Now after repeated attempts, I'm unable to boot into any secondary ROM. My primary ROM still seems to boot just fine, but if I try to boot to another ROM, the phone goes back to the fastboot screen. If I hit reboot, it will boot into recovery.

I've tried multiple versions of MultiROM, tried the modified APK, and recently discovered the newer 20151208 TWRP/Multirom. I was hopeful, but it appears it mimics the same behavior as before. I feel like I'm missing some important step, or something really obvious. Has anyone seen this behavior, or know what I'm doing wrong?

Thanks.
[One (M8) Android Development] rwagner74:
your multirom twrp recovery super secret modded made in december... cant find anywere

ive hit youer basket link, but the modded multiro twrp

recovery file(december build)cant be downloaded. really want my multirom back, and dont whant issuws again flashing a secondary rom wich whixh messes my partions since mm upgrade to srom. yi

your modded multi rom apk says unreckonized device as well. cant seem to find much success since mm

. also is there a flashable instalatin to reinstal multirom... it disapearred aff

srom installed. cant do it recover. sorry for rant, frustraition is just building up.
[One (M8) Android Development] Giblet-dono:
If your primary rom is GPE change it to Sense and retry

---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------

Both URLs download fine for me:

https://basketbuild.com/filedl/devs...ental/multirom-20151208-v32-UNOFFICIAL-m8.zip

https://basketbuild.com/filedl/devs...mental/TWRP_multirom_m8_2.8.7_20151208-01.img
[One (M8) Android Development] thekwijibo:
Sorry, I should have included that my primary rom is Sense (Venom).
[One (M8) Android Development] Giblet-dono:
That's strange..

I also use Sense as my primary rom, combined with ElementalX as my kernel

I use the build of which I posted the URLs one page back and they work properly for me

I can add/remove/boot almost anything I want!

Guessing you already tried reinstalling multirom recovery, multirom zip and kernel with kexec patch?

I am not sure where you problem lies, hope someone else can help you!

(Otherwise, RUU might be the only possible way)
[One (M8) Android Development] thekwijibo:
Yeah, I'm at a bit of a loss. A month or so ago, I was encountering some issues, and decided I was overdue for a RUU. That didn't seem to help things out, and I started having more difficulty with Multirom.

Right now, I'm even experiencing difficulty just clean flashing a ROM in my primary partition. I'm currently trying to debug this weirdness. I've done the following:

Full wipe, flashed Venom (MD5 double checked) - Rebooted. Boots into Fastboot(fail).

Full wipe, flashed Venom (without injecting curr. boot) - Rebooted. Boots into Fastboot(fail).

(*yikes* did I brick my M8?) Restored Venom backup. Nope, seems to boot fine.

Full wipe, flashed GPE MM - Rebooted. Boots into Fastboot(fail)

Full wipe, flashed GPE MM (without injecting curr. boot) - Booted into GPE!

:confused:
[One (M8) Android Development] Captain_Throwback:
The issue is Venom. It can't find your device variant so it doesn't install a boot.img. The MultiROM recovery was updated to reflect the proper device props in recovery and Venom apparently hasn't been updated to accommodate that yet, since that change hasn't made it into the official TWRP yet. If you add the correct value into the Venom ROM updater-script, I'm sure it'll install fine.

Not sure which GPE MM you're flashing, though. You could also have the lingering primary_boot.img issue depending on whether you were rebooting from any secondaries when you started making changes to your primary. I really would start from scratch - that's probably your best bet. And try flashing a ROM that uses the new asserts or update them yourself.
[One (M8) Android Development] thekwijibo:
First of all, thanks for the input and effort to help me figure this out, but I'll have to expose my inner-noobery. Correct value? Which value is that or how does one change that value? Would I have to monkey with the Venom installation script, or flash something post install? Or would I be better off flashing a different ROM?

I tried flashing [VZW Port] M8 Google Play Edition | Marshmallow 6.0 MRA58K.H9]

I'm not sure which ROM has the new asserts (as I'm not 100% sure exactly what that means), however if I could update them myself, that might be the best "catch-all". Can you steer me in the best direction on how I can do that?

Currently, after about an hour of playing around with Multirom and various fresh installs, I'm back to running Venom as my primary, and GPE as a secondary. However, whenever I switch ROMs, my phone goes back to Hboot. Then, after I select reboot, the previously selected ROM boots up. Seems like a wonky/unstable method, and I'd be interested on how to fix this properly.

Thanks!
[One (M8) Android Development] bazzi12:
Newer twrp and multirom builds in the thread work perfectly for me . Running ARHD 51.0 and CM13 as secondary. No issues at all
[One (M8) Android Development] Giblet-dono:
If I understand Captain correctly:

Venom rom should "ask" your recovery which variant of the M8 Hardware you are running (i.e.: Verizon, Sprint, ATT, International, Tmobile)

If you use the latest recovery from this thread (the one I linked one page back from captain) it (meanign the recovery) should contain the needed information.

Except that venom rom doesn't ask for this information yet and thus doesn't install (the correct) boot.img

To fix this, you could edit the venomrom updater script to manually tell it which hardware version you use..

The other thing you could do is manually flash the appropriate venom boot.img for your hardware

or you could flash a kernel with the kexec patch directly after flashing venom rom.

Now, the one thing I am not sure about: If I recall correctly, the venom aroma script ASKS which hardware version you have!

So I am not sure the above applies completely.. It should install the correct boot.img if you select the correct version in aroma

The version of venom rom you try to install, is it the same as the version you have installed (or backed up)?

If not: it MIGHT be a firmware issue
[One (M8) Android Development] thekwijibo:
Yeah, in the aroma installer it asks:

"Please choose your desired carrier tweaks (carrier-specific build.prop settings and other changes) If your carrier isn't listed below, select the Default one:"

Default

AT&T

T-Mobile-US

M8tl (China market)

My device is Verizon, and I've selected "Default" on all installs in the past.

My primary one I have backed up is 4.6.1, and the one I've been trying to install/reinstall is also 4.6.1. With how much trouble I've had with Venom on Multirom, I'm beginning to suspect it might just be a Venom issue or incompatibility. I have yet to be able to clean wipe/flash Venom using Multirom, in primary or secondary.

Today, I've done some more experimentation with Multirom's non-primary partitions to see if I can debug some other weird booting behaviors. Perhaps give those more clever than I some insight as to what might be happening, or how to fix:

Multirom - Venom 4.6.1

Boot - Fail - Goes into Fastboot

Fastboot - Reboot - Fail

Fastboot - Reboot - Fail

Fastboot - Hboot - Recovery - Recovery doesn't load but Venom boots instead. Venom flashes "no SIM" icon occasionally, and there is no cell/data signal. Unusable ROM.

Multirom - GPE Marshmallow 6.0 MRA58K.H9

Boot - Fail

Fastboot - Reboot - Fail

Fastboot - Reboot - Success.

Multirom - MIUI7 5.10.9 (replaced boot.img with Verizon supported version)

Boot - Fail

Fastboot - Reboot - Fail

Fastboot - Reboot - Fail

Fastboot - Reboot - Success.

(Actual number of reboots to achieve boot appears random. 3-5 times is "normal")
[One (M8) Android Development] nkk71:
Yeah, you misunderstood, he's talking about this