yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Giblet-dono:
So now that you have actually showed us your problem..

So the reason it's not officially supported is simply because the original maker of multirom (tasssadar) didn't make/port it to this device

It was someone from the community who did it...

So if you want it officially supported: Ship an M8 to tasssadar

The "port" was a collaboration between multiple devs and had a LOT of help from tasssadar himself

It works propely, but will never be official unless tasssadar get's an M8 and decides to develope multirom for it

Though it wont be much different from the current version!

Weird thing is.. I don't get the message.. so it could be that's it's still your rom that's ****ed up =D

As Captain already explained, it could be because your ROM is an M9 port, so it identifies itsself to the app as an M9 (instead of an M8)..

The App might not like that..
[One (M8) Android Development] eskimosound:
Well thank you for explaining it so eloquently without calling me.
[One (M8) Android Development] Giblet-dono:
Most people on these forums are actually out to help eachother..

Try to imagine the following:

A friend comes up to you and says: I have a problem with my phone

You say: well what phone is it?

and he says: a smartphone

Can you see how this information is totally useless cause it can still be a thousand types of phones?

So essentially the developers (and users) in this thread have the same situation..

We need to know exactly what your problem is, generic info won't help us..

And when we offer you a solution we expect you to try or research it..

The problem you have is, as explained multiple times, not a multirom problem at all!

So we expect you to reasearch for instance what modelname is in your build.prop

Or ask it in the appropriate thread...

Also, what's also been mentioned: this is a developer thread, is actually true..

A developer thread means that a certain level of "DIY" and udnerstanding are to be expected
[One (M8) Android Development] ckvisme:
It absolutely is a Rom issue.. As Captain already pointed out... The build prop reads as an m9... Which is not yet supported..

If you search back in this thread.., SkyDragon... Also an m9 port, had the same issue. Fortunately one of the SD team members made a flash-able zip to fix the way the Rom read... (MultiRom wasn't the only app that the ports build props mess with).

Also as you yourself already stated you shouldn't use SRom as your primary Rom (I don't think there is a compatabile kernel anyway)..

.. So why does it matter what the app says on SRom
[One (M8) Android Development] Captain_Throwback:
[MENTION=5480643]eskimosound[/MENTION]

Please post that full screenshot and logcat from you opening the app.

Everyone else - please let's quit the unnecessary insults and try to get this thread back on track.

But again, this is a ROM issue, not a MultiROM or app issue.
[One (M8) Android Development] Stephen:
Moderator information,

Thread has been cleaned. If you have an issue with a users post, do not reply to it, but report it and let the moderators deal with it. Do not start flame wars on threads.
[One (M8) Android Development] PunkUnity:
I've used multirom on many aosp and sense based roms without this issue. It is indeed your rom Eskimo, not the device.

---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------

Thanks stevie lol ?
[One (M8) Android Development] nkk71:
[MENTION=1162986]Captain_Throwback[/MENTION]

[MENTION=6402880]ckvisme[/MENTION] has noticed (and I can confirm) the TWRP_multirom_m8_20150819-01.img has a broken restorecon in MultiROM recovery.

extract from the recovery.log:

Running restorecon on ROM's /system
I:Running cmd "restorecon -RFDv /system"
restorecon: invalid option -- D
BusyBox v1.22.1 bionic (2015-08-19 23:38 -0500) multi-call binary.

Usage: restorecon [-iFnRv] [-e EXCLUDEDIR]... [-o FILE] [-f FILE]

Reset security contexts of files in pathname

-i Ignore files that don't exist
-f FILE File with list of files to process
-e DIR Directory to exclude
-R,-r Recurse
-n Don't change any file labels
-o FILE Save list of files with incorrect context
-v Verbose
-vv Show changed labels
-F Force reset of context to match file_context
for customizable files, or the user section,
if it has changed

more details here

And eventhough you're using omni repo, it seems the busybox you're using has that same problem.
[One (M8) Android Development] Captain_Throwback:
Last time I checked, recovery wouldn't build with Omni busybox on the android-5.1 tree. That's why I've been using CM busybox.

[MENTION=1238555]MassStash[/MENTION] [MENTION=5676253]fizbanrapper[/MENTION] Have you tried building without picking the CM busybox lately, and does it work for you?

P.S. When did I post an 8/19 recovery? I don't recall doing that - MassStash and fizbanrapper are posting the latest/up-to-date stuff now.
[One (M8) Android Development] nkk71:
Ah didnt know that, not following M8 much anymore, my bad :angel:

just saw your pull request with the new manifest, that's where i got the recovery from, but didnt check whose build it was, looks like:

