IssueTracker

Project: platform/frameworks/support
Branch: androidx-main

commit f1515ea14143b5754df3dcbcb47537eee49c30f2
Author: Mariano Martin <ymarian@google.com>
Date:   Thu Sep 05 13:12:04 2024

    [PullToRefresh] Fix issue where graphics layer doesnt invalidate
   
    Test: tested manually that now graphics layer invalidates, in some edge cases
    where pullToRefresh is used in fragments
   
    Bug: 356039090
   
    Change-Id: Ib80663f6dcf2f7f05bda4189b0931ee697230698

M       compose/material3/material3/src/commonMain/kotlin/androidx/compose/material3/pulltorefresh/PullToRefresh.kt

https://android-review.googlesource.com/3256138

I have a Google Pixel 2 that I've bought Unlocked from the Google store. "OEM unlocking" is greyed out and can't be toggled.

Expected output: Touching "OEM unlocking" should allow it to be toggled.

Current output: Touching "OEM unlocking" doesn't do anything.
I've already emailed a bug report through a personal ticket response, but here's a screenshot of the issue.

P0 Priority?

Thanks for the information, the engineering teams are already investigating this issue. I will update this issue with more information as it becomes available.

I'm having the same problem. Google Pixel 2 that I've bought Unlocked from the Google store. "OEM unlocking" is greyed out and can't be toggled.

Expected output: Touching "OEM unlocking" should allow it to be toggled.

Current output: Touching "OEM unlocking" doesn't do anything.
I've already emailed a bug report through a personal ticket response, but here's a screenshot of the issue.

I just received my Pixel 2 today from Google Store and am also having this issue.

Same issue. Pixel 2 64gb purchased unlocked from Google Store.

Case ID [2-7523000019474]

Expected output:
The OEM Unlocking option should be available and able to toggle on and off.

Current output:
OEM Unlocking is greyed out. Touching it has no effect.

Android bug report:
Provided in Case ID [2-7523000019474]. Not on a public forum.

Screemshot attached.

Same issue. Pixel 2 64gb purchased unlocked from Google Store.

Expected output:
The OEM Unlocking option should be available and able to toggle on and off.

Current output:
OEM Unlocking is greyed out. Touching it has no effect.

Bought a Pixel 2 64GB through Project Fi.

Case ID: [1-7601000019881]
Case ID: [3-3275000019675]
Case ID: [0-7012000020005]
Case ID: [8-4231000019595]

Expected output:
The OEM Unlocking option should be available and able to toggle on and off.

Current output:
OEM Unlocking is greyed out. Touching it has no effect.
This was attempted while connected to LTE through Project Fi and with LTE turned off, connected to personal WiFi.

Screenshot is attached below.

I got my replacement today. I was able to unlock the bootloader.

I was tempted to put my VZ SIM, or use the phone transfer wizard first. NOPE, not worth the risk. Skipped everything and used wifi only.

Same issue Case ID: [5-7443000019689] Received replacement RMA - working now.

Also was "promised" google AI buds for my troubles and the first to report Nov 1st however since the technicians failed to add that to the ticket, even though repeatedly saying "yes we can give you store credit" three calls later there is still no status change.

This is my third Pixel 2 - finally got what I paid for. Minus the camera app constantly crashing.

I'm also getting a replacement sent to me after talking to Google support a
3rd time. Hopefully the new phone will be free of bugs...
I'm pretty impressed with being able to get a rep on the phone pretty much
instantly every time though.

On Wed, Nov 8, 2017 at 5:55 PM, <buganizer-system@google.com> wrote:

Just wanted to add that I also received a pixel 2 with a grayed out OEM unlock slider in the dev options on my "unlocked" Pixel 2 ordered from the play store.  Final resolution seems to be RMA

Pixel 2, unlocked, bought from google store, OEM unlock is disabled under dev options.

Pixel 2, unlocked, bought from google store, OEM unlock is disabled under dev options.
Add comment

Same here. I bought Pixel 2 in Google Store. Unable to unlock bootloader because OEM unlock in Developer options is greyed out. Support always ask me for the same stupid information (the email support looks like a robot, always replying my email and asking the same thing). I gave up, returned my phone an ask money back. Case ID RMA01402257

Same here.

Same here, though I bought the Verizon SIM-enabled from the Google store. Assumed it would be unlocked.

Bought two unlocked Pixel 2 phones from the Google Store. Both exhibit this same problem. Used a T-Mobile SIM in both of them.  Case ID [8-3672000019730]

Google hardware support both times told me to call carrier to get it unlocked! Finally got case escalated to next level support, definitely seems like we're sent Verizon bootloader phones

I have the same issue. Case ID [9-7206000020017]. I bought the Pixel 2 64 GB unlocked from the Google Store.

Expected output:
The OEM Unlocking option should be available and able to toggle on or off.

Current output:
OEM Unlocking is greyed out. Touching it does nothing.

