Does Google Fi block OEM unlocking?

FlipH19Switch

I've tried unlocking the OEM on a Pixel 6a and a Pixel 7 Pro. Both of these phones were originally purchased through Google Fi. I believe that both are paid off, and neither phone is currently active on Google Fi.

Is it possible to unlock the OEM for phones purchased through/ used with Google Fi?

de0u

FlipH19Switch I think if you provide the serial number (or maybe the IMEI, I forget) to Google's warranty service tool it will display whether it is a carrier-locked variant.

If it was originally sold for Fi then contacting them might be useful.

wizoatk

https://grapheneos.org/install/web#enabling-oem-unlocking

How far did you get when you tried? I don't recall having any issues on multiple phones purchased from Google with a FI sim preinstalled.

FlipH19Switch

I could turn on developer mode and get into the developer settings in both phones, but the OEM unlock switch was grayed out for both of them. For the Pixel 7 Pro, I also tried a factory reset but got stuck at the same place.

wizoatk

Does your phone have internet access?

wizoatk

de0u

Good idea, either IMEI or SN. https://store.google.com/repair

FlipH19Switch

Thanks for the suggestions. I checked the Pixel 7 Pro IMEI and it is not unlocked. It is a family member's phone, so I'm not sure what's going on there. I'll have to check the Pixel 6 later as it belongs to a different family member.

I checked my Pixel 8a, which was also bought through Google Fi/ currently using Google Fi, and is not completely paid off, and it is unlocked. I can use the OEM switch on it.

All phones have internet access.

I'm downloading a system update for the Pixel 7 Pro since I reset the phone. If that doesn't open up the OEM switch, is there anything else I can try before contacting Google Fi?

gd5rccdy

FlipH19Switch Hi, have you solved the oem unlocking issue? I would like to point out your Pixel 7 Pro showed without "unlocked" on google's repair website does not mean it is carrier locked. I know it because I have Pixel 7 Pro and Pixel 6a myself purchased through google store directly, and Pixel 6a showed as unlocked while Pixel 7 Pro showed without unlocked the same as you. So as long as it isn't showed as some carrier's name with it, it is the unlocked version. And also Google Fi does not lock phones, so if you are sure you bought from Google Fi, it is unlocked.

For the OEM unlocking issue, I have a similar situation as you. I have a new Pixel 10 Pro XL purchased directly from google store and activated google fi on it. Much to my surprise, the OEM unlocking is grayed out on it. I have another Pixel 10 Pro with exactly same setup, but the OEM unlocking is good. I think maybe I need to activate fi AFTER turning on developer options and making sure OEM unlocking is toggable. Becuase on the 10 Pro without the issue, I did exactly this, but on the 10 Pro XL with grayed out OEM unlocking, I activated fi first then find OEM unlocking was grayed out. And more, I also turned on developer options well before I activated Fi on my old 7 Pro and 6a. Only on the 10 Pro XL, I made the mistake to activated Fi first. So did you activated Fi first on your 7 Pro and 6a before your turned on developer options?

If you find a solution, please share with me. It's so frustrating that I can't unlock bootloader on my 10 Pro XL now while I purchased this phone specially for using GrapheneOS.

wizoatk

If the Google database shows that a phone is carrier locked, then generally the unlock request must come from the carrier (e.g. Google Fi). I don't believe there's any way to get OEM unlock while the device is carrier locked. So unless I'm missing something, next step is contacting Google Fi to get an answer why it's still locked and what you need to do (if anything) for Google Fi to remove the lock from the Google database. Once that's done then the phone should pick that up (over the internet) and allow you to change the OEM Lock status.

Hopefully that makes sense.

FlipH19Switch

Okay great. Thanks!

de0u

gd5rccdy There was a brief window for one of the earlier devices where Google mistakenly provisioned a bunch of unlocked devices as locked in their database. A lot of people fussed (and some people returned devices), then they fixed the problem. So something like that is not out of the question.

Since the 10 Pro XL was purchased from the Google store, their support team should be willing to engage with you about OEM unlocking. If you try that, let us know how it goes!

gd5rccdy

de0u I have contacted google support and have chatted with multiple representatives. The first representative offered to replace my phone without any hesitation, making me think that the issue is very hard to solve. And another one asked me to send the phone to somewhere to repair it. But because I travelled shortly after I got the phone, I'm not in the US, so I can do neither of the two options. At last another representative submitted my case to their engineer for further investigation, but I haven't got a reply after several days.

I searched through all platforms discussing Pixel phones, and I only find one person on XDA who has a Pixel 10 Pro XL with Google Fi has the same problem as me. My own theory is that because Google Fi sim has a T-mobile sim profile actually, Google server thought it was a T-mobile phone for some reason. I heard for older Pixels. if you activate a US carrier on a UNLOCKED pixel before you look into developer options and make sure oem is toggable, it might be grayed out.

Again, I would recommend turn on developer options first and make sure OEM unlocking is toggable, and activate any US carrier later.

I'm a long long time google phones user but I never met such a issue before. Nexus and Pixel purchased directly from Google were always unlocked. But this time, I really don't know how to solve the problem now. Any help will be appreciated!

de0u

gd5rccdy I'm a long long time google phones user but I never met such a issue before. Nexus and Pixel purchased directly from Google were always unlocked. But this time, I really don't know how to solve the problem now. Any help will be appreciated!

If the problem is a glitch in Google's device database, only Google can solve it. And honestly it's not clear that first/second/third-line customer service will be able to do it. My sense is that last time what got their attention was a large number of people returning devices because they couldn't be OEM unlocked. Your best move might be returning this device.