Develop Bugs

Verizon Pixel Unlocked Bootloader Question

Just got my pixel xl today, unlocked immediately. Question is if i update the bootloader from the factory images, am i going to lose my unlock or will this stick until i manually lock it (which i won't )? Thanks!

It will stick, no problem. Update away.

So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?

danielson2047 said:
So just to clairfy because i'm paranoid about these things, I can run the flash-all script for the Feb update and my bootloader will remain unlocked correct?
Click to expand...
Click to collapse
Correct. Your bootloader will remain unlocked, unless you execute the following command: fastboot oem lock

With the Verizon bootloader, I used Depixel8 how do I work with the boot slots? I have been modifying since the LG ally but the table has changed and I don't want to end with a brick. Could I flash the bootloader to two slots?

Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.

JU57US said:
Safest thing to do is to dePixel8 right off the bat, and then take an OTA before you do anything else. The OTA installs on the other slot, guaranteeing that you have a bootloader on both slots before you start monkeying around.
Click to expand...
Click to collapse
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?

palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
No, unfortunately not.

I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.

Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
No it wont relock at all. ONly way for it to relock is to run the command for lock through download mode.

Falargi said:
I don't know if this is the right thread but here's my question...I have a pixel XL from Verizon with unlocked bootloader, not rooted (yet). If I were to factory reset it, will the bootloader be relocked? I don't want to take the chance since I already took the latest OTA. And now that I'm asking questions can someone point me to the right place for step by step guide to root? I don't have much knowledge but I can follow directions...Lol. any help will be greatly appreciated.
Click to expand...
Click to collapse
Follow this guide, it's in the guides section
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886

The only way to relock your bootloader is if you type "fastboot flashing OEM lock" once you have unlocked it, never never never relock it (VZW models only) only lock it if you need to do a RMA. Once unlocked you can flash whatever factory image your heart desires.

palvarez05 said:
my phone came stock with NMF26U, is a verizon model, anyway to downgrade and unlock the bootloader?
Click to expand...
Click to collapse
Are you positive that it had had to build out of the box? Or did it simply get upgraded before you checked? Either way you cannot now unlock the bootloader, but it is worthwhile to note whether or not Verizon is updating the phones before boxing them and shipping them. Check the side of your box your phone came in, to see the original build number that the phone had on it when it was boxed up.

Updating Verizon Pixel unlocked bootloader with depixel8

I want to update everything except leave the bootloader on 7.1. Will this work?

LoliSmith said:
I want to update everything except leave the bootloader on 7.1. Will this work?
Click to expand...
Click to collapse
Why would you leave the 7.1 bootloader? As long as you're unlocked, you can flash the whole factory image...
Cheers...

5.1 said:
Why would you leave the 7.1 bootloader? .
Click to expand...
Click to collapse
Because Verizon. I want to be able to relock but not lose the ability to unlock again.

LoliSmith said:
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
Click to expand...
Click to collapse
You should do some reading. It doesn't work like that. If you ever lock your bootloader you will never be able to unlock it again. No reason to lock it anyways.

aholeinthewor1d said:
It doesn't work like that. If you ever lock your bootloader you will never be able to unlock it again. No reason to lock it anyways.
Click to expand...
Click to collapse
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.
Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.

im pretty sure you have to manually relock the bootloader,so updating to 7.1.1 shouldn't matter.
They cant relock your bootloader through software is what i was told by depilxel 8 developer.
I am updating to 7.1.1 right now just to get back to factory state need google support.
cant be reached on most custom roms.
No current stock rooted roms exist,so fresh start is needed.

LoliSmith said:
Because Verizon. I want to be able to relock but not lose the ability to unlock again.
Click to expand...
Click to collapse
As soon as you update to 7.1.1 and you are locked, you will not be able to unlock again with depixel8. I don't care if you have a bootloader from 2 years ago. You probably should decide once and for all if you want the device secure and locked or unlocked. Otherwise at some point you will be in a pickle.
Sent from my Pixel using XDA-Developers Legacy app

There's always a way to find out. Let us know how it goes.

You should not be locking you're bootloader if it's not necessary. And depixel8 pushes stuff to system in order to enable allow oem unlocking. These things may not work on newer systems regardless of the bootloader version.

LoliSmith said:
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.
Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.
Click to expand...
Click to collapse
Your OP implies you can update everything else except the bootloader leaving you free to lock and unlock whenever you want which is 100% not true. There are new threads about this every week all the info is there. If you are on 7.1 you can unlock with dePixel8. Yea technically you could relock and unlock again ONLY while on 7.1 but there is 0 reason to. If you aren't 100% stock when locking you are going to have issues. Also if you're phone installs an OTA while you have the bootloader locked then you are 100% screwed and won't be able to unlock again. Either unlock it and never lock it again or don't bother. You're making something very simple overly complicated.

bobby janow said:
As soon as you update to 7.1.1 and you are locked, you will not be able to unlock again with depixel8.
Click to expand...
Click to collapse
Has anyone done this without updating the bootloader or are you just speculating?
bobby janow said:
I don't care if you have a bootloader from 2 years ago.
Click to expand...
Click to collapse
What are you basing this on? Has anyone every updated everything except the bootloader and then relocked or are you just speculating?

LoliSmith said:
Has anyone done this without updating the bootloader or are you just speculating?
/QUOTE]
Nope, we are all waiting for you to tell us how it goes.
Click to expand...
Click to collapse

aholeinthewor1d said:
Your OP implies you can update everything else except the bootloader leaving you free to lock and unlock whenever you want which is 100% not true. There are new threads about this every week all the info is there. .
Click to expand...
Click to collapse
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
aholeinthewor1d said:
Also if you're phone installs an OTA while you have the bootloader locked .
Click to expand...
Click to collapse
I never take OTAs so that isn't an issue for me.

LoliSmith said:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
I never take OTAs so that isn't an issue for me.
Click to expand...
Click to collapse
You can't.. it doesn't work like that. Go ahead and try if you want. There are countless threads about the bootloader. With all the knowledgeable​ people here do you think they somehow just overlooked something so simple? There are 5 bootloaders total actually. Once you install 7.1.1 you will not be able to unlock again. Multiple people have told you this but you seem to not believe anyone so go ahead and prove us wrong.

aholeinthewor1d said:
You can't.. it doesn't work like that..
Click to expand...
Click to collapse
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
It's a simple question. Either people have actually done this before, or you are just speculating.
aholeinthewor1d said:
There are countless threads about the bootloader. .
Click to expand...
Click to collapse
But has anyone updated everything but left the bootloader on 7.1?

aholeinthewor1d said:
Once you install 7.1.1 you will not be able to unlock again.
Click to expand...
Click to collapse
Again, there is a difference between updating everything to 7.1.1 and updating everything except the bootloader. Huge difference.

LoliSmith said:
So people have done this before? Updated everything but the bootloader and then relocked? Or are you just speculating?
It's a simple question. Either people have actually done this before, or you are just speculating.
But has anyone updated everything but left the bootloader on 7.1?
Click to expand...
Click to collapse
Again. You can't.

aholeinthewor1d said:
Again. You can't.
Click to expand...
Click to collapse
You've tried? Anyone else has tried?
So are you saying if I leave the bootloader on 7.1 and update everything else the phone won't work?

LoliSmith said:
You've tried? Anyone else has tried?
So are you saying if I leave the bootloader on 7.1 and update everything else the phone won't work?
Click to expand...
Click to collapse
There is more than one bootloader which is what you are not understanding. There are 5. No one is certain exactly what 7.1.1 changed but if you flash any part of it (not just the bootloader) then you won't be able to unlock again.

aholeinthewor1d said:
There is more than one bootloader which is what you are not understanding.
Click to expand...
Click to collapse
Why does that make a difference?
I am on the original bootloader, never updated anything.