Sent them a bug report and a screenshot. They did not offer an RMA.

I have this issue as well. Pixel 2 bought from Google store unlocked. I guess I'll reorder and return.

Update: I returned the first phone and just got the second Pixel 2 delivered. It has the same problem. 😔

@lu..., So sorry to hear that. You will just need to do another RMA, clearly Google isn't moving fast enough on this. Google will just have to pay the price on shipping here. You should push for compensation at this point.

This is an age old problem at this point for a fortune 500 company. One arm or division of Google does not talk to the other or at any realistic speed.

There is 3 layers of tech support where I think two of the layers are third parties. The highest level of support is via chat/email.

Then you have Google communities, no response there. This is just a free form of support from random Google users.

Then you have this bug tracking tool, which has gone nowhere and that's because of I have no idea. I think maybe it's because the people who manage the issues are not the same people who actually fix the problems.

And as soon as someone finds out it's not their issue (AOSP team), it might as well just die right there on the spot, because responsibilities and red tape?

So who's responsible is it to fix this issue? The warehouse manager at HTC?

How does this actually get escalated?

I bought 2 Pixel, the same. Sound's like a Verizon Bootloader, but INT Android OS.
The only solution seems replace the phone. Because Google was doesn't say anything about this bug.

Same issue, received the 8th started up the 10th to discover this.

Case ID [7-9968000019792]

On Nov 11, 2017 9:08 AM, <buganizer-system@google.com> wrote:

Just received the following response from customer support:

Thank you for contacting Google.

Thanks for taking the time to report this.

As mentioned, we're currently investigating this issue, however we do not have any resolution at this time. Google is committed to continually making improvements to our devices and regularly provides free software updates to customers.

Appreciate your patience and co-operation.

I have a "Kinda Blue" pixel. The CID is 0000000, so its not even Verizon(i'm not sure what it is). But my bootloader is locked too and the OEM unlock setting is greyed out. The whole purpose of buying this phone was to unlock it.

The "kinda blue" Pixel 2 is Verizon. That color is Verizon exclusive.

On Sat, Nov 11, 2017 at 10:35 PM, <buganizer-system@google.com> wrote:

The "kinda blue" Pixel 2 is Verizon. That color is Verizon exclusive.

On Sat, Nov 11, 2017 at 10:35 PM, <buganizer-system@google.com> wrote:

Did you actually talk to Google support and tell them the issue before
getting another one?

On Sat, Nov 11, 2017 at 6:26 AM, <buganizer-system@google.com> wrote:

I've bought this in India and also verified this via the Verizon website and google product forum (https://productforums.google.com/forum/#!topic/phone-by-google/XZ1jjBTRBYI;context-place=topicsearchin/phone-by-google/flipkart). This phone is not locked by verizon. And why would it be since I have bought it in India?

I am currently outside the country. But will be doing the full process of talking to all the organizations involved(Flipkart and Google service centers) once I get back tomorrow. Each call seems to be referring me the other party(Google says Flipkart, Flipkart says Google).

There is a difference between carrier unlocked and bootloader unlockable.
Verizon Pixels are not suppose to be bootloader unlockable. I'm afraid
you're misinformed.

On Nov 11, 2017 11:15 PM, <buganizer-system@google.com> wrote:

So you mean if I buy a Kinda Blue pixel anywhere in the world, it would be wrong of me to assume that this is bootloader unlocked? And could you please point me to that source of information.I have spent quite a while searching for it but could not find anything.

Any why would Google sell phones which are made for a specific carrier in areas where that Carrier is not available?

That wouldn't be a bad assumption. The only confirmed bootloader unlockable
Pixels are the ones bought directly from Google stores. If you bought a
Kinda Blue Pixel from a local 3rd party shop, you shouldn't expect it to be
bootloader unlockable. On top of that, you won't be able to RMA it with
Google.

On Sat, Nov 11, 2017 at 11:52 PM, <buganizer-system@google.com> wrote:

This is the *only* way Google is selling phones here. Not only that, they have also ensured a year of support on this. Based on your reply, I understand that you are not expected to buy Pixel phones outside USA/Canada. And can you point me to a document which states what you are saying. I ask this because I presume the company would have informed these clauses earlier(all Kinda Blue phones are bootloader locked) and we would not be providing any support for that problem whatsoever.

That wouldn't be a bad assumption. The only confirmed bootloader unlockable
Pixels are the ones bought directly from Google stores. If you bought a
Kinda Blue Pixel from a local 3rd party shop, you shouldn't expect it to be
bootloader unlockable. On top of that, you won't be able to RMA it with
Google. This is just information i've gather from various internet places.
You don't have to take my word for it.
Google technically isn't selling phones made for specific carriers in areas
where that carrier isn't available. Those phones being sold by 3rd party
stores are carrier unlocked so you could use it with whatever carrier you
want. It's just that they have the same bootloader as Verizon Pixels do.

On Sat, Nov 11, 2017 at 11:58 PM, <buganizer-system@google.com> wrote:

I don't have any documentations to show you, but when i was on the phone
with Google support, all 3 times, they asked me if i bought my phone from
the Google store and whether i specifically chose the "unlocked" version.
Then they told me that if i made those selections then my phone is suppose
to be bootloader unlockable.

On Sun, Nov 12, 2017 at 12:05 AM, <buganizer-system@google.com> wrote:

Ah ok So this means that unlocked phones are available only in the US and from the Google store.Thank's for the details and the help. I shall try looking into what I can do here. Its just frustrating that the one reason you want the phone and that's never going to work.

sa..., I see your confusion. The Google Pixel 2 is SIM unlocked AND bootloader unlockable (except if you have the above bug). The Verizon Pixel 2 is SIM unlocked (actually all Verizon postpaid phones MUST be SIM unlocked per C band FCC agreement). The Verizon Pixel 2 is NOT bootloader unlockable.

SIM unlocked is also called carrier unlocked. Most people who understand the benefits of bootloader unlocking, understand the difference between the two "locks".

Perhaps you are having trouble with your SIM card and carrier in India? That's an entirely different issue. Perhaps the Pixel 2 does not have all the radio bands for your carrier or your APN is not set correctly.

I will also note that the Verizon version can be found cheaper online both used and new, because Verizon offers discounts on the phone. Resale value is also much lower because it can't be bootloader unlocked. Take a look at resale values on the Pixel 1 on Swappa, unlocked vs. Verizon.

Perhapa the exchange rate was favorable too? Also, if you really value having an unlocked bootloader, then return your phone or sell it and buy the Google version.

There is a small chance someone will find a vulnerability that allows for bootloader unlocking the Verizon version. This happened on the Pixel 1, but it was short lived.

So my  IMEI specifically says NON-VZW on the verizon website,I'm not sure if that means my phone is still a Verizon 2 Pixel. What I think has happened is that they made Kinda Blue model specifically for Verizon in the US and shipped the same elsewhere. And I could have bought the phone cheaper elsewhere but I specifically bought it from the "most reliable" and sort of Google Assured place. I need to find out where to buy a Google version now. I mod ROMs . The only purpose of this phone for me is to have an unlocked bootloader.

sa..., Actually I think that's actually a good thing if it's says NON-VZW. Maybe do some more research on what non-us version exists. I didn't think they are making an international version.

I would actually lean more towards you being effected by this bug/warehousing/staging issue.

Your problem is just like everyone else as a fix doesn't sound like it's in the works anytime soon. BUT, getting a new version from Google is not a sure fire fix either!

And just thinking out loud, if you didn't get your phone from Google, then your beef is with HTC as they provide the hardware warranty? Can someone else chime in on this? Is Google handling all warranty work now since they are renting into the hardware business?

Entering... They did buy the HTC smartphone team for 1.1 billion.

sa..., Looks like you should be covered by Google India since it's officially sold in India:

https://forum.xda-developers.com/showpost.php?p=74403861&postcount=6

@marioqueiroz

Need this guy on the case:

https://mobile.twitter.com/marioqueiroz

I am experiencing the same issue. Pixel 2, ordered from Google Store. Build Number OPD1.170816.010. Ordered on October 29, 2017 and Shipped on the 31.

Contacted Google, they said it is a bug. No Estimated Date for resolution. Case ID [0-1985000019781]

Yes this gives me some hope. However Google is known for its astounding customer support, so in the mean time I'm going to try other possibilities of rooting this. I'll have a chat with the Customer Care again and see if they have anything new to say.

Same issue, ordered October 25th directly from Google, unfortunately booted with a Verizon SIM and now the bootloader is locked and cannot be unlocked, even without the Verizon SIM installed after factory resetting.

Bootloader: mw8998-002.0059.00
Device State: locked

Google Case ID  [0-3223000019753]

Just got my replacement today and "OEM unlocking" is still grayed out and
can't be toggled.


On Mon, Nov 13, 2017 at 12:55 AM, <buganizer-system@google.com> wrote:

Same problem.  Ordered through Project Fi (play store).  Order about two weeks ago, finally shipped and arrived today only to find the same issue.  Contacted Fi support and basically got the same canned answer about we have no resolution at this time.  The rep ended up "assuring" me that the engineers would fix this through a software update.  Standing by for now, but sucks cause I don't wanna get too immersed in my phone knowing it will eventually be reset.

My replacement also has the same problem. Lets hope the third time is the charm and I get a good one.

Same issue, OEM unlocking can't be toggled.

OEM Unlocking grayed out on Pixel 2 (Google version), confirmed version on IMEI.info

Same here. They told me this wasnt a reason in which my phone could be RMA'd. They are letting me refund the phone, so I guess ill buy another and see if its locked.

I got mine RMA'd for this reason. Expecting the replacement today.

Received my RMA yesterday for this reason. Everything works fine now!

Pixel 2, unlocked, bought from google store, OEM unlock is disabled under dev options. guess I should've bought a one plus or sammy. So much for Google, this was their last chance.

Just received a Pixel 2 today. Ordered direct from Google Store. Also cannot toggle OEM unlock. About to call and start the RMA process I suppose.. Ugh
Bootloader: mw8998-002.0059.00 locked
Walleye MP1

Same here had an issue with my original Pixel 2 (unrelated issue 1st unit -current device has a dead pixel on the screen). My original device was purchased directly from Google Store and has no issues unlocking the boot-loader.
Build # OPD1.170816.010

Damn. Just got my replacement for the original phone OEM locked and it's OEM locked as well. Just called support for another RMA and they asked me to hold off for a week or so as a possible software fix is in the works.

I was wondering if anyone has any idea on an ETA for the "update" that's
suppose to fix the OEM unlocking issue.

On Tue, Nov 14, 2017 at 5:00 PM, <buganizer-system@google.com> wrote:

Received one of my Pixel 2's (my other is an XL, still 2 weeks out on delivery) and it's locked. Google wouldn't RMA. Offered to refund and re-order but it's currently sold out and I'm not waiting 5 weeks again (my phones were ordered on Oct. 5th). Purchased directly from the Google Store.

Just curious what security update everyone is on? I just got a Pixel 2 from the Google store and mine is greyed out as well and stuck on Sept 2017 Security Patch. Same day I received an RMA replacement Pixel 2 XL from Verizon and it is OEM unlockable! Very strange but not complaining cuz this replacement 2 XL has a much better screen than my original and OEM unlocked. The Pixel 2 XL is on November Security Patch. Somebody must be messin with the boxes and getting them all mixed up! Or its software related and can be fixed.

#75, I updated my wife's phone to the latest (OPD1.170816.025). Saw it on whatever the OS was before I updated too.

I updated my Pixel 2 (non XL) to the November security patch, and the OEM unlocking is still greyed out.

Google support claimed that I selected the "Verizon SIM" when I ordered the Pixel 2 from the google store. I'm quite sure I did not select that option, nevertheless, I requested and received an RMA for a refund. I ordered another Pixel 2 from the google store, selected "unlocked" and verified with google support that the order was indeed for an UNLOCKED pixel 2. They confirmed that it would be unlocked. I received it in the mail today, did not put in a SIM card, skipped all the prompts for setup. Only entered in my wifi password (did not set up google account) went directly to settings, unlocked developer options, and OEM unlocking is greyed out.

Adding my comment to the list for visability. I have a non-vz Pixel 2 from google that has the OEM Unlocking greyed out. Hopefully the rumors are true a bugfix is in the works.

Add me to the list, support suggested I check back at a latter date for me info, no offer for an RMA so I just returned it for refund.  See ya later!

Im chipping in here to say that I'm affected by this. What can I do?

Le sigh. Guess we are just lucky.

Same issue here. OEM unlocking is grayed out. Can not unlock the bootloader. Pixel 2 bought from Project Fi. Need this fixed ASAP Google.

Same issue. Purchased phone on November 9th from Google Store.

Something of note, my build number is different from the one in the original comment: OPD1.170816.025 . This is still a non-vz unlocked Pixel 2 bought straight from the google store.

Seeing the same issue on my pixel 2 purchased on November 1 from project fi.

I can't toggle the OEM Unlocking option either.

Expected output:
The OEM Unlocking option should be colorized and touching it should move the slider from left to right.

Current output:
OEM Unlocking is grayed out. Touching it does nothing, not even an animation indicating it has been touched.

Purchased from Project fi

Same issue. Pixel 2 64gb purchased unlocked from Google Store on November 13.

Expected output:
The OEM Unlocking option should be available and able to toggle on and off.

Current output:
OEM Unlocking is greyed out. Touching it has no effect.

Same issue here. I purchased my Pixel 2 64GB unlocked from the Google Store on November 14th.

Expected Output:
The OEM Unlocking option should be blue and available to toggle on and off.

Current Output:
OEM Unlocking is grayed out, touching it does nothing.

Same issue with Pixel 2 64GB unlocked from Google Store. Returned for refund for now.

Also having the issue, my case number is 5-6962000019949 . It is a Pixel 2 64 gb which just arrived two days ago on November 14th.

Expected Output:
The OEM Unlocking option should be blue and available to toggle on and off.

Current Output:
OEM Unlocking is grayed out, touching it does nothing.

I'm pretty new to all this, is this something can be fixed with software updates? If it's true that we all have received Verizon Pixels then does that mean software updates will be delayed? Should I send the phone back for RMA replacement?

I have this issue as well. I had to RMA my first Pixel 2 due to it no longer accepting a charge. I was able to unlock the bootloader on my first Pixel 2. I just received my RMA replacement last night, and I am not able to unlock the bootloader on my new Pixel 2.

I ordered mine from the Google Store and specifically selected the unlocked version and my OEM unlock is grayed out as well. This is piss poor customer service from Google. I would expect more from a multi-billion dollar company. I have a 2nd one coming monday so hopefully that one works

change language to english (united states) will be ok.

My replacement arrived and saw that the OEM unlock was still grayed out. Then I realized that I skipped past setup and forgot to connect to WiFi. After I connected, I was able to enable OEM unlock.

I got the replacement for the replacement for the original phone and it also has the bug. Thats three devices in a row with this bug. Seriously Google, what the fuck.

I reported the issue to chat support. Got transferred over to preferred care who said that I did not have a verizon unit and did have an unlocked version from the Google Store. Am awaiting news. Not offered a replacement.

Just got mine today. OEM unlock grayed out on Pixel 2, white, 64 Gb.

My RMA replacement from Google is doing the exact same thing, even without the Verizon SIM in.   Setup once with just wifi, no google account login, still got OEM unlocking grayed with connect to the Internet or contact your carrier.  Also tried wifi+google login, and then finally with the Verizon SIM, to no avail.  Contacted Google and now they confess that RMA replacements are not solving this issue.   There is now a sister thread on xda-developers:  https://forum.xda-developers.com/pixel-2/help/google-store-unlocked-pixel-2-oem-t3700403

My RMA replacement from Google is doing the exact same thing, even without the Verizon SIM in.   Setup once with just wifi, no google account login, still got OEM unlocking grayed with connect to the Internet or contact your carrier.  Also tried wifi+google login, and then finally with the Verizon SIM, to no avail.  Contacted Google and now they confess that RMA replacements are not solving this issue.   There is now a sister thread on xda-developers:  https://forum.xda-developers.com/pixel-2/help/google-store-unlocked-pixel-2-oem-t3700403

Just wanted to let you guys know that there currently isn't even an ETA for
the fix. I've just asked the person monitoring my case and that's what they
told me.

On Nov 16, 2017 11:46 PM, <buganizer-system@google.com> wrote:

Now they're not even accepting RMA for this issue. I just had a chat with their support.
I'm going to wait till next week to see if they come up with an OTA update to fix this crap. If not, I'm returning it.

Same issue here.  I do not want to get a replacement.

I just got my phone today and without my at&t sim straight out of the box, the option is greyed out. This is a bunch of bull. Sandra from support fed me a line of crap and then said I'd have google play credit codes emailed to me. Yeah... Buy my silence you wench! But guess what.... No codes to redeem were emailed. Hello to my fellow disappointed pixel 2 owners

I got a code for credit but still want a fix too!!!

On Nov 18, 2017 05:48, <buganizer-system@google.com> wrote:

I was told I can't RMA so I ordered another phone. The new one had it grayed out. This is ridiculous.

This is bs, as bad as Apple

Same issue here. I purchased my Pixel 2 64GB unlocked from the US Google Store on November 1st.

Expected Output:
The OEM Unlocking option should be blue and available to toggle on and off.

Current Output:
OEM Unlocking is grayed out, touching it does nothing.

I just received my Pixel 2 from Google Store and am also having this issue. Ordered Unlocked version, and got a locked version for my troubles.
Mine did not ship early like a lot of people have reported. In fact, I ordered on Oct. 4, was supposed to ship on Nov 13, but didn't ship until Nov 15 and arrived on Nov 17.
Google Store support and operations is some of the worst I've dealt with. The first line support agents don't seem to know anything about anything. My belief that Google hired only the best is apparently completely off base.

Received my Pixel 2 from Google Store a couple of days back and am also having this issue. Ordered Unlocked version, and got a locked version. Tried factory reset couple of times, still no go.

I ordered on Oct. 7, was supposed to ship on Nov 13, but didn't ship until Nov 15 and arrived on Nov 17.
Google Store support and operations is some of the worst I've dealt with.

Support person suggested my phone is "unlocked" for any network, didn't know what bootloader was. SAD!

Adding my name to this list - would like to be able to unlock my phones full potential

Ordered the unlocked version from Google, received the locked version a few days ago. Opened a support request, was told "we do not have any resolution at this time." Hoping for a resolution before the period of time within which I can return the phone expires. Disappointed that I can't use the phone at all in the meantime, as I'm on the Verizon network and am under the impression that putting in my sim card would basically result in the bootloader being permanently locked, hence I want to unlock the phone prior to connecting to the network.

New Unlocked Pixel 2; OEM unlock grayed out. Ugh.

Confirming: OEM unlock grayed out on Fi Google Pixel 2, white, 64 GB.

Same issue for me, received my Google store unlocked Pixel 2 on Friday and OEM Unlock is grayed out.

aaaaand...another.  No help from Project Fi support.  Basically, just wait for it, we'll fix it...going to give it a little time before I return for good.

I ordered two unlocked Pixel 2 from the Google store on 11/16 and received the phones 11/17.  OEM Unlock is grayed out.  Support said that Google is aware of the issue, working on a fix, but has no timeline.  Support issued RMAs for the phones.

So I returned my device, Google apparently provides Customer Support in India since they consider themselves the seller. Waiting for the Support team to revert.

Please factory reset your device and make sure it connected to the internet during setup as this issue has been resolved.

Factory Reset:
Settings -> System -> Reset Options -> Erase all data (factory reset).

There goes my afternoon. If it isn't really fixed I'm gonna be pissed. It takes a shitton of time to setup a new phone.

Same, now I know what I'm doing tonight.

I just reset my phone, confirmed the issue has been fixed!  Huzzah!

i just received my pixel 2 today and its still locked. ill do a factory reset but it literally just came from the factory sooo. idk. here goes nothing

i have unstared  . disregard my previos comment. not sure why doing a factory reset after setting it up fixed it not installing any updates but sweet. it works now oem unlocking unlocked

As a developer, I'm curious as to how this was fixed. If it was AOSP, I'd appreciate a link to the PR/commit. Thanks!

Can confirm that the issue is corrected with a factory reset!

I can also confirm this issue is fixed was fixed with a factory reset on my Google purchase Pixel 2 phone.   It would be really nice if you could pretty please tell us what happened and how it was fixed, barring anything that releases any security concerns about how the boot loader is locked down on this phone.

I can also confirm that performing a factory reset fixes the issue. Would
have liked it if an OTA was made for the fix so we wouldn't have to set up
the phone all over again. Either way, just glad that Google was able to
solve the problem!

On Mon, Nov 20, 2017 at 9:34 PM, <buganizer-system@google.com> wrote:

@"Brent Rodriguez  <mentose457@gmail.com>" #120
The point of flipping the "Allow OEM unlock" switch is to 'fastboot oem unlock' which will wipe data anyway so you have to setup the phone again.
Restore from cloud works really well and will restore all your settings so it takes no time to setup the phone back to the previous state.

Nice, factory resetting didn't do the job a few weeks ago, but it works for
me now.

On Tue, Nov 21, 2017 at 11:20 AM, <buganizer-system@google.com> wrote:

@ts...@google.com, Can you provide some more detail about this bug and the fix? Was this a inventory issue or a bug in AOSP that only effected the Pixel 2 Mini?

Also, most people do NOT setup their phones first when they know they are being unlocked in fastboot. So people effected by this bug NEEDED a working phone so they set it all up, just to have it factory reset and setup again with the fix. So the wait was an inconvenience and having to factory reset was another on their only working phone.

Also it's fastboot flashing unlock now :) fastboot oem unlock was the old command for Nexus devices.

Reset fixed my issue, thanks.

Hola el mío es de Verizon Píxel 2 XL ,me lo trajo un amigo de Texas ,Austin, i biene con el OEM   ,bloqueado como puedo desbloquear,

Un saludo
Rafael Santacana
Barcelona, catalunya

A factory reset has resolved my issue as well. Thanks for the quick response time Google!

Hello all, is this a confirmed fix by Google?
With my replacement unit (returned) I did set it up on network, updated software and factory reset but still was unable to unlock.

to #135, did you do this before or after post #119 was made?

Just did a factory reset myself and it's still disabled :(

to #136 before post #119. Google sent me a replacement phone and all good now, needed to do nothing other then turn on developer options.

#119 -- I've just found the same issue, with a fresh replacement device from an RMA.  Here's the sequence for me -- I'm on the November patchlevel.

1) Boot a fresh phone, skip setup, etc. Enable developer options, then mash 'enable OEM unlocking'. Confirm and hit 'enable'.
2) Just for laughs, reboot the device. Go to developer options. Note that 'enable OEM unlocking' is still checked.  (This step does not change the outcome.  You can skip it or not.)
3) Reboot into the bootloader, by holding power, selecting 'restart', and holding vol-down.
4) 'fastboot flashing unlock' Get the messages:

joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s

4) Reboot into the OS. Go to the developer menu. "OEM unlock" is greyed out, with "connect to the internet or contact your carrier". Argh!
5) Factory reset and do it all over again...

I've tried this with multiple factory resets, and the issue persists.  I have been connecting to the network on initial boot each time.

***

I did an experiment to see exactly what conditions cause OEM unlocking to be greyed out, and what changes when I do.

Here's a little more detail.  I just updated to 8.1, factory resetted, and connected to the network as I went, etcetera.  I unlocked the developer options, and now 'OEM unlocking' is blue (checked).  When I do an 'adb shell getprop | grep oem', I see:

joshua@bruges:~/phone/pixel2$ adb shell getprop | grep oem
[init.svc.oemlock_bridge]: [running]
[init.svc.oemlock_hal]: [running]
[ro.oem_unlock.pst]: [/dev/block/platform/soc/1da4000.ufshc/by-name/misc]
[ro.oem_unlock.pst_offset]: [6144]
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [0]

I'll uncheck it, while doing a logcat, and when I do that, I get:

[...]
12-09 11:42:38.595   747   747 E /vendor/bin/hw/android.hardware.oemlock@1.0-service: Parse: Incorrect message command
12-09 11:42:38.596   747   747 I /vendor/bin/hw/android.hardware.oemlock@1.0-service: Running OemLock::setOemUnlockAllowedByDevice: 0
12-09 11:42:38.597  1125  3962 I OemLock : Updated device allows OEM lock state to: false
12-09 11:42:38.598  1125  3962 I OemLock : Update OEM Unlock bit in pst partition to false
[...]

