yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] alter2000:
Try another kernel with the patch from XDA: 777, Nebula, aCC (idk if it works)

+1 on [MENTION=6046143]marcdw[/MENTION] 's issue. Will try with another theme. If it shows the other partitions, we might be able to make do with that. I hope someone will find a way out, as I have no clue how to theme. [MENTION=7488625]AgEnT_aVi_99[/MENTION] [MENTION=5883369]takis[/MENTION] AROMA seems to work on latest official TWRP (3.0.2). I know this adds some hassle, but you can alternate between recoveries (backup/wipe/install Fulmics/backup with official TWRP, install MR TWRP, reboot, add Fulmics from backup as secondary).

EDIT

Other themes don't work either (other partitions not displayed if using MR theme or MR menu not displayed when using pure TWRP theme. This last bit was a desperate attempt)

D855 (16GB); DU/Fulmics (MultiROM)
[G3 Android Development] farangcm:
Multirom Folder location

I have had my Multirom TWRPS and Multirom zips on my external micro-SD card. I copied my Multirom folder to the internal card and it seems to have made a difference. Running Multirom TWRP from internal storage, I was able to boot my primary from the Multirom menu, which I haven't been able to do before.. Right now it's confusing because I have two copies of everything.

Should it make any difference where you run Multirom TWRP from, and where the Multirom zip files are run from?

Allen
[G3 Android Development] cidxtc:
Found issue with new multirom twrp not displaying secondary sd partition. It is in the theme rewrite to dark. I have been working on it but I have not done much theme work before. I am going to talk with the guy who made it and see if he can help fix the issue.
[G3 Android Development] bryan2894:
MultiROM TWRP Update

New update is up for MultiROM TWRP. This update should properly show the secondary SDcard partition and fix issues flashing AROMA packages. I tested OpenGApps Aroma and Fulmics as secondary and both work.

Note: when installing AROMA packages as secondary don't let the installer reboot for you. Let the installer finish installing and exit back to TWRP. This lets MultiROM properly restore the mounts. Afterwards, you can then reboot the system.

Download: https://www.androidfilehost.com/?w=files&flid=58526
[G3 Android Development] takis:
What about the playstore app? Has that case been adressed as well?

---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------

Why does uninstaller zip not work?
[G3 Android Development] bryan2894:
Not yet, just use the version I posted for now.

Can you post a log when using the uninstaller zip?
[G3 Android Development] marcdw:
Got around to testing. Two steps forward, one step back (sorry).

AROMA works. [emoji106]

Showing ext4 partition works. Can list and work with ROMs installed there. [emoji106]

Internal SD card, however, is showing up empty. Not sure why. Rebooted a couple of times but no change.

AROMA file manager doesn't work but that's something I have to check on. Installation issues no doubt.

Spoiler content hidden.

LG G3 D851, PAC-MAN LP ROM, Tapatalk 4.9.5
[G3 Android Development] Azlun:
Does this script help for “boot certification verify” ? or LG LOGO Security Error, I can not make MM works on my D855 based Android 6.0, I can not find any kernel avilable for D855 can go around "“boot certification verify” ,stock D851 kernel in link have a device model check;

even I remove it from installer sh file, it bring other errors, such as

Unpacking ramdisk failed...

Recovery busybox setup failed....
[G3 Android Development] dadi11:
it should fix errors (secure boot) after injecting multirom into the kernel. so you don't need to flash any kernel, just bump current one
[G3 Android Development] cidxtc:
[MENTION=2107489]bryan2894[/MENTION] how did you get aroma working? I have tried building on omni 6 and 5.1 and still aroma hangs on start then reboots.
[G3 Android Development] dadi11:
+1

Sent from LG G3
[G3 Android Development] bryan2894:
I had to go back to an older kernel (https://github.com/CyanogenMod/android_kernel_lge_g3/commits/cm-13.0-old). The newer kernel causes Aroma to freeze for some reason
[G3 Android Development] dadi11:
And now you're compiling it on omnirom-6.0 with cm old kernel inline? I would have to try it with my twrp as well ;)

Sent from LG G3
[G3 Android Development] bryan2894:
I'm still using omni 5.1 as the base
[G3 Android Development] dadi11:
Oh okay, for me just switching to 5.1 from 6.0 fixed the aroma issue.. Not completely though it crashes when you want to exit aroma instead of installing it.. But I didn't think about using old kernel ;)

Sent from LG G3
[G3 Android Development] bryan2894:
Same here. It still crashes when you try to exit instead installing
[G3 Android Development] cidxtc:
Thanks. The kernel I was using is based on new cm13 so that would be my issue. I will see if maybe I can figure out what is the issue with the kernel. Again thanks for the info.
[G3 Android Development] takis:
Can anyone report if multirom uninstaller works for him? I will try the log things if i am the only one
[G3 Android Development] cidxtc:
Heck just format internal sd or use file manager in twrp and delete multirom dir
[G3 Android Development] takis:
I had problems with dir of multirom and i dont wanna format data just to remove multirom thats why i asked sir ?
[G3 Android Development] marcdw:
Right. Multirom doesn't get in the way of anything. If the uninstaller doesn't work then deleting its directories is a simple matter.

If one uses regular TWRP then multirom is essentially nonexistent/invisible. No big deal.

It's been a long while since I tried or needed to use the uninstaller.

LG G3 D851, PAC-MAN KitKat ROM, Tapatalk 4.9.5
[G3 Android Development] Azlun:
offical kernel can not boot after multi ROM v33 installed and mr bump script run on my v30c-com-global firmware，blocked on “boot certification verify”，I suddenly get anykernel hardboot exec cracking works on other kernels, but block on [077]fastboot mode started. Still searching which kernel can be bump and with hardboot exec enabled.
[G3 Android Development] jmkarnai01:
All right anyone I seriously need some help. Any backup I install and I mean any as in the one I am running as primary I get the rejection posted in screen 1. I do have everything properly installed: I can boot to the option to select installed rom screen shot 2 and I am getting this previous rejection from a user in screen shot 3. What in the..... Am I doing wrong.

Edit: even on the same rom backup I'm getting the first rejection. Most recent twrp and the most recent multirom download for the ls990 and I've tried the previous also.

I have read every page and watched several videos and pictures and I'm still at a loss
[G3 Android Development] Azlun:
“fastboot mode started.” issue still blocking me, any body success to get MultiROM boot 2nd ROM with Android M at Primary ROM? please share your Kernel copy link here to bring me forward.
[G3 Android Development] manechkia:
Can I intall it on D858hk, and if I can which version should i flash?
[G3 Android Development] AlaeEl:
Hi, I am using f400 I get the error "unknown boardname f400 " when booting secondary ROM is there any way to fix this ?

UPDATE : i got it to work by using the "kexec" and "multirom" files from the the d851 MultiRom
[G3 Android Development] marcdw:
[MENTION=7605059]AlaeEl[/MENTION], well, that is quite interesting. After continued use please let us know how that is working out.

I would have never thought to suggest trying that. Cool.

LG G3 D851, Tekcafe ROM, Solid Kernel, Tapatalk 4.9.5
[G3 Android Development] Azlun:
Thank you for your screenshoot, AOSP-MM 777 kernel is what I need to have hardboot exec and no boot certification verify issue, now only small bug is. Unsupport device displayed on multirom manger apk, and rom list is not match to wigdet mode.
[G3 Android Development] cidxtc:
See in this pic where is says

ro.product.device=g3

Change g3 to your device number ex. d851

Then reboot and it should work fine.

Sent from my LG-D851
[G3 Android Development] emaxware:
I've tried using both multirom builds posted for vs985 and both complain about unknown boardname 'vs985' when attempting boot of any secondary rom
[G3 Android Development] takis:
[MENTION=2107489]bryan2894[/MENTION] any news on the playstore app updates?
[G3 Android Development] bryan2894:
The app developer hasn't pushed updates to the app for a while, so no.
[G3 Android Development] bryan2894:
MultiROM v33a - 08-26-16

Sorry for the delay but a new update is up. This update should fix the "unknown boardname" error for variants other than d851 and d855. You can now also flash roms containing "system.img" as secondary without it messing with your primary rom (usually happens with stock roms).

Also included with this release is [MENTION=2605798]nkk71[/MENTION] 's no kexec workaround. With this a kexec hardboot patched kernel won't always be necessary. I've tested this on d851 with a few AOSP roms and stock without trouble. Let me know if it works on the other variants (you'll most likely still need to flash the MR_bump.zip). To enable this feature and for more info read HERE.
[G3 Android Development] Prowler:
work perfect!

only a strange thing, multirom manager doesn't work in internal rom (fulmics 6.1) but it does in secondary roms.

d851
[G3 Android Development] marcdw:
Testing things out on D851. Haven't put it through all the paces yet.

