Unlock Bootloader on Verizon Pixel 2 [CONFIRMED]

[Shiestie]

I'm not entirely sure if this is old news or not, but if you have the Verizon Pixel 2 like I do, and have been depressed that we can't unlock the bootloader thanks to the Evil Verizon people, and want to stick it to the Evil Verizon people and still Unlock the Bootloader for whatever purpose (Root, TWRP or Custom recovery, Custom ROM, Kernel, etc...) we are in luck! :good:
Even though the Evil Verizon people have Disabled the OEM Unlocking in Developer Options.
There is a fastboot command that bypasses the disabled oem unlocking. :victory:
This only works for the Pixel 2 not the Pixel 2 XL variant.

Thanks to @b00ster23 for the following;

Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294

Big Thanks goes to @D3RP_ for finding the command.

***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.

As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method.

Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota

Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0

Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.

To Unlock your Verizon Pixel 2, follow the steps below..

1. Install ADB/Fastboot Drivers
2. Enable Developer Options
3. Enable USB Debugging in Developer Options
4. Plug Pixel 2 into PC
5. Open a Command Prompt window;
6. In Command Prompt, type

   adb start-server

   and hit ENTER
   If you see * daemon started successfully *
   continue to next step
7. In Command Prompt, type

   adb devices

   and hit ENTER
   If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
   continue to next step
8. On Pixel 2 - Allow PC for USB Debugging
9. In Command Prompt, type

   adb reboot bootloader

   Once your Pixel 2 has rebooted into the bootloader
10. In Command Prompt, type

    fastboot flashing lock_critical

    and hit ENTER
11. Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.

If you have successfully unlocked your bootloader on reboot you should see;

 

[JAYNO20]

Yup. Just did this with my Verizon Pixel 2 and it went through swimmingly.

 

[nes4r2]

OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.

 

[b00ster23]

Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294

Big Thanks goes to @D3RP_ for finding the command.

***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016 or LATER, you will no longer be able to run the command. And downgrade is not available at this time.

As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method.

Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota

Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) or 8.1.0 (OPM1.171019.011, Dec 2017)The command is not available on 8.0

***UPDATED 6/11/18***
https://forum.xda-developers.com/showpost.php?p=75945799&postcount=167 As of 3/19/18 People are still finding VZW Pixel2 phones in stores with the December patch. Not sure if VZW/Google are shipping newer patched phones at this time, but a good sign to users still looking for a phone they can unlock.

https://forum.xda-developers.com/showpost.php?p=75908059&postcount=1 Another user confirms that his phone was shipped "It was still on 8.1.0 (OPM1.171019.011, Dec 2017)"

***UPDATED 6-9-18*** https://forum.xda-developers.com/showpost.php?p=76757116&postcount=239 Another user received the 128GB White variant of the Pixel2 with the December build and was able to unlock successfully

***UPDATED 6-14-18*** https://forum.xda-developers.com/showpost.php?p=76795831&postcount=265 Users are are now getting phones directly from Verizon and the store with .016 or later factory installed.

To review, the command referred in the OP is available in 8.1 and not 8.0. Which means that you can upgrade to a compatible version of Android OS to take advantage of the command. However, your phone CANNOT be on ANY build OPM2.171019.016 or later, as the command was patched. Please see the attached table. Some users have been able to find phones in stores, and from surplus. However some newer phones are now being shipped with the latest security updates (OPM2.171019.016 and older.)

The best way to ensure you can unlock the BL on your VZW PIX2 is going to the store and physically verifying the patch revision on device.

 

[steejo]

OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.

I second this. After having read through the instructions for them both, it's still incredibly hard to understand what needs to be done.

 

[dobbs3x]

I thought you didn't want to use the unlock critical command on pixel 2 and only the xl?

 

[b00ster23]

I thought you didn't want to use the unlock critical command on pixel 2 and only the xl?

Not sure where you heard NOT to use the unlock_critical_ command. However, if there is a reason not to, please post your findings. Keep in mind this is for the VZW Variant ONLY that is being referenced. (See OP)

 

[Shiestie]

OP any chance you can include step by step instructions on how to load TWRP and magisk? I did mines already but I was a bit confused with loading (pushing) twrp.img via adb and also installing magisk.

I'll write up a little how to on flashing TWRP and Magisk first thing tmrw morning and add it to the original post.

 

[b00ster23]

I'll write up a little how to on flashing TWRP and Magisk first thing tmrw morning and add it to the original post.

I would add disclaimers....links to other posts where information is already available.... Reference this post is for unlocking VZW pixel2 only.... Give credit to the XDA user that found the command...

Personally it's difficult to try and hash thru data in a forum post when the scope of information is too broad or double-posted. I like to have steps and supporting discussion for each step... My 2 cents about guide posting

 

[SoloTSi97]

