yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dedraks:
Here is the output:

carlos@carlos-HP-Pavilion-11-x360-PC:~/android/uefidroid$ fastboot oem findbootimages
...
(bootloader) found ELF32 image on sbl1
(bootloader)	Entry: 0x08008080
(bootloader) found ELF32 image on rpm
(bootloader)	Entry: 0x00000009
(bootloader) found ELF64 image on tz
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF64 image on devcfg
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF32 image on aboot
(bootloader)	Entry: 0x8f600000
(bootloader) found ELF32 image on cmnlib
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on cmnlib64
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF32 image on keymaster
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on prov
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on rpmbak
(bootloader)	Entry: 0x00000009
(bootloader) found ELF64 image on tzbak
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF64 image on devcfgbak
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF32 image on abootbak
(bootloader)	Entry: 0x8f600000
(bootloader) found ELF32 image on cmnlibbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on cmnlib64bak
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF32 image on keymasterbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on provbak
(bootloader)	Entry: 0x00000000
(bootloader) found QCOM MBN image on modemst1
(bootloader)	ID:16(ramfs1) version:3
(bootloader)	Image: src:000001d8 dst:890198c0 sz:0017fe00
(bootloader)	Signature: src:891996c0 sz:00000000
(bootloader)	CERT chain: src:891996c0 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found QCOM MBN image on modemst2
(bootloader)	ID:17(ramfs2) version:3
(bootloader)	Image: src:000001d8 dst:e1600200 sz:0017fe00
(bootloader)	Signature: src:e1780000 sz:00000000
(bootloader)	CERT chain: src:e1780000 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found ELF32 image on metadata
(bootloader)	Entry: 0x02fb5fdf
(bootloader) found Android image on boot
(bootloader)	Kernel: addr:80008000 sz:008b6e28
(bootloader)	Ramdisk: addr:81000000 sz:001a29f4
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:0004d096
(bootloader)	pagesize:2048
(bootloader) found Android image on recovery
(bootloader)	Kernel: addr:80008000 sz:0087cce0
(bootloader)	Ramdisk: addr:81000000 sz:003a2a87
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:00190800
(bootloader)	pagesize:2048
OKAY [ 0.608s]
finished. total time: 0.608s
[Android Software/Hacking General [Developers Only]] :
same here on Xiaomi Mi Max (hydrogen), after booting uefi_boot.img the phone just reboots

(bootloader) found ELF64 image on devcfg
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF64 image on devcfgbak
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF32 image on sbl1
(bootloader)	Entry: 0x08006760
(bootloader) found ELF32 image on sbl1bak
(bootloader)	Entry: 0x08006760
(bootloader) found ELF32 image on rpm
(bootloader)	Entry: 0x00000009
(bootloader) found ELF32 image on rpmbak
(bootloader)	Entry: 0x00000009
(bootloader) found ELF32 image on cmnlib
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on cmnlibbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on cmnlib64
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF64 image on cmnlib64bak
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF32 image on keymaster
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on keymasterbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on tz
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF64 image on tzbak
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF32 image on aboot
(bootloader)	Entry: 0x8f600000
(bootloader) found ELF32 image on abootbak
(bootloader)	Entry: 0x8f600000
(bootloader) found QCOM MBN image on fsg
(bootloader)	ID:20(backup ramfs) version:3
(bootloader)	Image: src:000001d8 dst:00000000 sz:0017fe00
(bootloader)	Signature: src:0017fe00 sz:00000000
(bootloader)	CERT chain: src:0017fe00 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found QCOM MBN image on modemst1
(bootloader)	ID:16(ramfs1) version:3
(bootloader)	Image: src:000001d8 dst:88f53130 sz:0017fe00
(bootloader)	Signature: src:890d2f30 sz:00000000
(bootloader)	CERT chain: src:890d2f30 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found QCOM MBN image on modemst2
(bootloader)	ID:17(ramfs2) version:3
(bootloader)	Image: src:000001d8 dst:e1600200 sz:0017fe00
(bootloader)	Signature: src:e1780000 sz:00000000
(bootloader)	CERT chain: src:e1780000 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found Android image on boot
(bootloader)	Kernel: addr:80008000 sz:0096f409
(bootloader)	Ramdisk: addr:81000000 sz:0019255e
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:00000000
(bootloader)	pagesize:2048
(bootloader) found Android image on recovery
(bootloader)	Kernel: addr:80008000 sz:00966d30
(bootloader)	Ramdisk: addr:81000000 sz:00976799
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:00000000
(bootloader)	pagesize:2048
[Android Software/Hacking General [Developers Only]] magdeoz:
I'm trying on the Moto G4 msm8952, lk.img compiles without problems, but when boot with fastboot it stays on the splahscreen and from there nothing happens.
[Android Software/Hacking General [Developers Only]] MishaalRahman:
Glad to see this project get some love, let's hope that trend continues.
[Android Software/Hacking General [Developers Only]] SRIHARI_GUY:
Same here but instead of staying on the splashscreen it reboots to the system after a second or two . If flashed via TWRP or fastboot , it makes the screen flashing for eternity

Moto G2 msm8226
[Android Software/Hacking General [Developers Only]] 7root:
Yes it's a known issue and it's being worked on. See here: https://github.com/efidroid/projectmanagement/issues/89
[Android Software/Hacking General [Developers Only]] SRIHARI_GUY:
Hope it is fixed so titan could see a full working multiboot environment.
[Android Software/Hacking General [Developers Only]] 7root:
It's not working on Titan? Hm, I suggest leaving that info on the GitHub page from my previos post so that it gets fxed. I was trying to get it running on a OP3 (msm 8996) and it did not boot either. Expect to have it fixed soon.
[Android Software/Hacking General [Developers Only]] SRIHARI_GUY:
;) I have leaved the Device info there . Hope we both complete our port as soon as the bug gets fixed
[Android Software/Hacking General [Developers Only]] ztotherad:
I'd love to see this implemented on the Nexus 6! I may have to try to port this over this week or next weekend. Great work, dev!
[Android Software/Hacking General [Developers Only]] nihad15:
So, is there actually a version for hammerhead? There is a 2016 file on androidfilehost, not sure if it was uploaded by you tho
[Android Software/Hacking General [Developers Only]] Nintonito:
Trying efi on my OPO, using Lineage 14.1 as the second rom. TWRP installed fine but lineage seems to never finish booting.
[Android Software/Hacking General [Developers Only]] Anghirrim:
First time I installed Lineage OS it took ages to start, even without efidroid nor multirom
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Is there any way to flash an unofficial port without fastboot. As in flash it using twrp?

Both lk IMG and uefi IMG
[Android Software/Hacking General [Developers Only]] Joooscha:
Will this be ported to the OP3?
[Android Software/Hacking General [Developers Only]] Neuken69:
installed this on my verizon note 4 have an error ... cant load device info.please check your connection no value for samsung/gracelte and i cant change it to trltevzw
[Android Software/Hacking General [Developers Only]] abraha2d:
[MENTION=8135471]Neuken69[/MENTION], the Note 4 is not an officially supported device. Please keep Note 4 support questions to the Note 4 thread located here, so that this thread is not overwhelmed. Thank you!
[Android Software/Hacking General [Developers Only]] Neuken69:
[MENTION=7473369]abraha2d[/MENTION] it was actually YOUR thread i got into this app
[Android Software/Hacking General [Developers Only]] abraha2d:
Yup, because I've ported it to the Note 4. However, my thread clearly states that it's unofficial. That's why I asked you to post on that thread, instead of this one, to prevent this one from being clogged. Less work for [MENTION=313770]m1cha[/MENTION] to do.

If you can post your problem on my thread over in the Note 4 forums, then we can resolve this problem there. :good:
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Can someone tell me a way to flash an unofficial build without using fastboot.

I'm trying to test it so we can make it official but currently don't have access to any PC. [MENTION=3530648]m11kkaa[/MENTION]
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Can u explain please? Semi noob here
[Android Software/Hacking General [Developers Only]] mojoswagger1980:
all aokp/aosp Roms seem to take 4eva to install compared to the much larger touchwiz based Roms....I was wondering why? the boot seems extended too and doesn't seem to be affected by any of the standard tricks to speed up the process like speeding up the animation..
[Android Software/Hacking General [Developers Only]] nthacks:
I'm getting an error when trying to enter recovery of 2nd ROM for installing the zip.

"Cannot allocate ramdisk memory for boot."

I set selinux to permissive in uefi settings too.

Using bacon.
[Android Software/Hacking General [Developers Only]] m11kkaa:
where do you see this message? it doesn't look like a efidroid error message - at least I can't find it anywhere.
[Android Software/Hacking General [Developers Only]] abraha2d:
You could flash uefi_boot.img to the boot partition via TWRP. Transfer uefi_boot.img to your phone, then boot into TWRP, press "Install", then at the bottom, press "Install Image". Navigate to where you've stored uefi_boot.img. Select it, select the boot partition, and swipe to flash.
[Android Software/Hacking General [Developers Only]] nthacks:
In the same text box that says "booting into..."
[Android Software/Hacking General [Developers Only]] XeniX_Force:
And what about lk.img?
[Android Software/Hacking General [Developers Only]] abraha2d:
Works for that, too...
[Android Software/Hacking General [Developers Only]] XeniX_Force:
So I first flash lk.img on boot then uefi? Aren't they both supposed to reside at the same time?

By flashing uefi on boot after lk will override lk
[Android Software/Hacking General [Developers Only]] abraha2d:
UEFI replaces LK. Once you've built UEFI successfully, there's no more need for LK.
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Oh

Didn't know that. So I first flash the lkimg on boot, reboot then flash uefi IMG?

Please excuse my confusion. I just don't have a working PC right now
[Android Software/Hacking General [Developers Only]] abraha2d:
Wait, so someone has already built EFIDroid, and you just want to test it? Then all you have to do is flash uefi_boot.img to the boot partition...

Make sure you've backed up your boot partition, so you can restore it in TWRP if something goes wrong...

But, if you don't have a PC available, I don't see how you're going to test EFIdroid... Once you flash uefi_boot.img, you're going to have to connect to a computer, and do some fastboot commands to flash the proper boot.img... Otherwise, EFIDroid will boot, but it won't be able to boot anything, as the boot partition has already been overwritten...
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Yes that's the confusion. I can flash it but it won't boot up coz something is missing.

Can you tell what commands they are and of they can be sent from one Android to another by any way
[Android Software/Hacking General [Developers Only]] abraha2d:
Which device is this? I doubt that the fastboot commands can be sent from one Android to another...

Your best bet would be to flash the boot.img from whatever ROM you're running to get back to a working state, and then test EFIDroid when you have a computer available.

There might be a way to get this to work without a computer, but it's slightly convoluted, I don't know if it will work, and it's probably too long to walk you through here. If you join the Slack community, I can probably help you there.

http://join-efidroid.rhcloud.com/
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Its g4

And let me see. ill join it.
[Android Software/Hacking General [Developers Only]] Neuken69:
PLEASE someone tell me how to uninstall this
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Flash back your original boot image
[Android Software/Hacking General [Developers Only]] m11kkaa:
you can just hit the uninstall button in the app.
[Android Software/Hacking General [Developers Only]] crazykc:
Today I tried to use Omni ROM with EFIDROID, Its is not showing any Network even after changing different Basebands. I had the same problem When I tried Hydrogen OS in EFIdroid. Other than that Everything is working good in my Oneplus one. Even the mighty Color Os is working great with other Lineage based Roms.
[Android Software/Hacking General [Developers Only]] Kawalpreet Juneja:
Hello developer.

I'm so glad that [MENTION=7473369]abraha2d[/MENTION] had ported EFIDroid for Galaxy Note4. I've been using it since 5 days now.

A request from my side please:

Please add option to change name and icon of primary ROM.

Thank you so much for your work. It's really wonderful. UI is amazing.
[Android Software/Hacking General [Developers Only]] MBariya:
Is it possible to share every app data between multiroms??

Dual boot patcher does that job and its very useful. I am missing that feature..

But i liked this EFIdroid concepts.. No extra patching/flushing...Simple and easy.
[Android Software/Hacking General [Developers Only]] m11kkaa:
I've created an issue on github for that: https://github.com/efidroid/projectmanagement/issues/99

I'm currently working on architectural issues so features have to wait a little.
[Android Software/Hacking General [Developers Only]] m11kkaa:
https://github.com/efidroid/projectmanagement/issues/100

How exactly does this work? will the whole data partition be shared or just app data?

in case of app data: wouldn't there be conflicting user id's?
[Android Software/Hacking General [Developers Only]] MBariya:
Individuals app data are being shared. And not conflicting with user id's. It uses shared ramdisk for data sharing. I don't have that much deep knowledge how it works. But sharing link for source of dual boot patcher.

https://github.com/chenxiaolong/DualBootPatcher

Thanks for quick response...
[Android Software/Hacking General [Developers Only]] dedraks:
Hi.

Here is the output:

Sorry for posting again.

carlos@carlos-HP-Pavilion-11-x360-PC:~/android/uefidroid$ fastboot oem findbootimages
...
(bootloader) found ELF32 image on sbl1
(bootloader)	Entry: 0x08008080
(bootloader) found ELF32 image on rpm
(bootloader)	Entry: 0x00000009
(bootloader) found ELF64 image on tz
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF64 image on devcfg
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF32 image on aboot
(bootloader)	Entry: 0x8f600000
(bootloader) found ELF32 image on cmnlib
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on cmnlib64
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF32 image on keymaster
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on prov
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on rpmbak
(bootloader)	Entry: 0x00000009
(bootloader) found ELF64 image on tzbak
(bootloader)	Entry: 0x0000000086500000
(bootloader) found ELF64 image on devcfgbak
(bootloader)	Entry: 0x00000000866e6000
(bootloader) found ELF32 image on abootbak
(bootloader)	Entry: 0x8f600000
(bootloader) found ELF32 image on cmnlibbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF64 image on cmnlib64bak
(bootloader)	Entry: 0x0000000000000000
(bootloader) found ELF32 image on keymasterbak
(bootloader)	Entry: 0x00000000
(bootloader) found ELF32 image on provbak
(bootloader)	Entry: 0x00000000
(bootloader) found QCOM MBN image on modemst1
(bootloader)	ID:16(ramfs1) version:3
(bootloader)	Image: src:000001d8 dst:890198c0 sz:0017fe00
(bootloader)	Signature: src:891996c0 sz:00000000
(bootloader)	CERT chain: src:891996c0 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found QCOM MBN image on modemst2
(bootloader)	ID:17(ramfs2) version:3
(bootloader)	Image: src:000001d8 dst:e1600200 sz:0017fe00
(bootloader)	Signature: src:e1780000 sz:00000000
(bootloader)	CERT chain: src:e1780000 sz:00000000
(bootloader)	code size: 0017fe00
(bootloader) found ELF32 image on metadata
(bootloader)	Entry: 0x02fb5fdf
(bootloader) found Android image on boot
(bootloader)	Kernel: addr:80008000 sz:008b6e28
(bootloader)	Ramdisk: addr:81000000 sz:001a29f4
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:0004d096
(bootloader)	pagesize:2048
(bootloader) found Android image on recovery
(bootloader)	Kernel: addr:80008000 sz:0087cce0
(bootloader)	Ramdisk: addr:81000000 sz:003a2a87
(bootloader)	Second: addr:80f00000 sz:00000000
(bootloader)	Tags Addr:80000100, DTB sz:00190800
(bootloader)	pagesize:2048
OKAY [ 0.608s]
finished. total time: 0.608s
[Android Software/Hacking General [Developers Only]] d3multimedia:
I have been using an unofficial port for the Note 4 and it is working wonderfully. There's a few things that in reading the forum and through experiance that I feel is a little finicky.

1.) Primary OS naming. Wouldn't a custom build.prop entry fix that ie EFIDroidName.

2.) selinux permissive toggle placed under individuals ROMs instead of toggled across the board. A line in the multiboot.ini possibly.

3.) A timeout to boot ROM automatically.
[Android Software/Hacking General [Developers Only]] m11kkaa:
1.) we don't modify ROM's for efidroid. but it should be no problem to add support for externally configuring the internal ROM just like the multiboot ROM's

2.) you can already do that by setting a cmdline override. Either way. the whole thing is a workaround and should/will be fixed.

3.) Somebody is working on that: https://github.com/efidroid/projectmanagement/issues/57
[Android Software/Hacking General [Developers Only]] d3multimedia:
Thanks for the response. I actually noticed on github that the timeout was in progress. How would one setup the command line for permissive?
[Android Software/Hacking General [Developers Only]] m11kkaa:
in the slot settings, add a cmdline override:

name: androidboot.selinux

value: permissive

you can even change the serial number or security flags that way :D
[Android Software/Hacking General [Developers Only]] d3multimedia:
I've been on XDA for 4 years and haven't been this exited to want to participate this much.

