yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G3] Eliminater74:
Woot: I just received Confirmation that My MultiRom port for the D855 and LS990 are working.......... I gota do at&t and Verizon and see what happends there..

Reason I decided to do this, I think it will open more doors for the Developers to not be scared to test new ideas and have more options available to us.

At least thats what im hoping for.
[T-Mobile LG G3] Eliminater74:
UpDate: New MultiRom V32 Resurrected Posted...... Compiled with Sabermod 5.1/6.0 ...... Hopefully this fixes problems from last update.
[T-Mobile LG G3] marcdw:
I didn't know there were problems in last update. Did I miss something?
[T-Mobile LG G3] Eliminater74:
I thought that there was, and kinda.. but not really.. all I did

was change the kernel to Jon's kernel and turned off the lz4 in favor of lzma and used 2 commits from my kernel to compile his with saberrmod 5.1/6.0 ...

When you build Recovery, you also need kernel, prebuilt kernel isnt something I use much. Now that I have an updated Prebuilt kernel, I can use that from now on.

But your good to go................
[T-Mobile LG G3] modhack4life:
Can i go back and forth from 5.1 roms to 5.0 roms using multirom?
[T-Mobile LG G3] Eliminater74:
yes, thats the whole per-pus of MultiRom.. you can install any rom you want.. even OEM....
[T-Mobile LG G3] junkfactory:
Love to try this but after i flash the hard boot patch and reboot, just stays ob lg logo. Stock d581 20e bootloader
[T-Mobile LG G3] emilio546:
stock kernel

is there any stock patched kernel for lollipop?
[T-Mobile LG G3] marcdw:
So far not that I know of.
[T-Mobile LG G3] Eliminater74:
LG G3 Android Development threads.... a dude did a stock for all devices................ I think its LP.. I could be wrong. but I think it is..
[T-Mobile LG G3] marcdw:
If its got the hardboot kexec patch that would be ideal for those lookin' to run stock as primary.

I think that's what [MENTION=6777624]emilio546[/MENTION] is referring to (?).
[T-Mobile LG G3] Eliminater74:
This Link Here............

Talking about that one.. :D
[T-Mobile LG G3] tribalartgod:
This kernel doesn't work with multirom... or maybe it's the ROM I'm using? ... I'm using Lion Rom 5.5 Extended... It's a stock L base. I installed the quoted kernel, multirom, etc... All works fine... Then I restored a backup for my secondary ROM (No Data Restore) which is SR Remix 3.5. When trying to boot that ROM, it says that the kernel doesn't have the kexec patch, install one, blah blah blah... Should I try to install the kernel once more?
[T-Mobile LG G3] marcdw:
[MENTION=2571085]tribalartgod[/MENTION], I went to the Gabriel thread. Last time kexec was mentioned was in August. Seems the kernel does not yet have that feature.

LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5
[T-Mobile LG G3] tribalartgod:
Sadly, I too found that yesterday... Both of the ROMs I want to use are stock based. Looks like I'll be waiting to see if Gabriel gets patched.
[T-Mobile LG G3] marcdw:
[MENTION=2571085]tribalartgod[/MENTION], BTW, this thread has been replaced with the other MultiRom thread that covers other G3 variants. A similar discussion is going on over there. There is a kernel that may work.

Go to the last two posts I think.

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

[MultiRom V32 Resurrected ] D85x/LS990/VS985

LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5
[T-Mobile LG G3] SeerePetrova:
is a shame doesnt work with Cloudy3g cause there isnt a kernel with multirom support for it.. i tried it and it works fine but wouldnt boot to Cloudy until i flashed the zip for uninstalling it
[T-Mobile LG G3] Eliminater74:
you flashed as secondary rom or primary? when its flashed you must inject boot
[T-Mobile LG G3] SeerePetrova:
my primary rom is Cloudy G3 and the one i flashed as secondary was Temasek which boots perfectly but when i tried to boot Cloudy i got an error... it says that I must flash some kernel compatible with multirom
[T-Mobile LG G3] graphreak:
Stock TMO Lollipop D85120B compatibility?

Is this Stable Multirom compatible with newest TMO Stock Lollipop LG 5.0.1 D85120B ROM as Primary if the "Inject curr. boot sector" method is followed?

Plus if yes, can any AOSP Lollipop be flashed as Secondary to Internal with same "Inject curr. boot sector" method on it's kernel?

I had been using Skin1980's Multirom as daily driver with older 4.4.2 (D85110R) as Primary & AOSP Lollipops as Secondary on Internal until Stock D85120B Lollipop dropped a couple of days ago.

Thanks for all your efforts!

:good:
[T-Mobile LG G3] Eliminater74:
you didnt read the instructions.. you need to have the pactched kernel and I listed at least one already patched. read OP .
[T-Mobile LG G3] Eliminater74:
you will have to test it and find out. you would need a stock patched kernel most likely. you really cant mix the 2 like that.. if you have stock primary rom, then you need stock patched primary kernel.
[T-Mobile LG G3] SeerePetrova:
but that kernel says is for AOSP roms and cloudy is not... its based on stock... so the question is will that kernel work?
[T-Mobile LG G3] Eliminater74:
you would need to find a stock kernel. Here is Stock Kitkat Patched: https://www.androidfilehost.com/?fid=95897840722641286

you would have to find the stock patch of whatever version your primary is, if its LP then you need a stock LP patched Kernel.

I am working on patching now. but Im doing CM related at this time. I wasnt going to mess with stock patches. but ill look into it.

I dont like the rin kernel thats patched for LP.. it doesnt agree with my RR rom very well. So im going to patch my own CM kernel

and push that to my git and upload to filehost. But for now, you will have to search for a patched kernel for the android rom you have as primary or wait till one comes out.

I dont plan on stopping this dev. So I will update multirom and keep it going as long as I can. So, if you just hang on, something will be out that will work for you as a kernel.

Sum up the answer to your question, NO it wont work. you need patched stock rom for whatever android version your using.

PS: Most people seem to be running Custom roms, so I didnt think much about stock patches.. Hopefully someone else will take up that project for me and release a patched kernel for them.

If I get time, ill try... But I cant promise anything at this time.

I hope I answered your question in the best way I could.
[T-Mobile LG G3] SeerePetrova:
You did... Thanks a lot... I'll post on the Rom's threat might find a developer willing to help..... It's a lollipop rom based on stock btw...
[T-Mobile LG G3] arifqur:
Can't get CM12 to boot as secondary rom same as with [MENTION=2174433]Skin1980[/MENTION]'s Multirom version.

It was my understanding that this was rectified in the Multirom32

EDIT: List of roms that don't boot as secondary:

1 Beanstalk

2 Temasek

3 Euphoria

4 Mokee

5 CM12

6 Vanir

All end up in Kernel crash

However if you flash 777jon's kernel, they all boot
[T-Mobile LG G3] Eliminater74:
I got it to boot.. just as I did with skin1980 multirom port also................. I never had a issue booting cm12.. you must be doing something wrong.,.
[T-Mobile LG G3] arifqur:
Doing wrong like what?

I think it is a pretty simple thing to flash a rom zip in Multirom.

Anyways open to ideas.

Thanks for the new Multirom.

BTW can the no vibration issue in the Multirom TWRP be fixed.

Also the new DPI of the boot menu looks great
[T-Mobile LG G3] marcdw:
CM12 and other roms have not booted with MultiROM for some time. An alternative kernel is needed such as 777jon or tootsie-pop.
[T-Mobile LG G3] arifqur:
But the OP says that he got it to boot
[T-Mobile LG G3] marcdw:
Heh. Sorry, mostly I was thinking of the old multirom.

My current tests are ending in failure. With the latest build my ROMs get kernel crashes.

My daily driver since January is CM11, installed as secondary on internal.

Fusion LP was a secondary on an ext4 partition on microsd card. That's where I test other LP ROMs also.

Added/restored CM11 but kernel crashes. Same with Fusion.

Deleted those and tried fresh/clean flashes with same result. Flashing alternate kernels w/Fusion didn't work.

Since CM11 is my DD I decided to remove the new multirom and flash the old. I'm on CM11 now.

Of course I'll continue to test each multirom as Eliminator74 puts out.

At least the new TWRP is okay. Finally the timezone is working.
[T-Mobile LG G3] Eliminater74:
Let me explain something, Kernel Panics are the cause of this

MR flag: MR_RD_ADDR := XXXXXXXXXXXXXXX

This option might not be needed for your device. It sets address in boot.img to unpack ramdisk into, and most devices can handle MultiROM changes even without this option. But, some devices (Nexus 7 and Nexus 4) will panic on boot when the ramdisk is bigger than expected. As to what value to set, well, it's more about guessing than anything else. Look at default ramdisk address in your boot.img and try to use a bit higher address.

I took a common boot.img from a rom that I use all the time, and found the ramdisk address which was 0x2200000 and I set it at 0x2600000 ...

I was hoping that would fix the kernel panics. The roms that I have tested so far used the same kernel on both secondary and my primary I used the RIN kernel LP ..

If you have a kernel Panic, I need a copy of your boot.img or the ram address at least. So I can figure out whats the best address to set it at... Without that I cant fix the problem.

I can ask Tassadar who is the creator or Multirom anytime on IRC how to fix that part if needed.. but unless I try my self first, I wont ask him. I spoke with him 20 mins yesterday on how to

fix the multirom crash issue which turned out to be a simple fix.

So, anyone with kernel panics, I need to know where I can get a copy of your kernel so that I can find out the ramdisk address..

I am trying the best I can. Im learning as I go. When I set out to do something, I dont give up.

PS: Make sure you inject Boot Sec on each new ROM flash. Thats not checked by default. So if you flash a secondary rom, you need that checked. or it wont work.
[T-Mobile LG G3] Eliminater74:
This is from a fresh Kernel Build only of CM12 using latest github sources:

Kernel size 8281288
Kernel address 0x8000
Ramdisk size 1028173
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x100
Flash page size 2048
Board name is ""
Command line "console=ttyHSL0,115200,n8 androidboot.hardware=g3 user_debug=31 msm_rtb.filter=0x0 androidboot.bootdevice=msm_sdcc.1"

*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_RAMDISK_ADDR is 0x02000000
[T-Mobile LG G3] arifqur:
I think if you flash the latest CM12 nightly as secondary you would easily be able to take ts crash log yourself.

Your commitment towards making this work is highly appreciated by all of us.

Thanks
[T-Mobile LG G3] Eliminater74:
I think I found another mistake made by Mr [MENTION=2174433]Skin1980[/MENTION] ,

When I started this project, I used his github device tree forked over.

Now in his boardconfig.mk file he had:

MR_KEXEC_MEM_MIN := 0x20000000

When in fact it should be more like:

MR_KEXEC_MEM_MIN := 0x05500000

Reasons:

Configuring MultiROM's MR_KEXEC_MEM_MIN

Back to MultiROM's configuration in the BoardConfig.mk. This is the value where kernel and initrd are loaded before reboot. It has to be in the first 256MB of System RAM, and it must not be rewrote during the reboot. Again, look at /proc/iomem and select something reasonable, for example flo System RAM's first bank spans from 0x80200000 to 0x88dfffff and the mem-min value I've selected is 0x85000000.

...
80200000-88dfffff : System RAM
80208000-810ad21f : Kernel code
8121e000-8163e293 : Kernel data
...

See, After I checked my proc/iomem

I seen that my system ram is located at:

0x00000000 - 0x059fffff : system ram
0x0000800 - 0x00fc1d5f : kernel code
0x01110000 - 0x01514bc3 : kernel data

Thats why I came up with the value 0x05500000

Since its in between it all.

Ill give it a go and see if that helps.. But I think kernel panics and or not booting is the cause of wrong address..

Let me recompile my fix and re up it.. then I need some testers to tell me if that helped or not.

I could be wrong, But ill recompile and test it as far as making sure it boots up again.

Like I said, I started out with [MENTION=2174433]Skin1980[/MENTION]'s device tree then made my changes and pushed it to my github.

I only had to edit one C file in the multirom source tree to make the multirom compatible with our device, which [MENTION=452513]tassadar[/MENTION] has pushed to his github.

Yeah, I was wrong. Well I tried it another way now, Ill push the address to 0x24000000 from the 0x20000000

The last address I had caused a crash
[T-Mobile LG G3] arifqur:
Always here to check your latest and greatest
[T-Mobile LG G3] Eliminater74:
Im talking with [MENTION=452513]tassadar[/MENTION] now on IRC.. he wants logs. but since most of all you are mention about the problems. I need the logs from everyone here who says it crashed on them on boot from secondary rom.
[T-Mobile LG G3] joshuajones:
Thanks a ton for doing this! It seemed like everyone forgot about multirom, and I didn't think we'd ever see an update.
[T-Mobile LG G3] Eliminater74:
I dont mind doing this, But one must remember, Im still pretty new at this,

Yea I have been around computers since 1982 my first being a Commodore 64 and then Commodore 128/D and Commodore 64c. and Amiga1200 and Amiga500.

then many type of PC's that we all use now... I programmed mostly in Assembly and not C.. C is not my specialty thats for sure.

As for MultiRom, Im only doing this, because I really liked the program. and the Creator [MENTION=452513]tassadar[/MENTION] Is really a smart dude. and very helpful. I talk to him on IRC. in #multirom on network freenode.

But im learning as I go. Its kinda of a learn as you go thing. But yea, Im still working on the kernel part of multirom. I just need time..

As I said above, I need LOGS from users that say it crashed on booting secondary roms. I need proc/last_kmsg and dmesg then there should be also multirom/multirom.txt ..

For people that dont know how really. Drop to terminal

type dmeg > multirom_dmeg.txt

Make sure your in sdcard directory when you type that.

last_kmesg is the last boot log only. it resets next boot.. so you must get it the min the system crashes.. you can copy that with twrp.........
[T-Mobile LG G3] Eliminater74:
Update: After alot of test and trials and reading on top of all that, I finely got a working HardBoot Kexec Patched Kernel.

The source I used it taken directly from CM github forked over and patched with (funny this should work, but patched with the Hammerhead kexec patch). Then some minor

changes to memory.h file to set the page address and locations.. Compiled kernel.. tried it.. and it worked..

This kernel isnt beefed up outside of CM's Defaults and Hardboot Kexec patch..

But since I found the correct patch that works with no problems. Other dev's should be able to use it just as easy..

I will upload this working kernel later on..
[T-Mobile LG G3] graphreak:
All your efforts on this are much appreciated! :good:
[T-Mobile LG G3] arifqur:
Thanks dude.

Much appreciated.

If you could only patch the Lollipop stock kernel it would be great
[T-Mobile LG G3] Eliminater74:
I dont think the source code for the LP-D851 has been released. I looked the other day and couldnt find anything outside of KK..

Then again there isnt much difference from all the D850 - D855 , But if you want stock, find me the stock LP kernel source for the D851.. Problem is, I would have no way to test it.

There is nothing stock on all my devices. I kinda forget what stock looks like.. :) I rather someone that uses stock do that patch and test it.

I had to compile the kernel 7 times, trying diffrent things , before I got it working. That means I also had to flash it and test it. But then again, Now that I know what to do, its much easier..
[T-Mobile LG G3] arifqur:
I have faith in you man, You can do it. Once the source drops

Maybe the kernel source is included in the 20B here:http://opensource.lge.com/osSch/list?types=ALL&search=d851
[T-Mobile LG G3] Eliminater74:
Your killing me man, Now I would have to repo the whole android tree just to compile a stock kernel.. :)

Im used to CM.. all the breakfast,brunch,lunch ( I wonder why they never added a dinner) commands..

stock is old fashion make commands.. :P

I will look into it, but im not making any promises, I can only do one thing at a time.. I still have 2 other projects in the Samsung Galaxy S tab forums. matter of fact, I need to update my rom over there.

since nvertigo67 updated the kernel. which I use his source, I need to rebuild my rom with it.
[T-Mobile LG G3] graphreak:
The main Source ZIP LGD851TN_G3_Android_L_V20b.zip file. [1.00 GB (1,083,190,486 bytes) in size] does contain LGD851_G3_L_Kernel.tar.gz, LGD851_G3_L_Android.tar.gz & Readme.txt files.
[T-Mobile LG G3] jiovaxrs:
I really like to have the stock lollipop 5.0.1 and run resurection in my secundary. A need to wait for kexec patch for the stock 5.0.1?

And btw eliminater74 awesome job really
[T-Mobile LG G3] Eliminater74:
As I said in the 3rd post, I have a 2nd partition formated in ext4 10g's . I used that for all my secondary roms.

Also I noticed a small bug, When you reboot from the recovery it wont let you click on anything when the multirom menu pops up. till it boots primary then it lets you click box and choose rom.

Dunno what is causing that. but ill ask when I can and see if I can fix that. Not even sure if its the kernel I used which I doubt it, but you never know.

or if it could be some settings in twrp config that I need to change.......

Can anyone else vitrify this bug?? please report back to me.

Thank you.
[T-Mobile LG G3] arifqur:
Yeah used to happen with skin1980's multirom as well
[T-Mobile LG G3] Eliminater74:
It would be nice, if some of you would at least give me some feedback on how its working. I want to fix all the bugs, I have plenty of ample time

on IRC to talk to [MENTION=452513]tassadar[/MENTION] about the fixes. So I need Testers and feedback. Im trying to make this the best rom/recovery/kernel you would ever use on our device.

But unless I get some feed back, Its a little hard to track down all errors my self.

I do thank the users that have given me some feedback. You all know who you are..

But really, Im not asking for anything more then just a little feedback on how its working for you and what could make it better.

Thank you..

PS: I updated a build: MultiRom and TWRP-Multirom. Not much different, but a few bugs fixes that you woldnt noticed..

