[T-Mobile LG G3] SonjaMichelle:
Ok, I think I can see where some of the frustration and anger is coming from on both sides. I just sat here for the past couple of hours arguing with my phone trying to get the new MultiROM to work.

There isn't a lot of clear step by step documentation to go by. Though there is a lot of "This is Dangerous and could blow out your phone, Do at your own risk: and an hefty bit of stricken out text. Then you come to the list of files you need. Simple enough. I grabbed all those set them aside for my install.

Next step, after following the threads for a few days, was to find compatible kernels. This was the tricky part. There was kernel already in the first batch of files. Then there was a link further down to another kernel. Peppered throughout the thread there were mentions of other kernels but no links that I saw. Though one fact came to light. If you want to run the NEW MultiROM you were best off with kernels patched with NEW code. (Seem to recall that second linked kernel was old code) So my Plan to use SkyDragon as my Primary ROM maybe thwarted from the get go since it uses a skin1980 kernel. (old code). I gave it a shot any how.

As expected, SkyDragon took the new Multirom fine, though any time I tried to boot a secondary ROM, kernel panic! OK, no use jumping on the forum and crying about it. Known issue. :p So I tried swapping things around I used Fusion LP as my Primary with Eliminater74's kernel and SkyDragon as Secondary with skin1980's kernel. Resulted in the screen continually going into download mode. Then I seem to recall that the secondary ROM didn't need a patched kernel. Tried that. Nope, just hung at the boot screen and then would eventually reboot to recovery. Bugger all!

So now I decided to try Fusion and BlissPop with the TootsiePop Kernel. Fusion set-up as Primary with Eliminater74's kernel ... BlissPop set-up with TootsiePOP kernel. Yay we got some MultiROM love finally.

Yes it was a very long and frustrating process. There are some shortcomings mainly in the availability of patched kernels vs the about of ROMs that are out there to try. I think this is what everyone is getting hung up on. They keep trying to use old patches with the new code and getting error after error.

I think the quick fix is to produce more patched kernels. Now I know how to build a ROM. I have cm11 and cm12 source. Actually Downloading BlissPOP source now. I can build a kernel, But I don't know the first thing about PATCHING a kernel. (I'm NOT a programmer I'm just an old retired Firefighter/Medic) I have built a kernel before, But I haven't been able to package it into a flashable zip.

I'm willing to help. I'm retired so I have the time. I just need to learn those few things and I can hopefully help push out some patched kernels. We need them for the new 20b stock and some for the older stock for sure. The sources are out there. I have the source for the new 20b and I can repo the AOSP tree again.

Like I said, just teach this old dog a few new tricks and I can help out. I can babysit a compiler :silly:

---------- Post added at 04:33 ---------- Previous post was at 04:12 ----------

OH! And I found a temporary work-a-round to the no touch screen bug.

In MultiROM settings, go into auto boot. set it to key press. When you boo the phone it will automatically boot into your Primary ROM UNLESS you hold down either the volume up or down buttons while powering on. If done so the MultiROM menu will appear. With the volume buttons you can scroll through the the menu choices and with the power button make a selection. On subsequent boots. Once you release the volume up or down button the screen is touch sensitive again. Though once you boot coming from recovery again, you need to use the keys only.

This keeps you from having to full Boot into Primary then reboot just to get into your Secondary ROM. :good: