yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] yung40oz84:
DUh, I should have thought of that or known. ah! lol Thanks

---------- Post added at 03:00 PM ---------- Previous post was at 02:35 PM ----------

I just extracted the boot.img from Liquid Smooth and added it to CrDroid and it booted right up first boot, very quickly. But now I am getting a constant system UI crash. Progress is what I like though. So........ I am going to test on some others that would not boot.

EDIT: AICP also booted right up without hesitation when adding the boot.img from Liquid Smooth. I am getting the same system UI crashes though over and over. Well at least now I know it is something in the kernels or toolchains. But how come I am getting the system UI crashes? Would you know by chance? I took the boot.img from Liquid Smooth and deleted the boot.img from AICP and CrDroid and added the liquid one to both. Same UI crashes on both ROMs, but great boot ups.

The second time I did it with AICP it gave me the dreaded unable to mount /data so I had to format /data. ugh!
[One (M8) Android Development] Captain_Throwback:
Interesting. So I guess that confirms it's something with the kernel. I would expect FCs and stuff not to work flashing the kernel from one ROM to another, but if it boots, I think that proves your theory about the kernel.
[One (M8) Android Development] yung40oz84:
Indeed, Just wish it worked with different boot.img. I posted in Liquid Smooth to try and get them to create a zip file of their kernel. If I do that, I should be able to bypass the FC's and all that good stuff.

Also, The only way I can get sense Lollipop ROMs to boot is by using SkyDragon sense kernel. That boot sup all the sense ones for me, which will not boot either. lol
[One (M8) Android Development] Captain_Throwback:
I don't see how a zip of a kernel from a different ROM will help you. Most likely that zip will just include the same boot.img you just used.
[One (M8) Android Development] bbell101584:
if y'all don't mind I'll add my two cents and I really haven't ran into any multirom issues with installing or booting as secondarys or anything but I've just found It better to install roms as primary and move them to secondary after first boot I'll take backup of primary before I do it then just restore backup after moving Rom to secondary it might just be my imagination but roms just seem to do better when installed that way and it really doesn't take no longer then waiting for multirom to modify the zip it always says is to big the 5 to 10 min that take is just as long to backup and restore a Rom in my opinion but you've probably already heard that before
[One (M8) Android Development] yung40oz84:
I tried to add the blissful kernel from a long time ago, via boot.img and I got the FC's, I am about to try to flash a zip of the old kernel and see if that works, because adding the boot.img gave me the FC and usually flashing the kernel via zip it is compatible. In the zip file there is more than just the boot.img...... right? Well, I flashed a blissful kernel zip from 1/27 and boom! It works. No FC and setting up device as we speak. Here is the link to that kernel if it helps figure some things out. The new kernel from BlissPop will NOT boot which I will provide that link as well.

Old kernel that works is HERE

New kernel that does not work is HERE
[One (M8) Android Development] Captain_Throwback:
If you use SD-Ext, that's not an option, which is why I always install my ROMs as secondaries directly. The only other option is to restore a backup to a secondary, but as I've already noted, that's not really working for me :rolleyes:.

---------- Post added at 10:52 AM ---------- Previous post was at 10:52 AM ----------

Thanks for the links, but there's nothing for me to figure out, as this clearly isn't a MultiROM problem ;).
[One (M8) Android Development] yung40oz84:
There is something incompatible in multirom obviously. For it to boot secondary on only a slim few sense lollipop roms and a slim few CM12 based roms and having to use a specific kernel to get it to boot, there has to be something in multirom. I NEVER had a problem before on multirom botting anything in secondary or restoring a backup to secondary and booting it. Everything alway booted no matter the kernel, rom, or what. So is there maybe something within multirom that is causing a clash with these new kernels or toolchains?
[One (M8) Android Development] Captain_Throwback:
Nothing I'll be looking into. You can try to work with [MENTION=3418703]Tasssadar[/MENTION] on IRC to see if you can work through it with him. If there's anything actionable (that requires a code change), just ping me.

EDIT: Also, I have no issue flashing any ROM as a secondary, as we've already discussed. They appear to just be related to device/variant differences to me.
[One (M8) Android Development] bbell101584:
oh ok I understand I haven't yet to install any secondary Rom on ext- sd my 16 gb is full of music and such and I have plenty internal space to install multiple roms
[One (M8) Android Development] Captain_Throwback:
Space isn't why I choose to use SD-Ext. I use it because I RUU rather frequently and that wipes out Internal Storage. Having my ROMs on SD-Ext prevents them from being deleted ;), though currently, a factory reset will wipe them out. I have to update the fstab to fix that, actually.
[One (M8) Android Development] bbell101584:
Oh yea makes sense we'll I'm not worried about losing secondarys as I have them just for fun and to mess around with as I can see everyone has there own preference with installing roms and I really don't ruu unless need be for some reason. I'm just happy to be able to use it as I like.
[One (M8) Android Development] Captain_Throwback:
This is why I'm saying it's not a MultiROM issue that I'll be looking into.

To be thorough, I downloaded the latest version of each ROM you said wouldn't flash as secondaries. The below screenshots are from each of those ROMs. As I stated, I had no issue flashing any of them, which is why I blame device/variant differences, and not MultiROM.

AICP:

BlissPop:

CM:

CyanHacker:
[One (M8) Android Development] redwiz666:
Does anyone know how i can get the secondary roms to boot? Tried stock 4.20 and bad boyz rom both being lollipop and will only go to a black screen. I tried copying my primary rom which is lollisense to secondary and it will not boot ether but works fine when set as primary
[One (M8) Android Development] yung40oz84:
OK, I understand that part and that sucks u got em running, for me anyway. Lol. But isn't there maybe some compatibility issue in multirom. It should work for all variants correct? So possibly something conflicting in multirom with certain variants?
[One (M8) Android Development] Captain_Throwback:
Maybe you haven't looked around the forums, but a LOT of things work differently on different devices/variants for the M8. This is no different than anything else. So no, I don't think it's a MultiROM specific issue. I can't say it any other way. By all means, keep trying to work through it on your end to come up with a working solution, but there's nothing else I believe that needs to be done by me.
[One (M8) Android Development] remicks:
This is completely true. I have a vzw m8 and I can't replicate many of the issues reported to me about multirom compatibility. There is a ton of variations available for the m8 and not all of them behave the same.

BlissPop Nightlies - M8 - KLTE - Hammerhead

remicks
[One (M8) Android Development] dopy25:
I have no issue with BadBoyz as secondary, it's what I use mostly for now. I have stock installed as primary with Captains Lollisense kernel from the beyondstock at MikMik.

The only issue I have is trying to install a GPE rom as secondary, I can't get any of them. Sense roms are fine for me as are AOSP.

Sprint M8 HK.
[One (M8) Android Development] Captain_Throwback:
Updates to MultiROM (v31) and TWRP (2.8.5) have been pushed to the app. Both freshly built. I doubt the updates will make any difference to people who are having issues, but at least now everyone can use the latest versions :).
[One (M8) Android Development] dopy25:
Sweet beans. I just grabbed the updates (recovery anyway, already had v31 MR)

Just a reminder to those that like to use TWRP themes, remember that you might want to either grab the update for the theme and replace it if you are flashing the recovery from an app within a ROM or rename/delete the theme for 2.8.4 before booting into an updated recovery as you may end up with issues as far as layout, even if it is the same.
[One (M8) Android Development] Captain_Throwback:
Just because you already have v31 doesn't mean it has the latest updates. Better to have the latest and greatest. There are oftentimes minor fixes that don't warrant a version number increase.
[One (M8) Android Development] dopy25:
Fair enough. Good point. I honestly never even knew that. I thought that updates changed version numbers.