Test that kernel out to please.. its CM Default with Hardboot Kexec Patch.. Nothing fancy about it.
[T-Mobile LG G3] graphreak:
Just downloaded the files, let me try and make some time to cease playing with Stock 20B Lollipop (meantime I got side-tracked with an AOSP 5.1 I discovered today)

& test out your 20150402 version on CM12 based roms.

Thank you again for all your efforts! :good:
[T-Mobile LG G3] SonjaMichelle:
Do Share! :p

[MENTION=5687366]Eliminater74[/MENTION]

I've been busy undoing the mess the 20b ROM made of my phone (not a pretty picture) to really get into your MultiROM. Though I have been following the thread. I am currently running Fusion Lollipop. AFAIK it's CM based, am I correct that you cooked up a cm kernel? If so, can you point me in its direction then I can do some testing for you. Having MultiROM right now would be handy, being able to run a WiFI-Calling enable ROM while at home where I have no signal and then switching to Fusion while I out and about during my day.
[T-Mobile LG G3] graphreak:
[Here] -relevant to this thread, pretty easy to find wouldn't one say?? ;)
[T-Mobile LG G3] Eliminater74:
I do say, you people are brave running them stock roms.. To me LG Stock roms are nothing but trouble. I seen alot of phones get messed up over stock.. I have had less problems under custom roms then I ever had under stock.

LP is nice. but think about this, the stock LP is only 5.0.1 while google just released LP 5.1.1, which means T-Mobile stock is 3 behind the standard release LP...

I rather wait till CM or anyone alike comes out with the 5.1, then use that.. I do agree with you, I wish I could implant wificalling into CM. Problem is, Someone needs to take the stock source and get all the wifi calling api's and calls' then implant it into the calling/settings of CM or so. then the wifi calling app would work on CM..
[T-Mobile LG G3] arifqur:
One of the bugs that I would like to report is that there is no Touch Vibration in the Multirom TWRP.

It would be nice to have that fixed.

Thanks, currently backing up and then would flash the new Multirom and the TWRP and the latest CM12 nightly and then flash your patched CM12 kernel.

Edit: Flashed the latest Multirom and TWRP and the latest CM12 nightly and your test kernel as primary.

The primary boots fine. The secondary as CM12 boots fine but the kernel version it shows is Eliminater74 but I did not flash this kernel on the secondary rom's cm12.

Same thing happens with every other rom.

Edit 2:Removed the boot.img from one of the secondary roms and flashed 777jon's boot.img and after booting this secondary rom, the kernel version in settings still shows Eliminater74 kernel.

I think all the secondary roms are now using the Primary rom's kernel

Edit 3: If you flash Rin or 777jon kernel on Primary rom, most of the secondary roms don't boot
[T-Mobile LG G3] Eliminater74:
Do this test for me, Flash the kernel I posted again, Then flash a working kernel on secondary that you know has OC. then boot up secondary, then try OC.. if you can OC... I kinda noticed that too. but, im not 100% sure about that. do that test and tell me results.. and ill talk to Tassadar about it and see what he says.

Im almost wondering if its the patch that im running. but I cant remember if it did the same on the rin kernel patch also.. so try that too. See the problem is he has a few patches out. The only one I was able to

get to work with no errors is his HammerHead patch. but that makes sence, because the HammerHead is LG.. that uses the mech.msm.. while the other patches are mostly related to nextus.

If im not mistaking that same issue was also on Skin1980's version of Multirom as well. I tried to compile allready patched kernels and use them With no Luck. none of them worked.. So thats why I just did my own

from scratch. I have the source for the 777kernel and the Rin kernel. and compiling both didnt work when I went to try booting secondary rom...

Let me know.
[T-Mobile LG G3] arifqur:
Tried flashing 777jon kernel on a secondary rom and then tried to OC it but the values were not there.

Which means that the kernel still being used by the secondary rom is the Primary rom's
[T-Mobile LG G3] Eliminater74:
ill talk to Tassadar about that. Because its not good specialy if one wanted to install KK rom on secondary...

could you try that too.. install a KK or JB rom on secondary and tell me if it boots.

But what I ment Install RIN or 777 on primary and boot something from secondary and tell me if it shows the RIN or 777..

I know for a fact that RIN will boot blispop.. because thats one of the first secondary roms I tested.

Update: I am going to try patching the kernel again with another patch, Ill do this later on. Right now im going to lay down for a bit. but later I will take a crack at another patch and see if that works better.
[T-Mobile LG G3] arifqur:
Installing either Rin or 777 on primary does not boot Bliss on secondary