Should we unlock the Bootloader if no root planned

If you have no plans to root the phone is there any reason to unlock the bootloader?

It would probably break Safety net and Android pay. BUT if you're unlocked, you have ability to flash factory images. That could be beneficial something goes really bad and your device won't boot up. You're also less secure with it unlocked.
Sent from my marlin using XDA Labs

You can always lock and unlock the bootloader when you want.

I would say you should at least have the option checked on in the Developer settings.
So just in case something happened and you can't fully boot the phone. you can still get into it and unlock the bootloader and do what you need to do.
This happened to a friend of mine where something happened and couldn't fully boot and couldn't unlock bootloader cause the option was never checked.

I don't believe the unlock option stays enabled after it boots up.

I would argue why WOULDN'T you unlock the bootloader? Regardless of rooting, an unlocked bootloader is a safety net for when things go south. Phone decides to bootloop tomorrow? No big deal, flash the latest images via fastboot and start from scratch.
Sure there's the counter argument of the phone being much less secure and vulnerable in the hands of a person who is tech savvy and stole/found your device. I'm not worried about my phone being stolen so I ALWAYS unlock my bootloader.

Pain-N-Panic said:
I would argue why WOULDN'T you unlock the bootloader? Regardless of rooting, an unlocked bootloader is a safety net for when things go south. Phone decides to bootloop tomorrow? No big deal, flash the latest images via fastboot and start from scratch.
Sure there's the counter argument of the phone being much less secure and vulnerable in the hands of a person who is tech savvy and stole/found your device. I'm not worried about my phone being stolen so I ALWAYS unlock my bootloader.
Click to expand...
Click to collapse
or just flash the full OTA image without an unlocked bootloader.

mngdew said:
You can always lock and unlock the bootloader when you want.
Click to expand...
Click to collapse
Does re-locking the bootloader wipe the phone?

foosion said:
Does re-locking the bootloader wipe the phone?
Click to expand...
Click to collapse
Yes, it does. That's why you should unlock or lock the bootloader when flashing factory images.

mngdew said:
Yes, it does.
Click to expand...
Click to collapse
Thanks
mngdew said:
That's why you should unlock or lock the bootloader when flashing factory images.
Click to expand...
Click to collapse
I don't understand what you mean by this.
You have to unlock the bootloader to flash a factory image and you can eliminate the w flag so that flashing the factory image won't wipe the phone.

uicnren said:
or just flash the full OTA image without an unlocked bootloader.
Click to expand...
Click to collapse
Very true. If the phone goes into booploop due to a bad zip or whatever other reason you have a bricked device with no options to recover.

It's healthy for me to unlock my Bootloader ASAP on XDA!

Unlocking the bootloader was always the very first thing I did when I got a new phone. However, I use Android Pay all the time, and Google seems very determined to break AP for unlocked bootloaders with every new patch. Sure, someone usually finds a way to get it working again, but that sometimes takes time, and I simply use AP too much to deal with it. As long as AP won't work officially with an unlocked bootloader, mine stays locked unless I'm flashing an image, and even then, gets locked right after. Luckily, OTAs are posted by Google now, often at the same time as the Factory Images, so it hasn't really been an issue for me.

akenis said:
It would probably break Safety net and Android pay. BUT if you're unlocked, you have ability to flash factory images. That could be beneficial something goes really bad and your device won't boot up. You're also less secure with it unlocked.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
Thank you what actually is compromised when phone is unlocked?

uicnren said:
or just flash the full OTA image without an unlocked bootloader.
Click to expand...
Click to collapse
How can you flash with a locked bootloader?

painfree said:
Thank you what actually is compromised when phone is unlocked?
Click to expand...
Click to collapse
Data?
https://www.google.com/amp/s/www.ho...unlocking-your-android-phones-bootloader/amp/
Sent from my marlin using XDA Labs

