explaingit

zenfyrdev/bootloader-unlock-wall-of-shame

4,643Audience · developerComplexity · 1/5Setup · easy

TLDR

A community-maintained ranking of Android phone makers that block bootloader unlocking, plus documented technical workarounds for specific chipsets like MediaTek, Qualcomm, Kirin, and Unisoc.

Mindmap

mindmap
  root((Bootloader Unlock List))
    Manufacturer Tiers
      Tier 1 Terrible
      Tier 2 Avoid
      Tier 3 Restricted
      Tier 4 Safe
    Chipset Workarounds
      Kirin PotatoNV
      MediaTek mtkclient
      Qualcomm exploits
      Unisoc CVE
    Purpose
      Track user freedom
      Document restrictions
    Contributions
      Pull requests
      GitHub discussions
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Check a phone brand's bootloader unlock policy before buying to know if you can install custom ROMs

USE CASE 2

Find the right tool for unlocking a specific chipset such as mtkclient for MediaTek or PotatoNV for Kirin devices

USE CASE 3

Research which manufacturers respect user freedom and which tier they fall into on the ranking

USE CASE 4

Contribute updated unlock status or new workarounds for devices via pull request

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

This repository is a publicly maintained list tracking which Android phone manufacturers make it difficult or impossible to unlock the bootloader on the devices they sell. Unlocking the bootloader is a technical step that gives the owner full control over what software runs on their phone, including the ability to install a custom operating system. The project frames manufacturers that block this as companies pretending to protect user data while actually restricting user freedom. The list groups manufacturers into four tiers. The first tier, labeled as just terrible, includes brands like Samsung, Huawei, Apple, and Amazon, where unlocking is described as completely impossible without a workaround. A second tier marks brands to avoid, covering manufacturers that allow unlocking only under specific conditions, such as for certain regions or phone models, or that require unusual steps. A third tier covers brands that require an online account or a waiting period before you can unlock, including Google, Sony, and OnePlus. A fourth tier marks brands currently considered safe, where unlocking is relatively straightforward. Beyond the list itself, the repository documents technical workarounds for specific phone chipsets. For phones using Kirin chips, a tool called PotatoNV is mentioned. For MediaTek chips, a tool called mtkclient may work depending on the device. For Qualcomm chips, the README references some older exploits and a recently discussed but unconfirmed vulnerability. For Unisoc chips, a specific CVE exploit is listed for certain models. The repository also includes a section on custom Android Verified Boot keys, a feature that lets some devices run a custom operating system while keeping the bootloader locked, which is described as rare. Contributions are welcomed via pull requests or discussions on GitHub. Mirrors exist on Codeberg and another platform, but those are not monitored for issues. A Russian translation of the README is also available.

Copy-paste prompts

Prompt 1
I want to install a custom ROM on my phone with a MediaTek chipset but the manufacturer blocks bootloader unlocking. What does this repository say about using mtkclient and what are the risks?
Prompt 2
I'm shopping for a new Android phone and want to be able to install a custom OS. Based on the bootloader unlock tier list, which brands should I buy from and which should I avoid?
Prompt 3
Explain how Android Verified Boot custom keys work and which phones on this list support installing a custom OS while keeping the bootloader locked
Prompt 4
My Qualcomm-based phone is on the restricted list. What exploits or workarounds are documented in this repository for Qualcomm chipsets and how reliable are they?
Open on GitHub → Explain another repo

← zenfyrdev on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.