Related
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
newbienic said:
Hey guys, I'm wondering if anyone has done this, or knows if it's possible to (after unlocking bootloader) flash the Google stock Pixel system image instead of the Verizon one? I'm assuming the hardware and firmware are identical, but am not sure and am not skilled enough (or at all) in code to know if its possible. I bought my phone through Verizon, only because nowhere else had stock. I use it on T-Mobile, but fear there may be some behind the scenes Verizon stuff going on that may hinder my phone on T-Mobile. I haven't experienced any issues yet, but with the Nov security update mentioning a specific fix for wifi calling in New Mexico only on the Verizon pixels, it makes me weary that there is more happening beneath the surface than I am aware of. Thanks for any and all help! Appreciate it.
Click to expand...
Click to collapse
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Awesome! Thanks for the info... Really glad to know I can convert if need be. Thanks again!
jay661972 said:
I did yesterday, bought mine from Best Buy and I unlock the BL. Sideload the OTA yesterday and I used NDE63V that comes with new radio. oh I'm also on Tmobile
Click to expand...
Click to collapse
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
newbienic said:
Interesting side note on this...
I went ahead and unlocked my bootloader and flashed Google's stock Pixel image. All went well, no problems... Until I tried to use Android Pay. It's telling me my software can't be verified. And I out of curiosity checked, and the "allow OEM unlocking" in developer options is still greyed out, and not selectable, even though my BL is unlocked. Hoping this doesn't mean that we can't take an OTA. Weird, I guess we'll have to wait and see when next month's security update comes out...
Click to expand...
Click to collapse
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
ITGuy11 said:
Just having an unlocked bootloader trips SafetyNet now and you can't use Android Pay without a custom kernel.
Click to expand...
Click to collapse
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
danaff37 said:
And the OEM unlock option appears to be dependent on device ID (imeid? Ccid?), And not the software. So don't relock it, and you're fine
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
danaff37 said:
If you want to use Android pay, flash a custom kernel but don't root. Works for me.
Don't relock if you ever want to have it rooted, custom, etc. The unlock method isn't going to survive another security update.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Hypathetically, if I didn't want root or anything custom at all, do you think that relocking the bootloader could cause an issue while using the Stock Google image on a Verizon Pixel? I wish I had more knowledge on this, but I'm pretty in the dark on this stuff as of late... Thanks for your help!
Should be fine if all stock I think, just know that you may not be able to unlock later.
Sent from my Pixel using Tapatalk
newbienic said:
One thing I just realized, is in Developer Options, its greyed out like I mentioned, but also says "Bootloader is already unlocked". Which I actually remember seeing on my Nexus 5x when the bootloader was unlocked. It's got me really curious about re locking the bootloader. Mainly cause I actually use Android Pay. Had no idea bootloader unlocks are actually tripping safety net now. Major bummer. If anyone has gone through this process with a Verizon pixel and has actually relocked their bootloader with no issues I'd certainly appreciate any info you have. Otherwise, I may have to dive in blind and hope for the best.
Click to expand...
Click to collapse
Contrary to what people are saying. You CAN relock your bootloader and then unlock it again later. However, keep in mind that at some point there will likely be an update that blocks the use of dePixel8 and you will no longer be able to unlock the bootloader unless someone writes another exploit.
I would like to find a way to permanently unlock VZW Pixels but until I get one from the Google Store to compare with my Verizon one I don't think I will make much progress.
Relocking your bootloader is as simple as running the "fastboot oem lock" command from the terminal window.
Lastly. If you want to relock the bootloader, make sure your phone is 100% stock image or you risk bricking the phone
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
b316kane said:
If I were to buy the Verizon pixel and flash the unlocked (non European) image. How do you think updates would work? Would I get seamless updates from Google or would I need to flash every Ota manually. Might be too early to tell
Click to expand...
Click to collapse
This is exactly what I did, and I am curious as well... We'll see next month I guess, but I'm guessing it will take the OTA just fine. My wife has a Pixel from the Google store, and mine is from Verizon. I've compared everything (including booloaders) since flashing the Google store Pixel image, and every informational detail is identical. Not sure if there is some other place hidden to me that might indicate a difference, but I'm thinking that Verizon's Pixel is only different in its official software image... And, that may be it. Please don't take my word for it, I'm no developer, and know very little about any of this, but in my comparisons, they are identical now since flashing Googles official (Non Verizon, Non European) image.
Sidenote, I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking. I think Verizon used Googles "Allow OEM Unlocking" software toggle in developer options as the only method to actually keep people from unlocking the bootloader (again speculative), and now that I'm on Googles image, that software "block" should no longer be present, so I should in theory, be free to lock/unlock the same as Pixels purchased from the Google store... Again, I've got no proof, or actual skill to back this up, but it's a theory I have, and if I end up locking my BL again, I'll post what I find...
newbienic said:
I have yet to try this, but I'm thinking that since I am on Googles image, that if I re-lock my bootloader, that I WILL be able to unlock again after locking.
Click to expand...
Click to collapse
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
alluringreality said:
In the Verizon unlocking threads the people that tried relocking reported that they were unable to unlock again without depixel8, which is the same as how the Verizon phone typically works. Some people seem to have gotten into situations that could have been corrected with an unlocked bootloader, but because they had a locked bootloader that couldn't be unlocked using depixel8 they had no easy solution to get their phone working again at this time.
http://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
newbienic said:
Thanks for the heads up!!! Like I said, I really know nothing, just speculating. Appreciate you looking out.
Click to expand...
Click to collapse
I forget where, but I saw written or implied that the "checking for updates" screen about third of way through initial setup of first boot uses WiFi AND sim carrier data to install Verizon custom restrictions and settings that among other effects make depixel8 required.
Even on "non Verizon phones" (which you are saying use the same build images byte to byte?)... You have to either use a SIM card or wifi and google account to allow the developer options to enable OEM unlock.
My theory: In other words, if you don't allow via SIM and a network wifi or data connect, for Verizon to mark your phone, or another carrier, then the phone can not be unlocked. So carrier models may indeed be differentiated from current factory images AFTER boot and setup.
There is a post in Q&A of someone trying to unlock bootloader without loading into the device, not having luck. This is why oem unlock toggle is so important and why people are bricking from locked bootloaders that won't unlock (so no wipe and factory images cannot be flashed.)
Another thing to consider: SIM network lock will not be flashed over.
Sent from my sailfish using XDA Labs
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.
I was under the impression the device I ordered off ebay could be bootloader unlocked (apparently verizon pixel 3a), but can't seem to figure it out myself, and i'm starting to think its not possible. If anyone can unlock the bootloader, I am willing to pay.. If not.. :RIP: :crying: Hopefully this doesn't violate the rules, didn't see any.
Unlocking the bootloader on Pixel phones is pretty easy. You can use the guide here to unlock the bootloader.
You will need to use ADB. If you are not familiar with ADB, you can use the guide found here.
I'm assuming that you want to unlock the bootloader so that you can root your Pixel. I used this guide.
I reread your post and noticed that you bought a Pixel that is carrier locked to Verizon. Usually, unlocking the bootloader of a Verizon phone is either not possible or difficult. The information that I gave you is for carrier unlocked Pixels. I haven't had a carrier locked phone in many years so my memory of what is possible is probably a bit fuzzy.
desertcat said:
Unlocking the bootloader on Pixel phones is pretty easy. You can use the guide here to unlock the bootloader.
You will need to use ADB. If you are not familiar with ADB, you can use the guide found here.
I'm assuming that you want to unlock the bootloader so that you can root your Pixel. I used this guide.
I reread your post and noticed that you bought a Pixel that is carrier locked to Verizon. Usually, unlocking the bootloader of a Verizon phone is either not possible or difficult. The information that I gave you is for carrier unlocked Pixels. I haven't had a carrier locked phone in many years so my memory of what is possible is probably a bit fuzzy.
Click to expand...
Click to collapse
The phone is not carrier locked, but it was a verizon phone previously. Thanks for the links, and basically my problem I run into is the Greyed out unlock option in developer settings.
Have you tried doing a factory reset and then allow the phone to update over wi-fi?
TurboGSXpixel said:
The phone is not carrier locked, but it was a verizon phone previously. Thanks for the links, and basically my problem I run into is the Greyed out unlock option in developer settings.
Click to expand...
Click to collapse
Remove the sim card, do a factory reset, and then go through the setup without the SIM installed. This should allow the OEM unlock to be toggled. Its worked for multiple other people.
Did you switch from Verizon to Tmobile? It appears from what I'm reading that TMO sims are downloading carrier specific settings/options which block the unlock switch.
Regardless of whether you use tmobile or not, the above method *should* allow you to unlock.
According to this thread( https://slickdeals.net/f/14948867-google-pixel-3-phone-64-gb-pink-169-99?page=16#commentsBox ), one could unlock the bootloader of a Verizon 3 with the following method. I have already installed this month's update, so I cannot test it for now. If you have a Verizon Pixel 3 and have not installed this month's update, can you test this?
"
remove sim (!!!) if you ran it before with the sim inside - remove sim and do factory reset TWICE
connect to wifi
let it download the update
DONT INSTALL UPDATE
go to About Phone -> Build Version. Click it 10 times until it tells you're the Developer now
go to Developer menu
wait until the OEM unlock option becomes clickable (happens after system update is downloaded, but NOT installed)
toggle OEM unlock (result: should be enabled)
Enable USB debug on the phone (also Developer menu)
connect the device to your win/mac/linux machine with adb installed with USB cable with data pins. Phone will ask if you authorize your PC to USB debug it
from your PC run : "adb reboot bootloader". That will reboot your phone to bootloader with message and status "locked"
from your PC while your phone is in fastboot mode: "fastboot flashing unlock" (that should respond with
OKAY [ 0.356s]
Finished. Total time: 0.368s)
You're good now. It's bootloader unlocked. you can install any updates. It will not lock itself and can install any other 3rd party firmware (on your risk, sure)"
No replies... So, the method does not work?
yourrealking said:
No replies... So, the method does not work?
Click to expand...
Click to collapse
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
dcarvil said:
According to this thread, you have to do it when initially setting up the phone, before connecting to Verizon.
https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Click to expand...
Click to collapse
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?
yourrealking said:
That means that only never-used Verizon Pixel3 can be bootloader-unlocked using that method, and used Verizon Pixel3 phones has no chance of unlocking the bootloader, is that right?
Click to expand...
Click to collapse
That is the way I understand it.
dcarvil said:
That is the way I understand it.
Click to expand...
Click to collapse
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
It shouldn't hurt to try, but if it is a Verizon phone it is unlikely to work.
Ele Na said:
Is there any way for refurbished Pixel 3a XL to get bootloader unlocked? The main issue is OEM unlocking greyed out. Is there any sense to try this method?
Click to expand...
Click to collapse
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.
yourrealking said:
I have given up. I will wait until the official software support from Google ends (later this year). End of support means that whatever exploit will be found will not be patched by Google, so if people could find a way to unlock the bootloader using some security vulnerabilities, the method will reliably work from that point on for ever.
Click to expand...
Click to collapse
Even for Verizon version?
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