Pixel 6a has also not been added to the repair/warranty and OEM unlocking services. This is quite possibly a single oversight since it's the same data. For one thing, this means users trying to use store.google.com/us/repair get an error. It also means OEM unlocking isn't possible.
Conversation
We've done as much as we can developing GrapheneOS support for the Pixel 6a without OEM unlocking working.
People received devices before official launch day today (July 28th) and many things were missing, but these 2 things are still missing even after theoretical launch day.
1
4
12
I emailed 2 engineers who worked on bluejay and had commits related to AOSP merges about this and one of them sent an email along to the right person for the missing AOSP repository.
I'm unsure who I need to contact to get issue with repair/warranty and OEM unlocking db fixed.
1
2
13
It seems someone forgot to push the serial numbers for the Pixel 6a into those databases, so they don't know about the Pixel 6a. It's not terrible that the warranty/repair check service is broken but OEM unlocking being broken on an AOSP reference device is a huge pain for devs.
2
3
16
Replying to
Is that why people aren't able to use their unlocked 6A phones on Cricket (AT&T) and Visible (Verizon) wireless?
1
1
Replying to
It doesn't seem directly related but the root cause could be the same issue: they didn't deploy Pixel 6a support to the usual services. It may impact eSIM activation and other services.
2
1
Replying to
Visible support just confirmed that only eSIM is impacted and their SIM works fine on all unlocked Pixel 6A phones. So either it's a carrier issue or it's related to the issue you identified.
1
1
1
1
Sideloading the June release currently gated to only being given to Verizon users and then possibly doing a factory reset has a high chance of fixing it. That fixes the OEM unlocking toggle issue.
1
1
I'm not technical. Where do I download the June what release?
2
You can do what grapheneos.org/install/web#en says without doing the factory reset or enabling OEM unlocking. There's a guide on our site for sideloading an update and also a guide on Google's page for download the over-the-air updates. It requires using the adb tool from CLI.
