yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] ckvisme:
Well, adding the boot.img didn't work (I was a dumbass and 4got to try with the boot removed)

The roms are listed under dara/media/0/multirom

But I tried to flash Bliss as primary (full wipe oc) but recovery crashed during install and just kept booting to the "this is a dev build " splash screen... I could force it to bootloader but recovery just kept crashing... So I pulled SD card relabeled an older bootloader flashable MR Recovery that I had been using and flashed it via bootliader

Got recovery back up, hit inject curr boot sec and bam the Bliss I had flashed as secondary booted up just fine.... Very very odd..

But my PC is down ATM and I had to flash recovery again to get it together again so I wasn't able to get any kind of log.... Which really sucks ass

I re_updated to the 9_22 recovery from from the app and all is working again... So... Maybe Captain was right and there was/is so junk causing errors...

I am still getting unknown file system error ever time I flash a zip... Although it doesn't seem to cause any actual problems
[One (M8) Android Development] Captain_Throwback:
That's from a recent commit/patch - that should be easy to fix.
[One (M8) Android Development] fizbanrapper:
You should see the 9/23 build in your app. This addresses the fixes mentioned by [MENTION=1162986]Captain_Throwback[/MENTION].

I've also posted a new 9/24 test build for those of you who are in the M8 MR testers hangouts. See the hangouts for links and a change log for what's in the 9/24 build, but not in the 9/23 build. If you wish to join the hangouts group, just send me a PM.
[One (M8) Android Development] radeon_x:
Hypothetically, what would happen if you were to enable encryption on a secondary ROM?
[One (M8) Android Development] Captain_Throwback:
Only one way to find out - let us know how it goes.
[One (M8) Android Development] dopy25:
Not sure about what would happen, but theoretically; it should basically encrypt the folder that rom is stored in. Since the roms mount points are changed to that specific folder at boot, I can't see it changing anything other than the folder that rom is stored in and any subsequent files in that rom considering the folders are dynamic if on an ext partition.

If the rom has it's own img, then I assume it would encrypt that img. This might be a good question to consult the official developer on because what is done here is using his sources as well as very slight modifications, but usually only to the kernel using the kexec hardboot, from what I understand.

On that note, I think if it would be detrimental to the device or other roms, it would be identified in the OP.
[One (M8) Android Development] nkk71:
try and find out... though i do believe that encryption is supposed to encrypt the entire userdata partition, not the only the .... hmm not sure what to phrase that, as /data/..... and /data/media .... and /data/media/0/multirom are actually located in the same partition

happy hunting :eek:
[One (M8) Android Development] radeon_x:
Does anyone actually know if encryption on the M8 encrypts the /data/media (aka internal SD)? I can't find a straight answer...
[One (M8) Android Development] nkk71:
encryption has nothing to do with "/data/media/...." (aka, not known as internal SD)

I would highly encourage you to be careful,

encryption is/should/will encrypt your entire partition (aka p47 or whatever is userdata is on the m8), that includes

everything

) not just what you would like it to be
[One (M8) Android Development] radeon_x:
Ahh yeah, sorry - just checked the partition list. I thought that /data and /data/media were separate partitions for some reason.
[One (M8) Android Development] EZY-E:
Rom can't boot

Ok, I was on ViperOne rom, installed multirom app from play store, installed multirom, installed beyond stock kernel from multirom installation, restarted phone, phone went to multirom selection screen, booted internal boot only homescreen was shown without background and it immedietly restarted, again it boot to homescreen and restarted.

Then I flashed elementalx because I thought it was because I selected to install beyond stock recovery, kernel was installed, option for injecting - Inject curr. boot sector to multirom was shown, I selected it, and now when I boot rom only ViperOne boot screen is shown and it stays like that, help PLEASE.

EDIT: Now I uninstalled multirom with uninstaller file, still can't boot ViperOne :(
[One (M8) Android Development] Captain_Throwback:
Which BeyondStock Kernel did you install?

It sounds like your issue is an incompatible kernel, not specifically related to MultiROM.
[One (M8) Android Development] ckvisme:
Restore you NANDroid backup and it should be fine.

If you want to set up multirom it works better for me to start with an AOSP Rom ...there are a few out there that have the kexec hard-boot patch build in.
[One (M8) Android Development] Captain_Throwback:
Though it *should* work fine with any ROM with a compatible kernel. I've personally only ever used Sense and GPE ROMs as primaries and not had any issues.

