yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] GawciuX:
Second option is flash normal TRWP via ADB but i can't find working download mode drivers on windows 10.
[G3 Android Development] cidxtc:
Well that sucks. I know when twrp 3 was first released for our device it had that same issue. Hopefull it will be fixed soon by the dev so others dont have the same issue.

I still have the last builds from eliminater for the 851 so I have not actually tried these
[G3 Android Development] MrComputerRevo:
Does download mode support adb? I don't think it does.
[G3 Android Development] jclendineng:
Yep recovery is broke. DO NOT INSTALL!! Wait for dev to fix. I am almost done unbricking, I probably wont do multirom as I only really wanted miui to try.
[G3 Android Development] bryan2894:
Weird, the bump script is added and should auto-bump the recovery image. And it looks like its actually run when the recovery image is created.

I'll look into it but for now I've hidden the update for all bumped variants.
[G3 Android Development] cidxtc:
Talk with eliminater. It is actually an issue with twrp and our device. He had the same issue when twrp 3 was released.
[G3 Android Development] marcdw:
It's always been Nebula or 777 kernels. Primary ROM has to be (should be) AOSP/CM ROMs.

My primary is PAC LP from early last year. I haven't tried MM ROMs/kernels as primary. Probably won't either as I'm not quite pleased with MM. Maybe for testing I might.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] thecdn:
Thanks. The other disasters scared me but it looks like things are ok with the D851. Will probably try tonight.
[G3 Android Development] bryan2894:
Ok, I think the issue was with the script I was using to flash the recovery. I uploaded a build for D855 users to test. Let me know if you can actually reboot into recovery with this one. Make sure you can recover first if you can't boot into recovery.

Test build: https://www.androidfilehost.com/?fid=24545065934258453
[G3 Android Development] marcdw:
Yes, the D851 builds seems to work well but there is a problem with AROMA. If you like to flash AROMA Open GApps or Theme Ready Gapps you'll be out of luck. If not then you'll be good to go.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] marcdw:
Okay folks, here's one of those stories with good and bad.

In the aCC kernel thread someone asked if the kernel works with MultiROM since kexec boot patch is listed as a feature. Didn't work for me.

My primary LP ROM was backed up and replaced with AOKP MM for testing.

Once that was done I thought it's time to finally check out the D851 30D stock ROM.

The plan was to flash stock, back it up, use the backup as source for a secondary ROM. Stock-based LPs like Fulmics, Ti-X, etc. would only run as secondaries. Never as a main. Not sure why.

So, after flashing and backing up I decided to see if it would run. The stock ROM runs just fine, thank you.

The bad news (for me).

I had no idea flashing/running it would wipe out my internal storage. Googobs of stuff, gone. ROMs, gapps, kernels, tools, apps, TiBu update zips, etc. etc. Some things I probably can't retrieve again. Sure a lot of things are on SD but a helluva lot wasn't.

Sucks big donkey you-know-whats. Glad I have another day off to fix some of this mess.

The good news (for the rest of ya).

Stock 30D MM is running as MultiROM primary using Nebula 12.5-MM with no issues, so far.

MultiROM was wiped out with everything else so why not experiment.

Went into TWRP, flashed Nebula 12.5-MM.

Flashed MultiROM.

Injected boot sector.

Reboot.

Boot menu comes up. Now to see if ROM will start.

ROM booted up just as quick as with its default kernel. Moved around here and there and then installed Kernel Adiutor-Mod so I can verify.

I had/have no intention of running stock as primary. I may change my mind.

I did install it as a secondary before knowing it would work as above. Will wait before running it.

LG G3 D851, Validus ROM, Tapatalk 4.9.5
[G3 Android Development] marcdw:
Hmm, "Side effects may include" not being able to boot into Resurrection Remix or Dirty Unicorns. Stuck at the LG logo. Yet Validus boots up fine.

Might have to reflash those. ? ?

LG G3 D851, Validus ROM, Tapatalk 4.9.5
[G3 Android Development] jclendineng:
Moral of the story, backup to extsd before doing something risky and understand how to fix a soft brick :D it was actually fun. I haven't had to fix anything like that in a long while. Quite enjoyable besides taking a good part of the afternoon.
[G3 Android Development] marcdw:
Heh heh, yep.

