Know Your Phone

What unlocking the bootloader really does — warranty, banking apps and the things that do not come back

Updated

Unlocking is reversible in the obvious sense and irreversible in several others. This is the list of what changes, what a re-lock restores, and what it does not.

Team MMR3 min read

Unlocking the bootloader is presented as a switch: turn it off, install what you like, turn it back on. The switch part is true. What is not true is that everything returns to where it was when you flip it back, and the gap between those two statements is where people lose functions they cared about.

What the lock is for

A locked bootloader will only start software signed by the manufacturer. Each stage of the boot process verifies the next before handing control to it, so the running system can be traced back to a key the maker controls. That chain is what lets a phone make claims about itself that other software is willing to believe — that the system partition has not been modified, that the keys held in the secure hardware are still trustworthy, that content handed to it will not be intercepted.

Unlocking breaks the chain deliberately. That is the point of it, and everything that follows is a consequence of the same fact.

What happens at the moment of unlocking

  • The device is wiped. Mandatory, and by design: the alternative would let anyone with physical access unlock a phone and read its data. Take a backup first, and remember that the backup will not carry an eSIM profile — that has to be re-issued.
  • A warning screen appears at every boot. On most phones it cannot be removed while the bootloader is unlocked.
  • Hardware-backed attestation stops being trusted. Applications that ask the phone to prove its integrity receive a negative answer.

What does not come back after re-locking

Re-locking restores the boot chain and removes the warning screen. It does not restore everything that depended on the chain.

On many models the streaming DRM provisioning is invalidated permanently at the moment of unlock, and no amount of re-locking brings the higher certification back; the keys were revoked in the device, not merely disabled. The detail is in the piece on Widevine levels.

Several manufacturers also set a one-time flag in hardware when the bootloader is first unlocked. The flag survives re-locking, factory resets and firmware reinstalls, and a service centre can read it. Some makers treat it as evidence that user modification voided coverage for the affected parts; others do not. The important point is that the record is permanent and is not under your control.

Payment and integrity-dependent features are a mixed case. Some recover after a re-lock with official firmware; some record the event and stay cautious; some never behave the same way again on that handset. Which ones fall into which category changes over time, which is why the honest answer to "will my banking app work afterwards" is that you cannot know before you try, and that the app vendor has no obligation to help. The mechanics are covered in Play Integrity and banking apps.

Warranty: the distinction that matters

In most consumer-protection frameworks a manufacturer may decline a claim for a fault the user caused, and may not decline a claim for an unrelated fault simply because the user modified the software. A cracked screen and a failed camera module are not caused by a bootloader unlock, and a blanket refusal on those grounds is usually weaker than it sounds. A phone that will not boot after a firmware flash is a different matter entirely.

In practice the outcome depends on where you are, on the maker's policy and on the service centre. Returning the phone to official firmware with the bootloader re-locked before any service visit is sensible, and remains sensible even though the hardware flag may have recorded the event: it removes the argument about software from the conversation.

When it is worth it

Unlocking is worth it when the alternative is a phone that has stopped receiving updates and an actively maintained community build that will keep it patched — the security argument in the patch-level piece runs both ways. It is worth it for development work, and for keeping older hardware usable.

It is not worth it on a phone under warranty that you depend on daily, and it is not worth it for a cosmetic change. Decide before you unlock, because the decision is cheap in advance and expensive to reverse.