mirror of
https://github.com/melontini/bootloader-unlock-wall-of-shame.git
synced 2025-01-15 08:36:46 -05:00
173 lines
12 KiB
Markdown
173 lines
12 KiB
Markdown
![Bootloader Unlock: Wall of Shame](https://github.com/melontini/bootloader-unlock-wall-of-shame/assets/104443436/2b9dbf70-faf3-49ab-886b-d88f50c5dbe0)
|
||
|
||
Keeping track of companies that "care about your data 🥺"
|
||
|
||
[![Static Badge](https://img.shields.io/badge/License-CC--BY--NC--SA-blue)](https://github.com/melontini/bootloader-unlock-wall-of-shame/blob/main/LICENSE)
|
||
[![Hits](https://hits.seeyoufarm.com/api/count/incr/badge.svg?url=https%3A%2F%2Fgithub.com%2Fmelontini%2Fbootloader-unlock-wall-of-shame&count_bg=%2379C83D&title_bg=%23555555&icon=&icon_color=%23E7E7E7&title=hits&edge_flat=false)](https://hits.seeyoufarm.com)
|
||
|
||
## 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? Sideloading? 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/melontini/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!
|
||
|
||
### Huawei/Honor
|
||
In the past, Huawei allowed you to unlock with a special code you get by submitting some information to emui.com (IMEI, serial, model, and product ID), but in 2018 "corporate values have changed" and the site went down. <br/>
|
||
Worse, on Android 10+, the unlock command has been **completely removed** from fastboot.
|
||
|
||
Certain Kirin-based phones can use [PotatoNV](https://github.com/melontini/bootloader-unlock-wall-of-shame#kirin)
|
||
|
||
Paid methods:<br/>
|
||
I don't recommend paid methods due to general sketchiness. I have used one of these tools a while ago, it was okay.<br/>
|
||
Through HCU-client (Not everything is supported + incredible prices [hcu-client.com](https://hcu-client.com/buy/)) or DC-Unlocker (Same problems as HCU [dc-unlocker.com](https://www.dc-unlocker.com/buy))
|
||
|
||
### HMD Global/Nokia
|
||
In the flaming pile of HMD's "great" decisions to improve Nokia, one stands out more than others: They decided to follow the fresh "lock the bootloader" trend.<br/>
|
||
Why was this necessary? I don't know...
|
||
|
||
Well, anyway. Models released before early 2019 can request unlocking using Hikari Calyx's unofficial service [hikaricalyx.com](https://hikaricalyx.com/request-bootloader-unlock)
|
||
|
||
And for some other models, Hikari Calyx has a repo with prototype ABLs. [fih-firmware.hikaricalyx.com](https://fih-firmware.hikaricalyx.com/protoabl/)
|
||
|
||
Models 7.2, 8.3 and 5.3 can be unlocked offline, while others may require HMD Device Kit **which is not public and requires a service account.**
|
||
|
||
> Info kindly provided by [Hikari Calyx](https://github.com/HikariCalyx) themselves!
|
||
|
||
### Vivo/IQOO
|
||
The BBK family has an unlocking problem. If in case of OPPO/Realme they at least offer an app in some regions, Vivo is locked completely.
|
||
|
||
Well, that is, if [xdaforums.com](https://xdaforums.com/t/how-to-unlock-bootloader-of-vivo-phones.3686690/) doesn't apply to you.
|
||
|
||
On pre-May 2022 firmware. I believe these methods *were* ~universal, but proceed with caution:
|
||
|
||
* Vivo x70 Pro+: [xdaforums.com](https://xdaforums.com/t/vivo-x70-pro-bootloader-unlock-how-to-guide.4444989/)
|
||
* Vivo Y31 2021: [xdaforums.com](https://xdaforums.com/t/unlocking-bootloader-rebooting-in-edl-without-testpoint-vivo-y31-2021.4440801/)
|
||
|
||
### OPPO/Realme
|
||
I don't have much to say about OPPO.<br/>
|
||
The most annoying thing about them is that you *can* unlock your bootloader, but only if you can get into fastboot. And guess what? They locked fastboot with an RSA key!
|
||
|
||
As per Realme, they decided that segregating people by ~~race~~ their phone's region is cool. If you didn't buy your phone in China or India, chances are you won't be unlocking anything anytime soon.
|
||
|
||
In April-May 2023 you could unlock any Realme phone using this script [rmx3474-rooting](https://github.com/turistu/rmx3474-rooting), but on May 26th Realme posted this joke of an announcement on their forum [c.realme.com](https://c.realme.com/in/post-details/1671137365285982208). (They've deleted the original announcement)
|
||
Since then, they have forced their servers to only return "new struct" keys, which have model data attached, making the script useless.
|
||
|
||
In theory, if available, you could use full-OTA packages to change your phone's firmware region and use the deep testing app directly, but I can't verify that this works (please, correct me if I'm wrong). Guide: [xdaforums.com](https://xdaforums.com/t/change-region-via-full-ota.4535659/)
|
||
|
||
As for China and India... Seeing how easily Realme dropped the ball on their global users, I personally would be worried about their future plans. For now, you'll have to find and follow device-specific instructions at [c.realme.com](https://c.realme.com/in/). The process is pretty much the same for most phones, but newer models may require a HeyTap account.
|
||
|
||
### Xiaomi/Redmi/POCO
|
||
|
||
While this (currently) only affects users in China, Xiaomi's new policy makes unlocking very annoying.
|
||
|
||
With this new policy, **You must have a Level 5 developer Xiaomi Community account.** </br>
|
||
And here's a list of things you have to do to get that:
|
||
- You must be a citizen of China.
|
||
- You have to use HyperOS and report at least 1 bug per day. (????)
|
||
- You have to submit at least 1 HyperOS suggestion per month. (????)
|
||
- You must be an active Xiaomi Community user.
|
||
|
||
Additional BS applies:
|
||
- The permission to unlock is temporary and is granted for 1-year only.
|
||
- You can only unlock 3 devices per-year.
|
||
- You will not receive OTA updates.
|
||
- your warranty will be void.
|
||
|
||
Also, check out [Xiaomi-HyperOS-BootLoader-Bypass](https://github.com/MlgmXyysd/Xiaomi-HyperOS-BootLoader-Bypass) by [MlgmXyysd](https://github.com/MlgmXyysd).
|
||
|
||
> [!NOTE]
|
||
> While not as extreme, if [xiaomiui.net](https://xiaomiui.net/how-unlock-bootloader-xiaomi-hyperos-53493/) is to be believed, global unlock has also undergone some changes:
|
||
> * Your Mi Account has been active for more than 30 days.
|
||
> * Xiaomi Community App version 5.3.31 or above.
|
||
> * You can only unlock the bootloader of 3 devices per year with your account.
|
||
|
||
Look here if you want to learn about how Ximi's bootloader works: [Xiaomi-bootloader](https://github.com/lrh2000/Xiaomi-bootloader)
|
||
|
||
> Info kindly provided by [n1ses](https://github.com/n1ses)!
|
||
|
||
### Samsung
|
||
If you have a North American device, well, uh... If you're lucky enough not to update for a while, you can check out [this paid service](https://xdaforums.com/t/android-unsamlock-bootloader-unlock-for-samsung-us-canada-devices.4215101/). (At your own risk)
|
||
|
||
If you bought your phone elsewhere, and it's not carrier locked, you can use the standard process, but brace yourself for all the breakage coming your way!
|
||
|
||
For example, unlocking will permanently trip Knox. As a result, *any* Knox-based features will be broken *even if you re-lock*. This includes, but not limited to: Samsung Pay, Pass, Flow, Health, Secure Folder, Secure Wi-Fi, Smart View. Can you be denied warranty? Probably...
|
||
Some of those features can be fixed with this LsPosed module [KnoxPatch](https://github.com/BlackMesa123/KnoxPatch) and this Magisk Module [KnoxPatch#knoxpatch-enhancer](https://github.com/BlackMesa123/KnoxPatch#knoxpatch-enhancer).
|
||
|
||
In addition, some basic features can, and will probably break, such as VoLTE, (thanks to Samsung's proprietary implementation) and in certain cases [even the camera](https://xdaforums.com/t/a52s-5g-sm-a528b-unlock-bootloader-camera-failed.4336007/).
|
||
|
||
> Info kindly provided by [aries-ts-indo](https://github.com/aries-ts-indo)!
|
||
|
||
### ZTE
|
||
|
||
Old devices (pre Android 8):<br/>
|
||
[xdaforums.com](https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/)
|
||
|
||
## ⚠️ Proceed with caution!
|
||
|
||
### Motorola
|
||
To start off, to unlock your bootloader you have to submit a request on their website, which is pretty bad on its own (*wink* Huawei). But how do you know if your device is unlockable? Well...
|
||
|
||
* [This page](https://en-us.support.motorola.com/app/answers/detail/a_id/87215) says that "Most of our latest devices support our bootloader unlock program."
|
||
* [This page](https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a) says only "Photon Q 4G LTE, DROID RAZR M(Developer Edition), DROID RAZR HD(Developer Edition CDMA-LTE), MOTOROLA RAZR HD (Rest of World -UMTS/LTE), MOTOROLA RAZR HD (Rogers Canada - UMTS/LTE) and MOTOROLA RAZR i are supported by the Bootloader Unlock site."
|
||
* [And from this conversation](https://xdaforums.com/t/how-to-guide-unlocking-using-deeptest-gdpr.4585829/post-88734665) [turistu](https://github.com/turistu) had with their support: "most of our E devices doesn't support bootloader unlock program. Please see below a list of devices that support the bootloader unlock program : g100, g51 , g71 , g200 , g52 , g82 , g42 , g62 , g32"
|
||
* There's also an unofficial way with CID to check if your device can be unlocked, check here: [xdaforums.com](https://xdaforums.com/t/guide-un-locking-motorola-bootloader.4079111/post-85375429)
|
||
|
||
> Moto used confusion! It seems pretty effective...
|
||
|
||
### OnePlus
|
||
What? OnePlus? Aren't their phones super easy to unlock? - yes, but... <br/>
|
||
You probably heard about the OnePlus X OPPO os merger and while it did get called off, both companies started sharing a "unified codebase". You can probably see where I'm going.
|
||
|
||
If one day OnePlus decides to practice racism like Realme or go nuclear like OPPO/Vivo, they'll have those "unified" tools at their disposal.
|
||
|
||
## ℹ️ "Safe for now" :trollface:
|
||
|
||
### Google
|
||
Allows unlocking on almost any non-carrier locked device, but is also a pioneer in making rooting and custom ROMs painful with things like Safety Net and Play Integrity.
|
||
|
||
### Fairphone
|
||
No notes.
|
||
|
||
# Misc info
|
||
|
||
## Universal SOC-based methods
|
||
|
||
### Kirin
|
||
Kirin 620, 650, 655, 658, 659, 925, 935, 950, 960:<br/>
|
||
It's possible to unlock using testpoints 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) 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/))
|
||
|
||
### Unisoc
|
||
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)
|
||
|
||
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/)
|
||
|
||
### Qualcomm
|
||
There's no Universal Qualcomm method, unfortunately.
|
||
|
||
Although some of these might work for you:
|
||
|
||
The general exploit:<br/>
|
||
[alephsecurity.com](https://alephsecurity.com/2018/01/22/qualcomm-edl-2/) the bootloader unlock section.
|
||
|
||
Xiaomi Mi A1 and maybe all MSM89** manufactured before 2018:<br/>
|
||
[EDLUnlock](https://github.com/Giovix92/EDLUnlock)
|
||
|
||
***
|
||
|
||
<a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png" /></a><br /><span xmlns:dct="http://purl.org/dc/terms/" property="dct:title">Bootloader Unlock: Wall of Shame</span> by <a xmlns:cc="http://creativecommons.org/ns#" href="https://github.com/melontini/bootloader-unlock-wall-of-shame" property="cc:attributionName" rel="cc:attributionURL">https://github.com/melontini/bootloader-unlock-wall-of-shame</a> is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.
|