At least I know I can use stock as primary. Alas, I needed my working primary environment so I wiped out the stock ROM. I will try it as a secondary though.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] cidxtc:
Only issue I have had with stock (fulmics) as primary (nebula kernel) is with headphones. You have to connect the headphones then reboot for them to work and then reboot afterwards to have normal speaker operation.
[G3 Android Development] marcdw:
ACH. That's what I forgot to test before removing it. I couldn't remember what the issue was with stock Lolli and Nebula.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] thecdn:
I successfully flashed multirom-20160515-v33-UNOFFICIAL-d851.zip then TWRP-multirom-20160515-d851.zip. I have the latest 777 MM kernel installed in my current rom, brokenos.

When the phone starts up I am presented with the multirom boot screen with my primary (and only) rom set to boot in 5 seconds.

When I go into recovery I am presented with the Multirom TWRP v3.0.0-0 screen, then Team Win Recovery Project 3.0.0-0 - used to have 3.0.0-2 (I think).

When I look in Advanced, there is no option for Multirom, there is no Multirom option anywhere.

Have I left something out or missed something? I flashed both twice and it was successful both times.

I'm kind of confused about this......
[G3 Android Development] marcdw:
[MENTION=4010814]thecdn[/MENTION], technically you flash TWRP-multirom first. Reboot back into it and then flash multirom. Since you got the boot menu things seem okay on that front.

In TWRP the MultiROM menu is not under Advanced. It's right there on the first page of menus.

I lost my screenshots so I can't show what it should look like.

LG G3 D851, Validus ROM, Tapatalk 4.9.5
[G3 Android Development] thecdn:
Thanks for the quick reply. On my first page I have Install, Wipe, Backup, Restore, Mount, Settings, Advanced, and Reboot. There is no room for another option unless they shrink and make room for another row.

I will follow the flashing method you mentioned and see if that makes a difference. If not I have a nandroid backup of stock MM that I will restore, apply the kernel, and then flash multirom to see if that makes a difference.
[G3 Android Development] marcdw:
[MENTION=4010814]thecdn[/MENTION], the description of your first page is definitely different.

I just booted into TWRP and took a screenshot.

I tried the 20160515 but had an issue with AROMA so I rolled back. The screen was the same though.

Refer to posts #2 and #3 for more info.

Spoiler content hidden.

LG G3 D851, Validus ROM, Tapatalk 4.9.5
[G3 Android Development] ZenS78:
D855 Multirom Recovery

I have successfully flash TWRP-d855-test.zip

The first restart phone has received wipe data. I restore the data from a nandroid backup.

Now multirom recovery phone restarts fine. Erasing the data was no longer.
[G3 Android Development] shakibalawouz:
Um, i just flashed the only TWRP available using the only available link(in the first post) although it says D851 (my bad) and recovery is corrupted somehow, entered fastboot mode with a 780 error code, now i'm trying to figure out how to flash a new recovery using the phone alone(flashify). Any help would be appreciated.

Nevermind got it to work cz i only corrupted the recovery image.
[G3 Android Development] bryan2894:
MultiROM - 05-26-2016

I reuploaded the MultiROM & TWRP builds for all supported devices. The builds have the updated script for flashing recovery which should fix the issue before with bumped devices
[G3 Android Development] hroen_al:
Flash Order

TWRP

Kexec hardboot patched Kernel

MultiROM Installer

Bump Script Mod Modified

Kexec hardboot patched Kernel?

what is that?

kustom kernel or...??

I have d855 and want to try multirom

maybe stock as primary and brokenos as secondary
[G3 Android Development] mrk2006:
YEah, I wanted to know that too... I have a D855 with stock (v30c), marshmallow, I flashed the modified TWRp, rebooted in TWRP, flashed multirom, didn't flash anything else and reboot. Now it goes "secure booting error". If I enter recovery, it automatically flash 'openrecoveryscript' and reboot, again on "secure booting error". What should I flash? I'd like to have CM13 as first rom, and the stock rom as secondary.