That makes sense though because I always wondered why there were very few "updates" but different dates. Thanks for the heads up.
[One (M8) Android Development] redwiz666:
is there anyway to get a log from multirom so i can find out why none of the secondary roms i install will work?
[One (M8) Android Development] Giblet-dono:
in the multirom menu on the misc tab there are log options
[One (M8) Android Development] redwiz666:
i tried that and it freezes. any option i choose in the Misc tab freezes the phone. Is that the only way?
[One (M8) Android Development] tazfanatic:
Only issue i seem to have and it really isn't that big of a issue i can't click the cancel to bring up the boot menu. I have the latest it seem to work for a few last night but it stopped working now. I have LolliGPE by DH as my primary and Badboyz as a secondary with CM11 and 12.
[One (M8) Android Development] Captain_Throwback:
Sounds like a kernel issue to me. Just use the volume/power buttons to navigate or use a compatible kernel that allows touch to work in the MultiROM boot menu.
[One (M8) Android Development] tazfanatic:
Oh cool thanks. The app says the kernel is fine but will switch. This makes sense. I was making changes and with one of the kernels I picked and lost wifi so I did a nan and it stopped working.
[One (M8) Android Development] jcrompton:
After updates to the latest I too have been unable get a GPE ROM to update in a secondary slot or even do a fresh install as a secondary ROM ... My main reason for the post was to see if others were having the same issue. What happens is that the install almost completes and then it sticks at the end when trying to inject or finish the boot image. Sorry I don't have logs yet ... I will try to get them later.

On the bright side though I have been able to dirty flash (update) Blisspop in a secondary
[One (M8) Android Development] Captain_Throwback:
Weird - I was seeing that on my E8 build. Try running the uninstaller and then reinstalling multirom in recovery. That fixed it for me on the E8.
[One (M8) Android Development] jcrompton:
Thanks .. I tried that.

Even the install of the multirom after the uninstall borked out ....... during the end of the install the reboot dialog started flashing on and off and recovery automatically rebooted to recovery.

I did a recovery log then

I then tried to install loserskater multicarrier GPE to internal secondary .... same thing, got almost finished with the install ,,,, the reboot dialog started flashing and the install automatically rebooted to recovery without completing the install. I re did the recovery copy to SD

Attached is log
[One (M8) Android Development] Captain_Throwback:
Not sure what the log is for.

I'm using the updated versions with no issues, and I only saw the issue you're describing on my E8, to which I was trying to port MultiROM. I'm not sure what would be causing it for you on M8, though.

Is anyone else having this issue?
[One (M8) Android Development] tazfanatic:
I couldn't change kernels with GPE my primary or anything well on MultiRom. It would hang or not boot or go into hboot. I had it working fine with GPE by DH but that was my primary with when I installed MultiRom. I uninstalled MultiRom and am in the process of re-configuring my primary GPE to how I want it then will redo MultiRom.
[One (M8) Android Development] Captain_Throwback:
Where did it hang? When you flashed in recovery, or when it booted up?
[One (M8) Android Development] jcrompton:
For me it is during the installing of the boot.img ---- it's after all the rest of the ROM is installed

Then instead of hanging , I start seeing the boot options (the boot now or cancel screen) for multirom starts flashing on and off over and over again .... then reboots to recovery
[One (M8) Android Development] Captain_Throwback:
Yes, I know exactly what you're talking about. I was asking the other person, because I wasn't sure if they were confirming the same behavior, or talking about something else.

Try repairing the data partition too (doubt it'll help, but why not). I really don't know what causes that behavior.
[One (M8) Android Development] jcrompton:
Well I tried, as mentioned , the data partition repair did not work.

Of interest, I am certain that the last update of the Multicarrier GPE ROM of [MENTION=1016795]loserskater[/MENTION] was done in this secondary slot and it went off without a hitch. I don't have perfect records or logs only my memory (that's scary) but all that has happened since then was the upgrade to multirom 31 and the last recovery. Of course there could have been some changes to the istall file with the latest 3/3 update as well

Oh well ... mayb never know for sure Maybe some others can report their experiences
[One (M8) Android Development] tazfanatic:
With both GPE's it kicked me to hboot with element it hang at splash screen. So I removed wiped everything reflashed DH GPE with your kernel let it settle down and configured as I want and have made a nan. Now in process of reflashing Bad Boyz and CM12.
[One (M8) Android Development] jcrompton:
Ok all the funny stuff I was getting was solved by reverting back to the prior recovery again. It was the 1-26 version

After flashing it I was able to install either of my GPE ROMs even as secondaries
[One (M8) Android Development] jsaxon2:
I am having the same issue you had. Where did you find the 1/26 version? I can only find 1/15 on basketbuild.
[One (M8) Android Development] jcrompton:
Hopefully ok. Here is the img file zipped
[One (M8) Android Development] jsaxon2:
Thanks, I can now install the rom in a secondary slto on my Ex-SDCard but I cannot boot from it. Time to do some research. This is my first time using MultiRom.
[One (M8) Android Development] jcrompton:
Which ROM did you try? I've never had difficulty booting from the extsd
[One (M8) Android Development] jsaxon2:
I was trying FluentRom v2.0. It doesn't even list a secondary rom to boot from, only internel. If I add a secondary slot to the internal, it seems to work. I can select it and boot from it. I'm on Verizon with the Lollipop firmware that came out today.

Edit... It doesn't seem to be working correctly on Internal. It booted up and I went through the setup. Now when I reboot it does not prompt me to select which rom I want to boot.??? Good thing it will be a slow night at work. Plenty of time to sort things out.

Edit again... It is now prompting me, but when I select the secondary rom it takes me to bootloader. If I reboot from bootloader it just keeps going to the bootloader. If I power down from bootloader then then start up, it does take me to the secondary rom.

I'm going to get more information and do some research and I'll post back once I know what I'm doing. lol
[One (M8) Android Development] starcms:
Captain, will you be updating to add support for the new m8 official lollipop Verizon firmware which was just released yesterday?

When using the latest recovery and multitom from the app dated 3/3 I think, I am unable to access the boot menu which let's u choose which ROM to boot after upgrading to the official firmware. Still running BlissPOP as my primary.

Sent from my VZW One m8 running BlissPOP
[One (M8) Android Development] yung40oz84:
When I try to inject the current boot sector either directly after flashing the ROM or in the advanced multirom menu it flickers the screen and its weird. I can hit the volume up and down and actually see the multirom boot screen while doing so. And it won't go. It just gets stuck. Can't get the boot sector to work in order to boot my secondary ROMs I have installed.
[One (M8) Android Development] Captain_Throwback:
MultiROM isn't (directly) affected by firmware.

I probably do need to update the dts source in my recovery to the Lollipop stuff (once it's available) but that shouldn't be having the negative effects everyone is currently seeing.

I'll have to roll back to the previous versions until this stuff is worked out. Or see if the latest changes to MultiROM fix them.

Today's a busy day of work for me, though, so I don't know how much of that I'll get to.
[One (M8) Android Development] garywojdan81:
Same issue here, viperone 4.3.0 as host and adrenaline 1.2 as guest. Updated to the vzw official f/w yesterday, and installed the update to multirom and twrp that the app indicated were available, and lost the multirom boot menu. I can get into the guest rom, but only through the app, which boots into boot loader first.
[One (M8) Android Development] Captain_Throwback:
And what happens if you try to inject current boot sector in recovery?
[One (M8) Android Development] garywojdan81:
It runs through the process without any errors, but still doesn't bring up the boot menu. I'm running the latest elementalx kernel port on viperone and the latest elite kernel on adrenaline. Multirom manager shows everything in order too.
[One (M8) Android Development] Captain_Throwback:
You might need to use the updated dtb from the Lollipop boot.img for it to work right. I assume whatever ROM you're using isn't including it, so the kernel that MultiROM is trying to boot with also doesn't have it. That could be the issue (though technically that's not related to MultiROM if it is).
[One (M8) Android Development] starcms:
No errors but no help. Same problem using BlissPOP and other CM12 kernels.

Sent from my VZW One m8 running BlissPOP
[One (M8) Android Development] garywojdan81:
Makes sense. How would I remedy that?
[One (M8) Android Development] Captain_Throwback:
Try using the dtb from the Verizon OTA, like I said.
[One (M8) Android Development] garywojdan81:
Oh, I get you, I'm just not clear on how to do that.
[One (M8) Android Development] jtommyj:
+1 I spent about 4 hours last night trying different kernels, etc. Glad yo know it wasn't just me.

And BTW, thanks Captain for all you do. I can live without multirom until you have time to square it away.

Thanks,

Tom
[One (M8) Android Development] Captain_Throwback:
Just use the previous version. I don't think I'll be able to do anything about it for a while.
[One (M8) Android Development] TheBurgh:
Captain....is the 2-28 version thr previous version?
[One (M8) Android Development] Captain_Throwback:
Whatever the last one I posted in the thread was. Those all seemed to be working fine. The recovery update shouldn't be an issue, but in case it is, 1/26 was the previous version, I believe.
[One (M8) Android Development] jtommyj:
OK, I've done everything I can think of. I used nandroids and multirom from as far back as December with no success that I knew worked.

