Android Bootloader Unlocking vs Carrier Unlocking: What ADB and Fastboot Can Actually Do

Alex — Thu, 08 Oct 2026 08:26:32 +0000

If you've spent time working with Android devices, you've probably come across terms like carrier unlock, OEM unlocking, and bootloader unlock.

They sound similar, but they serve completely different purposes.

This distinction is particularly important for Google Pixel devices, where a phone can be network-unlocked but still have a locked bootloader.

Let's break down what each term means, how ADB and Fastboot fit into the picture, and what these tools can and cannot do.

1. What is carrier unlocking?

Carrier unlocking, also known as network or SIM unlocking, removes restrictions that prevent a device from accepting SIM cards or eSIMs from other compatible carriers.

For example, a carrier-locked Google Pixel might work with one mobile network but reject another carrier's SIM.

The unlocking process typically depends on the original carrier's eligibility requirements, including factors such as payment status, account standing, and device-specific policies.

Important: Carrier unlocking does not automatically enable OEM unlocking or unlock the bootloader.

2. What is OEM unlocking?

OEM unlocking is a setting found under Android's Developer Options on supported devices.

Enabling this setting allows a subsequent bootloader unlocking operation, provided the device supports it and other applicable restrictions are satisfied.

However, simply enabling OEM unlocking does not unlock the bootloader.

On some Android devices, the OEM unlocking option may be greyed out because of carrier restrictions, device management policies, or manufacturer-specific limitations.

A greyed-out OEM unlocking toggle does not necessarily mean the phone is network-locked.

3. What does ADB actually do?

Android Debug Bridge (ADB) is a command-line tool that allows developers to communicate with Android devices.

It is commonly used for debugging, inspecting device information, installing applications, and accessing supported system interfaces.

Here are a few useful commands:

adb devices
adb shell getprop ro.product.model
adb reboot bootloader

The first command lists connected devices that ADB can detect.

The second retrieves the device's reported model.

The third reboots the device into bootloader mode, where supported.

ADB requires an appropriate connection and authorization for normal device-debugging operations.

ADB cannot directly remove a carrier's network lock.

4. What can Fastboot actually do?

Fastboot is a command-line tool used to communicate with compatible Android devices in bootloader mode.

Developers use it for tasks such as inspecting device information and, on supported devices, flashing firmware or performing bootloader operations.

For example:

fastboot devices
fastboot getvar product

These commands can help identify a connected device and retrieve its product information when supported.

On devices that permit bootloader unlocking, Fastboot also supports commands such as:

fastboot flashing unlock

Warning: Do not run the unlocking command casually. On supported devices, unlocking normally triggers a factory reset, erases user data, and changes the device's security state. The operation requires device authorization and may be prohibited by the manufacturer or carrier.

An unlocked bootloader also does not mean the phone is carrier-unlocked.

Fastboot is not a universal network-unlocking solution.

5. Carrier unlocking vs OEM unlocking vs bootloader unlocking

Feature	Carrier Unlock	OEM Unlocking	Bootloader Unlock
Main purpose	Use compatible mobile networks	Permit a bootloader unlock operation	Enable supported low-level modifications
Removes SIM restrictions	Yes	No	No
Found in Developer Options	Usually no	Yes	No
Uses Fastboot	Usually no	No	Often
Erases user data	Normally no	No	Usually yes
Changes bootloader lock state	No	No	Yes

The key takeaway is that network unlocking and bootloader unlocking operate independently.

One does not automatically provide the other.

6. Why this matters for Google Pixel devices

Consider a Google Pixel purchased through a mobile carrier.

The carrier may approve a network unlock, allowing the device to accept SIM cards from other compatible networks.

However, the device might still have restrictions preventing bootloader unlocking.

Similarly, a Pixel with an unlocked bootloader is not necessarily unlocked for use with every mobile carrier.

The exact behavior depends on the device model, carrier variant, management policies, and software configuration.

For a more Pixel-specific explanation, I've also written a guide on Google Pixel Network Unlock vs OEM Unlock at GPixel.pro, a website I work on.

The guide focuses on understanding the differences between network restrictions and Android's bootloader security mechanisms.

7. Common misconceptions

"ADB can remove any carrier lock."

No. ADB is primarily a debugging and device communication interface. It is not a universal carrier-unlocking tool.

"Enabling OEM unlocking means the bootloader is unlocked."

No. Enabling OEM unlocking only permits a subsequent unlocking operation on supported devices.

"A carrier-unlocked Pixel always supports bootloader unlocking."

Not necessarily. Carrier unlocking and bootloader unlocking are separate processes governed by different restrictions.

"Fastboot can unlock every Android device."

No. Fastboot functionality depends on the manufacturer, device model, bootloader implementation, and applicable restrictions.

"Bootloader unlocking removes SIM restrictions."

No. Unlocking the bootloader does not normally affect carrier or SIM restrictions.

8. What should you check before attempting an unlock?

Before making changes to an Android device, it's worth checking a few things:

Identify the exact device model. Different regional and carrier variants can behave differently.
Determine the type of restriction. A SIM/network lock is different from a bootloader restriction.
Check official carrier policies. Carrier unlocking eligibility varies by provider.
Review manufacturer documentation. Bootloader unlocking support and procedures are device-specific.
Back up important data. Bootloader unlocking normally erases user data.
Understand the security implications. An unlocked bootloader can weaken protections against unauthorized system modifications.

Avoid relying on generic unlocking instructions without verifying that they apply to your particular device.

Final thoughts

Carrier unlocking, OEM unlocking, and bootloader unlocking are often discussed together, but they solve different problems.

ADB and Fastboot are valuable tools for Android development and troubleshooting, yet neither should be confused with a carrier's network-unlocking process.

Understanding these differences can save time, prevent unnecessary troubleshooting, and reduce the risk of making unwanted changes to your device.

If you're working with Google Pixel devices, always confirm the model, carrier restrictions, and bootloader support before attempting any unlocking operation.

Have you ever encountered a Pixel that was carrier-unlocked but still had OEM unlocking disabled? I'd be interested to hear what model and carrier variant you were using.

DEV Community: Alex