yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] Prowler:
[MENTION=6046143]marcdw[/MENTION] what the f..? that's a bit embarrassing.. I installed latest TWRP and Multirom over Fulmics 6.5, then cleaN as secondary and everything works great except dev options. You have no-kexec workaround enabled?

M̶u̶l̶t̶i̶r̶o̶m̶ ̶m̶a̶n̶a̶g̶e̶r̶ ̶s̶t̶i̶l̶l̶ ̶n̶o̶t̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶w̶i̶t̶h̶ ̶n̶o̶-̶k̶e̶x̶e̶c̶,̶ ̶i̶ ̶m̶e̶a̶n̶,̶ ̶i̶f̶ ̶i̶ ̶t̶a̶p̶ ̶t̶o̶ ̶r̶e̶b̶o̶o̶t̶ ̶i̶n̶ ̶s̶e̶c̶o̶n̶d̶a̶r̶y̶ ̶i̶t̶ ̶s̶h̶o̶w̶ ̶a̶ ̶p̶o̶p̶u̶p̶ ̶t̶e̶l̶l̶i̶n̶g̶ ̶m̶e̶ ̶t̶h̶a̶t̶ ̶t̶h̶e̶ ̶r̶o̶m̶ ̶d̶o̶e̶s̶n̶t̶ ̶h̶a̶v̶e̶ ̶a̶ ̶h̶a̶r̶d̶b̶o̶o̶t̶ ̶p̶a̶t̶c̶h̶ (nvm, my mistake).. the only and little issue so far is custom rom icon (not defaults), i cant change it with MR Manager provided here, but the play store version works great for that.
[G3 Android Development] takis:
Which device? I think d851 process is different as its unlocked
[G3 Android Development] marcdw:
[MENTION=5198834]Prowler[/MENTION], oh no, I didn't have any issues with CleaN as far as TWRP/MultiROM is concerned. It flashed as a secondary without issue but I did have a backup zip of the ROM ready with the updater-script you posted in another thread. Just in case. CleaNrom runs just fine other than my SuperSU and dev options problems.

The MultiROM Manager provided here allows me to change the icon of the primary ROM. Too bad secondary ROMs don't show up. For me anyway.

[MENTION=2107489]bryan2894[/MENTION], so I gave it ago again with the same results. My primary kernel (Nebula) is not being injected or something.

As before, I then can't boot into my primary. It'll jump to the recovery but after a couple of attempts as soon as the boot manager shows up phone shuts down.

I revert back to the Sep. 07 builds as before but it's a no go.

Had to reflash the ROM (PAC-MAN LP) to get back in. Twice so far.

The screenshot below is similar to what I got before. Not really sure what's going on.

Ach, but I didn't get a log. Not sure I want to have to flash my ROM a third time to get one. ?

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5

---------- Post added at 10:58 AM ---------- Previous post was at 10:04 AM ----------

If anyone wants to test there's a couple of MultiROM compatible themes below.

http://xdaforums.com/showthread.php?t=3336457

[THEMES][T.W.R.P. 3.x] TWRP Themes-Multirom Themes!!!(29/09/2016)

LG G3 D851, PAC-MAN LP ROM, Nebula 9.1 Kernel, Tapatalk 4.9.5
[G3 Android Development] Lapine Block:
I have stock 30N on primary and I'm trying to get RR5.7.4 on secondary. I install MultiROM on primary and bump the boot image for both. I can boot into primary fine until I try secondary and get the secure boot error. After that I have to reflash everything to be able to boot into primary again.

How do you have stock as primary and CM on secondary working?
[G3 Android Development] droiday:
twrp and multirom v33b can not save kernel with patc kexec hardbot, always back to first kernel in roms(with no kexec)..
[G3 Android Development] marcdw:
Not exactly sure what you are saying.

You mean the primary kernel (kexec) is not being injected? Cannot boot secondaries?

