yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] BIG_BADASS:
Well damn...

Good thing I switched my canadian H812 for the european H815.... I made the right decision......

I'm never buying this bull**** north american phones ever again all the features are locked.. bootloader is locked, carrier is locked, even certain OS featuers like VoLTE and even the bands and phone information screen you get from dialing MMI codes are locked, so I can't deal with this crap anymore.... from now on I buy only international or european version. I'm in Qatar now, alot of the same phones here have more SIM card slots or more CPU cores or RAM than the north american versions. To hell with them north american service providers locking all this crap and ripping you guys off... The reason European one doesn't have the bootloader lock is because it is open-market. In these countries mostly service providers don't sell the hardware with the plan, they give the plan alone.. most people buy the hardware separately from another vendor... which is actually much better when it comes to freedom of what you can do on the phone, and getting what you paid for..

Good luck to you SteadfasterX I wish you all the luck.. you will need as much as you can get....service providers make your job as difficult as possible so I respect the fact you will need some months to get it working.

Am praying on behalf of all LG G4 users with locked bootloaders you get this thing up and running without issues in reasonable time.
[G4 Android Development] XeniX_Force:
well since my phone is dead now, can you perhaps test for him? he has no testers right now
[G4 Android Development] BIG_BADASS:
Is it possible it may brick it?
[G4 Android Development] XeniX_Force:
your primary rom will stay safe. atleast mine did

second one (which ofcourse you will install for testing) will boot loop alot.

what's your mobile model and software version?
[G4 Android Development] steadfasterX:
Its very unlikely but there's always a risk. Never happened yet though.

The worst thing which could happen is a soft brick which can be solved with restoring a previous taken backup.

If you really think about helping check out the support section in the OP to get into IRC.

.
[G4 Android Development] BIG_BADASS:
I would be more than willing to help, but unfortunately I have one with an unlocked bootloader and it works perfectly. But I was in the same boat as all of you just 2 days ago.
[G4 Android Development] XeniX_Force:
deleted.
[G4 Android Development] BIG_BADASS:
Go 1 page back... its still there

---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------

Is the bootloader unlocked?
[G4 Android Development] J0SH1X:
Indeed I never buy a phone without the ability to run a custom. Rom (most cases the aokp, else the Ressurcution remix)

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] datorprofessor:
In practice; how is this different from multirom by Tassadar, I mean the end result? Of-course technique for loading is different, Efidroid can boot to linux and windows too in theory.

For me it would be enough to boot between Stock-rom and LineageOS 13. My question is, Will they share UserApps+data and will the two roms also share the internal-SD?

I own lg g4 unlocked and would test if you want. My next question is:

How many new mount-points does it creates? and what kind of read/write permission does it use to protect the newly listed partition from being manipulated when running other roms.

/-_________________________

This thing should have a new thread about running stock-kernel virtually on top of any roms (with the help of busybox like in Kali-linux-iso-image.) and let the camera-app speak/connect/hook with the virtual kernel while installed on custom roms. The intent is to get full working camera function with the hardware (laser OIS) and still running custom rom at the same time

____________________________-/
[G4 Android Development] steadfasterX:
As you said already: There are many technical differences but on a high level the end-result is the same: you get a boot menu screen when powering up and can choose what to boot.

Worth to mention nevertheless:

MultiROM has only one more requirement then efidroid: it requires a kexec-hardboot patched Kernel.

Either only on the primary ROM kernel when MultiROM was build with the "MR_NO_KEXEC" flag (which is very new btw!)

or every kernel in every ROM u wanna flash.

So the best option when u wanna use MultiROM is to build it with the MR_NO_KEXEC flag and patch the primary kernel only or just use efidroid (if it would work....).

Nice! I have not the time atm to debug the bootloops I encounter and I'm also out of ideas HOW I could do it until the efidroid re-write has been finished..

If you find a way it would be great or even when you just try & error all/multiple ROMs would help a lot.!!

If you try that pls report the excact builds tried - best with a download link. Tell if it works or not and if not what the error is (bootloop, etc)

For this technical stuff its best to ask the efidroid devs on slack http://join-efidroid.rhcloud.com/

but in short each ROM will be added to:

/data/media/0/multiboot/[YOUR-ROM-NAME]/

