pocophone f1 porting

[manuel-baum]

i have a problem with porting pocophone because theres no target for sdm845 if someone know how i can fix it plese say me

[manuel-baum]

also the main.mk fails because theres an problem in line 42 with @start_time (date + ....

[feherneoh]

Sorry to disappoint you, but probably the only way of "fixing" it is taking over maintenance of the whole project. Those "targets" you see are LK targets to use for OLD builds, and sdm845 should NOT have LK available according to what I know about it. It should be running UEFI out-of-the-box, so what you would need isn't the platform itself, but the tools running on top of it.

[feherneoh]

Also main.mk works just fine on my side, so you are probably missing some steps before invoking make

[manuel-baum]

OK thanks for the fast awnser but i can't do anything wich is so complicated

[TAOcroatia]

Sorry to disappoint you, but probably the only way of "fixing" it is taking over maintenance of the whole project. Those "targets" you see are LK targets to use for OLD builds, and sdm845 should NOT have LK available according to what I know about it. It should be running UEFI out-of-the-box, so what you would need isn't the platform itself, but the tools running on top of it.

@feherneoh
Could you elaborate on the "tools running on top of it" part? Is there any simple way to boot .efi files?

[feherneoh]

About a way of running .efi files... No idea. I don't have any Android phone that uses XBL.

tools running on top of it
GUI, ramdisk patcher, filesystem drivers, and stuff like that

[M1cha]

well there are a few theoretical and untested ways to run efi files with qcom's stock uefi:

• you find a security bug
• you replace abl which is an UEFI FV containing the BDS app(I dunno if the FV itself is signed, if EFI's need to be signed in general or if it'a all unprotected)
• you find a way to undo ExitBootServices()
• you find a way to reload the (modified) DXE-phase of UEFI without any side effects.

[feherneoh]

The FV itself is most probably NOT signed, but I'm positive it's in a signed container
The last one sounds like the "easiest" method

[luka177]

well there are a few theoretical and untested ways to run efi files with qcom's stock uefi:

* you find a security bug

Well mb mb, but i dont think so

* you replace abl which is an UEFI FV containing the BDS app(I dunno if the FV itself is signed, if EFI's need to be signed in general or if it'a all unprotected)

It is possible only on unfused devices (publicly available unfused devices are: Fxtec pro1/x, Shiftphone, Did i forgot anything? )

* you find a way to undo ExitBootServices()

Dont think its possible, but who knows

* you find a way to reload the (modified) DXE-phase of UEFI without any side effects.

Already done https://github.com/edk2-porting/edk2-msm

[M1cha]

@luka177 thanks for telling me about renegrade. Looks like they managed to do everything that I weren't able to - including porting windows.

[luka177]

Well they are focused on windows, not dualboot:D and uefi drivers are proprietary