yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] thisguysayswht:
OK, so I have had some strange first experiences.

First off, I'm using a Verizon M8, s-off, boot loader unlocked, super cid, and I'm on the latest firmware for Verizon. My primary ROM is digitalhigh's gpe ROM, with the latest lunar kernel. I used the multirom manager app to automatically install the multirom recovery, and multirom .zip.

Now the strange stuff. I am trying to setup viper one as my secondary ROM, when adding it as a secondary ROM I got an error about the .zip being to big, and that it was getting modified, and would no longer work outside multirom. After it got done flashing, and rebooted, I selected viper one and was greeted with a black screen for about 30 seconds, then it showed the splash screen, and started my primary ROM's boot animation, about 10 seconds into the primary ROM's boot animation, the boot animation froze for about 5 seconds, then rebooted to the multirom screen. I then tried to boot viper again, with the exact same results. I then booted my primary ROM and everything went fine, primary was unaffected.

I'm experienced with multirom (I use it on my nexus 7, and used to use it on my nexus 5), and have never experienced such things.

Now please note, I'm not complaining, or asking for a fix. I greatly appreciate all the work that has been put into this. I'm just wondering if anyone else has experienced the same issues or if I'm doing something wrong. This is the first non nexus android device I have owned, and its very likely that I'm doing something wrong, or that viper one isn't compatible with multirom.

If anyone can recommend me a sense based ROM that they have been able to boot as a secondary in multirom (on a Verizon M8), for trouble shooting purposes, I would greatly appreciate it. Also if there's any logs I can capture to help pinpoint the problem, please just let me know how to capture them, and I will gladly upload them.
[One (M8) Android Development] manup456:
Have you flashed a patched kernel with the rom?
[One (M8) Android Development] thisguysayswht:
Yes, the latest lunar kernel has the kexec-hardboot patch (according to the lunar thread, and the multirom application picked it up as compatible). Should I try a different primary kernel? Or do you mean on secondary, I haven't tried flashing a kexec kernel on the secondary ROM.

---------- Post added at 06:35 PM ---------- Previous post was at 06:14 PM ----------

Thanks man, just flashed the sense version of the lunar kernel over viper one, and it booted. Makes perfect sense that they can't share kernels, gpe and sense kernels are incompatible, duh, lol. Thanks again. You rock :highfive:
[One (M8) Android Development] remicks:
Sorry for the delay on this, long night. This list pertains to the Verizon M8 and may not apply to your M8.

My list of roms able to be flashed as secondary roms without issues:

CM11

AOKP

Nameless

Plain-Andy

PA

AICP

List of roms not working at all as secondary:

LiquidSmooth

Beanstalk

List of roms working using swap method:

ViperOne

InsertCoin

Renovate

CleanROM

BoneStock

SkyDragon

Stock Rooted 4.4.3

Please note that I haven't tried to flash many sense roms as secondary because most use a hard mount method to mount the partitions during install which will cause issues with multirom.

I will most likely expand on this list and make a dedicated topic for it when I have time. Hope this helps a few people.
[One (M8) Android Development] reubenskelly1992:
Liquidsmooth is working for me in the first slot:)
[One (M8) Android Development] remicks:
Yep so does Beanstalk, but not as secondary unfortunately :(
[One (M8) Android Development] jcrompton:
Yes ... I think ... that is what they were saying

Liquid installs fine as secondary but the radio (WiFi nor phone) work. But if swap to Primary then it works fine
[One (M8) Android Development] manup456:
MoKee ROM also works as secondary have not tried as primary.
[One (M8) Android Development] remicks:
Thanks for the heads up, will add that to the list when I make the topic :)
[One (M8) Android Development] donmarkoni:
All working. :)

Renovate wouldn't install as secondary, had to be swapped. [MENTION=2928662]task650[/MENTION]'s AOKP didn't have any signal (Wi-Fi, mobile dat, etc.) until custom kernel installed.

