yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] Eliminater74:
I forgot to mention that, The F400 device had issues, The kernel that was used in current F400 is 11.0 I think anyhow, I fixed alot of defconfig issues in 11.1 - 12.0 .....

So when I start to build again.. Ill make sure I have the latest kernel in it............

So that the F400 can have a chance at this............ F400 = Korean Model...

Thats also the model thats 99% the same as the D851 T-Mobile Model. which is what I have... SO I dont know what happen and why they had issues..........

but we will figure it out........
[G3 Android Development] gnashville:
So much for a break :P

Always moving forward
[G3 Android Development] Eliminater74:
Attention: Since none of us really use twrp to root our devices or install SuperSU..

Would anyone mind if I removed the superSU crap from the TWRP recovery image? I need the extra space for my theme pack and stuff. Anyhow, The new SuperSU runs a bit dif..

I rather just remove it... It would give me the space I need.........
[G3 Android Development] gnashville:
Wouldn't bother me one iota.
[G3 Android Development] Will_Xda:
Sounds good to me (Imagine there may be a few salty noobs who use that in TWRP though), looking forward to your themes :) Congrats on RC/RD status too, well deserved imo

Happy holidays dude
[G3 Android Development] klewisjohnson:
No problem from me;

a much better use of the space! [emoji13]
[G3 Android Development] masterxxxxxl:
The problem is not on the Blisspop one, it's on the Stock Rom, the Blisspop one's just the Internal one...

BTW: Where on exact are the second Rom's partitons located? Are they accessible?
[G3 Android Development] dadi11:
remove it. it only breaks mm roms after installing twrp supersu

Sent from LG G3
[G3 Android Development] vaibhavaggarwal:
Thanks for not forgetting about the F400...

I am sure you'll figure it out :)
[G3 Android Development] Eliminater74:
No Matter: What I do, I seem to keep getting Image to big issues... Compiles fine, But the image is slightly past the MAX........

It doesnt even like default settings.......... I might try and compile 4.8 and see if that goes though....................

The higher the Gcc Version, the bigger the image.. so maybe 4.8 will feel good........ Kernel is pre compiled with 6.0........

I will try again......... and again............
[G3 Android Development] Eliminater74:
Attention: Sorry, ButI cant add a preset theme package to the Final Build of TWRP Recovery for MultiRom........

Its just too big..... But what I will do is this, I will add the theme package to the installer, and have everything copy to the correct directory for your pleasure.........

I cant take anything else out.. and all the theme packages are at least 6megs - 20 megs......... and the Recovery partition is 16 megs max............. Now do you see my dilemma ?

But it does have the updated Kernel now............... Kernel alone is 5 1/2 megs.................

So for the time being you must deal with what I got now.... But as I said, ill create a installer for the theme packages for you.........

Calling All F400: I need a F400 User to test New edition to TWRP MultiRom Recovery..................

Calling all F400's ................................ Plz Msg me ASAP... Or better yet add me on hangouts...................................................

​
[G3 Android Development] Yamen Nwilaty:
F400 user over here :p

first of all thank you for supporting the F400 devices and for all your hard work on theme and every thing else

so where is the twrp that needs some testing :)
[G3 Android Development] bambotcha:
Every time I install multiROM uninstaller and reboot I get this message :

[790] Fastboot started

Whats going on ?
[G3 Android Development] Eliminater74:
If you were selling 5 cars.. all CHEVYS, but dif models... and I came to you the next day, and said "hey my car is broke, It wont start, something wrong with it."

Whats the first thing you would say to me? On top of the fact I didnt drive it over there..

?

I will tell you what the first thing you would say, "I sold you 5 cars, which one are you talking about?"

Get the idea?
[G3 Android Development] bambotcha:
Thanks for your reply

It was an issue with the kernel had nothing to do with multiRom

One last question if you don't mind , can I install a kitkat Rom as a secondary Rom ?
[G3 Android Development] klewisjohnson:
Yes of course
[G3 Android Development] Eliminater74:
Im not trying to be rude to you.. but you dont understand how many times people tell me things without giving me the full info..

If I dont know what device or OS and ROM you run.. I have no idea how to help you...............

The cars example was my way of trying to get you to understand where im coming from..

I cant read minds.. would be nice.. but I cant..

You can mix match any ROM/OS as long as primary has the Hardboot Kexec Patch.....................
[G3 Android Development] Youssef mo7a:
i do all steps but there is no multirom menu in advanced setting

D855 32gb
[G3 Android Development] bambotcha:
No offense taken , you are right in what you say

I have CM12.1 with 777 kernel as a primary ROM and I was asking about kitkat cause I tried to install MIUI Rom based on kitkat as a secondary but It failed to boot So I wanted to know If its even possible

Thanks again for you reply

---------- Post added at 01:29 PM ---------- Previous post was at 01:28 PM ----------

Make sure you install the MultiRom TWRP not the normal TWRP
[G3 Android Development] klewisjohnson:
Yes its very possible I have it as a secondary and it runs great
[G3 Android Development] Youssef mo7a:
The name of the twrp i flashed before flashing kernel, multirom and the bump

TWRP_MultiRom_D855_20151202_3-signed.zip
[G3 Android Development] john.shaleem:
First of all, this is a very sweet mod and I have been using it for the last 5 months or so. Thumbs for the dev for this great work. However, as you know that the stock MM is out and I wanted to try it. As far as I know I cant install it on MultiRom because we don't have the kernel for stock MM that supports MultiRom. I really wanna try it out.

So i want to ask the experts that can I install the stock MM as my primary Rom on MultiRom or not? If not, that can you please tell me how to uninstall MultiRom so that i can give the MM a try. Thanks
[G3 Android Development] Eliminater74:
Any Kernel with the Kexec hardboot patch can be installed as primary then you can install anything as secondary. Follow the FAQ to understand how to install MM custom roms as secondary.

and as for installing stock as secondary.. Some can and some cant.........
[G3 Android Development] Yamen Nwilaty:
for unistalling multi rom first wipe all secodnary roms you have

secondly flash multi rom unistaller then flash a normal twrp from flashify as far this point you must be on your primary rom with the kenel with multi rom support

lastly go to recovery and do a full wipe (cache _system _data ) and internal and factory reset if you want but sytem data the two cach is needed

and flash the flashable prerooted mm stock

hit the thank bottom if i hepled you ;)

hint:multi rom unistaller you finds it in the same place that you downloaded twrp multi rom and the multi rom installer
[G3 Android Development] john.shaleem:
Thanks for the explanation, i will try to find a stock MM kernel with the Kexec hardboot patch, so that i can make stock MM my primary ROM.

---------- Post added at 12:44 ---------- Previous post was at 12:41 ----------

Thanks for the detailed and step by step info. First i will try to find a stock MM kernel with the Kexec hardboot patch, and give it a go. If that dosent work then i will follow your steps. I just wanna check out the performance and new changes on MM :)
[G3 Android Development] Atarii:
There isn't a public MM kernel with the Kexec hardboot patch yet, but the source is available here: http://opensource.lge.com/osSch/list?types=ALL&search=D855
[G3 Android Development] burninitup:
Chh

Ok i had the same problem this is what i did--

- first make sure that multirom is installed. Boot ur phone and see if it ask for selecting rom)

-Go to http://xdaforums.com/lg-g3/development/mod-multirom-t2995047

-Download the multirom recovery from here

-flash it in twrp u have (only twrp, do not flash any other file)

- reboot to recovery and check if u have the multirom. Also ur twrp version will be 2.8.4

- now open the twrp with winrar and delete the recovery.img from it.

- extract the recovery.img from twrp given in this thread and pack it in another twrp zip ( the one u downloaded from another thread)

- that's it flash the new zip and u'll have multirom twrp 2.8.7
[G3 Android Development] sabresfan:
I had this happen to me. I just flashed philz recovery with flashify. Booted into recovery and flashed the latest twrp multirom and I was back in business.
[G3 Android Development] bigcletus:
Google Play store crashing and no internal or external SD card...

I have a AOSP rom as primary and stock based rom as the secondary rom. Both boot fine, but the secondary rom cannot open the play store or access either the internal storage or external sd card.

I have searched this thread and others. Most say the restorecon in TWRP fixes the issue but it does not seem to have any effect. I have also tried running this from adb : restorecon -FR /data/media/0 but still I cannot access the internal or external sd cards. I can see the files on each only through adb shell, the internal only shows files in /data/media/0 and the external in /mnt/media_rw/external_SD, but none of the other directories show anything, like the /storage sub dirs. They are all empty. Do I need to create symlinks or something? Any help is greatly appreciated. Thanks.
[G3 Android Development] ZenS78:
Progect is dead?
[G3 Android Development] Eliminater74:
UpDate News:

Listen peepz, this project is never dead as long as im doing it at least.

I talked to mr [MENTION=3418703]Tasssadar[/MENTION] today in IRC............. TWRP v3.0 is finished for MultiRom except The MULTIROM OPtions theme... thats still being worked on.. No point in me building it till its finished fully.....

Here is a little snippet of the convo on irc:

<Elimin8er> Tassadar, I know this is a dumb question, but I been out of touch with **** for a while I noticed you updated the modified twrp for multirom, Can I still use the omni LP tree or do I need to use the Omni MM tree now ? or does it matter?
<Tassadar> 5.1 works
<Elimin8er> Tassadar, and thats the new 3.0 everyone been ttelling me about ?
<Tassadar> yes
<Elimin8er> ok thank you...........
<Tassadar> the theme does not yet have multirom options
<Elimin8er> Tassadar, so should I wait?, so multirom options wont show up yet right ?
<Tassadar> yeah, it's not donme
<Elimin8er> ill wait.. then.. thanks.
<Elimin8er> im not in that much of a hury to please the world... I can wait till its finished.. :)
<Tassadar> ******** SELinux, being safe and ****

There you have it....... So just wait till its finished before I build it..........
[G3 Android Development] bigcletus:
That is good news. Once 3.0 is out, can we flash it on top of existing 2.8.7 and keep all secondary roms intact? Thanks.
[G3 Android Development] iluvamk:
That would be a negative ghostrider. No mutlirom menu till op builds it. You would have to flash back to 2.8.7 mr twrp to access secondary again.

Edit: My bad. Yes secondaries would still be intact you just couldn't access them from 3.0.
[G3 Android Development] Eliminater74:
MultiRom Update:

It looks like the 3.0 themes were merged into the New MultiRom TWRP 3.0 now... I will take a crack at it.. I am trying to build it with the omnirom LP tree, Which Tassadar said would work. If not.. Ill try the Omnirom MM tree.........

I did create a Recovery.img with LP tree.. I have yet to test it.. cause im going to go ahead and create the whole works of MultiRom package before I test..............

If all goes well. im going to go ahead and try the Omni MM tree... and when I feel all works right. ill create the new MultiRom for all Devices..........

Hope I can get the F400 to work for them peepz............

I am doing all I can do.............
[G3 Android Development] Eliminater74:
MultiRom Update:

I built the New MultiRom V33.

with New TWRP Modified Recovery v3.0 .. Looks good.. I rebuilt the recovery like 8 - 12 times, trying new options and things........

I did add a extra mount point for ext_sd (Extended 2nd Partition), Like me, I have a 10 gb partition on my 128gb sdcard... For adding all my MultiRom Extra Roms to it...........

So the new mount point will allow you to make changes to that partition.. Note, Partition should be ext4 or f2f (The ext sd) ........

More later on.............
[G3 Android Development] Eliminater74:
MultiRom Resurrection v33:

New Release: MultiRom Resurrection V33 W/TWRP V3.0 Themed........................

Warning: Flashable Recovery Zip will NULL out your Current Recovery partition Before flashing New one......

Reason for that: Because many said they flashed and nothing got replaced.. So im Removing Current Recovery before flashing new one over.........

I have already tested this on my own device.. But Be Warned......... You take your own Risks,.
[G3 Android Development] Eliminater74:
Update:

I made a huge mistake. I created a pull request with Mr [MENTION=452513]tassadar[/MENTION] to add the D855 device support for the kexec-tools..

And he merged it. But problem is, Its not merged in the code that I got from him. This is the #1 reason why this isnt working on secondary roms..........

const struct arm_mach arm_mach_hammerhead = {
.boardnames = { "hammerhead", "bacon", "d851", NULL },
.choose_dtb = hammerhead_choose_dtb,
.add_extra_regs = hammerhead_add_extra_regs,
};

It should be:

const struct arm_mach arm_mach_hammerhead = {
.boardnames = { "hammerhead", "bacon", "d851", "d855", NULL },
.choose_dtb = hammerhead_choose_dtb,
.add_extra_regs = hammerhead_add_extra_regs,
};

Reason for this in log:

6.888226 / 02-20 04:00:32.780] multirom: Unknown boardname 'd855'!
<3>[ 6.888235 / 02-20 04:00:32.780] multirom: Cannot load /zImage

I am sorry, I will fix this problem right now and re-up a new one.. its just the multirom part that I need to redo. The Recovery is fine...........

Update: Problem has been fixed. New multirom installer has been posted. Download and install......
[G3 Android Development] weedeater84:
can someone provide a way to flash, step by step.

im getting boot verification after im turning on the phone.

