yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] bryan2894:
Can you get me a logcat of the crash?
[G3 Android Development] ppajdek:
Thx, will test in on d855
[G3 Android Development] Antidote03:
Hi, I recently installed Multirom TWRP with the latest multirom 33e, i have lg g3 (d855) 32gb primary ROM fulmics 8.0 stock kernel tried to install RR 5.8.5-N as secondary rom by add rom select the option (enable system mode e.g. Magisk) but cannot see the secondary ROM i see only the internal ROM , tried again without tick the option the secondary rom installed and booted normally but no magisk root (Magisk is not installed) any idea thanks in advance

tried to boot to the secondary ROM from the apk ( MultiROMMgr-debug-20180216 )

An error occurred

Shutting down MultiROM to avoid data corruption.

report this error to the developer!

DEBUG INFO
[G3 Android Development] mtkmanjaro:
Here is the log dude
[G3 Android Development] marcdw:
All good on my D851.

As warned, secondary ROM wouldn't boot. Backed it up beforehand. Removed existing, restored backup, good to go.

General question. In an Axon 7 thread someone mentioned that TWRP 3.2 no longer breaks up files when backing up. So for instance /data would be backed up as one huge file larger than 4GB. Backups would fail on FAT32 drives.

I couldn't test that myself as I multiboot on my Axon 7 so backups are to be done via an app, not TWRP.

For the G3 all of my drives are FAT32.

So does 3.2 not break up files anymore? After work I guess I'll check for myself.

EDIT: Nevermind. Had the time and just did a backup. As expected data was broken up into little bits. Guess the issue was with that particular Axon 7 TWRP 3.2.

I did notice there is no longer an option to backup the modem. Is that normal?

LG G3 D851, CyanogenMod 12.1 ROM, Fechda Kernel R7, MultiROM, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
The log doesn't show any details of the crash
[G3 Android Development] mtkmanjaro:
OK sorry wrong file, try this
[G3 Android Development] mtkmanjaro:
After multirom manager crash in my device I installed manually then I flashed crdroid 8.1 as secondary rom, apparently all is ok. boot manager show me crdroid in the boot list, but i won't be able to boot take me at the firmware update screen

so my question is this is due to i done something wrong with the installation process or is because multirom don't support 8.1 roms
[G3 Android Development] ppajdek:
Installed latest crdroid 8.1 as secondary but it stuck on lg logo, N roms works ok.
[G3 Android Development] ppajdek:
It seems the problem is this commit, reverting it and the corresponding commit in device tree allowed crdroid to boot. Im using kexex workaround since my primary is stock with xceed kernel and it doesnt have kexec patch, [MENTION=2107489]bryan2894[/MENTION] anything can be done to solve this?

Dont know if it work ok if the primary have kexec patch.
[G3 Android Development] bryan2894:
Can you guys test this to see if Oreo ROMs can boot now as secondary?

D851: https://xdaforums.com/devdb/project/dl/?id=28741

D855: https://xdaforums.com/devdb/project/dl/?id=28742
[G3 Android Development] Prowler:
Tried latest twrp and mr + RR O as secondary on sd card but got stuck on download mode when I try to boot it.

I totally forgot to make logs, i'll do later if necessary.

D851
[G3 Android Development] ppajdek:
Lates crdroid - no boot, stuck on Lg logo

Btw reverting the kernel commit is enough.

D855 32G
[G3 Android Development] joeywen0830:
[MENTION=2107489]bryan2894[/MENTION] I use stock Marshmallow with stock kernel installed, but whenever I flashed the latest 2018-02-16 multirom and reboot, I always immediately skip into fastboot mode and cannot boot into primary rom. Any fix for this issue? Thanks.
[G3 Android Development] bryan2894:
Try reinstalling your secondary ROM or flash the MultiROM Reinjection script from HERE to reinject the updated MultiROM binaries to your secondary rom.

I just tested an Oreo ROM on both internal storage and external sdcard and they both booted.

What device do you have?
[G3 Android Development] bryan2894:
Also, for those trying to install Magisk on a secondary ROM, newer releases don't seem to work. Magisk v14.0 seems to be the latest release that works for secondary ROMs.
[G3 Android Development] joeywen0830:
[MENTION=2107489]bryan2894[/MENTION]I have a D855 32GB, also I have difficulty booting into secondary roms with marshmallow, they just stuck on the LG screen.
[G3 Android Development] Prowler:
ok I've tried with crdroid and resurrection remix, both 8.1 (i think this is the trouble since Oreo 8.0 boot just fine even before the update) and still stuck in download mode when I want to start the rom.. I mean, after install, reboot, choose 2nd rom, it stays a few seconds in bootlogo till finally phone is restarted and enter to download mode automatically.

