Database Info

Oem unlock questions

http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
This article is pretty much straight forward but i wasnt sure on it cause ive never had a phone with oem unlock in developer settings. From what it says oem unlock is required to be turned on anytime you do any kind of modification or flashing a stock tar.... so it has to be on basicially permentantly correct just to be on the safe side if your doing modifications or have modifications already on your phone?

haro25 said:
http://techbeasts.com/how-enable-oem-unlock-android-lollipop-marshmallow/
This article is pretty much straight forward but i wasnt sure on it cause ive never had a phone with oem unlock in developer settings. From what it says oem unlock is required to be turned on anytime you do any kind of modification or flashing a stock tar.... so it has to be on basicially permentantly correct just to be on the safe side if your doing modifications or have modifications already on your phone?
Click to expand...
Click to collapse
Everytime I've used OEM unlock was for a device that supports fastboot to unlock the bootloader. Now, Samsung doesn't do fastboot but it seems that you must click OEM unlock to flash (thru Odin) a custom recovery such as twrp.
-sent from this device using this app.

This what someone said online cant be 100 % sure if its accurate..
Quoted text.....
Sadly it backed fires the users who accidentally got themselves boot-looped and forgot to unlock oem.
Like me... Oem locked, and all are stocks no cwm/twrp... All i can do is bring this to the service center. :/
Mistake for me, error for google.

Question Does anyone know how to root this phone?

I tried this method but it doesn't work?
How to Root Samsung Galaxy A32 – Step-by-Step Guide!
Today in this article, I have come up with a detailed Step-by-step guide on how to Root Samsung Galaxy A32. So Hello, guys how are you? I hope you are
www.guidetoroot.com
This step doesn't work, there is not OEM Unlock option?
Now you have to open the settings again, and enable OEM unlock and USB debugging .To do this (Go to Settings → Developer Options and enable the ”OEM Unlock”
Click to expand...
Click to collapse

Samsh*t removed it

mingkee said:
Samsh*t removed it
Click to expand...
Click to collapse
that's bollocks! so is there no way to root this?

Neo3D said:
that's bollocks! so is there no way to root this?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/t/root-samsung-galaxy-a52-sm-a525f-magisk-root.4251283/ it may be work for A32 by patching boot.img

redymedan said:
Try this https://forum.xda-developers.com/t/root-samsung-galaxy-a52-sm-a525f-magisk-root.4251283/ it may be work for A32 by patching boot.img
Click to expand...
Click to collapse
Bootloader unlock required
The problem is this phone "OEM Unlock" option is removed by Samsh*t
Bootloader unlock cannot be done without OEM Unlock enabled

mingkee said:
Bootloader unlock required
The problem is this phone "OEM Unlock" option is removed by Samsh*t
Bootloader unlock cannot be done without OEM Unlock enabled
Click to expand...
Click to collapse
So, there's absolutely no way to unlock a bootloader if Tmobile requests them to be locked? Can I call Tmobile and ask them to unlock it?

Neo3D said:
So, there's absolutely no way to unlock a bootloader if Tmobile requests them to be locked? Can I call Tmobile and ask them to unlock it?
Click to expand...
Click to collapse
there are paid for services run by people, some of them use this site, where your phones bootloader can be unlocked either remotely or via a one use only token and instructions. not sure about A32 but on Galaxy S series phones it costs about 75 dollars US. search here you should find something, a link to a Telegram group probably.

3mel said:
there are paid for services run by people, some of them use this site, where your phones bootloader can be unlocked either remotely or via a one use only token and instructions. not sure about A32 but on Galaxy S series phones it costs about 75 dollars US. search here you should find something, a link to a Telegram group probably.
Click to expand...
Click to collapse
How are they able to bypass Samsung's lock? I don't think paying is worth it to get unlocked, esp over the internet where it could be a scam.

have no idea

Neo3D said:
How are they able to bypass Samsung's lock? I don't think paying is worth it to get unlocked, esp over the internet where it could be a scam.
Click to expand...
Click to collapse
you can join a telegram group full of people either waiting for or already had their bootloaders unlocked. it is quite pricey but it's not a scam (based on the people I've seen doing it) a moderator here used to do it and people have posted about being happy with the service they got.
if it not via that route there currently isn't any other way to unlock bootloaders for US Samsung phones

Be aware when you update ROM after that.
Later version ROM can lock bootloader again and current token may not unlock again

If anyone gets an unlocked stock rom or a bootloader.img even please post it here, for example I've heard some people have been getting unlocked with T-Mobile. Follow the instructions on how to dump the unlocked bootloader.img here:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
I've tried extracted boot.img's from my stock rom run through magisk like 4 times.. nothing is working even with download mode and odin.

Neo3D said:
How are they able to bypass Samsung's lock? I don't think paying is worth it to get unlocked, esp over the internet where it could be a scam.
Click to expand...
Click to collapse
I heard Sampwnd is pretty good

SM-A326U Combination Firmware
US Combination Firmware link for Galaxy A32 5G Supposedly you can FRP bypass or OEM unlock based on what I've heard https://drive.google.com/u/0/uc?export=download&confirm=syaM&id=1b8Umj0tNQ_YY-u9EpPfoH0z_vsZDNSv3
forum.xda-developers.com
Follow this post for unconfirmed claim of unlocking the bootloader. Please post back if this software allows one to unlock the bootloader.
TIA,
F

TypicalGellert said:
I heard Sampwnd is pretty good
Click to expand...
Click to collapse
weird that they don't list prices... seems like a red flag

Neo3D said:
weird that they don't list prices... seems like a red flag
Click to expand...
Click to collapse
I just checked Sampwnd and this phone isn't available yet, but the price is after you select the purchase link and select their list of devices

Yes. I've used these instructions https://www.naldotech.com/root-samsung-galaxy-a32-magisk/
I've used boot.img to patch, and then flashed with odin, worked as a charm.
Turn on Odin mode - by shutdding down your phone, then holding Volume Up + Down, then long hold Volume Up to unlock bootloader, You might need to reboot afterwards, also factory reset is(will be) a must.
Just shut down after that, redo holding Volume Up + Down, then long hold Volume Up, I cannot remember exactly, but I think after that it was once pressing Volume Down to have proper odin download mode to use patched image.
Select patched magisk image patched from/by boot/recovery.img.lz4 archive.
I've UK A326B

NetBos said:
Yes. I've used these instructions https://www.naldotech.com/root-samsung-galaxy-a32-magisk/
I've used boot.img to patch, and then flashed with odin, worked as a charm.
Turn on Odin mode - by shutdding down your phone, then holding Volume Up + Down, then long hold Volume Up to unlock bootloader, You might need to reboot afterwards, also factory reset is(will be) a must.
Just shut down after that, redo holding Volume Up + Down, then long hold Volume Up, I cannot remember exactly, but I think after that it was once pressing Volume Down to have proper odin download mode to use patched image.
Select patched magisk image patched from/by boot/recovery.img.lz4 archive.
I've UK A326B
Click to expand...
Click to collapse
The SM-A326U does not have the OEM Unlock option in Developer Settings to unlock the bootloader, so unfortunately we are unable to use the method linked.

tavella said:
The SM-A326U does not have the OEM Unlock option in Developer Settings to unlock the bootloader, so unfortunately we are unable to use the method linked.
Click to expand...
Click to collapse
I had an option, starting with tapping on build name to enable dev tools, enabling it then Vol Up + Vol Down.

Please feel free to verify images taken after root been aquired. (magisk image was patched on unrooted os at the time)
The OEM unlock itself in dev options is not doing complete OEM unlock, until contected to PC while Volume Up + Volume Down is presse
d, then loader gives option to do proper OEM unlock.
You're welcome.

Question OEM Unlock missing on SM-A326U

Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys

7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.

Seriously... So there's no way to unlock for free, or by waiting...?

Not a bootloader unlock. Its not just Tmo that are locking these down tighter.
You can unlock it for free if you can figure out whatever they do ;-)

Nah idc about a network unlock since I don't have service for this phone, I just wanna know if its possible to unlock the bootloader... I've tried everything

Who is talking about a network unlock?

TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
You said not a "bootloader unlock" so I was assuming you're talking about network unlock... Sorry, but should I just give up, there's seemingly NO WAYY to unlock the bootloader of a T-Sh*t phone.

Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.

TimmyP said:
Oh just misunderstanding my bad. I meant you cant wait for a bootloader unlock, but you can wait and maybe they would carrier unlock it later... but thats not what you want anyways.
Click to expand...
Click to collapse
That's kinda sad, I think I'm gonna just give up, but thanks for the information... Hopefully something happens in the future that allows it to be unlocked soon... Thanks man