ro.build.user=zaichron
ro.build.version.incremental=eng.zaichron.20150819.233403
[One (M8) Android Development] Captain_Throwback:
That's [MENTION=1238555]MassStash[/MENTION]'s build box ;).

The pull request is so that MassStash and fizbanrapper can have full control of updates to the MultiROM Manager app.
[One (M8) Android Development] nkk71:
yeah, only read back a few pages, didnt notice who was updating mrom :rolleyes::eek:
[One (M8) Android Development] Freak07:
Just install v4a as usual. And reboot back to your secondary rom
[One (M8) Android Development] Ather:
actually the problem i encountered with whatsapp was that i needed to re-verify my number on either ROM, the chats were actually being used from /sdcard/whatrsapp/database folder, but if i reboot lets say to sense, i'd have to reverify the number, but then later if i reboot to CM, i'll have to verify again...
[One (M8) Android Development] SammyTRK:
Is it safe to use the multirom manager app in the play store to install Ubuntu Touch?

Sent from my HTC One_M8
[One (M8) Android Development] Captain_Throwback:
I have a thread for a reason.
[One (M8) Android Development] manup456:
I wouldn't install ubuntu or try because we don't have it for our device.

You need to go into recovery advanced > multirom > ROM list > and select the ROM then you will see a option to flash .zip and away you go. The names could be a bit off in my instructions because I'm not looking at my recovery, but you will see it.
[One (M8) Android Development] Galaxysm:
do I use this method to install your recovery?

HBOOT Method*(S-OFF only)

Rename the file to exactly "0P6BIMG.zip" (no quotes)Place on root of (external)*SD cardBoot into HBOOT to flash (bootloader should detect zip automatically and prompt you to flash)
[One (M8) Android Development] SammyTRK:
Yea, I have 3 ROMs working right now. I was just hoping to try Ubuntu touch.
[One (M8) Android Development] Captain_Throwback:
There are 3 methods listed in the thread. Choose one.
[One (M8) Android Development] Galaxysm:
Im getting this?

Sent from my LG G3.
[One (M8) Android Development] Captain_Throwback:
Then use the "S-ON compatible" method.

EDIT: What is your model ID, so I can add it to future zips? Again, these questions belong in my thread, not here, as they don't relate directly to MultiROM.
[One (M8) Android Development] beats4x:
Any idea on the issue of second rom not booting? I let it sit for over 20 minutes after installing [MENTION=1162986]Captain_Throwback[/MENTION]'s twrp, still a no go ? I've used multirom on my nexus 5/7.2 and m7, definitely not a procedural error on my part
[One (M8) Android Development] Diddy555:
Try to go to recovery, reboot, see if it boots. For me it works but is kind of annoying...
[One (M8) Android Development] manup456:
You can also just pull the .img from the .zip put on your phone and use flashify app from the market.

---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------

This has happened to me a few times hard rebooting and re-trying usually it works. It's second and third for me not often.
[One (M8) Android Development] jake.99x3:
Extract it and find the recovery.img inside flash the recovery in fastboot using fastboot flash recovery (location of recovery)
[One (M8) Android Development] Galaxysm:
Thanks it worked :3
[One (M8) Android Development] manup456:
Just loaded 4th ROM all is well the app was getting stuck at points reverted to just using reboot option things got better.
[One (M8) Android Development] Giblet-dono:
This is not a problem with Multirom, it's a whatsapp problem, not actually a problem but more a limitation

To make sure someone else cant use YOUR Whatsapp account it can only be used on one phone.

The app sends the phone ID to their server and connects that to your phone number

A different rom has a different ID and thus you have to re verify
[One (M8) Android Development] daorderdillon:
Don't reverify number

---------- Post added at 07:34 PM ---------- Previous post was at 07:34 PM ----------

Use titanium to backup and restore it to other roms
[One (M8) Android Development] S1L3nTShaDoWz:
Alright, did as stated above for Verizon devices. Followed instructions in order using Throwbacks TWRP instead and the Elite Lunar kernel and then flashed the MultiROM zip in recovery and there is still no "MultiROM" option under > Advanced? When attempting to boot into my ROM it loads the MultiROM auto-load and lets me select my ROM (called 'Internal', default name) then boots into the main ROM but aren't I supposed to add the secondary/other ROM's via that section of recovery?
[One (M8) Android Development] Captain_Throwback:
Did you flash the correct TWRP?
[One (M8) Android Development] ckvisme:
[MENTION=2605798]nkk71[/MENTION] and [MENTION=1162986]Captain_Throwback[/MENTION]

I apologize

