Question 'fastboot flashing unlock' just brings up command list instead of unlocking

[rajalot]

Hey fam, hope you've been keeping well and safe.
I recently bought the Pixel 6 Pro (so happy with it!) and am currently in the process of rooting it.
It's a fairly simple process, and I've done it with all but I'm not sure what's going wrong at the initial unlocking the bootloader stage.
OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no avail.
It just won't unlock, and instead just gives me prompts of commands.
I've attached the screenshots.
What am I missing/doing wrong? Thanks!

 

[Alekos]

are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?

run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then

you can also just go to Android's Flash Tool to unlock the device:

Android Flash Tool

flash.android.com

 

[rajalot]

are you in fastboot when you are running these commands? boot into fastboot. type the command ' fastboot --version , what version does it output?

run fastboot devices command so your devices appears, then run the unlock command again. make sure you are you using latest platform-tools (not mininal adb etc). also reinstall the driver just in case. then

you can also just go to Android's Flash Tool to unlock the device:

Android Flash Tool

flash.android.com

Thankyou so much for your quick and really helpful reply!

So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.

The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.

 

[Alekos]

Thankyou so much for your quick and really helpful reply!

So I've investigated further, and re-installed all the tools/as you mentioned above - still no avail.
There does seem to be some sort of an issue as the fastboot version command responds back with 'version unknown'.

The Android Flash Tool looks like the best solution (didn't even know it existed, so thanks for that!) but I'm unsure how to proceed with it in order to unlock the bootloader (from what I'm gathered you need to have an unlocked bootloader before using it?)
I'm assuming you deselect the 'lock bootloader' option so that the tool unlocks the bootloader and then doesn't relock it? I've attached a screenshot to just check as well.

yeah you need to have OEM Unlocking enabled to use Google's Flash Tool. if you don't need any data, just enable these options in the flash tool: Wipe and Force Flash Partitions. That will unlock the bootloader and wipe/reflash Android. Enabling the "lock bootloader" option will re-lock the bootloader but since you are rooting it, leave it unchecked.

But you should look into why Platform-Tools isn't working on your system. Here are instructions on how to set it up (make sure to remove all other platform-tools)

there's also Nexus Tools from Github (developed my a known tech journalist)

 

[roirraW "edor" ehT]

@rajalot besides what @Alekos said, I always go straight to the source for the latest SDK Platform Tools every time I flash anything. Also, Get the Google USB Driver (this is for Windows). Note, a recent experience. I have a Samsung tablet and have the Samsung USB drivers installed. This driver worked perfectly fine for my Pixel 6 Pro too for the last two months, but for June the full factory image would error out trying to flash until I uninstalled Samsung's driver and went back to Google's. So if you have any other device USB drivers installed than Google's, you may have to uninstall those and install Google's.

But yeah, as @Alekos said, the site Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own) will get you what you need too although if there's a conflicting driver, you would still have to solve that.

 

[Nergal di Cuthah]

I'm going out on a limb but is this a Verizon p6p?

 

[roirraW "edor" ehT]

I'm going out on a limb but is this a Verizon p6p?

I hope @rajalot updates us, although they said they did enable OEM Unlocking (and seem to be indicating that they have since re-disabled and re-enabled it, although that can be interpreted differently), which would usually indicate that they're not using a Verizon device. Weird, huh? I'm guessing the Platform Tools version is the culprit, but I'd like to hear back to confirm.

OEM Unlocking & USB Debugging is enabled - I've tried to deactivate/reactive it, used different ports etc. but to no

 

[SchWeinSAuG]

bump!

well i had exactly the same issue with new pixel 6a.
installed latest google driver , latest platform tools... no luck

Nexustools did the trick for me instantly
thanks @Alekos for this share!!