I doubt they'll bring it back. OEM unlock that is. My phone is over 7 days old and I did the factory reset by holding the volume down and power buttons and then the volume up and power button and did the full factory reset. OEM unlock is still gone. Yes I got the developer options turned on. I rooted a couple of Nexus 6p's which of course are obsolete now since they were 3G and there is no backward capability. At least I got them used, replaced the batteries myself and can use them as WiFi phones with Talkatone through my WiFi. Read some blurbs about Kingo root working but I'd like to see that someone has pulled it off with the A32. Am under a 2 year obligation but I bought a second one to experiment on. I did that before I found out there was no OEM unlock. Well, if I break one, I'll have a backup. Except the phone is tied to the SIMM and I'd have to bring the backup in to have it reprogrammed.

TimmyP said:
Who is talking about a network unlock?
Click to expand...
Click to collapse
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...

iabhua said:
Any good service to network unlock SM-A236U or U1. Flashed XAA t no avail the Carrier_ID stays at DSH...
Click to expand...
Click to collapse
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know

TimmyP said:
7 days what? Tmo A326U doesnt have the option to unlock the bootloader, you need to pay the people here that provide the service. They are the only ones that seemingly know how to get it unlocked, and I can vouch for it.
Click to expand...
Click to collapse
Do you have any device with an unlock bootloader or unlock? I am trying to get a ram dimp for days nobody have an device.

andioshelp said:
I am working on unlock for it but I need root or a device on low security update. I am almost close to an solution if your device security patch is low please let me know
Click to expand...
Click to collapse
I have two SM-A236U’s but unfortunately one has binary 6 FW and the other binary 7.

1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
There was a similar procedure to unlock bootloader on a samsung mtk (A125U) same carrier as yours (T-Mobile TMB and the same applies to MetroPCS TMB) basicaly, you had to flash BL files from the A125W (canadian version) then unlocking bootloader using testpoint (bootrom mode) then using any paid or free app (in my case i use a paid one because i run a repair shop). even if you unlock bootloader using paid tools, it gets locked again when it turns on. (i tested it without flashing BL files)
sadly, i dont have a A326U lying arround to test said procedure.