All the data will be in there e.g. the /system or /data you see in the booted ROM will be written there. You COULD share the data between but better ask that on slack bc i've never done so

.
[G4 Android Development] BIG_BADASS:
How much progress have you made since the last time I asked for a status update? FYI it's been 2 months since.
[G4 Android Development] steadfasterX:
no testers => no progress.
[G4 Android Development] BIG_BADASS:
You my friend, need to find some testers.... what models do you require testers for? I can give recommendations maybe.

I can offer my device if you're searching for H815 tester... with unlocked bootloader

---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------

I will wholeheartedly, more than gladly test for you

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

Also, what use does efidroid provide, if the bootloader is already unlocked? Don't you think it's better you test directly on locked ones?
[G4 Android Development] BIG_BADASS:
You have to give a solution to those who need it the most, at the right place, and at the right time. I don't know why you are bothering with the users of unlockable bootloaders, when they have absolutely no use for efidroid in the first place. Give up on them, and move-on to the users with locked bootloaders, as they are the ones that need it the most.

Isn't this just plain old common sense??
[G4 Android Development] steadfasterX:
as already said: any g4 H81x model will work

your reputation here at XDA is not the best so Im not sure if this is a

valid

offer but if it is: why asking? just test. read the previous post about what and how.

you don't know what efidroid is it seems.

The way how I develop is for a reason. It makes absolute no sense to work on efidroid in FIsH when normal efidroid on unlocked devices does not work.

I have to? I have to do nothing tbh. I do this in my free time and you want to tell me what i have to do? Its 100% up to me what I do and how I do it.

If you don't like it: Make it better. This would be much more useful then just complaining on all posts you see without any valid reasons.

Again: you have no idea what efidroid is. Before writing such complains you should be sure what you're talking about.

.
[G4 Android Development] IronTechmonkey:
[EDIT] Pulling back and getting on topic: Although I found this thread by accident I've always been curious about dual/multi booting Android devices. Bummer I only have Moto devices running custom ROMs (LOS) but reading the OPs has given me ideas about what to look for and what to expect if I decide to do something like this. Thanks.
[G4 Android Development] :
Post removed.

That will do it for off topic posts.

Thanks. :good:
[G4 Android Development] Minto107:
Hey man if you need testers, hit me up ;) I have G4 H815 GBR unlocked with 602 mobo ;)
[G4 Android Development] steadfasterX:
Nice! I have not the possibility atm (my device is on its way to LG...) to debug the bootloops I encounter but more important I'm out of ideas on HOW I could do it until the efidroid re-write has been finished..

The full rewrite of efidroid will take weeks,months,years though but up to then there is no real way to debug such bootloops.. I was in contact with the devs regarding this and they told me to wait ..

If you want you can just try & error all/multiple ROMs - this may help a lot!

If you do so pls:

create a full backup with the latest TWRP !!!!

Go to the OP and follow the instructions to setup efidroid

Try LL, MM, N

report the exact builds tried - best with a download link

tell if it works or not and if not what the error is (bootloop, black screen, etc)

If you want to go further:

try to enable or flash kernels which allow ADB in the boot process to make an adb logcat while the device is booting. but thats even more advanced so if that is nothing u can do no prob ;)

EDIT

For the announcement readers:

For more step by step go on here: https://xdaforums.com/showpost.php?p=72913646&postcount=46

.
[G4 Android Development] Minto107:
Allright ;) I was about to update my RR so I'll try to do that with EFIdroid ;) one question(just to be sure :D) after installing EFIdroid, will I be able just to boot back to my system or I have to do backup, create new OS from EFIdroid manager and then restore it to new OS?
[G4 Android Development] steadfasterX:
The very first thing is really to install the latest TWRP. Its important thats why I say it again ;)

There are many reasons to use always the latest TWRP but the reason for efidroid is: it will dump the current recovery partition and use it later to do all the efi tasks and so TWRP must be compatible with/patched for efidroid which is the case for the current TWRP only.

We can update TWRP manually as well but its easier to go the usual way.

Reg. your questions:

you will not touch your primary ROM - unless you are not doing things wrong ;)

Before doing anything else: Backup with TWRP the whole system,data,etc! Do this even before installing efidroid just for the case..

install efidroid and once efidroid is installed you will prepare (in your current - primary ROM) with the efidroid app the secondary ROM "slots".

Then you reboot and in

efidroid

you select booting to TWRP (

not

via the factory screen key combination or adb reboot recovery!! only from within efidroid!!!)

You get asked which ROM slot you want to use and you choose the one you created in the efidroid app before.

TWRP pops up -> now you have TWRP but it runs technically in the secondary ROM slot! That means everything what you do here happens in the secondary ROM only!!!

Wipe data? Install ROM? Wipe whole system? etc.. It will be done in that selected slot and not tampering your primary ROM (it shouldn't.. as long as there are no bugs but for this you have your TWRP backup... ;) )

So you will install a ROM now while here in TWRP - then reboot

you will see efidroid on every boot so now you can choose the secondary slot name (not TWRP) and it should boot the secondary ROM just installed before.

You can choose always the primary ROM (everything named "internal" is primary) when in efidroid which just boots the main ROM as it is right now.

Hope that answers your questions.. :)

.
[G4 Android Development] BIG_BADASS:
SteadfasterX my friend, you are #1.

Make us proud on next status update, Ok! :)

Good Luck, and hope you find some good testers! (I'm too scared to test)

---------- Post added at 06:51 AM ---------- Previous post was at 06:32 AM ----------

Now please tell me... what would be the PC equivalent of Custom Recovery software like TWRP?

Would it be something like Acronis TrueImage ?

Also, would it make sense to say that a locked bootloader in a phone (PS: Notice I won't say 'Android Device', because the bootloader comes into play BEFORE the Android OS) is the equivalent of having 'secure boot' enabled in UEFI in a Windows PC? Thereby implying that the process of disabling Secure Boot in UEFI in a PC is the same as unlocking the bootloader in phones?
[G4 Android Development] steadfasterX:
first you write you will test then you say my work is useless then you write I'm your friend and the #1 and now you're scared about testing? What's wrong here?

The other questions are off topic (again). Stop this please. Ask on other forums related to your questions.

.
[G4 Android Development] the_naxhoo:
is this project still in process?. I'm willing to help for a stable version if required.
[G4 Android Development] steadfasterX:
Well the the development of efidroid itself is stalled since a long time . Besides that I believe no one want to use it even if the current state is usable with some manual tricks already
[G4 Android Development] the_naxhoo:
ok, well... I tried to use it anyway, and I got the Error: "Can't allocate ramdisk boot memory at 2000000 size 21816824" when I pressed "

TWRP (Internal)

" and I choose any rom slot.

So I can't install any ROM and TWRP only boot without patching ramdisk.
[G4 Android Development] steadfasterX:
oh well yeah the kernel I use in newer TWRP is not patched for it... just another example how old this all is. If you are really interested in testing I can provide a patched version but in 2 weeks first
[G4 Android Development] the_naxhoo:
oh my :eek: ... hm it's ok for me, I can wait it. Thanks.

EDIT:

[MENTION=5545101]steadfasterX[/MENTION] well... just for curiosity I tried to use an old TWRP version (3.1.1) and it's worked perfectly!. I can boot on my 2 ROMs now! :D Everything in both ROMs works as it should be. Thanks again for this project. :good:

Oh, and one more thing, but this has nothing to do with EFIDroid: do you know or have an idea of why I can't connect to my Wi-Fis (I have 2 xD), when I put the password they just "save" but they never connect. (that happened with AOSCP and RR).
[G4 Android Development] steadfasterX:
lol yea that one is the only out there which should work then :) that was the first official from me and it had that patch applied. i forgot about that ;)

no idea about wifi but it maybe is efidroid related. keep in mind that this project is not very heavily tested so it may destroy data etc. always keep a backup of everything..

-
[G4 Android Development] the_naxhoo:
the issue of wifi was because I had an empty WiFi-MAC (00:00:00 ...) and it happened to me not only with EFIDroid but that I tried with your CypherOS ROM clean and the problem was still there :confused:... so I modified "config" file located in /data/misc/wifi and the issue was fixed.
[G4 Android Development] steadfasterX:
yea I can confirm that TWRP 3.2.1 does not work but 3.1.1 does. Same issue here. Even with a patched kernel!

I have asked Micha regarding that and he told me that this is one of the reasons for the rewrite.

