mirror of
https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame.git
synced 2026-10-14 05:38:08 +00:00
196 lines
8.4 KiB
Markdown
196 lines
8.4 KiB
Markdown
|
||
|
||
Keeping track of companies that "care about your data 🥺"
|
||
|
||
[Switch to Russian translation](ru/README.md)
|
||
|
||
|
||
[](https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame/blob/main/LICENSE)
|
||
|
||
<details><summary>mirrors</summary>
|
||
<p>
|
||
|
||
- GitHub: https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame
|
||
- Codeberg: https://codeberg.org/zenfyr/bootloader-unlock-wall-of-shame
|
||
- tangled: https://tangled.sh/did:plc:rjhjcb3rgdsmdr6ykywuh63z/bootloader-unlock-wall-of-shame
|
||
|
||
</p>
|
||
</details>
|
||
Do note that issues, pull requests, and discussions on Codeberg and tangled are not monitored. Please use GitHub for these.
|
||
|
||
## Why?
|
||
Over the past few years, a suspicious number of companies have started to "take care of your data", aka block/strictly limit your ability to unlock the bootloader on your *own* devices.
|
||
|
||
While this may not affect you directly, it sets a bad precedent. You never know what will get the axe next: Shizuku? ADB?<br><br>
|
||
**They've already gone after [sideloading](https://keepandroidopen.org).**<br><br>
|
||
|
||
I thought it might be a good idea to keep track of bad companies and workarounds.
|
||
|
||
If you know of specific details/unlocking methods, please PR them or drop them in the [discussions](https://github.com/zenfyrdev/bootloader-unlock-wall-of-shame/discussions).
|
||
|
||
# The list:
|
||
|
||
> [!CAUTION]
|
||
> Reminder that no matter how nice a company is, <br/>
|
||
> you should not trust them unless their unlock process is 100% offline!
|
||
|
||
## ⛔ Avoid at all costs!
|
||
|
||
The following manufacturers have made it completely impossible to unlock their devices without a workaround.
|
||
|
||
### [Alcatel](./brands/alcatel/README.md)
|
||
|
||
### [Amazon](./brands/amazon/README.md)
|
||
|
||
### [Apple](./brands/apple/README.md)
|
||
|
||
### [Asus](./brands/asus/README.md)
|
||
|
||
### [Cat](./brands/cat/README.md)
|
||
|
||
### [Coolpad](./brands/coolpad/README.md)
|
||
|
||
### [Doogee](./brands/doogee/README.md)
|
||
|
||
### [Energizer](./brands/energizer/README.md)
|
||
|
||
### [Huawei](./brands/huawei/README.md)
|
||
|
||
### [Meizu](./brands/meizu/README.md)
|
||
|
||
### [Panasonic](./brands/panasonic/README.md)
|
||
|
||
### [Samsung](./brands/samsung/README.md)
|
||
|
||
### [Sharp](./brands/sharp/README.md)
|
||
|
||
### [TCL/BlackBerry](./brands/tcl/README.md)
|
||
|
||
### [Vivo/IQOO](./brands/vivo/README.md)
|
||
|
||
### [Vsmart](./brands/Vsmart/README.md)
|
||
|
||
### [Windows phones](./brands/winphones/README.md)
|
||
|
||
### Carrier-Locked Devices
|
||
|
||
> [!NOTE]
|
||
> Phone brands handle carrier locks differently, so check your device manual or contact support.
|
||
|
||
Carrier-locked devices are the ones you get after making a commitment with a carrier of your choice. This is quite common in North America and (supposedly) allows you to save some money on your device.
|
||
|
||
As a rule, almost all carrier-locked devices do not allow the bootloader to be unlocked. This usually makes sense, as it would allow you to completely bypass the contract. The problem is that many devices still do not allow you to unlock the bootloader even after the carrier lock has been lifted. For more details, see the [carriers page](./carriers/README.md).
|
||
|
||
## 🍅 Just terrible!
|
||
|
||
The following manufacturers allow unlocking under certain conditions, such as region, model, SOC, etc., or require a sacrifice to unlock.
|
||
|
||
### [Hisense](./brands/hisense/README.md)
|
||
|
||
### [HMD/Nokia](./brands/nokia/README.md)
|
||
|
||
### [Honor](./brands/honor/README.md)
|
||
|
||
### [HTC](./brands/htc/README.md)
|
||
|
||
### [LG](./brands/lg/README.md)
|
||
|
||
### [Motorola/Lenovo/NEC](./brands/motorola/README.md)
|
||
|
||
### [OPPO/Realme](./brands/oppo/README.md)
|
||
|
||
### [Oukitel](./brands/oukitel/README.md)
|
||
|
||
### [Xiaomi/Redmi/POCO](./brands/xiaomi/README.md)
|
||
|
||
### [ZTE/nubia/Redmagic](./brands/zte/README.md)
|
||
|
||
## ⚠️ Proceed with caution!
|
||
|
||
The following manufacturers require an internet connection and/or a waiting period before unlocking.
|
||
|
||
### [Fairphone](./brands/fairphone/README.md)
|
||
|
||
### [Google/Nexus](./brands/google/README.md)
|
||
|
||
### [Infinix](./brands/infinix/README.md)
|
||
|
||
### [itel](./brands/itel/README.md)
|
||
|
||
### [OnePlus](./brands/oneplus/README.md)
|
||
|
||
### [Sony](./brands/sony/README.md)
|
||
|
||
### [Tecno](./brands/tecno/README.md)
|
||
|
||
## ℹ️ "Safe for now" :trollface:
|
||
|
||
### [Blackview](./brands/blackview/README.md)
|
||
|
||
### [Cubot](./brands/cubot/README.md)
|
||
|
||
### [Micromax](./brands/micromax/README.md)
|
||
|
||
### [Microsoft](./brands/microsoft/README.md)
|
||
|
||
### [Nothing](./brands/nothing/README.md)
|
||
|
||
### [Shift](./brands/shift/README.md)
|
||
|
||
### [Teclast](./brands/teclast/README.md)
|
||
|
||
### [Teracube](./brands/teracube/README.md)
|
||
|
||
### [TP-Link/Neffos](./brands/tplink/README.md)
|
||
|
||
### [Ulefone](./brands/ulefone/README.md)
|
||
|
||
### [Umidigi](./brands/umidigi/README.md)
|
||
|
||
### [Volla](./brands/volla/README.md)
|
||
|
||
# Misc info
|
||
|
||
## Custom AVB Keys
|
||
|
||
Custom Android Verified Boot keys are a feature that allows you to run a custom OS with a locked bootloader.
|
||
|
||
It's rare to see a device that supports custom AVB keys, but some devices can be found [here](https://github.com/chenxiaolong/avbroot/issues/299).
|
||
|
||
## Universal SOC-based methods
|
||
|
||
### Kirin
|
||
Kirin 620, 650, 655, 658, 659, 925, 935, 950, 960:<br/>
|
||
It's possible to unlock using test points and [PotatoNV](https://github.com/mashed-potatoes/PotatoNV) (Read the README)
|
||
|
||
### MediaTek
|
||
If you own a MediaTek device exploitable by [mtkclient](https://github.com/bkerler/mtkclient) ([fork old version](https://github.com/R0rt1z2/mtkclient)) or [Penumbra](https://github.com/shomykohai/penumbra), you can unlock the bootloader using it.<br/>
|
||
If it also happens to be an OPPO/Realme device and you need to access fastboot: [lkpatcher](https://github.com/R0rt1z2/lkpatcher) ([web version](https://lkpatcher.r0rt1z2.com/))
|
||
|
||
If bootloader unlocking doesn't work on an Oppo Mediatek device using the SECCFG mod (unlocking via mtkclient), you can try unlocking fastboot by writing a modified boot1 (preloader). Writing a preloader also uses mtkclient: [oppo-mtk-fastboot-unlock](https://github.com/Shocked-Cat/oppo-mtk-fastboot-unlock).
|
||
|
||
### Qualcomm
|
||
|
||
#### Snapdragon 8 Elite Gen 5/Snapdragon 8 Elite
|
||
|
||
**Patched in February/March 2026**
|
||
|
||
On Snapdragon 8E5/8E, Qualcomm introduced a [vulnerability (CN)](https://www.cnblogs.com/sakrain/p/-/unlock-your-qualcomm) [(POC)](https://github.com/kasnria001/qualcomm_gbl_exploit_poc) where the boot process would not perform signature verification for the Generic Bootloader, so with write access to the `efisp` partition it was possible to run arbitrary code.
|
||
|
||
While the vulnerability itself is universal for the platform, it requires device/OEM-specific tricks to get root and write the GBL. Some exist for [Xiaomi devices](./brands/xiaomi/README.md#snapdragon-8-elite8gen38gen28gen1).
|
||
|
||
#### Other
|
||
|
||
The general exploit:<br/>
|
||
[alephsecurity.com](https://alephsecurity.com/2018/01/22/qualcomm-edl-2/) the bootloader unlock section.
|
||
|
||
### Unisoc
|
||
If you own a phone with the Unisoc UMS9620 or older, you can use [this](https://github.com/TomKing062/CVE-2022-38694_unlock_bootloader) (UMS9621 needs [this](https://github.com/TomKing062/exec_addr_v2) as exec address) to achieve temporary secure boot bypass and persistently unlock the bootloader. This is valid for all devices except some devices with [modified uboot](https://github.com/TomKing062/CVE-2022-38694_unlock_bootloader/wiki/patch_do_cboot%E2%80%90SPL#part-2-modify-fdl2ubootlk) which need [this](https://github.com/TomKing062/unisoc_chipram_signcheck_exploit) or [this](https://github.com/YC-nw/bsp_sign_fxxker) or [this](https://github.com/kasnria001/unisoc_secure_boot_bypass). Note that the method used in all three links is the same, but implemented by different people with possible differences. Also, using this, aside from unlocking the bootloader, it is possible to completely disable dm-verity by patching the trustos partition, which allows booting of unsigned partitions.
|
||
|
||
If you own a phone with the Unisoc UMS312, UMS512, or UD710, you can use [this](https://github.com/TomKing062/CVE-2022-38691_38692) exploit to achieve persistent secure boot bypass, which means all firmware, including splloader and uboot, can be modified and re-signed.
|
||
|
||
Otherwise, you can also look into this: [Spectrum_UnlockBL_Tool](https://github.com/zhuofan-16/Spectrum_UnlockBL_Tool) <br/>
|
||
This: [xdaforums.com](https://xdaforums.com/t/alldocube-t803-smile_1-bootloader-unlock-w-unisoc-t310.4393389/) <br/>
|
||
Or this: [subut](https://unisoc-android.github.io/subut/)
|
||
|
||
***
|