Why "OEM Unlocking" Is Greyed Out: Manufacturer-Specific Requirements Before Fastboot Will Unlock

Before fastboot flashing unlock or fastboot oem unlock will do anything, the OEM unlocking toggle in Developer Options has to be switched on, and for a surprising number of people that toggle is simply greyed out and can't be tapped at all. This isn't a bug in most cases — it's a manufacturer-imposed precondition, and which precondition applies depends entirely on the brand, not on anything the command line can work around.

The Usual Suspects

• No internet connection: the toggle requires the phone to check in with the manufacturer's server before it becomes available; a phone in airplane mode or without a SIM and Wi-Fi both connected simultaneously often can't complete this check.
• Account not signed in or not old enough: Xiaomi and several other brands require a manufacturer account signed in on the device for a minimum number of days before unlocking is permitted, specifically to deter theft.
• Carrier-locked or carrier-purchased phone: phones sold directly through a carrier, especially in the US, frequently have OEM unlocking permanently disabled at the firmware level regardless of account status, as a term of the carrier's subsidy or financing agreement.
• Enterprise or MDM-managed device: a phone enrolled in a company's mobile device management profile has this locked out by policy, and no amount of account tenure changes that.
• Corporate or education Google Workspace account as primary account: some managed Google account types block the toggle the same way a carrier or MDM profile does.

Brand-Specific Waiting Periods and Approval

Xiaomi's unlock process is the most well-known example of a formal waiting period, requiring account sign-in for a set number of days before the unlock tool's approval request will succeed, with the exact wait sometimes extended further based on the account's usage history. Other brands take a simpler approach: once the toggle is available and switched on, fastboot flashing unlock works immediately with just an on-device confirmation, no account or waiting period involved. There's no universal rule across brands — the only reliable way to know which category a given phone falls into is checking that manufacturer's own developer or unlock documentation rather than assuming the process from a different brand transfers over.

Confirming the Actual Blocker

1. Verify the phone has an active internet connection through both Wi-Fi and, if available, a SIM, then wait a few minutes and recheck the toggle before assuming a harder lock is in place.
2. Check whether the phone was purchased directly from a carrier versus unlocked/retail — carrier billing records or the box's model number suffix often indicate this.
3. Look for a Work Profile or a device administrator app under Settings > Security, which indicates MDM enrollment even if it wasn't set up intentionally (some employer or school-provided phones enroll automatically).
4. For brands with an account-based waiting period, confirm the account has actually been signed in continuously for the required window, not just created recently on a different device.

Once the Toggle Is Available

With OEM unlocking switched on in Developer Options, the actual unlock command and driver requirements are the same regardless of which precondition delayed getting there — see the general fastboot OEM unlock guide for the command-line steps, or the broader bootloader unlock walkthrough for what changes on the phone afterward, including the factory reset every unlock triggers.

When the Toggle Is Missing Entirely, Not Just Greyed Out

A greyed-out toggle that's visible but unavailable is different from OEM unlocking not appearing in Developer Options at all, and the second case is a much harder wall. Some carrier variants and specific regional models remove the option from the build entirely rather than merely gating it behind a condition, meaning no amount of account tenure, connectivity, or waiting resolves it — the capability was compiled out of that specific firmware. Comparing the exact model number against that manufacturer's own list of unlockable versus locked variants (commonly split between a "Global" or unlocked SKU and a carrier-specific one sharing an almost identical name) clarifies which situation actually applies before more time goes into troubleshooting a toggle that was never going to appear.

Why This Gate Exists at All

The waiting periods, account bindings, and connectivity checks all serve the same underlying goal: making a stolen phone significantly harder to unlock and resell for parts or firmware modification, since a thief typically can't wait out a multi-day account-tenure requirement or satisfy a connectivity check tied to the original owner's credentials. Carrier-level locks serve a related but separate purpose, protecting the subsidy or installment financing arrangement rather than security specifically. Understanding which of the two motivations applies to a given block helps set expectations for whether it's something that clears with time and patience, or something that simply won't budge regardless of how the toggle is approached.

Related: Fastboot Oem Unlock Guide · Re-Locking the Bootloader After Root or a Custom ROM: What Breaks and How to Recover