Develop Bugs

Downgrade from 7.1.1

Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?

ashish8 said:
Anyone know if it's possible to downgrade from 7.1.1 so I can run depixel8 and unlock the bootloader?
Click to expand...
Click to collapse
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.

@CZ Eddie is right. No way to go back with a locked bootloader on a VZW phone running 7.1.1.

CZ Eddie said:
I'm not Verizon but I have some experience and can tell you 100% no doubt that you're stuck if you're on the latest update from Verizon and do not have an unlocked bootloader.
There is no way to go back just to unlock the bootloader.
Sorry.
Click to expand...
Click to collapse
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL

grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Click to expand...
Click to collapse
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.

CZ Eddie said:
I'll defer this question to the more Verizon knowledgeable.
My suspicion is you're good to go but I'm only 70% sure about that.
Click to expand...
Click to collapse
grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.

grinchyyy said:
Question for you sir, I have a Verizon Pixel XL with 7.1 build NDE63X.
My bootloader is UNLOCKED. My phone is notifying me that 7.1.1 update is available.
I just wanted confirmation that I can take this update without the risk of my bootloader re-locking?
Thanks in advance.
Sent from my Nexus 6 that thinks it's a Pixel XL
Click to expand...
Click to collapse
Updates can't lock your bootloader.

thecarp1975 said:
It will not re-lock your bootloader. I'm on Verizon with the Verizon variant of the Pixel XL. I took the 7.1.1 update and my bootloader stayed unlocked.
Click to expand...
Click to collapse
airmaxx23 said:
Updates can't lock your bootloader.
Click to expand...
Click to collapse
Thanks guys! Just wanted to be absolutely sure.
Sent from my Nexus 6 that thinks it's a Pixel XL

is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?

raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
It's not necessarily impossible --nobody seems to have a 100% understanding of what the dual slots are doing on this phone. People who were on custom Roms and rooted have reported successfully taking a stock OTA update without boot looping their phones, although it did wipe out root and the custom recovery. But it's not a great idea to do it the way you suggest and basically hope you get lucky. You would be much better off unlocking the bootloader at least temporarily and flashing a full stock image from Google.

raybonz420 said:
is it possible to for someone to dump 7.1.2 unlocked bootloader rom to install as a OTA update via ADB?
Click to expand...
Click to collapse
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.

TonikJDK said:
No, because you would not be able to properly sign the file you created so your phone would reject it. The whole Certificate signing thing is what I speak of, if the file isn't signed with a google cert the ota would fail.
Click to expand...
Click to collapse
could it be signed using chainfires AVB?

raybonz420 said:
could it be signed using chainfires AVB?
Click to expand...
Click to collapse
No, an ota has to be signed by google.

replacement device unlocking question

So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.

@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3

cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.

@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.

cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?

Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.

cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?

Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.

cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?

Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased

pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?

mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.

pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.

mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.

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.

OEM Unlocking greyed

Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
If it originally came from EE it is locked, but EE can unlock it. Did you factory reset it? That also was a bug and the reset cleared it.

Badger50 said:
You may have to call Google. I think that some versions sold/purchased in the EU have a 6 month waiting period before they can get an unlocking code ?
Click to expand...
Click to collapse
The device is from usa

sabi95190 said:
The device is from usa
Click to expand...
Click to collapse
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.

TonikJDK said:
Factory reset it then connect to the internet. Early on Google shipped a bunch that had this problem. The fixed it on their end but it requires a fact reset.
Click to expand...
Click to collapse
I reset it from the settings?

sabi95190 said:
I reset it from the settings?
Click to expand...
Click to collapse
Yep...settings/system/reset options :good:

Badger50 said:
Yep...settings/system/reset options :good:
Click to expand...
Click to collapse
Done but nothing change

sabi95190 said:
Hello I bought a pixel 2 xl from ebay for 450$. I live in France... The pixel was showed as unlocked from google store i recieved it but the oem unlocking is greyed out..
Can someone help me? There's a screenshot of the cid
Click to expand...
Click to collapse
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?