I've already tried with all the latest, twrp, multirom, mr injector.. nothing works for me.

I have AOSPA 7.3 as primary btw.

OT: oh I just realised that nkk71 has passed away ?
[G3 Android Development] ppajdek:
Nah, didnt work, it only boots if i flash my custom kernel without the "mount system partition" commit.

Tested on crdroid and rr oreo 8.1.
[G3 Android Development] Spaceboy60:
Crashes for me to when it gets to updating metadata
[G3 Android Development] mtkmanjaro:
Same here i get stuck at download mode.

Lineage 14.1 as primary i try crdroid as secondary rom but is impossible there's no way to make crdroid boot and multirom app still crashing.
[G3 Android Development] Antidote03:
[MENTION=2107489]bryan2894[/MENTION] I use Fulmics (stock based rom )with stock kernel installed as primary,crDroid Oreo secondary , but whenever I flashed the latest 2018-02-16 multirom and reboot, I always immediately skip into fastboot mode and cannot boot into primary rom. fixed by restore the boot,img from my nandroid backup

any fix for that

thanks in advance
[G3 Android Development] bryan2894:
Here's another test build for those with Oreo ROMs as secondary.

D851: https://xdaforums.com/devdb/project/dl/?id=28900

D855: https://xdaforums.com/devdb/project/dl/?id=28899

If MultiROMMgr is still crashing for you, I'll need logs.
[G3 Android Development] Prowler:
Unfortunatelly it still not working for me.. same procedure as before: mr test, reboot recovery, flash oreo 8.1 rom as secondary, try boot it, stuck in lg logo.

btw I tried a 7.1 rom as a secondary and doesn't boot either, the phone just reboot into recovery :eek:
[G3 Android Development] admiral.ackbar:
I ran into the same issue attempting to install Fullmics as a secondary. I swapped my primary Oreo install to a secondary and was able to install Fullmics 8 as primary. Both boot now, but Magisk after 14.0 may cause trouble on secondaries. Hope this helps if you still have the problem.
[G3 Android Development] bryan2894:
Ok, here's another test build. I think I finally figured out the actual issue. Oreo ROMs don't seem to be booting as secondary because the SELinux contexts aren't set correctly. In Oreo, the file contexts is split into two different files instead of just one, which the recovery hasn't been updated to account for.

To test you'll first need to flash the recovery.img, then reboot back to recovery and flash the multirom*.zip. Next, you'll need to reinstall whatever Oreo ROM you have in your secondary slot. If the ROM still doesn't boot, use the "restorecon" option in recovery for the ROM that doesn't boot.

Links:

D851

Recovery: https://xdaforums.com/devdb/project/dl/?id=28960

MultiROM: https://xdaforums.com/devdb/project/dl/?id=28959

D855:

Recovery: https://xdaforums.com/devdb/project/dl/?id=28962

MultiROM: https://xdaforums.com/devdb/project/dl/?id=28961
[G3 Android Development] eeeelinen:
getting fastboot

Sadly, it's not working for me, I'm just getting "fastboot started"
[G3 Android Development] mtkmanjaro:
Sorry bro still not working, i don't have a log because my sdcard is death
[G3 Android Development] armandioan:
Fastboot here, as well. No need to install secondary ROMs just tap on inject boot and the phone goes into fastboot after reboot
[G3 Android Development] SDA93:
Clarification about TWRP

1. Does anyone know if the TWRP from this thread is compatible with roms that use aroma installer?

2. Another question

Is the f400 recovery also pre-bumped?

I am asking that because it is written that "D850/D852/D855/D856/LS990/VS985 recoveries are pre-bumped".

Thank You.
[G3 Android Development] marcdw:
[MENTION=8925047]SDA93[/MENTION], yes, this TWRP works with AROMA. This and the Artx TWRP I've used/use on the G3 without issue.

Don't know about the f400 being pre-bumped or not.

Moto G5S Plus XT1806, BootleggersROM-Shishufied, microG (NoGapps), MultiROM, Tapatalk 4.9.5
[G3 Android Development] SDA93:
Thank you.

One last question. (Or two :D)

To flash OREO roms, i will need this TWRP, because it is based on 3.2.1, right?

On the other end, ArtX TWRP is based on 3.1.1, so this one can't flash OREO roms?
[G3 Android Development] marcdw:
[MENTION=8925047]SDA93[/MENTION], I believe you are correct on both points.

Since I lost my sdcard slot I stopped flashing on my G3. Haven't tried Oreo since early alpha crDroid.

Hopefully someone can confirm.

ZTE Axon 7 A2017U, AospExtended v4.6 ROM, microG (NoGapps), Multiboot, Tapatalk 4.9.5
[G3 Android Development] son_91:
Any one tried to flash oreo 8.1?
[G3 Android Development] mtkmanjaro:
Yes, but don't boot because multirom recovery is broken, and brayan, still not fixed
[G3 Android Development] eeeelinen:
Anything new?
[G3 Android Development] :
It's working !

A very special thanks to developers who made it possible, hope to see support for 9.0 pie ROMs as soon as possible.
[G3 Android Development] marcdw:
So, is that still the case for folks? I've been out of the game since my sdcard slot failed back in August 2017. All of my secondary ROMs reside on an ext4 partition on the card. Had a second G3 but its slot died not long after I got it so I went back to the first, running two older ROMs. After years that beloved phone finally breathed its last breath. Now I'm on my third running all those ROMs again.

As far as Oreo goes all I could do is lurk and read but I wasn't about to replace my daily driver with it. So today I finally decided to test MultiROM and Oreo on my D851.

Primary is PAC-MAN Lollipop (since 2015) with Nebula kernel (has kexec).

Installed the 2018-03-24 TWRP that [MENTION=2107489]bryan2894[/MENTION] posted. Rebooted into it and flashed MultiROM. Rebooted again and flashed crDroid 4.6 Oreo. It boots and runs just fine as a secondary. I expected it wouldn't work given what I've read.

Got a couple of days off to test some of the other Oreos and see how they fare. As long as they don't have early system mount things might go well.

Moto G5S Plus XT1806, OmniROM, microG (NoGapps), MultiROM, XDA Legacy
[G3 Android Development] marcdw:
After messing around I realized that Oreo and MultiROM are fine on the G3. However, on my Moto G5s Plus where I also use MultiROM and Oreo ROMs (MR-TWRP is 3.1.1) I got hit by a new "feature" in Oreo ROMs. Around July they introduced something called early system mount. This does not work with MultiROM. ROMs will flash fine but on boot they will crash it. I have half a dozen ROMs running on it but not the latest because of that. Then the MultiROM dev ended support so no chance of a fix there. I might be the only one on the device using MR. The tag and info for it was even removed from the device's Telegram channel.

Apparently that's the same here. I flashed the last Liquid Remix 9.1.5 as well as AospExtended. MultiROM crashed the same way as on the Moto. crDroid and Liquid Remix 9.1.3 work just fine here. The issue is early system mount and not Oreo in general.

I haven't checked upstream but I gather that MultiROM probably hasn't been updated to deal with that. So one can't blame our dev for anything.

LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
[G3 Android Development] damod11:
Hi. Will it work with fulmics 8.0 ?
[G3 Android Development] marcdw:
Yes, it should. I've had Fulmics as a secondary in the past on my D851. Currently Clean ROM is in use (as far as stock-based goes).

Moto G5S Plus XT1806, balanceOS 2.0, MultiROM, XDA Legacy
[G3 Android Development] damod11:
I tried with fulmics 8 as primary and twrp returns some error about the boot saying ill need to re flash the rom. Ive restored backup for now. Ill try clean rom but i really want fulmics 8
[G3 Android Development] marcdw:
Oh, I thought you meant Fulmics as a secondary. Fulmics as a primary "should" have no affect. It should flash and work normally. I'm not exactly sure what you're doing.

Can you tell us what items you're using. MultiROM-TWRP 3.2.x or Artx twrp should work fine for flashing Fulmics.

I have a second G3 that I can test on. I haven't had Fulmics as a primary in ages. Might be some conflict I'm unaware of so I might give it a try and see what happens.

ZTE Axon 7 A2017U, Candy7 v5.2 ROM, Google free - no microG, MultiROM, XDA Legacy
[G3 Android Development] damod11:
Hi. im staying on fulmics single boot for now. dont have time for playing now :o . thanks anyway
[G3 Android Development] :
i get fastboot mode started after

full wipe

flashing cleanrom

injection of boot sector
[G3 Android Development] ins5736:
VS985

I tried installing multirom and can no longer access recover or download mode. Any help would be greatly appreciated.

I get a "secure booting error" when trying to start download mode (hold volume up while connecting to USB) and when trying to hard reset into recovery (hold volume key down when powering up). After the download mode fails, the screen turns blank but I believe the device is still on. After the recovery fails, the screen is off and the LED cycles blue and red.

I've tried ADB in both scenarios, and the adb devices command doesn't find my phone. Please help me!

EDIT: Got it back. Phew!!!
[G3 Android Development] Eliminater74:
Sounds like you didnt follow the instructions completely, Are you sure you cant access recovery? (Hold Vol Down + Power, wait for LG logo (let go for 1 sec, then Rehold Vol Down + Power)) That should take you to recovery..

I dont know what you did. but That download more error cant be from the multirom nore twrp.. Multirom is harmless exec files that fit along side twrp and also kinda like a 2nd bootloader..

Did you flash that oversharpping fix?

Someone here might be able to better help you then I.. I never seen nor heard of a problem like that..

I hope you can get back into recovery to fix this. If you did flash that. maybe you used a wrong value thats causing your screen to black out. But still working.. If thats the case.. you might have to blind reset it..

and that depends on how well you know your phone, and all commands and how long it takes to get there.
[G3 Android Development] ins5736:
Thank you for the response. I flashed the modified TWRP, then kernel, then installed multirom (all for the VS985) but not the oversharpening fix. I can't access the recovery at all. Following the key presses you describe. I get the LG splash with the secure boot error and then it loops. I rebooted from multirom to grab a new rom to try to install as a secondary and was in the situation described in my post. I fear it installed to the wrong partition and overwrote laf and/or boot.

EDIT: Well, that was weird. I was still Googling, and the LG site http://www.lg.com/us/mobile-phones/VS985/Userguide/097.html said to hold power and volume down for 10 seconds. That got me back to TWRP, and Life's Good.

I may try this again, but probably not for a day or two.
[G3 Android Development] RL77LUC:
After the download mode, if the device is still on, could you plug it to a computer and see if it's detected. If you laf is erased, that should bring you to fastboot mode...
[G3 Android Development] Eliminater74:
Yea fastboot mode, you will be able to flash from fastboot mode at least....... I hope so.. I hate to have someone brick their phone over this.

I cant see how you could of flashed to the wrong partition.. I mean multirom doesnt let you flash to anything other then your open partitions.
[G3 Android Development] engine95:
I'm on vacation for a week, but I still will work on it.

I made one for the 850, and was told it worked. But I haven't heard anything else or otherwise.

I also heard that it'll work for the 855 16g, but that was only for one person. I pulled those tests builds. I should've used testers instead of just throwing it out there.

Eliminator and I tried to get it for the 990, and it worked for CM/AOSP, but stock was a no-go at all.
[G3 Android Development] teddy0209:
just ask the dev there mate, I'm sure he will update his kernel if you point it out... =)
[G3 Android Development] RL77LUC:
I'm also working on kernels (AOSP for now, but I plan to release a stock one after). For the D855 16gb variant, you'll need to merge an additionnal patch (by [MENTION=4794976]777jon[/MENTION], look in his GitHub) to make it compatible, because it's not the same memory address, but it'll be working with that ;).

---------- Post added at 03:59 PM ---------- Previous post was at 03:56 PM ----------

Gabriel kernel will not work. This multirom uses a different kexec-hardboot patch ;).
[G3 Android Development] Edde3d:
Finally got it booting. Yay. Thanks for the tips. A stock kernel would definitely be nice to have. But it really doesn't matter. Thanks.

Kickin it on my VS985
[G3 Android Development] arjuna_:
This might be so obvious that it could be missed ( I made this mistake at least 5-10 times and kept getting an unsecured error or something about updater error binary or something) but you have to have a ROM already flashed (if using the 777jon's kernel have an AOSP ROM flashed). Then install TWRP, the multirom zip, the 777jon's kernel, and the oversharpening fix. Only after doing all of that was I able to get to multirom on my d850. Again I might be the only one doing it without an internal ROM installed which is why I had so many problems but maybe someone else can benefit from my stupidity lol.
[G3 Android Development] tetrahedonism:
That would be fantastic! There are a few of us around, and I've been thinking about rolling out some stuff for the D852 since we don't get a lot of support. I mean, I totally understand why but additional support is always nice.

Thanks! I really appreciate it! :D
[G3 Android Development] Edde3d:
I've found that flashing the kernel last really helps. I tried this and it worked nice.

1. Have aosp rom installed

2. Boot into recovery and flash modified twrp. Reboot into recovery

3. Flash kernel

4. Flash multirom

5. Wipe cache/dalvik

6. Flash sharpening zip

7. Flash kernel again

Reboot....

Step 3 may not be necessary but that was what I ended up doing and it booted right up.

Kickin it on my VS985
[G3 Android Development] Eliminater74:
Yea [MENTION=4794976]777jon[/MENTION] uses anykernel which isnt a boot.img. its just the ramdisk, you need to have a kernel already installed. And most likely its has to be the same type, as 5.1 ect. ect..

Its ok.. dont worry.. ill do it.. I have been building MultiRom for 7 months now.. Only reason I said hold a few days, because ill have to fork your device tree over and make modified changes and stuff like that.

im kinda lazy right now. and Didnt wanna do it yet.. :) but once done it only takes about 30 mins to build tops.......

