OEM Unlocking Greyed Out or Missing: Every Real Cause and Fix, by Brand

You opened Developer options, found OEM unlocking, and the switch will not move. Or the row is not there at all. Before you factory reset anything or download a "fixer" app, know this: that switch is not a button that is randomly stuck. It is a status display, and the phone is usually telling you exactly why it is locked out.

The short answer: OEM unlocking is greyed out because the phone is (1) already unlocked, (2) waiting for an online check of its carrier-sale status, (3) carrier-locked or restricted by the seller, (4) managed by an administrator, or (5) running firmware where the manufacturer never shipped the option. Four of those five have a legitimate fix or a clear explanation. The fifth, and some versions of the third, do not.¹²

Sources checked November 5, 2026. This is a documentation-based guide: DroidRooter did not test every phone mentioned, and manufacturer policy changes. Where a claim comes from press reporting or a community post instead of the manufacturer, the text says so.

Jump to: The five states · False alarms · Pixel · Samsung · Motorola · Xiaomi · Fairphone, OnePlus, Realme · Android versions · What not to try · Cost of unlocking · When it is impossible · Troubleshooting matrix · FAQ

Read the message under the toggle: the 60-second diagnosis

Android's own Settings source decides what you see. In the AOSP OemUnlockPreferenceController, the toggle is tied to a system service that only exists if the device was built with ro.oem_unlock_supported set to 1. If it is not, Settings logs that OEM unlock is unsupported and the option has nothing to control.¹² When the service does exist, the same controller disables the switch and writes a one-line summary beneath it for specific conditions.²³

The five states

Two details from the source matter in practice:

• State 4's text is shared. The same string, "Connect to the internet or contact your carrier", appears for a carrier disallow, for a device that simply has not been able to check in yet, and for a base DISALLOW_FACTORY_RESET restriction. You cannot tell a temporary wait from a permanent carrier lock by the words alone. AOSP's own code comment says as much: either another carrier restriction is in place, or the device has not yet been able to confirm which restrictions apply.²
• Skins can reword. These strings come from AOSP. Samsung, Xiaomi, Motorola and others can show different wording or no summary line at all.

A quick decision path

1. Is there an OEM unlocking row? No: go to state 1 and read the Samsung and brand sections.
2. Is the switch already on, or does the text say the bootloader is unlocked? Yes: you are already done, see false alarms.
3. Does the text mention carriers or the internet? Go online, update, wait, and follow the Pixel steps even if you do not own a Pixel; the logic is the same.
4. Is this a work, school or finance-managed phone? Then the administrator or lender controls it.
5. None of the above? Read the brand section and use the troubleshooting matrix.

Why the toggle exists at all

The toggle exists because Android is built to ship locked. AOSP says retail devices should ship with the bootloader locked, and that a device should refuse fastboot flashing unlock unless its unlock-ability value (get_unlock_ability) is 1. If it is 0, you have to boot to the home screen and enable Settings > System > Developer options > OEM unlocking. That setting then persists across reboots and factory data resets.¹ So the toggle is the manufacturer's consent step. If the manufacturer, carrier or administrator withholds consent, the unlock command is refused, and that is by design.

First, rule out the false alarms

These apply to every brand and fix a surprising share of "it's greyed out" reports.

Developer options must be on. On many phones: Settings > About phone, then tap Build number seven times. Fairphone's official guide says seven taps, and the LineageOS Motorola rhode page says at least seven. The number can vary by brand, so use what your phone's screen counts down.¹⁸¹⁴

Look at which way the grey switch is set. A switch that is on and greyed alongside a "bootloader is already unlocked" line is the finished state. A switch that is off and greyed, with a carrier, internet or admin line, is the blocked case.

"Bootloader already unlocked" is the success state. Owners asking why the switch is grey after they successfully unlocked are a recurring theme in forum threads that show up in search results. The AOSP string is literally "Bootloader is already unlocked".³ Samsung's Magisk documentation describes the same pattern: after the unlock, OEM unlocking exists but is greyed out.¹³

SIM unlock is not bootloader unlock. A carrier network unlock lets another carrier's SIM work. A bootloader unlock permits your own boot images. They are unrelated, which is why people report "my phone is network-unlocked but OEM unlocking is still grey". DroidRooter's bootloader unlock service page says the same: a carrier lock, a bootloader lock and an account lock are different problems.¹⁹

Work or school profiles. If a device is managed, a factory-reset restriction disables the toggle, and the OemLock service clears the allowed bit when an administrator sets that restriction.⁴ Check Settings > Accounts or your security settings for a management profile.