One annoying issue is I lose internal storage after actions like flashing a zip. Thus can't do anything else until I reboot back into recovery. I think I had that issue before.

Can't get Aroma file manager to work yet. Versions 1.9 and 2.0. Will check that later after work.

LG G3 D851, OctOS-M ROM, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
Fulmics & stock roms all label the device name as g3. You can either edit the build.prop and put in your device name as shown in this post: http://xdaforums.com/showthread.php?p=67859908 OR enable developer mode in the MultiROM app by tapping the version number. Then click Override device name and enter your device name (ex. d851).

Does toggling internal storage in mount options bring the sdcard back? And what package are you trying to flash that has Aroma 1.9, so I could test?
[G3 Android Development] marcdw:
[MENTION=2107489]bryan2894[/MENTION], I'll check on the mount toggle when I get a chance.

BasketBuild is down but luckily I kept the Aroma file manager zips. Versions 1.9 and 2.00 should be below.

https://mega.nz/#F!mZAGSayA!UqaJCF-01waAi0xpfrdzsQ

LG G3 D851, OctOS-M ROM, Tapatalk 4.9.5
[G3 Android Development] {101}darkvoid090:
Korean Variant

First of all I would like to thank the developer for his awesome work. :) :D

- My personal experience trying to install this on a korean variant (F400L) running stock based MM rom (fulmics 6.1) is a frustrating one. First of all, the latest version for the twrp modified recovery for f400 is giving boot secure error, after many attempts, I decided to try an older version of the twrp recovery which worked fine(TWRP-multirom-20160703-f400.zip). After hours of extensive research, I have failed to find any suitable kernel or work around for kexec, the provided kexec zip does not work either(says the device is not supported), nor the option for kexec workaround in the recovery (I get a warning message every time i try to tick it and it doesn't activate). The only option at this point is to remove the main rom, install a cm based rom as a main, then flash fulmics again, possibly from a back up. but the problem is, my current rom image is over 10GB, so I don't think that's an option for me. I have currently decided to wait for a fix or a workaround, I just thought to share my experience with other f400 owners and bring this issue to the spotlight, since our device sadly gets less attention than most variants. :rolleyes:
[G3 Android Development] marcdw:
Hello [MENTION=2107489]bryan2894[/MENTION], I've got a strange issue here.

But first let me say I've been using the latest TWRP and multirom and all is going well. The issue of the disappearing internal storage listing seems to have fixed itself after regular usage.

The thing that is confusing me, I install the LG QuickRemote on all MM ROMs and post successes and failures in its thread. 99% successes with only one ROM being a problem.

Anyway, with the new TWRP/multirom I'm getting failures to install it. Output of flashing shows success each time but the files are nowhere to be found on the ROMs.

As a test I manually installed/pushed the files. All was good. Then I'd go back and flash the remote. The remote's files are now gone from the ROM.

Generated a log and see that the files are being extracted to where they need to be but they actually don't.

Since I'm not versed in the ways of TWRP I'm probably missing something obvious.

Think you can take a look at the log? It's a zip file.

Thanks.

https://mega.nz/#!WI4mjbaY!12Ng6FiZTg3LFSSm8Ae-IYCAzKDm6QbqKl2YyE58b5M

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
I pushed an update that should fix the errors for your device. The kexec zip will only work if your using an AOSP rom as your primary. It won't work on stock roms like Fulmics.

I pushed an update for TWRP that should fix the issue. I tested it out and it seems to work fine.
[G3 Android Development] jrome123:
On d851 i have stock as internal I can do the work around on the last build work perfectly haven't tried the new one.
[G3 Android Development] bigcletus:
I was using multirom when I was using fulmics 5.3. I restored it as a secondary from backup, and also had a stock tmobile rom (lollipop) as a secondary with an aosp rom as primary. everything worked great. I wanted to start over with the latest fulmics 6.1 and tried the same procedure for restoring my backups as secondaries but none of them will boot past the LG boot logo. I can only get the aosp primary to boot. The only difference from my last setup was I think I was on the lollipop bootloader and modem. Now I am using the latest marshmallow bootloader and modem. Any ideas how to get these backups to boot? Using a D851. Thanks for any help.
[G3 Android Development] marcdw:
That was one excellent post. ??✌

Gonna have to save that one.

Regarding the time it takes kernels. I don't think anything can be done about that. Kernels, some stock ROMs that flash a specific kernel, even Oct-M which bumps the installation can take two hours or more. So normally I don't flash kernels against secondaries.

SD card. From the beginning I created an ext4 partition for ROMs (currently 20GB). Flashing ROMs is not too slow and ROMs run just as fast/stable as a primary.

Lunch break over. Will re-read the post. Excellent.

LG G3 D851, Mahdi KitKat ROM, microG Project (NoGapps), Tapatalk 4.9.5
[G3 Android Development] {101}darkvoid090:
I had a bootloop for some reason on my DU that I couldn't solve,it's probably not related to multi rom but after i deleted the rom (for the purpose of re-adding it later) my primary rom didn't boot and had to dirty flash it :confused: .

I will try to skip the kernel the next time i install du although the main purpose of my usage of multi rom is to tinker with secondary roms as much as possible without ruining the main rom(which means I want a custom kernel as well) and I still need to wait a while for Mr.Bump to flash. I might consider a re-partition option at a later point but for now the only viable option for me is to use the internal memory for secondary rom installations.

Another weird thing I noticed is that after I installed the first secondary rom, the second rom flashing process was much faster (still considerably slower than any actions on the main rom) but significantly faster than before. as for rom performance it runs just as good as primary even with all them tweaks on. :p
[G3 Android Development] marcdw:
Oh, [MENTION=2107489]bryan2894[/MENTION], I forgot to mention. Discovered by accident that the Aroma file manager runs just fine.

I downloaded another zip of it thinking it was an installation zip. When flashing it the file manager came up and works.

So the issue I was reporting I guess is that TWRP isn't set up to use an installed copy. Previously, if aromafm is installed, there would be an option in TWRP's settings to use it instead of the default.

LG G3 D851, Dirty Unicorns ROM, TeamBlackOut, Tapatalk 4.9.5
[G3 Android Development] hunghv1413:
Hi, now i am using fm 6.5

Can i use it as primary ROM?

And can i add cm13 as secondary rom?

Thanks

Gửi từ LG-F400L của tôi bằng cách sử dụng Tapatalk
[G3 Android Development] Breno Spangler:
FM 6.5? What rom os that?
[G3 Android Development] hunghv1413:
Sorry, fm 6.1

Gửi từ LG-F400L của tôi bằng cách sử dụng Tapatalk
[G3 Android Development] marcdw:
Still no idea what fm 6.1 is. If you mean Fulmics, say Fulmics.

Read post #884, just a few posts up. There is information there that may give you some ideas.

LG G3 D851, Mahdi KitKat ROM, microG Project (NoGapps), Tapatalk 4.9.5
[G3 Android Development] {101}darkvoid090:
it's all there in my post #884, read it carefully and report once you have done all the steps with your feedback. It would be a really good thing if we make a nice detailed walkthrough on how to install the mod for stock based rom users and spare the dev the repeated questions while making things easier for the user. 2 birds one stone i'd say :D ;)
[G3 Android Development] wolf45801:
I flashed the multirom files along with the twrp for multirom but I'm not getting the multirom section inside twrp any ideas? My device is the d850
[G3 Android Development] marcdw:
The MultiROM section is not readily apparent. That threw me off coming from 3.0.0.

