Develop Bugs

[Q] Possible root without unlocking?

I've just bought my Galaxy Nexus for two days to replace my dead Nexus One.
The UI of ICS is so great but I miss the function from DEVs, like vibrate when the call made.
I have rooted my Nexus One without unlocking the bootloader and I would love to root my Galaxy Nexus without unlocking too.
Is there any DEV going to work on this?

I don't believe anybody is working on this since BL unlock is so simple, and there aren't really any disadvantages (that I know of). In order for root to occur without BL unlock, there would have to be an exploit found in the stock image. Is there a particular reason you don't want to unlock it? You have only had the phone two days, so I imagine your data loss won't be that big of an issue.

kekspernikai said:
I don't believe anybody is working on this since BL unlock is so simple, and there aren't really any disadvantages (that I know of). In order for root to occur without BL unlock, there would have to be an exploit found in the stock image. Is there a particular reason you don't want to unlock it? You have only had the phone two days, so I imagine your data loss won't be that big of an issue.
Click to expand...
Click to collapse
unlocking BL void the warranty

Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
And rooting doesn't? After all, it does allow for modification/deletion of system files. In any case, you can re-lock it just as easily.

Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
Accidentally thanked you haha - missed the quote button.
You can lock it if you have to send it in or return it, you know. The lock command is just as simple as the unlock!

zombieflanders said:
And rooting doesn't? After all, it does allow for modification/deletion of system files. In any case, you can re-lock it just as easily.
Click to expand...
Click to collapse
Rooting doesn't make the splash screen change (the lock under "Google"), so it can be easily unroot by deleting related files in the system and make it look like stock.
Are you sure a unlocked devices can lock again? Nexus One can't do this.

