Database Develop

OEM Unlock is on... but returns as "disabled"

I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!

Just to clarify, are you actually attemping to unlock it? You have to first enable that option in developer settings, but you still have to put the phone in bootloader mode and run the command "fastboot oem unlock", then use the buttons on the phone to confirm it. I think all your data wipes first time you unlock your bootloader too so just be careful.

SilverSix said:
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Click to expand...
Click to collapse
Depending the Android build installed, sometimes the option has been greyed out. Don't know why...
You said you tried to get the "OEM unlock" slider working... But did you try issuing the unlock command in bootloader?
Good luck...

Yeah, I'm aware it wipes your device. Also, don't burn me but I was using a Toolkit to start the process but I just gave up and did it the old fashioned way. After restarting into bootloader and sending the fastboot command it prompted the question to unlock it, so everything went smoothly.
Somewhere I had read that Android purposely locks OEM unlocking after n reboots, and I thought I was completely out of luck, but everything went smoothly. Thanks for your time!

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

OEM UNLOCK OFF and/or RMM STATE PRENORMAL fix

Hi,
so I'm using some Samsung Galaxy S9 to measure GSM networks (like 50 pcs). Out of box; some S9 don't have OEM UNLOCK option (or the option is OFF and grayed out) and some have RMM STATE PRENORMAL, both options make use of the phones impossible (I use custom boot and fw). I made like one week research on this topic; found only some "standard" information mess and few guides. Just want to share how I fixed my problem.
Always try on fresh FW or after wipe (...fresh FW is preffered...).
1. If You have a phone that have OEM UNLOCK option not visible or grayed out, at first try to connect to network (WiFi / GSM) in most cases OEM UNLOCK option appears after few seconds, and in some cases phone restart is required. This helped me in few cases.
2. If first step didn't help then try to do date changing trick, there are some guides, but in short:
- make sure that GSM / WiFi networks are OFF, in [General management] > [Date and time], turn OFF [Automatic date and time] and change date back more than 7 days (ieg. 2 weeks or one month)
- turn on network (GSM / WiFi), make sure that the date didn't update after network ON (if it did, just repeat), go to [Software update] and click [Download updates manually], at update screen choose [LATER], after this under [Download updates manually] there shoudl be "Last checked on 99/99/9999" and shoudl display date You have set
if after this the date is actual not that which You choose, then wipe the phone and try again, if after few tryes there is no result, then this trick won't work on this phone
- restart phone and turn ON [Automatic date and time] , and then click [Download updates manually] and also choose [LATER], "Last checked on 99/99/9999" shoudl be actual date,
now restart the phone and check if OEM UNLOCK option appeared...
This trick/method worked only on 1 of my phones, so for S9 it's bad... it worked better on S8.
3. This is rather as bonus, it's useless for me, but maybe helps someone. Sometimes, doing firmware update via OTA ([Software update] > [Download updates manually]) OEM UNLOCK appears after update is is done. So, flash phone with older FW, an then do OTA update. This one did the trick few times.
As for RMM STATE PRENORMAL, method 1, 2 and 3 helps... but NOT always... it's a real pain... so...
4. This method helps with OEM UNLOCK OFF and RMM STATE PRENORMAL states (afterwards OEM UNLOCK is ON, and RMM STATE is NORMAL). Success rate was 100% in my case (3 out of 3 phones, other methods failed badly). One thing is weird, I'v found only 1 mention of this one... well, spoiler alert, it's paid, but gets the job done.
Just go to chimeratool.com, get paid trial version... than just few clicks and one minute later... viola! All done and working... real shock for me... afer week of research...
(I'm not paid and/or related to Chimera tool, just want to help others)
Hope it helps and clarifies some things!
Regards, Doman.
PS: as for SAMSUNG... shame on You for this stiupid lock...!

About RMM State : Prenormal... ChimeraTool did not worked in my case
G960F/DS

flyingcascade said:
About RMM State : Prenormal... ChimeraTool did not worked in my case
G960F/DS
Click to expand...
Click to collapse
Have You tried doing KG state fix first with Chimera and then RMM? There are two methods to unlock RMM, first just use RMM unlock, second first run KG unlock (even if You don't have problem with it) and then run RMM unlock. Also You can try contacting with guys from Chimera.

Doman2011 said:
Have You tried doing KG state fix first with Chimera and then RMM? There are two methods to unlock RMM, first just use RMM unlock, second first run KG unlock (even if You don't have problem with it) and then run RMM unlock. Also You can try contacting with guys from Chimera.
Click to expand...
Click to collapse
I have tried two methods. In both cases Chimera says something like "this phone doesn't support this type of unlocking". I think June 2019 firmware is too new for it. Tommorow will mark 168 hours while the phone is turned on. I'll give feedback when I reboot in download mode and if RMM State : Prenormal is still there.
EDIT: After 170 hours and reboot in download mode the state is still "Prenormal". I lost all hope...

flyingcascade said:
EDIT: After 170 hours and reboot in download mode the state is still "Prenormal". I lost all hope...
Click to expand...
Click to collapse
Contact Chimera guys; I'm sure that they'll work on it - if it is a new FW case.
Or... flash device with older FW and then try again.

I have never had the problem with oem. Its just my rmm state is prenormal, I tried the steps on that thread, to see if mabye the steps for oem can help. But the my rmm is still prenormal. All the steps to fixing rmm that i have found all involve twrp, And i dont have twrp due to my rmm state being prenormal. If you could help me futher that would be great thank you..

RMM STATUS is always Prenormal. KG STATUS is Checking. Why?

i flash russia firmware, somehow OEM is appear, i switch it off and on. Then i go to change language, again somehow OEM is missing, reboot to bootloader still RMM prenormal
I can root it with old firmware (no KG or RMM in download mode) but its older than latest firmware 2 years

what about KG prenormal with oem lock on.no oem unlocking option.tried all the methods.non of them has worked.suffering from this [email protected](ijg lock

HirukaNethmitha said:
what about KG prenormal with oem lock on.no oem unlocking option.tried all the methods.non of them has worked.suffering from this [email protected](ijg lock
Click to expand...
Click to collapse
Other than what I had put together, How To Guide , which is purely based on other people's work and trial-n-error, I am not sure how I can be of much help here. There are plenty of reports of this happening with devices that are purchased directly through Samsung (with financing or with trade-in !!!).
This is likely illegal by Samsung, as this block should resolve itself automatically on completion of payment / trade-in but it clearly doesn't. Someone would have to sue them to get this sorted.. You can try to contact their team, financing / trade-in, and VERY nicely request this to be unblocked. Other than that, google for random removal of prenormal state. Other than trying reflashing from scratch, not sure what else I would do. I literally just made sure to buy my device through a 3rd party vendor and categorially avoided the issue..

Two different Bootloader Lock Status !

Today i flashed 11.0.5.0 china rom using (flash_all.bat) adb platform tool method. after flashing the rom, i flashed TWRP, Magisk and everything is working fine. But when i opened ADB Fastboot Tools to debloat the rom(without fastboot mode) it was showing the device is locked. but when i turned my device into fastboot mod and again opened ADB fastboot tools, it shows the device is unlocked. i also checked in the developer options and it says the device is locked. now should i unlock the phone again using MI Flash tool? please let me know why the problem is happening and what is the solution to the problem. All the pictures are attached.
Thanks

Normal.
You've got Magisk installed. It tries to hide root.
I'm guessing when you boot it shows "unlocked"? That's now the most reliable indicator if you've got with Magisk installed. Mine's the same.

droident said:
Normal.
You've got Magisk installed. It tries to hide root.
I'm guessing when you boot it shows "unlocked"? That's now the most reliable indicator if you've got with Magisk installed. Mine's the same.
Click to expand...
Click to collapse
If it's about magisk then it's fine. But I also checked "Mi Unlock Status" in the developer options and it says the device is locked. Is it locked now?

zahidhasanzahid said:
If it's about magisk then it's fine. But I also checked "Mi Unlock Status" in the developer options and it says the device is locked. Is it locked now?
Click to expand...
Click to collapse
It's unlocked; I have an identical status on the "Mi Unlock Status" page with the 'add account option' - if I recall correctly I first noticed the bizarre faux-locked state on Xiaomi ADB Fastboot Tools myself too and went to verify at that precise Settings page. I was pretty much scratching my head given I'd done a few things that you just can't do on a locked bootloader. Then I asked about it here. Turns out it's just part of Magisk evading detection (to varying degrees of success - I still get the occasional app smart enough to figure out there's root at work).

droident said:
It's unlocked; I have an identical status on the "Mi Unlock Status" page with the 'add account option' - if I recall correctly I first noticed the bizarre faux-locked state on Xiaomi ADB Fastboot Tools myself too and went to verify at that precise Settings page. I was pretty much scratching my head given I'd done a few things that you just can't do on a locked bootloader. Then I asked about it here. Turns out it's just part of Magisk evading detection (to varying degrees of success - I still get the occasional app smart enough to figure out there's root at work).
Click to expand...
Click to collapse
Thanks man :good:

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: