Database Develop

[Exynos] Questions concering OEM Unlock

-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT

SaadatM said:
-This is probably going to be confusing and a bit all over the place, bear with me.-
So, I bought my N8 back in November and directly went in to the dev options and saw OEM Unlock was available.
Now I didn't bother with it and now recently I've been thinking about rooting it, the catch is I've seen countless threads claiming a notorious "RMM"-lock taking place and putting devices in to "Jail".
Here's the sketchy bit:
- I rebooted and checked in DL-Mode and saw no particular line referencing RMM. Then after some reading got buildprop editor and checked what the "ro.security.vaultkeeper.feature" status was; It's 1.
- Rebooted again, double checked and no RMM entry.
- Enabled OEM Unlock and rebooted about 3-6 times (no flashing done) and it booted up fine with the OEM Unlock setting still enabled and present.
- DL Mode still does NOT show any RMM message or line, just "OEM lock" and "FRP lock" are off.
Am I missing some information as to how the "Jail" is triggered or does flashing only trigger the "Jail"?
BTW, here's info on my device:
- N950F, unlocked, Germany
- On latest January Patch, N950FXXU3BRA2
- Non-branded, but marked as DBT
Click to expand...
Click to collapse
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too

sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.

Weird.
sefrcoko said:
You unlock the toggle and flash twrp, etc., then when you boot back up you must ensure the i.e. unlock is toggled on (or else toggle it). Otherwise you'll end up in jail when you reboot again, since you flashed custom and didn't unlock OEM before the new reboot.
This question could have been asked in the oem unlock thread too
Click to expand...
Click to collapse
SaadatM said:
Alright, I'll check that and see if i'm also in the boat.
Odd enough that it toggles itself off automaticallly, that is wondering me.
Click to expand...
Click to collapse
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.

SaadatM said:
Yep, just as I suspected; Your idea didn't apply @sefrcoko .
I installed TWRP, Magisk, the no-dmverity (in that order) and booted perfectly fine with the following result:
- Dev options were hidden since DATA was formatted
- After opening Dev options the OEM Unlock was still switched on.
That has me thinking if it is either sw or hw related, that some devices lock-up.
Click to expand...
Click to collapse
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.

sefrcoko said:
You asked what jail was, and I explained it... You're just not in jail. Not every device is affected, and fixes to prevent the issue are being baked into custom roms and .zips now too. Lots of factors at play, hence the monster OEM Unlock thread . RMM seems to be the culprit.
Click to expand...
Click to collapse
Figured not every device is effected.
Appreciate the input though.

Need Help Missing OEM unlock in developer Option

Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks

cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
Maybe try this and see if it works for you
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984

I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply

cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
If the workaround to bring back the oem unlock toggle isn't working, then you will have to wait the 7 days for it to appear. Then you can toggle it and try installing twrp again. You likely missed a step in the process last time which resulted in 'jail'.

cheemak said:
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
Click to expand...
Click to collapse
You could try my method here - https://forum.xda-developers.com/showpost.php?p=76962872&postcount=28

I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??

indercheema14 said:
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
Click to expand...
Click to collapse
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.

sefrcoko said:
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
Click to expand...
Click to collapse
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?

cheemak said:
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
Click to expand...
Click to collapse
I'm not sure but I think that installing the update could restart the 7-day wait period. If you want to root as fast as possible then it's probably safer to not install the update for now and just wait for the OEM Unlock toggle to appear. There is also a stick thread here with a workaround to skip the 7 day waiting period, but it didn't seem to work for everyone (although it did work for me the one time I tried it).

Any luck///need help too.
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!

dandel0074 said:
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
Click to expand...
Click to collapse
What model do you have? What's your csc?

sefrcoko said:
What model do you have? What's your csc?
Click to expand...
Click to collapse
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.

dandel0074 said:
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
Click to expand...
Click to collapse
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.

sefrcoko said:
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
Click to expand...
Click to collapse
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.

dandel0074 said:
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
Click to expand...
Click to collapse
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point

sefrcoko said:
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
Click to expand...
Click to collapse
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.

dandel0074 said:
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
Click to expand...
Click to collapse
Like I said you won't get it on the T-Mobile model (and iirc it's not needed for samfail, even if you are on the proper bootloader, etc.), but you can always check the 9600 and/or OEM unlock threads for more on that one if the stock flash/wipe and waiting period approach isn't preferred or doesn't work out.

Bootloader Unlock (Developer Option Bug)

Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.

Hey there! been lurking xda for ages but your post just made me register! Thanks a lot for sharing mate.
I just downloaded the update and tried this method, worked fine. Btw there's a new security patch as latest update (5/19), didnt bother doing it as they could have patched it probably.
So, i tried flashing twrp and noticed it still wouldn't let me and flashing get_unlock_ability returns 0. Did you manage to get past this?

This actually works. Havent flashed anything yet, as I'm scared of bricking it.
I just love the good old days when I had the Tmobile G2x with the Nvidia chip, flashed the darn thing so many times, even bricked it numerous times, but I was able to go into recovery and reflash it again. That phone was "Flash and Brick Proof"

thanks for sharing, spent countless hours trying to fix with usb driver setups and cmd lines from other tutorials.
question is what's next?

That's a dummy command,
You still need to properly Unlock it, I'm afraid all the options are paid service
Sent from my Xperia 1 using XDA Labs

This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?

alexben_007 said:
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
Click to expand...
Click to collapse
Try fastboot oem unlock

Mod edit - translated by https://www.deepl.com/translator:
Unlock the bootloader
****************************
Разблокировать загрузчик -358536084114397 -nokia5_nd1

I am N.E.E.T said:
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Click to expand...
Click to collapse
pretty usefull tip bro, it worked on my nokia 6 TA-1000