Booker-T said:
Rooting doesn't make the splash screen change (the lock under "Google"), so it can be easily unroot by deleting related files in the system and make it look like stock.
Are you sure a unlocked devices can lock again? Nexus One can't do this.
Click to expand...
Click to collapse
Yes, "fastboot oem lock" will re-lock the bootloader and make the padlock go away. Here is the write-up by droid-life (I can't view it at work, so I hope it has the right info!)
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/

kekspernikai said:
Yes, "fastboot oem lock" will re-lock the bootloader and make the padlock go away. Here is the write-up by droid-life (I can't view it at work, so I hope it has the right info!)
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
Mine one is the GSM one, I have searched on Googles, there is no GSM version re-lock tutorial there, so I doubt GSM version cannot re-lock.
And I don't have the stock image.

Booker-T said:
Mine one is the GSM one, I have searched on Googles, there is no GSM version re-lock tutorial there, so I doubt GSM version cannot re-lock.
And I don't have the stock image.
Click to expand...
Click to collapse
I thought the GSM factory image was pretty widely available?
http://www.theverge.com/2011/12/4/2610060/google-galaxy-nexus-factory-image-restore-phone
I am fairly certain people with the GSM variant have re-locked their phones, but I would check the Nexus android development section (GSM) for proof.

I've tested relocking and can confirm it works fine
Sent from my Galaxy Nexus using XDA App

Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
I feel like this is a myth. You're not using an exploit, or anything like that, you're using a manufacturer provided tool to unlock the bootloader. Taken from android.com:
On Nexus One, Nexus S, Nexus S 4G, Xoom, and Galaxy Nexus, the bootloader is locked by default. With the device in fastboot mode, the bootloader is unlocked with
$ fastboot oem unlock
The procedure must be confirmed on-screen, and deletes the user data for privacy reasons. It only needs to be run once.
On Nexus One, the operation voids the warranty and is irreversible.
On Nexus S, Nexus S 4G, Xoom, and Galaxy Nexus, the bootloader can be locked back with
$ fastboot oem lock
Click to expand...
Click to collapse

I would love a way to root without unlocking the bootloader -- coming from the Nexus One, which I easily rooted without ever touching the bootloader -- it didn't occur to me that rooting would require unlocking the bootloader. Of course, I wish now that I'd unlocked the bootloader right when I took the phone out of the box, which is, I see now, what everyone recommends. But I've more data on the phone than I want to deal with losing right now.
So if anyone following this thread turns up a way to root without unlocking the bootloader, please let us know!

You won't see this feature arrive until manufacturers start selling ICS phones with locked bootloaders (I'm looking at you HTC, LG, etc). Devs will then try to punch a hole through the OS instead of using simple fastboot commands, as the bootloader will be locked down.
I don't understand why you would wait though, just fastboot oem unlock, root, then fastboot oem lock. The only way your warranty is going to be voided is if you have a rooted rom, that padlock means nothing on the Galaxy Nexus. IF THEY SEE SUPERUSER, THEY KNOW YOU ROOTED. They don't give a **** about the splash screen

Galaxy Nexus bootloader unlocked itself?

I'm sure this sounds crazy, but here's the short version... I purchased a second Galaxy Nexus on eBay and it just came in. I activated the phone and tested calls, wifi, speakers, etc. to verify it was all working. Afterwards I flashed the GA02 update + LTE modem update (provided by sextape) using Odin 3.04. When it rebooted after flashing, the "unlock" icon was there. So once it was done, I pulled battery, went into the bootloader and sure enough it's now saying my bootloader is unlocked. The first boot and all subsequent restarts while doing the manual activation, it was locked. I compared bootloader screens when I first took it out of the packaging with my original Galaxy Nexus (unlocked bootloader) and the new one said "locked".
Has anyone ever had this happen? Does the GA02 update + LTE update by Sextape automatically unlock your bootloader?
I'm mystified...

Considering that you usually need an unlocked bl to touch the radio, i'd bet that LTE modem update tool has something to do with it. Did you check that thread? I've stayed away from odin, but perhaps that had an option checked to unlock it?

bodh said:
Considering that you usually need an unlocked bl to touch the radio, i'd bet that LTE modem update tool has something to do with it. Did you check that thread? I've stayed away from odin, but perhaps that had an option checked to unlock it?
Click to expand...
Click to collapse
I've searched it but didn't find anything related to the bootloader unlocking. I checked the contents of the LTE tar and it's just a radio.img. As far as I know the ODIN tool is just an interface to flash the images. The same would be accomplished using fastboot flash (partition) (image). Maybe it's something inside the recovery.img sextape modified.

You mentioned odin, if you haven have a unlocked bootloader, odin does it for you......................
You need to do more research before committing..................

Mach3.2 said:
You mentioned odin, if you haven have a unlocked bootloader, odin does it for you......................
You need to do more research before committing..................
Click to expand...
Click to collapse
I'm afraid I didn't understand most of what you said nor am I sure to whom you said it to. If to me, I have flashed using ODIN in the past and it did not unlock the boot loader. This was posted only out of curiosity and I'm just chalking it up to a modification in one of the images (boot loader maybe?)

I think Mach was talking to you.. My point is that i believe the bootloader must be unlocked to even touch the radio, as part of a security measure. I do not believe you could fastboot flash anything at all without first having the bl unlocked. Then again, you say you've used odin before to flash without an unlocked bl, and i know almost nothing about odin.

bodh said:
I think Mach was talking to you.. My point is that i believe the bootloader must be unlocked to even touch the radio, as part of a security measure. I do not believe you could fastboot flash anything at all without first having the bl unlocked. Then again, you say you've used odin before to flash without an unlocked bl, and i know almost nothing about odin.
Click to expand...
Click to collapse
You've got a point there. I switch between phones often (mostly HTC in the past) so I think I'm slightly mixed up on the different methods setup for the different handsets. Thanks for pointing it that out.

thefsfempire said:
I'm afraid I didn't understand most of what you said nor am I sure to whom you said it to. If to me, I have flashed using ODIN in the past and it did not unlock the boot loader. This was posted only out of curiosity and I'm just chalking it up to a modification in one of the images (boot loader maybe?)
Click to expand...
Click to collapse
Yup referring to you.
Haven use odin before, but i remember someone said if you have a locked bootloader, flashing using odin will unlock the bootloader.
Don't know why odin did not unlock your bootloader in the past when you used it, without a unlocked bootloader, you can't flash anything.

[Q] Bootloader unlock allowed: NO

Hello, guys
So i got a series of problems since i unlock the simlock,
I just got my new zl a few days ago, the device was lock to Bell.
I rooted the device and after that, i got a code and enter it to the sim free status.
but here is the problems:
when i check the rooting status, it says bootloader unlock allowed: no. It will fail on if unlock straightway.
As i know, it should turns to yes, but it didn't, hwo come? Also, i flash the recovery, but it only works on first time when i get in the recovery mode.
I selected "reboot system now", and cwm point out that will flash stock recovery, no matter i selected yes or no, recovery doesn't work on next boot.
I used to have Xperia S, it was also says no, after i unlock it turns yes. It wasn't happens on my ZL! I tried to flash a new ftf and wiped all the data,
it still says no. Anyone has a same situation? Can anyone fix it?

Nobody reply? Come on guys...

7xbyte said:
Nobody reply? Come on guys...
Click to expand...
Click to collapse
I unlocked mine too but not root and still say no
Sent from my C6506 using xda app-developers app

nutzuTo said:
I unlocked mine too but not root and still say no
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
Which network was ur phone locks to?

7xbyte said:
Which network was ur phone locks to?
Click to expand...
Click to collapse
It was locked on Bell Canada, I unlocked with a code to be used on fido network
Sent from my C6506 using xda app-developers app

nutzuTo said:
It was locked on Bell Canada, I unlocked with a code to be used on fido network
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
So do I, maybe Bell not allow BL to be unlock? Recovery can't even work correctly without BL unlock.
Before ZL. My XS was locked to Rogers. As I said, my XS shows BL unlock allowed after typed in the unlock code. Which mean Bell locked the
BL deadly?
I will keep following this god damn sh!*
nutzuTo, thx anyway.

Can anyone confirm that the Bell Mobility (Canada) ZL's are permanently bootloader locked? I want to get one off the used market, but won't unless it can be fully unlocked.
Thanks

Maybe I didnt read the post properly but unlocking your SIM doesnt unlock the bootloader as well. It simply allows your phone to be used with different carriers. I have the C6506 from Rogers, flashed the stock Sony ROM, rooted the phone and installed TWRP and CWM. My bootloader remains locked. I dont have the need to flash the Kernel so no point in unlocking the BL. Besides, unlocking your BL voids the warranty.
Anyway, I have played with the C6506 from Bell in a store and the BL is set to "Bootloader unlock allowed: No" so its pretty safe to assume that all Bell and Rogers phones cannot be unlocked. This doesnt stop you from rooting, flashing or installing recovery.

Simlock and bl lock two different things
if your bl unlock says yes that means you most have one direct from factory
if your bl unlock says no you either have it on a plan or bought it full price through bell or rogers
carrier branded usually bootlocked

Thanks for the replies guys.
I know that custom rom / root / recovery can be flashed, but coming from a galaxy nexus and n7, I'm used to being able to try out different kernels.
Can custom kernels be installed if they're part of the custom ROM? Usually the rom cook puts in the kernel of her/his choice but we can freely change after.
Anyone feel the need to change kernels or the standard one is good enough?

"Can custom kernels be installed if they're part of the custom ROM? Usually the rom cook puts in the kernel of her/his choice but we can freely change after."
Yes.When you are thinking about installing/flashing custom rom but want different kernel DL and extract the boot.img(name may vary but must end .img)
Now FLASHTOOL is sonys verision of the "Nexus Toolkit" . If you dont have adb setup download and install program to C: as well as all drivers needed. Now in the flashtool folder copy and paste the ".img" kernel into the folder named x10lib.
After double click folder labeled "x10lib" once inside the folder open command prompt window by holding left shift and right click anywhere in the opened x10lib folder.
now make sure your device is connected to your pc in fastboot mode (hold vol +) led will emit blue light.
enter command
"fastboot flash boot boot.img"
followed by
"fastboot reboot"
Anyone feel the need to change kernels or the standard one is good enough?"
yes i first used doomlords kernel (Xperia ZL) mainly for the fact that it came with cwm recovery .thus making the need to flash cwm seperatley an extra non needed step. this was before i flashed 4.2 update.

sirsmokey said:
"Can custom kernels be installed if they're part of the custom ROM? Usually the rom cook puts in the kernel of her/his choice but we can freely change after."
Yes.When you are thinking about installing/flashing custom rom but want different kernel DL and extract the boot.img(name may vary but must end .img)
Now FLASHTOOL is sonys verision of the "Nexus Toolkit" . If you dont have adb setup download and install program to C: as well as all drivers needed. Now in the flashtool folder copy and paste the ".img" kernel into the folder named x10lib.
After double click folder labeled "x10lib" once inside the folder open command prompt window by holding left shift and right click anywhere in the opened x10lib folder.
now make sure your device is connected to your pc in fastboot mode (hold vol +) led will emit blue light.
enter command
"fastboot flash boot boot.img"
followed by
"fastboot reboot"
Anyone feel the need to change kernels or the standard one is good enough?"
yes i first used doomlords kernel (Xperia ZL) mainly for the fact that it came with cwm recovery .thus making the need to flash cwm seperatley an extra non needed step. this was before i flashed 4.2 update.
Click to expand...
Click to collapse
With that said, how would I go about flashing CM or something else aosp based with a locked BL xperia zl?
Can flashtool unlock my BL to allow this?
I ask because I clean see an option there, just haven't wanted to muck about with things I don't yet understand lol

sadly only way to change bootloader unlock allowed to yes is to carrier unlock from ur carrier directly. anyone else and it will not change bootloaded unlock allowed no to YES. I have called bell and sony. sony told me i have to carrier unlock through bell to get it to change to yes only thing is. you have to have had your phone for 90 days and it costs75$ added to ur bill.

[Q] Is my device already unlocked, if it has no brand name on it?

I want to root my Google Nexus 7. I was skimming through the notes on how to do this and the first step is too unlock your tablet. However I ordered my tablet from Amazon it is a Google Nexus 7 2nd without any carriers on it that I can see (Samsung, AT&T, ect). So does this mean my device is already unlocked, is there a way I can check to see if it is unlocked? And finally, if it it unlocked where should I start so I can root the tablet? Any help will be greatly appreciated. I'm sorry if this question has already been answered I did not see it posted. Thanks! :good:

ferls1985 said:
I want to root my Google Nexus 7. I was skimming through the notes on how to do this and the first step is too unlock your tablet. However I ordered my tablet from Amazon it is a Google Nexus 7 2nd without any carriers on it that I can see (Samsung, AT&T, ect). So does this mean my device is already unlocked, is there a way I can check to see if it is unlocked? And finally, if it it unlocked where should I start so I can root the tablet? Any help will be greatly appreciated. I'm sorry if this question has already been answered I did not see it posted. Thanks! :good:
Click to expand...
Click to collapse
Carriers? Like a phone service? Do you haves the LTE version?

ferls1985 said:
I want to root my Google Nexus 7. I was skimming through the notes on how to do this and the first step is too unlock your tablet. However I ordered my tablet from Amazon it is a Google Nexus 7 2nd without any carriers on it that I can see (Samsung, AT&T, ect). So does this mean my device is already unlocked, is there a way I can check to see if it is unlocked? And finally, if it it unlocked where should I start so I can root the tablet? Any help will be greatly appreciated. I'm sorry if this question has already been answered I did not see it posted. Thanks! :good:
Click to expand...
Click to collapse
You're talking about two different "locks". There's the bootloader "lock", and a carrier "lock".
When you buy a phone or tablet or whatever through a carrier such as Verizon or AT&T, most of the time it is "carrier locked", can only be used on that carrier's infrastructure until you "carrier unlock" it, and will usually feature the carrier's name and symbol on the hardware itself. This is not the case with the Nexus 7, it is carrier unlocked, meaning it is bound to no carrier at all.
Then there is the "bootloader lock". Out of the box, your Nexus has a locked bootloader, meaning you cannot flash any unsigned packages/code, which is required if you want to root it. You need to unlock the bootloader so you can flash either some file or binary that grants root access, or a custom ROM that is already rooted. When you're reading guides about rooting and they say to "unlock" it, they mean unlock the bootloader.

Johmama said:
You're talking about two different "locks". There's the bootloader "lock", and a carrier "lock".
When you buy a phone or tablet or whatever through a carrier such as Verizon or AT&T, most of the time it is "carrier locked", can only be used on that carrier's infrastructure until you "carrier unlock" it, and will usually feature the carrier's name and symbol on the hardware itself. This is not the case with the Nexus 7, it is carrier unlocked, meaning it is bound to no carrier at all.
Then there is the "bootloader lock". Out of the box, your Nexus has a locked bootloader, meaning you cannot flash any unsigned packages/code, which is required if you want to root it. You need to unlock the bootloader so you can flash either some file or binary that grants root access, or a custom ROM that is already rooted. When you're reading guides about rooting and they say to "unlock" it, they mean unlock the bootloader.
Click to expand...
Click to collapse
Thanks a ton! I understand it now. I appreciate your help!

Google VS. Non-Google Variant Differences

This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.

So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.

I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.

Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.

Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.

1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.

My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app

suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app

1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.

dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?

Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.

1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?

coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.