yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] Eliminater74:
Update: I cant keep up with 5 threads of this project, So I made everything on this one thread now.

I also posted the fixes and orders that need to be taken for this to work on your locked Bootloaders....

I hope this clears things up for most, at least for the time being......

PS: I think my headache is starting to go away. :)
[G3 Android Development] Meakii:
:good: working perfectly. Thanks a lot for the work.

Sorry if I'm missing something obvious but how come Multirom boots so dark? :confused:
[G3 Android Development] Eliminater74:
Dunno on that.. there is a way to change the color in adv on the menu... just click on one of the colors at the bottom..

I personally use black.......

Default is White.............
[G3 Android Development] iluvamk:
What does the oversharpening need to be set to?
[G3 Android Development] Eliminater74:
Only reason for flashing that is so you dont get that security error.. its just a work around for the time being till I can come up with a beter fix..

As to what to set it too. ask someone in here.. or whatever default is.. I didnt come up with this fix.. other users did....

im just going off of what they said......
[G3 Android Development] Roi007leaf:
Any kernel that supports multirom I think 777 supposed to support it..
[G3 Android Development] GawciuX:
Unfortunetally, all instalation with aroma didn't work.
[G3 Android Development] farangcm:
I have long used the original Multirom for the G3, but with most new roms being Marshmallow, I found myself using Multirom less and less. I wanted to try the newer Multirom, but it seemed in a constant state of flux, and I didn't know how to approach it. I tried searching the thread without success, so I decided to start from the beginning. When I got to page 4, I found what I was doing wrong. So thank you [MENTION=5579865]MrSteve555[/MENTION] for setting me straight.

I was using CandySix, so I decided to make it the primary rom and a stock rom secondary. I tried many times, but I couldn't get the Multirom menu to appear, until I flashed the 777 kernel after the Multirom zip. I still don't understand the inner workings, but thanks to [MENTION=5579865]MrSteve555[/MENTION], I got it to work.
[G3 Android Development] marcdw:
Oops.
[G3 Android Development] SaschaNes:
Do I need the bump script for now? I use it always when I flash multirom. And is the bug with multirom-twrp solved?
[G3 Android Development] masterxxxxxl:
Yesterday I installed an update to my rom plus the Multirom package and TWRP + Bump Script on my D855 with DU 6.0 weekly 20160521 and straight up wanted to reboot into the TWRP again, which resulted in starting an open recovery script that wiped my /data (luckily without /data/media), cache and Dalvik, resulting in a loss of a week of app data because my backup schedule wasn't up to date, could this be caused by some of that Multirom zips I installed at that moment, that placed the script? It's not about the done damage, but maybe someone else could be warned about this who was even less cautious than I was...
[G3 Android Development] bambotcha:
So Is there anyway I cant install a Rom with AROMA (fulmics) as a secondary Rom ?
[G3 Android Development] SaschaNes:
No, because the TWRP Version 3.0.0-0 has a few Bugs and one of them is that when you try to install a Rom with Aromainstaller, it crashes instantly
[G3 Android Development] dadi11:
you are wrong ;)
[G3 Android Development] SaschaNes:
What? I read that so on some site. Tell me then whats wrong :D
[G3 Android Development] takis:
Official twrp doesnt have the bug you tell, also the latest build of twro by [MENTION=3792100]dadi11[/MENTION] is working just fine aroma wise i think... even tho i get some strange behaviour when flasiphing aroma gapps...
[G3 Android Development] SaschaNes:
But does it have mutirom Support?
[G3 Android Development] marcdw:
It all depends on the build, the base, etc. The TWRP-MultiROM 3.0.0 that I'm using (20160209 D851) has no problems with AROMA so I use it as a fallback if later versions don't work.

At least I think that's the one I'm using. Archives are getting cluttered. [emoji4]

LG G3 D851, SkyDragon KitKat ROM, Tapatalk 4.9.5
[G3 Android Development] mrk2006:
What script version did you tried? The latest one? 'Cause I'm really interested too, as I had the same problem..
[G3 Android Development] cidxtc:
Hey [MENTION=2107489]bryan2894[/MENTION] would it be possible to make a twrp version without nebula kernel? I have to use older 2.8.3 because kernel keeps going black screen and freezing recovery after a minute or two.
[G3 Android Development] Prowler:
Can i run CM13 as primary and DU as secondary? I currently using CM13 with stock kernel.. What i should do? Ty.
[G3 Android Development] bryan2894:
The recoveries built are using the CM kernel. I'm using the last TWRP 3.0 build and I have no issues.

