Database Develop

OEM Toggle is shown but can't be toggled; phone unable to go into download mode.

Hello XDA, I hope that you could help me troubleshoot my Note 8 (N950F).
So it's been 7 days and oem unlock toggle has finally appeared.. The only issue is it is greyed out and unselectable.
When I got this device I wasn't able to see developer options by pressing build number (though I got the notification that it was enabled), I was only able to access the setting by downloading an app short cut for it via the play store and on initial launch it said developer options are disabled. But then second launch it worked. Idk if this is significant but maybe the country this is meant for disabled it? Regardless of the sim card being in/out the phone, it is still greyed out. Also, I was able to factory reset the phone through the settings after downloading an OTA (I did this in hopes of developer options being enabled about a week ago.)
I tried to boot into download mode but it seems I can't boot into it (following the steps only lead to a normal reboot, and when I select that option from the stock recovery or through adb, it only boots the phone up normally. I purchased the phone off of swappa, in brand new/like new condition. Any ideas? Thank you for your help.
Edit: added screenshots.

SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.

Eddygraphic said:
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Click to expand...
Click to collapse
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware

Negroid said:
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Click to expand...
Click to collapse
That's weird I've never seen a Galaxy that can't enter download mode.

Eddygraphic said:
That's weird I've never seen a Galaxy that can't enter download mode.
Click to expand...
Click to collapse
Exactly. That's why I'm so concerned.

Have you logout your Samsung Account and Google account？sorry for my poor English.:crying:

Do you use any of the KNOX stuff? Did you do any factory reset?

Can you "clear data" on "settings" app? this would make the "developer option" menu hidden again. Then re-show it by tapping build number numerous time again. Hoping that OEM is now editable.

Hi, could you solve this problem? My Note 8 has the same problem and I have not found any solution :llorando:.
I would appreciate it if you can help me.

[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.

N950F bootloader issue

For mentioned model i do not get any type of Bootloader interface detected as hardware in device menager. Which also means i can not access it from adb in order to unlock bootloader. I have found some talk about switching into Unlock mode from Odin mode but can not find a way to do it. This also happens while i did USB debbiging and OEM unlock set on. I have latest Pie on it if that makes any difference.
I hope anyone has some advice on how to solve this and that you in advance

scudteshka said:
For mentioned model i do not get any type of Bootloader interface detected as hardware in device menager. Which also means i can not access it from adb in order to unlock bootloader. I have found some talk about switching into Unlock mode from Odin mode but can not find a way to do it. This also happens while i did USB debbiging and OEM unlock set on. I have latest Pie on it if that makes any difference.
I hope anyone has some advice on how to solve this and that you in advance
Click to expand...
Click to collapse
Go into developer options and toggle OEM unlock on. That's all that is required on Samsung's.

SnowFuhrer said:
Go into developer options and toggle OEM unlock on. That's all that is required on Samsung's.
Click to expand...
Click to collapse
Oh ok but still it wont let me flash twrp even thru odin. This seems far to complicated comming from xiaomi.

scudteshka said:
Oh ok but still it wont let me flash twrp even thru odin. This seems far to complicated comming from xiaomi.
Click to expand...
Click to collapse
That's probably because of some recent locks Samsung has made. It used to be easier with Samsung . But anyway, look here for more details. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

SnowFuhrer said:
That's probably because of some recent locks Samsung has made. It used to be easier with Samsung . But anyway, look here for more details. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Dude you are a major help and thank you very much ?

General What not to do with China ROM

I recently got the phone and i have the China version 12/256. Here are few things to take care:
1) Install Google Keyboard first before debloating system apps using adb.
2) Very Important: First update the phone to latest firmware (12.0.13) before you toggle the OEM Unlocking option in developer settings. If you dont update first and have the option toggled and try to install an OTA update the phone will just bootloop unless you clear the data and sign in with mi account again. This will reset the 168 hours time in the software. So always update the phone to latest update.
3) If you are using google pay, go to nfc settings and change the wallet from Mi Wallet to HCE Wallet.
4) The stock TPU cover is loose on the sides. I dont know if its just mine. But better buy another case from aliexpress.
5) DO NOT install global stock rom through fastboot or mi flash tool. It just wont work because of the different versions(regional) of phone. Only install xiaomi.eu ROM using the guide from a post on xda because the install script knows which version your phone is and installs the appropriate system files.

@ingbrzy can you confirm that? :
5) DO NOT install global stock rom through fastboot or mi flash tool. It just wont work because of the different versions(regional) of phone. Only install xiaomi.eu ROM using the guide from a post on xda because the install script knows which version your phone is and installs the appropriate system files.
Click to expand...
Click to collapse
xiaomi.eu is safe to install using fastboot method ?

veimus said:
@ingbrzy can you confirm that? :
xiaomi.eu is safe to install using fastboot method ?
Click to expand...
Click to collapse
It is safe to install. haven't installed it yet but read on forums that it is working.

so I guess
1) unbox your phone
2)update to latest software via settings.
3)factory reset device after that.
3)request bootloader unlock.
4) after 7 days, unlock your bootloader and tooggle that OEM unlock
5)follow instructions on xiaomiEU rom.
is that safe enough? Lmao
PS:
6) Find EDL support near you

avetny said:
so I guess
1) unbox your phone
2)update to latest software via settings.
3)factory reset device after that.
3)request bootloader unlock.
4) after 7 days, unlock your bootloader and tooggle that OEM unlock
5)follow instructions on xiaomiEU rom.
is that safe enough? Lmao
PS:
6) Find EDL support near you
Click to expand...
Click to collapse
1) Update to 12.0.13
2) Sign in to MI Account on device if haven't done yet.
3) Enable Developer settings, Developer Settings> Toggle OEM Unlocking
4) Turn off Wifi, Turn on Mobile Data, Settings> Additional Setting>Developer Settings> Mi Unlock Status> Click Add Account and Device.
5) Download Mi Unlock Tool, Login to same mi account > Turn off device, Hold Volume Down and Power Button ( you will see fastboot screen)> connect the device using USB, You will see the device, Click on Unlock button.
6) It will show wait for 168 hours to unlock.
7)Do not sign out/ change mi account on device or toggle the OEM Unlocking option. If you do you have to start from the beginning.
If you dont see your device in Mi Unlock tool install adb and fastboot drivers.

saisannihith said:
1) Update to 12.0.13
2) Sign in to MI Account on device if haven't done yet.
3) Enable Developer settings, Developer Settings> Toggle OEM Unlocking
4) Turn off Wifi, Turn on Mobile Data, Settings> Additional Setting>Developer Settings> Mi Unlock Status> Click Add Account and Device.
5) Download Mi Unlock Tool, Login to same mi account > Turn off device, Hold Volume Down and Power Button ( you will see fastboot screen)> connect the device using USB, You will see the device, Click on Unlock button.
6) It will show wait for 168 hours to unlock.
7)Do not sign out/ change mi account on device or toggle the OEM Unlocking option. If you do you have to start from the beginning.
If you dont see your device in Mi Unlock tool install adb and fastboot drivers.
Click to expand...
Click to collapse
7) Do not sign out/ change mi account on device or toggle the OEM Unlocking option. (You mean do not switch off anymore?)
Thank you

avetny said:
7) Do not sign out/ change mi account on device or toggle the OEM Unlocking option. (You mean do not switch off anymore?)
Thank you
Click to expand...
Click to collapse
yes. dont toggle it back to off.

saisannihith said:
yes. dont toggle it back to off.
Click to expand...
Click to collapse
Got it !!!
fantastic guide! Thank you !!!

I have flashed mine , it looks fine
Need some more time to evaluate performance
First boot takes awhile , don't panic or remove the cable!

speedtripler said:
I have flashed mine , it looks fine
Need some more time to evaluate performance
First boot takes awhile , don't panic or remove the cable!
Click to expand...
Click to collapse
Which method you follow?? The method from OP?
Post your installation from the beginning please.
With specifications of your phone.

speedtripler said:
First boot takes awhile.
Click to expand...
Click to collapse
My friend doesn’t matter how long it takes to boot up.....as long as you not in fastboot after restart

It seems to be working fine but I need to go outside and test the 5G and 4G signals are still as good as before
It's definitely feels much lighter and smoother
WhatsApp notifications are working properly
There's much less apps in the drawer, Chinese was very bloated , now there's not a Chinese app or character to be found!
Also banking apps are working fine!

speedtripler said:
It seems to be working fine but I need to go outside and test the 5G and 4G signals are still as good as before
It's definitely feels much lighter and smoother
WhatsApp notifications are working properly
There's much less apps in the drawer, Chinese was very bloated , now there's not a Chinese app or character to be found!
Also banking apps are working fine!
Click to expand...
Click to collapse
Please post the instruction how u did it. With full info

Just downloaded and install it from a Windows laptop
You have to wait 168 hours to unlock it and then open the phone in Chinese language to get to the developer options again before you flash , you need to enable usb debugging again!!!
You will need wi-fi to get back in because there's a security check after unlock, it maybe in Chinese but you will figure it out
I had never used a Xiaomi phone before this one , there are literally no downsides anymore....
I'll update if I can find something that doesn't work

speedtripler said:
Just downloaded and install it from a Windows laptop
You have to wait 168 hours to unlock it and then open the phone in Chinese language to get to the developer options again before you flash , you need to enable usb debugging again!!!
You will need wi-fi to get back in because there's a security check after unlock, it maybe in Chinese but you will figure it out
I had never used a Xiaomi phone before this one , there are literally no downsides anymore....
I'll update if I can find something that doesn't work
Click to expand...
Click to collapse
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?

jmikepr said:
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Click to expand...
Click to collapse
EDL guy:
Do it

deleted

jmikepr said:
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?
Click to expand...
Click to collapse
Because my phone went into bootloop. I updated to 12.0.10 and then toggled the OEM Unlocking. While i was waiting for 168 hours, i got 12.0.13 OTA update and i tried installing it. Phone restarted 3-4 times and took me to recovery. I then wiped data and it started again with a factory reset. So iam just warning people to get the latest update before doing this. Also, i do own a POCO F2 Pro and i am quite experienced with flashing ROMS. Developers always ask you to update to latest firmware before flashing as the new ROMs are based on latest firmware.
Xiaomi.eu is not a custom AOSP ROM but just a word of caution.

Sounds like after OTA 12.0.13 phone should be a factory reset it

jmikepr said:
Can you explain the technical reason and the source of the information when you claim that you must update to 12.0.13 before toggling OEM unlock.
I started my unlock last week and I have 12 hours left. 12.0.13 was not out last week. So, obviously I toggled it before that.
Can you explain why 12.0.13 specifically is required before toggling OEM unlock?
Click to expand...
Click to collapse
The toggle is nonsense
I toggled mine on and off a few times yesterday waiting for update 12.0.13 when I was on 12.0.10
It still unlocked like a charm today