1.fuxk_ said:
Hi guys,
Man oh man this phone...
So basically I'm trying to unlock my bootloader without waiting the 7 days, since I simply don't trust this phone to give me the OEM Unlock option after 7 days...
Before I decided to unlock my bootloader I had been using this phone for about 2 months like normal, sure I uninstalled a ton of bloatware and system apps that I didn't need which MIGHT have been the reason it didn't show the OEM Unlock after months, but the battery life was amazing.
But recently I've been considering rooting my phone, and before I started factory resetting and trying many different things to show the OEM Unlock option, keep in mind I've bee using this phone normally for a couple months, I checked the developer options and not a surprise, OEM Unlock wasn't there.
So ever since, I've tried sooo many things to show the OEM Unlock:
( I reflashed the stock firmware with Odin in between all these methods I've tried )
Also before I list everything I've tried heres the full specs of this phone and the drivers I've installed on my Windows 10
Samsung Galaxy A32 5G (SM-A326U)
T-Mobile, MTK, Network locked, No SIM, NOT Snapdragon
Drivers I've installed on my PC: Google USB Driver, ADB Interface, Samsung Android USB Driver, MTK Driver, USBDk and a few more can't remember the names...
1. Changing date, checking for an update and changing the date back, tried restarting the phone in between, tried turning wifi on and off in between.
2. Combination firmware, got unauthorized error on the download mode screen talking about the pit file.
3. Tried running:
adb reboot bootloader
fastboot devices (It successfully recognized my phone)
fastboot oem unlock: Unknown command
Didn't even run the command...
4. Since its a MTK CPU I had hope for mtkclient https://github.com/bkerler/mtkclient
It just kept asking to connect my phone, tried connecting with recovery mode, download mode and fastboot mode, none of them were recognized
The reason I need a quick way to unlock the bootloader, is cause I will be doing stuff with this phone that might result in me having to reflash the firmware which I can't risk it relocking and have to wait 7 days each time something goes wrong.
I heard that T-Mobile phones bootloader's are impossible to unlock, someone please tell me that is not true...
So basically,
Is there any way to unlock the bootloader? If not why and if yeah, what have I been doing wrong and how?
Thanks guys
Click to expand...
Click to collapse
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock

DjoFight said:
Did you tried, instead of fastboot oem unlock, fastboot flashing unlock
Click to expand...
Click to collapse
In case people need the procedures for those processes, I wrote this up recently to help others do it easier than it was for me to figure out.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode

Has any one made any progress regarding the missing oem unlock? I know what parameters to add to our kernel v1 to v3 during building to enable oem unlock and add access to fastbootd. Because of project treble our options have changed.
Sources:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Locking/Unlocking the Bootloader | Android Open Source Project
source.android.com
Sign in
DOCUMENTATION
Docs
More
Getting Started
Security
Core Topics
Compatibility
Android Devices
Reference
GO TO CODE ➚
Overview
Architecture
Overview
Hardware Abstraction Layer (HAL)
Kernel
HIDL (General)
HIDL (C++)
HIDL (Java)
Configuration
Device Tree Overlays
Vendor NDK
Vendor Interface Object
AIDL
Bootloader
Overview
Boot Reason
Boot Image Header
Implementing Bootconfig
Recovery Images
DTB Images
Supporting OTA Updates
Locking and Unlocking the Bootloader
Version Information in AVB Properties
Fastboot in Userspace
Partitions
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Virtualization
Tests
Updates
AOSP
Docs
Core Topics
Was this helpful?
Locking/Unlocking the Bootloader​bookmark_border
On this page
Unlocking the bootloader
Locking the bootloader
Setting lock/unlock properties
Protecting critical sections
By default, most Android devices ship with a locked bootloader, meaning that users can't flash the bootloader or device partitions. If needed, you (and device users with Developer options enabled) can unlock the bootloader to flash new images.
Unlocking the bootloader​To unlock the bootloader and enable partitions to be reflashed, run the fastboot flashing unlock command on the device. After setting, the unlock mode persists across reboots.
Devices should deny the fastboot flashing unlock command unless the get_unlock_ability is set to 1. If set to 0, the user needs to boot to the home screen, open the Settings > System > Developer options menu and enable the OEM unlocking option (which sets the get_unlock_ability to 1). After setting, this mode persists across reboots and factory data resets.
When the fastboot flashing unlock command is sent, the device should prompt users to warn them that they might encounter problems with unofficial images. After the user acknowledges the warning, the device should perform a factory data reset to prevent unauthorized data access. The bootloader should reset the device even if it can't reformat it properly. Only after a reset can the persistent flag be set so that the device can be reflashed.
All RAM not already overwritten should be reset during the fastboot flashing unlock process. This measure prevents attacks that read leftover RAM contents from the previous boot. Similarly, unlocked devices should clear RAM at every boot (unless this creates an unacceptable delay), but should leave the region used for the kernel's ramoops.
Locking the bootloader​To lock the bootloader and reset the device, run the fastboot flashing lock command on the device. Devices intended for retail should be shipped in the locked state (with get_unlock_ability returning 0) to ensure that attackers can't compromise the device by installing a new system or boot image.
Setting lock/unlock properties​The ro.oem_unlock_supported property should be set at build time based on whether the device supports flashing unlock.
If the device supports flashing unlock, set ro.oem_unlock_supported to 1.
If the device doesn't support flashing unlock, set ro.oem_unlock_supported to 0.
If the device supports flashing unlock, then the bootloader should indicate the lock status by setting the kernel command line variable androidboot.flash.locked to 1 if locked or to 0 if unlocked. This variable must be set in bootconfig instead of in the kernel command line in Android 12.
For devices that support dm-verity, use ro.boot.verifiedbootstate to set the value of ro.boot.flash.locked to 0; this unlocks the bootloader if the verified boot state is orange.

I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?

evnStevn said:
I have the A32 5G (64Gb Int. Stg.) & it's the Tracfone Only version or SM-S326DL. After recently receiving word that Android 13 was awaiting us, I quickly allowed my device to receive this very kool OTA operating system update. I mention this, because a week earlier I received an email from my prepaid wireless provider instructing me in detail how to manually unlock my A32 5G handset. So, to be clear, Tracfone notified me in their email how to unlock my device, but whan
this happens to often, to write this off as an app-mishap xda...why?!
(pls. explain this to me, what is really going on)?
Click to expand...
Click to collapse
I'm wondering too. Could you please pm me what you were trying to post?

Samsung A03s roo issues

Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
I'm using Magisk to patch the AP file
Then use ODIN to flash it and it stops at vbmeta with a error.
I'm new to this and have googled alot but now I'm really stuck.
So it fails, corrupt phone, I reflash oem AP and it restarts.
I have adb and fastboot ready to go,
Thank you.

Johnhek said:
Hey I am trying to root my sm-a037w, fully updated.
I remember having OEM unlocked it using the developer option which is now gone completely.
Click to expand...
Click to collapse
This is your problem, right here. If you closely read the Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.

V0latyle said:
This is your problem, right here. If you closely read the Magisk installation instructions:
If you can't see OEM Unlocking in Developer Options, and you see KG STATUS: PRENORMAL on the download mode screen, Vaultkeeper is still active and will reject custom images.
Click to expand...
Click to collapse
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?

Johnhek said:
Yea I've been trying for the last 48 hours and I can't figure it out how to get it back.
I did have developer mode active and had seen and allowed oem unlocking, not sure when I disappeared, I think it was the latest update.
Don't know how to proceed.
Tried setting the date back , disabling system update and software update, still no OEM Unlocking.
I have read those instructions many times, I have no prior experience rooting or modding android :/
Should I reflash original firmware?
Where do I go from here?
Click to expand...
Click to collapse
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.

flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com

aIecxs said:
flashing firmware is bad idea, this won't reset vaultkeeper. check RMM/KG state from download mode screen first. btw it's called odin mode (not fastboot mode)
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
Click to expand...
Click to collapse
Knox Guard has to be disabled by connecting to the Internet and checking for updates, and you have to be on stock firmware to do it.
Flashing the OEM firmware won't hurt anything, and is the only way to unlock KG.
Vaultkeeper is disabled by flashing the multidisabler in TWRP.

V0latyle said:
Did you ever see the OEM Unlocking toggle after you unlocked the bootloader?
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Reflashing the firmware might be a good idea. Keep in mind that Samsung is notorious for trying to disallow custom binaries on newer bootloaders. This is all speculation though, I'd need to see the error you got to have a better idea what the issue is.
Click to expand...
Click to collapse
Hey thank you once again for your help.
To be clear this is how I recall the events .
1. I did enable OEM unlocking in developer options.
2. I updated the phone through the user interface.
3. OEM unlocking option dissapeared entirely after updating to android 12.
4. Downloaded XAC region firmware using SamFirm
5. Copied AP to my phone storage
6. Patched AP with Magisk, then transferred patched file to my PC.
7. Flashed BL, patched AP, CP and CSC(not home) using ODIN 3.14
ODIN said AUTH fail at Vbmeta on my PC and on the phone iirc.
8.Reflashed using stock AP to make the phone usable again.
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Are KG and Vaultkeeper the same thing?
I guess my bootloader is locked and now OEM Unlocking option is gone.
This is the phone currently on latest firmware.
ODIN MODE reads:
FRP LOCK:ON
KG STATUS: CHECKING
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Baseband version A037WVLS 3 BVJ1 (bootloader version 3?)
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
I am also not sure of how to identify the region firmware I need, the software version in my about phone says:
SAOMC_SM-A037W_OYV_BMC_12_0004
BMC/BMC/XAC/BMC
I have downloaded both XAC and BMC, both have worked for me.

Ohhh, it's a Mediatek device
Johnhek said:
At downloader screen I never saw hold volume up to unlock bootloader, only press up to continue. (after booting holding volume up+down+power)
Click to expand...
Click to collapse
The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Johnhek said:
Are KG and Vaultkeeper the same thing?
Click to expand...
Click to collapse
More or less...Vaultkeeper is the process that determines the Knox Guard status, which in turn is what actually allows custom binaries
Johnhek said:
I guess my bootloader is locked and now OEM Unlocking option is gone.
Click to expand...
Click to collapse
We'll see...
Johnhek said:
KG STATUS: CHECKING
Click to expand...
Click to collapse
This means that KG (Knox Guard)/Vaultkeeper hasn't yet verified your device is supposed to be unlocked.
Johnhek said:
MTK SECURE BOOT: ENABLE (0)
sec ctrl status (1)
SECURE DOWNLOAD: ENABLE
Click to expand...
Click to collapse
Is there nothing on there that says OEM LOCK?
Johnhek said:
Thanks for all the info, sorry for the messy post and not including all the info required.
I will provide you with the info you request, I do not know how to verify my KG status, it reads checking in ODIN MODE.
Click to expand...
Click to collapse
That's exactly how - it tells you in download/Odin mode.
Since it says CHECKING, there are two things we need to do:
Ensure the bootloader is indeed unlocked, using the steps I gave above
Once bootloader is confirmed to be unlocked, you need to boot into Android, connect to the Internet (use a WiFi network), go into Settings > System > System update and check for software updates. This also checks Vaultkeeper/KG.
After checking for software update, enable developer options (if not already enabled) and verify OEM Unlocking is present; it should be grayed out with the message "Bootloader is already unlocked".

The proper way to enter device unlock mode is thus:
Unplug any USB cables, power device off completely
Connect a USB cable to your PC, don't connect it to your phone yet
Hold both Volume buttons, do not press Power, and plug in the USB cable.
The screen should turn on with 3 options: Volume Up for download mode, long press Volume Up for device unlock mode, Volume Down for restart. Release both Volume buttons, then hold Volume Up.
Device should prompt you to confirm you want to unlock. If it prompts you to confirm you want to re-lock, stop! The bootloader is already unlocked.
Click to expand...
Click to collapse
I just tried this and there is no mention of unlock bootloader, same as before (volume up to continue) I click to continue and it reads;
PRODUCT NAME: SM-A037W​CURRENT BINARY: SAMSUNG OFFICIAL​FRP LOCK: ON​KG STATUS: CHECKING (I never created a samsung account on this phone if that means anything)​MTK SECURE BOOT: ENABLE (0)​sec ctrl statu (1)​WARRANTY VOID: 0x0 (0x0)​RP SWREV: B3 NS3 Kb3, Kr3, Vb3, Vbs3 S3​SECURE DOWNLOAD: ENABLE​​​Maybe I have to wait 7 days as I have read somewhere before I get the OEM Unlock option back?​​Thank you for your help ​

your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com

aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
I am using the device normally and bought the phone new, using the google account i created for it , so i dont understand how this is possible.

Idk maybe FRP LOCK: ON disappears once you removed all bonded samsung and google accounts (maybe not caused by Google Factory Reset Protection but Samsung Reactivation Lock)?
V0latyle said:
I assume you -did- unlock the bootloader, correct?
OEM Unlocking does not unlock the bootloader, it simply allows you to.
Click to expand...
Click to collapse
No he didn't unfortunately. For bootloader unlocking and passing vaultkeeper one have to repeat that step twice, before and after unlocking/factory reset in odin/download mode.
https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699

aIecxs said:
your device is FRP locked. you have to unlock with google account first.
as you updated stock ROM and downgrade is impossible, I doubt you will ever get OEM unlocking back. updating stock ROM was bad idea.
BOUNTY; fix for persistent RMM state lock after 7 days
I've had a situation where RMM state has always been prenormal and OEM unlock been absent for months on Oreo. After updating to Pie, OEM unlock appeared immediately on first boot, but RMM state prenormal was still there and flashing twrp give me...
forum.xda-developers.com
Click to expand...
Click to collapse
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.

V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
Click to expand...
Click to collapse
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
Johnhek said:
I did have developer mode active and had seen and allowed oem unlocking, not sure when it disappeared, I think it was the latest update.
Click to expand...
Click to collapse
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
V0latyle said:
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
Click to expand...
Click to collapse
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...

V0latyle said:
Upgrading firmware shouldn't cause problems with OEM Unlocking or unlocking the bootloader. You've stated this a couple of times but have yet to provide any source for your claim.
FRP Lock is simply on because he has a Google account logged in, and has absolutely nothing to do with OEM Unlocking.
@Johnhek you have already connected your device to WiFi, yes? If not, you need to do so, then go to Settings > System > Software update to trigger a check. Once done, go back to Developer Options to see if OEM Unlocking is visible.
If the bootloader wasn't unlockable, the OEM Unlocking toggle would never be present. The toggle controls the state of sys.get_unlock_ability which tells the bootloader it can be unlocked. There are a couple of props that control whether OEM Unlocking is available, ro.oem_unlock_supported which is supposed to be baked into the ROM at build time, and ro.oem_unlock_allowed which determines whether the toggle is available.
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy.
Click to expand...
Click to collapse
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
aIecxs said:
I don't know for SM-A037W but I know about people selling their Samsung phones on Android 10 for buying same model on Android 9 for reason.
There is no official information but there are rumors that from certain security patch Samsung removed OEM unlocking forcefully (USA/Canada devices).
It's also my experience with SM-T555 region DBT still not unlockable as of today.
I think it's common sense when it comes to rooting/unlocking that older android versions are easier to root.
For other brands it's not possible to flash anything when FRP Lock is on. Furthermore that state means device is actually FRP locked. Didn't know about Samsung FRP LOCK ON is only information about device is ready for FRP locking, sorry about that...
nevertheless FRP lock is contradictory to OEM unlock, both together is afaik not possible (except for Xiaomi).
btw flashing stock firmware won't unlock RMM/KG prenormal
we will know more about in 7 days...
Click to expand...
Click to collapse
@Alecxs Yea I probably should have left it android 11.

V0latyle said:
I will admit I'm not very familiar with MediaTek Samsung devices, but I don't see why the process would be any different. Still, here is a guide on using MTKClient
Let's just see if we can get the OEM Unlocking toggle back and make KG happy
Click to expand...
Click to collapse
I will read the link tonight , much appreciated

Johnhek said:
@V0latyle hey I have tried those suggestions still no luck. Thank you and happy holidays, I will try waiting 7 days ND let everyone know
Click to expand...
Click to collapse
You can also try disconnecting from the Internet (take out your SIM as well) and set the date back by at least a week. Or you can set it forward.
Johnhek said:
@Alecxs Yea I probably should have left it android 11.
Click to expand...
Click to collapse
It shouldn't matter, honestly, although I generally prefer to do one thing at a time - unlock the bootloader, THEN update.
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Johnhek said:
I will read the link tonight , much appreciated
Click to expand...
Click to collapse
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.

V0latyle said:
I have a feeling that the MediaTek aspect of things may be the issue here, although I have no way of knowing.
Hopefully it will be of some help to you. It's not beginner friendly - you have to install Python and compile it, but if you can get MTKclient working, you can see if it's what you need.
Click to expand...
Click to collapse
Reading it now, I think I can handle it, the instructions seem clear.
As for the date trick.
I tried it while connected to wifi, I dont even have a sim card in this phone lol.
Tried setting to last month, havent tried forward in time though, will try disconnected as well.
The mediatek thing seems promising, I think the sec ctrl status (1) in the download screen is MTK related...
I will let you know.

I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.

aIecxs said:
I have read in one of the linked threads that SIM card plays a role here. I recommend to enable mobile data for 7 days, although there is less hope.
from what I have learned from elliwigy one can't cheat samsung bootloader not even with mtkclient. there is however paid service for devices with DID token on download screen (afaik Qualcomm only). but try mtkclient first it's a good exercise and maybe you're lucky and it works.
Click to expand...
Click to collapse
I tried mtkcient but I kept getting unauthorized handshake when trying to connect phone :/
Followed instructions as per link but I encounter one error in the process:
Get latest UsbDk 64-Bit​
Install normal MTK Serial Port driver (or use default Windows COM Port one, make sure no exclamation is seen)
Get usbdk installer (.msi) from here and install it
Test on device connect using "UsbDkController -n" if you see a device with 0x0E8D 0x0003
Works fine under Windows 10 and 11
I'm on windows 11 and when I put the command "UsbDkController -n" in terminal it doesn't recognize it.
I installed the usbdk drivers from git hub, a .msi fil, from the guide.
Another problem is I don't know how to set windows default COM Port one.

Can downloade mode be locked on sumsung devices and if so, can you unlock a locked download mode

i've read a blog post somewhere which talks of the possibility to lock a sumsung download mode, how can this be done or undone?

thelite said:
i've read a blog post somewhere which talks of the possibility to lock a sumsung download mode, how can this be done or undone?
Click to expand...
Click to collapse
Can you provide more details?
The bootloader lock prevents flashing and booting of unsigned images. With a locked bootloader, download mode does not accept custom software; all software packages must be OEM signed.
An unlocked bootloader (with Knox Guard disabled) will allow flashing custom firmware, such as TWRP recovery.
So, in that sort of sense, I suppose the bootloader lock does control what download mode will accept via Odin.

V0latyle said:
Can you provide more details?
The bootloader lock prevents flashing and booting of unsigned images. With a locked bootloader, download mode does not accept custom software; all software packages must be OEM signed.
An unlocked bootloader (with Knox Guard disabled) will allow flashing custom firmware, such as TWRP recovery.
So, in that sort of sense, I suppose the bootloader lock does control what download mode will accept via Odin.
Click to expand...
Click to collapse
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked

thelite said:
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked
Click to expand...
Click to collapse
im a newbie and i could be wrong about all this, but its been 2 days and googling has not hepled

thelite said:
im on the sumsung galaxy a032F, there is no oem unlock in developer options so i guess i cannot unlock the bootloader, and when i try to flash a custom firmware via odin i get an error mdm mode can't download odin. so after reading the blog post i was wondering, could the download mode be locked
Click to expand...
Click to collapse
Ah, ok. That makes a little more sense.
The bootloader has to be unlocked in order to flash custom firmware.
The process works like this:
Turn on OEM Unlocking in Developer Options (allows bootloader to be unlocked)
Boot device into unlock mode - starting with device off, hold both Volume buttons and plug in USB cable)
Follow device instructions to unlock (will wipe data)
Boot into system, allow system to connect to Internet to disable Knox Guard
Reboot into download mode, use Odin to flash TWRP
Use TWRP to flash custom ROM
So, if OEM Unlocking is not available, you can't do any of this, because that is the first step.