...it was MY lack of communication that caused the confusion.
[One (M8) Android Development] nkk71:
no problem, my mistake not checking whose build it was :angel:
[One (M8) Android Development] snebojsa:
I'm on Lee Droid 7.4.3 as primary and wanted to install Viper 4.5.1 as secondary. Installed ElementalX 4.0.5 on primary and multirom and recovery with multirom app, everything good. Then installed Viper as secondary, everything went well and rom booted, but have problem that no memory is recognized (internal and sd card), and have Google play store randomly force close (think that is related with memory is not recognized).

In Venom tweaks there is fix for this problem (because this is a common problem) but not working for me. I tried with adb command "adb shell su restorecon -FR /data/media/0" too, but that also not worked. Tried to reinstall rom with/without wipe but no good. Then I tried Andorid Revolution HD 43 (close to stock rom), but everything is the same, no sd card and internal memory recognized. Then I installed rom as primary and everything is good, memory is recognized properly like it should, so the problem is not in the rom.

Anyone have this problem and does anyone know how to solve it?

Thanks.
[One (M8) Android Development] nkk71:
I dont know which build you're using, but are you encountering this problem:

http://xdaforums.com/showpost.php?p=61307347&postcount=2530

(the unlabeled .layout_version will result in no sdcard)

if so the [MENTION=1238555]MassStash[/MENTION] and [MENTION=5676253]fizbanrapper[/MENTION] may wanna take a look at this: https://github.com/Tasssadar/multirom/pull/66
[One (M8) Android Development] snebojsa:
Yes, I think that's it. So, I didn't understand, can I do something to solve problem, or MassStash and fizbanrapper must do it?

How to mount secondary rom in twrp?

I did something and it worked.

In twrp/terminal emulator and run "restorecon /data/.layout_version"

then, run restorecon from multirom menu, and now sd card is ok.

Thanks.
[One (M8) Android Development] nkk71:
you could try the following:

TWRP->Advanced->MultiROM->List ROMs->select the one not working

then select Backup -> this will change the mount points, and you can then try

C:\ADB3>[B][COLOR="Blue"]adb shell[/COLOR][/B]

~ # ←[6n[B][COLOR="Blue"]ls -laZ /data/.layout_version[/COLOR][/B]
ls -laZ /data/.layout_version
-rw------- root root u:object_r:media_rw_data_file:s0 .layout_version

~ # ←[6n[B][COLOR="Blue"]restorecon -F /data/.layout_version[/COLOR][/B]
restorecon -F /data/.layout_version
SELinux: Loaded file_contexts from /file_contexts

~ # ←[6n[B][COLOR="Blue"]ls -laZ /data/.layout_version[/COLOR][/B]
ls -laZ /data/.layout_version
-rw------- root root u:object_r:install_data_file:s0 .layout_version
~ # ←[6n[B][COLOR="Blue"]exit[/COLOR][/B]
exit
[One (M8) Android Development] snebojsa:
I wrote at the same time with you.

Edited my previous post, resolve the problem, thanks.
[One (M8) Android Development] fizbanrapper:
New recovery is up now

And the MR zipfile to go with it

Though it is working very well for me, this is a test build. As such, please make sure that you have a current copy of your existing recovery image and multirom zip files of choice, prior to flashing. If you've been having issues with restorecon not functioning properly, the above should fix most of those issues. It's built with Omni's busybox repo instead of CM's.

Please flash the recovery (flashify or whatever) before flashing the multirom zip file.

Any problems? This is a test build! Logs please!
[One (M8) Android Development] snebojsa:
[MENTION=5676253]fizbanrapper[/MENTION]

I just installed new recovery and multirom zip you posted, delete existing secondary rom from multirom menu, installed fresh rom but the problem persist, no sd card...
[One (M8) Android Development] ckvisme:
After the SD card does not show up... Reboot to recovery go to multirom/secondary-rom-of-choice/run restorecon (swipe to confirm)...

Reboot and enjoy?

PS

You will also probably need to flash superSU update zip after
[One (M8) Android Development] fizbanrapper:
Yeah that's because [MENTION=3418703]Tasssadar[/MENTION] hasn't merged that pull request yet. The new build didn't fix that particular restorecon related issue. I'll keep an eye on it. If he doesn't merge it, I may just fork the repo and do it manually myself.

Until then you'll have to use the above mentioned workaround. Sorry.
[One (M8) Android Development] snebojsa:
Yes, I did it and it works, thanks.

Ok, thanks.
[One (M8) Android Development] nkk71:
you could just add those sections of the code to your file

https://github.com/Tasssadar/multirom/pull/66/files

and i may have an idea about the other issue (not entirely sure that's the reason, but could be), so lemme know where
[One (M8) Android Development] reaper420:
I finally decided to try multirom I installed the recovery and multirom zip fizbanraper recently posted and multirom manager. My problem is the manager says everything is installed and when I boot from recovery to the rom a screen pops up asking if I want to boot from internal, so I know everything is installed, but in the twrp advanced option I have no multirom option. Am I missing something I should have installed?
[One (M8) Android Development] ckvisme:
Do you have the materialised theme for TWRP?

If yes, make sure you get the MultiRom edition

If you don't, I would flashify the MultiRom recovery again...or you can do it from TWRP... as long as your using recent builds
[One (M8) Android Development] fizbanrapper:
If you flash the proper recovery image, you will have multirom option under "advanced".

If you don't see that option you're on the wrong recovery, no matter what the app is telling you.

Please let me know if you still need help
[One (M8) Android Development] reaper420:
Thanks, I never even considered the theme was the problem. I've been using it for so long I forgot it was just a theme. I deleted it and it's all the way it should be now
[One (M8) Android Development] ckvisme:
Lol, yep... You r not the first?

I use the theme too and have set up the incorrect version b4... DOH!
[One (M8) Android Development] reaper420:
I'm sorry for the stupid questions but I'm trying to install a secondary rom now to the SD card is that what the /dev/block/mmcblk1p1 (vfat) option is?
[One (M8) Android Development] Captain_Throwback:
Yes, but that won't work. You can only install ROMs to an ext4 partition on the external SD (well, you can install them to vfat on external, but they'll never show up in the MultiROM boot menu).

EDIT: [MENTION=5676253]fizbanrapper[/MENTION] has reminded me that vfat works fine, It's just exfat that doesn't. Sorry, my bad. That'll work fine.
[One (M8) Android Development] Mjduddin:
Does anyone have a kernel for CyanogenMod 12.1 Snapshot with Kexec built in? I've looked and haven't found anything yet.
[One (M8) Android Development] PunkUnity:
You can use candy kernel, blackbird kernel, and I have a boot.img I made from slim kernel that has Kexec...
[One (M8) Android Development] and.u:
Hi guys, can you please help me? I want to install it on my htc one m8. It has already a sense 7 android 5.0.2 rom (s.rom) and i want to have also cm 12.1. Can i do everything with the app from the playstore?? Even if i'm not s-off?? Thank you so much
[One (M8) Android Development] ckvisme:
Last time I checked S.Rom doesn't play very nicely with MultiRom but if you make a NAND of SRom and flash CM

(after CM you need to add a kernel with Kexec hard-boot patch for MultiRom support)

You can then setup via the MultiRom manager app on CM and then add S. rom as a secondary (via backup option)

And no S-off isn't needed for this?
[One (M8) Android Development] and.u:
OK man. So after intall cm and gapps I have to flash a kernel that support kexex hard-boot (which one do you suggest me?) And then restore the backup of s.rom. right?

Inviato dal mio HTC One M8 utilizzando Tapatalk
[One (M8) Android Development] ckvisme:
Yes exactly correct.

It really doesn't matter... There are several roms with kexec now... Candy is a common one... If you know where to look [MENTION=5676253]fizbanrapper[/MENTION] has a new boot.img you can use that has 30 some different governors (if you like to play with kernel settings). [MENTION=4983354]PunkUnity[/MENTION] also has a really good boot.img that includes kexec.

You can also copy the boot.img out if any Rom that has kexec support and flash that.

You only need the kexec support on the internal (primary) Rom... Your secondaries do not require it
[One (M8) Android Development] and.u:
Thank you! Now I'm downloading candy 5 than install multyrom from the app (or is better doing by my own?)

Inviato dal mio HTC One M8 utilizzando Tapatalk
[One (M8) Android Development] ckvisme:
Go ahead and set up with the app... If you look back through the thread there are a few known issues but easy to work around and I think it won't be long before there is another update to the app.

What's your carrier?
[One (M8) Android Development] and.u:
TIM, I had an international m8 model, using s.rom the app says this..

Inviato dal mio HTC One M8 utilizzando Tapatalk
[One (M8) Android Development] ckvisme:
I there is not a kexec kernel compatabile with SRom AFAIK

And most sense 7 ports are going to tell the MultiRom app that you have an m9 instead of an m8... You can flash them but probably not as primary
[One (M8) Android Development] and.u:
hey man please help me...i did everything...flash candy5 rom and then intall multyrom form the app...entered in the recovery and install from backup the sense rom but now are passer about 20 min with the sense boot screen...what swould i do?????

