Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
whiggs2 said:
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Click to expand...
Click to collapse
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
jwoegerbauer said:
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
Click to expand...
Click to collapse
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
whiggs2 said:
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
Click to expand...
Click to collapse
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
SubwayChamp said:
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
Click to expand...
Click to collapse
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Droidriven said:
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
Click to expand...
Click to collapse
This - The 'U' devices do not have OEM unlock by default.
whiggs2 said:
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Click to expand...
Click to collapse
This may be just a kind of starting point, to have in mind, but that need more research though, I did it in my GN8 but with your device, things may be different.
There are some things you have to check, in the download screen, KG has to be completed, not prenormal or checking, also search for the CSCs that are compatible for your device, this is one of the tutorial, kind of, that I followed https://www.getdroidtips.com/guide-...ocked-firmware-galaxy-note-8-sm-n950u-n950u1/
Related
Alright, so, last weekend I got a new Samsung Galaxy J7 with Android 6.0.1. The first thing I did was rooting it. It was all going fine until I accidentally unticked the "OEM Unlock" option on Developer Mode, so when I rebooted it, it had an FRP Lock.
I used a Latin American firmware to be able to boot it again. At boot, there was this "entel" logo, and this seemed to have changed my IMEI because my phone always said Network Unavailable. I didn't check the IMEI prior to rooting it, but I noticed the printed one and the one shown on the phone weren't the same... but this isn't the real problem.
Originally, the phone was unlocked (no specific carrier/operator holding it), and I somehow "fixed" the Network Unavailable thing by erasing the efs folder on root... well, it was a longer process than just deleting it, I backed up the folder and copied some files (some might know what I'm talking about). After that, the IMEI was the same than the printed one, but, my phone is now network SIM locked!
I have to input a code to unlock it. I did some googling and apparently only the carrier can give it to you, so I tried 3 different carrier SIM cards to see if any of them were the carrier's, but none of them worked as accepted,and I don't know what carrier could it be... I'm even worried it may be a Latin American one (from Chile or Argentina maybe since that's where the firmware used was from) and I won't be able to get it.
I know there are websites to get a code, but I don't want to pay so much and risk getting scammed.
I tried to see if "entel" was a carrier to unlock it, but it didn't help.
Also, when I try to choose a network on Mobile Networks settings, the only available one is AT&T (which I don't use/have a SIM of), but when I accessed their website to unlock, it said my IMEI wasn't registered as theirs apparently.
Then, I also tried using Samsung's Smart Switch application on PC with the Device Initialization option, but when I try to use the firmware from that I get a SW REV. Check Fail.
I might be wrong, but I feel that since messing with the system files/root was what changed it, maybe I can fix it the same way with no unlock code or carrier help.
So, does anyone have advice, or know some other way to reset it? Or do I really have to go get it fixed/unlocked somewhere?
frostx said:
Alright, so, last weekend I got a new Samsung Galaxy J7 with Android 6.0.1. The first thing I did was rooting it. It was all going fine until I accidentally unticked the "OEM Unlock" option on Developer Mode, so when I rebooted it, it had an FRP Lock.
I used a Latin American firmware to be able to boot it again. At boot, there was this "entel" logo, and this seemed to have changed my IMEI because my phone always said Network Unavailable. I didn't check the IMEI prior to rooting it, but I noticed the printed one and the one shown on the phone weren't the same... but this isn't the real problem.
Originally, the phone was unlocked (no specific carrier/operator holding it), and I somehow "fixed" the Network Unavailable thing by erasing the efs folder on root... well, it was a longer process than just deleting it, I backed up the folder and copied some files (some might know what I'm talking about). After that, the IMEI was the same than the printed one, but, my phone is now network SIM locked!
I have to input a code to unlock it. I did some googling and apparently only the carrier can give it to you, so I tried 3 different carrier SIM cards to see if any of them were the carrier's, but none of them worked as accepted,and I don't know what carrier could it be... I'm even worried it may be a Latin American one (from Chile or Argentina maybe since that's where the firmware used was from) and I won't be able to get it.
I know there are websites to get a code, but I don't want to pay so much and risk getting scammed.
I tried to see if "entel" was a carrier to unlock it, but it didn't help.
Also, when I try to choose a network on Mobile Networks settings, the only available one is AT&T (which I don't use/have a SIM of), but when I accessed their website to unlock, it said my IMEI wasn't registered as theirs apparently.
Then, I also tried using Samsung's Smart Switch application on PC with the Device Initialization option, but when I try to use the firmware from that I get a SW REV. Check Fail.
I might be wrong, but I feel that since messing with the system files/root was what changed it, maybe I can fix it the same way with no unlock code or carrier help.
So, does anyone have advice, or know some other way to reset it? Or do I really have to go get it fixed/unlocked somewhere?
Click to expand...
Click to collapse
Did you ever get anywhere with this? I am trying to switch carriers from t mobile to boost on the Sm-j700f and I need to unlock it
So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota
My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
andrepd said:
Hi, I bought a refurbished Pixel 3. I tried to unlock bootloader by: starting the device, skipping all set-up, enabling developer options, trying to enable "OEM unlocking". But it is greyed out with message "Connect to the Internet or contact your operator".
Then I tried to connect to wifi, still same message. Then I inserted a SIM card, still same message. I also rebooted a couple times, still nothing. Doing "adb reboot bootloader" shows that the bootloader is locked.
So what does this mean? I looked up online that some phones are from Verizon so they will not be able to be unlocked. Is this the case? How can I check this? If the bootloader is not unlockable I'm just going to return it x) which will be a pain in the a** since I'll have to pay return shipping and everything.
Thanks for any help!!
Click to expand...
Click to collapse
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
dcarvil said:
The IMEI will tell you if it is a Verizon phone. I believe Verizon IMEIs begin with 35. Google "IMEI lookup" and you'll find plenty of sites that will give you information on that phone.
Click to expand...
Click to collapse
Thanks, I tried that, it is indeed a Verizon model. Do you know if there is any way around this to unlock the bootloader? I guess I'll have to google around a bit to figure out if it's hopeless or not x)
There is no way to unlock a Verizon phone.
Hmm well I'm getting quite mixed signals here:
- imei.info says "Pixel 3 128GB, US VZ, Just Black"
however:
- ro.oem_unlock_supported is 1
- and bootloader screen says "Product revision: MP1.0(ROW)", not "(VZW)"
- box says "ESIM" rather than "SIM"
and also in some threads users report being able to unlock verizon phones... So it's all very strange x)
Pretty much same here. Did you figure out something?
me too
Ok, so a brief update here, the results of my search over the last couple of days:
Most likely, your Pixel 3 cannot be unlocked, it has been locked by Verizon when activated on their network and we don't have a way to undo this OEM lock. If you bought it re-furbished or second hand, and OEM Unlocking is grayed out, the most likely is that there is nothing to do.
Relevant / connected threads:
- https://forum.xda-developers.com/t/oem-unlocking-grayed-out.3860023/page-21
- It can be unlocked before it has activated on verizon: https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
- Some (unsuccessful) attempts are discussed at https://forum.xda-developers.com/t/bounty-unlock-bootloader-vzw-pixel-3-xl.3856605/page-113 and
Use 'fastboot oem citadel' to unlock bootloader? (Verizon Pixel 3)
I unfortunately have a Pixel 3, from Verizon (when I bought it it was not described as a phone issued by Verizon had I known it I wouldn't have bought it). I'm trying to accomplish The impossible by finding some way to unlock the bootloader...
forum.xda-developers.com
- This post pretends that it can be undone, but this has not been confirmed / applies only to very speecific cases:
https://www.reddit.com/r/GooglePixel/comments/sc2w1r
- https://support.google.com/pixelpho...ixel-3-verizon-flashed-3xl-system-image?hl=en
-
https://www.reddit.com/r/GooglePixel/comments/rsrnu0
Hello everyone,
sorry if it's a common issue, here and not, but i can't find a way to do a thing i'm trying to do since months........
I bought 3-4 months ago a Nord CE 2 and i still haven't found a way for disabling the need to insert the pin when i turn it on, so it can connect to radio capability and all the connections.
I'm not talking about the sim block, but the entire connectivity. In my last phone (Lenovo P2) it was called "secure boot", and i disabled it.
I followed a tutorial for obtaining it: i removed the sequence pin, and re-setted it, but the option of disabling at boot what i need did not appear in my phone.
Any help or direction to follow?
Many thanks in advance.
Greetings.
mbrancalion said:
Hello everyone,
sorry if it's a common issue, here and not, but i can't find a way to do a thing i'm trying to do since months........
I bought 3-4 months ago a Nord CE 2 and i still haven't found a way for disabling the need to insert the pin when i turn it on, so it can connect to radio capability and all the connections.
I'm not talking about the sim block, but the entire connectivity. In my last phone (Lenovo P2) it was called "secure boot", and i disabled it.
I followed a tutorial for obtaining it: i removed the sequence pin, and re-setted it, but the option of disabling at boot what i need did not appear in my phone.
Any help or direction to follow?
Many thanks in advance.
Greetings.
Click to expand...
Click to collapse
I'm not sure about what secure boot you're referring too
ko_hi said:
I'm not sure about what secure boot you're referring too
Click to expand...
Click to collapse
When i turn on my actual phone and the former one, you can only make emergency call and nothing else, until you insert the sequence pin. Then the phone unlock, and so the normal screen appear, data connection starts, etc.
With my former phone, the Lenovo, there was a way to disable this "secure boot mode", so when i turned on the phone it connected to the web, etc, for downloading messages, email etc, and only the screen remained blocked, as the normal behaviour when phone is already on.
I'd like to obtain this with the Oneplus, but i can't find a way. A maybe a way does not exist....
mbrancalion said:
When i turn on my actual phone and the former one, you can only make emergency call and nothing else, until you insert the sequence pin. Then the phone unlock, and so the normal screen appear, data connection starts, etc.
With my former phone, the Lenovo, there was a way to disable this "secure boot mode", so when i turned on the phone it connected to the web, etc, for downloading messages, email etc, and only the screen remained blocked, as the normal behaviour when phone is already on.
I'd like to obtain this with the Oneplus, but i can't find a way. A maybe a way does not exist....
Click to expand...
Click to collapse
Are you referring to sim pin
Just search sim card lock
If you mean
The extra security for the device (that breaks the decryption in custom recovery that might be called as you say) i haven't seen that option on this device
ko_hi said:
Are you referring to sim pin
Just search sim card lock
Click to expand...
Click to collapse
No, it's not the sim card pin. I always disable it, in all phones.
ko_hi said:
The extra security for the device (that breaks the decryption in custom recovery that might be called as you say) i haven't seen that option on this device
Click to expand...
Click to collapse
I'm started to think that, as you say, in the stock rom it's not possibile to disable it in the Nord.
BTW: this phone has too many things that i don't like. I strongly suspect that it will be my first and last oneplus phone........
mbrancalion said:
No, it's not the sim card pin. I always disable it, in all phones.
I'm started to think that, as you say, in the stock rom it's not possibile to disable it in the Nord.
BTW: this phone has too many things that i don't like. I strongly suspect that it will be my first and last oneplus phone........
Click to expand...
Click to collapse
I don't think it's enabled at all
Sim card lock was enabled by default, as in all the phones i've seen.
I'm talking about another thing.
I'm very thankful for your replies, but they are not on topic.
I think newer phones like my phone oneplus 9 pro and above - you cannot disable secure boot. If you boot into bootloader menu, you will see it say something like "SECURE BOOT - YES".
I believe qualcomm processors have it forcibly enabled.
I'm not going to mess up with unlocking it, etc.
I don't use Windows, too......
I'm starting to be very disappointed with this phone. I can't record calls...... It does not update.....Assistants at Oneplus go on replying to me uninformed and unuseful emails.
mbrancalion said:
I'm not going to mess up with unlocking it, etc.
I don't use Windows, too......
I'm starting to be very disappointed with this phone. I can't record calls...... It does not update.....Assistants at Oneplus go on replying to me uninformed and unuseful emails.
Click to expand...
Click to collapse
I wouldn't unlock it either mainly because TWRP is not available for this oneplus nord ce 2 phone and rumors have it there is no known working MSM tool for this phone. Without proper safety measures, I would stay on stock.
immortalwon said:
I wouldn't unlock it either mainly because TWRP is not available for this oneplus nord ce 2 phone and rumors have it there is no known working MSM tool for this phone. Without proper safety measures, I would stay on stock.
Click to expand...
Click to collapse
TWRP is available for Android 11.
And an update will come today or tomorrow for android 12.
regarding staying safe, i've found a way to be able to play it safe with this phone
ko_hi said:
TWRP is available for Android 11.
And an update will come today or tomorrow for android 12.
regarding staying safe, i've found a way to be able to play it safe with this phone
Click to expand...
Click to collapse
TWRP may officially support A11, that does not mean it supports every device. If you go on official TWRP website, the device the OP is talking about is not on the supported list.
immortalwon said:
TWRP may officially support A11, that does not mean it supports every device. If you go on official TWRP website, the device the OP is talking about is not on the supported list.
Click to expand...
Click to collapse
Sorry i meant it is unofficially supported for our device, and by on A11 i didn't mean any other device then ours
jeeze louise man, its like a barren wasteland in here....
I concur. Seems like this forum is oriented to newer phones. I have a J3 and hope to be able to load a custom OS on it.
Did you figure out how to unlock the bootloader on your phone? I'm still trying to get to the "hidden" OEM unlock in the developers options. If you were able to figure out how to do it, please share.
If you haven't unlocked the bootloader, a custom rom will be impossible to load.
You need turn on OEM unlock. You go to settings, about phone, software information, you tap on "build number" 7 times. This unlocks Developer settings which should be at the bottom of the settings page. OEM unlocking should be one of the options, but be aware iirc it should factory reset your device so back your things up. After that you can install twrp, here's the link to the page for the J3: https://forum.xda-developers.com/t/...axy-j3-2017-sm-j330f-j330fn-j330g-ds.3709056/
As for finding a custom ROM for this device, good luck, you'll need it.
Hope all this helps.
LegendaryCheerio said:
You need turn on OEM unlock. You go to settings, about phone, software information, you tap on "build number" 7 times. This unlocks Developer settings which should be at the bottom of the settings page. OEM unlocking should be one of the options, but be aware iirc it should factory reset your device so back your things up. After that you can install twrp, here's the link to the page for the J3: https://forum.xda-developers.com/t/...axy-j3-2017-sm-j330f-j330fn-j330g-ds.3709056/
As for finding a custom ROM for this device, good luck, you'll need it.
Hope all this helps.
Click to expand...
Click to collapse
Thank you for taking the time to reply. I have been trying for weeks to get OEM unlock to appear in my Developer Options. I've tried reading every article and watching every youtube video on how to do this, and none of them will unhide the OEM unlock.
I appreciate you sending me the link. Maybe I missed it, but that appears to be telling you how to install TWRP using Odin. Are you suggesting installing TWRP with the bootloader locked?' Or was that intended to be done after the unlock was successful?
All the articles I read suggest setting the time back a week or so. That might work if you just bought a phone, but mine is about 5 years old. Nevertheless, I have tried it many times and it doesn't unhide OEM unlock.
Is there another way to unlock the bootloader? Any idea why Samsung made it so difficult? I tried calling Samsung support and of course they were zero help, telling me that OEM unlock was for level 2 Samsung technicians and not mere mortals.
If you have any further thoughts or suggestions, they would be most welcome, as I have pretty much hit a brick wall.
BigZ1 said:
Thank you for taking the time to reply. I have been trying for weeks to get OEM unlock to appear in my Developer Options. I've tried reading every article and watching every youtube video on how to do this, and none of them will unhide the OEM unlock.
I appreciate you sending me the link. Maybe I missed it, but that appears to be telling you how to install TWRP using Odin. Are you suggesting installing TWRP with the bootloader locked?' Or was that intended to be done after the unlock was successful?
All the articles I read suggest setting the time back a week or so. That might work if you just bought a phone, but mine is about 5 years old. Nevertheless, I have tried it many times and it doesn't unhide OEM unlock.
Is there another way to unlock the bootloader? Any idea why Samsung made it so difficult? I tried calling Samsung support and of course they were zero help, telling me that OEM unlock was for level 2 Samsung technicians and not mere mortals.
If you have any further thoughts or suggestions, they would be most welcome, as I have pretty much hit a brick wall.
Click to expand...
Click to collapse
Hi, when the "OEM Unlock" option is invisible, you need to search update, disable and re-enable developer option.
I'm sorry for my bad english but i hope that will help you.
LinkyWolfka said:
Hi, when the "OEM Unlock" option is invisible, you need to search update, disable and re-enable developer option.
I'm sorry for my bad english but i hope that will help you.
Click to expand...
Click to collapse
I don't understand what you meant by "you need to search update".
If you meant to click on system updates and then check for an update, I tried that, then I disabled and re-enabled developer option. OEM Unlock is still missing.
If you meant something else, please explain. Thanks for helpling.
I've heard there can be a 7 day lock period for some Samsung devices to unlock OEM, or even just straight out unavailable in certain regions. Worst case scenario you could flash the OS from a different region.
Well, I'm about to give up on this phone. I haven't been able to find any Custom ROMs for it. So there is little value in spending more time trying to figure out how to unlock the bootloader. I think the OEM Unlock feature is not available to USA customers.
Thanks for your assistance.