Yes you can. You'll need to flash a kexec-enabled AOSP kernel like the Nebula kernel, first on top of your CM build.
[G3 Android Development] cidxtc:
Well if you read the OP all your questions will be answered. They dont spend all that time writing it for no reason.
[G3 Android Development] wilson223:
I've been watching this thread and am interesting in trying this on my D852.

I do find the flashing order a bit confusing as I've noticed a few different variations.

I know I need to change my current rom as its Fulmics and I don't believe it will work. So was thinking maybe Xenon or Resurrection. Maybe CM13, not sure. (thats why I want mulitrom lol)

And I know I need to change the kernal.

Just not sure exactly what order to flash it all in. Sorry if this seems redundant, but I do find the thread a little convoluted.
[G3 Android Development] marcdw:
[MENTION=7512773]wilson223[/MENTION], I can sort of understand where the confusion comes in. Post #2 shows the flashing order but it's concerned with TWRP and MultiROM. Insert a ROM in there somewhere and one might get confused.

First off, I have a D851 so don't have to do step #4 (or at least haven't had to). Not really sure when that needs to be done with regards to ROM flashing (before, after, doesn't matter). Others can chime in on that.

Concentrating on just the primary ROM right now...

If using stock(-based) ROM, make a nandroid backup. At this point you can remove it or leave it for the time being.

[Ach. Secondaries are easily removed. Primaries/mains are wiped. Anyway...]

Do step 1: Flash TWRP-MultiROM.

Reboot back into recovery (necessary?).

Do step 2: Flash Nebula or 777kernel or ?.

Do step 3: Flash MultiROM.

Inject current boot sector now or after step #4. Sorry but again I don't know about the bumping.

Boot back into recovery OR boot regularly and see if boot menu comes up. If it does then that part is good.

[ Could take your chances and try to boot into the stock ROM but let's not. ]

If you do get the boot menu swipe to the last screen and select to boot into recovery.

For the sake of arg let's say step #4 is done. Time for a ROM.

Wipe system, data, dalvik, cache. Not internal storage.

Flash AOSP/CM ROM, gapps, etc.

Reflash Nebula or 777 as they will have been overwritten/removed by ROM flashing.

Inject current boot sector.

Reboot. Boot menu should come up. Select the primary/internal ROM and hope it boots or plays well with kernel.

Jury is still out regarding latest CM13 nightlies and these kernels.

When you first get TWRP and MultiROM flashed I suggest going into their respective setups and configuring them to your liking.

Later we can discuss adding a backed up ROM as a secondary (stock for instance).

Still, the bump thing needs to be addressed since I don't know.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] YechiamTK:
Hi, I want to use multirom but I want to be sure first- I have d855 with twrp 3.0 on it (with DU rom). What exactly do I need to flash? Do I need to flash a different twrp? Do I need to flash the sharpening mod? Or just straight forward flash the kernel, the multirom and the bump script (I have d855, do I even need the bump script)?
[G3 Android Development] Roi007leaf:
I asked the d855 maintainer..the DU stock kernel supports multirom (kexec patched) so you don't need dif kernel..as for the order..I would like to know the right one too :good:
[G3 Android Development] marcdw:
[MENTION=4971851]YechiamTK[/MENTION], as far as I know you have to use a multirom TWRP. I don't think a standard TWRP recognizes multirom or provides a menu for it.

[MENTION=6449207]Roi007leaf[/MENTION], that's great news about your DU's kernel. Is your DU maintainer Nitin by any chance?

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] Roi007leaf:
Nope. [MENTION=3792100]dadi11[/MENTION]
[G3 Android Development] marcdw:
Ah cool. dadi11 is da man!

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] Roi007leaf:
Yup! Any info regarding the flash order for d855 bro?
[G3 Android Development] farangcm:
All my primaries and secondaries exist as TWRP backups, so this information is limited and may even be wrong. First, the Primary. I can always get it to work this way, but I am not sure about rebooting to the Multirom menu. Sometimes it works and sometimes it doesn't. I start by restoring the Primary (CandySix rom) from the TWRP backup. Then I go to the Multirom sub-menu (the list of Secondaey roms). I click the three dot menu at the upper right, and choose "Inject Multirom." Then I go back to the main Multirom TWRP menu and click "Install." The folder that opens is my "Multirom Resurrected" folder, containing most of my Multirom files.. In this case I flash "MR_Bump.zip" which takes me to the Multirom menu and I press "Boot now," and my Primary has always booted successfully.