painfree said:
If you have no plans to root the phone is there any reason to unlock the bootloader?
Click to expand...
Click to collapse
If you ever contemplate going onto the Verizon network, when you first boot up after placing VZN sim into the phone,
the ability to ever unlock again is eliminated. You could relock it, but it will have the Unlock option in Developer
Option greyed out forever after that. I would unlock it maybe because of Verizon thing, but also to be able to flash factory a image in case I ever mess up the phone.

michaelbsheldon said:
If you ever contemplate going onto the Verizon network, when you first boot up after placing VZN sim into the phone,
the ability to ever unlock again is eliminated. You could relock it, but it will have the Unlock option in Developer
Option greyed out forever after that. I would unlock it maybe because of Verizon thing, but also to be able to flash factory a image in case I ever mess up the phone.
Click to expand...
Click to collapse
As long as you have the Google version it should never grey out on you at least that's how it was with the first pixels. I have Verizon I've never had it grey out.

jt3 said:
Unlocking the bootloader was always the very first thing I did when I got a new phone. However, I use Android Pay all the time, and Google seems very determined to break AP for unlocked bootloaders with every new patch. Sure, someone usually finds a way to get it working again, but that sometimes takes time, and I simply use AP too much to deal with it. As long as AP won't work officially with an unlocked bootloader, mine stays locked unless I'm flashing an image, and even then, gets locked right after. Luckily, OTAs are posted by Google now, often at the same time as the Factory Images, so it hasn't really been an issue for me.
Click to expand...
Click to collapse
This. Android Pay is pretty convenient and I always told myself I didn't need it compared to unlock+root. Wish Google would allow AP with unlocked bootloader but I can understand why they don't from a security standpoint.
Sent from my Pixel 2 XL using Tapatalk

foosion said:
Thanks
I don't understand what you mean by this.
You have to unlock the bootloader to flash a factory image and you can eliminate the w flag so that flashing the factory image won't wipe the phone.
Click to expand...
Click to collapse
When you unlock the bootloader, phone is wiped automatically.

How to Relock the Bootloader For Return

I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?

enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
Fastboot flashing lock.

toknitup420 said:
Fastboot flashing lock.
Click to expand...
Click to collapse
does this work? anyone tried?

mgear356 said:
does this work? anyone tried?
Click to expand...
Click to collapse
LOL of course it works, the command is directly from Google.

That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app

slaydog said:
That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Cheers mate.. Was worried as my last phone was 6p.
My first pixel lol..

If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?

vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
Why you returning the phone in the first place?

Jiggs82 said:
Why you returning the phone in the first place?
Click to expand...
Click to collapse
Returning it to Google and re buying elsewhere for at least $200 less.

vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
when you lock or unlock, it wipes the phone.

uicnren said:
when you lock or unlock, it wipes the phone.
Click to expand...
Click to collapse
Just that I read in a couple of places when re locking some have had a "no os installed" result.

enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
You don't need to lock bootloader to return..I returned multiple devices without locking

vibrantliker said:
Just that I read in a couple of places when re locking some have had a "no os installed" result.
Click to expand...
Click to collapse
simply flash both partitions first then.

Just wipe it and ship it. Google will only inspect it for physical abuse and water damage. The don't care if it's unlocked. It Google, the sell us unlocked phones. I too have sent them back unlocked as have many others.

I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.

vibrantliker said:
I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.
Click to expand...
Click to collapse
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.

TonikJDK said:
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.
Click to expand...
Click to collapse
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?

vibrantliker said:
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?
Click to expand...
Click to collapse
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.

mac796 said:
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.
Click to expand...
Click to collapse
It is completely stock, but what does that mean
"Flash the image to both slots"?

vibrantliker said:
It is completely stock, but what does that mean
"Flash the image to both slots"?
Click to expand...
Click to collapse
Go to Google's factory image page download January's image and do the flash all to slot a. Then change to slot B.
Fastboot --set-active=b then flash all to slot B. Probably Overkill but you'll for sure be stock. Then issue you're relock command to both critical and the regular bootloader one. For one you need to make sure your fastboot is current if it's not up to date you're probably going to have problems.
Edit. I would just send it back the way it is

Pixel 2 XL no operating system fix

So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.

oliverfongftw said:
So I recently got my hand on a pixel 2 xl without the operating system.
I know this is an issue happened to some devices and the best way is to send it back to Google for a replacement.
However neither do I have the box and receive with me nor I am living in the official launch area. So there is no easy way for a replacement from Google. (I can't even post question at there official pixel user forum)
Therefore I really would love to know if I can indeed install the official ROM with tool like this one? https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
And hopefully won't wasted a good device.
Click to expand...
Click to collapse
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images

If you have the stock recovery and can boot into it you can adb sideload the most recent ota zip.
Sent from my Pixel 2 XL using XDA-Developers Legacy app

ram4ufriends said:
Did you have OEM Unlocking checked in Developer options before it happened? If yes you can flash factory images
Click to expand...
Click to collapse
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.

oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
You can get the bootloader lock status simply by booting into the bootloader. Locked or unlocked? You don't "think" it has a working recovery is not good enough to help you. If it does have a stable recovery, you can flash the OTA. If it does not and the bootloader is locked you are S.O.L. and the phone is dead. Follow this video and let us know.

oliverfongftw said:
Thanks for the answering guys, however I think it is one of the machine that Google ships with a OS in it... so I don't think OEM unlocking is enabled nor the recovery is working.
Click to expand...
Click to collapse
If you can hold down volume and hit power to get into bootloader and choose Recovery, you can fix this phone.
Go here: read instructions at top. You will be booting to bootloader, then to recovery, then choose Apply Update from ADB.
Then give adb OTA command as described. Don't skip or modify any step.
https://developers.google.com/android/ota

I am in this exact same situation. Did you ever figure it out? Or did anyone figure it out?

Got this exact problem with a locked bootloader and no recovery, any solution?

0x0null said:
Got this exact problem with a locked bootloader and no recovery, any solution?
Click to expand...
Click to collapse
How did you lose the recovery with a locked bootloader?
Sent from my Pixel 2 XL using XDA Labs

CyberpodS2 said:
How did you lose the recovery with a locked bootloader?
Click to expand...
Click to collapse
Got it that way thinking i could use recovery to recover the phone

0x0null said:
Got it that way thinking i could use recovery to recover the phone
Click to expand...
Click to collapse
It came without a recovery.

Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.

mookiexl said:
Just use deuce script to flash the factory image guys. That's what I did when I got the no os message. Mines started when I ignorantly thought I had to relock bootloader before flashing stock.
Click to expand...
Click to collapse
Locked bootloader wont let me use the script.

If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.

Strephon Alkhalikoi said:
If your bootloader is locked with no way to unlock it, and with no working recovery, you're screwed. The device needs to be sent to Google to fix, which is rather problematic when the device is in a country where it wasn't sold.
Click to expand...
Click to collapse
Yea, your on point. Only edl firehose may save me

0x0null said:
Locked bootloader wont let me use the script.
Click to expand...
Click to collapse
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?

mookiexl said:
The script unlocks the bootloader and flashes firmware. Did you try or just assumed it wouldn't work?
Click to expand...
Click to collapse
It Unlocks only if 'oem unlock' is engaged from the booted system.

0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Which is exactly why it should never be in the locked position...
Sent from my Pixel 2 XL using XDA Labs

0x0null said:
Yea, your on point. Only edl firehose may save me
Click to expand...
Click to collapse
and save me to. I try to find firhose for my pixel 2xl but I didn't find it. Hope someone can provide QFIL Firmware to save as.
Sent from my MI 9 using Tapatalk

0x0null said:
It Unlocks only if 'oem unlock' is engaged from the booted system.
Click to expand...
Click to collapse
Did you try? I used it with no 0S installed so oem unlock couldnt have been engaged.