Another day, another Google Pixel 2 problem: Many users can't unlock their bootloaders
OEM unlocking is greyed out on some Pixel 2 units, and it's not supposed to be
It would seem that a number of Google Pixel 2 units purchased straight from the Play Store and not some shady reseller are arriving with bootloaders that can't be unlocked. As you might imagine, the issue first popped up on XDA's developer-centric forums, where multiple users bemoaned that they are unable to unlock the bootlaoders of their new devices though they are supposed to be able to do that by default, as Google has had a rather lax stance on bootloaders ever since early Nexus days. Roughly 40 reports on XDA and over a dozen on Google's issue tracker have claimed to have the issue, which seems to be exclusive to the smaller Pixel 2 that HTC manufactured.
Almost all users that have reported the issue are also claiming that they are already pushing Google for an RMA.
While regular users will have zero problems with their Pixel 2 devices being locked down, tinkerers and developers alike absolutely need to have a device with an unlockable bootloader in order to obtain root access and meddle with their devices.
We've already reported about some Pixel 2 XL units which came with no operating system out of the box, a few devices that exhibited weird screen flash when locking, an unpleasant microphone issue, and finally, peculiar problems with visualizing LED lights on video. Those add up to the already fixed, but nonetheless major OLED burn-in display issues as well as the clicking audio in the earpiece when talking on the phone.
Overall, not a very good quality control track record for Google's latest devices.