Hey all,

If I buy a Pixel 7 Pro from Google directly, is it guaranteed that the bootloader is unlocked? I'm ready to pull the trigger but would like to be sure.

If it's not guaranteed, how is your experience with their return policy? I'm reading I have 15 days to return for any reason, and don't see mention of a restocking fee. Are they good in that regard?

    I don't know about return policies, but the Google Store is the least likely to prevent you from using the bootloader unlocking option. Carriers mainly do it so it's easier to retrieve a phone if the contract is cancelled early, from my understanding. All Google Store phones are carrier-unlocked, for starters, but they don't officially say whether bootloader unlocking is available. If you ask support, they're likely to neither confirm nor deny whether it is, and dissuade you from doing so.

    I Just installed Graphene on my Pixel 6, which I got from Google Fi (so, I bought it from Google). The support, while being mostly useless, informed me that Pixels phones from them are always unlocked. Is this true? From what I see, yes.

    In the bootloader, it will say the phone is locked; however, you can use the bootloader menu to turn the lock off. That's what I had to do. Hopefully this helps you.

      JuTaRo

      The support, while being mostly useless, informed me that Pixels phones from them are always unlocked.

      I thought this in my initial line of questioning, but when pushed, the support person had completely ignored the word "bootloader" (and surrounding context) and assumed I was referring to carrier-unlocking. When I pushed more, they realized what I meant, got in contact with technical staff, and started dissuading me from trying to "root the phone". Trying to explain that GrapheneOS uses verified boot did not help. In the end, they failed to give me an answer one way or the other, but when I purchased the phone, the bootloader for my Pixel 6a was unlockable.

      But yes, phones sold from the Google Store, US or otherwise, likely all have bootloader unlocking available to customers.

      As @JuTaRo says, the bootloader is always locked on Google Pixel phones, and it should be. GrapheneOS expects and strongly advises you to lock the bootloader (providing an easy button in the web installer that does so) after installing to maintain verified boot, and to satisfy checks from some financial apps such as those from banks which check if the bootloader is unlocked. Bootloader unlocking is the functionality we need, which is the ability for the customer to unlock the bootloader so they can install another operating system like GrapheneOS on it.

        Equal2024 Thanks for your insight. I'm still learning how bootloader locking works. Are you saying I can lock and unlock it from within the OS, such that an unauthorized user couldn't install a new OS (or tamper with the existing OS) but the authorized user could? (i.e., login to phone, find menu, unlock bootloader again)

          • [deleted]

          • Edited

          mike876213 Yes, any Pixel from Google directly is guaranteed to have the bootloader unlockable. <3

          Equal2024 said that:

          Carriers mainly do it so it's easier to retrieve a phone if the contract is cancelled early, from my understanding

          Yes and another reason why the OEM unlocking option is disabled and grayed out on carrier locked devices, is to prevent users from rooting their device and enabling access to other carriers.

            [deleted] I've heard that some carriers will allow you to use any carrier after you finish paying the full amount of your contract, but Verizon is not one of those carriers. Additionally, even if carrier-unlocking (sometimes called SIM-locking) is enabled, it is not guaranteed they will allow you to unlock the phone's bootloader, but it is not unheard of.

            I don't agree with preventing the bootloader from being unlocked for any computing device sold to a customer for any reason, but there are various reasons why someone other than the customer would want it to be permanently locked.

            mike876213

            Are you saying I can lock and unlock it from within the OS, such that an unauthorized user couldn't install a new OS (or tamper with the existing OS) but the authorized user could? (i.e., login to phone, find menu, unlock bootloader again)

            The way it works is:

            1. Setup the proprietary version of Android and go to System Settings, then tap the build number 7 times to enable developer mode.
            2. Go into developer options and enable OEM Unlocking to enable the ability to unlock the bootloader. The bootloader is not yet unlocked.
            3. Reboot the device and hold down the power button to boot into what is effectively the BIOS settings for a Google Pixel phone.
            4. Use the volume buttons, with the help of GrapheneOS's web installer, to unlock the bootloader.
            5. Install GrapheneOS onto the phone.
            6. Lock the bootloader.
            7. Setup GrapheneOS, go to System settings, disable OEM Unlocking, and turn off Developer Mode.

            You need to be logged in before you can enable OEM Unlocking, which is what allows you to unlock the bootloader, but once this option is enabled, you don't need to be the privileged user to unlock the bootloader and load another operating system onto it. This is why it's important to turn off OEM Unlocking again when you have GrapheneOS installed; to prevent tampering and to maintain verified boot.

              Equal2024 I've heard that some carriers will allow you to use any carrier after you finish paying the full amount of your contract, but Verizon is not one of those carriers

              Verizon phones can be used with other carriers after being paid off. I’ve done it several times.

              However it is not possible to unlock the bootloader on their pixel phones. Even after paying it off.

                Hey all, just an update. I received my Pixel 7 Pro from google today and I was able to unlock the bootloader pretty easily. I'm now a fellow GrapheneOS user, woot.