Database Info

Samsung galaxy j3 prime sm-j327t1

Does anyone have any development on this device? It's newer and running a droid 7.0 nougat. Any root info or bootloader unlock info would be greatly appreciated

I too am looking, upgraded from the smj320a, gotta day love the phone just needs root do I can retire my older one.
Side note, I noticed oem unlock is missing. Haven't been able to find a reason or answer.

Yeah I seen that too. I was thinking about trying the custom recovery twrp for the galaxy emerge which has the same board and specs as the j3 prime except it's running marshmallow. If I flash it that might work but then it will trip the frp lock and the phone will be soft bricked. It's hopeless with a locked bootloader

Well, frp bypass is kind of my new found hobby. Have locked 10 devices and bypassed them all, one was a new found bypass on the lg tribute 5 running that 5.1.1. So if you frp I can help. Can we tag people in these like that crap spy social network site? Aka FB. Because I do know someone who could possibly help.

I too would also like to root this phone. T-Mobile variant.

How do we go about getting the sm-j327t1 it's own set of development threads?

bobbyp1086 said:
Well, frp bypass is kind of my new found hobby. Have locked 10 devices and bypassed them all, one was a new found bypass on the lg tribute 5 running that 5.1.1. So if you frp I can help. Can we tag people in these like that crap spy social network site? Aka FB. Because I do know someone who could possibly help.
Click to expand...
Click to collapse
Frp is not locked as I have not tried to flash a recovery but I know if will lock if I flash my device with the bootloader locked

mrmack44240 said:
Frp is not locked as I have not tried to flash a recovery but I know if will lock if I flash my device with the bootloader locked
Click to expand...
Click to collapse
I did some digging and
https://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
Idk if that's what we're looking at so far only lead to it tho
Also did some digging with shortcut master found some interesting things

Adb shell getprop shows 1 for oem unlock ability

bobbyp1086 said:
Adb shell getprop shows 1 for oem unlock ability
Click to expand...
Click to collapse
At the same time it says it's not allowed check pictures

Also found this,
https://www.google.com/url?sa=t&sou...RE0Emhghh1sYy7IZw&sig2=DRKv6ALTtyfnCCjjE-CzgQ
Verified boot. Maybe a root that takes affect after boot. Like a temp boot, an on and off switch type root.

bobbyp1086 said:
At the same time it says it's not allowed check pictures
Click to expand...
Click to collapse
I don't own this device, but according to what I can gather, it seems that FRP can be OEM unlocked, but the property is not set hence the property set to 0 for sys.oem_unlock_allowed.
For why it doesn't appear in dev settings I think is another issue. Can anyone confirm that this device does NOT have a manufactuerer locked bootloader.
Just to clarify:
OEM unlock = disable Googles FRP lock not unlock the bootloader.
If this device has a manufacturer locked bootloader then the likelyhood of root for this device is minimal.

ashyx said:
I don't own this device, but according to what I can gather, it seems that FRP can be OEM unlocked, but the property is not set hence the property set to 0 for sys.oem_unlock_allowed.
For why it doesn't appear in dev settings I think is another issue. Can anyone confirm that this device does NOT have a manufactuerer locked bootloader.
Just to clarify:
OEM unlock = disable Googles FRP lock not unlock the bootloader.
If this device has a manufacturer locked bootloader then the likelyhood of root for this device is minimal.
Click to expand...
Click to collapse
How can I check it?
Also while roaming through a shortcut creator I noticed frp is an option in many of the secret menu settings, what ever happened to temp root?

bobbyp1086 said:
How can I check it?
Also while roaming through a shortcut creator I noticed frp is an option in many of the secret menu settings, what ever happened to temp root?
Click to expand...
Click to collapse
Do you have the stock firmware?

ashyx said:
Do you have the stock firmware?
Click to expand...
Click to collapse
Yes Sir only a week old

bobbyp1086 said:
Yes Sir only a week old
Click to expand...
Click to collapse
The easiest way would be to simply remove the signature from the stock recovery image and then see if it flashes with odin. If it does the bootloader isn't locked. If it fails then it's highly likely to be locked.

ashyx said:
The easiest way would be to simply remove the signature from the stock recovery image and then see if it flashes with odin. If it does the bootloader isn't locked. If it fails then it's highly likely to be locked.
Click to expand...
Click to collapse
English? I have Odin, then what

I found an article saying for oem unlock to factory reset and don't set up Google, no frp to stop oem unlock. I'm backing up apps now will update in a few hours

bobbyp1086 said:
I found an article saying for oem unlock to factory reset and don't set up Google, no frp to stop oem unlock. I'm backing up apps now will update in a few hours
Click to expand...
Click to collapse
That sounds promising

Yes I didn't set a screen lock as from what I've learned that's what activates frp, unfortunately my laptop has crashed (anyone good at bios pm me) but still no oem unlock and adb isn't working now, pc at work I've got android studios downloaded but I'll refrain from the lock until I can check, still don't know how to pull a signature from a stock image tho... But also in that article it States that oem unlock was enabled even tho there was no setting but they had unlocked boot loaders

SM-S205DL (Straight Talk Model)

Hi all,
I have a Straight Talk Galaxy A20, model SM-S205DL. Will root instructions work for this model? I don't notice an OEM unlock option in the Developer Mode menu, but I can boot in download mode. Thoughts? It's been a while since I tried to install custom firmware.

justlance said:
Hi all,
I have a Straight Talk Galaxy A20, model SM-S205DL. Will root instructions work for this model? I don't notice an OEM unlock option in the Developer Mode menu, but I can boot in download mode. Thoughts? It's been a while since I tried to install custom firmware.
Click to expand...
Click to collapse
You need to unlock OEM for it to work

physwizz said:
You need to unlock OEM for it to work
Click to expand...
Click to collapse
Okay. Is there a way to do that other than the developer options menu? If the OEM unlock option isn't there, is there some other method?

justlance said:
Okay. Is there a way to do that other than the developer options menu? If the OEM unlock option isn't there, is there some other method?
Click to expand...
Click to collapse
There is a trick where you change the date to some weeks in the future.

im having the same issue

yea the dev options to show OEM Unlock seems to be gone from Straighttalk/tracfone versions, its even Gone from Download Mode (you dont even SEE the option for long-press vol+ to unlock bootloader)

is there a way to root

Corelua01 said:
is there a way to root
Click to expand...
Click to collapse
Some places claim to be able to change the CID of the phone. Would that help? I imagine once able to load different non-TFN BS firmware on the phone that magic developer option may appear. Or is it a hardware thing and the exynos chip has something to do with it? Not sure how it all works yet. Anyone know what the unlocked us retail model contains?
I'm not smart enough to find out so hopefully someone is and reads this and can chime in regarding all the points...
Me and my arrow...

Question How to unlock bootloader?

I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.

- Hit settings
- about phone
- software information
- build number 5 times
- profit

I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.

RedHatter271 said:
I have no issue unlocking developer options. As my first post said the OEM Unlock option is missing from dev options.
Click to expand...
Click to collapse
Have you tried through fastboot? (fastboot oem unlock)

Oh, got you. Sorry!

As far as I'm aware samsung devices don't support fastboot. I did attempt to connect it in case I was wrong but was not able to get fastboot to recognize the device.

RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.

darkidz555 said:
You can try directly unlock without ticking the oem unlock. By boot into download mode. The other thing is your device or carrier or country wont allow your flip 3 to be unlock. There last step you can try is clean flash via odin with your latest firmware.
Click to expand...
Click to collapse
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.

RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
Did your Developer Options come already unlocked after setting it up?

twistedumbrella said:
Did your Developer Options come already unlocked after setting it up?
Click to expand...
Click to collapse
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9

luigi90210 said:
If you had them enabled on your last phone and you restored from your Google backup, developer options will be enabled. Has happened on all of my phones since Android 9
Click to expand...
Click to collapse
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.

twistedumbrella said:
Thanks, but I was asking @RedHatter271 to see if the restore data might have corrupted the options.
Click to expand...
Click to collapse
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking

luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader unlocking
Click to expand...
Click to collapse
They support it.

RedHatter271 said:
I can get into download mode fine but don't know how to use that to unlock directly. Can you give more details?
I tried a clean flach with my latest firmware but it didn't change anything.
It's a US carrier unlocked version I bought directly from Samsung. CSC of XAA. Currently using a T-Mobile SIM.
Click to expand...
Click to collapse
If you can boot into download mode there is an instruction just press vol up button and it will prompt do you want to unlock bootloader mine is like that. Im not sure yours since mine is korea version.

luigi90210 said:
My option is missing as well but I have the T-Mobile model that I have sim unlocked. As far as I knew all us models of Samsung phones did not support bootloader .
Click to expand...
Click to collapse
They support bootloader unlock. samsung dont support using fastboot unlock or command at all

if you're in North America, Canada etc Qualcomm chips there do not support bootloader unlocking, at least the Samsung one's don't, not sure about other OEMs.

darkidz555 said:
They support bootloader unlock. samsung dont support using fastboot unlock or command at all
Click to expand...
Click to collapse
They used to, so there was always a possibility it returned.

I recently read this article on XDA about unlocking the boot loader on the Fold 3 which results in Samsung disabling the camera (WTH?), Is this a thing on the Flip3 too?

My device is rooted. I have always been able to find the OEM unlock option under developer options without any constraints.
My camera is NOT affected. I can still use it without any issues.
I have an European device (SM-F711B).
Hope this helps some of you to track down whether this is a location or carrier based problem.

Hey Redhatter,
Out of topic question, but are you getting Tmobile 5G just fine?
RedHatter271 said:
I just received my Flip3 (SM-F711U1) and would like to unlock my bootloader. However developer options is missing the OEM Unlock option. It's completely missing not just grayed out. I read a few articles about needed to change the system date but none of those guides changed anything. Can someone help?
Also, I attempted to call *#*#7378423*#*# to double checked that it wasn't already unlocked and I got a popup saying "Unabled to process the request."
Thank you.
Click to expand...
Click to collapse

Bootloader unlock GALAXY A13 5G

Greetings,
I'm really frustrated trying different methods online to show the hidden "OEM unlock" in developers menu, but without avail. Anyone can help to root this mobile?
VERSION:
AP: A136WVLU1AUK9
CP: A136WVLU1AUK9
CSC: A136WOYV1AUK9
MODEL: SM-A136W
Android Version: 11
Regards,

Hope this helps

droidkill3r said:
Hope this helps
Click to expand...
Click to collapse
Thank you for sharing, I’ll give it a try

To root a phone's Android unlocking its bootloader is NOT required.
You simply have to add SU binary to Android's filesystem and make this binary executable.

I want to oem unlock bootloader for trwp and roms but I can't find oem unlock in dev settings and tried the video above and a couple of other things I found

You need the Samsung flash tool and the version of android for the phone and su +twep+magisk is optional good luck
Ps. Allways back up everything!

lashark06 said:
You need the Samsung flash tool and the version of android for the phone and su +twep+magisk is optional good luck
Ps. Allways back up everything!
Click to expand...
Click to collapse
And I'm fixing the Samsung flash tool is PC only correct? My **** got stolen like a few weeks ago so I'm trying to figure out how to do this **** without a computer and it's a pain in the ass pretty much impossible.

I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful too.

Maybe who's find how to unlock bootloader on this device after July update?

When u chage time back to 3 years OEM Unlock is comeback

nagante0 said:
When u chage time back to 3 years OEM Unlock is comeback
Click to expand...
Click to collapse
Tell how to do this

I just got the galaxy a13 and have tried to unlock the bootloader without success. Has anyone figured this out or am I looking in the correct forum?

nagante0 said:
When u chage time back to 3 years OEM Unlock is comeback
Click to expand...
Click to collapse
Tried this multiple tines without success. Can you explain ?

hello guys. i have an mkopa samsung galaxy a13, -current binary Samsung official -KG state Active (01) -OEM lock On(L) -Eng mode Factory bin allowed (DASEUL) -Eng mode Atcmd allowed(DASEUL).............is it possible to flash its software....?????????? bootloader also locked

xXx yYy said:
To root a phone's Android unlocking its bootloader is NOT required.
You simply have to add SU binary to Android's filesystem and make this binary executable.
Click to expand...
Click to collapse
how do i achieve this

DerekLindvall said:
I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful Odin is sams factory setup utility
Click to expand...
Click to collapse

Odin is sam's factory utility for setup and repair. It will flash any sams device with it's OEM firmwear AFASIK

DerekLindvall said:
I am having this issue and can't find a resolution for it anywhere.
Boost Galaxy a13 5g android 12:
No OEM unlock switch available...
The trick changing the date doesn't work at all...
I am not trying to flash custom ROM, just to tweak the system kernal settings.
I seen someone mentioned to root w/o the OEM unlocking switch available, all that is needed is to flash the SU binary with Odin.. I haven't tried this yet but I am almost positive Odin for windows doesn't even read the Samsung devices without the bootloader being unlocked.
Anyone care to chime in here? i'd be very appreciative!
Mainly WTF is the OEM unlock switch not available on my device. I actually have 2 of the same devices and both are without the switch.
Also would flashing SU work and do the trick?
Any other useful information you could send my way would be really helpful too.
Click to expand...
Click to collapse
United States versions of samsung phones never have the oem unlock option. even if it is unlocked.

TheWorldYT said:
United States versions of samsung phones never have the oem unlock option. even if it is unlocked.
Click to expand...
Click to collapse
only models outside the united states have the oem unlock option.

TheWorldYT said:
only models outside the united states have the oem unlock option.
Click to expand...
Click to collapse
Is there any way to root the A136U 5g without unlocking the bootloader. I'm currently running on Android 13.. I want to delete or debloat the ATT & Samsung app installed at that takes up 8G of storage

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.