please help guys !!!
[G3 Android Development] Eliminater74:
Try doing what this guy above said.................
[G3 Android Development] weedeater84:
:( unsecsses...

please step by step, if u wanna help me..

---------- Post added at 07:04 AM ---------- Previous post was at 06:08 AM ----------

please someone ?!?!
[G3 Android Development] Scrine:
I Flash New multirom-20150711-v32-UNOFFICIAL-d855.zip [2nd release, Fixed boardnames] then 777Kernel_MR_support_lp51_20150711.zip [Zipfile should be fixed now] but I still have the error " error executing updater binary in zip sdcard/777Kernel_MR_support_lp51_20150711"
[G3 Android Development] Eliminater74:
Just download 777Kernel for your device from [MENTION=4794976]777jon[/MENTION] and everything will work just the same..
[G3 Android Development] Scrine:
Wow Its work!!!!!!!!

I was able to run and second ROM as well. But I had a problem . When installing Cloudy G3 2.5 installer can not install the kernel . I installed the kernel m apart . Loading the second ROM takes a long time , but the expectations are .

Excellent work . Now we have multirom-v32 for D855
[G3 Android Development] tupie:
Then, the only way to have multirom is having an AOSP as primary with 777jon's kernel ? We cant have a primary stock on D855 of 16Gb?

Tnx for all the hard work guys
[G3 Android Development] RL77LUC:
It's now working (D855 16gb user with 777 kernel), you're amazing ! Thanks a lot.
[G3 Android Development] Eliminater74:
It will work with any rom as long as its kernel is patched with the Kexec hardboot patch. If you can get someone to patch the stock kernel, then you can run stock.

my patch works with stock/EOM as well as AOSP/CM kernels. My job was porting over MultiRom. as for stock kernels. Sorry, I didnt even do that on my own device.

I let someone else do that. I have at least 6 projects going on right now. and I dont have the time to deal with the kernel end part on your devices.

But now that MR v32 is ported over, im sure someone will patch a stock for you.

Here is my Kernel Patch That works for any G3 Device stock/AOSP/CM, with some adjustments of course..

And yes you will need to know how to build a kernel to use that patch.

Anyhow, glad to hear that it finely works. Now im just waiting on Sprint to test it............

Side Note: Speaking of installing separate kernels on secondary roms after rom has already been installed. flashing a kernel to secondary rom can take a very long time. I dunno why and I never really cared why, But a work around is this: goto TWRP then MultiRom menu, then click list roms, then click the location that your secondary rom is on, then click remove boot.img

then ater that.. Click add boot.img, then just manually add the boot.img that you want injected into that rom. Now since [MENTION=4794976]777jon[/MENTION]'s kernel uses AnyKernel, So that means no boot.img ..

you will have to create a boot.img first.

Also please note, you dont need to have a patched secondary kernel.. only the Primary needs the patch, Im sure most of you already know that...
[G3 Android Development] suljo94:
could you make the multirom.zip bump the kernel(there is a beta stock patched kernel but sec error)
[G3 Android Development] Eliminater74:
Im not sure I can do that dude. not sure I know what you mean.. the kernel is bumped and the recovery is also.. but anything you install would already have that bumped or so..
[G3 Android Development] RL77LUC:
If we flash multirom after kernel, we have security error, do you know why ? I mean that's what he meaned by "bump multirom".
[G3 Android Development] suljo94:
I'm sorry I typed my previous comment from my phone on the way home. what I meant was After you flash the multirom zip untop of an bumped kernel you will get an security error, I think that it is because multirom doesn't sign(bump the hex values) the boot.img when it merges the acctual kernel and ramdisk back together
[G3 Android Development] Eliminater74:
I dunno, multirom isnt an image.. and as for that.. whatever the other people are doing.. they got it to work right. but going in some order.. but ill look into what your saying.... ill try.
[G3 Android Development] suljo94:
jon777 his kernel works if you flash it then the multirom zip and then the kernel again becausehis kernel is anykernel it uses the modified ramdisk but it bumps it too because the anykernel.sh file executes the bump file under tools (see his zip) skin1980 used a file called sign to do the same thing in this inject_boot.sh file

# signing new boot.img

cat newboot.img /res/sign > newboot_signed.img

echo "Cleaning boot partition"

dd if=/dev/zero of=$BOOT_DEV

echo "Writing new boot.img..."

dd if=/tmp/newboot_signed.img of=$BOOT_DEV

return $?
[G3 Android Development] Eliminater74:
I used sign too.. all multirom ports use sign..

Note: if you want a kernel bumped, just installed a bumped kernel. its the same as installing 777Kernels.. I dont understand what you are asking, Because MultiRom doesnt add anything

special outside from installing roms on secondary. and allowing you to boot from it. The kernels are something that you supply. if you install a bump kernel. then you should be fine.

I dunno.. my bootloader is unlocked and came unlocked. So never had to deal with bump. I just finished porting this MultiRom to every single g3 family there is. I dont have the time to

go though and figure out away to bump kernels that go though multirom.. my version is no different then Skin1980's other then its a newer version and will allow to install stock roms as secondary..
[G3 Android Development] :
Request: can the OP please post the list of patched kernel's that work on stock rom please?

I have used the old multirom before and as far as i know the latest patched stock kernel was chupachups kernel which is based on v20E and its old.

Thanks
[G3 Android Development] diogo.sena:
d855 16gb version, working perfectly here using CM12 + 777jon R10 kernel in primary rom, and stock as secondary, now we just need a stock kernel with the new multirom patch (i'm not asking)
[G3 Android Development] RL77LUC:
The problem here is that : if you install multirom AFTER kernel, then you'll have security error at reboot, so multirom must change something related to kernel signature.

And the bootloader on G3 is and will still be locked, probably forever. The only reason that makes us able to flash roms/kernel is that someone found a way to sign custom roms/kernels like LG (bump). We can't perform OEM-unlock like Nexus and all other unlocked-phones, which turns off the kernel signature verification.
[G3 Android Development] Yamen Nwilaty:
F400 , flashing twrp 3.0 .zip caused a secure boot eror and my LED keeps flashing red and blue then i tried to flash the recovery.img manually by flashify (unzipped the twrp 3.0 then flashed data-->recovery.img) and no luck.

please fix this i have never tried a multi rom yet and i really want to :p

have a nice day:D
[G3 Android Development] Eliminater74:
Ill try again.. Ill take the device tree from twrp github and try with that one.....

also, wont be for a bit.. cause im building Pac right now.
[G3 Android Development] Encinos:
Hi there, I'm using d855 32GB. There is a problem I encountered with the latest version of multiROM, v33. Secondary ROMs won't boot, says shuts down multiROM to avoid data corruption, with a page of klog on the screen. I would love to provide you this klog but I don't know where to locate it.

I tried mixing and matching with old TWRP and different versions of kernel, and in the end I went back to multiROM v32. V32 works with the latest TWRP 3.0.0-0 and the latest kernel rev12.3.

I don't have a primary ROM installed so I'm not sure if it works.

The closest thing I found to be logs are these two:

https://drive.google.com/file/d/0B8MIrCO6H1VDOGg3MGpzdlMtalU/view?usp=docslist_api

https://drive.google.com/file/d/0B8MIrCO6H1VDX2NKeUhNNTVDS1U/view?usp=docslist_api
[G3 Android Development] Eliminater74:
Attention Everyone:

I made a mistake.......... I forgot to add your device to the device board..........

Which is the reason for this error:

3>[ 7.169177 / 01-07 12:04:07.759] multirom: Unknown boardname 'd855'!
<3>[ 7.169188 / 01-07 12:04:07.759] multirom: Cannot load /zImage

I was in such hurry I forgot to do that.. Yes, no secondary rom will boot without your device being added in.. Let me redo it tomorrow..

It wont take long..................

Sorry peepz, my bad on this......... Ill fix it.
[G3 Android Development] marcdw:
I've read here and there that Aroma does not work with TWRP 3 built from marshmallow sources. Is that the case with this one? The one that uses KK (or LP?) sources is okay, or so I've read.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[G3 Android Development] thedevilslettucemd:
Mods please delete.
[G3 Android Development] Eliminater74:
Attention Everyone: This means all MultiRom and Recovery Alone Users:

I made a mistake on MultiRom: That will be fixed shortly, I know about the factory reset. Thats got to do with the /misc partition..

IT had to be commented out in the twrp.fstab and recovery.fstab files..... Which I have now done.. and its back to normal as it should be.........

I am Building NEW Working MultiRom & Recoverys for All Devices:

Stay Tuned........
[G3 Android Development] :
I'm on vs985. I flashed Twrp and wiped dalvik. i rebooted recovery and it wiped my apps. the rom was fine but it had tro be set up again. i restared to recovery and flashed nebula kernel vs985 12.3 mm and multirom and wiped cache and dalvik and got a secure boot error. im on xenonhd. what do i do?