Edit. I did all again, flashed modified TWRP, reboot TWRP, flahshed multirom, flashes also nebula kernel, tried to flash CM13 but gave me an error (can't install on top data, or something, error 7). Tried to 'inject boot sector" - error as well. Rebooted phone, it shows LG logo, shows "powered by nebula kernel logo" but the screen then turns black and I can do nothing, i had to remove the battery. If I enter recovery, it automatically flash that openrecovery thing again!!

Any help?
[G3 Android Development] marcdw:
This might be a really simplified explanation. A kernel with the kexec boot patch essentially allows for booting/starting/launching another kernel. Handing it off as it were. Having a kernel without the patch is not an option. Make sure to follow all steps and don't exclude anything.

A kernel with the patch is needed for the primary ROM.

[As one Nexus user on G+ mentioned his primary ROM doesn't work anymore but the kernel does so he's still able to boot into secondaries. A nice benefit of MultiROM.]

Kernels with the patch are Nebula, 777, and supposedly aCC. My tests failed with aCC as primary.

Also recently tested Nebula 12.5-MM with D851 30D stock ROM as primary. Worked okay too but I didn't keep the ROM long enough to put it through its paces with Nebula.

As has been the case starting with [MENTION=5687366]Eliminater74[/MENTION]'s builds only AOSP/CM ROMs are/were supported as primary. Stock(-based) is/was not supported. Stock should run fine as secondary.

[Going old school I restored and am running SkyDragon KitKat stock]

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5

---------- Post added at 09:59 AM ---------- Previous post was at 09:46 AM ----------

[MENTION=5819500]mrk2006[/MENTION] , it looks like you're doing a few things out of order or not following the steps posted.

Also, if you flash CM13 after Nebula then you've lost Nebula. You'll have to reflash Nebula, then inject it.

You haven't mentioned which Nebula you're using. A question has been posed recently if whether Nebula 12.5 and the latest CM13 nightlies even work well together.

I haven't tried Nebula2e unless it was already included in a ROM. I don't even know if it has the patch as I haven't followed that kernel.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] mrk2006:
Hi, thanks for the reply.

As long as it looks like the first ROM can't be stock, i installed CM13. Well, first I installed stock and made a backup of it. Then I rebooted into TWRP and flashed the multirom-twrp. Rebooted into TWRP multirom edition. Went on "multirom", add rom and selected the stock backup rom. Installed it. Flashed Nebula kernel 12.5 MM. Tap "inject current boot sector"... done. Rebooted system. It shows LG logo, then "powered by nebula" logo, and then black screen again :/

Is there anything wrong? Thanks

EDIT! I rebooted, and has appeared a sort of menu. I suppose multirom menu. It asked what location to choose, it was "internal" by default if I read it correctly, and after the timeout of 5 seconds CM13 booted up. It started "optimizing" all apps, but suddently stopped and all turned black again.

Won't reboot by pressing the power button, so i took off the battery, pulled it in again, and rebooted. Again the multirom menu. I selected 'internal', and the CM13 booted up. Now it optimized only 1 app, and then asked me for the system language (ok, so it is a fresh installation...). I didn't had the time to tap on the language, it turned black again.

So I tried boot the secondary rom (stock), but same thing, it all goes black after 15-20 seconds...

Now i'm flashing all stock again via download mode, because the recovery is useless (as soon as I open it, it flash an "openrecovery script" and reboot).

Any ideas?
[G3 Android Development] Eliminater74:
I just popped in to see how things are going....... Looks like they are going good.........

Yea I knew I made the right choice when I asked [MENTION=2107489]bryan2894[/MENTION] to take over for me........

Things have been crazy for me lately, I been in and out of the whole android scene do to issues..................

But, glad to see all doing well............
[G3 Android Development] marcdw:
Would you happen to know if AROMA works with this build? Haven't gotten around to downloading yet.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] bryan2894:
Redownload the new recovery from today which should stop the openrecovery script from wiping data

Not sure; there aren't much changes from the previous build, so if it didn't work previously it still might not work
[G3 Android Development] mrk2006:
Ok I'll try, thanks. But what about the fact it turns all black and unresponsive after a few seconds from when it completed boot?

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Android Development] bdusmc:
no, I'm kind of out of commission for a while

Oops wrong window. Sorry. LOL
[G3 Android Development] Roi007leaf:
From my experience I remember having those issues just with nebula..try different kernel and see if it still happens
[G3 Android Development] mrk2006:
I see... Any suggestions for another kernel? Thanks!

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Android Development] Eliminater74:
Get someone to patch with the new patch.

Im sure someone can patch a stock for you. I never even patched our D851 stock... I left all the stock stuff to other people..

Now let me get this straight, you said everytime after you flash multirom you have to reflash kernel or else you get that security error, Can I ask why you keep installing multirom? you only need to install it once and leave it. till next update. Im sorry if im not understanding you so well.. im American. my lang is blunt and can sound forcefull, I mean no disrespect by it..... Im just trying to figure out whats really happening.. I havent heard any of this on any of the other G3's.. I ported to D850,D855,LS990,VS985 all in one day.. Only reason I even did this, cause people kept bugging me about doing so. I even posted a How to guide on porting Multirom over and nobody did it, So I figured I had a little time, I would do it. and the fact that [MENTION=4794976]777jon[/MENTION] was nice enough to finely add my kexec hardboot patch to his kernel. I figure it was time to now port over the newer multirom so people could take advantage of it... I never thought it would give me a huge headache over it.

I really dont have the time to deal with all of it like that. I build two custom roms for 2 devices and 1 custom kernel for one device, I maintain the multirom. I even work on the MultiRom Manger app to get support for our Devices.

as I have already created a pull request with mr [MENTION=3418703]Tasssadar[/MENTION] with support for our devices. And all that takes alot of my time as it is.. If you or someone wants to talk to me one on one about this, so it can be explained a bit beter, then msg me on hangouts or irc. im on both. But I said, right now. my kernel takes alot of my time.
[G3 Android Development] suljo94:
just flash the oversharpening zip it will bump it But the fact is that for the multirom zip to bump roms you would have to Edit the automated script of the zip and I know that this can cause delays or even Abort the process of something getting to be "official", so let's just do it the hard way and flash the zip and enjoy our soon to be official multirom
[G3 Android Development] RL77LUC:
I have installed multiroms three times, since the first two times, it didn't worked (security error due to multirom zip flashed after kernel the first time, error due to first version the second time). That said, I keep flashing multirom after every rom update, because that way, I can automatically update Cyanogenmod using Cyandelta (and with the automatic flash feature), because without that, multirom will be erased because the automatic installation doesn't seems enable the bootloader injection. That would be also useful for new users, since it's said nowhere that flashing multirom zip AFTER kernel will cause a security error...

Don't worry about language, I take it fine ;). My english is also pretty bad, I'm sorry for that.

Take the time you need, these issues are still minor, since we can fix it by flashing kernel after multirom.

Unfortunately, I can't explain you this in details, since I'm not an android dev, I'm not aware of all advanced things related to signature check and so, but feel free to ask me any question you want in this thread (or everywhere else) if you need it, I would be happy to answer you the best I can ;).

I have no problem with that, flashing kernel after multirom also solve the issue. I just explain it for new users and perhaps a bugfix ;).

That said, maybe [MENTION=5687366]Eliminater74[/MENTION], if he has time, could see the script to add the "bump" section of oversharpening script to his multirom...

EDIT :

[MENTION=5687366]Eliminater74[/MENTION], here's a script to fix security error (by bumping kernel) thanks to [MENTION=2174433]Skin1980[/MENTION] :

#!/sbin/sh
#Livebump for LG G3 kernel
#by skin1980@xda

IMAGE=/tmp/original-boot.img

if [ -z $IMAGE ]; then exit 1; fi
mkdir /tmp/out
/tmp/unpackbootimg -i $IMAGE -o /tmp/out

if [ -e /tmp/out/original-boot.img-ramdisk.gz ]; then
rdcomp=/tmp/out/original-boot.img-ramdisk.gz
elif [ -e /tmp/out/original-boot.img-ramdisk.lz4 ]; then
rdcomp=/tmp/out/original-boot.img-ramdisk.lz4
else
exit 1
fi

/tmp/mkbootimg --kernel /tmp/out/original-boot.img-zImage --ramdisk $rdcomp --dt /tmp/out/original-boot.img-dt --cmdline "$(cat /tmp/out/original-boot.img-cmdline)" --pagesize $(cat /tmp/out/original-boot.img-pagesize) --base $(cat /tmp/out/original-boot.img-base) --ramdisk_offset $(cat /tmp/out/original-boot.img-ramdisk_offset) --tags_offset $(cat /tmp/out/original-boot.img-tags_offset) --output /tmp/image_bumped.img

echo "Bumping the boot.img..."
printf '\x41\xA9\xE4\x67\x74\x4D\x1D\x1B\xA4\x29\xF2\xEC\xEA\x65\x52\x79' >> /tmp/image_bumped.img

If you could add it to your multirom installation zip, that would fix the security error after installation ;).

EDIT 2 : If you need binairies used in this script, you can download the whole zip here : http://xdaforums.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
[G3 Android Development] Eliminater74:
thank you.

