[Solved] Problem to unlock device via fastboot on FP4

Help Fairphone 4
42

I agree, none of the OTA updates lock / unlock critical partitions.

Calyx for example uses the OTA update mechanism in fastbootd (fastboot in userspace) to flash some of the partitions during installation, critical partitions are still unlocked on my phone.
And the recent Fairphone OTA didn’t lock critical partitions on the other device I have access to either.

So for @Volker locked stays locked and for me unlocked stays unlocked, I’d say case closed :smirk:

Edit: I just stumbled upon this bit of information in the Android docs:

OTAs should fail to update critical sections if the device is in lock critical state.

So this…

…might actually not be the case? :thinking:

2 Likes
43

The bootloader of my device is unlocked, but critical partitions aren’t. So I can tell you after next OTA if it works…

1 Like
44

Maybe this depends on the OTA as well, I’m not even sure OTA updates generally should touch critical partitions?
According to the docs:

devices shouldn’t ship in the unlock critical state

So if critical partitions are locked from the factory and OTA updates shouldn’t update them, are they even supposed to be changed apart from flashing factory images?

Would be nice to know which of the partitions are critical partitions, the normal system partitions mentioned in the docs probably aren’t and the part about critical partitions doesn’t offer much more information :thinking:
Probably anything that’s loaded before the system is booted. If we use this (old) blog post as a reference, that would mean abl, xbl & Co.

45

xbl_config_a
devcfg_a
xbl_a
tz_a
hyp_a
keymaster_a
abl_a
aop_a
imagefv_a
multiimgoem_a
qupfw_a
uefisecapp_a

and the same on slot b obviously.

2 Likes
46

I’ve just done an OTA update and as expected it worked perfectly (with critical partitions locked). :slight_smile:

1 Like
47

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.