Allen
[G3 Android Development] tiendat1295:
Can you recommend some good MM Roms that runs well with Nebula Kernel, so that I can make it as primary rom? I've tried it with Resurrection Remix and BlissPop but it just gave me black screen after LG and Nebula logo :'(
[G3 Android Development] farangcm:
What is considered "good," depends on how you use the phone. For example, I don't use Bluetooth or Maps (for navigation), so I care less about those features. But I watch videos and read E-books on my phone, so battery life is important to me.

I also got black screens using some custom kernels.. That's why I use [MENTION=3792100]dadi11[/MENTION]'s MR_Bump.zip instead. I used 777kernel R22 with some of the roms you mentioned, but as secondary roms (after getting an error in the Multirom menu stating that Kexec-Hardboot support is required for these ROMs).

Sorry I don't know about Nebula kernel; maybe someone else can answer your question.

Allen
[G3 Android Development] cidxtc:
For black screen solution read the nebula faq's.
[G3 Android Development] tiendat1295:
Thank you for your answer. Battery life is my priority, too. Can you tell me what is your combo of rom & kernel that you're using now? :D (also, my phone is D851, T-mobile)
[G3 Android Development] farangcm:
I like my ROMs to support Xposed Framework, primarily for XPrivacy.. From what I've read in this thread, different LG G3 variants have different problems with Multirom.

Currently, I am running CandySix (Marshmallow) as primary using the boot script instead of a custom kernel. I am still having some problems with secondary ROMs using 777kernel R22 (again because of a Multirom menu error): Oct-M seems to boot OK, but Fulmics 5.3 boots missing the Apex launcher and 3 widgets. When I reinstall them, they are treated as updates. Finally, I am having trouble booting AICP 11.0, which has booted in the past.

Update: I've given up on AICP for the moment and substituted BlissPop 4.0.3, which booted after the "POWERD BY NEBULA" black screen.

Allen
[G3 Android Development] cidxtc:
I have asked for a twrp build with a different kernel and never got a response. The issue is during install/backup/restore the device overheats and requires a battery pull. So I have made my own. If other users have the same issue pm me and I can link you to the builds.
[G3 Android Development] bryan2894:
MultiROM - 06-19-2016

New update is available now. TWRP has been updated to v3.0.2-0, now with the new stock TWRP theme thanks to nkk71. TWRP also now has touch to wake support thanks to dadi11 and also shouldn't overheat as much. To access the MultiROM menu, now you'll have to click the icon in the top right corner. I was also able to fix up support for the MultiROM Manager app. The app should now support most G3 devices. With the app you can easily flash MultiROM+TWRP updates. Note: for bump'd devices after installing updates from the app you may also need to flash the bump script right after in order to properly boot.

Kexec supported kernels are also provided for AOSP roms. The kernel is based off CM sources and uses AnyKernel, so it should work on most AOSP roms. A kexec kernel is also available for Stock-MM D851 roms for using stock as primary.

Download links for all items are in the second post. I was only able to test for d851, so post if something isn't working for other devices
[G3 Android Development] marcdw:
Okay, did some testing and hit a serious snag. TWRP does not recognize or offer up my ext4 partition on the SD card. That's where all secondary ROMs live. That means I cannot list, manipulate, or add ROMs.

I'm only offered Internal, MicroSD (FAT32 partition), and USB OTG.

Oh, and AROMA doesn't work.

Was hoping to check out MultiROM Manager but like the Play Store version it doesn't recognize TWRP 3.0.0-0 (last known good working version).

D851.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
For the SDcard is this on the newer recovery (3.0.2-0) or 3.0.0-0?

Also, the manager app will only work on the latest recovery image. If needed, I can rebuild the older image to support the app.

For AROMA, are there issues flashing as primary, secondary or both?
[G3 Android Development] marcdw:
For the SD card it is on the newer recovery, 3.0.2-0.

No need to mess with the manager app. Assigning icons to the secondary ROMs is all I've been waiting for. ?

For AROMA, both. Just running it will cause the phone to reboot. Be it Theme Ready Apps installer or Open GApps.

I had also tried Mancuso's TWRP (with Reaper kernel) with the same issue.

BTW, my TWRP is from 20160209. That's the one I fall back on when all else fails.

LG G3 D851, XOSP ROM, Tapatalk 4.9.5
[G3 Android Development] marcdw:
Probably not useful but screenshots showing the storage selection dialogs between the old and the new.

Spoiler content hidden.

LG G3 D851, XOSP ROM, Tapatalk 4.9.5
[G3 Android Development] dadi11:
Compile twrp with omnirom 5.1 source to fix aroma issues.

Sent from LG G3
[G3 Android Development] takis:
[MENTION=2107489]bryan2894[/MENTION] really thanks for all your hard work! just installed the app now...( a question on this, will the official playstore app be updated to support the g3? in other words is your app's build like something ahead of the playstores?)
[G3 Android Development] poster288:
Hmm..Maybe I've missed something. Will the app work for the 852? I downloaded the APK in the first post, but after installing it says its not supported by my device.

Just want to make sure I'm not missing anything.
[G3 Android Development] bryan2894:
I am actually using the 5.1 sources for building. Is there any specific commit or repo that has the fix?

Yes, the app is the same as the current playstore version, just updated for the G3. I'll have to talk to Tasssadar to see if he can update the playstore version with the changes I made.

Yes, the app should work for d852. What ROM are you on and also can you post a logcat after trying to use the app?
[G3 Android Development] dadi11:
unfortunately I don't know.. I was just trying to compile twrp on omnirom-6.0, xenonhd, pac-rom sources and noticed that only on omnirom-5.1 aroma works fine
[G3 Android Development] marcdw:
[MENTION=2107489]bryan2894[/MENTION], if you're still in touch with Eliminater74 he might be able to point you toward whatever he used on the build I'm running.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] glickman:
I have a D852 as well and the app doesn't appear to work. Rom is Fulmics.
[G3 Android Development] cidxtc:
Fulmics build.prop is a little messed up. It has all the device labels wrong so you wont get multirom manager to work properly. Other roms (aosp) should work fine.
[G3 Android Development] schleyseiner:
Okay, I just installed the whole thing to test it and I apologize beforehand if my question has been answered before. I do like what I'm seeing and so far it seems to work as promised. I have it running on a verizon LG g3 (vs985). Now my question: How do I delete the whole thing in case I wanna have a straight forward setup again? Big thanks for an answer!
[G3 Android Development] cidxtc:
Use multirom uninstaller zip. Then either keep multirom recovery (wont hurt anything) or flash normal twrp recovery.
[G3 Android Development] schleyseiner:
Thanks. I read about it but couldn't locate Uninstaller file. ????

Never mind! Found it. All is well now!
[G3 Android Development] schleyseiner:
Well, I'm out of luck. None of my secondary ROMs would boot. Tried resurrection remix and the latest cm. It also didn't matter where I installed the ROM (external or internal). Too bad, would have loved multiple ROMs.
[G3 Android Development] farangcm:
Multirom.zip Error 7

I have searched this thread for error 7, but couldn't find anything relevant. Above the error message it states: 'assert failed: run_program("/tmp/inject_boot.sh")' followed by

"Updater process ended with ERROR: 7"

I had this problem last night for about an hour, every time I ran Multirom.zip. I tried many things, including uninstalling Multirom (which left my secondary ROMs intact, but didn't fix the problem, after reinstallation. Finally, the error just went away. I must have done something to fix it, but I don't know what.

Now the error has come back this morning. Does anybody how to fix it?

Update: I restored my primary, injected Multirom, and flashed MR_Bump. At the Multirom menu, I clicked "Boot Now". After booting, I rebooted to the Multirom menu and got the error that all my secondary ROMs require KEXEC support. Then I went back to recovery and successfully flashed Multirom.zip

Allen
[G3 Android Development] cidxtc:
Some roms dont like to boot as secondary. I normally install all roms as primary then backup and use backup to install as secondary. Just did this with the no caf-aosp rom.

---------- Post added at 05:04 AM ---------- Previous post was at 05:02 AM ----------

Any time you get an error during install make a recovery log. It will give you/us more info to help you. Normally error 7 is a mismatch of devices. Such as recovery states you have d855 while zip is looking for d850.
[G3 Android Development] farangcm:
All my Multirom files have D855 in the filename, but internally, I don't know. Thanks for the information.

Sorry, I missed "such as" in your post. You were just giving an example, and I took it literally.
[G3 Android Development] AgEnT_aVi_99:
XOSP + Fulmics = fail

Hi Dev,

Phone = Lg g3 D855 32/3

Root= yes

Super Su = yes

XCEED // XPOSED = no

Base Rom = XOSP 6.2 (no extra mod)

MultiRom had an error when I tried to flash Fulmics 5.3 as second Rom (log attached). MultiRom worked for these roms though (with XOSP) 1. liquid dark 2.bliss rom. :eek:

Help!
[G3 Android Development] marcdw:
Hmm, if you're boot menu works then I guess you're primary kernel is okay. Since I haven't been able to use the new TWRP I can't check for myself, though my multirom was the build recently posted.

Just maybe there may be a last log kind of thing. Try to boot one of the ROMs. After failure and you're back at the boot menu, swipe right to the last screen. There should be a button on that page to save a log file to SD. That log may have something in it.

LG G3 D851, PAC-MAN LP ROM, Tapatalk 4.9.5
[G3 Android Development] cidxtc:
Aroma style installs have issues because they call partitions diffrently. Best bet is to backup primary then wipe and install fulmics as primary. Then backup fulmics and restore xosp then install fulmics backup as secondary (i always use internal for secondary).
[G3 Android Development] farangcm:
If your problem with the new Multirom TWRP is only Aroma installs, can't you temporarily install the official 2.8.7.0 TWRP or [MENTION=3792100]dadi11[/MENTION]'s unofficial 3.0.2-0 TWRP? And then when Aroma ends, there is usually an option to boot system, which you turn off, then reinstall Multirom TWRP for the rest of the process?

I realize this scenario may not work for all Multirom processes, but I have used it successfully on the Stock Aroma installs.

Allen
[G3 Android Development] AgEnT_aVi_99:
Hello again,

1. I copied xosp into secondary from primary. So at that time i had two xosp on my phone internal memory. (Via multirom menu advanced). Rebooted to system.

2. I then put fulmics on sdcard and went into twrp and went for wipe- dalvik, cache,system,data. (I have full backup on extsdc too).

3. Tried to flash fulmics from install menu and bam it rebooted at launching aroma installer.

4. Happened twice. The primary xosp in multirom boot menu got corrupted twice too.

4.a. simple wipe and flash. Failed!

4.b. added third mod zip (mr*. zip) from op in queue with rom as mentioned for changing primary rom. Multirom crashed [MENTION=690570]Aroma[/MENTION]. So no use!

5. Copied secondary xosp onto primary. Phone works fine now.

Am I doing something wrong ? Do I need to remove multirom or something first? You mentioned using xosp recovery to install as secondary rom. How?

Thanks a lot for all the help! :)
[G3 Android Development] marcdw:
[MENTION=3209035]farangcm[/MENTION], one of the problems I have with the new Multirom TWRP is it doesn't show or recognize my ext4 partition on the SD card. That is where all the secondary ROMs live.

The AROMA issue is minor compared to that.

My current Multirom TWRP works fine so I'm still in business.

[MENTION=7488625]AgEnT_aVi_99[/MENTION], AROMA doesn't currently work. Regardless of the order you do things it won't matter.

In the meantime you can try what farangcm just posted along with [MENTION=7380272]cidxtc[/MENTION]'s advice.

Sounds like the best bet to get Fulmics initially installed.

Briefly, sounds like it would be...

Install a TWRP where AROMA works.

Flash Fulmics.

Back it up.

Do the normal full wipe (not internal storage of course).

Flash or restore XOSP.

Install/flash Multirom TWRP.

(Reboot back into recovery I guess).

Install/flash suitable kexec kernel (optional if it was already present in a restore?).

Make sure to inject current boot sector/image in Multirom.

Maybe reboot to make sure all is well and boot menu comes up. If so swipe to the last page and go back into recovery.

Go into Multirom and add secondary ROM. Use the Fulmics backup as the source.

Hopefully that works.

LG G3 D851, PAC-MAN LP ROM, Tapatalk 4.9.5
[G3 Android Development] takis:
So when aroma is fixed fulmics will be fully compatible?
[G3 Android Development] rodsayd:
Guys, can someone help me please. I'm on D851, I have flashed multirom kernel and flashed Temasek cm13 based ROM as a secondary ROM. And also I flashed the zip with AOSP kexec kernel for CM13, but still when it boots it says "Error, kerxec-hardboot support is requiered to boot this ROM".

But I flashed the kernel inside the cm13 ROM! Any help?