yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] bambotcha:
How to update from the old MultiRom to the new resurrected MultiRom ? Can it be done ?
[G3 Android Development] Eliminater74:
I think 2 ways that should work.

Method 1:

Download the MultiRom Uninstaller and flash it... Then install the new MultiRom

Method 2:

Just flash the zips over your pre multirom.. since im sure Tassadar didnt change the dir struct very much.. should have no issues..

I would try method 1....................................
[G3 Android Development] thatkindaguy:
How the hell do I uninstall multrom?
[G3 Android Development] suljo94:
you flash the Uninstaller zip
[G3 Android Development] thatkindaguy:
I just did before your reply and I got.the secure boot error. Luckily I could get into download mode, so I flashed back to stock.
[G3 Android Development] suljo94:
just reflash the sharpening mod in that case
[G3 Android Development] nicsnyx:
Have anyone ever tried MIUI6 as a secondary rom ??

i have tried and then bootloop at LG logo screen :(
[G3 Android Development] thatkindaguy:
I think you misunderstood my first post. I had to use LG flash tool to revert back to complete stock. The uninstaller zip completely unistalls TWRP and doesn't replace it with the original TWRP, which gave me the secure boot error.
[G3 Android Development] bambotcha:
I successfully installed MultiRom and I am running Euphoria as my primary ROM , but when I restored my Cloudy 2.3 ROM as a Secondary ROM and try to boot it I got a message saying that Kexec-hardboot support is required to boot this ROM , Primary still working fine.

Any Suggestions ?

Thanks for the great work.
[G3 Android Development] Eliminater74:
The Uninstaller doesnt Uninstall TWRP it only uninstalls MultiRom.. it deletes all the Dirs that go with MultiRom. IT DOESNT UNINSTALL TWRP.

and if you only got a boot error, then you have no idea if you still had twrp or not.. hence the locked boot loader..........

So dont go about saying that it uninstalls twrp when it doesnt............................

If you dont believe me send [MENTION=3418703]Tasssadar[/MENTION] a msg and ask him................
[G3 Android Development] Eliminater74:
I missed this message, anyhow, You need a kernel that supports the new hardboot patch.. Not Skins version....... So get 777Kernel for primary..

I would say you could use mine, but Im not going to say that... thats all up too you.. I know there are at least 3 dif kernels here that support the new patch............
[G3 Android Development] lapocompris:
Do you guys know any V20P patched kernel ?

I tried Gabriel but it lowered the Antutu score down to 29k.
[G3 Android Development] suljo94:
Gabriel is the old patch and antutu doesn't actually mean anything

[MENTION=5687366]Eliminater74[/MENTION] maybe you can ask the kernels that support the new patch to list multirom resurrected instead of just multirom and if you add that to post 2(something like search for kernels that say multirom resurrected) it might help with the confusion
[G3 Android Development] bambotcha:
Thank you for your quick reply , I installed 777 kernel R10 , the error messege no longer appears but upon booting the stock ROM ( secondary ) I get an error messege telling me that a log is generated that I can show to the developer , when I navigate to the multirom folder I find no files there , Any suggestions

And thanks for your support
[G3 Android Development] Eliminater74:
depending on how far you get into the boot process, there is /proc/last_kmsg and there is upon boot when you see the multirom menu hit advanced and then click copy log

or you can copy log while in twrp ..

Best bet is the last_kmsg But be warned, last_kmsg is for failed boots. it records the kernel messages up to the failed part.. but after you reboot again. its gone...............

it only records the last and I mean last failed boot msgs.. as long as you get far enough into the boot process......
[G3 Android Development] bambotcha:
This is the Log that i saved after the boot failure,

Thank you in advance
[G3 Android Development] Eliminater74:
20<Elimin8er>30 Tassadar, http://paste.ubuntu.com/11959483/ <---
18<19Tassadar18> nothing in there
20<Elimin8er>30 nothing related to an error or nothing as in blank log?
18<25rirozizo18> no errors
18<25rirozizo18> i can see it, so i bet he can
18<25rirozizo18> Tassadar: what does "has_bootimg: 0" actually mean?
18<25rirozizo18> shouldn't every rom have its bootimg?
18<19Tassadar18> if 1, then it is not sharing the kernel with primary rom
18<19Tassadar18> these days all of them should have the bootimg
18<25rirozizo18> ah i see
18<19Tassadar18> except for internal
18<25rirozizo18> that's why internal is obviously 0

There you have it. The man him self cant even see any errors out of that log....

So whatever your doing wrong isnt related to MultiRom..

Maybe a little more nfo, Like what roms are you using for primary and secondary and what kernels and how did you install your secondary..

try to use a nandroid backup..
[G3 Android Development] bambotcha:
Thanks for your reply

Primary is Euphoria ROM with 777 R10 kernel , Secondary is Cloudy 2.3 based on stock ROM , Installed the secondary ROM by restoring a nandroid backup.

As soon as i press on the secondary ROM to boot it says:

An error occured

Shutting down MultiROM to avoid data corruption.

Report this error to the developer

Debug info:/sdcard/multirim_log.txt

Last lines from klog :
[G3 Android Development] Tech_Savvy:
That error accured to me when i didnt have the proper boot. Img..
[G3 Android Development] bambotcha:
Thank you very much its working now
[G3 Android Development] skrypj:
Can anyone suggest a kernel for a stock rom that works with multirom I tried Navel with Cloudy 2.5 for the D850 but I get a secure boot error after that.

Another question: I just got my phone, rolled back to 10D, rooted, TWRP'd, then flashed Cloudy 2.5. Do i need to flash a Lollipop patched 20f boot.img to properly run multirom?
[G3 Android Development] rob0809:
Where did you get the stock boot image? I'm trying to boot a secondary stock image (Jasmine) and it hangs.

Thanks!
[G3 Android Development] nicsnyx:
i have tried to installed r12 777 kernel many times

but it have no effect and still be the original kernel from euphoriaOS as a primary rom

how to flash a new kernel for PRIMARY ROM ??
[G3 Android Development] tetrahedonism:
Any luck on getting the D852 version going? If you need a test subject, let me know! :D
[G3 Android Development] Eliminater74:
I didnt forget you man, I jut been having alot going on right now.. and Im stepping back a bit before my head explodes...
[G3 Android Development] tetrahedonism:
No worries! Thanks for the update! :) Good luck with everything!
[G3 Android Development] suljo94:
just flash it in twrp, if it doesn't work get us a recovery log
[G3 Android Development] nicsnyx:
i figure it out