I still try to figure out why it works in 3.1 then and hope for an answer on slack by him.
[G4 Android Development] adam_s_459_:
Hello steadfasterX, i have an H812 and saw that you needed testers for this. i really want this project to succeed so i am fully able and willing to test if you want me to. if there is anything in particular you would like me to try just say the word. Thanks for this project!
[G4 Android Development] steadfasterX:
Thanks but I am kind of stuck here at the moment because the main source base is moving to a complete rewrite which I guess will take years to complete.. besides that the current state is quite usable except for the limitation of TWRP of course
[G4 Android Development] Spaceboy60:
Play store link no longer works. Any working links?
[G4 Android Development] steadfasterX:
Seems he removed it due to the rewrite.. Download it from his thread here:

https://xdaforums.com/devdb/project/?id=16767#downloads
[G4 Android Development] adelpozoman:
What you give to the G4 and its community and users is unvaluable. Thanks!
[G4 Android Development] Spaceboy60:
Not working for me. Keep getting error : cannot load device info, please check your connection : no value for lge/H815
[G4 Android Development] adam_s_459_:
Just copy and paste this in into your build.prop using a root file explorer (without the quotation marks)

"efidroid.server_url=https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master"
[G4 Android Development] Spaceboy60:
Thanks, unfortunately I then get an error about needing root (not sure if issue with magisk: is granting root, but still comes with that message, had it with one other app too even though once again root being granted)
[G4 Android Development] adam_s_459_:
Go into magisk and see if u can find the app and Grant root permission manually. U could u'nkow also follow the guide in the OP that outlines how to do it perfectly lmao. It requires adb
[G4 Android Development] Spaceboy60:
Yes, I done that. App still says no root (even though magisk dialog comes up with "root permission granted ")
[G4 Android Development] adam_s_459_:
So you're getting an error in the efidroid manager app? Or is it somewhere else?
[G4 Android Development] Spaceboy60:
Yes. efidroid manager app.:
[G4 Android Development] adam_s_459_:
I'm assuming you have granted premission manually and that you are rooted, so have you tried a different version of the app? Or maybe reinstalling magisk? Also what rom are you on and do you have the latest magisk manager? If you have tried all of this then maybe install supersu
[G4 Android Development] Spaceboy60:
EFIDroidManager_1.0-g82cc5f5 is one i installed. Yes, I manually granted permission. Running 17.1 (was running 27.2 but used the direct download option in magisk to downgrade). Magisk manager is 6.0. ROM is AICP Latest. Could try magisk 16 I guess otherwise supersu only option,but lose the magisk modules with that.
[G4 Android Development] adam_s_459_:
Yeah I guess that's all u can do:confused:
[G4 Android Development] Spaceboy60:
Well flashed supersu latest beta, didn't even show up in my app drawer. Didn't give any errors when I flashed, so guess I'm a bit stuck. Magisk 16.7 didn't work on terms on EFIDROID recognising root.
[G4 Android Development] adam_s_459_:
You have to download the superSU app from the internet
[G4 Android Development] Spaceboy60:
Apparently I just have to extract superuser.apk from the common folder. So will try again tomorrow
[G4 Android Development] Spaceboy60:
Ok, tried supersu, same result : no root error in efidroid (AMD permission is granted! I checked in super su)

Edit: can somebody confirm A ROM/Rooting method where they've had no issues with this app?
[G4 Android Development] Spaceboy60:
OK,reinstalled a different ROM as I've was having some other issues, now I can't get past this point. Used Root Explorer to modify build.prop in /system and saved the file. Rebooted and same error.
[G4 Android Development] adam_s_459_:
What is you're phone model? If it isn't H815 try changing it to H815 in the build.prop
[G4 Android Development] Spaceboy60:
It's H815
[G4 Android Development] adam_s_459_:
Can you screenshot the error?
[G4 Android Development] Spaceboy60:
Here you go :
[G4 Android Development] steadfasterX:
It's important to follow this order:

1) clear app cache and app data of efidroid manager

2) uninstall efidroid manager

3) set the property as written in the OP

4) install efidroid manager and start it

Unfortunately the app has a cache issue so once started it will not update the url set in the build prop unless you remove the cache and data of that app (there is another way but this one is the fastest and easiest)
[G4 Android Development] Spaceboy60:
Done that 3 times, no change
[G4 Android Development] SnowFuhrer:
It says it's for a g4 but would it work on any lg?
[G4 Android Development] steadfasterX:
Ok then I have to check it here first because I currently do not have it installed .

