Fastboot Device state: locked (unlockable)

imreallystuck

Hi everyone, I need of some help.

I have just bought a brand new pixel 8 pro.

I have enabled oem unlocking.

Upon booting into the bootloader interface next to device state it says locked (in green) BUT next to that it states (unlockable) in red.

I have never seen this before and I am totally stumped. I have enabled and re enabled the oem a few times incase that was the problem. I have both tried with a fully upto date device and after a factory reset on a totally new setup and it is still the same.

What am I missing?

Any help is very much appreciated.

Thank you

argante

imreallystuck

You need to install android platform-tools (for fastboot tool). Then you do everything as in the GOS installation manual, but when you get to the stage of unlocking the bootloader, you need to connect the phone to the computer/laptop and execute the following command (terminal on Linux/Mac or Power Shell on Windows):

fastboot flashing unlock

Next, you can go to the GOS installation page. Skip the unlocking stage and go straight to downloading the image and flashing.

spring-onion

Good day!

The OEM unlock toggle is what enables you to unlock the bootloader, but it doesn't do so on its own. That is a separate action, click the button on the web installer and accept the command on device.

imreallystuck

spring-onion Thank you. Sorted now. I have just not seen it state "unlockable" before and it was throwing up errors when I did click the button via the installer!

strikersignal

imreallystuck how did you manage to unlock it? i have the same problem on my pixel.

spring-onion

strikersignal What's not working?

SpokenFor

I am receiving this same message. I enabled OEM unlocking. My device (Pixel 8) says "locked" in green "(unlockable)" in red, right next to it. I went through the web install process and it seemed to do its thing. On locking the bootloader I am receiving the same message: "locked" in green "(unlocked)" in red. What does this mean? How do I resolve this? Does it need to be resolved? Thank you.

spring-onion

SpokenFor You need to disable OEM unlocking in the developer settings now. Then you're done.

SpokenFor

spring-onion I apologize for my delayed response. I did not realize this page did not refresh itself.

Yes. I disabled the OEM unlocking after the install per the web install directions. I did not receive any errors during the installation. Everything seems to be working. This is my first time installing GrapheneOS and I am not tech savvy at all. I just wasn't sure if it was a problem that I had the "unlockable" message in red following the "locked" message in green. Did it prevent GrapheneOS from installing as it should? Or, since the install seems to be functioning, everything is fine?
Thank you.

spring-onion

@SpokenFor It sounds like everything went smoothly. You can now verify the installation by comparing the verified boot key hash you see when your phone is starting to the one that's on the website and setup auditor.

Think of it this way: When you enabled OEM unlocking in the developer settings, you were given a key. You can unlock a door with that key, but that's a separate action and doesn't happen automatically. That's what it's telling you, the door is locked right now (as it should be) but you could open it again if you wish. Now if you disable OEM unlocking you put the key away so you're not carrying it with you at all times.

SpokenFor

spring-onion
I have finally figured out where to find the boot key hash on my phone to verify. I must have missed that screen when I rebooted. Thank you all so much for your help. I'm looking forward to using this OS. Thanks again.

spring-onion

@argante USB debugging isn't part of the install instructions, and you shouldn't have to switch to the command line at any point.

helpos

Hello! I think I have the same issue here. The device state shows as locked (in green), followed by unlockable (in red).
I am using a Chromebook, and I have no idea how to solve this, as most info is explained using Windows. The first challenge I've found is that when I click "unlock the bootloader" on the web installer, I only see these options on the Pixel 9: start, restart bootloader, recovery mode, rescue mode, barcode, and power off. So, I cannot accept the command on the device because it is not available.

Any help will be greatly appreciated.

Thank you

spring-onion

@helpos When you hit unlock bootloader your browser should prompt you to establish the connection with your pixel in a pop-up window. Once that's done the available options on the phone change, you're moved onto a different screen that warns you about the dangers of unlocking the bootloader, etc. Please describe exactly what happens on your end. Use the usb-c cable that came with your pixel if you aren't already.

helpos

spring-onion My apologies for the delayed response. I’m not very experienced with tech, and this is my first time installing GrapheneOS. From what I can tell, the issue isn’t the “unlockable” device status, but rather this recurring error message: “timeout of 10000 ms exceeded.”

So far, I have tried all the usual troubleshooting steps:

Using different USB cables (including the original one that came with my phone, which is brand new, and a high-quality replacement)
Trying different USB ports on my Chromebook (which is new, so they should work fine)
Confirming that Android USB drivers aren’t needed since the Chromebook is compatible by default
Testing with different browsers, including Brave (with shields down) and Google Chrome
Ensuring my Pixel is always in fastboot mode with OEM unlocking enabled (I even toggled USB debugging off)

I’m really frustrated and at a loss here—I just can’t figure out what might be wrong. Is there anything I might be missing? Thank you very much for your help!

Unknown-Phallus

spring-onion Your Onion salubrious.

n3t_admin

helpos from experience, I'd suggest just trying a different host device. Can be pretty much any half way decent computer, I assume you have someone in your friends&family circle with a computer (or an Android phone). Sometimes that's just a lot easier than troubleshooting from a distance.

helpos

Now I have a bigger problem :(

I kept trying, and eventually I managed to unlock the bootloader and get the factory images. But when I tried to flash the release, I got this error:

"failed to execute 'transferOut' on USBDevice: A transfer error has occurred"

Now my phone seems corrupted (that message was displayed), and it’s stuck on the Google logo. I feel like I just flushed a few hundred dollars down the toilet. Please, somebody tell me this can still be fixed.

n3t_admin

helpos it's close to impossible to brick a modern Android device. You just need to get back to the bootloader screen with the key combination and try again (skipping the bootloader unlock step this time).

de0u

helpos Please, somebody tell me this can still be fixed.

It is nearly certain.

But at this point the best move really may be trying the installation from something other than your Chromebook. Maybe use a friend's device.

As long as the boot key hash is correct at the end of the process it doesn't matter which device was used to do the installation.

helpos

de0u Ok, thank you so much! I’ll try to find another device and give it another shot. But before I take the leap of faith, I have one question:

When I was trying to get back into the bootloader screen, I noticed that my Pixel might have done a factory reset on its own (I now have to select language, time zone, etc. — just like when I first turned it on). The bootloader is still unlocked, though.

Is this normal? Does it mean I have to start completely from scratch (except the unlocking part), or should I be fine just hitting “Flash Release” on a new device?

Any advice would be greatly appreciated :)

n3t_admin

helpos you just need to boot into the bootloader and proceed with the flashing in the web installer, no other steps have to be repeated.

de0u

helpos When I was trying to get back into the bootloader screen, I noticed that my Pixel might have done a factory reset on its own (I now have to select language, time zone, etc. — just like when I first turned it on).

Unlocking the bootloader wipes the user data partition. Also, locking the bootloader wipes the user data partition.

helpos Does it mean I have to start completely from scratch (except the unlocking part), or should I be fine just hitting “Flash Release” on a new device?

If launch the web installer from some device other than the Chromebook, you will need to do basically the entire process from the start. In particular, you will need to download a release, and you will need to put the device into fastboot mode.

Basically, always start from the beginning ("a very good place to start").