yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G3] Eliminater74:
Update: Today I will be rebuilding MultiRom.. a few fixes where made by [MENTION=452513]tassadar[/MENTION] and he asked me to pull the git and rebuild.. also

the problem with the kernel patch will be fix soon.. [MENTION=452513]tassadar[/MENTION] gave me instructions on what to change in the patch file so that I can repatch the kernel

and try out the new Kernel Patch build. I will have an update sometime today or later on.. Right now Im watching StarGate SG-1 on hulu and im on season 3 EP-7. :P

I cant spend all my time on this project.. I need a little time to my self too :)

But trust me, I will get this working good enough to make alot of people happy to use it............. just give me time to work out all the bugs..
[T-Mobile LG G3] graphreak:
Was able to test out Multirom 20150402 and here's my experience:

Followed procedure to install Multirom recovery/app then flashed cm-12-20150402-NIGHTLY-d851 ROM as Primary, flashed kernel_test_04-02-2015-signed.zip kernel on it, also did Inject curr. boot sector and it booted up fine.

After completing initial setup I went back into recovery & added Secondary ROM on Internal.

Tried two ROMs separately as Secondary on Internal:

(a) BlissPop-v2.2-d851-OFFICIAL-20150330-0919 (with built-in kernel as well as with kernel_test_04-02-2015-signed.zip and later,

(b) BeanStalk-5.0050-20150323-d851 also with kernel_test_04-02-2015-signed.zip .

All three times these Secondary ROMs stayed stuck on the bootanimation screen.

Just FYI, I had the older skin1980 Multirom (20150112) running on my D851 for over a month earlier with Stock D85110R as primary, and was able to flash as Secondary on Internal in parallel, each incremental version of BlissPop & DU without having to update their kernel/boot.img.

In fact, BlissPop and DU were the only two ROMs that flashed clean on Secondary without any boot problems on skin1980's Multirom.
[T-Mobile LG G3] Eliminater74:
Here is why, and fix will be out later today:

<Tassadar> your kexec hardboot page seems to be located at a pretty weird place
<Tassadar> did you modify the code that reserves the memory somehow?
<Elimin8er> you mean the memory.h yea. I used what most others used
<Elimin8er> from kernels like the RIN and the 777kernel
<Elimin8er> both have the kexec patch.. but doesnt work that great
<Tassadar> I mean in arch/arm/mach-msm/lge/devices_lge.c
<Tassadar> in lge_reserve
<Elimin8er> no I cant say I have.. guess I need to do that
<Tassadar> g3 has memory ordered somewhat differently
<Tassadar> https://gist.github.com/Tasssadar/7833796#file-hammerhead-aosp-implement-kexec-hardboot-patch-L471 line 471 you want "bank = &meminfo.bank[2];" there
<Tassadar> and "if (meminfo.nr_banks < 3) {" on line 466
<Tassadar> and on line 472 you want "start = bank->start + bank->size - LGE_PERSISTENT_RAM_SIZE - SZ_1M;"
<Tassadar> afk for maybe an hour
[T-Mobile LG G3] Eliminater74:
NEW-Working MultiRom Builds. Download everything.

New and working Build Has now been posted........

Only Bug left to fix, the reboot touch screen, It wont let me click anything till after one full reboot......

Now when you boot secondary rom, you will have that secondary rom as it should be.

Problem was in address, G3 uses a very strange address locations. I had to make changes to source

to allow the locations used.. Now it works..

Please Test and Report back to me what else you find...

I know about the Menu No Click screen till one full reboot. I think I know why. But Ill fix that as soon as I can.

Thanks.
[T-Mobile LG G3] GeroP1985:
Getting kernel crashes on secondary ROM upon booting, specifically on Validus and Blisspop

h x x p// pastebin dot com/ 4Q2tUyty
[T-Mobile LG G3] btort1:
Is there still no way to have a stock lg rom like Cloudy and an asop rom as a secondary or vice versa? Will that be ever possible in the future?
[T-Mobile LG G3] Eliminater74:
Im running Blisspop as my secondary and I dont have any problems with it.. Its the Blispop that [MENTION=3771760]aclegg2011[/MENTION] puts out. with his Custom Tootsi kernel.......

Did you flash the new Multirom?

hmm.
[T-Mobile LG G3] GeroP1985:
Yeah, I flashed it before hand, having uninstalled the previous builds for quite some time in addition. Flashed zip, GAPPS, and Furnace Kernel. Tried various combinations of this as well. Made sure to inject boot sector etc.
[T-Mobile LG G3] Eliminater74:
Please Listen: I have Resurrection Remix as my Primary, I have BlissPop (@alec2011 Version with his kernel) as secondary. I also have a full Restored backup of my Resurrection Remix as a Secondary.

I can boot into any of the listed rom without problems.. Matter of fact. the Blisspop boots very fast. from what it used to boot as..

Kernel panics are caused from the location settings dealing with the ramdisk address, At least thats what I get out of the guides. anyhow. Most of our Ramdisks are 0x20000000.

I set it slightly higher around 0x22000000, If I must Ill set it higher.. but as I said, the blisspop I used works no problems...........
[T-Mobile LG G3] jiovaxrs:
hy eliminater. ok i got stock 4.4.2 rom and had the furnance kernel whit had the patch for multirom and this is my primary rom for the camera and other think.

when i flash resurection as my secundary rom and tried to boot in resurection i got a black screen.

ok i flash the old multirom by i thing is user name was somthing like 1980 and the old twrp and do the same and resurection remix boot all ok.
[T-Mobile LG G3] Eliminater74:
I keep getting alot of people telling me about This version of MultiRom not working for them.

Let me break down a few things,

First [MENTION=2174433]Skin1980[/MENTION]'s version of MultiRom is v30

My Version is V32, in V31 [MENTION=452513]tassadar[/MENTION] changed alot of things and even the patches.....

Old Hardboot paches as RIN and Others use Dont work that well with v31+

So using my copy of MultiRom with some of the older patches Prob wont work..

Using my Copy with the kernel I patched above. Should work.. ( at least for me it does)

If you flash the OLDER MultiRom and use the older patched kernels, Then yes they will work for you.

[MENTION=452513]tassadar[/MENTION] told me him self that hes made many changes since the first Multirom was released for our devices that [MENTION=2174433]Skin1980[/MENTION] Ported..

I my self couldnt get many roms to boot with the older patched kernels. That was the whole reason I patched my own so that I could prove the differences between them.

and so that I could know for a fact that MultiRom works.

SO again, Old patch, then you will need older MultiRom.. New patch, then you will need New MultiRom.....

I am working on fixing the problems as best as I can. If you want to stay with the older MultiRom. Then your welcomed to do that.

I didnt port this over to please anyone.. I did this mainly for my self. But I thought I would be nice enough to allow others to try it out as well. But nobody seems to listen to reason here..

I keep hearing about how Well the older MultiRom is. and how mine doesnt work. But Nodoy listens to the reason why....

If nobody is interested in this version anymore. Then ill stop posting updates and just keep it all to my self.. But you can stick with v30.. and ill move on to v33 which is set to be released soon..

but if I stop posting updates, that means I stop posting everything even the twrp mod.

For a while I was getting some positive feedback, now it just seems to be nothing but negative.

I am new to all this coding, I have had talks with [MENTION=452513]tassadar[/MENTION] on IRC everyday getting help which he has been kind enough to do...... IF you all cant wait till I fix it, Then sorry. Just stay with the older version.

Im about to close out this thread and delete this project for good..
[T-Mobile LG G3] SonjaMichelle:
Take everything with a grain of salt, I've found in my years than most forum dezions are heave whiners and have high expectations of developers. Anyhow, for what that's worth.

I'm getting ready to dig into your MultiROM and I think I have things set. I have the base files. Modded-TWRP, MR-Installer, Your Kernel ( which I understand works with CM bsed ROMS?). I have that set up. Now it's on to the secondary ROMS. I wand to try SkyDragon (stock- worked with skin1980s kernel - issues?), Fusion (CM LP, Your kernel I presume?) for the time being. Put these two, a 4.4 based ROM and a 5.01 based ROM. through their paces. Then I want to be able to flip flop them around, maybe add another ROM or two and stick in a larger SD.
[T-Mobile LG G3] jiovaxrs:
im here to help make this as good posible, that why i test and give some feedback. you make a good work im only give some feedback.

thats the reason for the forum. test/ feedback/ test/ feedback/

but i undestud you.

the reason i like multirom is because i can had the stock rom and a bunch of aosp,cm for play.

keep the good work :)
[T-Mobile LG G3] arifqur:
Come on man don't be disappointed with the weird feedback's, people are dicks.