The concept will work on many devices but it is always a device model specific build needed
[G4 Android Development] steadfasterX:
Regarding that error I may have to adjust something here:

Please do this on your phone:

adb shell (or open a local terminal)

getprop

Copy the whole output and paste it to http://bpaste.net or attach it to your answer
[G4 Android Development] Spaceboy60:
https://bpaste.net/show/30db21ef0f7a
[G4 Android Development] steadfasterX:
hm ok thats the problem: you havent set the efidroid OTA url correctly.. (line 51 of your bpaste)

Do the installation as stated in the OP again, I have updated it to do it in TWRP instead of Android which is more bullet proof.

Ensure you copy the URL correctly this time ;)

(btw : there is a tiny thx button ;) - for

useful

posts)

EDIT: important you NEED the latest efidroid app which seems to be removed everywhere but I had a local copy.

Find it in the downloads tab of this thread and use that one - otherwise it will never pass the root check

.
[G4 Android Development] Spaceboy60:
I do those commands from Windows command line?
[G4 Android Development] steadfasterX:
Those commands? You must follow the guide and boot to TWRP. Whenever you see a command to be executed it must be done either from a local terminal or from the PC terminal . as usual I recommend FWUL for all the stuff but whatever works for you
[G4 Android Development] Spaceboy60:
Thanks, finally got it up and running
[G4 Android Development] steadfasterX:
Ok great!

(and I'll live with the fact you still ignore the thx button :rolleyes: )
[G4 Android Development] daiskun:
Hi, i'm willing to try it on an h815 usu'd device, what extra steps do i have to take? I'm on nougat with supersu installed
[G4 Android Development] steadfasterX:
@ all readers:

I may be able to restore a state where I can build efidroid again. I was in contact with the dev and he gave me a manifest which at least syncs but fails on build.

I think that's fixable and if I fixed that I may can do more regarding newer TWRP versions.

UPDATE:

ok "fixed" the compile errors and hope it will boot :D

Ensure you read and understand the known issues first.

That means you need to remove the ASSERT line(s) on any ROM you want to install in the secondary slots.
[G4 Android Development] Xsavi:
Willing to Test.

Hello [MENTION=5545101]steadfasterX[/MENTION] I just wanted to thank you for bringing EFIDroid to the LG G4. I have a LG G4 H811 (First three S/N 510), and I saw your post that you needed testers. I am more than willing to help you test out EFI Droid. I have more than enough time as I have nothing to do ATM.

What I have done so far:

Followed your exact instructions, managed to get a secondary ROM to boot, but I am facing permission issues.

My Setup:

TWRP Version: 3.1.1-0

Primary ROM:

Stock ROM version 20x

Llama Sweet Kernel R7 Marshmallow (Not stock): Link to Kernel Thread

Latest SuperSU v2.87

Secondary ROM:

Atomic OS LabMade v2.5 H811 10/25/2018 (Oreo): Link to ROM Thread

Issues: Internal Storage not showing up, Apps constantly crash. Seems to happen mainly when trying to write to the internal storage.

Boot Log (Got it during boot, and it is quite a bit. Recommend viewing this on a PC): https://bpaste.net/show/6088c6cc8828

Logcat of app crashing: https://bpaste.net/show/6680d6b2ad0b

Another interesting thing is when you connect it to a computer, it doesn't show the regular internal storage, it shows "Shared Internal Storage" (Screenshot provided).

Everything boots. There is just storage issues.

Next, I am going to try Nougat (Stock based and Non-Stock Based) and report back.
[G4 Android Development] steadfasterX:
do you have read post #2 ---> "1) random app crashes, settings do not persist on reboot" ?

.
[G4 Android Development] adam_s_459_:
[MENTION=5545101]steadfasterX[/MENTION] if you have the ability to build now, do you plan on trying to debug some of the issues? Or is this project dead?
[G4 Android Development] steadfasterX:
It's not dead just paused
[G4 Android Development] Spaceboy60:
Flashed twrp 3.1.1 and still getting ramdisk error when I select it. Any ideas?
[G4 Android Development] steadfasterX:
Impossible.. When you say you have flashed it: when? Before or after installing efidroid?
[G4 Android Development] Spaceboy60:
It may have been after. Presuming I should have done it b4?