Bootloader Stuck and Remains Unlock - Failed Installation

A2B

Hello, I bought a brand new unlocked Pixel 6a. The OEM unlocking was available and proceed the installation with the Web Installer with the stock cable, all smooth until 'Flash release' step with this error:

"Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface."

I tried two other cables c-a with same error.
Switch to LCI and it keeps saying:

< Waiting for any device >

Switch cables again with no change in the message.
I did 'Restart bootloader' and try again and nothing change. Neither the web or CLI.
No option or chance to 'Lock the bootloader' I tried it all I could.
Select 'power off' and started in Bootloader (still Unlocked) and tried again but nothing. It wont connect-detect the phone. I'm not able to lock the Bootloader in any way.
When start the phone, Google starts again. This time with a warning message at booting saying:

The bootloader is unlocked and software Integrity cannot
be guaranteed. Any data stored on the device may be
available to attackers. Do not store any sensitive data on
the device.

Visit this link on another device:
g.co/ABH

After the previous warning, starts in Google OS and the OEM it's greyed.

I Deleted my pin and any security.
Factory Reset and nothing changed.

So:

Non of the web or CLI worked for me.
The process did change the Bootloader version?
Bootloader remains stuck UNLOCKED
The OEM it's greyed now in Google OS.

I need help before I do any harm I will regret, if I'm not there already...
¿Any advice?
Thank you in advance!

Detected Changes:

-> The Fastboot screen reads NOW:

Fastboot Mode
Product revision: bluejay MP1.0

Bootloader version: bluejay-1.2-9075776
Baseband version: g5123b-........
Serial Number: ......
Secure boot: PRODUCTION
NOS production: yes
UFS: 128 Micron
Device state: unlocked (In orange colour)
Boot slot: a
Enter reason: vol down pressed
UART: disabled

-> BEFORE UNLOCKING: (The rest data looks the same)

Bootloader version: bluejay-1.2-8893284
Device state: locked

Operating System: TUXEDO OS 22.04 (based on Ubuntu 22.04 LTS)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-10052-tuxedo (64-bit)

mythodical

I received a similar error when attempting both the web and manual installation methods while using Debian Sid (GNOME and Chromium). Ultimately, I had to switch to a Windows 10 PC and Chrome to complete the process for the first phone (using the same cables that failed under Linux). For a second phone, I had great success using another phone (Huawei) with Chrome as the installer source (USB-C to USB-C).

A2B

Thank you, I will give it a try in windows and chrome as soon I get to a machine with windows.
I'm concern to the fact that the phone bootloader it's stuck as unlock and the bootloader version changed from the start, when it was locked. I don¡t know if it is normal or related to the inability to revert it back to "Locked".

A2B

To whom may concern, finally got it right (full installation and final locked) with Windows 10 and web Installer. Stock cable.

SOLVED

Thank you mythodical !

New2Graph

Hi I'm having the same issue after failed flash (internet dropped) now seem to be stuck in loop. Getting the following error msg:

Your device is corrupt. It cant be trusted and may not work properly.
Visit this link on another device
g.co/ABH

If i try and proceed then google (white background) comes up but stays stuck on this screen? Any help much appreciated, apologies new to this and to the forum.

Kind Regards

treequell

New2Graph Hi there, I just replied to your other post, please have a look at my reply there: https://discuss.grapheneos.org/d/7496-your-device-is-corrupt-failed-when-flashing/2