Is there anywhere that shows the cmdline override options available to be used.

Correct me if I'm wrong but as I understand it the interface's "framework" is based off of twrp. As such is there any way to modify the theme such as blanking out the menus when it goes to boot a ROM, changing colors or graphics.

Is a touch interface in the works?

I have to say this is much more powerful and customizable than I previously thought.
[Android Software/Hacking General [Developers Only]] m11kkaa:
Thank you for your interest :)

- There's no list of available cmdline options because that depends on the kernel and ROM used.

- EFIDroid is a bootloader, no kernel/OS/framework is being loaded - the UI gets rendered directly to the framebuffer using libaroma.

There's no theme engine but allowing to change colors would be a possible feature.

- Touch would be very complicated and would need a lot of work for every single device - and there are no plans for it
[Android Software/Hacking General [Developers Only]] afaneh92:
mohammad@mohammad:~/efi$ finalize_device device/samsung/kltevzw
Error: [Errno 2] No such file or directory
Traceback (most recent call last):
File "/home/mohammad/efi/build/tools/finalize_device", line 139, in <module>
runmain(main)
File "/home/mohammad/efi/build/tools/../core/utils.py", line 91, in runmain
sys.exit(main(sys.argv[1:]))
File "/home/mohammad/efi/build/tools/finalize_device", line 62, in main
p = subprocess.Popen(['fastboot', 'oem', 'findbootimages'], stderr=subprocess.PIPE)
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

Any idea what going on?
[Android Software/Hacking General [Developers Only]] m11kkaa:
Sounds like you don't have fastboot installed or it's not in your PATH.
[Android Software/Hacking General [Developers Only]] afaneh92:
Thanks its working.

I will add official support after testing all thing.
[Android Software/Hacking General [Developers Only]] evilracer123:
[MENTION=3530648]m11kkaa[/MENTION] Would you kindly check out my pull request for Yotaphone 2 support? :)

https://github.com/efidroid/device/pull/11

Efidroid is a great project, but setting up the server for installing the app is a massive PITA.
[Android Software/Hacking General [Developers Only]] 1freedude:
First, thanks for your work.

Now, how can we compensate for different versions of bootloaders? On my device, T-mobile Galaxy Note 4, LP bootloaders break MM custom firmware, and vice versa.

EFIdroid is (now) only beneficial to me if I can boot two different BL versions. Is it really possible?
[Android Software/Hacking General [Developers Only]] m11kkaa:
you got a comment on github :)

on 1p1 I've done exactly that. It's generally possible if there is a way to make the same boot image boot on both bootloaders. Once UEFI is up and running it's just a matter of finding all information needed to boot all kinds of ROM's(made for the differnet bootloader versions).
[Android Software/Hacking General [Developers Only]] shanx_verma:
Heyy [MENTION=7189826]SMYM[/MENTION], I just came across this, and while [MENTION=5890172]Rishabh Rao[/MENTION] is working on MultiROM, maybe you can try and port this for our Snapdragon device #Kenzo! :)

It'd be a completely different miraculous story if we can boot up GRUB with the help of this, and subsequently things like ubuntu might become easier to port later! :)
[Android Software/Hacking General [Developers Only]] m11kkaa:
GRUB is easy to boot. took like 5min to port and actually can be compiled using the uefi build system after inlcuding the optional manifest :)

keep in min dt hat GRUB's loader may not be feature-complete "enough" for qcom's android kernels so it may make more sense to add some more linuxy kernel booting methods to the EFIDroidUi.
[Android Software/Hacking General [Developers Only]] shanx_verma:
I'm not a dev actually, was just pointing out this wonderful creation of yours to my device's big developers.

Thank You So Much for this wonder, though!!

Ist ja doch wunderbar!! :)
[Android Software/Hacking General [Developers Only]] symbuzzer:
cant mount created 2nd roms data and cache partitions on Nokia X2? any help?

edit: I use "format data" option o twrp and enable to mount data, but couldnt for cache

edit2: I use twrp and make ext4 these 2 partitions and finally I can mount them. can you fix this issue for Nokia X2 which is officially supported phone by efidroid project?

edit3: founded bugs for nokia x2:

- users must make ext4; system, data, cache partitions manually.

- no need to firmware for each roms. users must copy firmware.img manually for using data and wifi.