melontini/bootloader-unlock-wall-of-shame: Keeping track of companies that "care about your data ๐Ÿฅบ"

์ฝ˜ํ…์ธ 

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.
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

And for some other models, Hikari Calyx has a repo with prototype ABLs. fih-firmware.hikaricalyx.com

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 themselves!

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 doesn't apply to you.

On pre-May 2022 firmware. I believe these methods were ~universal, but proceed with caution:

I don't have much to say about OPPO.
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, but on May 26th Realme posted this joke of an announcement on their forum c.realme.com. (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

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. The process is pretty much the same for most phones, but newer models may require a HeyTap account.

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.
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.

Note

While not as extreme, if xiaomiui.net 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

Info kindly provided by n1ses!

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. (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 and this Magisk Module 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.

Info kindly provided by aries-ts-indo!

Old devices (pre Android 8):
xdaforums.com

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 says that "Most of our latest devices support our bootloader unlock program."
  • This page 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 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

Moto used confusion! It seems pretty effective...

What? OnePlus? Aren't their phones super easy to unlock? - yes, but...
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.

Ugh, well, this is just egregious!

No, wait, I have a point.

All Fairphones after 2 require you to request a code from this website to enable OEM unlock. There is nothing stopping them from requiring an account and having device unlock limits in the future. This is "proceed with caution" after all.

Not very fair in my opinion, but whatever fairs your phone.

Sony has an open policy for software developers:

  • They are releasing AOSP sources under Sony Open Devices Program.
  • Jolla provides first-class support for installing Sailfish OS on select Xperias. That wouldn't be possible without Sony's openness.

Since Sony likes to ruin a perfect thing:

  • Sony requires you to request an unlock code from their servers. They can pull the plug anytime. You have to send your IMEI and agree to warranty voiding.

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. With the latest feat being RCS messaging which requires DEVICE integrity to work. (To prevent "spam", of course)

Nothing Phones can be unlocked via fastboot without any codes. The only requirement is to enable OEM unlocking in Developer Options settings page. This is the same procedure as on Google Pixel.

Kirin 620, 650, 655, 658, 659, 925, 935, 950, 960:
It's possible to unlock using testpoints and PotatoNV (Read the readme)

If you own a MediaTek device exploitable by mtkclient you can unlock the bootloader using that.
If it also happens to be an OPPO/Realme device and you need to access fastboot: lkpatcher (web version)

If you own a phone with the Unisoc ud710 or ums512 SOCs you can look into this exploit: CVE-2022-38694_unlock_bootloader

Otherwise, you can also look into this: Spectrum_UnlockBL_Tool
This: xdaforums.com
Or this: subut

There's no Universal Qualcomm method, unfortunately.

Although some of these might work for you:

The general exploit:
alephsecurity.com the bootloader unlock section.

Xiaomi Mi A1 and maybe all MSM89** manufactured before 2018:
EDLUnlock

You canโ€™t perform that action at this time.

์š”์•ฝํ•˜๋‹ค
The article discusses various challenges and methods related to unlocking bootloaders on different smartphone brands such as Nokia, OPPO, Vivo, Realme, Xiaomi, Samsung, ZTE, Motorola, OnePlus, Fairphone, and Sony. It provides insights into unofficial services, tools, and procedures required for bootloader unlocking, highlighting restrictions, risks, and potential issues users may face. The article also touches on the impact of bootloader unlocking on device features, warranty, and user experience. Additionally, it mentions the evolving policies of smartphone manufacturers towards bootloader unlocking, emphasizing the importance of caution and awareness when attempting to unlock bootloaders on different devices.
ย