Did you connect it to the internet and update? If after that the toggle is still greyed out, you're likely out of luck.

Most stores refer to "carrier unlocked" and not "OEM unlockable", meaning you can use it on any phone network provider. There are ways to have the provider unlock it for you if you're lucky, but most of the times it's easier to just return and refund the device if possible. If you buy from Google directly or at Best Buy, you should get an OEM unlockable device. Swappa also seems to be reliable in giving you the information whether a device is OEM unlockable.

I hope you find a quick and satisfying solution.

    N1b It will be sad if the one amazon sells is not OEM unlockable as I believe for previous models it has been.

        Hey @tnk479 , as others in the thread have mentioned, OEM is not the same as Network unlocked. Usually listings will include ''Factory Unlocked'' to indicate that OEM will be available.
        Some devices of Pixel can be troublesome (sometimes for no obvious reason) but here are my usual methods to enable OEM.

        Method 1. First thing I try is to go to Google's Stock ROM installer and plug the Pixel into a laptop using a Chrome based browser (Chromium, Brave work). Check for an update and see if you see anything relating to ''Verizon or T-Mobile''. This indicates that it is originally from one of these carriers and OEM unlock will not be available no matter what you try.

        Method 2. Boot, run through setup, connect to internet (try wifi connection and mobile data too). Update to latest version from within settings. Then check OEM. If it's still greyed out, THEN factory reset, boot, run through setup, connect to wifi and check OEM again. This factory reset after an update can make the OEM become available.

        Method 3. Do the same as method 2 and wait a few days, rebooting from time to time but always connecting to wifi. Sometimes a wait time enables the OEM toggle.

        If nothing above works then it is almost certain you got a SIM unlocked phone and not a Factory Unlocked phone which enables OEM unlocking.

          Cws6dNKPNL3j guess the moral of the story is when buying a phone we have to say "Is this phone OEM unlockable?" And perhaps they'll know what that means...

              flighty_sloth I did my Brave searches and found that. Tried it right away last night. Failed. Nothing worked. I just returned the damned thing to Amazon. I will go and get one from Best Buy.

                Cws6dNKPNL3j thank you kindly for all of this. Hopefully this will serve someone in the future. I decided to return the device to Amazon and to get one from Best Buy instead. These corporations can eat a dick. I am so tired of it.

                  CodexAG Yeah, I usually just ask the seller to follow my instructions to enable their developer options and check OEM themselves before buying.

                    I picked up an "unlocked" Pixel 8a at Best Buy an hour ago. Same problem. I ran system updates. Factory reset. Still can't toggle OEM Unlocking.

                    • de0u replied to this.

                      • [deleted]

                      • Post #16
                      • Edited

                      Having the exact same problem. Got mine at Best Buy and can't unlock it.

                      These models are identical to the ones from Google directly. I've read reports on Reddit and XDA of people purchasing directly from Google also not being able to unlock.

                      Factory reset multiple times, connected to the internet overnight, tried the "checkin" dialer command. Nothing works.

                      Very frustrating.

                        @de0u and @tnk479 did you try ''Method 1'' in my post earlier?

                        First thing I try is to go to Google's Stock ROM installer and plug the Pixel into a laptop using a Chrome based browser (Chromium, Brave work).
                        Check for an update but don't install anything. Just check if you see anything relating to ''Verizon or T-Mobile''. This indicates that it is originally from one of these carriers and OEM unlock will not be available no matter what you try.

                        I have had experience with phones from both Google directly and 3rd party sellers who say 'Factory Unlock' and yet when first running a check with the installer from Google, I see the dreaded Verizon/T-Mobile update.
                        If you see this, the phone is no good for unlocking the bootloader no matter what the seller says.

                          Cws6dNKPNL3j

                          When I do that and I select the 14.0.0 release the following options are presented:

                          • AT&T, T-Mobile
                          • Verizon, gStore, CA, USC
                          • KDDI
                          • EMEA, APAC, JP
                          • Default

                          Is that the set of options you are referring to? From where does this phone originate?

                            @tnk479 Making unsubstantiated claims like the one we've removed will result in your thread being locked and unlisted.

                              GrapheneOS

                              Sorry, what? I looked at your Twitter feed. I did not see anything about Pixel 8a and OEM Unlocking...if I am incorrect in that then I apologize. Your deletion and warning is seriously unwarranted. I am a GrapheneOS fan.

                                  GrapheneOS Ahhh, I get it now. I should have said "Pixel 8a" and not Pixel??? Either way, if you're adamant that there's a fix, I am definitely loving that. Can't wait.

                                    GrapheneOS And actually, not only am I a fan, I have donated a monthly amount through Github for quite some time now.

                                      tnk479 Unlocking the Pixel 8a, installing GrapheneOS and locking it again works fine. Nothing is over for the Pixel 8a. You having issues with may be caused by your network or they may not have actually been unlocked devices. Best Buy and Amazon may have ended up with devices which aren't unlocked somehow. A significant logistics failure doesn't indicate any issue with the device model itself.