i am able to flash r9 r8 r7 r6

however r10 r11 r12 is able to be flashed but not stick with the rom

i think it is a 777 kernel problem, does not a multirom problem

however thx for notice my question
[G3 Android Development] suljo94:
if you try it again get a recovery log so that jon777 can fix the issue
[G3 Android Development] bambotcha:
I installed Navel kernel v2.3 for my phone (D855) , and it worked perfectly

---------- Post added at 09:36 AM ---------- Previous post was at 09:34 AM ----------

Navel is working perfectly you just need to flash the sharpening fix zip to git rid of the secure boot error

EDIT : This is of course for the secondary ROM , you can't have stock as primary
[G3 Android Development] chacho_2me:
help. having issue booting 2nd rom

Security error

primary RR rom

2nd Slick rom

procedures done

1. installed RR rom(already)

2. Installed 777kernel

3.installed multirom twrp

4.installed installed multirom

5. installed slick rom on 2ndary

(very long 90%)

6.installed navel kernell (very long 70%) on 2ndary

7. installed sharpen fix on primary

still SECURITY BOOT on 2ndary

8. installed 777kernel primary

still SECURITY ERROR on 2ndary

what i do wrong? huhuhu
[G3 Android Development] Illogi.xbone:
Which device are you using? I had issues with 777 kernel, it wouldn't flash, try Nebula which is based off of 777 but does have more features. If anything boot into your primary and see which kernel is flashed.
[G3 Android Development] Eliminater74:
Send log, plz post log....... at least attach it.. thank you..
[G3 Android Development] Illogi.xbone:
I think it is just an issue of 777 kernel flashing or not.
[G3 Android Development] chacho_2me:
Hi guys.suri for the late reply.. all ok. im not really sure what happened... but only flashing 2ndary stock rom did the job. i thought there was a need to flash kernel since flashing rom would stop at 90% when flashing a kernel. anyway all ok now.

for others like me. here is what i did

1.same as previous post but only until step 5..

cheers.

also sir. i know getting log when phone is on. but how to get log when phone is booting? will try read old posts. maybe there ar infos on that
[G3 Android Development] Illogi.xbone:
When in the boot menu scroll to the right. There is a log button.
[G3 Android Development] Eliminater74:
Update: This is just a note to all, I am thinking of recompiling all with UBERTC, since it seems to work best and faster for the most part.... So keep at look out for new updates soon..

