OEM on(u) in download mode - Samsung Galaxy S10e Questions & Answers

hi guys
i have a samsung s10e SM-G970F Exynos 9820. i enabled allow oem to be unlocked in developer options, and also usb debugging. i am running android 12 as phone just updated. i cant flash anything using odin it just fails all the time. i did notice in downlaod mode that it said next to oem it said oem on(u) and underneath it said KG checking.
any help with an explaination of what the both mean as i would like to flash twrp and custom rom
regards
albouet

Related

[Completed] Samsung Galaxy Grand Prime+(SM-G532F) rooted and locked after disabling OEM unlocking

Hey guys, I'm new here...
Well yesterday my dad bought me a Samsung Galaxy Grand Prime+ SM-G532F (vodafone, South Africa).
I wanted to root it( i always used to use KingoRoot) but i found a thread with an exploit to root the SM-G532F/M/G or something like that. Anyways i used it and flashed the "root-boot.tar" and followed all the steps( Enabled OEM unlocking and usb debugging) and i had root access and everything was perfect.
Then i thought i didn't need the OEM unlocking and the usb debugging anymore so i disabled both. Then afterwards i rebooted my phone( Because i had just installed Magisk so i could play pokemon go on a jailbroken device and it required a reboot.).
As it restarted, I got this message on a light blue screen( i don't think it even booted), "Security Error: This phone has been flashed with unauthorised software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost."
I think this is because of disabling the OEM unlocking. I tried flashing a stock ROM(it was really small though, but am downloading a 1.5Gb one right now) using odin while in download mode( The phone doesn't have a recovery menu to wipe/factory reset. It goes straight to download mode) and it appears that the custom binary (boot.img) is being blocked by the FRP lock.
Here is what appears when i go into recovery(well download mode):
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G532F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0x1 (0x302)
MTK SECURE BOOT: ENABLE
AP SWREV: B1 K0 S0
SECURE DOWNLOAD: ENABLE
I can't use ADB because it doesn't even appear if i try "adb devices" it is completely blank. But in odin it shows 0:[COM4]. Is this because my usb debugging is disabled? Can i flash with odin if usb debugging is disabled? If not, is there a way to enable usb debugging with the phone only in download mode( As in no ADB recovery or updating from sd card etc).
Please help. I really need to fix this. Even if i lose everything on the phone it's fine since i only got it yesterday.
nullbyte001 said:
Hey guys, I'm new here...
Well yesterday my dad bought me a Samsung Galaxy Grand Prime+ SM-G532F (vodafone, South Africa).
I wanted to root it( i always used to use KingoRoot) but i found a thread with an exploit to root the SM-G532F/M/G or something like that. Anyways i used it and flashed the "root-boot.tar" and followed all the steps( Enabled OEM unlocking and usb debugging) and i had root access and everything was perfect.
Then i thought i didn't need the OEM unlocking and the usb debugging anymore so i disabled both. Then afterwards i rebooted my phone( Because i had just installed Magisk so i could play pokemon go on a jailbroken device and it required a reboot.).
As it restarted, I got this message on a light blue screen( i don't think it even booted), "Security Error: This phone has been flashed with unauthorised software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost."
I think this is because of disabling the OEM unlocking. I tried flashing a stock ROM(it was really small though, but am downloading a 1.5Gb one right now) using odin while in download mode( The phone doesn't have a recovery menu to wipe/factory reset. It goes straight to download mode) and it appears that the custom binary (boot.img) is being blocked by the FRP lock.
Here is what appears when i go into recovery(well download mode):
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G532F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0x1 (0x302)
MTK SECURE BOOT: ENABLE
AP SWREV: B1 K0 S0
SECURE DOWNLOAD: ENABLE
I can't use ADB because it doesn't even appear if i try "adb devices" it is completely blank. But in odin it shows 0:[COM4]. Is this because my usb debugging is disabled? Can i flash with odin if usb debugging is disabled? If not, is there a way to enable usb debugging with the phone only in download mode( As in no ADB recovery or updating from sd card etc).
Please help. I really need to fix this. Even if i lose everything on the phone it's fine since i only got it yesterday.
Click to expand...
Click to collapse
Greetings and welcome to assist. FRP lock shouldn't prevent you flashing stock rom, the easiest way to restore your device should be with kies/smart switch and using the emergency firmware recovery option
Regards
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. FRP lock shouldn't prevent you flashing stock rom, the easiest way to restore your device should be with kies/smart switch and using the emergency firmware recovery option
Regards
Sawdoctor
Click to expand...
Click to collapse
Ok thanks... Neither worked but i managed to flash the stock rom i got from sammobile.com using odin and it was able to boot and the security error was gone
nullbyte001 said:
Ok thanks... Neither worked but i managed to flash the stock rom i got from sammobile.com using odin and it was able to boot and the security error was gone
Click to expand...
Click to collapse
Thats great news, I'll close this one up then
Sawdoctor

cant enable oem unlock

im on nemesis rom with s8+ rooted ..but i went to developer option try to enable the oem unlock and it turn on and off again why what to do?
If you already have twrp installed this is useless and is functioning properly.

A30s..A307FN how to unlock bootloader (security patch:August 1,2019)?

Hi! to all
Here are details:
baseband version:A307FNXXU1ASHE
security patch:August 1,2019
in developper settings oem show up and enable
phone still locked in download mode
KG STATE:Checking
FAP LOCK OFF
OEM LOCK ON(U)
Best Regards!
netphone said:
Hi! to all
Here are details:
baseband version:A307FNXXU1ASHE
security patch:August 1,2019
in developper settings oem show up and enable
phone still locked in download mode
KG STATE:Checking
FAP LOCK OFF
OEM LOCK ON(U)
Best Regards!
Click to expand...
Click to collapse
Hello friend, maybe you can try to download and reinstall the same rom you have and use odin to install it, the rom will give you a clean system later you can try to enable OEM again!
netphone said:
Hi! to all
Here are details:
baseband version:A307FNXXU1ASHE
security patch:August 1,2019
in developper settings oem show up and enable
phone still locked in download mode
KG STATE:Checking
FAP LOCK OFF
OEM LOCK ON(U)
Best Regards!
Click to expand...
Click to collapse
open you phone and connect to internet
Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Download and Install Samsung Mobile Phone Drivers ( ignore this if you have installed it ) Drivers Download
Enter Download Mode ( Connected USB Cable to PC, Turn Power off the phone, Press and hold Volume Down + Volume Up keys together then while pressing these keys connecting the phone to PC with USB Cable Data, release all keys when Download Mode appears ).
In Download Mode you see the long press Vol Up option to enter Device Unlock Mode. Unlock the bootloader ( that will wipe your device so be sure to backup of your data )
After Bootloader unlock, the phone will reboot and make sure the phone connected to the internet
now repeat (1) and go to devolper options you will found that OEM unlock is checked with gray and you cannot change it
now your bootloader will be unlocked successfully .

HELP!!! Custom Binary (BOOT) Blocked By OEM Lock

Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when I flash the recovery.tar file. After it fails it gives me a prompt on my phone on recovery mode saying Custom Binary (BOOT) Blocked By OEM Lock. I have enabled OEM Unlocking and USB debugging but it seems like it doesn't enable is there a way that your carrier can block these options to not enabled because that's what my starting to think why I can't seem to root my device. Can anyone suggest any workaround or fixes for this problem.
While your phone is turned off hold down both volume buttons and connect the usb cable, it will give you 2 options just hold down the volume up button and your bootloader will be unlocked
mody00 said:
While your phone is turned off hold down both volume buttons and connect the usb cable, it will give you 2 options just hold down the volume up button and your bootloader will be unlocked
Click to expand...
Click to collapse
That will go to download mode but wont unlock bootloader
2triple0 said:
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when I flash the recovery.tar file. After it fails it gives me a prompt on my phone on recovery mode saying Custom Binary (BOOT) Blocked By OEM Lock. I have enabled OEM Unlocking and USB debugging but it seems like it doesn't enable is there a way that your carrier can block these options to not enabled because that's what my starting to think why I can't seem to root my device. Can anyone suggest any workaround or fixes for this problem.
Click to expand...
Click to collapse
This happens to the a207f because it has Snapdragon instead of Exynos
You have to flash Stock Firmware
Boot back to download mode and long Press Volume up button.
then you will be oem unlocked
....except not that I unlocked and relocked bootloader on s10e it won't show up again in developer options

Fastboot, Samsung Galaxy A51

Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online

Categories

Resources