If the ROM doesn't boot after uninstalling MultiROM, then MultiROM isn't the issue. The user just needs to make sure the selected kernel is the proper one for the ROM being used. MultiROM won't prevent a primary ROM from booting.
[One (M8) Android Development] EZY-E:
The one that was offered in multirom app.

Now I installed ElementalX again but it still hangs on booting.

Maybe to try dirty flash ViperOne?
[One (M8) Android Development] Captain_Throwback:
Again, which one from the app? I'm thinking you didn't look closely at the description of the kernel you installed.

Dirty flash might work.
[One (M8) Android Development] EZY-E:
I don't remember what version it was :/
[One (M8) Android Development] Galaen:
Dirty flash the rom. Otherwise, clean flash.
[One (M8) Android Development] EZY-E:
Huuuuuh! Yes! Dirty flashed and everything is fine now, thanks everybody :D
[One (M8) Android Development] fizbanrapper:
The easy way to fix this is to have viper as a secondary ROM on your internal or external sd (I recommend internal).

Then you can flash any kernel with kexec patch, to your primary boot partition. If you do it this way, you don't have to touch the kernel you're using on viper because secondaries don't need to be patched.
[One (M8) Android Development] Captain_Throwback:
The only reason I don't recommend using Viper as a secondary is because, like all Sense ROMs, it is RAM-intensive and resource-heavy. There will be some slight performance loss as a secondary ROM and that can become really bad if using a Sense ROM as such. I'm actually having some lag issues on my stock rooted ROM on a device that doesn't even use MultiROM, lol, so I can't imagine it would be any better as a secondary. But, as always, ymmv.

The two BeyondStock kernels in the MultiROM app should work fine on either stock Sense or GPE, but the user obviously has to select to appropriate version for the ROM they're using (which I think, ultimately, was the issue in this case).
[One (M8) Android Development] Galaen:
One should note that the newest viper rom is a port from the m9. Even elementX had issues working for some. Those individuals had to put viper's ram disk in the kernel zip, or kernel, or however that works. So, that may be the case for BeyondStock, or as you said, the wrong version was used.
[One (M8) Android Development] Captain_Throwback:
BeyondStock doesn't replace the ramdisk. If it (the M9 port) uses some custom kernel, that's a different story.

EDIT: If the port does use a custom kernel, it would just need to be updated with kexec-hardboot support.
[One (M8) Android Development] snebojsa:
I am using Viper as secondary and didn't noticed any performance loss. My primary rom is also Sense rom. One thing, as both roms are on internal memory, it is almost full.
[One (M8) Android Development] gimpchop:
Hi I looking for patched kernal that will work for the latest viper one rom. Is there one that works thabks
[One (M8) Android Development] snebojsa:
Try ElementalX.
[One (M8) Android Development] MrCancela:
Helo, I have an M8 ATyT S-ON and rooted device, with Google Play Edition Android 5.1. I installed MultiROM but when I try installing a second ROM to external SD TWRP shows in red letters:

E:mount -o loop ext4 /mnt/multirom-m8/cm-12.1-20150901-SNAPSHOT-/cache.img /cache process ended with ERROR=255

E:mount -o loop ext4 /mnt/multirom-m8/cm-12.1-20150901-SNAPSHOT-/data.img /dataprocess ended with ERROR=255

E:Failed to mount image /mnt/multirom-m8/cm-12.1-20150901-SNAPSHOT-/data.img!

I will appreciate if someone can help me. Thanks
[One (M8) Android Development] Bubbadogg14:
How are you able to fit both ROMs on your internal memory? I have SD 10.2 as my primary and intalled bliss as my secondary but ran out of space before most of my apps were restored.
[One (M8) Android Development] Shamestick:
Just depends on how much space you've got available really.. I've run 2 sense and 3-4 aosp at the same time in the past. I usually have 15-20 gigs available though
[One (M8) Android Development] snebojsa:
I don't have many apps installed, maybe 15 or so (no games), same apps are in both roms, so I have about 600mb space left now. If you have more apps (large ones) you will run out of space, and only solution is to try to install secondary on external memory (I didn't try that).

My phone is WWE (Europe) variant and have 16GB internal memory, maybe you have other variant with more internal space.
[One (M8) Android Development] Voklav:
Till now i have been using multirom with two roms IN internal memory...

Now i want to try secondary rom installed on SDcard.

But no luck.

Any advise and suggestions ?
[One (M8) Android Development] ckvisme:
Have no clue what you tried or what roms u have set up with what MultiRom version

But at a guess I'd say you need to format ur SD card and make a separate partition for roms to boot from... I use ext4 (20gb on my 64 GB micro SD card)
[One (M8) Android Development] Voklav:
Windooooows .... May be ...https://plus.google.com/communities/114053643671219382368
[One (M8) Android Development] wiQbold:
the Q&A thread isn t up2date so sorry that I ask here.

but my bootmenu is freezing if I wan t to change to CyanogenMod!?

I made the "restorecon", one time it helps but not twice? now it hangs in bootloop on cm.

wiped dalvik & cache but bootloop stays

my m7 and Shield tablet haven t had this problem, thats why I can t help myself!? it is frustrating

Internal - ARHD 43.0 / ElemantalX m8 v4.05 sense / multirom v32 / TWRP 2015-09-23 (H/K Mod if that is important) and renamed it to ARHD-43.0

2nd Internal - Cyanogenmod-12.1

so is the kernel not useable?

did I have to use the "Beyond-Stock" one!?

How could I made a log of the startup!? could someone guide me, please? adb logcat isn t working
[One (M8) Android Development] ckvisme:
Try removing the boot.IMG from your cm secondary rom , then try to boot it.

(You can copy the boot.IMG out of the ROM zip and add it back into the ROM later if you want...it should still boot)
[One (M8) Android Development] serseri22:
hi any chance can you tell me how u install rom to sd card coz I tried it but multirom manager not seeing the rom it just showing internal rom thank u...
[One (M8) Android Development] Captain_Throwback:
MultiROM Manager doesn't show external ROMs. You boot them from the External tab of the boot menu, provided they are either 1) installed on a vfat-formatted card (i.e. FAT32) and not an exfat partition, or 2) installed on an ext4 or f2fs partition on the external SD.
[One (M8) Android Development] wiQbold:
Thanks.

did not worked. but after I installed cm again it boots.

then I deleted the boot.img of CM again and it hangs in bootloop.

but I could get a logcat.

I only renamed logcat.txt to xxx.zip

then I did a dirty flash over CM again and it boot. did a restart and it boots.

then I changed to internal and tried after another reboot to change to CM.

then bootmenu freezes.

hardreboot and done a restorecon over recovery and tried again.

result bootloop.
[One (M8) Android Development] Captain_Throwback:
Since your main ROM is Sense, removing the boot image from your secondary ROM (CM) will always result in a failed boot. Just flash CM again as a secondary (or add the CM boot.img to the secondary ROM directly) and it should be fine.

Removing the boot.img is only appropriate if your secondary ROMs are the same type (Sense, GPE, AOSP) as your primary, meaning all of the secondary ROMs without a boot.img will boot using the primary ROM's boot.img.
[One (M8) Android Development] wiQbold:
yeah. I did flashed it again, that is the second logcat. there are many mistakes by xposed. can this cause the problem of bootloop?

oh I see there is no other logcat.. I ve edited the post. the file is on pc at work..

here is a new one. also renamed
[One (M8) Android Development] Captain_Throwback:
Have you tried it without Xposed? If it works, there's your answer.
[One (M8) Android Development] wiQbold:
yes it is without xposed. but problem stays.

if I install cm again it will boot directly into it.

you can reboot it without problem.

but if you change to internal and than back to cm the boot menu freeze and you have to hardreset and do a restorecon.

than cm hangs in bootloop. (the last logcat)

the internal boots without any problem.

the inrernal rom I ve renamed to "ARHD-43.0"
[One (M8) Android Development] Captain_Throwback:
No idea on any of that. I'll have to defer to the people that use CM and are actively developing on this. I can boot into secondaries with no issue.
[One (M8) Android Development] reaper420:
I'm having an issue, I have been using multirom for a while now and have never had this problem. When I reboot the phone and it gets to the MultiRom screen where I can choose which rom I want to boot into, I can't pick anything I just have to wait for it to boot to the internal rom. When in in the internal rom I can still use the MultiRom manager to boot to a secondary rom but I can't from the initial boot screen. If anyone knows what's wrong and how to fix it, I would appreciate any help.
[One (M8) Android Development] wiQbold:
cool. yes within the multirom app it worked to boot cm. thanks

If I slide at the top of the freezed bootmenu I can select sometimes the entries
[One (M8) Android Development] ckvisme:
The s4 has a similar issue if you use touchwiz roms as primary.