If so the same here. Have to use v33a in the meantime.

I still need to get some kind of log.

LG G3 D851, PAC-ROM 6, Tapatalk 4.9.5
[G3 Android Development] Shady282:
Multirom manager in the second post is not working it says it does not support g3 i m on Fulmics 6.5.

Also, did anyone manage to boot crdroid in multirom?

also i m having issue with primary internal rom not having an OS ... i try to copy or move a secondary os into the primary os but i get error : E: copying failed, see log for more more info!

I tried to move different secondary roms. and one that was primary and it is not working :/

D851
[G3 Android Development] cidxtc:
Fulmics build.prop must be modified for multirom manager to work.

I installed crdroid 7.0 as primary then moved to secondary and have no issues besides known ROM bugs.

If no ROM is installed to primary then you can not move/copy any secondary to primary.
[G3 Android Development] eamon.ash:
But if i use the manual installation.. the multirom will work or not
[G3 Android Development] cidxtc:
I don't understand your question
[G3 Android Development] eamon.ash:
If the multirom manager did not work .. What should i do
[G3 Android Development] cidxtc:
Edit build.prop to match the attached pic
[G3 Android Development] eamon.ash:
Can you give me you build.prop file .. Cuz i edited it but the manager wont work .. It says. Unfortunately multirom manager has stoped working
[G3 Android Development] cidxtc:
You saved it and rebooted?
[G3 Android Development] eamon.ash:
Yep

---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------

Yep
[G3 Android Development] bryan2894:
MultiROM v33b - 10-10-16

New update is up. This update should fix a majority of the issues with injecting kernels, and flashing images. Swapping roms should also be fixed too. MultiROM and TWRP have also been updated to auto-bump your kernel after MultiROM gets injected. So, the mr_bump script shouldn't be necessary anymore. The MultiROMMgr app has also been updated to support roms on external storage. You can now change the rom's icon, delete and rename the rom from the app. However, you can't boot into the rom from the app for now. The app should also work now on stock roms, without modifying the build.prop.

In regards to flash speeds, 10 minutes is about normal for flashing secondary roms. For those who flash kernels on secondary roms, kernel install times should be improved a bit except for those using AnyKernel. The reason is the scripts included in AnyKernel try zero out and clear the boot image before flashing. It does this by filling the space of the image with zeros to clear it out. This process is short if flashing as primary since its flashing to the boot partition, which is only about 16MiB. However, for secondary roms the boot image is on your external storage, so it ends up trying to fill all the space on your storage which is why flashing takes so long. To stop this from happening you can do the following:

Lastly, if you have a nougat rom as secondary, you might have issues entering Development Settings. If you do, you can flash the a patch linked HERE. It should fix the issue.

Download: https://www.androidfilehost.com/?w=files&flid=58526
[G3 Android Development] marcdw:
I take it the dev opts patch is flashed against the N ROMs. Just making sure.

I was wondering why dev options worked sometimes and not other times. Didn't make the connection from when I was running as primary vs secondary.

?

LG G3 D851, Fulmics v6.5 ROM, Solid v2.2 Kernel, Tapatalk 4.9.5
[G3 Android Development] wolf45801:
I flashed the newest builds for the d850 but now when I boot the phone it comes up fast boot mode started and I noticed it keeps saying failed to flash kernel please help
[G3 Android Development] marcdw:
Hello [MENTION=2107489]bryan2894[/MENTION] sir.

Things have fallen apart for me once again. Had major issues a day or so ago that have resurfaced. Currently can't get into my secondaries. No kexec issue persists.

Don't want to type everything again. Can you look at my two posts here:

http://xdaforums.com/showthread.php?p=69073073

Tried to get logs dumped as soon as possible.

MultiROM

https://www.dropbox.com/s/zolplt7dsmw9t87/multirom_log.txt.zip?dl=0

TWRP

https://www.dropbox.com/s/77qs3h5ee2wl7vt/recovery.log.zip?dl=0

