Should I enable OEM unlocking before system updates as a safety measure?

deofol

My daughter's phone is now stuck in a bootloop as described here: https://9to5google.com/2026/04/10/google-pixel-bootloop-issue-march-update

Until Google releases a fix, her phone is unusable. If OEM unlocking had been enabled, I could have probably installed GrapheneOS.

This makes me wonder, Is it wise to enable OEM unlocking before applying updates, then disable it once the upgrade has finished? This would provide a recovery option if an update causes bootloop or similar issues.

Even with GrapheneOS installed on my own phone, I assume I'm not immune to these types of update problems. Would having OEM unlocking enabled help in this scenario?

Upstate1618

You can always factory reset your phone whether or not the option is enabled.

deofol Until Google releases a fix, her phone is unusable.

Not true.

ceramics

Could also defer updating for a few days and see if there are reported issues before updating.

I do feel my update anxiety would be much lower if we had a consistent backup solution.

deofol Even with GrapheneOS installed on my own phone, I assume I'm not immune to these types of update problems.

I think unless they start vibe coding we're probably ok.

legreteco

OEM Unlocking would have helped, but I don't know if the trade offs are worth it.

secrec

legreteco I don't know if the trade offs are worth it.

What "trade-offs"? There's no security risk to enabling unlocking -- when it is actually unlocked, the phone gets factory reset, no way around this.

Vincent96

Be aware changing these options may factory reset the phone.

de0u

Vincent96 Be aware changing these options may factory reset the phone.

I am unaware of reports that enabling OEM unlocking can result in a factory reset. Is information available that would support that claim?

Murcielago

de0u

I am unaware of reports that enabling OEM unlocking can result in a factory reset. Is information available that would support that claim?

I’m not speaking for Vincent96 , of course, but it sounds like he may be referring to unlock the bootloader.

If i understand it correctly, OEM unlocking (Settings> System> Developer options> OEM unlocking) sets a flag (get_unlock_ability = 1) and is a prerequisite for unlocking the bootloader.

Bootloader unlocking (not OEM unlocking) performs a factory data reset and wipes all data.

sources:
https://source.android.com/docs/core/architecture/bootloader/locking_unlocking
https://grapheneos.org/install/web#enabling-oem-unlocking
https://grapheneos.org/install/web#unlocking-the-bootloader

Murcielago

deofol

I am talking about OEM unlocking. Since this was disabled before the update, I'm unable to unlock the bootloader and install GrapheneOS.

Thanks for your update and explanation.

But I was referring to Vincent96 warning that OEM unlocking could factory reset a phone and de0u answer to that.

legreteco

secrec your phone is easy to steal + what if there are exploits abusing that functionality?

schklom

secrec Some apps (I think mostly banking) refuse to run if they detect that Developer options are enabled. Also, like all features, OEM Unlock and Developer Options may be vectors of attack. Not enabling them is safer, even if only a little.
The tradeoff may be worth it, but it is a tradeoff

deofol

Upstate1618 I can factory reset the phone from the recovery menu but, it's still going into a boot loop. I read somewhere about this might be a corrupt a/b partition. I can even reflash an image using the pixel recovery tool but, I can only flash it using the latest stock version which caused the issue in the first place, or do you know something else?

deofol

Murcielago I am talking about OEM unlocking. Since this was disabled before the update, I'm unable to unlock the bootloader and install GrapheneOS.

My son and I have a Pixel 8 and a Pixel 9 running GrapheneOS, and we are both using the latest updates without issue. Looking at the recent stock issue, any phone can be impacted. If we are eventually hit with something like this, I don't think we would be able to recover. We might be able to flash back to stock using the Pixel Repair Tool, but we haven't tried that yet.

FYI: Using the pixel repair tool allows you to flash the current or newer image even with a locked bootloader and OEM unlocking disabled.

Upstate1618

If you really worry about a bootloop that can't be fixed by factory reset, you can leave the OEM unlocking enabled. Please note gos recommends users to disable the option as defense in depth. The option is mainly used for factory reset protection on stock. It also makes sure bootloader unlocking clears user data. There was an exploit where bootloader unlocking does retain user data and thus makes the phone vulnerable to forensics.

raccoondad

secrec risk vector.

Dev options are def a risk vector and GOS recommends disabling OEM unlocking due to that

Johnnyloans

Guys, the original question is this:

Should I enable OEM unlocking before system updates as a safety measure?

It is a temporary, short amount of time to toggle a switch, update, then toggle it back.
We aren't leaving dev options on or walking around bad neighborhoods while our phone updates to get it stolen. Toggling a security feature for a few minutes then auditor runs afterwards in our home isn't too wild.

This is similar to the people that disable their screen unlock methods before updates.

OEM unlocking causing a factory reset is another story, if that exists. Evidence of this was asked for in this thread.