Related
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
Dont worry, its normal.
shagbag913 said:
Dont worry, its normal.
Click to expand...
Click to collapse
But what if I need to re-lock my bootloader? Don't I need this switch available?
lucasdeeiroz said:
But what if I need to re-lock my bootloader? Don't I need this switch available?
Click to expand...
Click to collapse
Nope.
To lock the bootloader, connect via USB to a computer that has the SDK Platform Tools on it, and reboot to the bootloader.
Open a command prompt in your "platform tools" folder and type:
Code:
fastboot flashing lock
This will lock your bootloader and wipe the device. I believe this also sets the "get_unlock_ability" flag to 0 (which the OEM unlock switch corresponds to).
To explain this a little more simply:
There are three components in play here.
First, there is a firmware flag that determines whether the device can be unlocked at all: "ro.oem_unlock_supported". If this is set to 0, OEM Unlocking will be greyed out and unlocking is not possible.
Second, there is another firmware flag that determines whether the bootloader can be unlocked:
"get_unlock_ability". This corresponds to the OEM Unlocking switch - off is 0, on is 1. If the switch is on/flag is set to 1, the bootloader may be unlocked.
Third, there's the bootloader itself. If the "get_unlock_ability" flag is set to 0, the bootloader will refuse unlock commands. If the bootloader is already unlocked, it will override the flag.
Hope this helps and makes sense!
KnifeSkills said:
First of all: Is it normal for my OEM unlocking to be greyed out with status "Bootloader already unlocked" on this device after unlocking the bootloader? On my pixel2xl the option is not greyed out even after unlocking the bootloader, so I'm confused.
More info: Trying to set up a Pixel 2 64GB unlocked version from google store, it came on 8.0 November update. I was able to unlock the bootloader, had trouble flashing to the latest February 8.1 straight from November 8.0, but was able to boot back into 8.0 and let it do the OTA to 8.1 February update successfully. I factory reset after updating to 8.1 February update and have been connected to wifi and have a sim card in while setting up (if that matters), and now the option for OEM unlocking is still greyed out with status "Bootloader already unlocked". Not that it really matters I guess since I want the bootloader to remain unlocked, but the fact that it's different on my 2 pixel devices makes me think I did something wrong somewhere or misconfigured something.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net
i came here just to say that i love you, great tips
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Kool19 said:
I just unlocked the bootloader on my shiny new Pixel 4 XL. It is the Verizon variant as it was purchased directly from Verizon themselves. I'm unsure whether this is a coincidence, whether Google is no longer offering cell phone service providers a locked bootloader option, or did I just get lucky. The steps I took are...
1: Removed the pre-installed sim card
2: Went through the set-up process via Wi-Fi
3: Immediately turned on Developer options
4: Turned on OEM Unlock
5: Used the "fastboot flashing unlock" command via ADB/Fastboot
Normally the OEM unlock option would be greyed out as it was on my original Pixel XL that I also bought through Verizon but was able to use DePixel to unlock, then flash the Google Factory Image, the bootloader. I was then able to re-lock the bootloader for security and mobile payment reasons while retaining the "OEM unlock" option in the developer settings. I will now attempt to do the same thing when Google releases the Factory Image for the Pixel 4 XL.
It also could be because I removed the sim card before the phone had the opportunity to activate.
I am interested whether anyone else has been able to do this.
BTW: Model# G020J
Click to expand...
Click to collapse
What is DePixel?
DePixel8
Who-Lep said:
What is DePixel?
Click to expand...
Click to collapse
It was software that would unlock the bootloader of the Google Pixel and Google Pixel XL that had the bootloader locked to Verizon. The catch was it only worked on Android 7.1.0 I believe. It was patched shortly after so if you updated your device, no luck.
KillerBytes said:
Did this just now on my AT&T Pixel 4 XL 128GB. Nada... Screw this; I'm returning this.
Click to expand...
Click to collapse
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Kool19 said:
Sorry to hear that. Was your model number different. I am truly interested in why I was able to do this so easily.
Click to expand...
Click to collapse
Model number is G020J as well.
got mine from vzw and was able to unlock bootloader as well, removed sim before turning on, set up phone on wifi and check oem unlocking in dev settings before popping in sim card
I am hoping I am in the same boat. I couldn't pass up getting 450 for a pixel xl so I bought the verizon variant it's coming Monday. I have seen where this has worked in the past with the pixel 2. Here is hoping the toggle gets grayed out when it's sees your on verizon's network. I plan on removing sim booting up and getting to developer options taking the least path of resistance and then trying to unlock. If I am successful I will report back.
Well I'm beat my is locked
bigv5150 said:
Well I'm beat my is locked
Click to expand...
Click to collapse
I'm waiting on a 128 GB white from Verizon, but I tried it on my dad's black 64 GB. His is locked as well unfortunately.
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
anon_lastname said:
Currently trying to root my google pixel 2. The guy who sold me this phone said it was unlocked but I guess that was a LIE. When it arived, It had a verizon SIM card and the OEM unlockd button was grayed out. Surprisingly, this method actually managed to get the grayed out OEM unlock button to turn blue:
Here’s an easy method to bootloader unlock a Verizon Pixel or Pixel XL
There's now a simple method to unlock the bootloader of your Verizon-branded Google Pixel or Pixel XL. Give your phone new life!
www.androidauthority.com
However, after I ran "adb reboot bootloader" the command "fastboot oem unlock" still failed. And after the OS booted, the button was grayed out again.
1. What is actually going on here? Why does this method seem to work for some people?
2. Is there any way to get around this?
Click to expand...
Click to collapse
I just tried my AT&T SIM card in the phone and it worked... So the phone is not even carrier locked, but the bootloader is locked.
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Junglism93 said:
If you can reactivate the OEM unlock button try using 'fastboot flashing unlock' rather than the OEM unlock command. Mine wasn't carrier locked but fastboot flashing unlock unlocked my bootloader.
Had the same drama unlocking a pixel I had and fastboot flashing unlocked sorted the bootloader once I'd activated the OEM unlock button.
Click to expand...
Click to collapse
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
anon_lastname said:
I tried that after using the exploit in the OP to get the unlock OEM button. Didn't work.
I'm pretty much done with this POS phone.
Click to expand...
Click to collapse
Fair enough mate, worth a try but definitely sounds like it's the end of the road for unlocking it sadly. Might be time to sell it on mad move on to something else.
Curious if I'm overthinking this/misunderstanding, but OEM Unlocking seems to be available on my T-Mobile locked OP9 after yesterday's update. My girlfriend has not yet updated, and I confirmed it was still disabled/greyed out on android 11. Both of our phones are sim locked.
Did T-Mobile really just mess up and allow this accidentally? I ran the command to get the unlock code from fastboot and am just waiting on OnePlus to send me the token.
Anyone else able to confirm this?
I can oem unlock my TMO variant as well. I bricked my device and sent it to OnePlus for repair. They sent back and it was locked again after I used tools to OEM unlock for the unlock token. I unlocked the bootloader after I recieved the unlock code.bin file. After I updated to A12 the other day I could OEM unlock. The original unlock code fails now when I try to use it. I get verify failed. So I sent the code I got for another unlock request and am waiting for it. I do confirm this OEM unlock options on OP9 now
I'm not asking how, I already know that part. I have an unlocked TMobile/Sprint phone, but from reading TMobile roms are a bit different as they do thier own or modified oos.
I have checked and I can toggle the oem locking in settings. I own the phone outright but I don't have an unlocked sim. I've heard with TMobile you have to call and have the sim unlocked , which in turn let's you then toggle the oem unlock so you can unlock the bootloader.
So my question is, since I bought the phone unlocked, and I can toggle the oem unlock feature, can I just unlock the bootloader now and proceed with root or does it sim need to be unlocked too??
You have to go into fastboot to check if you have it toggled on in dev options go into bootloader and do fastboot oem unlock from command prompt it will unlock or it won't you may have to get an unlock token from one plus also TMobile locks bootloader you need an unlock token file