Ordered my VZW Pixel 2 on 12/31, received it yesterday. It automatically updated to the January OTA. This morning, I ran the above steps and the bootloader is now unlocked. Easy Peasy. Thanks @Shiestie for the guide and @D3RP_ for the discovery!

 

[D3RP_]

Ordered my VZW Pixel 2 on 12/31, received it yesterday. It automatically updated to the January OTA. This morning, I ran the above steps and the bootloader is now unlocked. Easy Peasy. Thanks @Shiestie for the guide and @D3RP_ for the discovery!

Oh. My. God. AAHHHHH! Could you go over to My thread And post a screenshot (cover your serial) and a picture of your bootloader screen?

 

[Slapbox]

I'm trying this on a Pixel 2 which I received today (have not connected it to any network yet to ensure I avoid OTAs) but when I run fastboot flashing lock_critical I just get: FAILED (remote: Device already : locked!)

Any ideas? Thanks!

---------- Post added at 11:04 PM ---------- Previous post was at 10:54 PM ----------

According to this thread, you need the Android 8.1.0 OTA before you can unlock it. https://www.reddit.com/r/GooglePixel/comments/7ms5ke/verizon_pixel_2_bootloader_unlock/drxs086/

UPDATING TO 8.1 LET ME UNLOCK IT!

 

[wormy123789]

Worked for me as well, thanks for the post

Sent from my Pixel 2 using Tapatalk

 

[SoloTSi97]

Oh. My. God. AAHHHHH! Could you go over to My thread And post a screenshot (cover your serial) and a picture of your bootloader screen?

Will do.

 

[Ozzy0708]

Just tried it and it worked fine for the January patch!

 

[dobbs3x]

Not sure where you heard NOT to use the unlock_critical_ command. However, if there is a reason not to, please post your findings. Keep in mind this is for the VZW Variant ONLY that is being referenced. (See OP)

It says it on the google developers website here ----> https://developers.google.com/android/images

scroll down a little and you will see this --->


" If necessary, unlock the device's bootloader using one of the following methods:

If you are updating a Nexus or Pixel device that is manufactured in 2015 or later (for example, a Nexus 5X, Nexus 6P, Pixel, Pixel XL, Pixel 2 or Pixel 2 XL device), run this command:

fastboot flashing unlock
Note: the 'flashing unlock' command is only available with fastboot version 23.0.1 or later. The latest available version of fastboot can be downloaded from SDK Platform Tools.
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.

For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:

fastboot flashing unlock_critical
If you are updating an older device, run this command:

fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)

See Unlocking the bootloader for more detailed instructions. "

 

[b00ster23]

It says it on the google developers website here ----> https://developers.google.com/android/images

scroll down a little and you will see this --->


" If necessary, unlock the device's bootloader using one of the following methods:

If you are updating a Nexus or Pixel device that is manufactured in 2015 or later (for example, a Nexus 5X, Nexus 6P, Pixel, Pixel XL, Pixel 2 or Pixel 2 XL device), run this command:

fastboot flashing unlock
Note: the 'flashing unlock' command is only available with fastboot version 23.0.1 or later. The latest available version of fastboot can be downloaded from SDK Platform Tools.
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.

For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:

fastboot flashing unlock_critical
If you are updating an older device, run this command:

fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)

See Unlocking the bootloader for more detailed instructions. "

Interesting. I may take some time later to understand exactly what the command is intended to do. I have a feeling that the command was probably intended for an lock/unlock to other areas, but because of BigRed's config the phone defaults to the bootloader unlock option first. It's like giving the command to upgrade windows, and the setup displaying a format option without actually giving the format command. Speculation here...

Either way... Tick Tick Boom goes the dynamite

 

[robocuff]

Interesting. I may take some time later to understand exactly what the command is intended to do. I have a feeling that the command was probably intended for an unlock to other areas, but because of BigRed's config the phone defaults to the bootloader unlock option first. It's like giving the command to upgrade windows, and the setup displaying a format option without actually giving the format command. Speculation here...

Either way... Tick Tick Boom goes the dynamite

You aren't using fastboot flashing unlock_critical to unlock the verizon Pixel 2. It's fastboot flashing lock_critical. Either way, yes, it shouldn't do what it does.

 

[BDragonD24]

I can confirm that it worked on mine this morning. I just used the fastboot flashing lock_critical command I found in the article that was posted out on the main site. Hate having to put all of my stuff back but it was worth it. That said, can I leave the standard recovery on the phone and continue to get VZ updates and not have it relock the bootloader? Or should I definitely install TWRP ? If I do that will I still get OTA updates or will I have to start doing them manually?

 

[b00ster23]

You aren't using fastboot flashing unlock_critical to unlock the verizon Pixel 2. It's fastboot flashing lock_critical. Either way, yes, it shouldn't do what it does.

Correct... I should have stated lock not unlocked...edited