[Google Pixel 2 XL Questions & Answers] simplepinoi177:
Thanks for the reply. I do appreciate it.

To answer, yes, I have to connect to the internet and WIFI first... I actually do that, and then the toggle does enable and turn blue. The weird thing is that, although it is blue and is able to be "toggled", it won't "unlock" -- whether using the direct fastboot.exe commands directly or Deuce's tool (which is essentially an advanced for of the flash-all batch script file [.bat]) -- because, for whatever reason and even if it is blue and toggled "OEM unlocking" enabled, the bootloader would still be locked and refuse to unlock, even if...

Some questions [MENTION=6431541]Droid_Nut[/MENTION] :confused:... You had a "...phone that was stolen out of the box"?!?! But it was "...direct from Google", so it was stolen after being delivered? or stolen "out of the box" from the warehouse/shipping center and you were sent an empty one? And if so, how did you convince Google about all of this? If not, did you get the shipper/shipping company to cover the cost? Also, good to know about the IMEI and starting with 35, but, while reading about this issue online, it seems the only sure-fire way to unlock the phone is to have one "new in box" -- so getting one from Swappa should be successful, as it is...

Now, I'll continue on to an update on this issue...(and a request for some advice...)

So, after bringing it in to uBreakiFix, and although they were able to switch out the motherboard and have the phone up and working, they were informed by a "Google contact" that, in essence, the replacement motherboards are not unlockable -- even if it displays different in fastboot commands and oem unlocking. So, left with very limited options, I was planning on contacting Google support and have them switch it with an RMA and desperately try that route. But here's where further complications come in...

After contacting Google support, and giving them a bull**** reason to attempt to get an RMA (since it's technically a perfectly working phone, but the unlocking ability is not working and/or has "stated" that all refurbished phones are purposefully fashioned blocking that ability), after entering the new IMEI that came with the new motherboard, they found that it isn't "registered in the system"! It makes sense, since the IMEI came on/with a part (motherboard) and not necessarily with a phone (what would be properly processed "from the factory"), and I don't really know how spare "refurbished" parts work, but maybe those recycled and/or spare parts don't get "processed" or their number is erased/scrubbed from the system... :shrug: In any case, without the IMEI in the system, how can they process a RMA, or even be expected to...? But...that's the dilemma I'm at as it is...

So...it seems pretty hopeless now...the last, final ideas I'm pondering is somehow explaining the situation to Google support and let them know that I had it serviced at a "certified service center" which is a uBreakiFix location and that's why it doesn't register "in the system" -- but the caveat is convincing them (usually a outsourced call-center) to even if there's a working device as well as many of them are mis-educated on being allowed to unlock one's bootloader. Also, I ran into issues about them wanting a "proof of ownership", but how can I do that with a repaired/refurbished IMEI? Will being able to provide a receipt of service help any, you think? Or attempt and beg/plead with the uBreakiFix to contact Google and explain the situation and/or get the & their IMEI's registered to their system...?

As you can tell, I am pretty desperate and "grasping at straws" here, so -- if that can be kept in mind -- any thoughts or ideas?