Unless you have factory restarted your device within the last week, no oem unlock means no custom firmware. You have the snapdragon variant, right?

V0latyle said:
Ah, ok. That makes a little more sense.
The bootloader has to be unlocked in order to flash custom firmware.
The process works like this:
Turn on OEM Unlocking in Developer Options (allows bootloader to be unlocked)
Boot device into unlock mode - starting with device off, hold both Volume buttons and plug in USB cable)
Follow device instructions to unlock (will wipe data)
Boot into system, allow system to connect to Internet to disable Knox Guard
Reboot into download mode, use Odin to flash TWRP
Use TWRP to flash custom ROM
So, if OEM Unlocking is not available, you can't do any of this, because that is the first step.
Click to expand...
Click to collapse
thanks for the answer, but i was wondering is there a way in which the oem unlock option can be hidden and unhidden or some way in which you can be prevented from unlocking the bootloader, because even the wipe data/factory reset is disabled, i came across this kind of devices and i was just curious is this entailed in android development or what material can you recommend if i want to know more about this

thelite said:
thanks for the answer, but i was wondering is there a way in which the oem unlock option can be hidden and unhidden or some way in which you can be prevented from unlocking the bootloader, because even the wipe data/factory reset is disabled, i came across this kind of devices and i was just curious is this entailed in android development or what material can you recommend if i want to know more about this
Click to expand...
Click to collapse
Bootloader lock doesn't prevent a factory reset. The screen you showed is recovery mode, not download mode. That's really strange, I've never seen factory reset hidden before
thelite said:
i get an error mdm mode can't download odin.
Click to expand...
Click to collapse
I think this is the clue. You have a organization managed device with an MDM lock (Mobile Device Management). MDM is used by enterprise IT departments to manage devices and can prevent bootloader unlocking as well as factory reset.
Let me guess, you bought this device used?

V0latyle said:
Bootloader lock doesn't prevent a factory reset. The screen you showed is recovery mode, not download mode. That's really strange, I've never seen factory reset hidden before
I think this is the clue. You have a organization managed device with an MDM lock (Mobile Device Management). MDM is used by enterprise IT departments to manage devices and can prevent bootloader unlocking as well as factory reset.
Let me guess, you bought this device used?
Click to expand...
Click to collapse
yes, i got this device from somebody for experiment, just to see if i can go past all this, and yes the screen i showed is a recovery mode screen, i was showing the hidden factory reset option. any help how i can go about this

thelite said:
yes, i got this device from somebody for experiment, just to see if i can go past all this, and yes the screen i showed is a recovery mode screen, i was showing the hidden factory reset option. any help how i can go about this
Click to expand...
Click to collapse
I think your only option is to find out which company the phone belonged to before. If they removed it from their fleet, they can probably remove the MDM lock. This is actually pretty common - enterprise managed devices will be "retired" from fleet service and sold without being properly decommissioned - they're wiped, but the IT department doesn't remove the MDM lock.
They might or might not unlock it for you, but it doesn't hurt to ask.

V0latyle said:
I think your only option is to find out which company the phone belonged to before. If they removed it from their fleet, they can probably remove the MDM lock. This is actually pretty common - enterprise managed devices will be "retired" from fleet service and sold without being properly decommissioned - they're wiped, but the IT department doesn't remove the MDM lock.
They might or might not unlock it for you, but it doesn't hurt to ask.
Click to expand...
Click to collapse
so technically i can't find a way around it myself, i just have to request the company

There is no way I know to bypass it.

There are lots of videos online if you Google “ bypass mdm lock android “

thelite said:
so technically i can't find a way around it myself, i just have to request the company
Click to expand...
Click to collapse
MDM locks typically can't be removed by the end user. That's the whole point - to prevent employees from using devices inappropriately and removing them from enterprise management via factory reset

Kolay gelsin hocalarım telefon kendi kendine Samsung yazısında kaldı revovery kullanamıyor bende Odin ile stok rom attı kilit açmadan
Şuan telefon indir sadece tek giriyor başka hiçbir şey açılmıyor OEM kilit ve frp kapalı
Take it easy, my teachers, the phone is stuck in the Samsung text itself, cannot use revovery, I have a stock rom with Odin, without unlocking it Now the phone is downloading only one entry nothing else does not open OEM lock and frp is off