You keep up the development. It is highly appreciated by the majority.

You are doing a super job here. As for [MENTION=2174433]Skin1980[/MENTION], he came out with the first version and never bothered to update even after several requests by me. You have put in more work here in the last few days that is exemplary and commendable.

Just flashed your latest version and everything is back to normal.

The Secondary roms now boot from their own kernel.

However, I flashed 777jon's kernel in one secondary and it also shows up as 777jon's kernel in the settings but there are no OC frquencies present.

Any thoughts?

EDIT: ResurrectionRemix boots out of the box as secondary
[T-Mobile LG G3] SonjaMichelle:
Where can I find a list of working MultiROM approved Kernels? :confused:
[T-Mobile LG G3] Eliminater74:
I will ask [MENTION=452513]tassadar[/MENTION] about that. can you sent log as well. he will want to see one..
[T-Mobile LG G3] Eliminater74:
I am going to compile my next build with Hyper-ToolChains 4.9 and see if it would make any differents.

I wont post it up, unless I feel it works good. and even if I did , Ill post under testing section only...........
[MENTION=452513]tassadar[/MENTION] isnt around, hes only on irc for a bit.. I will talk to him tomorrow.
[T-Mobile LG G3] Eliminater74:
I do thank you for the effort that you just put in.. As for the the Patching.