Google Pay not working - Phone not rooted

Hey,
I purchased a Samsung Note 8 (SM-N950F) a couple of years from Amazon.de. The phone was unlocked, since then new OS releases were really slow so I decided to download the Pie update from Sammobile and updated my phone via Odin. The phone is using official firmware and has never been rooted yet when I try to activate Google Pay I receive the following error; "Couldn't finish setup to pay in shop. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I spoke to Samsung and told me to check a few things and they confirmed the phone is not rooted, I spoke to Google and they told me I should ask Samsung how to unlock the bootloader but Samsung said doing this would void my warranty. I'm a bit confused as to what to do, is there a stock pie rom I can use without voiding my warranty?
Thanks a lot, appreciate any help
Regards
p4rma

The only thig i can think of is that, the phone you've got has a CSC code of a region where Google Pay is not supported, or maybe you are living in a country that do not support Google Pay.
If you think I'm wrong, flash stock pie firmware.
Flashing stock offiicial binaries doesn't need your bootloader to be unlocked.

Thanks for the quick reply I will try this. Would Samsung have their own stock pie rom? Kinda wish I just waited for the pie update rather than flashing. Its annoying I can't use Netflix either as it says my device is not compatible.
I just checked and my bootloader is N950FXXU7DSJ1

Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.

Unix_Dominator said:
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Click to expand...
Click to collapse
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix

p4rma said:
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
Click to expand...
Click to collapse
I'm glad it worked out for you too!!!

Unix_Dominator said:
I'm glad it worked out for you too!!!
Click to expand...
Click to collapse
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks

p4rma said:
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
Click to expand...
Click to collapse
It has been permanently fixed for me, I never faced any issue with GPay after that method (I don't use Netflix though). Could you also see if you phone is updated to the latest version, if so also check if your phone has a fix for Stagefright.
To check if you are vulnerable to that exploit download this app it will tell you Click Here . If it fails, try OEM unlock as off and see, might fix it.
I really hope this issue doesn't come back for you.

Question S21 Ultra SM-G998B

Dear Friend,
I am having issue with S21 Ultra which i purchase just 2 months ago.
I decide to make my device root able , then i have notice that there is no OEM Lock option (Missing) in developer mode.
After searching XDA forum and Google all the setups mention there i have tried to visible OEM Unlocker option but OEM lock option never visible. Even flash stock rom again and again and wait for 168H but still its not visible.
When i go in download mode and try to flash TWRP or any custom rom it show below mention msg.
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"
Can any one guide me what is the issue, i had purchase this product with Full payment then why it is behaving so strange.

google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
EDIT: sorry if you cant see these option list, there could be something different in your case.

Very srtange situation. I have exact same model.

vlubosh said:
google is best friend please add him to your friend list
reboot to download mode(connected phone to pc, reboot and hold vol+ and vol-) and read first screen options:
View attachment 5580147
EDIT: sorry if you cant see these option list, there could be something different in your case.
Click to expand...
Click to collapse
Thanks brother for your prompt response , i tried this but issue remain same

Samaly01 said:
Thanks brother for your prompt response , i tried this but issue remain same
Click to expand...
Click to collapse
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.

vlubosh said:
Can you boot the phone? Try fastboot oem device-info to check what state od BL is.
Click to expand...
Click to collapse
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....

Samaly01 said:
Phone is booting ...no issue in that ....Fastboot not working in s21 Ultra g998b....
Click to expand...
Click to collapse
Allow usb debugging in dev.settings

vlubosh said:
Allow usb debugging in dev.settings
Click to expand...
Click to collapse
USB debuggin already allowed ....ADB command work but not fastboot

Samaly01 said:
USB debuggin already allowed ....ADB command work but not fastboot
Click to expand...
Click to collapse
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?

Macusercom said:
I think you need to have a SIM card in there and to have internet access to see the OEM unlock toggle. Do both of these things apply to you?
Click to expand...
Click to collapse
SIM Card is installed both WIFI and Data is working but issue remain same.

Samaly01 said:
SIM Card is installed both WIFI and Data is working but issue remain same.
Click to expand...
Click to collapse
Try disabling the automatic date and time and set the date to a day at least one week from now

I have observe a very strange thing, when ever I reboot the device and visit develope option Oem Locker appear then again revisit to developer option it disappear again. Only rebooting device option bring oem option just for few minutes.

so then, when you see unlock option reboot right to DL mode and look if you see device unlock

vlubosh said:
so then, when you see unlock option reboot right to DL mode and look if you see device unlock
Click to expand...
Click to collapse
Still same issue
"Cause
No sign info: (Recovery)
Custom Binary (Recovery) due to remaining installment balance"

Someone suggested to use Samsung combination file, after searching on google there are only 3 Combination files available U1, U2, U3.
Latest file available is COMBINATION_FAC_FAR0_G998BXXU3AUD3
( I think this not usable on Android 12 version (U4)
Please suggest what option i have left to resolve above mention issue.

Could you try to flash latest Stock rom(Via odin) and try again?

Latest Firmware (SM-G998B_BTU_G998BXXU4CVC4) Flash via Odin...Result same

Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com

vlubosh said:
Found this, maybe your case
Custom binary blocked due to remaining installment balance galaxy
Hi, I recieved my S21 Ultra yesterday and sucessfully rooted it using the guide/youtube tutorial. Today, I restarted the device and upon restarting it would go into a bootloop with a small message on top saying: 'Custom binary blocked due to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks Brother, but issue is same mine.... no solution

checke my stats in DL mode:
KG state checking
FRP lock off
OEM lock OFF(u)
Warranty void 1
HDM status none
I think you problem is in KG state.
Maybe try to change date as in this tutorial: