Database Info

I just won a Google Pixel. Now what?

Hi everyone. I just won a Google Pixel. The contest was on a tech site and prize was provided by verizon. The phone package doesn't show verizon on it at all. Is there a way to tell if it is verzion locked? Also what does it mean if it is? Will I not get the updates when they go out? I am currently with T-Mobile and my phone before is a Nexus 6P. I haven't rooted or flashed a phone in years. Doesn't mean I'm not willing. Just thought I'd post and see if I could get some advice on what to do next with my Google Pixel. Any help is greatly appreciated. Thanks!

When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.

uodii said:
When you get the phone, reboot it to bootloader mode and use fastboot from your pc (obviously connect phone to computer first) and run the command: fastboot oem unlock
If it unlocks then you're money. If not, it's prolly Verizon and if that's the case try to figure out what software is on the phone (pray that it's an old phone somehow) before they fixed the bootloader workaround.
Click to expand...
Click to collapse
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.

TonikJDK said:
It won't unlock that way no matter what version if he doesn't hit the slider first.
OP:
You will get updates from google if it does not have a Verizon sim in it. If it does they come from Verizon. The Verizon version of the software has some tweeks for their network, nothing more.
To find out if it is unlockable hit the developer options and find 'oem unlock' if you can slide it to allow oem unlock it is a Google version. That will not unlock it, that will allow you to then do what the poster above said...and that will unlock it.
You must have an internet connection to use the slider. That can be just with wifi if you want. It phones home to see if it is allowed to unlock. And that is the only difference between a VZ version and a Google version. It is in the data base to be unlockable or not.
Click to expand...
Click to collapse
I forgot about that in the developer settings. It's been a while since I did that. Good catch.

Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?

GeekyWilliam said:
Thanks. Unfortunately the oem unlocking option isn't available. So I should be able to just pop my T-mobile Sim in and have no issues?
Click to expand...
Click to collapse
Yep, you will be all set. And updates will come from google.
About phone...what version of N is it on? Dont let it update until you answer that. If it is lower than 7.1.1 you can unlock it still.
http://theroot.ninja/depixel8.html

It is 7.1. Thanks again!

GeekyWilliam said:
It is 7.1. Thanks again!
Click to expand...
Click to collapse
Hit it now. You don't have to full unlock but depixel8 it and get the slider done before it updates.

Ok. I'll do it now. Once I depixel8 then I can get the updates?

GeekyWilliam said:
Ok. I'll do it now. Once I depixel8 then I can get the updates?
Click to expand...
Click to collapse
Yea, you can finish the unlock later after it updates. But be aware the next step in unlocking will wipe your phone. So you may want to get it over with.

Verizon Pixel XL - unlocking bootloader on Oreo

Hi,
I have Oreo on Pixel XL, and was wondering if there's any way to unlock the bootloader with dePixel8 or otherwise so I can install TWRP/root?
Thanks!

No

I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?

H0wdy said:
I was given the phone from a family member. I'm assuming it was Verizon, but I use it on Sprint now. Under developer options, OEM unlocking is greyed out, and it says to go online or talk to carrier.
Surely there's a way to root this phone?
Click to expand...
Click to collapse
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.

robocuff said:
If it's a Verizon phone (sounds like it is), no. There is currently no way to root. If it's a Google phone, it can be done. However, for the option in developer options to not be greyed out, you need to be connected to the internet one way or another. If you are connected and it's still greyed out, it's almost certain that it's a Verizon phone.
Click to expand...
Click to collapse
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.

H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.

robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Thanks. I guess I'll wait to see if something else occurs.

I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)

AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.

jmartin72 said:
I don't believe this will work. The accepted theory is that Verizon locks the bootloader by IMEI number, so if your phone has an IMEI that is on the list, it will be locked no matter what. However, I'm not sure if anyone has tried to change their IMEI to test this theory. I'm also not sure if you can change your IMEI without root. That would require an unlocked bootloader, so probably no way to test.
Click to expand...
Click to collapse
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.

AncientDeveloper said:
But the bootloader is still locked locally. So even the phone sends the IMEI to Verizon, and Verizon sends some command back to the phone to lock it, it shouldn't require changing the IMEI to unlock.
Click to expand...
Click to collapse
I wish someone could figure out how to get it done.

Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Edit: OEM unlocking is *not* greyed out even on Wifi

nyisles said:
Hi - My Verizon Pixel XL is on Oreo OPR3 and OEM unlocking is *not* greyed out but bootloader status is LOCKED. Is it possible with my setup?
Click to expand...
Click to collapse
Yep, Google has messed up on quite a few phones. Hit that slider now. That won't unlock it, you still have to issue the fastboot command. But moving that slider now will future proof you if you want to unlock.

jmartin72 said:
I wish someone could figure out how to get it done.
Click to expand...
Click to collapse
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.

Pixxlman said:
What if we could overwrite the bootloader and leave the sim out of the phone and activate it with wifi then verizon can't check the imei and can't lock it? i have a verizon pixel XL i can try this with if someone could walk me through overwriting a bootloader
Click to expand...
Click to collapse
There are multiple problems with that theory. First, Verizon does not lock them. They all come locked, when they start up they phone home to Google and get permission to unlock. And two, the SIM has nothing to do with locking.

What is the point of Google shipping the phones with two different bootloaders and unlocked and locked states.

Some hope with the clkscrew exploit? Sounded like the phone needed to be rooted to work, but being able to pull trustzone keys from a Google variant could possibly enable a workable patch for the Verizon variant.
Have no idea, but sure sounds plausible.

H0wdy said:
Robocuff,
Thank you. That seems to be my situation, but I was wondering why this isn't an option?
https://www.xda-developers.com/verizon-pixelpixel-xl-bootloader-unlock-has-been-released/
Does it no longer work? I understand it probably doesn't, but I didn't know if there was another way.
Click to expand...
Click to collapse
robocuff said:
dePixel8 doesn't work anymore. It only worked for a couple months. Google patched the hole that dePixel8 exploited in the December security update. So, any Verizon phone that was updated in December or anytime after and wasn't all ready unlocked, became unlockable after that.
Click to expand...
Click to collapse
Google did not close the exploit. Verizon did with the release of 7.1.2 in November 2016.
AncientDeveloper said:
I wonder if overwriting the Verizon Pixel's bootloader with a non-Verizon bootloader from one of the factory images would work. The logic behind this is that all G-2PW2100s seemd to have identical hardwares, and factory images contain all the bootloader/radio partition images; so in theory, flashing a non-Verizon factory image should make the device non-Verizon.
(Please note that this is just a theory & I have not tested this. There's a chance that doing this will brick the device.)
Click to expand...
Click to collapse
The package will probably fail to install after modifying because of improper signature. It has been tried before....
AncientDeveloper said:
While I haven't figured out a way to gain the ability to write to the eMMC, it seems that the last byte on the eMMC controls whether the device is unlockable.
Click to expand...
Click to collapse
Probably encrypted, you don't have access to the correct tools, or both.

Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk

gobi42 said:
Would flashing the original image from Google onto the phone and running depixel then. Would that work? Or has that been tried?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
No. You can't downgrade with a locked bootloader.

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.

Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170

depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.

Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?

depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?

rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.

geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net

Pixel 4 XL Unlocked bootloader

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.

Question How to unlock bootloader?

I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.

- Hit settings
- about phone
- software information
- build number 5 times
- profit

I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.

RedHatter271 said:
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
Click to expand...
Click to collapse
Have you tried through fastboot? (fastboot oem unlock)

Oh, got you. Sorry!

As far as I'm aware samsung devices don't support fastboot. I did attempt to connect it in case I was wrong but was not able to get fastboot to recognize the device.

RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.

darkidz555 said:
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
Click to expand...
Click to collapse
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.

RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
Did your Developer Options come already unlocked after setting it up?

twistedumbrella said:
Did your Developer Options come already unlocked after setting it up?
Click to expand...
Click to collapse
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9

luigi90210 said:
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
Click to expand...
Click to collapse
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.

twistedumbrella said:
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
Click to expand...
Click to collapse
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking

luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
Click to expand...
Click to collapse
They support it.

RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
If you can boot into download mode there is an instruction just press vol up button and it will prompt do you want to unlock bootloader mine is like that. Im not sure yours since mine is korea version.

luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader .
Click to expand...
Click to collapse
They support bootloader unlock. samsung dont support using fastboot unlock or command at all

if you're in North America, Canada etc Qualcomm chips there do not support bootloader unlocking, at least the Samsung one's don't, not sure about other OEMs.

darkidz555 said:
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
Click to expand...
Click to collapse
They used to, so there was always a possibility it returned.

I recently read this article on XDA about unlocking the boot loader on the Fold 3 which results in Samsung disabling the camera (WTH?), Is this a thing on the Flip3 too?

My device is rooted. I have always been able to find the OEM unlock option under developer options without any constraints.
My camera is NOT affected. I can still use it without any issues.
I have an European device (SM-F711B).
Hope this helps some of you to track down whether this is a location or carrier based problem.

Hey Redhatter,
Out of topic question, but are you getting Tmobile 5G just fine?
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse