Build instructions for Fairphone 3 FP3?

[andrelam]

Since the Fairphone build is a GSI, are there instructions how to build it? I flashed
IMG-e-0.9-p-2020051454091-dev-FP3.zip but like to make some edits. This is verified boot so i can’t just flash a new system.img if i am correct? Any instructions about that, how would i make a verified system image?

Edit:I’m going to make an issue on Gitlab, think its better to ask there.

Edit2: The build is NOT a GSI, i misunderstood.

[someguy]

Hi @andrelam!

The build instructions @Manoj always refers to, are available at:
https://doc.e.foundation/how-tos/build-e

That said, I haven’t been able to successfully build an image for FP3 yet.

I’d attempted to follow the instructions a few weeks (before IMG-e-0.9-p-2020051454091-dev-FP3), using Debian testing (bullseye) and Debian-provided Docker. Having set:

BRANCH_NAME=v1-pie

and

DEVICE_LIST=FP3

and

OTA_URL=https://some.fake.url.local/

did not yield success (nor an image). If I remember correctly, a device-specific Git repo couldn’t be cloned.

As soon as I have some more diskspace, I intend to try again.

[andrelam]

@someguy

That said, I haven’t been able to successfully build an image for FP3 yet.

Normally the vendor files are downloaded from TheMuppets, and kernel and device tree from LineageOS. Since FP3 is not supported by LineageOS yet (i think this will come soon using /e/ sources) the normal way of building would fail.

The good news is, /e/ has sources/ manifest here. The bad news is one repository is private, e/devices/android_vendor_fairphone_FP3

Now more good news I extracted the vendor blobs from the official build, and i’m running a build. The first attempt failed at 81%, i did something wrong and hope the new build does succeed. @manoj do you know why the vendor blobs are private repo?

[andrelam]

Ok the build finished successful. So this is my current situation:

• I have flashed /e/ IMG-e-0.9-p-2020051454091-dev-FP3
• Relocked boot loader

I have these files from my build:

• boot.img
• dtbo.img
• dtbo-pre.img
• product.img
• ramdisk.img
• ramdisk-recovery.img
• system.img
• userdata.img
• vbmeta.img
• vendor.img

The /e/ instruction instructs to flash these files:

• fastboot -w

• fastboot flash system system.img

• fastboot flash boot boot.img

• fastboot flash vendor vendor.img

• fastboot flash dtbo dtbo.img

• fastboot flash product product.img

• fastboot flash vbmeta vbmeta.img

• fastboot flashing lock

I used the manifest from /e/

@sooorajjj

1. What do I have to flash? Just do all the steps again as instructed by /e/, or could I just flash system.img only?
2. I must unlock before flashing? (think so otherwise it would have no use)
3. Can I lock boot loader again with the self build image?

[sooorajjj]

Please flash official e/ OS build , now using adb extract the blobs
there are two scripts in device tree which you need run after connecting the device
device/fairphone/FP3/setup-makefiles.sh
device/fairphone/FP3/extract-files.sh

[sooorajjj]

1. What do I have to flash? Just do all the steps again as instructed by /e/, or could I just flash system.img only?
   => Yes just run same steps to flash /e/
2. I must unlock before flashing? (think so otherwise it would have no use)
   => If you are already on e/ OS then No
3. Can I lock bootloader again with the self build image?
   => Yes

[andrelam]

Yes i used official /e/ sources, also vendor, thanks!

[andrelam]

It works… I did have to unlock again, because I could not flash!

After unlocking everything went well, and the build runs:

Now I’m scared to do the lock thing, could I lock myself out? I think I’ll leave it unlocked so I can do some building, and testing :).