Check the actual lock state. Many phones show the lock state on their bootloader screen. AOSP defines the unlock-ability value but does not document one universal command to query it, so we do not give a fastboot command for it here.¹

Google Pixel: the most searched case

Pixels are where the "Connect to the internet or contact your carrier" text is most common, and where the cause is often temporary.

A new or reset Pixel: get online and wait

GrapheneOS's install guide states that on Pixel variants that can be sold carrier-locked, enabling OEM unlocking requires internet access so that the stock OS can check the sale state.⁵ One person who tested this on a Pixel 7 Pro bought from the Google Store in Canada found the switch stayed grey until the phone was online, and it freed up at about the time the phone contacted a Google provisioning host, after which Settings had to be closed and reopened. He is clear he does not know which network hosts are actually required, and it was a single device.⁷

What to try, in order:

1. Connect to Wi-Fi and stay connected.
2. Install any pending system update (look under Settings > System; the exact "System update" label varies by Android version).
3. Wait a few minutes, then close and reopen Settings and look again.
4. Restart once, and recheck.
5. If it is a very new phone, leave it online for a while before concluding anything.

Back up first if you are heading toward an unlock. AOSP says a device should factory reset when it is unlocked; the toggle itself does not wipe anything.¹

Pixel 6a: the dated exception

GrapheneOS notes that the Pixel 6a's original factory OS will not enable OEM unlocking. You need the June 2022 update or later, installed through a normal OTA update, followed by a factory reset. This is a model-specific, dated note, not a general rule.⁵

Carrier-locked Pixels, including Verizon

This is the case where Settings cannot help. GrapheneOS says carrier variants have a non-zero carrier ID stored in the persist partition that disables carrier and bootloader unlocking. It adds that the carrier may be able to remotely lift this, but its support staff may not know the option exists. GrapheneOS's FAQ says carrier locks are primarily an issue with US carriers and that the hardware is the same either way, so their advice is to prefer a carrier-agnostic purchase.⁵⁶

On Verizon specifically, forum users say the toggle never frees up. That is community consensus, not a Verizon statement, so check with the carrier rather than treating it as official policy.⁸

A Pixel Community reply on a Pixel 6 thread said such a phone was "most likely sold as a carrier specific phone" and that in theory the carrier can unlock it, but that the poster had never seen a report of it happening. It is one community reply, and that Pixel 6 was a demo unit, which is an unusual case.⁹

"I bought it unlocked" and it is still grey

This shows up with renewed or third-party-sold units. In a GrapheneOS forum thread about a Pixel 10 Pro, the owner tried three times with two factory resets, still got "Connect to the internet or contact your carrier", wondered if he had received a permanently locked unit, and said he planned to return it. Replies in the thread say carrier-locked units have no workaround, and suggested a few things users reportedly tried: leaving an Android beta programme, or using a VPN or a different Wi-Fi network.⁸ Those are user tips, not documented fixes.

If you are buying a used Pixel to unlock, ask the seller for the original carrier or store, and test the toggle as soon as it arrives, while the return window is still open. "Unlocked for any SIM" and "bootloader can be unlocked" are not the same promise.

Samsung Galaxy: where the answer changed in 2025

One UI 8 and later: the toggle is gone on affected firmware

In July 2025, SamMobile reported that One UI 8 removes the bootloader unlock option. Its evidence was the S25 One UI 8 beta code plus the stable Galaxy Z Fold7 and Z Flip7 builds, and it said this holds regardless of region. It also noted the US models had long lacked the option. Samsung did not issue an explanation in that reporting.¹⁰ A follow-up said the change is "likely due to" the EU Radio Equipment Directive 2014/53/EU, whose cybersecurity requirements it said were set to be enforced from August 1. That is the publication's inference, not a Samsung statement.¹¹

Treat this as reported, not confirmed by Samsung, and based on one outlet. The practical meaning: if you are on One UI 8 or later and the OEM unlocking row is absent, that is state 1. There is nothing to toggle, no setting to flip back, and no safe fix we can offer. Be wary of anyone who sells one.

One counter-example: SamMobile also relayed a user report that the Galaxy XR headset still shows the toggle and that a user completed the unlock, "at least for now". That is one user, relayed by one outlet, about a headset.¹²

Phones still on One UI 7 or earlier

On those versions, "missing" was often about the market or a remote lock, and the Magisk documentation gives a way to check. Magisk says to enable Maintenance Mode first (under Device Care), then boot into Download mode.¹³