Thank you both for that. I know it has to suck dealing with a locked bootloader.. im thankfull that all the T-Mobiles bootloaders are already unlocked.

I will see what I can do.. but if I can add some type of patch to the multirom source, I would have to keep using that patch for every update.. which isnt that bad since the updates are maybe 1 a month or so.

I dont update multirom like people do roms. as its a great product as is.. and [MENTION=3418703]Tasssadar[/MENTION] doesnt upgrade that much unless he needs too.. and I only update if it contains to our device. otherwise,

I leave it alone. Its also funny, The people on my D851 threads told me I would go crazy if I started porting to other g3's..

I did all this in hope that others would use it to test and create newer roms and kernels.. I hate to see one of my fav phones Die out....... so im trying to keep it alive.........

Multirom comes in handy for rom devs for testing. I can test any rom without having to delete my primary.............

There is one small bug, I dunno if its been fixed on newer updates or not. I did mention to [MENTION=3418703]Tasssadar[/MENTION] once. but, if you install a secondary rom and flash from the Internal SD Card. it will install on primary.

Doesnt make any sense to me.. Dunno if the bug is still present.. It was reported to me by very good testers of mine long ago.

And I will create a FAQ and some instructions as you have said. so new users know how to use it..
[G3 Android Development] RL77LUC:
I didn't know that T-Mobile G3 was unlocked out-of-the-box, lucky users ! :)

The patch here is for the zip file, not for the compilation. I suggest you to read the oversharpening fix script (if you have time, obviously), you'll see how it's used ;).

I didn't understood the bug, sorry, my english is really bad, (young) french user here ^^'.
[G3 Android Development] Eliminater74:
i looked at all the patch scripts that I could find.. even the MultiRom stuff it self. I dont see how I can implant it my self.

Let me see if I can get this straight. When you flash multirom install script.. it causes you to have to reflash the kernel or else you get that security error.

I know that multirom injects the boot.img after each flash. I dont understand the multirom enough to really get deep into that.. but I will ask [MENTION=3418703]Tasssadar[/MENTION] about it and see what he says..
[G3 Android Development] RL77LUC:
"When you flash multirom install script.. it causes you to have to reflash the kernel or else you get that security error." -> that's it, you're right.

You can use the script that I sent you above. You need to put the boot.img in /tmp before that and eventually edit the paths to match your script, but that should work, that's used in oversharpening fix ;).
[G3 Android Development] weedeater84:
Im getting play store fc's on every rom i installed as secondery.. Cannot install any app.. Any help please ?
[G3 Android Development] diogo.sena:
use restorecon option in your secondary rom, using twrp

twrp -> advanced -> multirom -> list rom -> pick your rom -> run restorecon
[G3 Android Development] Eliminater74:
I will look more into this when I get the time.. I just started working on my kernel again. Im one of those people that when my users request something I do it. and I had a few request for my kernel..

and I implated it for them. I will do my best to fix this multirom/bump issue for you.. just give me time.. if I fix it for you. I may as well fix it for each and every ported G3 device outside of the D851 that has unlocked bootloaders..

But as I said, ask anyone on the D851 (T-Mobile) Threads.. I always come though for my users.. only problem with this is, I dont own a D855 and I cant run test that are needed to tweak this out.

So I need to find a D855 or heck any of the G3's other then the D851 user that can have consent contact with for testing.. its going to take alot of testing.

I just wanna say thank you for posting that nfo... I really cant keep up with everyones questions...........
[G3 Android Development] tobitege:
[MENTION=5687366]Eliminater74[/MENTION] just wanted to pass on my sincere Thanks for your awesome work you do, greatly appreciated!

Finally an updated version of MR is great news for G3 D855!
[G3 Android Development] suljo94:
hey are there any sources for the patch, gits(couldn't find it on jon777 and fechinator their git)? engine95 was experimenting with multirom he might be interested in adding the patch to the stock kernel
[G3 Android Development] Eliminater74:
I will post that on the main #op.. give me a few.. ill post the links for all patches.
[G3 Android Development] RL77LUC:
Don't worry, we're not in a hurry, take the time you need, your work is already awesome !

If I can do anything (testing, helping or anything else), feel free to contact me ;).
[G3 Android Development] thiefxhunter:
Thanks a lot for this MOD , it works when i flashed the oversharpening zip , now its amazing boot aosp + stock !! Thankssss

Obs : The flash order was : First kernel , The multizip installer and oversharpening zip .

The device is D855