From dcd1f904252bf8340fdfba747931b8c4202b8b92 Mon Sep 17 00:00:00 2001 From: melontini <104443436+melontini@users.noreply.github.com> Date: Sun, 13 Oct 2024 17:34:58 +0700 Subject: [PATCH] Add 'Generic Unlock Guide' + reject the OnePlus page. --- brands/google/README.md | 1 + brands/nothing/README.md | 1 + brands/oneplus/README.md | 3 +- brands/umidigi/README.md | 4 +- brands/xiaomi/README.md | 2 + misc/generic-unlock.md | 101 +++++++++++++++++++++++++++++++++++++++ 6 files changed, 110 insertions(+), 2 deletions(-) create mode 100644 misc/generic-unlock.md diff --git a/brands/google/README.md b/brands/google/README.md index 37d953e..077a8ce 100644 --- a/brands/google/README.md +++ b/brands/google/README.md @@ -1,6 +1,7 @@ # Google * Verdict **ℹī¸ "Safe for now" :trollface:** +* [**🔓ī¸ Unlock Guide**](/misc/generic-unlock.md) 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) diff --git a/brands/nothing/README.md b/brands/nothing/README.md index 8bab943..ec432ca 100644 --- a/brands/nothing/README.md +++ b/brands/nothing/README.md @@ -1,6 +1,7 @@ # Nothing * Verdict **ℹī¸ "Safe for now" :trollface:** +* [**🔓ī¸ Unlock Guide**](/misc/generic-unlock.md) 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. diff --git a/brands/oneplus/README.md b/brands/oneplus/README.md index 5a5a7e1..8888ce8 100644 --- a/brands/oneplus/README.md +++ b/brands/oneplus/README.md @@ -1,6 +1,7 @@ # OnePlus -> â˜ĸī¸ This info is just speculation! +> [!CAUTION] +> 🛑 This page is rejected and requires a complete rewrite. - Verdict: **⚠ī¸ Proceed with caution!** diff --git a/brands/umidigi/README.md b/brands/umidigi/README.md index 2db66bd..2fa297d 100644 --- a/brands/umidigi/README.md +++ b/brands/umidigi/README.md @@ -2,7 +2,9 @@ * Verdict **ℹī¸ "Safe for now" :trollface:** -Umidigi phones are generally unlockable, however due to them being a budget-focused manufacturer, they use Unisoc SoCs, and [Unisoc requires a bunch of extra steps to unlock for whatever reason][Unisoc Unlock], and therefore I wouldn't consider them completely safe. MediaTek Umidigi devies can just use flashing unlock/oem unlock in fastboot. +Umidigi phones are generally unlockable, however due to them being a budget-focused manufacturer, they use Unisoc SoCs, and [Unisoc requires a bunch of extra steps to unlock for whatever reason][Unisoc Unlock], and therefore I wouldn't consider them completely safe. + +MediaTek devices can follow the [**🔓ī¸ Generic Unlock Guide**](/misc/generic-unlock.md). *** Authored by [Ivy / Lost-Entrepreneur439](https://github.com/Lost-Entrepreneur439).
diff --git a/brands/xiaomi/README.md b/brands/xiaomi/README.md index ffa92fc..fcb7045 100644 --- a/brands/xiaomi/README.md +++ b/brands/xiaomi/README.md @@ -38,6 +38,8 @@ While not as extreme, if [xiaomiui.net][global-requirements] is to be believed, ## Android One +* [**🔓ī¸ Unlock Guide**](/misc/generic-unlock.md) + Devices shipping with Android One do NOT have any unlock requirements. They follow the standard Android unlock process. *** diff --git a/misc/generic-unlock.md b/misc/generic-unlock.md new file mode 100644 index 0000000..72d15dd --- /dev/null +++ b/misc/generic-unlock.md @@ -0,0 +1,101 @@ +# 🔓ī¸ Generic Unlock Guide + +- Difficulty: **Easy 📗** + +> [!CAUTION] +> Read in full before you act! + +The standard unlocking process is to enable **OEM unlocking** from the developer options and then run some commands from fastboot. + +## Requirements + +- A device to which you can connect your patient. +- Ability to tweak terminal commands to fit your system. +- Ability to follow simple instructions. + +> [!NOTE] +> This guide does not work with Unisoc/Spreadtrum devices!
+> They require additional steps not mentioned here. + +## Getting Ready + +To unlock you phone, you have to download SDK Platform Tools. + +Go to [developer.android.com](https://developer.android.com/tools/releases/platform-tools#downloads) and download the package for your OS (most likely Windows) and extract the archive where appropriate. +On Linux it may be better to use your distro's package manager, although the package may be quite old. + +### Windows + +On Windows, some devices might require special drivers. In these cases, Windows can download them automatically. +Otherwise, go to [OEM USB Drivers](https://developer.android.com/studio/run/oem-usb) and search for your manufacturer. +If your device isn't included in this list, you'll have to search for drivers yourself. + +### Linux + +> Should only happen when using the archive version. + +If you run `./fastboot devices` now, you may get a `no permissions; see [http://developer.android.com/tools/device.html]` error. + +One solution is to use `sudo`, `pkexec` or `run0`, +but the correct way is to set up `udev` rules for the adb/fastboot binary to work. The procedure usually depends on the distribution. + +## OEM Unlocking + +To enable OEM Unlocking, you must first gain access to Developer Options. + +> [!NOTE] +> OEM Unlocking allows you to unlock the bootloader, but it also disables Google's factory reset protection. + +On almost all Android phones you will need to go to "About Device" or similar to unlock the dev options, +in this menu look for "Build Number", +now tap the button several times until a confirmation toast/prompt appears. + +Now you can search for Developer options and from there enable OEM Unlocking. + +## Fastboot + +Now you need to restart your phone in Fastboot mode. +This varies from device to device, but can usually be done by pressing and holding the power and volume down button while the phone is switched off. +Another option is to use ADB: + +```sh +adb reboot bootloader +``` + +To unlock the bootloader, you have to run the following commands in fastboot mode. + +
Almost all modern devices +

+ +```sh +fastboot flashing unlock +``` + +

+
+ +
Older devices +

+ +```sh +fastboot oem unlock +``` + +

+
+ +## Troubleshooting + +> I cannot get into Fastboot. + +If you cannot boot into Fastboot using the volume buttons, try the ADB command above. +If the device still refuses to boot, your OEM may have restricted fastboot access, +in which case you'll need to consult device-specific guides. + +> I get `fastboot flashing unlock: FAILED (remote: Unrecognized command flashing unlock)` when I try to run the command. + +Make sure the device is in Fastboot mode, not FastbootD. FastbootD is for other things. + +If Fastboot still doesn't recognise your commands, +your OEM may have removed the correct unlock command, +in which case you'll need to consult device-specific guides. \ No newline at end of file