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.

    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!

        a month later

        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.

          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 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.

              @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.

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

                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.