bootloader-unlock-wall-of-s.../README.md

111 lines
3.9 KiB
Markdown
Raw Normal View History

2024-10-16 13:41:55 -04:00
![Banner. A lock and a key on fire on the left and the text 'Bootloader Unlock: Wall of Shame' on the right.](/misc/banner/banner.jpg)
2023-07-30 09:00:32 -04:00
2023-06-10 08:47:24 -04:00
Keeping track of companies that "care about your data 🥺"
2023-06-10 09:31:25 -04:00
[Switch to Russian translation](ru/README.md)
2024-05-30 13:31:04 -04:00
![Terrible](https://raw.githubusercontent.com/melontini/mini-badges/main/personal/terrible.svg)
[![License CC BY-NC-SA](https://raw.githubusercontent.com/melontini/mini-badges/main/licenses/cc/CC-BY-NC-SA-4.0.svg)](https://github.com/melontini/bootloader-unlock-wall-of-shame/blob/main/LICENSE)
2023-06-29 15:14:54 -04:00
2023-06-10 09:31:25 -04:00
## 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.
2023-07-07 22:14:28 -04:00
While this may not affect you directly, it sets a bad precedent. You never know what will get the axe next: Shizuku? ADB? Sideloading? I thought it might be a good idea to keep track of bad companies and workarounds.
2023-06-10 09:31:25 -04:00
2023-06-29 11:57:10 -04:00
If you know of specific details/unlocking methods, please PR them or drop them in the [discussions](https://github.com/melontini/bootloader-unlock-wall-of-shame/discussions)
2023-06-10 10:16:37 -04:00
2023-06-10 09:31:25 -04:00
# The list:
2023-12-19 10:21:08 -05:00
> [!CAUTION]
> Reminder that no matter how nice a company is, <br/>
> you should not trust them unless their unlock process is 100% offline!
2023-11-08 12:37:07 -05:00
2023-12-19 10:21:08 -05:00
## ⛔ Avoid at all costs!
2023-06-10 09:31:25 -04:00
2024-10-04 12:21:21 -04:00
### [Huawei/Honor](/brands/huawei/README.md)
2023-06-10 09:31:25 -04:00
2024-10-04 12:21:21 -04:00
### [HMD Global/Nokia](/brands/nokia/README.md)
2023-06-10 09:31:25 -04:00
2024-10-04 12:21:21 -04:00
### [Vivo/IQOO](/brands/vivo/README.md)
2023-06-10 10:16:37 -04:00
2024-10-04 12:21:21 -04:00
### [OPPO/Realme](/brands/oppo/README.md)
2023-06-11 00:47:26 -04:00
2024-10-04 12:21:21 -04:00
### [Xiaomi/Redmi/POCO](/brands/xiaomi/README.md)
2023-06-11 00:47:26 -04:00
2024-10-04 12:21:21 -04:00
### [Samsung](/brands/samsung/README.md)
2024-10-04 12:21:21 -04:00
### [ZTE](/brands/zte/README.md)
2024-10-04 12:21:21 -04:00
### [LG](/brands/lg/README.md)
2024-10-04 12:21:21 -04:00
### [HTC](/brands/htc/README.md)
2023-06-11 00:47:26 -04:00
2024-10-04 12:21:21 -04:00
### [Meizu](/brands/meizu/README.md)
2023-06-10 10:16:37 -04:00
2024-10-04 12:21:21 -04:00
### [Asus](/brands/asus/README.md)
2023-06-10 10:16:37 -04:00
2024-10-04 12:21:21 -04:00
### [Alcatel](/brands/alcatel/README.md)
2023-06-11 13:03:43 -04:00
2024-10-04 14:44:14 -04:00
### [Apple](/brands/apple/README.md)
2024-09-24 13:10:59 -04:00
2024-10-04 12:21:21 -04:00
### [Motorola/Lenovo](/brands/motorola/README.md)
2024-09-24 08:38:29 -04:00
### [Energizer](/brands/energizer/README.md)
## ⚠️ Proceed with caution!
2024-10-04 12:21:21 -04:00
### [OnePlus](/brands/oneplus/README.md)
2024-04-07 21:05:48 -04:00
2024-10-04 12:21:21 -04:00
### [Fairphone](/brands/fairphone/README.md)
2024-04-07 21:05:48 -04:00
2024-10-04 12:21:21 -04:00
### [Sony](/brands/sony/README.md)
2024-04-07 21:05:48 -04:00
2024-10-04 12:21:21 -04:00
### [Microsoft](/brands/microsoft/README.md)
2023-12-19 10:21:08 -05:00
## "Safe for now" :trollface:
2024-10-04 12:21:21 -04:00
### [Google](/brands/google/README.md)
2023-12-19 10:21:08 -05:00
2024-10-04 12:21:21 -04:00
### [Nothing](/brands/nothing/README.md)
2024-04-07 21:05:48 -04:00
2024-10-04 12:21:21 -04:00
### [Umidigi](/brands/umidigi/README.md)
# Misc info
2024-10-04 13:54:32 -04:00
## Custom AVB Keys
Custom Android Verified Boot keys is a feature which allows you to run a custom OS with a locked bootloader.
It's rare to see a device which supports custom AVB keys, but some devices can be found [here](https://github.com/chenxiaolong/avbroot/issues/299).
## Universal SOC-based methods
2023-07-07 22:18:56 -04:00
2023-12-19 10:21:08 -05:00
### Kirin
2023-07-11 13:03:02 -04:00
Kirin 620, 650, 655, 658, 659, 925, 935, 950, 960:<br/>
2023-11-08 13:03:15 -05:00
It's possible to unlock using testpoints and [PotatoNV](https://github.com/mashed-potatoes/PotatoNV) (Read the readme)
2023-06-10 10:16:37 -04:00
2023-12-19 10:21:08 -05:00
### MediaTek
2023-11-08 13:03:15 -05:00
If you own a MediaTek device exploitable by [mtkclient](https://github.com/bkerler/mtkclient) you can unlock the bootloader using that.<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/))
2023-07-01 13:55:27 -04:00
2023-12-19 10:21:08 -05:00
### Unisoc
2023-11-08 13:03:15 -05:00
If you own a phone with the Unisoc ud710 or ums512 SOCs you can look into this exploit: [CVE-2022-38694_unlock_bootloader](https://github.com/TomKing062/CVE-2022-38694_unlock_bootloader)
2023-07-07 23:10:34 -04:00
2023-11-08 13:03:15 -05:00
Otherwise, you can also look into this: [Spectrum_UnlockBL_Tool](https://github.com/zhuofan-16/Spectrum_UnlockBL_Tool) <br/>
2023-11-22 10:09:55 -05:00
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/)
2023-07-11 12:59:41 -04:00
2023-12-19 10:21:08 -05:00
### Qualcomm
2023-07-07 23:10:34 -04:00
There's no Universal Qualcomm method, unfortunately.
2023-07-07 23:29:04 -04:00
Although some of these might work for you:
2023-07-07 23:10:34 -04:00
The general exploit:<br/>
2023-11-08 13:03:15 -05:00
[alephsecurity.com](https://alephsecurity.com/2018/01/22/qualcomm-edl-2/) the bootloader unlock section.
2023-07-07 23:10:34 -04:00
Xiaomi Mi A1 and maybe all MSM89** manufactured before 2018:<br/>
2023-11-08 13:03:15 -05:00
[EDLUnlock](https://github.com/Giovix92/EDLUnlock)
2023-07-16 17:29:13 -04:00
***