Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Register
  • Sign in
  • C calyxos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 490
    • Issues 490
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CalyxOSCalyxOS
  • calyxos
  • Issues
  • #980
Closed
Open
Issue created Apr 13, 2022 by hirnsushi@hirnsushi

FP4 - get_unlock_ability reset to 0

CalyxOS version: 3.3.2
Build number: SP2A.220305.013.A3.22303020

I've noticed that on my FP4 installing CalyxOS somehow reset get_unlock_ability to 0. The bootloader is still unlocked, but the toggle to enable OEM unlocking in developer settings is disabled and greyed out.
The phone started on stock Fairphone OS, was then reflashed with the factory images provided by Fairphone and after that flashed to CalyxOS, no other OS in between, but it has been rooted with Magisk before.
Before being flashed to CalyxOS, get_unlock_ability was still at 1 and there wasn't any issue during installation.

I acknowledge that this probably isn't an issue exclusive to Calyx, others have reported similar issues with /e/, iode and even stock FPOS on the Fairphone forum. I only wanted to reach out, to see if the Calyx devs have some insight on why this might be happening, since Fairphone support just slapped a warning in the docs and hasn't shared any details with the community so far.

Edited Aug 11, 2022 by hirnsushi
Assignee
Assign to
Time tracking