Also, F400 and D852, I didnt forget you.. I will add you this go around.............
[G3 Android Development] Eliminater74:
Project Update: Been a while.. its not like [MENTION=3418703]Tasssadar[/MENTION] updates MultiRom everyday.. anyhow I just wanted to post some findings and nfo.

[MENTION=4794976]777jon[/MENTION] has found something for me that might help with the peepz in the locked bootloaders, that need bump.. Good ol Bump.....

# D851 This nfo is of no use to you...............

Anyhow [MENTION=4794976]777jon[/MENTION] found this: GitHub: Cbump

Just maybe I can implant that into MultiRom ifdef Needbump := true that it will

call upon that and bump your images auto.......

### Note to all Device ####

I compiled MultiRom and the TWRP with UBERTC, and I gota admit, its much smoother and faster then it was before.......

Now that im trying to fix a issue with my kernel and MultiRom. ill be jumping back in forth between the 2.

Well thats all folks.. This was just a little Update as to MultiRom.....................................
[G3 Android Development] Hoomey:
That literally saved me from a complete reflash as I though that problem might be fixed and I messed up with my MultiRom/BlissPop/Nebula Kernel combo. Simple Kernel reflash and reboot fixed it. Always worth looking through old posts.
[G3 Android Development] Eliminater74:
Attention: I can now be reached though IRC on Channels #NebulaKernel and #MultiRom

at this Link: W-IRC: FreeNode

Just enter your Nickname and verify that your not a bot and click connect.
[G3 Android Development] b_randon14:
I got multiROM installed no problem on d850 using 777jons R16 kernel. My primary is cm12.1 nightly. I tried to add the debloated 20f stock ROM as my secondary but for some reason it ends up overwriting the cm12.1 system. I have tried installing from both the internal sd and the micro SD. When I navigate to /data/media/0/multiROM/roms/debloated20f/system it is empty.

I think it may be because the updater-script for the debloated rom installs it by writing the system.img to /dev/block/platform/msm_sdcc.1/by-name/system. Does anyone think that would cause a problem? Does the multiROM TWRP redirect this dev entry to the "system" for the secondary rom? Or does the updater-script for a secondary rom need to write the system data in another method?

EDIT: I installed the secondary rom(debloated 20f) by going into Advanced>multiROM>add rom and I choose internal storage and then select the zip.
[G3 Android Development] Hoomey:
Just gonna post here saying that it works just flawless (D855). Even if you don't use it for experimenting or to keep work and private stuff separate, just reboot if you want an hour or two of silence or maximum battery life without playing around with stuff. Just as easy as that. If there is ever going to be the option for Win10M/Android dual boot, my life would be complete.
[G3 Android Development] Eliminater74:
I heard word about Win10 on android devices.. but not sure on that.......... Im a beta tester for M$ thats only how I know.
[G3 Android Development] :
I thought I heard that you couldn't use multiRom with Android 5.0 and Android 5.1 but I guess I heard wrong ?
[G3 Android Development] marcdw:
Right. At one point I had 5.0, 5.1, and a KitKat ROM running. No probs. [emoji106]

---------- Post added at 12:07 PM ---------- Previous post was at 11:10 AM ----------

So, story time. Two days of strangeness starting Thursday.

I'm a tester for D851 OctOS. New build was up for testing. Flash 8/20 M2. It had some issues and was about to report but find they have a new build out. Remove the ROM.

Flash 8/20 M4 successfully. Reboot and all I'm getting is LG logo in a loop instead of the normal multirom boot menu. No idea why.

For the next almost two hours I'm reflashing Nebula kernel, reflashing and restoring Pac-Man, etc., but all I'm getting is the loop. In between that I reinstall TWRP and multirom. Still no go.

Gotta go to work and would like access to a ROM but it's not looking good. At the last minute I flash 777kernel R7 and lo and behold I get the boot menu. Was gonna boot Pac-Man but that would take too long so I went to a secondary (Fusion or MoKee).

At the time I didn't notice that OctOS was not in the secondary list. Maybe it overwrote the primary. I don't know.

After work I go through the process of fixing up Pac-Man. Restored nandroid but was back in a loop. Wiped dalvik, cache, and system. Flashed ROM on top, updated gapps, then SuperSU.

Boot up was okay now. Brought apps and whatnot current. Reboots are fine.

Since all is good let me reflash latest Nebula.

Oops, back to LG looping.

Flash 777 R16 this time and boot is okay.

Friday night/Saturday morn.

But just before posting this something new has been added. After work today I'm in a game and was immediately thrown into the LG logo, and a loop.

This time I couldn't get out of the loop. Even the method to get to TWRP wasn't working.

For no reason in particular I plugged in the charger and the boot menu immediately appeared. That was unexpected. Hmm. I wonder...

Go into recovery and flash Nebula. Reboot and all is okay. Hmm once again.

Unplug phone and reboot. Loop once again.

Timed just right I do the power/volume-down thing and plug in charger, then get into twrp. From there I reboot again to Pac-Man.

So with all that noise I just wrote I couldn't say at what times I was plugged or unplugged on the first day's issues.

Symptoms of a failing battery? If so would that have affected my flashing of OctOS? Or something else.

[I have since flashed another OctOS build to secondary without issue earlier Friday.]

I know it all sounds disjointed but I can't figure out why phone is unstable since the flashing.
[G3 Android Development] tetrahedonism:
Psssssst! Any news on a D852 build yet? :D
[G3 Android Development] :
To be honest. I think its kernel related. Did you get it working?
[G3 Android Development] b_randon14:
So this may be a stupid question but you can flash stock based roms as secondary roms using the latest multiROM corrct? I have cm12.1 with 777jon kernel installed and multiROM installed fine. I tried to install a debloated stock based ROM and it overwrote the cm12.1 install. After getting everything restored and back working I installed a second install of cm12.1 and it worked fine.

So my question is can you install a stock 5.0 based ROM as a secondary rom using multiROM? I use cm12.1 as my daily driver but I would like to be able to boot into a stock rom every now and then for the camera features. Thanks!
[G3 Android Development] NatusVincere:
Yes stock ROMs should work as secondary ROMs. I personally use Blisspop 3.9 as primary and Cloudy 2.5 (not stock, but stock based, 5.0 ROM) as secondary.

As for the camera on AOSP I would recommend you to flash HTC M9 Camera. I find it pretty good.

Direct download link: http://www.mediafire.com/download/8a0d1afyt7my6fe/HTC+M9+P-80512015.zip

Original post: https://plus.google.com/+JishnuSur16061993/posts/PKBzsgfqxfV
[G3 Android Development] b_randon14:
Okay I guess it's just the way the debloated 20f rom I tried to install installs its system. It contains a system.img and just extracts that to /dev/block/platform/msm_sdcc.1/by-name/system.

I will look into cloudy though. I downloaded it and was looking at its install script and I didn't like how it flashes all kinds of other partitions. I guess it's where people could upgrade from KitKat so it needed the lollipop bootloaders and all that.

Do you know if the newer cloudy roms will work as well?

And also do you just install normally as in go to advanced>multiROM>add rom and choose the cloudy zip?
[G3 Android Development] NatusVincere:
Like I said I'm using the 2.5 build which is the latest one so...

Yes it's simple as that, advanced multiROM, add ROM, choose zip, flash, then aroma installer appears, you choose version and some other stuff and done.

Didn't get the part you spoke about bootloaders, but I'm still on kitkats one.
[G3 Android Development] b_randon14:
Just realized 2.5 is the latest. And yeah I guess I am on KitKat boooaders. My phone came already updated to 5.0 so when I was installing a bumped TWRP, I had to flash the KitKat laf and aboot. I am assuming that cloudy includes these KitKat laf and aboot so that the bumped kernel will work?
[G3 Android Development] NatusVincere:
I don't think Cloudy zip will touch your laf and aboot and it has a kernel that comes with it which is already bumped I guess. I replaced that kernel with Gabriel, it has much more features. Works perfectly well here as both secondary ROM and long ago when I used it as primary.
[G3 Android Development] marcdw:
That right there is probably enough to get me to try CloudyG3 (still have and use v1.2 KK every so often). Haven't used any stock(-based) Lollipop ROMs on this phone and always had reservations about them. Didn't want to screw things up.

Will give it a go soon.
[G3 Android Development] marcdw:
No sir.

This morning phone is plugged and fully charged. Took care of all my phone business, calls, etc.

Unplug phone, reboot, and it just loops. Running Nebula.

Got into twrp, do the standard clearing and flash 777 again. Loopdee loop.

Plug phone in, no loop. Go back to Nebula, no loop.

Another unplanned test: I was at the boot menu ready to select a ROM. Not plugged in it immediately started looping before i could select.

I'm at a loss.
[G3 Android Development] VvUuOo:
confused don't know why?

So I did everything what I was told to do how and it didn't boot up after that but I made a buckup of my whole phone. My phone is lg G3 d855

---------- Post added at 05:19 AM ---------- Previous post was at 05:13 AM ----------