MultiROM Manager also didn't show any secondary ROMs. Maybe because my ROMs are on a separate ext4 partition?

LG G3 D851, PAC-ROM 6, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
Does fastboot mode show when you enter recovery or when you try to boot a secondary rom? Can you also post a log from recovery after you get the "failed to flash kernel" error? You can do this in recovery by going to Advanced > Copy Log. This copies the log to your internal storage. Post the log here so I can look at it.

Do you have issues booting into your primary rom as well or is it just your secondaries?

For MultiROM Mgr, does the separate partition where your roms are stored show up in Android? Are you able to access it? If you can, do you know what folder it gets mounted to?
[G3 Android Development] wolf45801:
The 690 fastboot mode showed up as soon as I tried to boot the phone I couldn't do anything other than enter recovery using the power and volume down buttons I did a restore of my backup and it fixed the problem
[G3 Android Development] marcdw:
Just the secondaries. Though when all this started I had no primary. Taking a cue from J. Mancuso I decided to try a secondaries only setup. Using the primary/internal spot for flashing and backing up ROMs for secondary use.

I'm finally back into my secondaries after a night of frustration. Heh.

The general behavior was something like:

Reach boot manager.

Select ROM.

LG logo for a bit then then thrown back to boot mgr.

Select ROM again but told no kexec kernel present.

After a bunch of messing around, downgrading and upgrading MR, flashing/injecting kernels, etc. I get to the point where the ROMs (save for one) were all stuck at the LG logo.

Currently I'm using the no-kexec workaround in conditional mode. Some ROMs will boot directly, some will be thrown back to boot mgr. On reselect no-kexec workaround gets used.

Well, hope this doesn't sound confusing.

Had been using PACMAN LP as my primary since July 2015. The ext4 partition doesn't exist in any manner in the ROM. Which was fine.

Marshmallow secondary ROMs show two sdcard1 entries in storage settings. One is always "corrupt". I knew from the beginning that referred to the ext4 partition its running on, so always ignored (where applicable I use NotifyClean to hide the notification).

The partition doesn't exist in the filesystem.

Now, KitKat and Lollipop is a different story. The ext4 partition doesn't exist as far as Settings is concerned but it is accessible via the file system. I can access any of the installed ROMs via the following path:

/mnt/mrom/mmcblk1p2/multirom-d851/

Refer to Partition Toolkit images for actual device names.

LG G3 D851, PAC-MAN LP ROM, Tapatalk 4.9.5
[G3 Android Development] Eliminater74:
[MENTION=2107489]bryan2894[/MENTION], I just wanted to let you know that there is a Kexec Hardboot workaround patch available.. It may have to be tweaked a little for the G3....

We have it on our HTC10.... Yes I have a LG V10 and a HTC 10 ............ and a guy created the kexec hardboot patch.. it allows you to boot secondary roms without the need for a kexec hardboot kernel.

so any kernel will work.. it will also work with kernels that do have the patch.. but it might be something worth looking into.

Check it out here: .......

I just stepped in for a bit to see how things are going.. Its nice to see that your still updating this..

I left LG all together.. I still have my G3... but as for ever buying another LG, It will never happen........ I have Zero Respect for LG now.

they locked down all their newer devices so tight.. you cant do anything.. the G5 still cant get camera to work...............

and the V10, no camera and blue doesnt work................. so I gave up on LG... So as it stands the G3 is the best phone LG ever released before going stupid.

well.. l8rz dude.
[G3 Android Development] bryan2894:
Usually, when using MultiROM if a ROM gets stuck on the LG screen, the first thing you should try is restoring SELinux contexts for that ROM. You can do this by going to the MultiROM menu in recovery > List ROMs > Select the ROM with boot issues > then Run Restorecon. This fixes boot issues most of the time, especially if the ROM is using SELinux in enforcing mode (most LP, MM ROMs).

For the app, I think I should have a workaround for that soon.
[G3 Android Development] bryan2894:
Thanks. We've actually been using that patch for a while now. It works pretty well, I didn't have to make any tweaks for the G3.
[G3 Android Development] lucbondar:
dumb question: devoptions fix should be installed on main or secondary rom? I try installing it over secondary Cleanrom but unfortunatelly doesnt work..

btw, rommanager app still not working, at least for me, in stock based rom (fulmics 6.5) without change build.prop or overriding device name in-app.
[G3 Android Development] bryan2894:
The patch should be installed on your secondary. If the script doesn't work, your ROM probably doesn't support init.d which is needed for this to work. There are a few apps on the Play Store which can help. And last, what device are you using?
[G3 Android Development] lucbondar:
Thanks for quick answer. Ill try adding init.d support and report.

d851, i forgot mention it.

edit. i noticed that the systemless su doesnt work with etc/init.d so i unroot and install system root, then succesfully added init.d support but the fix still not working, i cant try in another N rom (cm14, crdroid) because doesnt boot in MR.
[G3 Android Development] marcdw:
Ooh, I didn't know about the init.d requirement when I tried. Good to know.

Alas, my G3 got bricked some days ago. SuperSU's unroot (in a secondary ROM) saw fit to extend the deed beyond where it should've. No boot, no recovery, no nada. Just a rapidly flashing screen with a little droid bot with wings or a cape. Can't tell. Bummer.

Samsung Galaxy Light SGH-T399, Jelly Bean 4.2.2, Tapatalk 4.9.5
[G3 Android Development] UniX1rm:
I am installing Nougat as a secondary. I did not get any errors whatsoever, but gets stuck on the LG bootscreen. I have tried a couple of roms clean. I am running fumic 6.5 as my base rom. Anything I am missing? Kernel? etc .. ? I have cm13 installed as a secondary rom as well, boots without a single issue. Any help would be much appreciated.
[G3 Android Development] cidxtc:
Brand new Android version with multirom issues? Would never thought that possible.

Of course you will have issues with 7.0. It is new and will need things modify to work 100%. It is not every 7.0 rom but many won't run as secondary. With time things will get figured out.
[G3 Android Development] bryan2894:
MultiROMMgr update & DevSettings fix

OK, I updated the MultiROMMgr app to support Fulmics roms, other stock roms, and also roms on all external partitions. I also updated the DevSettings fix to better support all roms. Having init.d support shouldn't be necessary, since this patch now modifies the kernel ramdisk instead. Links are below.

Let me know if the MultiROMMgr app still doesn't work for you.

DevSettings Patch: https://www.androidfilehost.com/?fid=312978532265364374

MultiROMMgr: https://www.androidfilehost.com/?w=files&flid=71244
[G3 Android Development] vbenkovskyy:
Dear DEV where the other patched stock mm kernels not only fom T-Mobile version?
[G3 Android Development] bryan2894:
They're not available. The no kexec workaround works better with stock roms anyway.
[G3 Android Development] vbenkovskyy:
So how make it work on Fulmics rom?

I've installed kexec kernel for AOSP as MultiROMMgr has proposed and no boot menu appears on boot.

Zip installed, bump installed, kernel w patch installed. Where is my mistake?

EDIT:

I'm sorry. I've found your answer that I should install AOSP as primary ROM.

Can I ask you to fix MTP mode on MultiROM TWRP for D855?
[G3 Android Development] lucbondar:
Great! now multirom mngr works fine on fulmics, except when try to pick an image from gallery for custom rom icons.

sadly devoptions fix doesnt work for me, settings keep freezing in cleaNrom.
[G3 Android Development] bryan2894:
This update should finally fix it (DevSettings): https://www.androidfilehost.com/?fid=312978532265364374
[G3 Android Development] lucbondar:
Excelent!! thanks!
[G3 Android Development] vbenkovskyy:
Dear DEV fix this BUG please.

