yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] SMYM:
I've tried that,in my idea, that's nearly impossible.

We can completely port sailfish os or such OSs (that have gnu and cm source )to kenzo,but Ubuntu touch is impossible.

Even if we port it to rn3, it will have many sensor bugs,bro....

But sailfish os is going to progress in being ported to other devoces,if you take a look at its source, u can easily find out that it may be compatible with all phones after arm64 architecture.
[Android Software/Hacking General [Developers Only]] m11kkaa:
these aren't bugs. formatting partitions and installing stuff is the job of your favorite recovery tool.

EFIDroid only allocates space and sets up redirections for virtual partitions.
[Android Software/Hacking General [Developers Only]] symbuzzer:
Thanks for your reply. I understand. But redirecting modem (firmware) partition causes Radio(wifi, bluetooth etc) and RIL problems. (I use right firmware (modem) image sure) Is there any way for disable this except compiling efidroid?
[Android Software/Hacking General [Developers Only]] shanx_verma:
I do understand there are complications involved in making ubuntu work for us, but maybe you misunderstood me.

I wasn't requesting you to work on Ubuntu.

I am requesting you to try and port EFI Droid for Kenzo.

.

There are a lot of other things this kind of a boot setup could achieve, well...

Like running a lot of new stuff requiring the support of a uefi bootstage environment.

#windows98 #windowsXp etc etc etc, even if just for fun (I doubt xp contains any support for phones / calling etc. Lol)

I know all this might sound as mere postulates,, but anything - and I repeat - anything,, will only be possible only after porting this wonder to our device.

That's something you can easily do, I believe.

The rest and really harder parts can be handled by more seasoned developers. :)

Cheers!!! :angel:
[Android Software/Hacking General [Developers Only]] m11kkaa:
for the internal ROM or for multiboot ROM's?

disabling the redirection is not a solution - I guess that your only problem is selinux and that it would work in permissive mode.
[Android Software/Hacking General [Developers Only]] symbuzzer:
Only for multiboot roms. I already enabled force permissive mode for selinux from efidroid.