I forgot to say that when I did boot up it just said some kinda code

Like

"500" something*

"501" something*

"502" something*

"503" something*

*Something I meant I don't remember what is said

Then my screen blacked out and my notification led was bling red over and over until I took battery out and restored the buckup
[G3 Android Development] MrComputerRevo:
You did not flash sharpening fix for the main ROM. Flash that and it will boot fine.
[G3 Android Development] :
Any change to'increase the brightness? The light is really low and you can barely see the boot options outside if the sun is shining. ?
[G3 Android Development] VvUuOo:
Thanks for the reply and I'll flash that ROM and tell the feedback.

---------- Post added at 05:17 PM ---------- Previous post was at 04:46 PM ----------

It worked thx
[G3 Android Development] squabbi:
Finally working! :D

Ok I have the D855 and this is what I did:

Installed AOSP ROM (Paranoid Android 5.1)

Flashed Multi-ROM TWRP

Reboot Recovery

Flashed 777 AOSP Kernel

Flashed Multi-ROM

Added new ROM (AICP)

Added Cloudy G3 2.2 (Gets stuck at 90%, after 10 minutes the phone shut off and then I had to pull the battery and reboot back into recovery).

Selected Cloudy and flashed Chubachups 2.1 kexc kernel

All 3 ROMs booted properly and without issues. :)
[G3 Android Development] Eliminater74:
Project Update: Thank to [MENTION=4794976]777jon[/MENTION] for this find, We now found a Cbump which runs on android, Going to take a crack at implanting it into MultiRom and twrp's source. so that it will auto bump your images.....

Not sure how this is going to work. I dont have a locked bootloader.. and I havent started on it yet.. still trying to map everything out in my head.......
[G3 Android Development] Wimmme:
Good news, will try again this evening. Last attempt gave me bootloops on second ROM (RR, Cloudy, ...)

Also good news, tnx for the effort !
[G3 Android Development] aamer513:
Where is kernel patch????

Iam on stock rom lion 5.5 on my g3 d855
[G3 Android Development] aamer513:
Can anyone send the link of kernel which supports multirom
[G3 Android Development] cick:
I've been having some trouble on my VS985 when trying to get this going. I started the process on BrokenROM, and proceeded as follows:

-Install MultiROM TWRP

-Reboot into new recovery

-Install 777 kernel (R16)

-Install MultiROM

-Install Sharpening mod

Now, at this point, the internal ROM will boot, but usually I'll have to hard restart once or twice for MultiROM to start (I've repeated this process several times, in vain it seems), and sometimes another hard reboot after that, as the ROM startup appears to hang and just gives me a black screen. Next, I'll try installing a secondary ROM. I've tried Jasmine 8.0 which has 24B baseband (relevant?), and SkyDragon 4.0.0 (23C). In both cases after installing, I can no longer boot the internal ROM and it changes the boot animation to Verizon and continues to bootloop after choosing internal from MultiROM. When I attempt to choose the secondary ROM, it simply restarts the device and hangs at the LG boot screen.

I'm obviously doing something wrong, but I'm not sure what. I apologize of this has been a problem for someone else in the thread, I've read a bit (not all) and haven't seen this. Any insight would be GREATLY appreciated. :D

And thanks for the devs ahead of time for all the hard work you guys do.

Edit: Also, though I'm not familiar with coding or building, I'm very willing to test device specific files, though it seems it's not needed as it doesn't seem others are having much trouble.
[G3 Android Development] suljo94:
when multirom shows up press the get log button and post it here
[G3 Android Development] cick:
Will do. I don't have time to do it now, about to leave for work. Removed all elements of multirom for now, since I have to have my phone fully functional.

At which point should I get a log? Or do all logs persist through removal?
[G3 Android Development] suljo94:
when booting up the multirom menu should appear
[G3 Android Development] :
If its does not it means something went wrong. I got sometimes a missing boot menu. also I found out there is a mini game available ?I must be slow
[G3 Android Development] Eliminater74:
If the multirom menu isnt showing up then either you are not using a kernel that has kexec hardboot patch or you didnt flash multirom setup zip...........

Your primary kernel must have the kexec hardboot patch or no menu and no booting secondary rooms.

but long story short, to get the menu you need to have the boot img injected into multirom. for it to read it and display a menu. otherwize it wont work..

you can flash a kexec hardboot patched kernel all day and night.. but if its not getting injected.. then you will not see a menu.. Supposed to auto inject unless you removed that

checkmark. you can manual do it in settings/multirom settings.. then inject current boot image....