No change in the properties after doing that.  I'll power the device all the way down, now, and power it back up.  In the developer options menu, 'OEM unlocking' is still unchecked.  No change in the 'getprop' output.  Powering the device all the way down, and powering it back up while holding voldown, I do a 'fastboot getvar all', and see:

joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot getvar all 2>&1 | grep 'secure\|lock\|cid'
(bootloader) have_oem_lock_id:yes
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) cid:00000000
(bootloader) secure:yes

Reboot into the system, and 'OEM unlocking' is still unchecked.  Reboot into the bootloader again, and this time try to unlock (which we expect to fail, for of course it is not unlock-enabled):

joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [  0.001s]
finished. total time: 0.001s
joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s

But this time, 'OEM unlocking' is greyed out, with the 'contact your carrier' message!  No change in the 'getprop' output, no change in the 'getvar' output.

***

I tried two more experiments.  First, I did a factory reset from recovery, then did a 'flashing unlock', then ran through initial setup, skipping wifi.  "OEM unlock" was greyed out.

Then, I did another factory reset, did a 'flashing unlock', and then ran through initial setup again, this time with wifi turned on.  'OEM unlock' was not greyed out, and was set to 'off' (as I had left it from the previous experiment).  I flipped it to on, then tried to unlock, and the mystery gets weirder:

joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [  0.000s]
finished. total time: 0.000s
joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.002s
joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [  0.000s]
finished. total time: 0.000s

The box is greyed out in developer settings.  When I reboot, 'get_unlock_ability' is still 1, but 'Flashing Unlock is not allowed'.  And for bonus bizarre points:

joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing unlock_critical
...
FAILED (remote:         Device already : unlocked!)
finished. total time: 0.000s
joshua@bruges:~/phone/pixel2$ ~/phone/platform-tools/fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s

But I cannot 'fastboot flash bootloader', even though we are 'unlock_critical'.

***

I have the device sitting on my coffee table here in Mountain View, and I can drop it by this week if you want it.  But otherwise, I'll need to send it back to the Google Store to RMA it (...again...) soon.

#139 I'm experiencing the same behavior as you. Only thing I'll add is that running fastboot flashing lock_critical while in this state will actually unlock the bootloader, lol.

Apparently the issues persist. I'm on 8.1 and this is on a Pixel 2 I just received today.

#139 exactly same situation ! Should we wait for Jan 2018 security patch ? Or Updated bootloader version ? Google are you listening ?

FWIW, I sent back my (returned-RMAed) device (phone #2); the one that I got
back (phone #3) works fine.  (This also means that the device is no longer
sitting on my table.  Googlers, if you are capable of tracking it by the
RMA, this is RMA01472574 / IMEI 357537082967779.)

#140, was this to mean that 'fastboot flashing lock_critical' solved the
problem entirely for you?  Bizarre.

On Sun, Dec 17, 2017 at 7:40 AM, <buganizer-system@google.com> wrote:

#142 Not exactly.

I WAS able to unlock the bootloader by issuing the counter-intuitive lock_critical command, but there are still two problems that I have no resolution for:

1) My device always thinks that it has achieved unlock_critical regardless of any setting/state. If I turn off the ability to unlock via the bootloader (via the "OEM unlocking" switch) and verify that get_unlock_ability = false and sys.oem_unlock_allowed = 0, I can always run a fastboot flashing lock_critical to toggle between unlocked/locked. Running fastboot flashing unlock_critical always returns the same result (Device already : unlocked!) regardless of the state of the bootloader (locked/unlocked) or the OEM unlocking switch.

2) Running fastboot flashing unlock always returns "Flashing Unlock is not allowed" despite the fact that get_unlock_ability = true and sys.oem_unlock_allowed = 1

There's still either a bug or defective devices out there, and I'm not sure whether to RMA or simply return the device and move on to something else. These "quirks" are a bit more numerous than I'm comfortable with for a flagship device.

#142 Did you unlocked on 8.1 latest update ? December patch or November patch ? I think its bug with bootloader version 66.00 !

#144 Yes, the behavior I described is what I found on the 8.1 official release. When my device was on the 8.0 November patch I experienced exactly what #139 did. It could be a bug, but if so then there was/is a problem with both releases, not just the latest.

I'm leaning more towards this being a defect in a number of devices, but Google support is giving me a bit of a runaround at this point and hasn't sent me a new device (despite the fact that this one is 3 days old) so I can't confirm. #139 ended up saying he resolved his issue with yet another new device, so that seems to support this.

Factory reset didn't make oem unlocking available

yes i also test with 8.1 my pixel 2 xl by ee Factory reset didn't make oem unlocking available :( any help for fix this ishu wellcome

hey guys. Francky on Pixel2 XL, any success stories anyone can tell?

be good,
F.

can any one help us with this
what the benefit of have pixel the pure android and can't unlock the bootloader
really i will get my iPhone back

