A Pixel from the Google Store is guaranteed to be able to be unlocked. A non-carrier Pixel from elsewhere should also be fine unless the retailer is doing something wrong such as mixing inventory between carrier and non-carrier Pixels. There mostly aren't separate SKUs for carrier Pixels but rather it's a dynamic thing determined based on how they decided to sell it. That's why it needs internet access to check whether it's a carrier Pixel or not. They started out with a Verizon partnership where they had regular Pixels and Verizon Pixels but moved away from that to simply having Pixels which can be sold locked by a carrier via an entry in their server-side database. Recently, a few people have had issues with this. If they claim it's unlocked but it isn't, then it's false advertising and there should be no issue getting money back. It should also put it on their radar that something is wrong if they're competent but unfortunately that's a lot to ask...

    tnk479 The retailer is doing something wrong such as marking it as being sold as a carrier Pixel when they aren't. There isn't any hardware/firmware difference and there doesn't have to be a separate SKU (we don't know if they still have separate SKUs for Verizon, but Verizon Pixels used to be the same hardware/firmware with a carrierid flashed at the factory).

      Has anyone been able to OEM unlock any Pixel 8a yet and if so where did they purchase from? I purchased a unlocked Pixel 8a from Target with the same grayed out issue. Before I return the device and reroll a phone from Best Buy it would be good to confirm if anyone has succeeded at this. Otherwise refund and pickup a Pixel 7a, 7 or 7 pro.

        I recently purchased a Pixel 8a (Unlocked) from the Google Store and am also facing the "OEM Unlocking" setting being greyed out issue. After recieving the phone I connected it to Wi-Fi and two carriers to test it (AT&T and a Verizon based MVNO), as well as updating all software. I'm in contact with Google support to try and get this option enabled, but am still unsure whether the SIM card's caused this issue.

        Tomorrow I will try and test out factory resetting, software updates, and other solutions proposed in this thread. I can also confirm on the Google Store warranty page it is a Pixel 8a (Fi), not Unlocked like ordered.

          • [deleted]

          GrapheneOS "A Pixel from the Google Store is guaranteed to be able to be unlocked."

          I do not believe this is true.

          There is a report on XDA and a report on Reddit of people having the OEM Unlocking function greyed out on their Pixel 8as purchased directly from Google.

            GrapheneOS Is it acceptable to post the Reddit and XDA forum posts of other people having issues unlocking the bootloader of Pixel 8a's?

            • [deleted]

            • Edited

            michaelsoftbinbows I'm starting to think no one has. I actually have yet to see a single report of anyone being able to successfully OEM unlock their 8a, regardless of where it was purchased from.

            I wouldn't go through the hassle of returning and rebuying just yet. Hopefully we can get some light shined on this soon.

            Something weird is going on here. It seems almost exactly like the 6a situation when that released.

              jahim663 I can also confirm on the Google Store warranty page it is a Pixel 8a (Fi), not Unlocked like ordered.

              This does seem like something for their support people to work on, so it's good it's in their hands. If, hypothetically, they are shipping the wrong devices to end users, maybe they are also shipping the wrong devices to retailers.

              Please report back!

                [deleted] actually have yet to see a single report of anyone being able to successfully OEM unlock their 8a, regardless of where it was purchased from.

                I suspect at least one GrapheneOS developer unlocked at least one 8a 🤔

                  • [deleted]

                  jahim663 My Best Buy model lists it as (Fi) as well.

                  Which is curious because if that means it's a Google Fi branded model, it should still be bootloader unlockable, as phones purchased through Google Fi have always been fully unlocked (sim and bootloader) Pixels.

                    de0u Google Support forwarded the issue to "Google Pixel Hardware Support" team. If anyone else reaches out to Google Support, they seemed to recognize it was an issue after explaining carrier unlocking is different from bootloader unlocking "OEM unlocking" option.

                      [deleted] I've been scouring Reddit and XDA for last few days and people in the Pixel 6a forums ancedotally mentioned that Pixel 6a (Unlocked) purchased from Google Store show up as Pixel 6a (Fi) in the warranty page.

                      • de0u replied to this.
                        • [deleted]

                        jahim663 Glad you were able to submit a report.

                        They refused to help me at all because I didn’t purchase the phone from them. Which is a whole other can of worms. I’ve never had a manufacturer of any product refused to help me just because I didn’t buy it directly from them. and my warranty is still through them so that literally makes no sense.🙃🙄

                        jahim663 People in the Pixel 6a forums ancedotally mentioned that Pixel 6a (Unlocked) purchased from Google Store show up as Pixel 6a (Fi) in the warranty page.

                        Hmmm. When I put my serial number into the "Warranty Helper" it comes back as "Pixel 6a 128GB Sage (Unlocked)".

                        jahim663 SIM card can't cause an issue with this. It doesn't matter which carrier you're using. It's supposed to say it's an unlocked device, not a Google Fi device.

                        [deleted]

                        "A Pixel from the Google Store is guaranteed to be able to be unlocked."

                        It is true. If you're having a technical issue with enabling OEM unlocking with your unlocked device, contact their support and get it resolved.

                          [deleted] That's utter nonsense since we obviously had to unlock a device to add support for it and many of our users have tested it and are using it. You're doing the opposite of what would get you useful support.

                            de0u We could not have added support for it without having devices with GrapheneOS and having people who tested it with GrapheneOS. It makes no sense to claim that no one has devices they were able to unlock when a bunch of people are using GrapheneOS on the Pixel 8a already...