I will personally up the patch fix to my github. Then I will post the instructions of where to get it and how to patch with it.

My patch is for CM related but im sure it can be used on others with minor changes..

Just a hint, When I patch I use the command line patch, I dont use the github patching. example:

patch --verbose -p1 < patch/cm-kexec-hardboot.patch

That is the command that I use. it should work without errors.. I only used that on cm12.0 so far...

But later on, I will give link to my gisthub, Yea I said gist not git.. that has the fixed patch.....

Also, Speaking of the bootup menu bug, I compiled with hyper-toolchain and funny, the menu bug is gone..

I cant say that it fully works with roms yet.. I havent really tested that part out yet.. but I did notice some differents.

Wait till later, and ill give step by step instructions on getting the patch and using it to patch your kernel... (Only if you plan on compiling your own kernel)

(The Patch isnt for already compiled Kernels, This is a message to others who might think that)

Ill post later on about it...
[T-Mobile LG G3] SonjaMichelle:
Keep in mind, I'm not a programmer. I was a Soldier, Medic, Firefighter by trade the last 24 years. I mainly do this by bashing it all together until something works. :laugh:.

I have AOSP source repo'ed, LG source merged into it, kernel source awaiting a patch. Now I just gotta figure out HOW to patch that source, then get my compile on. Then to figure out how to package it all into a usable format.
[T-Mobile LG G3] Eliminater74:
ITs not that hard. as long as you have all the dev files needed to compile. since you told me you have built roms before, then you should have everything thing needed.

I compile on a Ubuntu 15.04 (beta) AMD Quad Core 2ghz 4tb Storage

As for what I said before, Yes hyper-toolchain seem to fix the menu problem. but it would boot with the primary kernel. Now im doing a test thinking I might know the reason why.

I did make a few changes to address locations only by a fraction. But im going to build without the hyper-toolchain, the same config and see if it works as it should.
[T-Mobile LG G3] SonjaMichelle:
Just built a stock LG system img. It gave me a system.img instead of a nice flashable zip package like I'm used to when building CM ROMs. SO I either missed something or AOSP needs some more steps. Hi Ho Hi Ho off to work I go.............
[T-Mobile LG G3] Eliminater74:
Im not sure if building stock gives you flashable zip file images.. I think they only build the .img part.. you will have to use a zipcreator to do that. But im not sure on all that.

But yes, im very used to the CM builds.... stock is very diffrent from the CM ways...

I build my multirom packages on OmniRom 4.4.4 and I built my Kernel on CM-Resurrection Remix LP 5.0.2 Using Linaro toolchain.

But what mix I build on doesnt matter since my kernel source comes from CM regardless. I just added the patch..
[T-Mobile LG G3] arifqur:
Thanks once again.

Trying the new Multirom and would report on the results
[T-Mobile LG G3] Eliminater74:
I can verify that I have installed Resurrection Remix as Primary using my Patched Kernel

Blispop External ext4 partition as secondary

Backup of resurrection Remix External Ext4 Partition as secondary

Carbon 4.4.4 External ext4 Partition as secondary

I have a 10gig ext4 2nd partition on my 128gig sdcard.

The above listed roms all installed and booted.

My Bug Report:

