OEM Unlocking Grayed out on non-VZW Pixel 2.

Search This thread

Hey!kevin

Member
Oct 21, 2017
13
2
New York
@gvsukids
They won't send you a new one, refurbished is the policy, it's in the warranty documentation. I would have preferred a new one but the 128 GB Pixel 2 is out if stock so after 3 returns they chose to give me a refund
 

Hey!kevin

Member
Oct 21, 2017
13
2
New York
So I have to ask for another refurbished one, hoping this one is not greyed out?
I can't predict how things will play out in your case, all I can do is share my specific experience, which seems similar to many others on XDA. It seems like every RMA pixel 2 has OEM locking disabled - I got 3 in a row and now I'm stuck using a Nexus 6P until I decide what to buy, and I haven't received my refund yet.

My advice - check the official Google support threads and explain your problem. See if they can sort it out, I saw at least one post that dealt with this exact problem. A vendor is in charge of the refurbished, my guess is they are shipping out units with it disabled.

The support people that you talk to through pixel help and email don't even understand what OEM locking means, and they don't know what is causing this problem or how to fix it. All they can do is process your return.

You have 3 options: demand a new phone, roll the dice and see if your next replacement works, or ask for a refund.
 
Last edited:

AsuraDas

Senior Member
Oct 9, 2016
210
31
So I to got a replacement device months ago. When I activated my new refirb selected "oem unlock" and called it day. I thought I was safe if my phone ever bootlooped or if I ever wanted to root/mod in the future I could.

Well turns out I can't, same story as everyone else. Oem unchecked fasboot flashing unlock. Returns "remote' Flashing Unlock is not allowed" reboot and oem unlock is greyed out.

Factory reset allows me to check off oem unlock however flashing command in bootloader fails. I reboot and it's greyed out.

I have factory again allowing me to oem unlock again. I can reboot as many times as I want and I continue to have oem unlock. I can deselect oem unlock reboot and reselect oem unlock and it works. I can boot into bootloader restart back into the OS and oem unlock is still tickable. As soon as I use the command "oem flashing unlock" it fails and oem unlock is greyed out in developer settings.

---------- Post added at 06:23 PM ---------- Previous post was at 06:08 PM ----------

My theory is that these phones are google branded. However when they flash new software they inject a bootloader that does not allow it to be unlocked. The software is Google so you can still check and uncheck oem unlock. I am guessing they are thinking by not allowing users to unlock bl it's a fail safe for user error
 

AsuraDas

Senior Member
Oct 9, 2016
210
31
Talked to support they are sending me a replacement I am not holding my breath that it will be fixed based off other person's experience.

That being said I tried to install ota update in recovery and it failed. Signature verification failed. I confirmed I have the right OTA download for pixel 2 and October security update which my phone currently has.

Anyone else with this problem able to flash OTA via recovery (adb sideload)

I am concerned this phone is even more locked down than the VZW
 
Last edited:

eneka

Senior Member
Dec 10, 2010
158
32
Hacienda Heights
Getting the same exact issue as everyone else. Was able to toggle unlock, but running the command fails and becomes greyed out. Tried everything I could think of to no avail. Google support was useless and blamed it on the carrier (I'm on tmobile)


They even asked if the phone was rooted when I was telling them I couldn't unlock the bootloader. :rolleyes:

They've escalated it to a specialist team which will get back to be in 24-48 hours.

This was quite infuriating

Kevin C11:14 PM
This is totally related to carrier. They will have to unlock this for you to access it.

J11:14 PM
but this was a replacement device directly from the google store

Kevin C11:14 PM
Normally if the bootloader is unlocked as you are getting an option of FDR.

Kevin C11:15 PM
Yes. That is right. This option is related to carrier not us.

J11:15 PM
i was having this issue prior to inserting my sim card actually

Kevin C11:15 PM
This is totally related to them.

Kevin C11:15 PM
You will have to contact them for any further help.

Kevin C11:16 PM
Before inserting the sim card this options is not available at all.

J11:16 PM
it was

Kevin C11:18 PM
Okay;. In this case I will route this case to my specialist team and they will get back to you via email with in 24-48 hours of time. Is that fine?
 

mamarcac

Senior Member
Sep 29, 2016
109
29
Do you need to toggle OEM Unlock inside the OS though? It's been a while since I unlocked my BL but all I recall having to do is enable USB Debugging and then run the fastboot oem unlock command. Upon booting, OEM Unlock was greyed out BUT it was greyed out in the right way; showing it was unlocked.
 

eneka

Senior Member
Dec 10, 2010
158
32
Hacienda Heights
Do you need to toggle OEM Unlock inside the OS though? It's been a while since I unlocked my BL but all I recall having to do is enable USB Debugging and then run the fastboot oem unlock command. Upon booting, OEM Unlock was greyed out BUT it was greyed out in the right way; showing it was unlocked.

must be toggled before running the command, which is now "fastboot flashing unlock"
 

eneka

Senior Member
Dec 10, 2010
158
32
Hacienda Heights
Anyone have insider info on this issue or if their case was resolved? I'm getting quite annoyed because the device is essential useless to me without being able to unlock the bootloader. They are refusing to provide me ANY option of resolution, including my suggestion to have my original phone repaired. There's been reports of this over a year ago so I don't have confidence it'll be fixed anytime soon.

Thank you for writing back to Google Support.

I certainly understand your situation and I'd feel the same If I were you. As of now we are still investigating this issue, however we do not have any resolution at this time. May I request you to extend your patience in this regard.

Thanks!
 

ljcorsa

Senior Member
Sep 5, 2010
53
6
Google Pixel 4a
I've been having an issue with color washout, Google threw up their hands and sent me a replacement that has this issue. (Fortunately I could send it back.) They seemed genuinely surprised the replacement wouldn't unlock.

And they charged me when they didn't get my original phone back (I sent them back their useless replacement.)

Not looking good for the rooting community.
 

mbiscuits

Member
Nov 16, 2010
20
4
5th times a charm

After going through the RMA process five times, I finally got a Pixel 2 today that allowed me to unlock the bootloader. Maybe Google has fixed it now. Good luck everyone.
 

AsuraDas

Senior Member
Oct 9, 2016
210
31
Getting my pixel 2 this Friday. Hoping for the best. Either way now that Fi supports any phone. I'll probably get a one plus 6t and use unreal mobile (att) I will lose Sprint network but gain att which is better anyeays.

Still hoping I do love me pixel 2
 

AsuraDas

Senior Member
Oct 9, 2016
210
31
Getting my pixel 2 this Friday. Hoping for the best. Either way now that Fi supports any phone. I'll probably get a one plus 6t and use unreal mobile (att) I will lose Sprint network but gain att which is better anyeays.

Still hoping I do love me pixel 2
No go still problem. The 6t is looking better by the day
 

eneka

Senior Member
Dec 10, 2010
158
32
Hacienda Heights
Just got a second RMA. Still can't unlock the bootloader. Factory reset doesn't make the toggle work again either.

Google support is of no help.

Thanks for taking the time to report this. We're currently investigating this issue, however we do not have any resolution at this time as a replacement did not resolve the issue. Google is committed to continually making improvements to our devices and regularly provides free software updates to customers. Thank you for your patience.
 

AsuraDas

Senior Member
Oct 9, 2016
210
31
Just got a second RMA. Still can't unlock the bootloader. Factory reset doesn't make the toggle work again either.

Google support is of no help.
Not surprising, I have the same story. I emailed them last night stating how displeased I was and that I have bought many Google devices more than half of the Nexus line, pixel 2 and 2xl. No response. At least with Samsung or LG you know your getting a locked down device.
 

amtrak23

Member
Aug 17, 2009
11
2
Just tried my 3rd replacement...it won't unlock. Original can't take pictures when it thinks it has bad reception, and have now wasted well over 5hrs on the phone with Google and Fi support. This last rep basically said that there was nothing she could do, except let em talk to a supervisor. Then after 5 mins she says that I have passed their allowed time for me to wait for a supervisor and that I should get a call back from someone in the future.
 

bunklung

Senior Member
Mar 20, 2011
526
107
Just tried my 3rd replacement...it won't unlock. Original can't take pictures when it thinks it has bad reception, and have now wasted well over 5hrs on the phone with Google and Fi support. This last rep basically said that there was nothing she could do, except let em talk to a supervisor. Then after 5 mins she says that I have passed their allowed time for me to wait for a supervisor and that I should get a call back from someone in the future.

Did you see this comment?

https://issuetracker.google.com/issues/68897739#comment177
 

farrenicus

Senior Member
Oct 1, 2013
91
59
Just received my warranty replacement Pixel 2. OEM unlock is greyed out, so the problem lives on.

I don't see why this is regarded as a bug at this point. Part of the refurb process seems to be locking the bootloader permanently.
 

thedude9821

Member
Aug 8, 2014
5
5
I'm having the same issue with my RMA'd pixel 2. Google told me to try factory resetting it, which didn't work, and then told me to submit a bug report. They didn't even offer to RMA it again. I'm really unhappy since my (rooted) pixel 2 was hands down the best phone I've ever had, and I can't afford to upgrade to a different phone. So I'm stuck with this crappy unrootable RMA now.

EDIT: Literally just before I packaged up my original phone to send to google, I was able to fix it. If anyone is having the "Slot Unbootable: Load Error" problem and still has their original phone, try my solution here before you send it in!
 
Last edited:

nolimit78

Senior Member
May 13, 2009
1,269
194
Kansas City
Excellent find! I wish I would have seen this yesterday before I sent mine in. I had the same exact issue that you had described and my RMA device can't be unlocked.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    This looks to be a problem with the "refurbished" Pixel 2s they send out for warranty replacement. After sending me 3 "refurbished" ones, they now said I qualify for an exception to receive a new phone, and got the new one -- which worked immediately without any problems. Notably, in Developer Options, the "OEM Unlocking" slider is off after a factory reset, not on as on the refurbs.

    Also curious: if you do a adb shell getprop ro.boot.cid, you should see VZW__001 on a Verizon phone and 11111111 on a Google phone. My refurbished phones, as well as the new one I just received, all returned 00000000.

    The refurbished phones all shipped with a 3/2018 patch date, whereas the new one shipped with a 9/2017 patch date. That might also be part of the issue.
    2
    Mine was a brand new device. I did update to the June security patch before I finally got it to work. I refused to install my SIM card (which is Verizon) until I managed to get the bootloader unlocked.
    1
    What build number are you on?
    1
    The resale value? For whom, a few XDA users? No one cares about bl unlock any longer and it's going to go away. The resale value is due to it's great support in terms of updates, the camera and the device itself. Don't think that bl unlock will continue for any length of time at this point. Here's an article for you that portends what is coming down the pike. Get used to it, sorry to say.

    https://www.androidpolice.com/2018/05/24/huawei-halts-bootloader-unlock-program-indefinitely/

    Agree that it's probably going away... But disagree "no one cares about BL unlock". I care... LOL:p
    1
    I have the same issue, refurbished replacement from Google. The option is available on first boot after factory reset but fastboot command does nothing. After reboot, option is greyed out. Has there been any developement on this? Or am i stuck in their RMA cycle until they wise up and send a new one... Ive reached out to them and requested a new device based on the info provided here and reddit etc.. its been escalated to management but i highly doubt its going to be resolved to my satisfaction..