I am developer of MultiBootloader for Nokia X2. I already saw this problem before.
[Android Software/Hacking General [Developers Only]] m11kkaa:
you should check for the exact problem then, because the firmware is just another partition containing a filesystem and not(or should not be) something that's used by low level bootloaders.
[Android Software/Hacking General [Developers Only]] symbuzzer:
so anyway to disable it?
[Android Software/Hacking General [Developers Only]] m11kkaa:
only by compiling - you have to exclude the firmware partition from multibooting in the fstab.
[Android Software/Hacking General [Developers Only]] symbuzzer:
:( Can you add enable/disable necessary partitions option to EFIDroid Manager for future updates?
[Android Software/Hacking General [Developers Only]] m11kkaa:
maybe, but as I said, this wouldn't not be a solution and redirecting the fw partition must be fixed. a logcat would be a good first step.
[Android Software/Hacking General [Developers Only]] Camlin3:
Sir,

Can you extend support for other snapdragon devices too ?

Mine one is kenzo,sd650
[Android Software/Hacking General [Developers Only]] 7root:
If he had your phone, sure. He has to own the phone to port it. Easiest solution would be that you port it yourself
[Android Software/Hacking General [Developers Only]] Joooscha:
Is it easy to Port this app? Could you give me a hint how to start?
[Android Software/Hacking General [Developers Only]] 7root:
Well, step 1 is to use Linux, either as your OS or as a virtual machine. It's pretty easy if you have some experience with the Linux terminal, git and rom building. There's a great tutorial on EFIDroids GitHub page: https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device

In case you don't run a Linux System on your Computer, use oracles open source VM manager called "VirtualBox".

I recommend using Ubuntu 14.04.

To set up your build environment to get started porting/building/developing, google provided an excellent tutorial here: https://source.android.com/source/initializing.html

Good luck
[Android Software/Hacking General [Developers Only]] 7root:
Using a VM is the easiest solution
[Android Software/Hacking General [Developers Only]] Joooscha:
Ok, I am now on the right track I think, but I stuck at make -j1 lk (do you know what I mean?) It works everything well untill this. I am always getting the error:### make failed to build some targets### and then make: *** [ok] Error 2. Didn't find anything on Google, can you help me? I am really new to this, sorry. PS: I try to Port to a OnePlus 3
[Android Software/Hacking General [Developers Only]] Joooscha:
Sorry, I don't know which one you need?:confused:
[Android Software/Hacking General [Developers Only]] Joooscha:
(Deleted) Installed libz-dev
[Android Software/Hacking General [Developers Only]] Joooscha:
Ok last question I think then I'll have it: everything worked and I have the lk.img but nothing happens when I flash it. If I boot to bootloader everything is normal. Finelize_device does exactly nothing than showing the curser for ever
[Android Software/Hacking General [Developers Only]] 7root:
What's your device? Some 64 bit devices have problems with lk.img see GitHub: https://github.com/efidroid/projectmanagement/issues/89

But somewhere in the middle M1cha posted a workaround. Try it, maybe it works for you. Good luck!
[Android Software/Hacking General [Developers Only]] Joooscha:
I have an OnePlus 3. Thank you very much, but I can't find a solution. I might have to wait for a 64 bit version?
[Android Software/Hacking General [Developers Only]] 7root:
OnePlus 3 here as well, same annoying problem. I suggest you to join the slack group and catch up with the news there. This problem will eventually get fixed, I am sure.
[Android Software/Hacking General [Developers Only]] Joooscha:
Any news about 64bit device compatibility?
[Android Software/Hacking General [Developers Only]] 7root:
Asked on Slack group, according to M1cha, a new UEFI version comes out soon. That update should make it easier to fix this issue. I strongly suggest to join the Slack group to catch up with the news
[Android Software/Hacking General [Developers Only]] 0lvin:
Hang on boot jag3gds

I have created lk image and it indeed works. i can boot from lk my boot image from lineage-14.1.

But when i have tried to boot uefi.imag from lk, device only hangs.

Repository with settings for device.

How i can debug it or receive some additional information about what is wrong with my uefi img?
[Android Software/Hacking General [Developers Only]] 7root:
What device? Some devices with a 64-bit system don't really like LK.img or UEFI.img. See GitHub or Slack for more info
[Android Software/Hacking General [Developers Only]] 0lvin:
I have tried on LG G3s : Quad-core 1.2 GHz Cortex-A7 (32bit). Lk is booted without any problems, i have issues only with uefi image.
[Android Software/Hacking General [Developers Only]] 7root:
Join the Slack group and ask M1cha
[Android Software/Hacking General [Developers Only]] abraha2d:
Do you have anything in the Override OTA Server field? It should be blank. Try clearing the data of the EFIDroid Manager app.

Also, make sure your build.prop is set to trlte, so that the EFIDroid Manager app can identify it as a Note 4...
[Android Software/Hacking General [Developers Only]] abraha2d:
Yes, EFIDroid Manager relies on the build.prop to identify the device. Change ro.product.device to "trlte", which is the device code for the note 4...
[Android Software/Hacking General [Developers Only]] sub77:
try https://github.com/sub77/bootloader...fa222d9#diff-c4c3ba55f8dab8c4081f8ccd30af060c
[Android Software/Hacking General [Developers Only]] ayeitschris:
Can you add an option that allows the phone to automatically boot into a selected rom after like 60 seconds? So the phone isnt stuck in the bootloader if phone randomly reboots.

Edit: oh nevermind, searched the the thread and its being worked on. thanks.
[Android Software/Hacking General [Developers Only]] MetalmanIX:
Damn what am I missing? I ve installed the app and created an entry for a new ROM I want to install and then rebooted into recovery, but how do I actually flash the new rom?
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Go to twrp, choose the new rom and then install the rom package
[Android Software/Hacking General [Developers Only]] MetalmanIX:
I tried that but how do I install the rom package when I can't access my internall memory from twrp?
[Android Software/Hacking General [Developers Only]] abraha2d:
/multiboot/data/media/0/ is your internal storage, if I'm not mistaken...
[Android Software/Hacking General [Developers Only]] XeniX_Force:
Place your rom zip in /data/media/0/multiboot/*your rom name*/data/ and then you can find it in twrp
[Android Software/Hacking General [Developers Only]] petbede:
[MENTION=3530648]m11kkaa[/MENTION], I need your assistance, what can I do here... My device not coming on and my device cannot be detected by my laptop.

It can boot to downloader mode but Odin and my laptop can not detect it.

Please, what can I do to fix it?
[Android Software/Hacking General [Developers Only]] m11kkaa:
Which device? Are you porting a new one or just installing efidroid?
[Android Software/Hacking General [Developers Only]] petbede:
My device is N910F.
Was installing efidroid on ported rom.

Thanks so very highly much...

I got the phone back from the shop and it been fix.

I thank you so very highly much for your reply, you highly awesomatic :good:
[Android Software/Hacking General [Developers Only]] 0lvin:
Thank you, it helps.
[Android Software/Hacking General [Developers Only]] the-blind-bandit:
???? can't wait for this on the Oneplus 3T
[Android Software/Hacking General [Developers Only]] kewinhw:
I tried to install omnirom, ressurection remix, nitrogen os, jgcaap

Omnirom > bootloop

Nitrogen OS > bootloop

Ressurection > error message

Out of 4 roms only jgcaap works to installning as secondary for me.

I also have checked md5, I always check md5
[Android Software/Hacking General [Developers Only]] steadfasterX:
What's the best way to debug a bootlooping secondary ROM?

.
[Android Software/Hacking General [Developers Only]] MetalmanIX:
I have no luck with Ressurection Remix and CypherOS on OnePlus One.

Both keep giving me bootloops.
[Android Software/Hacking General [Developers Only]] Camlin3:
why did you dropped for kenzo ?

can you start it again? I mean build boot and recovery IMG.
[Android Software/Hacking General [Developers Only]] 0lvin:
Other posible solution for fix boot uefi.

Other solution align size to 1024.

diff --git a/uefiapi/target/msm8226.c b/uefiapi/target/msm8226.c
index 47915ded..aeba3bc6 100644
--- a/uefiapi/target/msm8226.c
+++ b/uefiapi/target/msm8226.c
@@ -6,6 +6,8 @@

#include <uefiapi.h>

+#define ROUNDUP(a, b) (((a) + ((b)-1)) & ~((b)-1))
+
/////////////////////////////////////////////////////////////////////////
// KEYS //
/////////////////////////////////////////////////////////////////////////
@@ -43,7 +45,7 @@ void uefiapi_platform_init_post(void)
void* uefiapi_mmap_add_platform_mappings(void *pdata, lkapi_mmap_add_cb_t cb)
{
// iomap
- pdata = cb(pdata, MSM_IOMAP_BASE, (MSM_IOMAP_END - MSM_IOMAP_BASE), LKAPI_MMAP_RANGEFLAG_RESERVED,
+ pdata = cb(pdata, MSM_IOMAP_BASE, ROUNDUP(MSM_IOMAP_END - MSM_IOMAP_BASE, 1024), LKAPI_MMAP_RANGEFLAG_RESERVED,
LKAPI_MEMORYATTR_DEVICE, 0, LKAPI_MMAP_RANGEFLAG_UNUSED|LKAPI_MMAP_RANGEFLAG_DRAM);

return pdata;
[Android Software/Hacking General [Developers Only]] MetalmanIX:
So practically no ROM works on this app. Tried 4 different ones, every one of them bootloops. Is it even support on OPO?
[Android Software/Hacking General [Developers Only]] steadfasterX:
I have the same issue for the g4 but no idea how to solve it or even troubleshoot those efidroid related bootloops.. I've asked here and on slack but no answer..

.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Many thanks for these useful insights! It's good to know that this is a known issue and that there's someone working on this problem regarding debugging
[Android Software/Hacking General [Developers Only]] Samuelgames:
A build of the Windows 10 Mobile Adaptation Kit has been released on the wild, is there any chance of this can be reviewed given the information provided in the documents?
[Android Software/Hacking General [Developers Only]] m11kkaa:
The problem is that Qualcomm's original drivers for Windows are not compatible with the Linux-targeted firmware(e.g. TrustedZone, GPU, ...) running on our devices and we can't install a different one when the device requires these binaries to be signed by the OEM.

Ofc we could just implement our own Windows drivers based on the Linux firmware and opensource drivers, but then we wouldn't have DirectX support - and implementing DirectX on top of OpenGL would be a lifetime project by itself.

So it's actually possible using the 2nd way(assuming a DirectX layer could logically/mathematically be efficient), but it's just a lot of work.
[Android Software/Hacking General [Developers Only]] r.mutt:
1.) Do I miss something or is Playstore the only source for org.efidroid.efidroidmanager.apk? It would be great to have an alternative source: Github, Androidfilehost .... (Yes, I'm afraid of big data and I think it is a good idea to avoid Playstore.)

2.) Is EfiDroid worth a try on OnePlus One right now or are there still too many bugs? There are damn lot reports about bootloops ;)

3.) [MENTION=3530648]m11kkaa[/MENTION]: EfiDroid is a milestone. Thanks a million for your efforts!
[Android Software/Hacking General [Developers Only]] 7root:
I am patiently waiting for EFIDroid to be finished. The previous versions were buggy and bootloop issues are acknowledged. Currently, EFIDroid is experiencing a full revamp and all the radical changes to the structure should fix issues people are experiencing. For more information, visit the slack channel. As for now, I recommend you to wait until the stable new version is ready, because even compiling it is problematic at the moment.
[Android Software/Hacking General [Developers Only]] m11kkaa:
1) Everything I do is opensource :)

https://github.com/efidroid/android_app_efidroidmanager

That's why the playstore changelog contains commit id's and github links.

2) right now it's not worth porting any device because I'm in the middle of a giant rewrite.

3) Thanks a million for your kind words :)
[Android Software/Hacking General [Developers Only]] addy692:
As u r busy rewriting

There is one suggestion i want to give

I.e if its possible please setup such a system so peaple can create pull request on ur github and u verify that req. And add support for that device

Then it would be easy to add support for further devices
[Android Software/Hacking General [Developers Only]] m11kkaa:
It's been like that since the beginning.

In fact you can't disable pull requests on github :)
[Android Software/Hacking General [Developers Only]] addy692:
Oh sorry

I don't know about that

Actually i once teued to compile this for my device

But didn't succeed thats y :silly:

I said to take pull req.
[Android Software/Hacking General [Developers Only]] oF2pks:
[MENTION=3530648]m11kkaa[/MENTION] ,( I wish I could understand bootloader stuff , but) as a blind user , I noticed Oneplus 5 OOS use edk2

<project name="abl/tianocore/edk2" path="bootable/bootloader/edk2" revision="a80977c37e1b4bd44b39bea8065beca015952bac" upstream="uefi.lnx.1.0.r13-rel"/>
<project name="kernel/lk" path="bootable/bootloader/lk" revision="dd34344f0bad979e6e60df09e2b45cefa82adfaa" upstream="lk.lnx.1.0.r13-rel"/>
-------------------------------------------------------
# Compile
include bootable/bootloader/[B]edk2[/B]/AndroidBoot.mk

$(INSTALLED_BOOTLOADER_MODULE): $(TARGET_EMMC_BOOTLOADER) | $(ACP)
$(transform-prebuilt-to-target)
$(BUILT_TARGET_FILES_PACKAGE): $(INSTALLED_BOOTLOADER_MODULE)

droidcore: $(INSTALLED_BOOTLOADER_MODULE)
endif
-----------------------------------------------------------------
TARGET_BOARD_PLATFORM := msm8998
TARGET_BOOTLOADER_BOARD_NAME := msm8998

TARGET_NO_BOOTLOADER := true
TARGET_USES_UEFI := true
TARGET_NO_KERNEL := false

So, is there an easy way to patch straight EFIDroid to OOS/platform_/bootable/bootloader/edk2 and build directly ?

And how can I "read" https://github.com/efidroid/projectmanagement/wiki/[Reference]-Device-Config-documentation to match https://github.com/efidroid/build/blob/master/tools/finalize_device

Thx for any clue
[Android Software/Hacking General [Developers Only]] m11kkaa:
Can you give me a link to that OnePlus repo?
[Android Software/Hacking General [Developers Only]] oF2pks:
https://github.com/OnePlusOSS/android/tree/oneplus/QC8998_N_7.1?files=1

I have it on my old laptop....

EDIT:

-when I check OP5 4.5.5.zip in /firmware there is logo.bin & abl.elf "auto motive bootloader" ? (like s8) and no emmc_appsboot.mbn (like OP3T)

-bootable/edk2/makefile ... LOAD_ADDRESS := 0X9FA00000

- https://gitlab.com/Codeaurora/abl_tianocore_edk2/commit/fedf9ac6a42f37e8417eb5a7bc58051d8c4920a1
[Android Software/Hacking General [Developers Only]] m11kkaa:
While it's possible that your device uses edk2(can you send me a system dump with aboot/uefi partitions?), that edk2 repo only contains the loader application, the whole platform part is closed source.
[Android Software/Hacking General [Developers Only]] oF2pks:
I already have the full OOS repo synced on my laptop (included /edk2 and all OP5 vendor): I made one rom build but stucks on 'android' silver bootlogo; I will make another one (user-debug) soon (with ? https://xdaforums.com/showpost.php?p=72804704&postcount=66).

Concerning the dump: these are the things I really don't understand, but I'm pretty sure [MENTION=6584600]xdvs23[/MENTION] has all these stuff (ready to go). If doesn't have this dump , I will try to get that by next week-end.

That also lead me to further interrogation : are they any intersection between EFIDroid (finalize_device) and rescue tools to unbrick Qualcomm devices based on rawprogram0.xml ?

https://xdaforums.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201

Thx for helping.

Attached rawprogramm0 is from YU device
[Android Software/Hacking General [Developers Only]] m11kkaa:
finalize_device is a just a tool utilizing efidroid-lk's fastboot to find a proper loading addr for UEFI and LK.

It's actually been deleted in the rewritten efidroid.
[Android Software/Hacking General [Developers Only]] xdvs23:
I actually worked with EFIDroid already but I'm not really familiar with it in depth.
[Android Software/Hacking General [Developers Only]] m11kkaa:
so can you upload some bootloader dumps from this device so I can analyze them in-depth?
[Android Software/Hacking General [Developers Only]] xdvs23:
I don't have an OP5, yet. Just OP2.
[Android Software/Hacking General [Developers Only]] m11kkaa:
I saw that 1+1 offers full firmware downloads.

And indeed - they ditched LK and are using UEFI now.

And after some research I found this:

https://www.inforcecomputing.com/inforce-qualcomm-secure-boot-prevents-malicious-software

Now I have to figure out how to get my hands on an 8998 or 8996(are there cheap ones?)
[Android Software/Hacking General [Developers Only]] m11kkaa:
as I said I have everything I need already, because you can officially download these dumps from the oneplus website.

what I found out so far:

- abl = android bootloader, which is an UEFI FV which contains the opensource linux loader application

- xbl = eXtensible Boot Loader, this contains a huge ELF binary with XBL, tons of configs and the main UEFI FV

I only said that I need a device with such a soc so I can do tests and maybe make efidroid work on their existing uefi implementation.
[Android Software/Hacking General [Developers Only]] oF2pks:
(ok, logo.bin seems new too; ) I heard somewhere, you can find OP5 for 400$ due to ScreenJellyEffect returns.

What about rawprogram0.xml, is it useless or can it help setting EFIDroid address before compilation ?

Good luck
[Android Software/Hacking General [Developers Only]] m11kkaa:
The problem is that it looks like they don't allow you to boot EFI files, which means I'd basically have to sideload a modified stock-uefi anyway.

And at that point I'd actually prefer the opensource alternative.
[Android Software/Hacking General [Developers Only]] FunkyRasta:
I've been using EFIdroid on my bacon for sometime but I had to stop. Random reboot during night makes mu stuck in boot menu and miss alarms... I've searched the thread a little but didn't come to any conclusions. Is autoboot to previously used ROM or a chosen one after timeout being planned/worked on ? I would love to go back to using EFIDroid instead of shuffling nandroid backups! ;)
[Android Software/Hacking General [Developers Only]] abraha2d:
Possibly after the rewrite... I was working on this feature for the current EFIDroid, but it would be pretty pointless to continue working on it, as v2 is on the horizon...
[Android Software/Hacking General [Developers Only]] tomgaga:
Hi,

I'm using this on my yotaphone2, it's really cool!

But i was wondering if there is a way to share the data partition between 2 systems. I would like to have 1 rooted and 1 unrooted system but using the same data partition....
[Android Software/Hacking General [Developers Only]] m11kkaa:
wouldn't a UEFI boot plugin which dynamically enables/disables root(or magisk) more space efficient? :)
[Android Software/Hacking General [Developers Only]] tomgaga:
Yes I'm using that, but it's actually also xposed that I would then install in the rooted one. (Systemless xposed does not work for me)

But so would it not be possible to let 2 os's link to the same data partition?
[Android Software/Hacking General [Developers Only]] tomgaga:
Interesting! How would you go about it?
[Android Software/Hacking General [Developers Only]] Chetan Lodha:
i have been syncing efi droid sources since the last few hours......can anyone tell me whats the approx size of completely synced sources?
[Android Software/Hacking General [Developers Only]] 7root:
25GB I think. Correct me if I'm wrong
[Android Software/Hacking General [Developers Only]] m11kkaa:
Every device supports encryption - if you don't have a partition for the key you can still store it in the filesystem footer - it's all supported by Google.

The next version of efidroid comes with touchscreen support though ;)
[Android Software/Hacking General [Developers Only]] LPW00:
Edit: seems like this issue is known, there's a workaround to get it boot.
[Android Software/Hacking General [Developers Only]] timo_capa:
Windows 10 for ARM64 builds start to pop up. I wonder... :p
[Android Software/Hacking General [Developers Only]] steadfasterX:
in theory.. maybe. but in practice? better forget it.