Two cautions. First, "Prenormal and 168 hours" is Magisk's wording of what should happen, not a published Samsung policy. Second, the widely repeated "wait 7 days" advice is community lore; we could not find a documented Samsung source tying a 7-day figure to the toggle. Magisk says Samsung unlock wipes data, that it is done by long-pressing Volume Up in Download mode, and that after the unlock the OEM unlocking row should exist and be greyed out. A greyed row after unlocking, combined with a non-locked KG state, is the expected outcome.¹³

KG Active or Locked is not a bug. It usually means the device is financed, insured or reported lost or stolen. If that is your own paid-off phone, contact the carrier, retailer or insurer that placed the lock. If it is not yours, stop. Do not attempt to remove a lock from a phone you do not own.

For the warranty side of a Samsung unlock, see our Samsung Knox and warranty guide. For model specifics, see the Galaxy rooting guide and note that guides written before One UI 8 may describe a toggle your phone no longer has.

Samsung Auto Blocker

The top results for this problem repeat that Samsung's Auto Blocker can grey out developer settings. We could only find that claim in videos and not in any Samsung documentation, so we are not asserting it. If you run into it, test it on your own phone rather than assuming.

Motorola

For newer Motorola phones, the LineageOS install page for the Motorola rhode device says that some newer Motorola devices must be connected to the internet for up to seven days before the OEM unlock toggle can be switched.¹⁴ That is one device page from one project, so do not assume it holds for every Motorola, but it is the one documented figure we found.

Motorola's own unlock page says that once you get the unlock code, the warranty no longer covers the device, that unlocking does not change a subsidy lock, and that a carrier may prohibit the use of unlocked devices.¹⁵ Its device list is stale, so use it for the policy text and check Motorola's live portal for whether your exact model is supported. We could not verify carrier-by-carrier eligibility; carrier-sold Motorolas may be treated differently.

What to do: stay on Wi-Fi, leave the phone online for several days if it is new, update it, and look again. See the Motorola rooting guide for what comes after.

Xiaomi, Redmi and POCO: a different kind of "grey"

On Xiaomi phones the switch is often available, and the real obstacle is the Mi Unlock tool. The official Mi Unlock page describes downloading the tool on a PC, signing in with a Mi Account, powering the phone off, entering Fastboot with Volume Down and Power, and clicking unlock. It also warns that unlocking disables Find device and some high-security services. That page carries a 2019 footer, so treat it as an outline, not current policy. It does not state wait times.¹⁶

Forum posts mention waiting periods of 72, 168 or 360 hours. Those come from forums and are account and region specific, not Xiaomi policy. Trust the number the Mi Unlock tool shows you, and do not sign out of the Mi Account during the wait.

For China, XimiTime reported in February 2025 that Xiaomi added a rule for China only under which users with an infraction in the past 180 days can no longer unlock. XimiTime states the change applies to China only, so do not assume it applies to global ROMs.¹⁷ Do not install "bypass" tools: they are not an official route, and an unofficial tool on a locked phone can create a recovery problem. See our Xiaomi rooting guide and POCO X6 Pro guide.

Fairphone, OnePlus, Realme and others

Fairphone has the clearest official path. Its support article covers all models except the FP2: enable Settings > System > Developer options > OEM unlocking, wait for verification, and if the toggle fails check your internet connection and update the software. Then fastboot flashing unlock followed by fastboot flashing unlock_critical, each of which wipes the data. Re-locking with a non-Fairphone OS or an older patch level can leave the phone unable to boot, so do not re-lock unless you are back on official software.¹⁸

OnePlus. Our OnePlus 12/13 guide says T-Mobile US variants have OEM unlock disabled, and the LineageOS wiki lists the 8T (T-Mobile) as a separate device. We could not retrieve OnePlus's official unlock documentation, so we state only that carrier variants differ from the global models: verify with your exact model.

Realme and Oppo. Our Realme GT 6 guide mentions an approval step called In-Depth Test. We did not re-verify its current process or timing for this article, so check the vendor's current instructions for your exact model.

We have no sourced statements for Honor, Vivo or Sony, so we make no claims for them.

Android 14, 15, 16 and 17: what actually changed

Search results are full of "Android 16 fix" advice. The honest summary is short.

What differs between phones is mostly manufacturer and carrier policy, not the Android version number. Be skeptical of any guide that gives a different fix for each version without citing a source.

What we could not verify