Cheers guys!
[One (M8) Android Development] Captain_Throwback:
I was able to use Viper as a secondary back when my device was working. That and my stock rooted for Sprint both worked.
[One (M8) Android Development] TheBurgh:
Very helpful. Did you do anything special to get AICP to flash as a secondary? I cannot get past the boot screen. I am wondering if it has something to do with the 4.4.2 gapps in their thread.
[One (M8) Android Development] remicks:
I only use pa_gapps packages with any aosp rom. Pico is my personal favorite.
[One (M8) Android Development] anthony92170:
Any idea why this happens in primary I am on Sprint trying renovate rim 4.5 I even tried changing kernels.
[One (M8) Android Development] fen0m:
Vanir was fine as a secondary also
[One (M8) Android Development] donmarkoni:
I was intrigued by the way you said what you did, so I tried it myself. :D

Indeed ViperOne fails to boot as a secondary after installing. It's caused by installer script not allowing to exit without reboot, which hinders MultiROM from doing it's stuff. After flashing any zip, while leaving checked to inject MultiROM, it will be done and ViperOne will boot as a secondary.

Cheers! :cowboy:
[One (M8) Android Development] drewopo77:
Not sure if I did something different during install. But I have cleanrom running as a secondary Rom without haveing to swap to get it to work. I have viper one as primary
[One (M8) Android Development] Captain_Throwback:
Right, any ROM that wants to automatically reboot at the end of install, you have to say no to. Just uncheck the reboot option at the end of the install or choose the "No" option when asked to reboot by AROMA. If you don't do that, MultiROM won't be able to inject itself into the boot.img properly.

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

The ROM devs must've changed the ro.product.device entry in the build.prop to what you see in your screenshot. It should be "htc_m8whl." It's probably just a typo. Fix that and the device should be detected properly.
[One (M8) Android Development] krazyace35:
Anyone know why I am getting this message "WARN: modifying the real ZIP, it is too big! The ZIP file is now unusable for non-MultiROM flashing!" I have searched for an answer but only found this question posted along with 2 other questions in the Nexus forum talking about Ubuntu. Someone posted a link that answers the other 2 questions but not this question. I'm trying to flash a stock sense rom under multirom in twrp on my htc m8. Any help would be appreciated

Sent from my custom M8
[One (M8) Android Development] Captain_Throwback:
Because the zip is too big? Just let it go and it'll flash.
[One (M8) Android Development] Diddy555:
Hey, I still have the problem that occasionally multirom wont boot any Rom until I go to recovery and reboot from there. What I found out is that before the freeze happens, the animation for the autoboot popup bounces down off the screen and then back to the middle. Normally it doesnt go down so far. Could it be that the multirom config doesnt get loaded in this case? I also cannot reboot from multirom in this case. Nothing happens if I try. I hope it helps to figure out the culprit...
[One (M8) Android Development] randp1:
Just flashed, everything working great, thanks to all the devs who made this possible....
[One (M8) Android Development] LiLPurP:
Ok guys i flashed the miui v5 from the offical website, flashed as secondary, it said the zip was modified for multirom and could no longer be flashed as normal. First boot went fine, however i switched back to my primary for the night, now when i select miui it goes to the boot animation screen and stays there. Any ideas guys? I love the rom, always have always will. Thanks in advance
[One (M8) Android Development] Diddy555:
Did you flash a custom Kernel to Miui?
[One (M8) Android Development] mlin:
Recovery not available for download???

[MENTION=1162986]Captain_Throwback[/MENTION] Any word on why/if the recovery was pulled and/or if it will be reposted for download?
[One (M8) Android Development] krazyace35:
It never flashes it just sits on the warning screen and below that it says flashing I let it set for 10 minutes

Sent from my custom M8
[One (M8) Android Development] Captain_Throwback:
Try re-downloading the ROM and flash it again.
[One (M8) Android Development] krazyace35:
I'll try that but the rom flashes fine on stock side thanks for your help btw

Sent from my custom M8
[One (M8) Android Development] Captain_Throwback:
I don't know what you're talking about? :confused:
[One (M8) Android Development] mlin:
Download through app fails. In addition, the AFH link in the OP has a 404 error. https://www.androidfilehost.com/?fid=2368116109607132
[One (M8) Android Development] Captain_Throwback:
Not sure about the link through the app - it's a good link. AndroidFileHost appears to have been down for a few days for me.
[One (M8) Android Development] mlin:
weird, download keeps failing through the app. I checked your site and couldn't find a link to download the most recent recovery. Do you by chance have a link?
[One (M8) Android Development] Captain_Throwback:
I don't have it uploaded anywhere.

At what step is it failing? Is it failing for anyone else? Have you tried it on WiFi vs. mobile network, or vice versa?
[One (M8) Android Development] mlin:
I searched through the thread and didn't see it mentioned.

It fails on both WiFi and mobile data. My network connectivity is fin in chrome and other apps.

Maybe a server-side issue w/MultiROM?
[One (M8) Android Development] jcrompton:
Swap to primary and it will work. Look back a few pages. Some ROMs won't work as secondary ...... This happened with Liquid for me
[One (M8) Android Development] old.splatterhand:
Sometimes download in the app only worked on mobile data for me.
[One (M8) Android Development] mlin:
I'm unable to download the recovery through the app.
[One (M8) Android Development] starbase64:
no problems here at WiFi
[One (M8) Android Development] starbase64:
Same problem here, with HTC stock rom.
[One (M8) Android Development] mlin:
Thanks for confirming that its an isolated issue, now I have to figure out why I can't download. If anyone has a copy of the recovery they want to upload somewhere, that would be greatly appreciated!
[One (M8) Android Development] Captain_Throwback:
Yours is a different problem. If you look at the output, your ZIP flashed fine. The issue on yours is the boot image. Is it unsecured?
[One (M8) Android Development] old.splatterhand:
I have said sometimes (and this can have multiple reasons).

And whats happening to me, don't need necessarily happen to you, too.

And i have a stock rooted rom as second rom running fine.
[One (M8) Android Development] Captain_Throwback:
I'm uploading to a mirror now and adding a link to my recovery thread.
[One (M8) Android Development] starbase64:
I don't now, is a deodexed stock rom.
[One (M8) Android Development] mlin:
Nm
[One (M8) Android Development] edwinrodriguez810:
I don't know it if it has been asked before but I want to know if having a secondary ROM slows down the primary ROM on the phone
[One (M8) Android Development] k4p741nkrunch:
Help please!

Hey guys,

I hope you'll go easy on me, I'm not usually here for technical assistance, but I'm having a bit of trouble getting this working 100%.

I've got ARHD for my primary rom, and the sense-based NV-Rom for my secondary. I am able to switch between the two with the MultiRom Manager app, but I have never once gotten the MultiRom boot menu to appear. I've looked through this thread, and the consensus was to inject the boot sector, but I have tried that to no avail. I have tried using all available activation options for the boot menu, but none of them work. I even tried forcing generic screen drawing and that also doesn't work. Could it be my Rom selections that are causing the problem?

Going to try loading up an AOSP Rom just to test.

Also, just to put this out there, NVRom in secondary has borked WiFi. I'm sure some of you already know, but just in case someone new doesn't want to read through 77 pages.
[One (M8) Android Development] manup456:
I run 4 roms and they all function the same for me. I can't speak for everyone else, but if you read or know what your doing you won't have issues.
[One (M8) Android Development] BIGWORM:
I don't know if this has been answered, but I'm wanting to take the dive into multi-roms. Does the data stay intact in between ROMs, like text, and app data?
[One (M8) Android Development] Captain_Throwback:
This is answered in the OP. There are many links and reading that need to be done before you attempt this so that you fully understand what it does.

To answer you question directly: No. They are all completely separate ROMs.
[One (M8) Android Development] remicks:
You should make a thread man, these are perfect for this app.
[One (M8) Android Development] rpalmerin:
So in running vzw m8 on T-Mobile networks viperone 2.5 4.4.3 fw... I've download app on market, installed it. Installed recommended twrp, and no matter what I try, with numerous ways, it says I need a patched kernel... I tried elemental, tried to run a fresh install of nusense, sky Dragon, and all say I need a patched kernel. I figured hey at least nesense has a patched kernel ready... Well, no go... Am I going at it wrong or missing something? Or what any help at all would be grateful

Edit: nvm I got it, just googled it instead.
[One (M8) Android Development] mlin:
Which version of AOKP are you using? The one from the official website?
[One (M8) Android Development] remicks:
Yes.
[One (M8) Android Development] Oface82:
ooopsy

So hey guys, I could really use a helping hand if anybody's got any advice. I've been using multirom for a couple days and had gotten everything figured out despite a few hiccups. Then about an hour ago I was setting all my apps up the way I like them in PA 4.6, which was in a secondary slot, when it randomly powered down and tried to boot back into the internal rom without popping up the multirom menu. Unfortunately, it then bootlooped at the animation. Booting back into recovery TWRP says multirom isn't installed and even worse, it won't successfully any of the partitions for me to flash another rom or anything for that matter. Tried reinstalling TWRP through fastboot but the adb connection won't recognize the phone. Suggestions?

:confused:
[One (M8) Android Development] gokun:
Finally Tried it Out

Ok, well I finally decided to give the old app a try tonight and see where it got me. Here is my experience...

Installed the multirom app from play store.

Installed recovery, etc from there since that option is now available.

Also flashed the patched kernel in from there since that was also available.

Decided to just use my stock sense rom as the base(although I had read it may not work right).

Installed MIUI as secondary.

Both worked fine and booted quickly, except my host(the sense rom) had borked wifi. I presume this is because the elemental kernel doesn't agree with that part of the stock rom as I've read that elsewhere in the thread. So I make sure the other stuff is working ok, then boot back into MIUI(wifi works fine there), to see that everything works pretty much as it should there too.

So, everything was as it should be (except the wifi which was to be expected).

At this point, I deleted the second rom, ran the uninstall zip, then rebooted....hung. Probably kernel or something, so I reboot into fastboot and flash my own kernel. It boots up, but still no wifi. Hrmmmm.

So, my question here is: what is the proper way to flash your kernel back using a twrp backup?

I suspect either I did it wrong, or the settings were borked enough previously that it didn't help. Either way, would appreciate some insights from those of you wiser than myself on such matters.

The good news is I made a backup just before I started all this, so my loss was minimal.

Anyways, just thought I'd share my experience and ask my question before I gave it another go later.
[One (M8) Android Development] HC4Life:
Flar update his kernel for sense roms to ElementalX-m8-1.08-Sense, can we flash over the old version?
[One (M8) Android Development] starbase64:
[MENTION=695508]HC4Life[/MENTION]

Yes, inject boot.img after flash.
[One (M8) Android Development] HC4Life:
Ok, i already did that, now i want to install Renovate Rom as a secondary rom but as already been said Renovate doesn't work as a secondary rom only with swap method, how does it work that swap method? I have Viper as primary rom and i didn't install any rom as secondary rom yet.
[One (M8) Android Development] starbase64:
Hi,

here is a modifid boot.img for HTC Stock Rom 2.22.401.4 > http://ul.to/h8w88kfd

MultiRom works with this as secondary rom.

regards

starbase64
[One (M8) Android Development] HC4Life:
But i have 2.22.401.5 firmware...
[One (M8) Android Development] boringalex:
It seems you flashed the wrong recovery. Check again.
[One (M8) Android Development] boringalex:
I specifically said in the first post to disable screen lock from TWRP before flashing BIG roms or those that install through aroma. That's what TWRP does if aroma takes too long. I don't know why but it isn't a multirom bug.

Delete all roms that you installed and then TWRP blacked out, then go to Settings->Screen and disable screen lock and install your ROM again.

As far as I can see MultiROM works correctly. There are just some procedure errors for some users. But we will get over those as well :)
[One (M8) Android Development] Captain_Throwback:
Due to the initialization of specific block devices by MultiROM, I don't believe this will work on Verizon devices, because the partition table is slightly different.

The mr_init_devices.c code here is what I'm referring to:

//gpe
"/sys/block/mmcblk0",
"/sys/devices/msm_sdcc.1",
"/sys/devices/msm_sdcc.1/mmc_host/mmc0",
"/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001",
"/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0",
[B] "/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p42",
"/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p47",
"/sys/devices/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p45",[/B]

//sense
"/sys/block/mmcblk0",
"/sys/devices/platform/msm_sdcc.1",
"/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0",
"/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001",
"/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0",
[B] "/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p42",
"/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p47",
"/sys/devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p45",[/B]

It seems that the necessary block devices won't be initialized for Verizon devices. If there was a way to access these paths via symlink (like with fstab), it would eliminate this issue.
[One (M8) Android Development] TarekElsakka:
I had already disabled screen lock from TWRP and that's not what's causing this. Paranoid Android is AOSP and is small in size and it doesn't use AROMA. The problem I am facing is after rebooting and then choosing "PA" from the bootlist.
[One (M8) Android Development] Diddy555:
At least your screen does change, mine freezes as soon as I tap the rom. With auto boot it freezes at 1 sec...
[One (M8) Android Development] reubenskelly1992:
Seems to work great. Have viperrom 4.0 as my internal and du 4.4 as my second. The switch between the 2 is seem less:) awesome work
[One (M8) Android Development] boringalex:
Oh, ok then. In that case, after it reboots from no booting into PA, choose Internal and do a "adb pull /proc/last_kmsg" and send it to me.
[One (M8) Android Development] daorderdillon:
well mines is working now so i staright and its working fine nice job guys
[One (M8) Android Development] boringalex:
Or we can add the Verizon partitions as well (all of them). Can you please give them to me and I will update multirom to include them as well. We need boot, system and userdata.
[One (M8) Android Development] Root-Maniac:
Working Flawless here so far. Anyone having trouble just follow the directions in the OP. Very simple procedure to get MultiRom up and running :)

Thank you [MENTION=5565418]boringalex[/MENTION] This is awesome!!!
[One (M8) Android Development] boringalex:
I sent you a PM. Your multirom install folder seems to have a corrupted subfolder and I think that's why it freezes. Very weird indeed. Follow the steps I sent in the PM and keep me updated.
[One (M8) Android Development] manup456:
I followed all steps and I can boot the primary rom with no problem (ex: installed GPE and flashed ElemtalX kernel after used the inject option like the instruction say and tried to install insertcoin as my secondary). My issue is when I select to boot secondary screen just goes black I let it sit for a while and nothing. I thought let start over and use Sense as a primary and GPE as my secondary still same issue black screen not sure what's going on.

Edit: Any specific reason we are using a old twrp recovery?

Either way great work man I once all issues are worked out this should be great.
[One (M8) Android Development] boringalex:
1. How long did you wait with a black screen?

2. Please reboot to internal after it hangs with a black screen and then do a "adb pull /proc/last_kmsg" and sent it to me.

Thank you.
[One (M8) Android Development] manup456:
Will do that now give me a sec.
[One (M8) Android Development] TarekElsakka:
By the way if I want ViperONE (Sense) to be my base/main ROM, I am supposed to flash this right? "Stock Sense insecure (4.4.3): boot_m8_sense_insecure.img not tested properly!"
[One (M8) Android Development] boringalex:
Flash that but there is a chance it doesn't work (I didn't test it). You can flash ElementalX Sense kernel though, it's tested and it's sure that it will work. Your choice.
[One (M8) Android Development] TarekElsakka:
Oh wow! I thought that was just a boot.img rather than a kernel! So I am going to be re-doing the whole process over again and re-installing ViperONE as base rom and flashing ElementalX then injecting it (or w.e it's called), and after booting into it and making sure all is well I'll install CM11 as a secondary ROM.

I had no idea that "Stock Sense insecure (4.4.3): boot_m8_sense_insecure" replaced ElementalX.
[One (M8) Android Development] Freak07:
could you send me this as well? i think i have the same issue where the multi rom menu freezes and at auto boot it freezes at 1 second left.

i can neither boot primary nor secondary rom. when i hit cancel the multi rom gui freezes also.

after pressing power + vol up the same thing happens again.

i have a last kmsg if you need it.

i´m on a renovate nightly and have latest elemental x kernel installed.
[One (M8) Android Development] boringalex:
Install the multirom zip after you flash ElementalX and it will be injected automatically. You won't need to Inject manually from multirom menu.

But it's a good idea to see if it boots first.
[One (M8) Android Development] Galaxysm:
Can't download multirom .zip?

Also where can I get the modified boot image? Is it twrp? I already installed the modified twrp.
[One (M8) Android Development] manup456:
I was thinking of making a thread in the theme section I have even more I put together, I'll do it tonight.
[One (M8) Android Development] remicks:
Swap method:

In swap roms menu on multirom select move primary to secondaries, then flash Renovate to primary (internal) slot, then select swap primary with secondary and then reboot.
[One (M8) Android Development] HC4Life:
Thx bro for the info. Another question: MultiRom will support the new firmware android 4.4.4 for sense roms?
[One (M8) Android Development] remicks:
That's a question for [MENTION=5565418]boringalex[/MENTION] or another project Dev. I would assume so though.