Checkout this from the main OP: https://xdaforums.com/showpost.php?p=72784493&postcount=320

sfX
[Android Software/Hacking General [Developers Only]] ShadowEO:
I know this has been idle for a little while, but I managed to get EFIDroid up and running on the Nexus 7 (2013).

OTA package is at https://github.com/ShadowEO/efidroid_ota_asus_flo

It can be built with the following config.ini:

[variables]
DEVICE_NAME = Nexus 7 2013
LK_TARGET = msm8960
LK_BASE = 0x0000000088f00000
LK_SOURCE = qcom/LA.BF64
BOOTIMG_BASE = 0x80200000
BOOTIMG_PAGESIZE = 2048
BOOTIMG_ADDITIONAL_ARGS = --ramdisk_offset 0x02000000
LCD_DENSITY = 230
EDK2_BASE = 0x00000000fe000000
EDK2_SIZE = 0x0000000002000000

and the following fstab.multiboot

/dev/block/platform/msm_sdcc.1/by-name/system /system auto defaults multiboot
/dev/block/platform/msm_sdcc.1/by-name/cache /cache auto defaults multiboot
/dev/block/platform/msm_sdcc.1/by-name/userdata /data auto defaults multiboot,esp=datamedia
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults multiboot,uefi,nvvars
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults uefi