Install via Sideload for secondary roms option not works. On PC:

And after it screen goes on and off, on and off... Tried different ZIPs everything the same.

Install via Sideload for primary rom option works well.
[G3 Android Development] farangcm:
Red & Blue Light Security Error

I tried TWRP-multirom-20161010-d855.zip and multirom-20161010-v33b-UNOFFICIAL- d855.zip on my 16 GB D855 and got the red and blue light security error every time.I "boot system" after installing MultiROM to boot a secondary ROM (the Inject MultiROM box was checked). I tried with both AOSP-LP-777-Kernel_d855-16G-R22.zip, which I normally use, and kexec-AnyKernel-20160620-d855.zip, which I only use if the R22 kernel doesn't work with a ROM. I tried to go back to version 33a files, but I couldn't get in Download mode or even charge the phone without getting the red and blue lights. The phone stayed that way for a couple of hours, while I tried simple solutions I found on the internet. None worked.Then, miraculously, the red and blue lights just turned off. I almost foreswear-ed MultiROM, but now I am back on version 9/7/2016 33a again.

Allen
[G3 Android Development] PanagiotisGreece:
is there any posibility to support also lg g3 d858
[G3 Android Development] vbenkovskyy:
You CAN get into Download mode! Try again. I had exact situation.
[G3 Android Development] tiendat1295:
Can anyone flash Fulmics as secondary rom (primary rom is aosp)? I was stuck in "Updating kernel" at the end of the installation of Aroma installer
[G3 Android Development] marcdw:
Flashing kernels on secondary ROMs takes a very very long time. Could be up to two hours in some cases.

So you probably weren't stuck.

Best bet is to backup primary ROM and wipe. Flash stock(-based) ROM and back it up. Wipe and restore your primary.

Use backed up stock ROM as source when adding secondary ROM.

More steps but a whole lot quicker.

If you're primary uses a kexec kernel, don't forget to inject it.

Should be more info in the first few posts.

Samsung Galaxy Light SGH-T399, CyanogenMod CM12 ROM, Tapatalk 4.9.5
[G3 Android Development] tiendat1295:
Thank you so so much. :good::good:

Which one do you recommend as primary rom: aosp-based or stock-based? And also is there a way to share app data between roms like data in Internal Sdcard/Android/data?
[G3 Android Development] DuMKaSD:
Try flashing 21C modem over the ROM that's not booting. Got crDroid and Fulmics 6.6 running in dual boot, no issues so far aside from whatever the ROM bugs are
[G3 Android Development] UniX1rm:
Thank you, will give that a shot.
[G3 Android Development] {101}darkvoid090:
Update on F400 Multi-Rom v33b

First of all I would like to thank the developer for the update. I have finished testing today and have came up with the following conclusions:

(Using fulmics 6.6 as primary, DU 10.5[AOSP] as old secondary and attempting to flash resurrection remix 5.7.4 [CM13]as a new secondary as well as flyme OS [Android 5.1 base])

1- Flashing new secondary roms on v33b causes security error on boot, no matter what I try the error will persist.

2- This error also causes the primary rom to hang on lg logo on boot, while old secondary boots to recovery instead of booting.