Glad you got it working.........
[G3 Android Development] tetrahedonism:
Oh I didn't wanna take your thunder away, I meant more rom-wise. ;D
[G3 Android Development] iluvamk:
Which kernel did u use? Have tried but get insecure boot error.
[G3 Android Development] redbeard1083:
D850: for the life of me i cannot get a second rom to boot. i've used two kernels with the kexec patch applied to the internal rom following the steps in this and the d850 thread and multirom tells me i need to install a kexec kernel. primary boots fine. no clue what's I'm doing wrong.
[G3 Android Development] Eliminater74:
Post your Primary Rom type.. and post your Kernel version..

###################################################################

NOTE: If you flash a boot.img that has the kexec patch by it self. you must then click advanced then multirom, then click inject current boot img.

Or else you wont get the menu...................
[G3 Android Development] redbeard1083:
ROM: CM12.1

Kernel: AOSP-777-Kernel_d850-R10
[G3 Android Development] RL77LUC:
Flash ROM (and gapps if you need it), then multirom zip, then kernel.

That should work.
[G3 Android Development] Edde3d:
I used the 777jon kernel that's linked in post 3

Kickin it on my VS985
[G3 Android Development] iluvamk:
Have u been able to install a secondary. Finally for MR to boot with primary but when installing secondary TWRP goes blank half way through and I have to pull battery.
[G3 Android Development] Edde3d:
I have Lion rom and cloudy 2.5 as my secondary roms. But I installed those as nandroids.

Kickin it on my VS985
[G3 Android Development] redbeard1083:
i tried a clean install and did exactly the following:

1. flash rom

2. flash gapps

3. flash xposed

4. flash supersu

5. flash kernel

6. flash multirom

7. flash oversharpening

8. flash kernel again

9. flash pa rom as secondary

phone boots to OS selection screen and primary boots. secondary gives kexec error when booting. i'm at a loss on this.
[G3 Android Development] RL77LUC:
Oversharpening fix is not necessary if you flash kernel after multirom ;). Also, you don't need to flash kernel before multirom.

But I don't think that's the problem. Could you give us the kexec error ? It is probably a multirom bug.
[G3 Android Development] redbeard1083:
booting primary rom gives no error. trying to boot secondary rom tells me that i need to install a kexec kernel to the internal rom. i'm not sure if i'm missing a step somewhere, but what i posted above is exactly what i did.
[G3 Android Development] Edde3d:
I flashed sky dragon 5.0 and when I try to boot it just sits at the LG screen. No led flashes or anything. I installed 2 other roms from nandroids and they work fine. Hmmmmm

Kickin it on my VS985
[G3 Android Development] RL77LUC:
Check your device info parameter and take a screenshot, please. Especially "kernel version" section.
[G3 Android Development] redbeard1083:
will do when i get home. not permitted to even have my phone past the front doors of where i work.
[G3 Android Development] Eliminater74:
Kexec error is always going to happen if you dont have a kernel that supports the kexec patch. What I would need from you is the log. Prob, /proc/last_kmsg log...........

when a boot fails. its always posted to your proc/last_kmsg but only for a short time.. after the next reboot it will delete it self. I need the log so that I can

see where and why its giving you that error.. Mr [MENTION=3418703]Tasssadar[/MENTION] put alot of error traps in MultiRom, so you can find the errors quickly. If I cant

figure it out.. he can just by looking at the log.

That goes with anyone.. I need logs posted so that I can help you beter.. We can sit here and go round and round in circle all day what it could be. but it would be faster if logs

got posted. There was a guy on here that posted a log to me about it not working right. I found the error within seconds. Which is was the boadnames. Since I forgot to add

the device name to it... So plz people post or send me a log to check out. (logs: proc/last_kmsg ) Remember that log is only good for the first boot after a unsuccessful boot..

Use KernelAdiutor to help you out with logs if needed.......
[G3 Android Development] RL77LUC:
He said he uses 777 r10, and it supports Kexec-Hardboot ;).
[G3 Android Development] joshuajones:
I couldn't get it to flash as secondary either, so I flashed as primary then copied it to secondary instead. Works fine now