Even know each rom installed with its own kernel, OC abilities are present but cant use.

Im thinking, your limitations are due to primary, But ill ask [MENTION=452513]tassadar[/MENTION] about that when I see him again.

Other thing, I cant see 5ghz wifi channel.. but that could be my wifi which is on channel 149.. So I need others with dual band to test that out,

My dual band is as this: 2.4 is on channel 11 while my 5ghz is on 149 USA mode... UK uses diffrent channels.

To fix first problem is my calculations are correct, Limitations are due to primarys kernel limitations. IF thats a fact, then I just need to patch

a fully OC working kernel as primary and then all secondary OC rom will have full access..

Ill ask [MENTION=452513]tassadar[/MENTION] about it.

Update: I have been looking into a ubuntu-Touch Port.. From what I see, it uses alot of CyanogenMod Files. and Android 4.4.2 ..

I think it might be possible, but the directory tree in /device is not something im used too. Unless its just putting all needed files in each Device tree, Instead of separate Dir's that each sim. device could use.

I gota be carefull, I dont wanna bite off more then I can chew.....

Update: After studying ubuntu-Touch source tree, Hammerhead is official on ubuntu-touch, G3 and Hammerhead are almost exact in boardconfigs. Remember that I used the hammerhead patch with slight modifications to compensate for the strange memory locations that the G3 uses.

So with alot of comparing, I might be able to cook up a device tree for the G3 to compile Ubuntu-Touch. I just have to go off the HammerHead device tree.

Would be a nice challenge. Dont expect this anytime soon. Im not sure if I even want to take on that project. But I figure it would be nice since we have MultiRom.

I would love to be able to boot up Linux on my phone. If someone else wants to take that project up. Go ahead and do it. But as I said, Hammerhead and G3 are pretty much the same

on all config files. Just minor memory locations differ..

Update: Stock Kernel can be Patched using my Patch listed above. I applied the patch to a stock KK kernel. and thats all. I havent tested it.. but the patch gave No errors..

Someone else can take a crack at the building sock image using the patch. I have no desire to do it my self.. I am just letting you know that it can be applied with my patch.

....
[T-Mobile LG G3] arifqur:
Dude I don't understand half the stuff that you tell us but its good to know that we have such a dedicated Dev working for our team.

Thanks man. Keep it up.
[T-Mobile LG G3] jiovaxrs:
Wow perfect. How can i add the patch to the stock 4.4?
[T-Mobile LG G3] Eliminater74:
Read: This Post For patch

Then clone to android tree in dir patch

then type:

patch --verbose -p1 < patch/D851-CM_hardboot_kexec_kernel.patch

One file it wont be able to patch, that would be the config file. Since stock doesnt use cm.. you will have to

edit the stock config file by hand and make the changes that the patch shows for that file..

IF you dont understand this, Then maybe you shouldnt be trying it.
[T-Mobile LG G3] tribalartgod:
Forgive my ignorance, but what are the differences between this work and the work Skin1980 did HERE?

I only ask, because the one on this thread, I can't seem to get to work properly...But the one Skin posted works just fine for me...Touch screen, brightness, and all...

EDIT: Disregard... Went a few more pages back and got the answer. Also learned something new... I'll try with the new stuff after work and see what happens.
[T-Mobile LG G3] Eliminater74:
Again, Im not trying to sound like a (blank), but ill explain one more time,

[MENTION=2174433]Skin1980[/MENTION]'s multirom thread was closed do to not sharing source for kernel, something like that. I used his version, Many people received kernel panics and dev's had to make changes to their code to compensate for

the multirom code.. When the fact is, [MENTION=2174433]Skin1980[/MENTION]'s code is from v30.. As of v31, [MENTION=452513]tassadar[/MENTION] rewrote alot of the code. making old patch useless.. And since [MENTION=2174433]Skin1980[/MENTION] decided he was going to ignore all of our request to continue updating for us. (He abandoned the D851 Completely). I decided that I would Resurrect it back. after I learned what I needed to. My rom building teachings came from some of the biggest names on

xda. Which im very grateful that they took the time to teach an old dog new tricks..

My version of MultiRom is v32. My patch is Directly from [MENTION=452513]tassadar[/MENTION] him self. Hes the one that told me what Locations to change to make it work for my device.

And since Mr [MENTION=452513]tassadar[/MENTION] is the one that Created MultiRom From Scratch. I think he would know what hes doing. So that in mind, you know the patch that I made

wasnt some made up BS.. It was created with Instructions from its creator.....

So if you want to run them new fancy kernels, Then ask the dev, to patch their Kernels with the patch that I supplied..

I cant say that Multirom is compatible with every rom, Because its not. Alot of Custom kernels out their are changed to the point where its far from original. Making the Hardboot patch not work no matter what you do.

Only the Original Owners can Fix that..

Again, If you think [MENTION=2174433]Skin1980[/MENTION]'s MultiRom is better, Then stick with it., Only draw back you will have, Is no Updates..

If you want continue support and updates then use the one I put up.

Im not trying to sound like an (blank).. Im just stating the facts so people would have more of an understanding..

Now I know what dev's go though.
[T-Mobile LG G3] arifqur:
Dude you don't have to explain yourself again.

People who are interested would and should read through the thread before posting.

Your work is highly appreciated.

PS: Any updates about fixing the no vibration issue in TWRP?

Thanks
[T-Mobile LG G3] Eliminater74:
I havent asked [MENTION=452513]tassadar[/MENTION] yet, he seemed like in a bad mood the other day. So I dare not ask at the time.. I know the screen not blinking out was defualt turned off because he told me

it caused his Nexus to freeze up.. But the config TW_NO_SCEEN_BLINK := false Should have fixed that.. but it didnt..

I will ask him about the vibration thing. but ill be honest, I dont think thats high on his list.. Vidration or not, its not going to effect the outcome of the program..

And yea, I know I didnt have to explain again, but I wanted to be a little more clear on it. Since I really didnt explain that part..

This is still pretty new to people once again. The good news is, I have a G3 D851.. And I dont plan on getting the G4 when it comes out.. Since I seems the screen went down in size.

anyhow I couldnt afford it right now. So I will keep updates to all my devices. I do this to support the community. I get no gain other then the satisfaction of learning more.

I have always been the type of person, That if I cant find what I need, Build it my self. (That also means, I dont depend on anyone.) Long ago, someone once said, if you want it done a special way, The best way would be to do

it your self. As I Re-Learn my coding again. I can make things better. I was away from all this for a long time. I have just recently started to get my memory back on everything..

And with everyone helps, we can make MultiRom happen once again.

L8rz.
[T-Mobile LG G3] arifqur:
Great thoughts and nicely said
[T-Mobile LG G3] marcdw:
I'm about to jump back into testing but need some advice. Rereading the posts and hints/tips here's the deal...

On my old setup I have stock-based ROM (SkyDragon) as primary. Secondary internal is CM11. A 10GB ext4 external partition has been used for Lollipop testing as well as a place to restore some fave KK ROMs that I like to keep current (restore, update apps, backup again).

Far as I know there is no patched kernel for stock KK. To test latest multirom I need to use an LP ROM as primary along with the patched kernel.

Trying to figure out what to do with SkyDragon. Secondary internal (if space permits) or external.

How well does a stock-based ROM work in an external location.

Any tips are greatly appreciated. ?
[T-Mobile LG G3] Eliminater74:
Looks like my OP got messed up. Ill have to fix that later.........

XDA must have had to done a restore or something.. because all my changes I made on post #1 have resorted back to original..
[T-Mobile LG G3] SonjaMichelle:
I tried adding the patch to the t-mo 4.4.2 kernel source. I get a few hunk failures when running the patch.

http://pastebin.com/NbPzyLNL
[T-Mobile LG G3] Eliminater74:
Yours good. it only failed at the CM config, you will have to do that by hand.. just find the kernel config file thats used its something like g3_tm* I dont know the rest its

in android/kernel/arch/arm/configs

Remember you have stock, the patch was originally done for CM.. its just 3 lines you need to add to the kernel config, so that it compiles the and turns on the patch, thats all..
[T-Mobile LG G3] Eliminater74:
I know this is a dumb question, But im going to ask anyhow, I have always built roms off the CM source never anything stock related..

Anyhow, The source code for the D851 on opensource.lg.com whatever site.. When I extract all the files

I see nothing thats of use to our device in the device tree.. I see in device/lge , I see hammerhead and mako .. So how the heck is one

supposed to build on it for the d851 if no ready device tree is listed even though you download the source that says for d851...

I need the AOSP souce for Ubuntu_touch port.. But I admit, I cant figure this one out....... Would be much easier if it was based off of CM..
[T-Mobile LG G3] arifqur:
Hope I could help you buddy.