3- Restoring boot partition for primary rom restores functionality for main and old secondary rom, but attempting to boot the new secondary rom brings the issue back again. :(

4- The workaround for me was to flash back to v33a, everything works normal again( Flash rom then Mr.Bump.zip), and I was able to add a new functional secondary (RR5.7.4) but no support for android 7.0 which I don't mind currently but some people might be interested in. :confused:
[G3 Android Development] bryan2894:
Can you get me a copy of the recovery.log after flashing secondary with v33b?
[G3 Android Development] bigcletus:
how are you guys running Fulmics as a primary rom? I thought you needed a kexec patched kernel for that and I was not aware of a kernel available that has this feature on stock based roms?
[G3 Android Development] rndlgna:
Kexec kernel is optional as of multirom v33a
[G3 Android Development] bigcletus:
Thanks. Can I ask what is different between the a and b versions? I could not find info on this.
[G3 Android Development] marcdw:
These posts may provide some info.

v33a

http://xdaforums.com/showthread.php?p=68388958

v33b

http://xdaforums.com/showthread.php?p=68900839

Samsung Galaxy Light SGH-T399, CyanogenMod CM12 ROM, Tapatalk 4.9.5
[G3 Android Development] bigcletus:
Did you get it working? I'm having the same problem with 7.0 Roms. If I flash an older modem on the secondary ROM, it still won't boot and my primary ROM cannot make calls until I flash 30d back over.
[G3 Android Development] rndlgna:
You don't need to flash the modem on 2nd, just edit the update-script inside the zip file and remove the assert baseband line so it won't give you no 21c modem error.

But yeah I'm having some trouble also with v33b, I can boot succesfully with 7.0 on 2nd rom after flashing mr. bump on it but if I reboot the phone it will give boot verification error. I went to recovery there's an error no primary_boot.img on the log, then I flash mr. Bump on primary and try to boot it but the screen just goes black. So I went back to recovery again and restore the kernel on primary rom, now I can boot to primary rom but I can't boot to 2nd rom anymore (boot verification error). Tried with both v33b versions on d855.
[G3 Android Development] UniX1rm:
I actually got it working, but was a little buggy, so installed crdroid latest version. Bluetooth works in it for the tmobile variant and have that standalone!
[G3 Android Development] cidxtc:
Flashing modems applies to all roms installed. There is no way (yet anyways) to have modems installed for secondary roms.
[G3 Android Development] bryan2894:
MultiROM v33c - TEST

Need testers for a new build. This build should fix issues with booting secondary roms. If there are any errors flashing, or if there are still issues booting roms, try to provide a recovery.log. You can do so in TWRP, by going to Advanced > Copy Log.

Test Builds: https://www.androidfilehost.com/?w=files&flid=126252
[G3 Android Development] takis:
Why is multirom manager apk force closing on my d855? Has this been a known issue? (Happened ever since September builds of it i think)
[G3 Android Development] bryan2894:
I'll need a logcat
[G3 Android Development] lucbondar:
I got this trying to boot crdroid 7.1 as secondary (cm13 primary)

d851, today multirom and twrp builds.

http://pastebin.com/bhx7e7aj
[G3 Android Development] bigcletus:
I have the tmobile version as well, d851, when you say standalone what are you referring too? I have yet to get a 7.0 rom to boot as a secondary. Tried a couple different roms. It just sits at the LG boot logo. I was considering flashing as a primary but haven't tried that yet.
[G3 Android Development] UniX1rm:
I mean by standalone thr regular twrp
[G3 Android Development] bryan2894:
Can you test the updated multirom installer to see if it boots now?

Link: https://www.androidfilehost.com/?w=files&flid=126252

Have you tried restoring SELinux contexts? From recovery, in the MultiROM menu, select List ROMS and choose the ROM that doesn't boot. Then choose the "restorecon" option. After that, try booting secondary rom again
[G3 Android Development] suljo94:
40 is same as always 0= over sharpening is gone completely but colors look washed out a bit try 15 till 20
[G3 Android Development] Illogi.xbone:
Cannot get secondary rom, made from a backup, to load at all.
[G3 Android Development] RL77LUC:
Tried your patch file on D855 16gb kernel, it doesn't seems to work. After reboot, the kernel is loading during a looooong time (1-2 minutes), and then I see stock LG animations, but it doesn't stops... (bootloop).
[G3 Android Development] Illogi.xbone:
Wrong post to quote. =D
[G3 Android Development] RL77LUC:
Fixed. Thanks :)

I may have found the solution thanks to a [MENTION=4794976]777jon[/MENTION] commit (lowmem support)...