Tap on the "menu" icon you see at the upper right of the TWRP screen. That will take you to the MR stuff.

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] wolf45801:
I don't have the menu icon in the upper right corner looks the same as original even though it says multirom at start up when loading recocery5
[G3 Android Development] farangcm:
If you don't have the three horizontal lines menu in the upper right side of the screen, you MUST be using the wrong TWRP--maybe an older Multirom TWRP. For the LG G3 D850 variant, the file should be "TWRP-multirom-20160907-d850.zip."

Allen
[G3 Android Development] wolf45801:
That's the one I flashed
[G3 Android Development] marcdw:
Is it possible to post a screenshot?

The standard Power+VolDown works in TWRP for shots.

Can't understand why it's not showing up.

If MultiROM is not or incorrectly installed I wonder if that button is still present.

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] wolf45801:
Yeah as soon as I get home ill try
[G3 Android Development] wolf45801:
Here's my screenshot when it first loads its blue with the 3 headed dragon it looks like and says multirom twrp 3.0.2-0
[G3 Android Development] cidxtc:
That is not the multirom recovery. It is easy to for me to know the difference because 1st it is black and red and has the wrong title displayed. See attached picture.
[G3 Android Development] marcdw:
Okay, I see what happened. You're using a theme. There are no TWRP-MultiROM themes available for the v3 series. That's mentioned in the TWRP themes thread.

Compatible themes are only available for versions below 3.0.0.

MultiROM users are out of luck when it comes to themes. Remove the theme and you should see the MultiROM menu button.

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] wolf45801:
Ok well hell I should have did that before sorry. And thanks
[G3 Android Development] farangcm:
I don't know how you figured that out. Of course, I have never used themes. Well done!
[G3 Android Development] marcdw:
I've seen some really nice themes out there. Too bad we can't use them. I drool over some of those themes. I think those that make the themes don't have/use MultiROM.

At least our current TWRP is darkish. 3.0.0 was way too white and bright but I liked the layout.

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] AndroidxWolF:
I have a d855 model and I wanted to install MultiROM app in this device , for that I needed to modify that build.prop ( exactly "ro.product.device" from "g3" to "d855" ) the thing is camera stopped working for no raison even after wiping its data so what is wrong ? did I missed anything ?

I am sorry if I got in the wrong thread ...
[G3 Android Development] 8ballhacker:
Anyone have issues with losing signal, seems since about a day after installing multirom my phone seems to be losing signal going into emergency calls only and no sim card status. I have tried reflashing roms, kernels, multirom. But to no avail. I have 3 roms installed and all do the same on boot up has signal then after a little time the device loses signal again, or up on boot no sim card. Then it seems I have to reflash rom but only fixes issue, maybe for a day or maybe even a couple hours. Any ideas how to fix?
[G3 Android Development] bryan2894:
MultiROM v33b - 09-27-16

New update is up.

Changelog:

MultiROM

* No kexec-hardboot v4

* Allow auto booting from ext. storage

* MultiROMMgr app updated to support no kexec workaround

Recovery

* No kexec-hardboot v4

* Fix install from backup

* Fix support for Nougat roms
[G3 Android Development] takis:
what about slow install times?
[G3 Android Development] bryan2894:
If for secondary roms, that's normal.
[G3 Android Development] takis:
Yes but its too slow, it can take even hours
[G3 Android Development] bryan2894:
What ROMS are you installing and are you installing it on internal storage or and external sdcard?
[G3 Android Development] takis:
actually i tried installing aosp N without success (secure boot error) but even when i flashed on it the bump.zip it took it 10 ! minutes) others reported that changing kernels took 2 hours
[G3 Android Development] marcdw:
[MENTION=5883369]takis[/MENTION], ROM flashing times are okay but kernels can indeed take two hours. So far that seems par for the course.

Tonight I'll do Nougat again. If it fails to flash I'll use a modified updater-script that worked with the previous AOSP and CM14.

LG G3 D851, AOSPA-M ROM, Gamma Kernel, Tapatalk 4.9.5
[G3 Android Development] takis:
please post a guide if you manage to install nougat on second rom
[G3 Android Development] marcdw:
With the new TWRP/MultiROM no fix or workaround needed. Yair's AOSP Nougat flashed as secondary with no issues, warnings, or errors. That's good.

Got serious issues with SuperSU and developer options which I may post about on G+.

However, things went south after that and now I'm in the process of redoing my primary ROM.

Flashed TWRP. Reboot back into it.

Flash MultiROM. Reboot back into recovery.

Inject current boot sector. Reboot.

Chose primary so I could install latest MultiROM Manager, see if anything has changed. Nope. Not functional yet.

Now time to reboot into Nougat. Nope. Boot manager tells me there is no kexec kernel available. I think to myself "Excuse Me?!?" Tried to boot into other secondaries with same response.

Back into TWRP. Flash and reinject kernel. Same same. Tried to boot into primary. Either I'm thrown into TWRP or phone shuts down. Other times just reaching the boot manager will trigger a shutdown.

Reflash kernel, inject, wipe some dalvik and caches for good measure.

There were onscreen warnings and errors when I inject. I did not get screenshots. Sorry.

Eventually I had to revert to previous TWRP/MultiROM. Then I was able to inject kernel and boot into Nougat and other secondary ROMs. Unable to boot primary so went for a reflash session. Haven't yet tried to boot into it.

Once I fix everything up I will reinstall and reproduce any issues along with screenshots.

For reasons unrelated to this I had to reflash Nougat. Flashing failed because I'm on older TWRP but luckily I made a patched/fixed zip just in case.

LG G3 D851, SlimSaber LP ROM, Tapatalk 4.9.5