Hi all,
I have spent over 9 hours trying with ODIN, Offical and unofficial guides, Youtube tutorials and the lot, and I cannot figure this out for the life of me. So I wanted to ask anyone to ease the pain I am currently feeling. I have an international S22 (SM-S901B), and CSC is: "EUX" The option to unlock OEM is not there, yet when I boot into "Download Mode", it states, "OEM Lock: ON(L)", which indicates to me it Perma locked, is there any CSC out there that would give me the option?
In regards to this, I am getting the strangest of errors called, "Cause: Custom binary (VBMETA) blocked due to remaining instalment balance (1)" when I try flashing custom ROM. I am just lost at this point; someone, please give me the strength to resolve this issue.
Greetings, I encountered something similar during a brick I had with an S8 device a few years ago, my OEM toggle option was not available from the start.
https://forum.xda-developers.com/t/...ormal-on-oneui-android-pie-9-0.3911862/page-4 : Check my post at page 4. I noticed that the OEM toggle is only available after some time using the ROM, I don’t remember if it also depends on CNC, give it a try.
Edit : skip the flash firmware part since your bootloader is locked, try doing a factory reset instead, then follow the steps to see if the OEM toggle becomes available.
You owe or some one owes money on the device and payment services are enabled. So Knox guard is keeping the bootloader locked uuntil payment services are paid and released
TheMadScientist said:
You owe or some one owes money on the device and payment services are enabled. So Knox guard is keeping the bootloader locked uuntil payment services are paid and released
Click to expand...
Click to collapse
I already paid for the device in full, do you think I should contact Samsung support about it?
Related
Is this possible to skip? Can we unlock with adb / fastboot or is that not going to work / likely to brick the device?
Unlock Resposibly
adb or fastboot unlock will only work after 14 days of waiting. It is to allow you to rethink your decision. OEM unlock will obviously void your warranty and applications like Android pay will stop working. Trust me, relocking will not be easy as unlocking. Even if you somehow get it relocked, Android pay will still not work for you. So, unlock responsibly.
Thanks for the reply . I'm really doing it for root access, modifying the hosts file, changing fonts and boot animation, but the latter two aren't necessities.
I don't use Android pay (don't use contactless) but I am a little concerned that online banking will cease to function when the phone is on a stock firmware and rooted. If there's an effective system wide ad blocker I may use that instead.
For hosts file, I recommend dns66, available through fdroid, no root required.
i have found that many banking apps will continue to work with root provided you also have a hide root app installed but android pay is a no go.
jk77 said:
For hosts file, I recommend dns66, available through fdroid, no root required.
Click to expand...
Click to collapse
Thanks! First I've heard of fdroid, looks very useful, and dns66 does exactly what I was planning on doing.
Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?
cutom rom
Albert612103 said:
Need to put Android 10 so only way is custom ROM. How to put custom rom without OEM unlock?
Click to expand...
Click to collapse
there is no way. Should be rooted
CHEERS
Hello guys.
For those having bootloader unlock server issue (normally everybody), there's a post on the Lenovo forum that gives the origin of the issue:
https://forums.lenovo.com/t5/P2-P2a...-bootloader/m-p/4574568/highlight/true#M12457
In fact, the problem seems coming from an non renewed SSL Certificate in the Lenevo server tracking the OEM Unlocking requests.
The suggestion given by fls2 is to change the date of the P2 phone to a previous date than the 10 July 2019 and the Bootloader Unlocking process should be launched.
That's what I've done with a second P2 I bought that has its bootloader locked.
I set the date to 10th of April 2019 and the phone is now waiting for 14 complete days to engage the OEM Bootloader unlock instead of the usual Lenovo ID error pop-up.
I'll wait for the process to end and see if everything went fine, but it seems that it should be OK as it was with my first P2 phone.
I'll keep you informed if there are some trouble in the process but I stay confident.
In case of success, we should address a very big "thank you" to fls2 for pointing out the issue with Lenovo server.
20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...
Hello everyone,
As I have written in my last post, I've used the suggested method of manually changing the date to one before the 10th July 2019.
So, as I've said, the 14 days counter has been correctly launched and I was able to see the counter evolving from 14 to 2 days.
Then I was a little bit busy and I haven't followed my P2 phone until last week-end.
When I tried to consult the status of the bootloader unlocking request, I had the same annoying pop-up telling me there's a problem with my account.
The date was fixed to 10th of April 2019 manually, but still had connection error pop-up.
I then tried to switch to current day date of the week-end (29/02/2020), and tried to check again the bootloader unlock status: Annoying pop-up again.
Before giving up, I've tried putting another date manually but at least 14 days after the one I've put when I made my first request and still before the 10th of July 2019, so I switched to 10th of June 2019.
This time, when I checked the bootloader unlock request, I've got no error and had a positive bootloader unlock message that told me the phone is going to reboot and erase all user data that are present.
The phone has rebooted in Fastboot mode and I was able to send the awaited "fastboot oem unlock" command from my laptop.
I didn't try to reboot the system and see if the fastboot command will work if I go in fastboot mode by myself, because I didn't want to miss the opportunity to succeed in unlocking the bootloader of this phone.
I let the people brave enough to try if they feel comfortable with that.
Now this phone is working with an AICP Android Q ROM that seems very stable.
@ Albert612103
20 days have passed since registered. Always shows error.
Unable to unlock OEM.
Don't know what to do...
Click to expand...
Click to collapse
Try to follow my steps.
There's no reason I've succeded and you cannot.
I'm sure you'll be able to unlock your bootloader as I've done.
If you have some question, just feel free to ask.
I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks
xavicosco said:
I'm trying to unlock the bootloader too. Is there any way to avoi waiting 15 days? I'm still using the Stock Rom by default (Android 6).
According to the last comment in the Lenovo forum, the changing date no longer works.
Thanks
Click to expand...
Click to collapse
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.
mahmutpekkara said:
AFAIK, no. You need to wait that. Also there is bigger problem than that which its the unlocking bootloader (server problem). Just you can read above, for no reason you cannot unlock bootloader.
Click to expand...
Click to collapse
@mahmutpekkara somehow I managed to unlock the OEM. It took me few attempts tho, so I'm guessing their servers are not always operating. No needed to change the date in my case.
Only 3 days remaining, so hopefully everything goes well.
So, after 15 days waiting I was getting the message ''Server sync data success'. I managed to get thru by signing off and signing in again with another account. Flashed properly and enjoying Syberia OS
I recently got a 7x from ebay.co.uk. I noticed the opened box states the model is BND-AL10 (Chinese) but in the phone settings it's a BND-L21 (International). S/N and IMEI match.
Out of curiosity I tried Huawei Firmware Finder for Oreo. I used DNS method, picked the top one as seen here (verified): hxxp://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C432&firmware_page=0
It downloaded like 20 patches totalling around 8+GB and then asked to reboot...and failed.
My phone still works but I now get this during boot:
"your device has failed verification and may not work properly.
1) Press power key to continue.
2) Press volume up key up to 3 seconds to enter erecovery to restore your device.
3) your device will stop,start if there is not operation.
I tried Huawei eRecovery: 'Getting package info failed'
What should I do? Noob.
Brent.M said:
I recently got a 7x from ebay.co.uk. I noticed the opened box states the model is BND-AL10 (Chinese) but in the phone settings it's a BND-L21 (International). S/N and IMEI match.
Out of curiosity I tried Huawei Firmware Finder for Oreo. I used DNS method, picked the top one as seen here (verified): hxxp://pro-teammt.ru/firmware-database/?firmware_model=BND-L21C432&firmware_page=0
It downloaded like 20 patches totalling around 8+GB and then asked to reboot...and failed.
My phone still works but I now get this during boot:
"your device has failed verification and may not work properly.
1) Press power key to continue.
2) Press volume up key up to 3 seconds to enter erecovery to restore your device.
3) your device will stop,start if there is not operation.
I tried Huawei eRecovery: 'Getting package info failed'
What should I do? Noob.
Click to expand...
Click to collapse
erecovey fails for everybody. dont know why.
the message you see is normal if bootloader is unlocked. You should have had that same message first time you turned it on too.
Attempting to use firmware finder to apply updates , is not possible to unlock bootloader, so it had to have already been that way.
mrmazak said:
erecovey fails for everybody. dont know why.
the message you see is normal if bootloader is unlocked. You should have had that same message first time you turned it on too.
Attempting to use firmware finder to apply updates , is not possible to unlock bootloader, so it had to have already been that way.
Click to expand...
Click to collapse
Thanks for the reply. I definitely did not have this message before trying Firmware Finder. I have not done anything else to the phone.
Brent.M said:
Thanks for the reply. I definitely did not have this message before trying Firmware Finder. I have not done anything else to the phone.
Click to expand...
Click to collapse
This is known message resulting from of having boooader unlocked. Few people have been trying to make it not show , but no one has made it public if they have been successful at hiding it.
Now you got that phone (used, I assume ).From eBay. Perhaps the previous owner found some way. And attempting to update made his "hack" undo. Don't really know.
You can check if bootloader lock status to be sure if it is unlocked or not.
mrmazak said:
This is known message resulting from of having boooader unlocked. Few people have been trying to make it not show , but no one has made it public if they have been successful at hiding it.
Now you got that phone (used, I assume ).From eBay. Perhaps the previous owner found some way. And attempting to update made his "hack" undo. Don't really know.
You can check if bootloader lock status to be sure if it is unlocked or not.
Click to expand...
Click to collapse
In FASTBOOT&RESCUE MODE:
PHONE Unlocked
FRP Lock
This phone is sold as brand new boxed. However, like I said it was opened. I wasn't expecting to get a Chinese version that has been flashed. I should have just paid a bit more from Amazon. Though, I'm not fussed as long as I get updates and it's stable.
https://www.ebay.co.uk/itm/Huawei-H...var=541715986486&_trksid=p2057872.m2749.l2649
The 'your device has failed verification and may not work properly.' screen also says:
To learn more,visit:
http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Brent.M said:
In FASTBOOT&RESCUE MODE:
PHONE Unlocked
FRP Lock
This phone is sold as brand new boxed. However, like I said it was opened. I wasn't expecting to get a Chinese version that has been flashed. I should have just paid a bit more from Amazon. Though, I'm not fussed as long as I get updates and it's stable.
ebayDOTcoDOTuk/itm/Huawei-Honor-7X-5-93-Octa-Core-16-0MP-32-64-128g-Android-7-0-OTA-Smartphone/332608261102?ssPageName=STRK%3AMEBIDX%3AIT&var=541715986486&_trksid=p2057872.m2749.l2649
The 'your device has failed verification and may not work properly.' screen also says:
To learn more,visit:
http://zh.ui.vmail.com/emotiondownload.php?mod=restore
Click to expand...
Click to collapse
that status is very bad.
that combination of unlocked bootloader and locked frp is often hard if not impossible to get past.
unless you can access developer options menu and enable "enable oem unlock" menu option.
mrmazak said:
that status is very bad.
that combination of unlocked bootloader and locked frp is often hard if not impossible to get past.
unless you can access developer options menu and enable "enable oem unlock" menu option.
Click to expand...
Click to collapse
PHONE Unlocked
FRP Unlocked
I read that "Huawei is no longer offering bootloader unlock code in 60 days." I tried to request a unlock but I get just get
"If you have any questions about the unlock code application, please contact us."
Nothing happens. I contacted them.
Will I ever need that unlock code given that it is already unlocked? Should I return/refund the phone and buy from Amazon UK or am I wasting my time, since I'll likely be requesting a unlock code and possibly be playing with roms in a few years. I keep phones as long as possible and a basic user which is why I have little knowledge with them.
Brent.M said:
PHONE Unlocked
FRP Unlocked
I read that "Huawei is no longer offering bootloader unlock code in 60 days." I tried to request a unlock but I get just get
"If you have any questions about the unlock code application, please contact us."
Nothing happens. I contacted them.
Will I ever need that unlock code given that it is already unlocked? Should I return/refund the phone and buy from Amazon UK or am I wasting my time, since I'll likely be requesting a unlock code and possibly be playing with roms in a few years. I keep phones as long as possible and a basic user which is why I have little knowledge with them.
Click to expand...
Click to collapse
I would try and get a refund (if you bought via PayPal I think you may get some kind of support).
You can get the 7x from UK retailers for as low as £210. But the current Amazon price of £228 is not bad.
Do you browse HotUKDeals? Always check there before buying anything in the UK or from China.
Cracking deal for a China sourced redmi note 5 from tomorrow:
https://www.hotukdeals.com/deals/sa...900mah-aliexpress-xiaomi-online-store-2948784
Search for 7x deals.
Cheers
Sent from my BND-L21 using Tapatalk
sipart said:
I would try and get a refund (if you bought via PayPal I think you may get some kind of support).
You can get the 7x from UK retailers for as low as £210. But the current Amazon price of £228 is not bad.
Do you browse HotUKDeals? Always check there before buying anything in the UK or from China.
Cracking deal for a China sourced redmi note 5 from tomorrow:
https://www.hotukdeals.com/deals/sa...900mah-aliexpress-xiaomi-online-store-2948784
Search for 7x deals.
Cheers
Sent from my BND-L21 using Tapatalk
Click to expand...
Click to collapse
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Brent.M said:
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Click to expand...
Click to collapse
i think it is a little suspicious on the bootloader getting unlocked like that, but if its working , and you flashed full ota, then maybe give it a try.
¯\_(ツ)_/¯
¯\_('.')_/¯
`
mrmazak said:
i think it is a little suspicious on the bootloader getting unlocked like that, but if its working , and you flashed full ota, then maybe give it a try.
¯\_(ツ)_/¯
¯\_('.')_/¯
`
Click to expand...
Click to collapse
"Dear buyer,
Sorry for bring you any inconvenience and disappointment, the reason we have opened the package is because we need to download a multiplied language system to the phone before sent it out, they it can be use normal in this country. And for the model no, that's a normal phenomenon after rooting the phone.
Anyway, is it affect your use? what can us do for you now?"
Brent.M said:
Yes, PayPal. I contacted the seller on the matter. Will see what they say. After using Firmware Finder correctly I updated to 8.0 Oero. The message during boot also went away... I'll certainly check out hotdeals. But if the phone works should I bother?
Click to expand...
Click to collapse
Oh yes if you got it working no point. Enjoy the 7x
Sent from my BND-L21 using Tapatalk
Since the bootloader is unlocked I won't need to request a unlock code or ever need that code? As I did read Huawei is no longer offering bootloader soon.
Bootloader unlock and relock
deleted, posted on a new thread
Hi. I'm having an issue with this new phone. It's Wowi Ultra SQ766. On start up interface the 'Red State' notice comes up, goes off for 5 seconds and comes back on. The full message states:
'Red State
Your device has failed verification and may not work properly.
Please download boot image with correct signature or disable verified boot.
Your device will reboot in 5 seconds'.
Could you please help me out with a solution or fix for this.
I'd be happy if you would help.
Awaiting your reply.
Noob
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
SnowFuhrer said:
I assume you know that the OEM unlock toggle is in the developer settings? To enable developers settings, tap build number repeatedly until it says you are now a developer. You will need no fancy trick to show it as the lock that hides OEM unlock, only came out in oreo. I don't think carriers disable OEM unlock on Samsung's but I could be wrong. Lastly, if you get it figured out, go over here to the right thread and get it rooted. Good luck! https://forum.xda-developers.com/sa.../how-to-root-twpr-flash-a300fu-a300y-t3494362
Click to expand...
Click to collapse
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
-sofiann- said:
Thank you for the answer.
You assume right. I enabled developers settings first, saw that I didn't have OEM unlock option visible, then started to look about this issue. It is quick to see that in many case, even for phone not on OREO (I'm with Marshmallow 6.0.1), this OEM unlock is missing. But based on internet available data, it seems that in most of the case there is a trick to make it visible again. It is a sort of samsung security against thief that hide this option for seven days.
The trick didn't work for me and by looking more I saw that some people seems to be facing the same situation as mine. Some suggest that it is disabled by carrier.
But I couldn't find a solution anywhere for that context.
My question remains.
Here is a more detailed explanation :
from https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
""There are two kinds of phones in this world: Those that let you unlock your bootloader, and those that don’t.
Whether you’re allowed to unlock your bootloader depends on the manufacturer of your phone, the model you have, and even your carrier. Nexus phones are all unlockable by nature, and many phones from Motorola and HTC allow you to unlock your bootloader through a similar process as the Nexus.
Other phones, however–and some carriers–don’t allow you to unlock your bootloader the official way, which means you have to wait for developers to exploit a security vulnerability if you want to root and flash ROMs. If you have one of those phones, this guide will sadly not help you.
The best way to find out which category your phone falls into is to browse its section at XDA Developers. If you have an HTC or Motorola phone, you may be able too research its unlockability on HTC or Motorola’s website. If it doesn’t support unlocking, you’ll have to use an unofficial unlocking or rooting method, which you’ll usually find on the XDA Developers forums.""
Click to expand...
Click to collapse
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
-sofiann- said:
Hi everyone !
Hope I'm not making any double post but I couldn't find any explanation for this very specific situation.
After thorough research it, it seems that most of samsung devices has a secret setting called "OEM unlock" that we have to use to do the first step of rooting the device. In some cases that setting is missing but can be displayed again by some "date settings" tricks or waiting 7 days. In some other cases which seems to be mine, the "OEM unlock" setting is simply removed by probably the carrier of the phone and can't be reinstated.
In that last case which seems to be mine, I can't find any precise information wether we can or we simply can't unlock bootloader by other way and therefore root the phone.
Could anyone enlighten me ?
Thank you very much in advance !
Click to expand...
Click to collapse
The Galaxy A3 2015 (SM-A300FU) has no OEM unlock as A3 from 2015 don't even have FRP Lock, neither it has RMM state. That means there is no lock which prevents you to flash any custom binaries like TWRP recovery with Odin. You'll only lose access to knox apps/services (because of knox 0x1), rest remains the same.
SnowFuhrer said:
The trick didn't work for you because there is no security thing on marshmallow. What carrier are you on if you don't mind telling? Samsung's aren't bootloader unlocked like other phones.
Click to expand...
Click to collapse
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
-sofiann- said:
Hi !
About my device, here are details :
Samsung A300FU
Android 6.0.1
BASEBAND VERSION : A300FUXXU1CPH3
Build number : MMB29M.A300FUXXS1CQD5
Carrier was French company called Bouygues.
About bootloader lock or not, I can see on various website that many samsung are bootloader locked but can be unlocked easily by this OEM unlock option. Sometimes it is missing. Two reasons for that : Security check that is removed after 7 days or apparently permanently removed by carrier or geographic area control.
If i'm in that last case, is there any other solution to unlock the boatloader ?Or the phone is just unrootable. It seems strange to me that some phone are just unrootable.
Thanks again !
Click to expand...
Click to collapse
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
SnowFuhrer said:
If you read @prototype74 's post it explains it quite well. I think your bootloader is already unlocked if I read right.
Click to expand...
Click to collapse
Hi !
Thank you very much both of you for your help. Indeed there was no OEM unlock.
Many posts talking about OEM unlock existing on that A3 and the fact that I couldn't check if it was locked or not using the two methods advised (with adb or with a special code to dial up on the phone interface) led me to stop at that step to be sure before going on.
It is advises not to root a divise with a bootloader locked to avoid bricking it.
Anyway, trusting your input I did the whole process of rooting and putting a custom rom and it's all great !
I'm trying to get oem unlocking to show up in Developer Options but am not having any luck. It's a Samsung Galaxy Note 10 + running Android 10. It's the 256gb aura glow color if that matters. Anyways I've had it turned on for 170+ hours without rebooting it. Yet I still don't see any mention of oem unlocking in Developer Options. Did I miss a step? I see some people mentioning stuff to do with changing the time and stuff and I tried that in the past with no success. I just tried to check for software updates then went back to developer options and still don't see anything about oem unlocking. I have put the phone in airplane mode a few times so could that be it?
What is the criteria or whatever you need to do to get oem unlocking to show up?
It's not rooted and I currently have had it on for over 168 hours and tried checking for software update by going to settings>software update>download and install.
Help? Thank you
that1guyyep101 said:
I'm trying to get oem unlocking to show up in Developer Options but am not having any luck. It's a Samsung Galaxy Note 10 + running Android 10. It's the 256gb aura glow color if that matters. Anyways I've had it turned on for 170+ hours without rebooting it. Yet I still don't see any mention of oem unlocking in Developer Options. Did I miss a step? I see some people mentioning stuff to do with changing the time and stuff and I tried that in the past with no success. I just tried to check for software updates then went back to developer options and still don't see anything about oem unlocking. I have put the phone in airplane mode a few times so could that be it?
What is the criteria or whatever you need to do to get oem unlocking to show up?
It's not rooted and I currently have had it on for over 168 hours and tried checking for software update by going to settings>software update>download and install.
Help? Thank you
Click to expand...
Click to collapse
What is your model number? N975(?)
SM-N975U
Your not doing anything wrong and there is nothing you can do.
The SM-N975U and SM-N975U1 do not provide us with the ability to unlock our bootloader. This means we will not be given the OEM Unlock option.
But isn't unlocking bootloader part of rooting? Or is there a way around that? I mean I don't absolutely have to root it but I thought it would be cool to have the option. What's so different about this one that I can't be given the oem unlock option? Sorry if I sound irritated.. I am but not at anyone on here
Also I got this through us cellular. Maybe should have just bought it through Samsung? Model number would probably be different and would probably be able to get oem unlocking option
You should do a little more research. None of the US snapdragon Note10's are bootloader unlockable and hence, are not rootable. Doesn't matter where you purchased it. As far as I know, this is the case for all Samsung phones sold in the US and has been the case for quite a long time.
You can read more here.
that1guyyep101 said:
Also I got this through us cellular. Maybe should have just bought it through Samsung? Model number would probably be different and would probably be able to get oem unlocking option
Click to expand...
Click to collapse
No US versions of the Note 10+ can be OEM unlocked or rooted. Does not matter if you bought it from Samsung carrier unlocked or from a service provider. Carrier versions are SM-N975U and unlocked version is SM-N975U1. It has been a very long time since you could root a Samsung US device. I believe the S6 or S7 were the last rootable Galaxy phones in the US. The Note 8 could be rooted with an engineering kernel but it was more of a hack since you could not fully charge the phone.
Dear friends! I am writing for help. I received this device and ran into a problem. I can't get an OEM item in Developer Options.
I reset the phone to factory settings, then activated the developer mode. This item did not exist. Turned on wifi, checked for updates, rebooted the device. But this point did not appear.
I tried to change the date to earlier, a month, a couple of weeks, a year. It doesn't help. How can I get this item and what conditions must be met? I heard that you need to wait 7 days. Where does the time count come from? Can this be bypassed?
I can’t even install the official firmware through Odin, because it writes about the com port. I changed the device, and on the other device it says a read error. I need to install magic, so this item must be enabled for sure.
Help me please.
REDaHEAD said:
Dear friends! I am writing for help. I received this device and ran into a problem. I can't get an OEM item in Developer Options.
I reset the phone to factory settings, then activated the developer mode. This item did not exist. Turned on wifi, checked for updates, rebooted the device. But this point did not appear.
I tried to change the date to earlier, a month, a couple of weeks, a year. It doesn't help. How can I get this item and what conditions must be met? I heard that you need to wait 7 days. Where does the time count come from? Can this be bypassed?
I can’t even install the official firmware through Odin, because it writes about the com port. I changed the device, and on the other device it says a read error. I need to install magic, so this item must be enabled for sure.
Click to expand...
Click to collapse
Hi there I'm new on this forum but I have the same problem with my samsung s9 SM-G960U the oem unlock option is disabled and cuz the the device is either carrier locked or it have a snapdragon processor in both cases u can't unlock the bootloader cuz the carrier doesn't allow you to flash another firmware same thing with the USA model if your device has a Exynos processor then u can unlock the bootloader (oem unlock) if your device have a snapdragon processor then its a USA model and u can't unlock the bootloader
You can unlock bootloader now. I myself have G965U1, and I did it a few days ago and then installed custom Android 12 ROM.
It is paid service though, contact the author of this thread: https://forum.xda-developers.com/t/...unlock-for-samsung-us-canada-devices.4215101/