Hi everyone I'd like to root my s10e, it is on android 12 One Ui 3.1
I can't unlock the bootloader the option called oem unlock is just not there in developer settings, I tried the trick with time changing and it just doesn't work, though in adb it says that it could be unlocked, I'm from Europe I orded a unlocked phone on Amazon here a screenshot of more detailed information, I'd like some help guys I'm going crazy trying everything
Look inside here:
Unlock Bootloader Samsung Galaxy S10e and Hard reset
How to Hard reset and Unlock Bootloader Samsung Galaxy S10e without Trigger KG State / RMM state Prenormal. If you want to flash ROM, you need to unlock the bootloader, unlocking bootloader on Galaxy
www.recovery-mode.com
jwoegerbauer said:
Look inside here:
Unlock Bootloader Samsung Galaxy S10e and Hard reset
How to Hard reset and Unlock Bootloader Samsung Galaxy S10e without Trigger KG State / RMM state Prenormal. If you want to flash ROM, you need to unlock the bootloader, unlocking bootloader on Galaxy
www.recovery-mode.com
Click to expand...
Click to collapse
Thanks man but unfortunately I tried this as well, I don't have the third option for unlocking, all I have in recovery is cancel and continue, holding volume up doesn't do anything
Hello ? Can someone tell me at least if it's doable ?
Someone ?
I've been in the same boat for a couple of months now. It seems that Samsung does not allow this option in the UI (or anywhere else I can find for that matter) for Qualcomm versions. Hopefully someone will come up with a proper hack soon because the bloatware on s10e is just disgustingly invasive and desktop mode is definitely lacking compared with Linux alternatives.
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-A037WCURRENT BINARY: SAMSUNG OFFICIALFRP LOCK: ONKG 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 S3SECURE DOWNLOAD: ENABLEMaybe 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.