Namolas said:
Just to be clear, being SIM unlocked and bootloader unlocked are two completely different things. Are you sure the advertising for it being "unlocked" wasn't referring to the SIM status?
Click to expand...
Click to collapse
Yes I knew that but I thought that the Google Version have a unlockable bootloader...

sabi95190 said:
Yes I knew that but I thought that the Google Version have a unlockable bootloader...
Click to expand...
Click to collapse
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?

Namolas said:
Google version does have an unlockable bootloader. The question is are you 100% positive it's the Google version you bought/received and not the Verizon version?
Click to expand...
Click to collapse
I looked for the cid of the phone and it appears that the phone isn't from Verizon. And the seller also told me that he bought the phone from Google store

It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739

ImWarped said:
It's likely the previous owner tried to unlock the bootloader and failed. By the looks of things the only current way to fix it is RMA to Google.
https://issuetracker.google.com/issues/68897739
Click to expand...
Click to collapse
I don't think it will be possible I'm not original owner

sabi95190 said:
I don't think it will be possible I'm not original owner
Click to expand...
Click to collapse
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.

uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
delete

uicnren said:
What version of android is it currently on?
After the factory reset, did you set the phone up at all, or just go to settings to try and enable it?
Set the phone up, connect it to WiFi and let it update system apps. You dont have to set the phone up completely, but let it connect to the internet and update.
Once thats done reboot it and skip thru any setup then go to settings and enable dev options and see if it is toggle-able.
Also make sure you are using the latest adb/fastboot.
Click to expand...
Click to collapse
It didn't work
Edit: I verified the IMEI in a website and it shows as a verizon device...

OEM Unlocking grayed out

I have this issue on the unlocked version running .30. Anyone else running the XL experienced this?

If you got it from Verizon it's locked you can not unlock the bootloader... If you got it from Google maybe it's a mistake you need to call them...

mostyle said:
I have this issue on the unlocked version running .30. Anyone else running the XL experienced this?
Click to expand...
Click to collapse
I had this issue at first. I had to do a factory reset after putting in my sim card. See if either or both of those work.
Sent from my crosshatch using XDA Labs

If your phone is unlocked, please leave it greyed out and spend the time with your kids or call your mother. Time better spent... Unless your OCD, it will bug crap out of you, [emoji23] [emoji23] [emoji23]. Phone is unlocked, you won't unlock it more, no?
Sent from my Pixel 3 XL using Tapatalk

I think he is referring to OEM unlock, that slider not being accessible is most def a serious problem.

krabman said:
I think he is referring to OEM unlock, that slider not being accessible is most def a serious problem.
Click to expand...
Click to collapse
Why? His phone is unlocked. Am I missing something?
Unless, he is referring to a non-vzw as unlocked (to a carrier?) and he can't unlock the bootloader cuz it's greyed out..? If so my bad and the answer posted already worked for me too.
Sent from my Pixel 3 XL using Tapatalk

Which unlock slider do you imagine he would be referring to when there is only the one? Lol Ya screwed up man. And no, I'm not busting your balls. It happens, done it myself.

ridobe said:
I had this issue at first. I had to do a factory reset after putting in my sim card. See if either or both of those work.
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Done several resets and set up with and without SIM. Still Grayed out.
MArtyChubbs said:
Why? His phone is unlocked. Am I missing something?
Unless, he is referring to a non-vzw as unlocked (to a carrier?) and he can't unlock the bootloader cuz it's greyed out..? If so my bad and the answer posted already worked for me too.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Correct... Sorry, I should have clarified. It is Play Store purchased, non-VZW, non-project FI device running on AT&T.
This isn't my first rodeo so I knew what should have happened (I have 6p, Pixel 1 and have been running customs long before that) when I fired it up. It just didn't behave as expected so I was polling to see if others had a similar experience.
Sorry for the confusion... I shoulda been more explanatory in the OP.
Several non-xl users have said they experienced the issue (posted there as well) so I'm thinking it isn't device specific but rather an OS issue. Found Google support threads that reference the exact same described issue that was resolved by an OS hotfix. We'll see. RMA arrives tomorrow.