Try using a cm based Rom like Pac for your primary.

---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------

Ok, I don't remember. You ha e a sense rom as primary?

First try a CM based roms as primary like I said in the previous post (i use Pac usually) .
[One (M8) Android Development] wiQbold:
but with my M7 there is no problem with arhd as internal. I don t want to loose my running sytstem.. or media specific things..

Gesendet von meinem HTC One_M8 mit Tapatalk
[One (M8) Android Development] Captain_Throwback:
Your kernel isn't fully MultiROM compatible. Talk to your kernel dev and have him/her update it.
[One (M8) Android Development] wiQbold:
so the beyond stock one is the better choose?
[One (M8) Android Development] Captain_Throwback:
Sorry, my reply wasn't to you. Quotes aren't working in Tapatalk currently. I already mentioned that I don't have any further input on your issue, as I don't use CM.
[One (M8) Android Development] wiQbold:
but he descripes the same problem in few things?

freezed bootmenu and start secondary rom over app is ok

for me it helps if I slide at the top of the screen and after a while my thouches will recognized, in the multirom bootmenu.

i have "keypressed" selected to start the multirom bootmenu.
[One (M8) Android Development] Captain_Throwback:
If the issue is that when you have CM as your primary you can't select a ROM from the boot menu, then yes, you need a fully compatible kernel. I can't tell you where to get one for CM. I don't build CM.
[One (M8) Android Development] ckvisme:
Candy, BlissPop both have kernels with Kexec out of the box.

Also Fizbanrapper has build some with MultiRom support as well
[One (M8) Android Development] Jyotirdeb:
Can we use other device rom ie like samsung roms etc ?:confused:
[One (M8) Android Development] Giblet-dono:
Only if they are ported to the M8

Multirom only boots roms specifically meant for the device you are using it on!
[One (M8) Android Development] Power user:
Thank you so much for this guide and all the work!! You guys are really amazing, thanx again!!!!!
[One (M8) Android Development] gjrscribe:
Issue on GPE VZA M8 ROM

Hi Captain Throwback,

I tried your kernel on a M8 vzw GPE rom...It made it so that there was no touch interface UI reaction after reboot. Tried a flashing a few times. Turns out I wasn't the only one experiencing this. What's strange is that the kernel worked for a short time and was amazing (especially on battery) but then upon reboot, no touch action.

any thoughts? would love to use your kernel again. thanks!
[One (M8) Android Development] ckvisme:
I would try to grab some logs... If others have had this same symptoms, but no resolution then he is probably been unable to replicate the issue leaving no way for him to find the possible problem.

Also there are several m8 variants out there so be sure to leave some device, Rom and flash step info whith any logs you post for best chance at isolating causes.
[One (M8) Android Development] Giblet-dono:
Still loving Multirom, and whilst I have answered questions in the past, I am now beat for an answer to one of my own.

I suspect the question has already been answered and I think I even recall the answer, but I can't find it trough searching.

Was there a way to change the icons of secondary roms that are located on an ext4 partition on the SDcard?

I suspect the answer is, because they are not visible trough the app.

But is there another way? changing them trough recovery? or even changing them trough some kind of config file?

Thanks for any and all help
[One (M8) Android Development] Captain_Throwback:
I have changed them by changing the icon of a ROM I can change to the icon I want for the secondary on my SD card. Then, in recovery, I mount SD-Ext and copy that icon to the folder for the ROM I want it for. When I reboot, that icon *should* be set for the secondary ROM. I've noticed though that icon seems to randomly reset for unknown reason, though. If someone could figure out how to modify the app to look at external ROMs, that'd be ideal.
[One (M8) Android Development] TarekElsakka:
It seems that MultiROM works fine unless you use a secondary that has an AROMA installer, right? I have tried to install several GPE secondary ROMs which use AROMA but none of them worked whereas installing an AOSP without aroma works just fine. And if so, does anyone know where I can find a GPE ROM without Aroma installer? My main ROM is stock, rooted Sense 6 (5.0.1).
[One (M8) Android Development] Giblet-dono:
It's probably not Aroma, it's probably GPE roms that don't like being installed to a secondary slot.

What I did to get my GPE Marshmallow rom working is:

Backup primary (Venom)

Install GPE to primary

Backup primary (GPE)

Restore Venom to Primary

Restore GPE to secondairy

Swapping might also work:

Backup Primary

Install GPE to Primary

Swap it to Secondary

Restore Primary

It could take some time, mostly dependant on your SDCard speed.

But get's you a fully working GPE secondary rom!
[One (M8) Android Development] snebojsa:
I have two roms, Lee and Venom, both have Aroma installer and I have no problems in multirom, so Aroma is not a problem.
[One (M8) Android Development] dopy25:
[MENTION=1240955]TarekElsakka[/MENTION]

And anyone else interested. Aroma is technically the issue. When selecting reboot from within the aroma, it does not remount multirom points. Any time you install via aroma, do not let aroma reboot. Choose no. Let it go back to recovery and finish up the script, then back out and reboot system.
[One (M8) Android Development] Giblet-dono:
I had some time today to test this and it works pretty well!

Except exactly as you described, sometimes they just dissapaer
[One (M8) Android Development] TarekElsakka:
Thank you for the information. I followed your steps and it worked, however I was facing problems with the SD Card. The Marshmallow ROM seems to have changed the external SD card's format or something and it became only readable on both the Sense and GPE sides. When I booted up Marshmallow it gave me an option to use the external SD card either as part of the internal storage or another option, and I chose the latter one so I don't understand what happened.
[One (M8) Android Development] Giblet-dono:
This is not as much a problem as a feature ;)

Then again, I do see how it can be problematic, and thus I have not used any of the two options when I installed my GPE rom..

The trouble is that there is no real way to undo the damage, as in: you are not getting your data back (easily)..

You can however reformat it in your pc or in recovery and use it again as a "normal" SDcard..

I just checked an, after NOT makign a chocie it doesn't bug me about it again and I still have my SDcard as a regular SDcard, no re-formatting of sorts
[One (M8) Android Development] nkk71:
get rid of this part in the updater-script:

...
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "30,0,32770,32833,32835,33347,65535,65536,65538,98304,98306,98369,98371,98883,131071,131072,131074,163840,163842,163905,163907,164419,196607,196608,196610,229376,229378,229441,229443,229955,236205") == "d783413ceb8f7be9b9f37d3823a538bf1391db79" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "36,32770,32833,32835,33347,65535,65536,65538,66050,97792,98304,98306,98369,98371,98883,131071,131072,131074,131586,163328,163840,163842,163905,163907,164419,196607,196608,196610,197122,228864,229376,229378,229441,229443,229955,236205,236717") == "0d32630ef45efe48ee1ed19e40dbebdecbc50bd9" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
...

EDIT: just to elaborate:

range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system"

checks the entire system partition, much of which is already described here by CaptainThrowback, about block based OTAs

since MultiROM, doesnt actually use a "full partition", this check will always fail, remove it and it should flash fine.... the bad thing is, that future OTAs (etc), which also rely on "full partition" checks will fail
[One (M8) Android Development] dopy25:
Worked like a champ! Thank you.
[One (M8) Android Development] whytry23000:
I've been running multirom for a while and haven't had any problems. I just downloaded the new ViperOne and when I go to flash it, it begins installing, but then the installation fails every time. I'm running cm 12 with candy kernel as primary, and I have the most recent recovery and multirom updates. Can anyone help?
[One (M8) Android Development] whytry23000:
http://pastebin.com/QKruvrd1
[One (M8) Android Development] Captain_Throwback:
Flashing ZIP file /external_sd/M8/ViperOneM8+4.6.1.zip
ROM: ViperOneM8+4.6.1
Preparing ZIP file...
rm: can't remove '/tmp/mr_update.zip': No such file or directory
I:Running cmd "mkdir -p /tmp/META-INF/com/google/android/"
[B]I:ZIP size limit for /tmp: 410.19 MB[/B]
I:Modifying ZIP /external_sd/M8/ViperOneM8+4.6.1.zip in place, gonna restore it later
I:Running cmd "cd /tmp && zip "/external_sd/M8/ViperOneM8+4.6.1.zip" META-INF/com/google/android/updater-script"
[B]zip I/O error: No space left on device[/B]
zip error: Output file write failure (write error on zip file)
rm: can't remove '/tmp/mr_update.zip': No such file or directory
Erasing incomplete ROM...

Run out of space?
[One (M8) Android Development] whytry23000:
I saw that, and I checked my space. I've still got 12 gigs of internal space (where I'm installing the rom) and 2 gigs on my sd card (does this matter since I'm installing the rom internally?).