• GeneralPixel 6a
  • OEM Enabled but not able to unlock bootloader in fastboot options

I have OEM Enabled on my Pixel 6a. I downloaded the google driver that Graphene instructions told me to download. I then update the phone with the 'WinUSB driver'. Is that the right one? I think there must be a problem with the way I'm updating the driver. Then when I go to fastboot mode the unlock bootloader option still doesn't show up. What am I doing wrong?

  • de0u replied to this.

    Subliminal I am not a Windows user, so can't help directly. But in general it is easier to help if given very detailed info (e.g., the URL of the driver you downloaded), the last two steps that worked right (if any did), the exact step that went wrong, and details of the result (perhaps a screen shot). For GrapheneOS installations, say which install path (web or command line). If browser, indicate which one. More details will mean faster resolution.

    These days installation has a very high success rate, so it's likely you can soon be on your way.

    Thank you for the response. I honestly wouldn't know where to start as far as screenshots go. I am about to try to do the install on linux. Do you think for a somewhat competent user of linux that is would be easier to install GOS?

      Subliminal I have done three GrapheneOS installs so far.

      The first was in 2019 and was a bit of an adventure, but part of that was that I built from source. I don't think there was a web installer, so after some false starts I got the command-line install to work.

      The second was trying to use the web installer in Vanadium on a Pixel3a running GrapheneOS to install onto a Pixel 6a. That didn't work -- some step kept failing after a long time and eventually I gave up on it. I then tried with the web installer on Ubuntu, but not with a recommended browser, and that failed too.

      So I fell back to the command line again, and that worked.

      Whatever method you try, it is important to follow the directions very carefully. Anything specific in the directions (e.g., use Browser X or else Browser Y) is there because substituting something else has failed for a bunch of people (if the directions say "Chrome", that does not extend to other browsers that contain some amount of code from Chrome; it means exactly Chrome). Also, if some step doesn't work, stop and ask for help, because the steps are not skippable, and doing things out of order could potentially brick your device.

      I guess the short answer is that if a reasonably competent Linux user follows the directions carefully and exactly then it is very likely to work - for either the web installer or the command-line procedure. If the web installer works, it is much harder to make a mistake with it.

      Good luck! Follow the directions carefully and exactly!

        de0u I figured it out eventually with a lot of help in the matrix chat room. I switched to linux command line, which got it unlocked, then figured out I was using Firefox which isn't support, so I switched to brave browser... Then the cable I was using was working so I switched to the one which came in the box with my pixel but couldn't connect it to my laptop since it didn't have a usb-c port. So then someone told me to try another Android phone and connect USB c to USB c via both phones then follow web install instructions which worked flawless.

        In conclusion, If I had to do it again or I had to tell someone else to do it I would recommend android phone to pixel option with manufacturer phone USB c cable, then follow install instructions on web browser guide.