Does anyone know definitively if a non-VZW pixel gets activated with VZW, does the bootloader become non-unlockable?
DevADX said:
Does anyone know definitively if a non-VZW pixel gets activated with VZW, does the bootloader become non-unlockable?
Click to expand...
Click to collapse
It doesn't.
Just did that myself. I put in the Vzw sim, have service and bootloader remains unlockable.
wtherrell said:
It doesn't.
Just did that myself. I put in the Vzw sim, have service and bootloader remains unlockable.
Click to expand...
Click to collapse
Is this true even after VZW OTA update? I'm thinking about buying an used Pixel but want to be certain that the bootloader is unlockable.
DevADX said:
Is this true even after VZW OTA update? I'm thinking about buying an used Pixel but want to be certain that the bootloader is unlockable.
Click to expand...
Click to collapse
That, I don't know. I have not taken a Vzw ota in years.
DevADX said:
Is this true even after VZW OTA update? I'm thinking about buying an used Pixel but want to be certain that the bootloader is unlockable.
Click to expand...
Click to collapse
I have a Google phone on VZ. It stays unlocked no matter what you do.
TonikJDK said:
I have a Google phone on VZ. It stays unlocked no matter what you do.
Click to expand...
Click to collapse
So just to confirm, as long as it's not a Verizon variant of the Pixel, even if it's running stock VZW ROM & has received OTA updates while the bootloader is locked, it's still unlockable? I'd feel more confident buying an used one if this is the case; just need to confirm the SKU prior to purchasing.
nothing you do (besides manually relocking the device) will re-lock the bootloader.
My google bought xl runs a full verizon image.
Is there another way to differentiate the VZW & non-VZW Pixels besides the SKU on the box?
DevADX said:
So just to confirm, as long as it's not a Verizon variant of the Pixel, even if it's running stock VZW ROM & has received OTA updates while the bootloader is locked, it's still unlockable? I'd feel more confident buying an used one if this is the case; just need to confirm the SKU prior to purchasing.
Click to expand...
Click to collapse
The non-Verizon Pixel has nothing to do with Verizon. The only thing Verizon about a non-Verizon variant is the Verizon sim card you put in. You mentioned it running a Verizon ROM however...the only way to have the Verizon ROM on it would to have unlocked the bootloader at some point and replaced the stock android with a Verizon ROM.
markcyst said:
The non-Verizon Pixel has nothing to do with Verizon. The only thing Verizon about a non-Verizon variant is the Verizon sim card you put in. You mentioned it running a Verizon ROM however...the only way to have the Verizon ROM on it would to have unlocked the bootloader at some point and replaced the stock android with a Verizon ROM.
Click to expand...
Click to collapse
I should mention that I made a USUnlocked Pixel XL be never unlockable again.
Before putting in a VZN sim, I unlocked it. Sometime after, I got tired of the warning on boot-up and locked it.
The Verizon sim or the Google Verizon Image greyed out the Developer's Option of Unlock bootloader choice.
Forever. There was no way to get that icon to become alive again. So, the VZN sim or the VZN image will not relock
your phone, but it for sure prevents you from locking and unlocking it again. Felt like an idiot for relocking.
michaelbsheldon said:
I should mention that I made a USUnlocked Pixel XL be never unlockable again.
Before putting in a VZN sim, I unlocked it. Sometime after, I got tired of the warning on boot-up and locked it.
The Verizon sim or the Google Verizon Image greyed out the Developer's Option of Unlock bootloader choice.
Forever. There was no way to get that icon to become alive again. So, the VZN sim or the VZN image will not relock
your phone, but it for sure prevents you from locking and unlocking it again. Felt like an idiot for relocking.
Click to expand...
Click to collapse
Wait a minute. You are leaving out some very pertinent information.
1. Was this a Google phone or a Verizon phone
2. Did you unlock with depixel 8 or not
3. After you locked the bootloader did you slide the switch over in dev options
This is the first I heard anything like that happening. If this is a Google phone then you can certainly return it stating what happened. You bought a developer device and somehow it became a consumer phone. That sounds like a warranty return to me.
bobby janow said:
Wait a minute. You are leaving out some very pertinent information.
1. Was this a Google phone or a Verizon phone
2. Did you unlock with depixel 8 or not
3. After you locked the bootloader did you slide the switch over in dev options
This is the first I heard anything like that happening. If this is a Google phone then you can certainly return it stating what happened. You bought a developer device and somehow it became a consumer phone. That sounds like a warranty return to me.
Click to expand...
Click to collapse
1.) Bought directly from Google.
2.) Unlocked just after opening box and getting on Wi-Fi.
3.) Yes, after locking it, I enabled Dev Options and slid that slider back to locked stock status.
I basically ruined the phone for tinkering. Because it was locked, I could not go back to an Android version
that could be unlocked with depixel8.
michaelbsheldon said:
I should mention that I made a USUnlocked Pixel XL be never unlockable again.
Before putting in a VZN sim, I unlocked it. Sometime after, I got tired of the warning on boot-up and locked it.
The Verizon sim or the Google Verizon Image greyed out the Developer's Option of Unlock bootloader choice.
Forever. There was no way to get that icon to become alive again. So, the VZN sim or the VZN image will not relock
your phone, but it for sure prevents you from locking and unlocking it again. Felt like an idiot for relocking.
Click to expand...
Click to collapse
michaelbsheldon said:
1.) Bought directly from Google.
2.) Unlocked just after opening box and getting on Wi-Fi.
3.) Yes, after locking it, I enabled Dev Options and slid that slider back to locked stock status.
I basically ruined the phone for tinkering. Because it was locked, I could not go back to an Android version
that could be unlocked with depixel8.
Click to expand...
Click to collapse
This is concerning. So does this mean a Verizon SIM permanently locks all Pixel variants regardless whether it's a Google one or Verizon one?
michaelbsheldon said:
VZN sim or the VZN image will not relock your phone, but it for sure prevents you from locking and unlocking it again.
Click to expand...
Click to collapse
If I were to buy an used non-VZW Pixel that was activated with VZW, then the bootloader is no longer unlockable (given that it's stock & locked) even if I'll be using it with another carrier?
DevADX said:
This is concerning. So does this mean a Verizon SIM permanently locks all Pixel variants regardless whether it's a Google one or Verizon one?
If I were to buy an used non-VZW Pixel that was activated with VZW, then the bootloader is no longer unlockable even if I'll be using it with another carrier?
Click to expand...
Click to collapse
Yes, in my experience. But I’m just 1 gumbah on 1 phone.
Maybe someone with HTC knowledge can tell us..
michaelbsheldon said:
1.) Bought directly from Google.
2.) Unlocked just after opening box and getting on Wi-Fi.
3.) Yes, after locking it, I enabled Dev Options and slid that slider back to locked stock status.
I basically ruined the phone for tinkering. Because it was locked, I could not go back to an Android version
that could be unlocked with depixel8.
Click to expand...
Click to collapse
So on your dev options under the grayed out oem unlock, what does it say? Depixel8 was only meant for Verizon phones not Google ones.
Have you tried calling Google? Because even on wifi only, no sim, you bought a device that you could unlock and develop with. Somehow that device malfunctioned and you deserve a replacement. It's as simple as that imo.
I don't believe this to be common. In fact I've never heard of this happening before.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
So on your dev options under the grayed out oem unlock, what does it say? Depixel8 was only meant for Verizon phones not Google ones.
Have you tried calling Google? Because even on wifi only, no sim, you bought a device that you could unlock and develop with. Somehow that device malfunctioned and you deserve a replacement. It's as simple as that imo.
I don't believe this to be common. In fact I've never heard of this happening before.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
Didn't call Google. It's now on a family T-Mobile line and still can't be unlocked. She likes it as it is.
michaelbsheldon said:
Didn't call Google. It's now on a family T-Mobile line and still can't be unlocked. She likes it as it is.
Click to expand...
Click to collapse
I get that. I don't unlock my bootloader and I'm perfectly happy too.
But you are correct, it's ruined for tinkering. Think in the future for a few. What about when you get a new device for the family member and yourself. Now you have a great device you can play with to either test stuff or mess with new roms or images. But you can't.
Just sayin. But it's always good for a trade in. I'd love to hear if this has happened to anyone else.
Sent from my Pixel using XDA-Developers Legacy app
I originally bought a Pixel 3 XL to take me in the future. Aside from getting the newest updates and newest operating systems for the next 2/3 years, I've always found these devices to be The easiest to unlock, root and mod.
My plan was too keep Android stock until Google announced that it wouldn't do further updates then I would unlock bootloader, root and mod. However I have been reading on the forums how some providers are fixing exploits that would not allow us to mod the phone (mostly verizon). This makes me question if it is worth waiting.
I am currently with bell Canada. Does anyone have any experience with Bell and there willingness to block unlocking and rooting? Should I be worried that bell will fix these exploits in the future? Has anyone unlocked the bootloader with bell yet or run into any issues when doing it with bell?
Sent from my Pixel 3 XL using Tapatalk
If you bought the phone FROM Google, carrier shouldn't be able to enforce a lockdown. If you got it from your carrier you may not be able to unlock it at all. The Verizon/Best Buy versions are not unlockable but the Google Store ones are, even when being used on Verizon's network.
You can unlock the bootloader and not root, but you may lose access to some apps due to SafetyNet checks. Android Pay I believe is one that won't work, Pokemon Go, Netflix used to, not sure if they still do or not. If you unlock your bootloader and root, then install Magisk or similar, I believe you can spoof SafetyNet and get around that. If you don't have any concerns with SafetyNet you could just unlock and root later.
If the phone is from Google as far as I know it will always be unlockable no matter what so the only risk of waiting is that you'll have to wipe when you unlock it. I haven't rooted since my Pixel XL 1 so I'm not up on the current processes. Rooting may still require a wipe beyond the one induced by unlocking the bootloader.
Clarification. Bootloader unlock depends on one thing, did it come from Google or did it come from a carrier that bootloader locks it.
There is no exploit needed to unlock a Google phone. There is no exploit available for any that the carrier locked, such as Verizon in the US.
Google will not lock their versions, they support bootloader unlocking.
It is my understanding that Bell sells a pure Google version.
What are the first two numbers of your IMEI? If it is 99 you are good to go.
Downside to waiting is that unlocking causes a full wipe, there is no avoiding that.
Mine was bought through Bell. The imei starts with 35. I should have looked into this further before I bought the phone. I didn't realize pixel s were carrier locked like that. I'm going to have to try to unlock the bootloader sooner then I expected just to be safe.
Thanks for the help.
Sent from my Pixel 3 XL using Tapatalk
icanrule said:
Mine was bought through Bell. The imei starts with 35. I should have looked into this further before I bought the phone. I didn't realize pixel s were carrier locked like that. I'm going to have to try to unlock the bootloader sooner then I expected just to be safe.
Thanks for the help.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I've heard that some of the European providers sim lock their device until it's paid off. They then carrier unlock it and sometimes allow bl unlock. I have no idea what the IMEI number is, however. If you're only unlocking for future device support after 3 years I wouldn't worry about it much. You'll probably have a new device by then hopefully. The only other option is to sell it now while it's relatively new and purchase a Google branded one. General consensus is that there will not be an exploit in order to allow bl unlock on these devices. It will probably cost you about $100 on the swap. I lost close to $150 on my Pixel 3 this week and it was mint condition.
I have a Virgin Mobile Pixel 3 XL & just unlocked bootloader after reading this. Since Bell & Virgin basically same company and carry the same phones you should be good! (IMEI Starts with 35)
TonikJDK said:
Clarification. Bootloader unlock depends on one thing, did it come from Google or did it come from a carrier that bootloader locks it.
There is no exploit needed to unlock a Google phone. There is no exploit available for any that the carrier locked, such as Verizon in the US.
Google will not lock their versions, they support bootloader unlocking.
It is my understanding that Bell sells a pure Google version.
What are the first two numbers of your IMEI? If it is 99 you are good to go.
Downside to waiting is that unlocking causes a full wipe, there is no avoiding that.
Click to expand...
Click to collapse
I am currently looking into getting the Rogers version. Is the bootloader unlockable and that version rootable? I am not sure what the IMEI would start with either.
Also is the carrier locking the bootloader different the lock which fastboot commands unlock?
spncr_wu said:
I am currently looking into getting the Rogers version. Is the bootloader unlockable and that version rootable? I am not sure what the IMEI would start with either.
Also is the carrier locking the bootloader different the lock which fastboot commands unlock?
Click to expand...
Click to collapse
Yes carrier locking and bootloader locking are different. Carrier locks mean you can only use that phone on one network, bootloader lock controls the software on the phone.
It's mildly confusing because some carriers also restrict bootloader unlocking (like Verizon).
fury683 said:
Yes carrier locking and bootloader locking are different. Carrier locks mean you can only use that phone on one network, bootloader lock controls the software on the phone.
It's mildly confusing because some carriers also restrict bootloader unlocking (like Verizon).
Click to expand...
Click to collapse
I was asking about the bootloader restriction. So for the Verizon version what is limiting it's ability to be rooted? No exploit yet?
spncr_wu said:
I was asking about the bootloader restriction. So for the Verizon version what is limiting it's ability to be rooted? No exploit yet?
Click to expand...
Click to collapse
The software checks the IMEI against a database to see if it is unlockable or not. When you first boot the phone if you try to turn on OEM unlocking in settings it requires a network connection in order to verify the IMEI on that list. If it's a blocked carrier (like Verizon) it won't let you turn it on (it gets grayed out).
Exploits were found for previous Pixel devices but I don't know if anyone is pursing them anymore.
If I buy from Google and set it up with Sprint, can I root?
I'm currently on HTCU11, and thought it was one of the most recent you could root of using Qualcomm phones.
You can root this even if it's using Qualcomm chip?
spncr_wu said:
I was asking about the bootloader restriction. So for the Verizon version what is limiting it's ability to be rooted? No exploit yet?
Click to expand...
Click to collapse
mcwups1 said:
If I buy from Google and set it up with Sprint, can I root?
I'm currently on HTCU11, and thought it was one of the most recent you could root of using Qualcomm phones.
You can root this even if it's using Qualcomm chip?
Click to expand...
Click to collapse
If you buy from Google you can unlock and root no matter what carrier you use the device on. The carrier imposed bootloader locks are only imposed on phones sold by that carrier, not any phone used on that carrier's network.
fury683 said:
The software checks the IMEI against a database to see if it is unlockable or not. When you first boot the phone if you try to turn on OEM unlocking in settings it requires a network connection in order to verify the IMEI on that list. If it's a blocked carrier (like Verizon) it won't let you turn it on (it gets grayed out).
Exploits were found for previous Pixel devices but I don't know if anyone is pursing them anymore.
Click to expand...
Click to collapse
This is good news because I have oem unlocking available in settings and was able to toggle the option. I may try to unlock the bootloader in the next week because Bell is big and I don't trust them. It may be unlocking now but may not be in the future.
I hate living in fear like this.
Sent from my Pixel 3 XL using Tapatalk
bobby janow said:
I've heard that some of the European providers sim lock their device until it's paid off. They then carrier unlock it and sometimes allow bl unlock. I have no idea what the IMEI number is, however. If you're only unlocking for future device support after 3 years I wouldn't worry about it much. You'll probably have a new device by then hopefully. The only other option is to sell it now while it's relatively new and purchase a Google branded one. General consensus is that there will not be an exploit in order to allow bl unlock on these devices. It will probably cost you about $100 on the swap. I lost close to $150 on my Pixel 3 this week and it was mint condition.
Click to expand...
Click to collapse
I'm Canada we get robbed here. My cellphone costs 1300 off contract, and according to eBay (if it's reliable) I can only get 1000 for it. That is a pretty big loss to me.
Sent from my Pixel 3 XL using Tapatalk
I am happy to say that I was able to unlock the boot loader and reboot the phone. We now know that Bell Canada Pixel 3 XL can have the bootloader unlocked.
Its been a very long time since i have done any of this stuff. I bought the verizon version and cannot get bootloader unlocked. I have searched and see there has been the same problem in the past models. Is there a bypass or workaround? I can only find one for early Pixel products.
Kpwise509 said:
Its been a very long time since i have done any of this stuff. I bought the verizon version and cannot get bootloader unlocked. I have searched and see there has been the same problem in the past models. Is there a bypass or workaround? I can only find one for early Pixel products.
Click to expand...
Click to collapse
nvmnd. found my answer
Kpwise509 said:
nvmnd. found my answer
Click to expand...
Click to collapse
I am in the same boat.. curious to what answer you found?
m1ng15 said:
I am in the same boat.. curious to what answer you found?
Click to expand...
Click to collapse
I found another thread on here after I searched, and searched. From what I understand now. If it's a Verizon pixel the bootloader is locked permanently.
If you purchased your device from Verizon, or a Verizon variant from a 3rd party retailer (Best buy, Costco, etc.) the bootloader is locked tight!
If you want the option to root; return your VZW device and order one directly from Google.
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
mustangtim49 said:
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
Click to expand...
Click to collapse
Incorrect. SIM unlocking is not necessarily related to bootloader unlocking. While T-Mobile (and I think AT&T) users on here have found and reported that when they achieve SIM unlocking on their variants, that they can then bootloader unlock as well, Verizon has for a very, very long time enforced bootloader lock with all their will.
The only exceptions that I've ever heard of were not by choice of Verizon, but by hacks/vulnerabilities. Such as the VS985 LG G3, there was an exploit that didn't actually bootloader unlock, but more made it so that the locked bootloader didn't really matter. On the Pixel 1, if you had the Verizon variant and were still on Android 7.10 or below, you could unlock the bootloader, but once the 7.11 OTA came out, if you hadn't already unlocked the bootloader (or at least toggled the toggle), then you were locked in until a foreign national found a hacking way to get in, but they charge for it. All this while Verizon phones have been ultimately SIM unlocked for similarly a very long time.
mustangtim49 said:
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
Click to expand...
Click to collapse
You might be thinking 'carrier unlocked' vs "bootloader unlocked".
VZW does NOT like people rooting their devices so they have locked the bootloaders for several years now. I honestly don't even think any devs are working on a workaround/bypass for VZW devices anymore because they've had a long history of tightly locking down their device's bootloaders.
Az Biker said:
You might be thinking 'carrier unlocked' vs "bootloader unlocked".
VZW does NOT like people rooting their devices so they have locked the bootloaders for several years now. I honestly don't even think any devs are working on a workaround/bypass for VZW devices anymore because they've had a long history of tightly locking down their device's bootloaders.
Click to expand...
Click to collapse
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information.
If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point.
I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
I seriously doubt the "60 day sim unlock" allows the bootloader to be unlocked, otherwise we'd have a ton of VZW variant threads filled with development, and devices that are 61 days old, rooted, and running custom Roms.
But we don't. We don't have even have any developers working on VZW devices, regardless of age. So deductively thinking, the "60 day sim unlock" doesn't sound like it's currently an option.
Just my .02 (USD) worth
mustangtim49 said:
Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader.
Click to expand...
Click to collapse
That has never, ever been the case with Verizon variants of phones. 1) Verizon phones have been SIM/carrier unlocked from the get-go for a very long time and 2) Except for rare anomalies like the Pixel 1 on Android 7.10 or below, OEM unlocking was always grayed out.
mustangtim49 said:
Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options.
Click to expand...
Click to collapse
That has never happened on a VZ Pixel and it is not going to happen on this one. Why is this so hard for people to understand?
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
sorry. your misinformed. Pixel devices from Verizon cannot have the bootloader unlocked. Period. end of story.
Have you ever had a Verizon device that was "carrier/sim unlocked" but couldn't unlock the bootloader? I have. and its real, so please research before you post misinformation.
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
Unfortunately, and I hate to be the bearer of bad news because I didn't want to find this out for myself lol (but of course I really did), but I can tell everyone that I have the Verizon version and after 60..well a little after that because of course it was not as easy as their terms say on their website that it will automatically unlock after 60 days...yeah right..I had to call and chat I cant even tell you how many times...to finally get the right person to help me...which turned into waiting a few more days but he came through and unlocked it....
so the bad news: the oem unlock in developer options is still greyed out. Now it says to contact your carrier or connect to the internet
I still have hope for maybe one day? i mean there is ALWAYS a way to do anything on phones..someone smart enough just has to figure it out
mrindependent said:
Unfortunately, and I hate to be the bearer of bad news because I didn't want to find this out for myself lol (but of course I really did), but I can tell everyone that I have the Verizon version and after 60..well a little after that because of course it was not as easy as their terms say on their website that it will automatically unlock after 60 days...yeah right..I had to call and chat I cant even tell you how many times...to finally get the right person to help me...which turned into waiting a few more days but he came through and unlocked it....
so the bad news: the oem unlock in developer options is still greyed out. Now it says to contact your carrier or connect to the internet
I still have hope for maybe one day? i mean there is ALWAYS a way to do anything on phones..someone smart enough just has to figure it out
Click to expand...
Click to collapse
This was the same for the Verizon Pixel 2 XL, and every Verizon Pixel since. No unlockable bootloader unfortunately.
My first foray into rooting was with the Galaxy Nexus. That had no issues unlocking the bootloader, and was the last phone I've bought at a store.
It's sad, that I can bring my rooted device and get a new line, but I can't tinker with their versions if I were to buy one at a store, online, whatever.
Their loss imo as there are a number of us I think, who would buy at the store if we could unlock the bootloader. I guess we as a group aren't big enough for them to worry about though.
You can however, play musical SIM card between devices, and it works. For the most part anyways.
I hate this.
What do they think people are just going to accidentally stumble on this, mistakenly download specific apps and Roms and out of the blue, randomly, and incorrectly, flash a very specific file causing the phone to brick and they don't want to keep fixing it?
Cause those Muppets all have iPhones...
Beyond stupid.
And here I was, done with how Samsung limited this process, so I ditched it for the shiny new Pixel... I'm the Muppet
tmessy said:
And here I was, done with how Samsung limited this process, so I ditched it for the shiny new Pixel
Click to expand...
Click to collapse
Every Verizon variant of phones is locked down, and certainly, historically different models of them have been able to be either unlocked, or most of the time as far as I've experienced a workaround (security vulnerability) to unlocking was found (IIRC, the Stump method on LG phones worked this way), and the (again, as far as I'm aware) single time(s) that a Verizon phone was able to be bootloader unlocked as if it was made to be able to do so from the get-go, more or less: The Pixel 1 on Android 7.10 or below, and there is some foreign hacking method which can exploit some secret vulnerability if you're willing to pay to still be able to bootloader unlock the Pixel 1.
In my opinion, Samsung limits are even worse than the carrier-imposed limits, as Samsung keeps their phones from being bootloader unlocked on every U.S. Carrier, and even the direct from Samsung bought in the U.S. factory carrier unlocked model, but please correct me if I'm wrong. I only know the experience with the phones I've actually owned and what I remember from reading about others' experiences, however. The Exynos-based versions of Samsung phones are able to be bootloader unlocked at least in most countries, and again IIRC, some Snapdragon-based Samsungs in one or a few select countries too. Sony officially allows their bootloaders to be unlocked, but they purposefully and permanently gimp your phone's features if you do - and some other OEMs do similar, I'm given to understand.
I know it's frustrating about Verizon. Besides no longer buying carrier-specific models of phones, I no longer use Verizon as well, but it sucks for those who really need the carrier incentives.
roirraW edor ehT said:
Every Verizon variant of phones is locked down, and certainly, historically different models of them have been able to be either unlocked, or most of the time as far as I've experienced a workaround (security vulnerability) to unlocking was found (IIRC, the Stump method on LG phones worked this way), and the (again, as far as I'm aware) single time(s) that a Verizon phone was able to be bootloader unlocked as if it was made to be able to do so from the get-go, more or less: The Pixel 1 on Android 7.10 or below, and there is some foreign hacking method which can exploit some secret vulnerability if you're willing to pay to still be able to bootloader unlock the Pixel 1.
In my opinion, Samsung limits are even worse than the carrier-imposed limits, as Samsung keeps their phones from being bootloader unlocked on every U.S. Carrier, and even the direct from Samsung bought in the U.S. factory carrier unlocked model, but please correct me if I'm wrong. I only know the experience with the phones I've actually owned and what I remember from reading about others' experiences, however. The Exynos-based versions of Samsung phones are able to be bootloader unlocked at least in most countries, and again IIRC, some Snapdragon-based Samsungs in one or a few select countries too. Sony officially allows their bootloaders to be unlocked, but they purposefully and permanently gimp your phone's features if you do - and some other OEMs do similar, I'm given to understand.
I know it's frustrating about Verizon. Besides no longer buying carrier-specific models of phones, I no longer use Verizon as well, but it sucks for those who really need the carrier incentives.
Click to expand...
Click to collapse
NOt every verizon phone, The samsung s20 bootloader was able to be unlocked.
lucky_strike33 said:
NOt every verizon phone, The samsung s20 bootloader was able to be unlocked.
Click to expand...
Click to collapse
As it came without some temporary trick or vulnerability someone was able to take advantage of?