However, when I was reading dottats ruu thread something jumped out and that is the blocks have changed in the official lollipop update.

I'm no Multirom expert but wondering if this could b the problem we're having.

http://xdaforums.com/showthread.php?p=59241998
[One (M8) Android Development] ahsan64:
Hi

The latest version of beyondStock kernel for lollipop is 2.1.0 ?

EDIT: I downloaded dev version of kernel from mikmik site .So i think it's the latest one ?
[One (M8) Android Development] garywojdan81:
Good catch, now I'm wondering that too. I rolled back to v.30 which was rock-solid for me, and still no boot menu, only hboot. It got stuck in a loop there and I had to use the uninstaller through recovery to get back to my primary rom.
[One (M8) Android Development] Captain_Throwback:
Looks I have to initialize the previously non-existant block 49. That would explain a lot . . .
[One (M8) Android Development] Captain_Throwback:
Just pushed updates to the app.

I can't test them as I don't have a Verizon device, but I can say everything is still working for me after flashing them. Hopefully initializing mmc0blk49 fixes the issues people are having (it should, since that's where userdata is now). If it doesn't, then I'll have to look into it further, I guess. But not today.
[One (M8) Android Development] garywojdan81:
Good to go now on Verizon! Thank you sir, I guess that's why you're the Captain!
[One (M8) Android Development] jsaxon2:
Maybe I'm not following correctly, but what issue is this supposed to fix on Verizon? I am on Verizon with Lollipop firmware. When I boot into primary, everything works fine. If I boot into Secondary, I still go to bootloader and have to hit reboot, sometimes twice. Whenever I reboot from a secondary rom, it boots into primary. I then have to reboot from primary to get the MultiRom menu to select to boot into my secondary rom. I can also reboot to recovery from the secondary rom and then reboot system out of recovery and it will give me the menu to select a rom to boot.

Did you have to do something to get this to work? I installed the new TWRP from MultiRom Manager.
[One (M8) Android Development] Captain_Throwback:
Did you also install the updated MultiROM v31 from MultiROM Manager? As I previously stated, that version number doesn't always increment. That's where the fix is that you need.
[One (M8) Android Development] garywojdan81:
The issue of not being able to access the boot menu to select which rom to boot into. The official vzw f/w changed the partitions so the previous version of multirom would take you to the boot loader when trying to boot the guest Rom. Mine got to the point of being in a loop, always booting to boot loader and never the host rom. I had to uninstall multirom in recovery to get back to my host rom.
[One (M8) Android Development] jsaxon2:
I am new to MultiRom so I apologize, no I did not install the updated MultiROM v31 cause it did not display as needing updated. I just installed it from there and now I am prompted with the boot menu when rebooting from secondary but it is still going to bootloader when I select secondary. I am fine with it, just letting you know. It is not hard to reboot from there.

Thanks for your patience and for everything you do for this project.
[One (M8) Android Development] Captain_Throwback:
Previous people have stated that's related to the kernel. I believe most people have said ElementalX fixes it for them, but since I haven't updated my port of that, you can use [MENTION=1238555]MassStash[/MENTION]'s FlarPort kernel (port of ElementalX for CDMA) and see if that fixes it for you.
[One (M8) Android Development] jsaxon2:
That is the kernel I am using for both primary and secondary. Thanks for the suggestion, I will try some different kernels out and see if I get one that likes my device. lol

Gotta love that I have the same Verizon device as the next guy but they are not the same.

garywojdan81, what rom/kernel are you using for primary?
[One (M8) Android Development] yung40oz84:
I am still getting the flashing on and off flickering of multirom boot screen when trying to inject current boot sector. Won't inject. Reverted to 26 build for now. Thanks for the hard work! I will always be riding till death with multirom and this thread ?
[One (M8) Android Development] Captain_Throwback:
Any version of the recovery should be fine, as long as you've updated to the latest MultiROM ;).
[One (M8) Android Development] yung40oz84:
I am on multirom v31 and tried both the 3/03 and the 3/07 recovery and they both do the flickering when trying to inject. Only the older one from I think 1/26 is working for me and injecting multirom properly. I am ATT with firmware 4.16.1540.8 and BlissPop as primary with their kernel.