What are people's stories with Pixel 3 on Fi regarding bootloader unlock? Is it greyed out or unlock is working for people?
Quick search only indicated there are open issues in this area and no resolution.
Ordered Pixel 3 from the Google Store with Project Fi, and bootloader unlock is not grayed out on my phone. No idea if that's common or uncommon, just reporting on my device.
samnada said:
Ordered Pixel 3 from the Google Store with Project Fi, and bootloader unlock is not grayed out on my phone. No idea if that's common or uncommon, just reporting on my device.
Click to expand...
Click to collapse
You mean you ordered from fi.google.com, right?
devsk said:
You mean you ordered from fi.google.com, right?
Click to expand...
Click to collapse
Pretty sure I ordered the phone on store.google.com, and specified the Project Fi version, then completed the Fi registration on fi.google.com.
devsk said:
What are people's stories with Pixel 3 on Fi regarding bootloader unlock? Is it greyed out or unlock is working for people?
Quick search only indicated there are open issues in this area and no resolution.
Click to expand...
Click to collapse
Ordered the Project Fi version from the Google store. Bootloader still locked. Option to enable bootloader unlocking not grayed out.
I ordered mine from Project Fi directly (through the app) and received with the greyed out "OEM unlock". Even after updated and factory resetting, still greyed out.
Just got my black XL 64 direct from Fi, financed, today. OEM unlock was not greyed out and let me toggle it on. Haven't performed an unlock.
josephpalozzi said:
I ordered mine from Project Fi directly (through the app) and received with the greyed out "OEM unlock". Even after updated and factory resetting, still greyed out.
Click to expand...
Click to collapse
Did you enable it in devoloper options?
OEM unlocking grayed out
josephpalozzi said:
I ordered mine from Project Fi directly (through the app) and received with the greyed out "OEM unlock". Even after updated and factory resetting, still greyed out.
Click to expand...
Click to collapse
I ordered a Pixel 3 from the Project FI/Google Store and received the Pixel 3 with OEM unlocking grayed out. After searching the web I found that some people had received the Verizon version from Project FI. I called FI support and was able to RMA the first phone, I then received a Pixel 3 with OEM unlocking enabled. I was told by support that there was no guarantee that the device I receive would have OEM unlocking enabled, but it was worth it to me and I got LUCKY.
Because I returned it within the 15 day return policy, they were able to guarantee me a new phone and not a refurbished device. I would call support to make sure of this, I had to talk to a manager.
Probably everyone resolved this already, but in my experience Pixel 3s from Google all come with OEM unlocking turned off and grayed out (ie can't be unlocked), at least initially, then during setup, something is downloaded or something is queried that makes the option selectable.
I had 3 of them, 2 from Project Fi and 1 from Google Store. I set up all of them initially not connecting to WiFi, and obviously not connecting to Google Account.
For all 3, I enabled developer options, then found OEM unlocking was turned off and grayed out (not selectable)
After connecting to WiFi and Google account, then the option was selectable.
There is probably a list of serial #s somewhere that gets queried and it controls whether your OEM unlocking option will be selectable or not. Assuming there is such a thing, until that theoretical query is successful, your device will have OEM unlocking grayed out.
Related
Hey,
I have a Galaxy S7 that is now in FRP Lock after I rooted it, as I didn't know about ticking with "Allow OEM Lock".
I also have a Pixel that I rooted and so far is doing fine. I'd obviously like to avoid FRP Lock with my Pixel as well. When I went to the Settings to turn on "Allow OEM Lock" that option was greyed and I can't change it. It says "bootloader is already unlocked".
Does it mean my Pixel is safe from going through FRP Lock or... I need to do something about it?
Thanks in advance,
TheAsker70 said:
Hey,
I have a Galaxy S7 that is now in FRP Lock after I rooted it, as I didn't know about ticking with "Allow OEM Lock".
I also have a Pixel that I rooted and so far is doing fine. I'd obviously like to avoid FRP Lock with my Pixel as well. When I went to the Settings to turn on "Allow OEM Lock" that option was greyed and I can't change it. It says "bootloader is already unlocked".
Does it mean my Pixel is safe from going through FRP Lock or... I need to do something about it?
Thanks in advance,
Click to expand...
Click to collapse
So that is grayed out because it is already unlocked. It keeps you from sliding it while unlocked which can lead to a disaster if you have to re flash.
I am confused, your post is the first time I have heard of FRP lock from rooting. It is only triggered from resetting a phone, or flashing it, and not properly removing the Google account. You can get back in with the same account. It's only an issue if you don't know the original account info, like you buy it used.
TonikJDK said:
So that is grayed out because it is already unlocked. It keeps you from sliding it while unlocked which can lead to a disaster if you have to re flash.
I am confused, your post is the first time I have heard of FRP lock from rooting. It is only triggered from resetting a phone, or flashing it, and not properly removing the Google account. You can get back in with the same account. It's only an issue if you don't know the original account info, like you buy it used.
Click to expand...
Click to collapse
So I want it grayed and to stay like that? This what keeps the phone from going into FRP Lock?
I don't recall flashing the S7. The Pixel went through a lot before I figured how to root it. Then I switched to the S7 and already had some more concrete knowledge how to root it. But... maybe I have done that with the S7 as well. It was a few weeks ago. It took some trials and errors.
Since then I turned off the S7 because I was out of the country and needed a new SIM Card to start using it, so it was just off ever since the root and some data transfer from the S5 (that I'm still using). But...certainly, it's not a used phone. I bought it brand new from Amazon. Unlocked but new. So never had issues with the Google account. Maybe I didn't remove the Google account in one of the times I flashed it? Anyhow, it never asked for my password before FRPing it. I just found it this way when I came to install the new SIM Card.
Or maybe this means the phone wasn't brand new...?
TonikJDK said:
So that is grayed out because it is already unlocked. It keeps you from sliding it while unlocked which can lead to a disaster if you have to re flash.
I am confused, your post is the first time I have heard of FRP lock from rooting. It is only triggered from resetting a phone, or flashing it, and not properly removing the Google account. You can get back in with the same account. It's only an issue if you don't know the original account info, like you buy it used.
Click to expand...
Click to collapse
So got my S7 back up and running.
On the S7, from what I was told, to avoid FRP Lock, I need to set "OEM Unlock" to be On.
My Pixel is still greyed out.
Any idea why the difference between the two units?
From your post I understand keeping the "OEM Unlock" on can be dangerous.
So I'm a bit confused.
TheAsker70 said:
So got my S7 back up and running.
On the S7, from what I was told, to avoid FRP Lock, I need to set "OEM Unlock" to be On.
My Pixel is still greyed out.
Any idea why the difference between the two units?
From your post I understand keeping the "OEM Unlock" on can be dangerous.
So I'm a bit confused.
Click to expand...
Click to collapse
Once it is unlocked, do not relock it. Once you slide it to allow OEM unlock leave it there.
OK. Hopefully the it'll stay greyed on the Pixel. Thanks again!
OEM unlock has nothing to do with FRP. I don't know much about the galaxy series but if Knox is still integrated then rooting may have upset Knox and for some reason triggered FRP (just a theory I have no way of backing up) as far as on the pixel FRP is to prevent activating someone else's previously activated phone after completely wiping it. It simply asks for the password of a previous Gmail account on the device. As far as bypassing FRP I believe there are ways to do it but I've never tried it
I typed in the command to get oem_unlock_data and got my devices string. I input it into fastboot and it says "phone not eligible". I previously had a Motorola G5 plus and had no issues and aft r checking the phone is definitely eligible. I put the Gmail I use onto the phone from my Motorola account and am still having errors. I read a thread stating my device id may be within settings option of phone and if i take off this setting it may work. I cannot find this option within settings. Any ideas on how to unlock bootloader on an eligible device that is telling me is ineligible? My device also says oem_locked in bootloader screen so I know this is the case. Any input would be highly appreciated.
WarrenC1236 said:
I typed in the command to get oem_unlock_data and got my devices string. I input it into fastboot and it says "phone not eligible". I previously had a Motorola G5 plus and had no issues and aft r checking the phone is definitely eligible. I put the Gmail I use onto the phone from my Motorola account and am still having errors. I read a thread stating my device id may be within settings option of phone and if i take off this setting it may work. I cannot find this option within settings. Any ideas on how to unlock bootloader on an eligible device that is telling me is ineligible? My device also says oem_locked in bootloader screen so I know this is the case. Any input would be highly appreciated.
Click to expand...
Click to collapse
Go to system settings>developer options, find the OEM unlock setting and toggle it to the enabled position. To enable developer options, go to system settings>about>software info>build number(or wherever your build number setting is located in your device's settings). Tap on the build number 7-10 times quickly, this will enable dev options. Then go back to system settings and you'll see developer options has been added to the list somewhere at the bottom.
Then try your unlock method.
Sent from my SM-S767VL using Tapatalk
So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota
My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
andrepd said:
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
Click to expand...
Click to collapse
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
dcarvil said:
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
Click to expand...
Click to collapse
Thanks, I tried that, it is indeed a Verizon model. Do you know if there is any way around this to unlock the bootloader? I guess I'll have to google around a bit to figure out if it's hopeless or not x)
There is no way to unlock a Verizon phone.
Hmm well I'm getting quite mixed signals here:
- imei.info says "Pixel 3 128GB, US VZ, Just Black"
however:
- ro.oem_unlock_supported is 1
- and bootloader screen says "Product revision: MP1.0(ROW)", not "(VZW)"
- box says "ESIM" rather than "SIM"
and also in some threads users report being able to unlock verizon phones... So it's all very strange x)
Pretty much same here. Did you figure out something?
me too
Ok, so a brief update here, the results of my search over the last couple of days:
Most likely, your Pixel 3 cannot be unlocked, it has been locked by Verizon when activated on their network and we don't have a way to undo this OEM lock. If you bought it re-furbished or second hand, and OEM Unlocking is grayed out, the most likely is that there is nothing to do.
Relevant / connected threads:
- https://forum.xda-developers.com/t/oem-unlocking-grayed-out.3860023/page-21
- It can be unlocked before it has activated on verizon: https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
- Some (unsuccessful) attempts are discussed at https://forum.xda-developers.com/t/bounty-unlock-bootloader-vzw-pixel-3-xl.3856605/page-113 and
Use 'fastboot oem citadel' to unlock bootloader? (Verizon Pixel 3)
I unfortunately have a Pixel 3, from Verizon (when I bought it it was not described as a phone issued by Verizon had I known it I wouldn't have bought it). I'm trying to accomplish The impossible by finding some way to unlock the bootloader...
forum.xda-developers.com
- This post pretends that it can be undone, but this has not been confirmed / applies only to very speecific cases:
https://www.reddit.com/r/GooglePixel/comments/sc2w1r
- https://support.google.com/pixelpho...ixel-3-verizon-flashed-3xl-system-image?hl=en
-
https://www.reddit.com/r/GooglePixel/comments/rsrnu0
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
whiggs2 said:
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Click to expand...
Click to collapse
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
jwoegerbauer said:
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
Click to expand...
Click to collapse
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
whiggs2 said:
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
Click to expand...
Click to collapse
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
SubwayChamp said:
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
Click to expand...
Click to collapse
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Droidriven said:
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
Click to expand...
Click to collapse
This - The 'U' devices do not have OEM unlock by default.
whiggs2 said:
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Click to expand...
Click to collapse
This may be just a kind of starting point, to have in mind, but that need more research though, I did it in my GN8 but with your device, things may be different.
There are some things you have to check, in the download screen, KG has to be completed, not prenormal or checking, also search for the CSCs that are compatible for your device, this is one of the tutorial, kind of, that I followed https://www.getdroidtips.com/guide-...ocked-firmware-galaxy-note-8-sm-n950u-n950u1/