We've published experimental releases of GrapheneOS for the Pixel 6a with full support for the hardware. Our web installer has also been extended with support for the Pixel 6a. There are currently no known issues with the release that's currently in all 3 release channels (Stable, Beta and Alpha) for the Pixel 6a. However, it hasn't been tested much and there are likely still issues that need to be reported to us and resolved. The best place to report issues at this point is in the #testing:grapheneos.org chat room on Matrix rather than the issue tracker. Issues can be opened once they're discussed there if there isn't a quick fix.

OEM unlocking toggle in the stock OS is currently buggy and we've provided instructions on how to work around the issue in both the CLI and web installation guides. This currently makes installation much less convenient, especially for web installation. It will be much better once the stock OS has an over-the-air update available for most users. At the moment, the update is gated as only being available to users on Japanese carriers or Verizon. The workaround for the issue is updating to the newer stock OS release and then doing a factory reset. We've confirmed that this works on the generic OS release currently gated as a Verizon only release. It's likely only available to Verizon users due to not yet going through the standard 4 weeks of testing and Google's close relationship with Verizon for Pixels likely allowed them to ship it early, although the details aren't known.

23 days later

6a looks bricked?
Here''s the steps I took using Pixel6a+Debian11+Chromium Browser

  1. Updated android to v12 dated June 22
    2 Successfully unlocked OEM on pixel
  2. sudo apt install android-sdk-platform-tools-common
  3. Successfully booted the bootloader interface
  4. Connected Pixel to PC
  5. Used web interface to unlock bootloader
  6. Used web interface to successfully download graphene factory images
  7. Used web interface "Flash release". After several minutes of what appeared to be successful operations, got an error message on web interface "Error: failed to execute 'claimInterface' on 'USBDevice': unable to claim interface".
    9 Pixel states "your device is corrupt......" press power button to continue: then "the bootloader is unlocked........." Press power button to resume ------> gives white screen with google logo. Pressing the power button for at least a minute bring back the bootloader menu
    10 Tried flashing again but Debian 11 cannot detect the pixel.

I should probably raise this as a standalone issue?

Any help would be gratefully received

    Hello,
    I'm sorry, I'm not going to answer your question "directly", but maybe you can try the command line procedure:
    https://grapheneos.org/install/cli
    The steps are really well detailed and you would probably have a more recent version of fastboot than with the android-sdk-platform-tools-common package: https://grapheneos.org/install/cli#standalone-platform-tools
    You could then check the presence of the phone via "fastboot devices".
    I hope this will help you.

    molly Don't worry, it's not bricked. You can just start over and try again.

    "Unable to claim interface" means another program is interfering and is connected to the phone in some way. Make sure you only have one tab of the web installer open and that you do have adb running in the background. Rebooting can help ensure that.

    Just FYI, the Matrix room is probably a better place to get help with installation since it's more real-time.