zenfyrdev/bootloader-unlock-wall-of-shame

Keeping track of companies that "care about your data 🥺"

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 55 minutes ago
Added to GitGenius on September 12th, 2026
Created on June 10th, 2023
Open Issues & Pull Requests: 5 (+1)
GitHub issues: Enabled
Number of forks: 162
Total Stargazers: 5,415 (+0)
Total Subscribers: 66 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.7 hours
Mean response time: 3.8 days
90th percentile: 8.4 days
Tracked items: 86

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 16% of issues opened in the past year have been closed. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 35 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Detailed Description

Bootloader Unlock: Wall of Shame is a reference database that documents smartphone manufacturers' policies and practices around bootloader unlocking.

The project addresses the growing trend of device manufacturers restricting or blocking bootloader unlocking on consumer hardware, framing this as a data privacy and device ownership issue. It maintains a curated list of manufacturers organized by severity: those that make bootloader unlocking completely impossible without workarounds, and those that allow it only under restrictive conditions such as regional limitations, specific device models, or other sacrifices. The repository collects specific details about each manufacturer's unlock policies and documents known workarounds where they exist.

This resource is most useful for developers and enthusiasts who prioritize device ownership and the ability to modify their hardware, or who are concerned about the precedent set by manufacturers restricting low-level access. It serves as a decision aid when choosing devices, particularly for those who may want to run custom ROMs, use development tools, or maintain full control over their own hardware. The project emphasizes that even manufacturers with relatively permissive policies should not be fully trusted unless their unlock process is completely offline, requiring no external verification or company approval.

The project actively solicits community contributions through pull requests and discussions, indicating ongoing maintenance and a willingness to incorporate new information about manufacturer policies and unlocking methods. The maintainer has established the repository across multiple platforms including GitHub, Codeberg, and tangled, though GitHub is designated as the primary channel for issues and contributions.