can i restart it?? Just in case, for uninstall multyrom i have just to flash the uninstaller file and then everything is done, right?
[One (M8) Android Development] fizbanrapper:
If you're s-on, you'll have to flash the boot.img after flashing the ROM.
[One (M8) Android Development] and.u:
ok man, but i can't turn off the phone...how can i do???
[One (M8) Android Development] ckvisme:
Umm... Huh?

Lol, what do u mean you can't turn it off?
[One (M8) Android Development] and.u:
OK man I finally turn off...but how to flash the boot IMG? Just put into the SD card and flash via fastboot?

Inviato dal mio m8 utilizzando Tapatalk
[One (M8) Android Development] izzaeroth:
You can put it in your adb folder. Open a terminal, cd to adb folder. Put phone in fastboot mode and type: fastboot flash boot boot.img
[One (M8) Android Development] and.u:
The last question now, i swaer: for uninstall the multirom how can i do??
[One (M8) Android Development] izzaeroth:
There should be an uninstall file you flash
[One (M8) Android Development] fizbanrapper:
You're only having these troubles because you're s-on. Get s-off and you can run as many ROMs as you want, without issue
[One (M8) Android Development] MassStash:
Update Time!

Multirom Installer 2015-09-18-v32-Unofficial-M8

TWRP MultiRom M8-2015-09-18

Changelog: Got some stuff fixed, let me know what works better! haha
[One (M8) Android Development] ckvisme:
Install errored with Desolation as primary (then I remembered)... So I restored Pac as primary and it installed without any issues...

[G-Drive Logs

i will let you know how it gets along... Glad to see you back Mass!
[One (M8) Android Development] MassStash:
lol nice. Let me kno man, I'm too busy to flash a bunch of ****.

This just in! app updated! Yaaay. Test out, make sure working. Peace.
[One (M8) Android Development] ckvisme:
Haha, look at u go! OK, 9_18 seems good now, I'll update to the new one from the app
[One (M8) Android Development] sym_m:
hi guys i am new here can i install it on s-on ? i use sd 10.2 rom
[One (M8) Android Development] nkk71:
any details :D
[One (M8) Android Development] ckvisme:
Hey [MENTION=1238555]MassStash[/MENTION] I'm getting mount errors after flashing the recovery from the app...it was flashing Bliss pop as primary and recovery crashed and not looped...

I flashed back go the 9~18 recovery u posted and booted back to Android.

When I went back to recovery same errors.

Here are the recovery logs I grabbed.

https://drive.google.com/folder/d/0B8bG_OajnI4gVkdZZGprMlZFeEU/edit
[One (M8) Android Development] Captain_Throwback:
You haven't recently flashed any firmware, have you? Try going into fastboot mode and doing a "fastboot erase cache" and see if that fixes the cache mounting errors.
[One (M8) Android Development] ckvisme:
Actually yes, the 4.25.651.14 RUU then I updated to 4.25.651.18 via OTA but it mis-behaved (wouldn't boot HTC official rom) and it was a useless update anyway so I RUUed back to 4.35.651.14 . I only run custom roms anyway so I don't need HTCs stagefright stuff...

Anyway I ended up formatting internal SD (had to repair cache file system first) and that cleared it up
[One (M8) Android Development] Captain_Throwback:
Yeah those errors were definitely caused by the failed update, then. Unrelated to MultiROM and TWRP.
[One (M8) Android Development] ckvisme:
OK after formatting internal SD and flashing the installer zip and recovery via the MR app today I flashed Bliss and Pac (both today's builds 9_22) and both failed to boot past "this is a dev build" splash screen.

I tried restorecon and fixing file permission on Bliss... No change...

Odd because I had used the 9_18 MultiRom that Mass posted with no issues... And this 9_20 build yesterday for Flash some roms without problem

*recovery.logs from Bliss and Pac

https://drive.google.com/folder/d/0B8bG_OajnI4gQnBlZnAxbWhWRjg/edit

TIA
[One (M8) Android Development] Captain_Throwback:
Maybe you should try running the latest RUU, booting that up, and then installing MultiROM and flashing whatever ROMs? I'm wondering if your system is still in an unstable state from the failed upgrade.

After looking at the logs, I'm really not sure what the issue is, though I'm not really sure what I'm looking at :rolleyes:. Have you tried adding the boot.img from the ROM to the ROM in the MultiROM settings menu? if you navigate to /data/media/0/multirom/roms, are the ROMs there, with the boot.img and boot, system, cache & data folders?
[One (M8) Android Development] ckvisme:
I have not.. But I will try it.. And check out the file manager in recovery... Thank u
[One (M8) Android Development] MassStash:
How'd that go?