Hello,
I just got the Samsung Galaxy Note 10+ on September 30th, SM-N975U1 variant, and I cannot toggle the OEM unlocking because it is missing. I read that this is due to the KG state of the phone and I would have to wait 7 days for it to be an option to toggle. I am trying to find out from other Note 10+ users with the same variant as mine if the option appeared after waiting 7 days?
BadBoy2K7 said:
Hello,
I just got the Samsung Galaxy Note 10+ on September 30th, SM-N975U1 variant, and I cannot toggle the OEM unlocking because it is missing. I read that this is due to the KG state of the phone and I would have to wait 7 days for it to be an option to toggle. I am trying to find out from other Note 10+ users with the same variant as mine if the option appeared after waiting 7 days?
Click to expand...
Click to collapse
Unfortunately the "U" variant does not have an unlockable bootloader. The OEM toggle is not there so that variant cannot be rooted (no USA variants can at the moment).
Exynos equals root.
carandcar said:
Unfortunately the "U" variant does not have an unlockable bootloader. The OEM toggle is not there so that variant cannot be rooted (no USA variants can at the moment).
Click to expand...
Click to collapse
For realsies? none of the "U" Variant... So I cant root my note 10+ SM-N975U? Dang that really grinds my gears!!!!!!!!
Leave it to samsung to figure out a new way to keep people from rooting their phones... "Hey lets get rid of the OEM unlock toggle, that way they cant unlock the bootloader and root their phone, and will have to keep all the bloatware we, and their carrier, force down their throats against their will, whether they want to or not."
I knew I never should have bought this phone. I swore 6 years ago I would never own another Samsung Device, but then they came out with this cool new phone and I wanted it so bad. I should have just waited until the pixel 4 XL came out and bought it instead.
Guess I'll Know better next time around at least, and by the time I need a new phone hopefully all phones will have the inscreen ultrasonic fingerprint reader.
I HATE YOU SAMSUNG!!!!!!!!
1. You could have informed yourself prior to buying, it is common knowledge US SD-models have locked bootloader and cannot be rooted...
2. It is merely a US-provider requirement to have locked bootloader, not Samsung's choice. Note 10/10+ is rootable in most other parts of the world..
OnnoJ said:
1. You could have informed yourself prior to buying, it is common knowledge US SD-models have locked bootloader and cannot be rooted...
2. It is merely a US-provider requirement to have locked bootloader, not Samsung's choice. Note 10/10+ is rootable in most other parts of the world..
Click to expand...
Click to collapse
What do u mean SD Models? Also if it's a us provider requirement then how come you can buy phones that have the OEM unlock option available on them?
Also this page is the first I even heard of it... Every time I search it shows that 7 days after you activate it the OEM unlock shows up. And on top of that just because it's not rootable at the time of purchase doesn't mean somewhere down the line someone won't figure out how to.
In fact my last phone was sold by a carrier, as carrier unlocked, and it had the bootloader toggle on it as well which made rooting a breeze.
I'm sorry but I don't agree with you... It has nothing to do with carriers, it's Samsung who has removed this feature not carriers. This is actually the first phone I've heard of that has the oem bootloader removed from the android software.
And besides that if you buy the carrier unlocked version of the note 10+ it should be your choice what you do with it not carriers and not manufactures.
Oh also I found an article (link below) Where someone managed to root the note 10+ SM-N975U with a patched boot image, which I would assume would also work for SM-N975U1 as well.
So like I said it's only a matter of time before someone figured out how to root it anyway. And my post was me griping at Samsung for doing what they did, and staying if I had waited I could have gotten a device that is made by a company that isn't actively trying to thwart rooting.
Link: http://androidbiits.com/root-samsung-galaxy-note-10-plus-sm-n975u-sm-n975u1-easily/
SD=Snapdragon, the SoC of the N975U/N975U1 phones. Those devices for US market have the locked bootloader.
The models with Exynos SoC (Samsung's own SoC), in models of most international markets N975F have working OEM unlock option and thereby unlockable bootloader.
Why would Samsung provide unlockable bootloader for one part of the world, but not for US where phones have US SoC (I.c. Snapdragon)? You tell me...
Maybe you can join this club: https://forum.xda-developers.com/galaxy-note-10+/how-to/bounty-sm-n975u1-note-10-usa-unlocked-t4006249
gkennedy88 said:
What do u mean SD Models? Also if it's a us provider requirement then how come you can buy phones that have the OEM unlock option available on them?
Also this page is the first I even heard of it... Every time I search it shows that 7 days after you activate it the OEM unlock shows up. And on top of that just because it's not rootable at the time of purchase doesn't mean somewhere down the line someone won't figure out how to.
In fact my last phone was sold by a carrier, as carrier unlocked, and it had the bootloader toggle on it as well which made rooting a breeze.
I'm sorry but I don't agree with you... It has nothing to do with carriers, it's Samsung who has removed this feature not carriers. This is actually the first phone I've heard of that has the oem bootloader removed from the android software.
And besides that if you buy the carrier unlocked version of the note 10+ it should be your choice what you do with it not carriers and not manufactures.
Oh also I found an article (link below) Where someone managed to root the note 10+ SM-N975U with a patched boot image, which I would assume would also work for SM-N975U1 as well.
So like I said it's only a matter of time before someone figured out how to root it anyway. And my post was me griping at Samsung for doing what they did, and staying if I had waited I could have gotten a device that is made by a company that isn't actively trying to thwart rooting.
Link: http://androidbiits.com/root-samsung-galaxy-note-10-plus-sm-n975u-sm-n975u1-easily/
Click to expand...
Click to collapse
lol they sure get a lot of clicks with that fake news
try setting a lock. i've had this same issue and thats what worked for me. Although when i unlock and root, it factory reset which sucked.
OnnoJ said:
1. You could have informed yourself prior to buying, it is common knowledge US SD-models have locked bootloader and cannot be rooted...
2. It is merely a US-provider requirement to have locked bootloader, not Samsung's choice. Note 10/10+ is rootable in most other parts of the world..
Click to expand...
Click to collapse
Well why not do a oneplus/google thing where unlocked versions have unlockable bootloaders while carrier versions don't?
Note 10+ Snapdragon
It is a nice device stock, after flashing the N975U1 firmware with ODIN, and disabling (at least), about 150 system-apps with ADB, it is fast and efficient.
I can't imagine how nice the Note 10+ would be with administrative rights.
Its been a very long time since i have done any of this stuff. I bought the verizon version and cannot get bootloader unlocked. I have searched and see there has been the same problem in the past models. Is there a bypass or workaround? I can only find one for early Pixel products.
Kpwise509 said:
Its been a very long time since i have done any of this stuff. I bought the verizon version and cannot get bootloader unlocked. I have searched and see there has been the same problem in the past models. Is there a bypass or workaround? I can only find one for early Pixel products.
Click to expand...
Click to collapse
nvmnd. found my answer
Kpwise509 said:
nvmnd. found my answer
Click to expand...
Click to collapse
I am in the same boat.. curious to what answer you found?
m1ng15 said:
I am in the same boat.. curious to what answer you found?
Click to expand...
Click to collapse
I found another thread on here after I searched, and searched. From what I understand now. If it's a Verizon pixel the bootloader is locked permanently.
If you purchased your device from Verizon, or a Verizon variant from a 3rd party retailer (Best buy, Costco, etc.) the bootloader is locked tight!
If you want the option to root; return your VZW device and order one directly from Google.
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
mustangtim49 said:
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
Click to expand...
Click to collapse
Incorrect. SIM unlocking is not necessarily related to bootloader unlocking. While T-Mobile (and I think AT&T) users on here have found and reported that when they achieve SIM unlocking on their variants, that they can then bootloader unlock as well, Verizon has for a very, very long time enforced bootloader lock with all their will.
The only exceptions that I've ever heard of were not by choice of Verizon, but by hacks/vulnerabilities. Such as the VS985 LG G3, there was an exploit that didn't actually bootloader unlock, but more made it so that the locked bootloader didn't really matter. On the Pixel 1, if you had the Verizon variant and were still on Android 7.10 or below, you could unlock the bootloader, but once the 7.11 OTA came out, if you hadn't already unlocked the bootloader (or at least toggled the toggle), then you were locked in until a foreign national found a hacking way to get in, but they charge for it. All this while Verizon phones have been ultimately SIM unlocked for similarly a very long time.
mustangtim49 said:
It's not necessarily true, according to Verizon, they Sim unlock their phones after 60 days. Once that is done, we should be able to to check oem unlocking option in developers options and unlock the bootloader. Am I missing something?
Click to expand...
Click to collapse
You might be thinking 'carrier unlocked' vs "bootloader unlocked".
VZW does NOT like people rooting their devices so they have locked the bootloaders for several years now. I honestly don't even think any devs are working on a workaround/bypass for VZW devices anymore because they've had a long history of tightly locking down their device's bootloaders.
Az Biker said:
You might be thinking 'carrier unlocked' vs "bootloader unlocked".
VZW does NOT like people rooting their devices so they have locked the bootloaders for several years now. I honestly don't even think any devs are working on a workaround/bypass for VZW devices anymore because they've had a long history of tightly locking down their device's bootloaders.
Click to expand...
Click to collapse
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information.
If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point.
I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
I seriously doubt the "60 day sim unlock" allows the bootloader to be unlocked, otherwise we'd have a ton of VZW variant threads filled with development, and devices that are 61 days old, rooted, and running custom Roms.
But we don't. We don't have even have any developers working on VZW devices, regardless of age. So deductively thinking, the "60 day sim unlock" doesn't sound like it's currently an option.
Just my .02 (USD) worth
mustangtim49 said:
Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader.
Click to expand...
Click to collapse
That has never, ever been the case with Verizon variants of phones. 1) Verizon phones have been SIM/carrier unlocked from the get-go for a very long time and 2) Except for rare anomalies like the Pixel 1 on Android 7.10 or below, OEM unlocking was always grayed out.
mustangtim49 said:
Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options.
Click to expand...
Click to collapse
That has never happened on a VZ Pixel and it is not going to happen on this one. Why is this so hard for people to understand?
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
sorry. your misinformed. Pixel devices from Verizon cannot have the bootloader unlocked. Period. end of story.
Have you ever had a Verizon device that was "carrier/sim unlocked" but couldn't unlock the bootloader? I have. and its real, so please research before you post misinformation.
mustangtim49 said:
No, I've been rooting/modding phones since eclair and used to be an XDA News writer, I definitely understand the difference between sim and bootloader unlocking. Once the phone is sim unlocked, the "OEM UNLOCK" option should no longer be greyed out in the developer options. Once that setting becomes available after sim unlock, there shouldn't be anything in the way of unlocking the bootloader. The only thing that could be an issue is if the manufacturer then required a token to unlock the bootloader, but I'm gonna go with Google isn't requiring that. Now, this is all based on my own knowledge and experience, if anyone has more insight to either back me up or shoot me down, please, this is the whole reason we're here in these threads, to gain knowledge and information. If Verizon is so informal about sim unlocking their phones after 60 days, it really doesn't make sense for them to enforce bootloader locking at that point. I mean, what is the point once they cut you loose with your sim card? Check this out, I had this ****ty Nord 10 5G from Metro and a guy figured out which apps to remove via ADB to carrier unlock the phone, hence making the OEM UNLOCK choice available in developer settings. What I'm saying is sometimes things aren't as locked down as you think, I mean, Metro is pretty strict on carrier locking their phones and really don't like doing it after you've met all the requirements. So if it's as easy as getting rid of a few apps via sneaking through ADB, it's gotta be that way for all the phones it's not like they're running different software (other than version level) they're all Android. Maybe this information will inspire someone on here that knows way more than me to figure out how to unlock a Verizon locked bootloader. If I'm correct, they really don't have that power to lock the bootloader, only to take away our option to do so by "sim/carrier" locking the phone which the software is told to take away our ability to choose that option. Please, anyone, I honestly would like to know if I'm wrong, but don't just say I'm wrong, explain to me and the rest of us. Thanks guys and girls!!!
Click to expand...
Click to collapse
Unfortunately, and I hate to be the bearer of bad news because I didn't want to find this out for myself lol (but of course I really did), but I can tell everyone that I have the Verizon version and after 60..well a little after that because of course it was not as easy as their terms say on their website that it will automatically unlock after 60 days...yeah right..I had to call and chat I cant even tell you how many times...to finally get the right person to help me...which turned into waiting a few more days but he came through and unlocked it....
so the bad news: the oem unlock in developer options is still greyed out. Now it says to contact your carrier or connect to the internet
I still have hope for maybe one day? i mean there is ALWAYS a way to do anything on phones..someone smart enough just has to figure it out
mrindependent said:
Unfortunately, and I hate to be the bearer of bad news because I didn't want to find this out for myself lol (but of course I really did), but I can tell everyone that I have the Verizon version and after 60..well a little after that because of course it was not as easy as their terms say on their website that it will automatically unlock after 60 days...yeah right..I had to call and chat I cant even tell you how many times...to finally get the right person to help me...which turned into waiting a few more days but he came through and unlocked it....
so the bad news: the oem unlock in developer options is still greyed out. Now it says to contact your carrier or connect to the internet
I still have hope for maybe one day? i mean there is ALWAYS a way to do anything on phones..someone smart enough just has to figure it out
Click to expand...
Click to collapse
This was the same for the Verizon Pixel 2 XL, and every Verizon Pixel since. No unlockable bootloader unfortunately.
My first foray into rooting was with the Galaxy Nexus. That had no issues unlocking the bootloader, and was the last phone I've bought at a store.
It's sad, that I can bring my rooted device and get a new line, but I can't tinker with their versions if I were to buy one at a store, online, whatever.
Their loss imo as there are a number of us I think, who would buy at the store if we could unlock the bootloader. I guess we as a group aren't big enough for them to worry about though.
You can however, play musical SIM card between devices, and it works. For the most part anyways.
I hate this.
What do they think people are just going to accidentally stumble on this, mistakenly download specific apps and Roms and out of the blue, randomly, and incorrectly, flash a very specific file causing the phone to brick and they don't want to keep fixing it?
Cause those Muppets all have iPhones...
Beyond stupid.
And here I was, done with how Samsung limited this process, so I ditched it for the shiny new Pixel... I'm the Muppet
tmessy said:
And here I was, done with how Samsung limited this process, so I ditched it for the shiny new Pixel
Click to expand...
Click to collapse
Every Verizon variant of phones is locked down, and certainly, historically different models of them have been able to be either unlocked, or most of the time as far as I've experienced a workaround (security vulnerability) to unlocking was found (IIRC, the Stump method on LG phones worked this way), and the (again, as far as I'm aware) single time(s) that a Verizon phone was able to be bootloader unlocked as if it was made to be able to do so from the get-go, more or less: The Pixel 1 on Android 7.10 or below, and there is some foreign hacking method which can exploit some secret vulnerability if you're willing to pay to still be able to bootloader unlock the Pixel 1.
In my opinion, Samsung limits are even worse than the carrier-imposed limits, as Samsung keeps their phones from being bootloader unlocked on every U.S. Carrier, and even the direct from Samsung bought in the U.S. factory carrier unlocked model, but please correct me if I'm wrong. I only know the experience with the phones I've actually owned and what I remember from reading about others' experiences, however. The Exynos-based versions of Samsung phones are able to be bootloader unlocked at least in most countries, and again IIRC, some Snapdragon-based Samsungs in one or a few select countries too. Sony officially allows their bootloaders to be unlocked, but they purposefully and permanently gimp your phone's features if you do - and some other OEMs do similar, I'm given to understand.
I know it's frustrating about Verizon. Besides no longer buying carrier-specific models of phones, I no longer use Verizon as well, but it sucks for those who really need the carrier incentives.
roirraW edor ehT said:
Every Verizon variant of phones is locked down, and certainly, historically different models of them have been able to be either unlocked, or most of the time as far as I've experienced a workaround (security vulnerability) to unlocking was found (IIRC, the Stump method on LG phones worked this way), and the (again, as far as I'm aware) single time(s) that a Verizon phone was able to be bootloader unlocked as if it was made to be able to do so from the get-go, more or less: The Pixel 1 on Android 7.10 or below, and there is some foreign hacking method which can exploit some secret vulnerability if you're willing to pay to still be able to bootloader unlock the Pixel 1.
In my opinion, Samsung limits are even worse than the carrier-imposed limits, as Samsung keeps their phones from being bootloader unlocked on every U.S. Carrier, and even the direct from Samsung bought in the U.S. factory carrier unlocked model, but please correct me if I'm wrong. I only know the experience with the phones I've actually owned and what I remember from reading about others' experiences, however. The Exynos-based versions of Samsung phones are able to be bootloader unlocked at least in most countries, and again IIRC, some Snapdragon-based Samsungs in one or a few select countries too. Sony officially allows their bootloaders to be unlocked, but they purposefully and permanently gimp your phone's features if you do - and some other OEMs do similar, I'm given to understand.
I know it's frustrating about Verizon. Besides no longer buying carrier-specific models of phones, I no longer use Verizon as well, but it sucks for those who really need the carrier incentives.
Click to expand...
Click to collapse
NOt every verizon phone, The samsung s20 bootloader was able to be unlocked.
lucky_strike33 said:
NOt every verizon phone, The samsung s20 bootloader was able to be unlocked.
Click to expand...
Click to collapse
As it came without some temporary trick or vulnerability someone was able to take advantage of?