mostyle said:
Done several resets and set up with and without SIM. Still Grayed out.
Correct... Sorry, I should have clarified. It is Play Store purchased, non-VZW, non-project FI device running on AT&T.
This isn't my first rodeo so I knew what should have happened (I have 6p, Pixel 1 and have been running customs long before that) when I fired it up. It just didn't behave as expected so I was polling to see if others had a similar experience.
Sorry for the confusion... I shoulda been more explanatory in the OP.
Several non-xl users have said they experienced the issue (posted there as well) so I'm thinking it isn't device specific but rather an OS issue. Found Google support threads that reference the exact same described issue that was resolved by an OS hotfix. We'll see. RMA arrives tomorrow.
Click to expand...
Click to collapse
Same here with a Verizon sim. I had the greyed out OEM and reflashed stock image or reset like you (can't remember cuz my brain is old) and then I was able to toggle it. Well, cool beans on the RMA!
If someone else has the problem, post here and maybe a fix can be documented.

MArtyChubbs said:
Same here with a Verizon sim. I had the greyed out OEM and reflashed stock image or reset like you (can't remember cuz my brain is old) and then I was able to toggle it. Well, cool beans on the RMA!
If someone else has the problem, post here and maybe a fix can be documented.
Click to expand...
Click to collapse
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?

XtazyMike said:
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?
Click to expand...
Click to collapse
I believe, "Verizon sim", are the key words there. I don't think he means he has a Verizon Pixel.

XtazyMike said:
Wait... You have a VZW pixel 3( or xl) and you managed to bypass the OEM unlock? how?
Click to expand...
Click to collapse
No, from Google but I put my VZW sim I got with my Pixel XL in my P3XL. Sorry, like the OP, we had a weird problem unlocking BL with it being greyed out.
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
No, from Google but I put my VZW sim I got with my Pixel XL in my P3XL. Sorry, like the OP, we had a weird problem unlocking BL with it being greyed out.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Just to be clear, you didn't 'flash' anything originally, correct? Just a factory reset? Since the bootloader is locked, if you flashed something please share. I saw the or in your post. Just making sure that I read that correctly.

I think I wanna say I DID flash leaving the -w in the bat file.
Locked bootloader means you can't flash non stock images, no? You can srill upgrade the bootloader even if it's still locked, right? What I mean is, I can still use the fastboot images on a locked phone or can't I?
I erased the data partition at least and then the OEM unlock was not greyed out. But I am in the habit of fastbooting (that's what I ment by flash) with or without -w so I am pretty sure that is what I did. Maybe not, I dunno...
Sent from my Pixel 3 XL using Tapatalk

You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Thanks for the confirmation I felt like I was inventing a memory for a moment there.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
You can flash a factory image with a locked bootloader as long as it retains the signature, which would be broken the second it gets modified.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.

bobby janow said:
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.
Click to expand...
Click to collapse
This is correct. This is why you can't lock the bootloader while having non-stock firmware. You can't boot because it's "corrupt", you can't flash because you are BL locked and you can't boot to toggle "OEM unlocking".
Sent from my crosshatch using XDA Labs

ridobe said:
This is correct. This is why you can't lock the bootloader while having non-stock firmware. You can't boot because it's "corrupt", you can't flash because you are BL locked and you can't boot to toggle "OEM unlocking".
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
By firmware do you mean a ROM? Because if the rom is signed even if it's not Google's signature then you can lock the bootloader. All it looks for is that signature so it can perform checks to make sure that signature stays the same.
Sent from my Pixel 3 XL using Tapatalk

bobby janow said:
Are you sure about that? I don't believe you can flash anything other than sideload an OTA with a locked bl. But I could be mistaken, just like to confirm.
Click to expand...
Click to collapse
You are not mistaken. Just tried.