Unlocked warning on startup - recent installation

I helped a friend install EOS on a new FP6 today through ADB and can’t lose the ‘Unlocked’ warning message.

It was pretty straightforward, the ‘phone booting to EOS at the end of the installation. However, an ‘unlocked’ warning came up to I went back into ADB and did the critical lock command. The warning still showed up so I checked the lock/unlocked setting in Developer Options and it’s locked. I went back into ADB to re-issue the critical lock command figuring I’d hit the wrong vol up/vol down button but it failed with the error, ‘already locked’.

It’s not a deal breaker, the phone works perfectly but the error message persists.

Any thoughts?

You did not overlook that the locking process is two stage Install /e/OS on a Fairphone - The Fairphone (Gen. 6/Gen. 6+) - "FP6" | /e/OS documentation

  • lock critical then
  • lock the device

But you had fully ruled out anti-rollback before attempting to lock?

I thought I had followed all the steps but clearly I did something wrong.

  • Locked critical
  • Went to lock the device but it was already locked

I will probably

  • unlock the device again,
  • then unlock critical,
  • then boot to boot loader
  • then relock critical,
  • then boot the device
  • Then relock the device.
  • Then reboot…

Pfff. Or just leave it unlocked !

Yes, I checked the security patch dates and they’re fine.

“adb” is not so usefull to install /e/ on a FP6 but “fastboot”..
What about :

1 Like