After factory reset, my Pixel 2 XL "OEM unlocking" is still disabled. Anyone can help?

Many thanks,
Z

Really now Google becomes Apple like?i have just bought my pixel and cant unlock bootloader also, running lastest 8.1 oreo with january security patch.

Come on help us

Phone: Pixel 2 (unlocked)
Android 8.1.0 OPM1.171019.013
Purchased from Google Store (non-Verizon version)

Here are the 12 steps to consistently reproduce this issue for me (verified on two different Pixel 2's).

1. Factory reset
2. Enable Wifi continue set up, agree to TOS, then Settings>About phone>enable developer options
3. Navigate to Developer Options.  Enable USB debugging and OEM unlocking
4. At this point, the phone can be rebooted, powered off, or left to continue updates and the "OEM unlocking" toggle will still be active.
​5. Poweroff phone and enter fastboot mode (power + vol down)
6. Connect the phone via usb-c to pc (linux in my case, but verified on Windows 10)
7. Ensure device is detected
# dmesg
[snip]
[241703.655623] usb 1-2: Product: Android [XXXXXXXXXXXXXX] usb 1-2: Manufacturer: Google
[241703.655632] usb 1-2: SerialNumber: FAXXXXXXXXXX
8. check with developer sdk that the device is recognized
# ./fastboot devices
FAXXXXXXXXXX    fastboot
9. query device info
# ./fastboot oem device-info ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true OKAY
[  0.025s] finished. total time: 0.025s
10. Attempt unlocking (via oem unlock or flashing unlock).  Both will fail
# ./fastboot oem unlock ...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.010s
# ./fastboot flashing unlock ...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.009s
11. Reboot phone
# ./fastboot reboot rebooting...
finished. total time: 5.035s
12. Navigate back to Developer Options to see that OEM Unlocking is now greyed out

No solution to date.

Anyone that is still having trouble unlocking their phones, please file a new issue and provide a link to the newly created bug here.
Alternatively, users can try contacting the support team at: https://support.google.com/pixelphone/answer/7109524?hl=en for an RMA.

I also had this problem, exactly as #152 described, and fought with it for hours.

What fixed it for me was, instead of trying to unlock it with fastboot, I did issued the command "fastboot flashing lock_critical" ( I know, I know ). The popup about UNLOCKING appeared, and when I confirmed, I got the device correctly unlocked and phone erased.

I guess that's some weird software bug Google will fix soon.

I've had the phone for a couple of months now and just went to unlock, noticed the option was not allowed.

I factory reset the device and still can't oem unlock.

This has not been fixed or is a variant of the problem. OEM Unlock is enabled but as soon as fastboot flashing unlock is issued it reports failure and the device is still locked and OEM Unlock is now greyed out. Factory reset will reenabled OEM Unlock and back to square one.

Details in https://issuetracker.google.com/issues/73217322#comment1

I'm having the same problem. Google Pixel 2 XL that I've bought Unlocked from the Google store. "OEM unlocking" is greyed out and can't be toggled.

Expected output: Touching "OEM unlocking" should allow it to be toggled.

Current output: Touching "OEM unlocking" doesn't do anything.

I also had this problem,I also had this problem,buy it at google pay ,OPM1.171019.019, Feb 2018,) Power on the device and let the android boot.

2) after successful boot Go to Setting -> Developer Option -> OEM Unlock
3) adb reboot bootloader
4) After successfully boot into BOOTLOADER mode perform : fastboot flashing unlock or fastboot flashing lock_critical
5)  It both  fail.
6) Restart the device and boot into normal android.
7) You will see OEM unlock option permentatly disabled ( Greyed Out )
i Strongly ask to solve bug

I also had this problem, exactly as #152 described.

For everyone who is still suffering from the OEM unlocking issue in Android 8.1, please star the new ticket so hopefully the priority of fixing this bug will become higher. Thanks!
https://issuetracker.google.com/issues/73217322

my google pixel xl does not release the oem unlock. anyone else with this problem? Any solution?