• Whether Samsung Auto Blocker affects the toggle.
• The status of One UI 8.5 and later, and of Android 17 on Pixel.
• Verizon's own stated policy on unlocking Pixels.
• Official OnePlus unlock steps, Realme and Oppo process details, Honor, Vivo and Sony specifics.
• Xiaomi's official wait times by region.
• Motorola carrier-model eligibility.
• Warranty effects for Pixel beyond what each manufacturer states.

What not to try

Most "fixes" advertised for this problem either cannot work or put your data and device at risk.

• Universal unlocker APKs and "OEM unlock enabler" tools. The setting is a policy decision made in the firmware and by carriers. An app on the phone cannot override it, and an unvetted APK is a risk in its own right.
• Paid services that promise to flip the toggle remotely. If a carrier, finance company or administrator controls it, only they can release it. Never pay to remove a lock from a phone you do not own.
• Editing build.prop. AOSP says ro.oem_unlock_supported is set at build time, so editing files on a running phone does not change what the firmware supports.¹
• Guessing fastboot oem commands. AOSP says a device should refuse fastboot flashing unlock unless unlock-ability is 1.¹ Vendor-specific commands are undocumented, often disabled and can leave a phone unbootable.
• Flashing random firmware. Especially on Samsung with KG or RMM active, this can turn a locked phone into a bricked one.
• Changing the system date to skip a wait. We found no documentation that supports it, so we do not recommend it.
• Signing out of the Mi Account on Xiaomi during a wait.

What unlocking really costs

• Data. The toggle itself does not erase anything. The unlock does. AOSP says the device should reset to factory state on unlock, Magisk says Samsung unlock wipes the phone, and Fairphone says each unlock step wipes it.¹¹³¹⁸ Back up first.
• Warranty. Motorola says its warranty no longer covers the device once you obtain the unlock code.¹⁵ We have not verified the position for Pixel, and Samsung's Knox flag is covered in our Knox guide. Do not assume your warranty survives.
• Re-locking. Fairphone warns that re-locking with a non-Fairphone OS or an older patch level can stop the phone booting.¹⁸
• Security. An unlocked bootloader removes protections the device normally enforces, and some banking or payment apps may refuse to run. See our rooting risks guide before you decide.

When it is impossible, and what to do instead

Stop trying if any of these applies. None of them is fixable from Settings:

• A carrier-locked Pixel where the carrier will not release it (reported for Verizon units).
• A Galaxy on One UI 8 or later with no toggle (as reported).
• A Galaxy that shows no OEM Lock value in Download mode (Magisk calls this probably not unlockable).
• A Galaxy with KG or RMM Active or Locked, which is a remote lock by an operator or insurer.
• A work, school or finance-managed phone.
• A counterfeit or misdescribed unit.
• A China-market Xiaomi where the official policy is restrictive.

Realistic options:

1. Return it while the return window is open, and buy a variant sold unlocked by the manufacturer.
2. Ask the owner of the lock. That is the carrier, lender, insurer or employer.
3. Stay on stock and use what does not need an unlock. See Should I root my Android? for the honest trade-offs.
4. Check the Rootability Checker for your exact variant. Some phones have other routes, and the rooting guide explains the options.

Troubleshooting matrix

Not sure which state you are in? Use the Rootability Checker or send the exact model, region, carrier and the text under the toggle through our bootloader unlock review.

Before you ask anyone for help

Have these ready:

1. The exact model number from Settings > About phone.
2. Country, carrier or store where you bought it.
3. The software version and security patch.
4. The exact grey text under the toggle, or a note that the row is missing.
5. Whether the toggle ever worked.
6. Proof you own the phone or are authorized to administer it.

Never send passwords, one-time codes or recovery phrases.

The bottom line

A greyed-out OEM unlocking switch is almost always a message, not a malfunction. Read the line under it. If the phone is unlocked already, you are done. If it is waiting on an online check, give it a network and time. If a carrier, a lender, an administrator or the manufacturer's firmware has taken the choice away, no setting, app or paid trick will return it, and the right move is to ask the owner of that lock or choose a different phone.

If you cannot tell which case you are in, DroidRooter can review your exact variant before you plan an unlock. We need the model, region, carrier and the grey text, plus confirmation that you own or administer the device, and never any passwords or codes. We only discuss official paths: we cannot unlock carrier-locked, remotely locked or administrator-managed phones, and we do not promise results. Start with the Rootability Checker, then the bootloader unlock review. If an unlock is legitimately possible and you want the next step, see our Android rooting service and Magisk installation pages.

Sources and project documentation