Database Info

[Q] Secure download: Enable and can't use odin to flash anything or stock rom

I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?

Use the latest version of Odin

kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
try diffrent USB ports on the computer and diffrent signal cords

kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
Did you enable usb debugging? Oh my bad, scratch that, try connecting your phone to your pc b4 you open Odin (using the latest Odin and run as admin)

kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
hi! i have the same problem , did you find a solution please? thanks

That secure download enable thing is normal mine has the same thing. Your phone is not connecting for whatever other reason

Try flashing exact stock firmware with odin.
SMG920I
POWERED BY INSUFFICIENT RAM
TUNED BY TEAM PINGPONG
DRIVEN BY KFORKAI

darksimo said:
hi! i have the same problem , did you find a solution please? thanks
Click to expand...
Click to collapse
Yeah i got it flashed. Turned out that i used an old odin also you have to get a firmware which has the same csc or one that it compatible with your device. Info on samsung csc can be found on the net, look for multi csc codes if you wanna change to software from another carrier.
Sent from my VS980 4G using XDA Free mobile app

Before you start flashing always disable reactivation lock. Othervise flashing may fail.

ODIN won't detect Galaxy S5 G906K [KT]
Hello All,
I've been having the same issues as people in this thread but have been unable to come up with a solution so far. I've tried to the whole battery trick which sometimes works with other Samsung devices but have been unable to solve this problem. It seems that ODIN just won't detect the 906K while it is on the recovery mode window. However if the phone is booted normally ODIN sees its fine.
i.imgur.com/boK57io.jpg
Can anyone provide some assistance?
Thanks in advance..
ODIN Version: Odin3_v3.10.7
Device Model: Samsung Galaxy S5 SM-G906K [kt]

Resolved.
nano-dev said:
Hello All,
I've been having the same issues as people in this thread but have been unable to come up with a solution so far. I've tried to the whole battery trick which sometimes works with other Samsung devices but have been unable to solve this problem. It seems that ODIN just won't detect the 906K while it is on the recovery mode window. However if the phone is booted normally ODIN sees its fine.
i.imgur.com/boK57io.jpg
Can anyone provide some assistance?
Thanks in advance..
ODIN Version: Odin3_v3.10.7
Device Model: Samsung Galaxy S5 SM-G906K [kt]
Click to expand...
Click to collapse
So after an entire day of investigation and logging I've figured out that this was an issue related to a carrier update by Olleh (KT). For anyone who runs into the same problem on the SM-G906K I recommend KingRoot as a means of getting started for root. CWM/TWRP are also methods that I tested with success.
I hope this helps someone who has the same problem down the road.

kingroot not working!
nano-dev said:
So after an entire day of investigation and logging I've figured out that this was an issue related to a carrier update by Olleh (KT). For anyone who runs into the same problem on the SM-G906K I recommend KingRoot as a means of getting started for root. CWM/TWRP are also methods that I tested with success.
I hope this helps someone who has the same problem down the road.
Click to expand...
Click to collapse
.................................................................................................................................................................................................
kingroot was working when they released V.4.5.0 but now not working anymore :crying:
sorry for my bad English

kekeke9e said:
I'am using S6 G920F. When i connect it to my computer, everything is ok, i setup all driver. However, when i put my phone in download mode to flash stock rom or root file by odin, odin 3.10.6 can't connect with my phone. In screen of download mode, i see " Secure dowload: Enable" in blue. I tried to use older version of odin but all are failed
I was already turn off Samsung Reactivation Lock, check USB Debug.
How to fix this problem?
Click to expand...
Click to collapse
try using box tools like z3x to see if problem would be solved

Update: i fix it by unmouting checking and mounting back the phone...weird a part or idk had to be not well attached.

Hello
I was trying to root Samsung galaxy grand prime G530H. But it has stucked in 'downloading...'
Secure Download : Enable in blue

Why can't I unlock the bootloader on FZ? There is just no such option in Dev Mode.

Hi there, have Samsung sm-G935F..stuck at Samsung logo..tried 2 flash file available from z3x team, shell. When using Odin to flash the programme freezing, when using Samsung tool to flash, it's reading the device and file but it's gerring error. Any advice on this?

Feyaad said:
Hi there, have Samsung sm-G935F..stuck at Samsung logo..tried 2 flash file available from z3x team, shell. When using Odin to flash the programme freezing, when using Samsung tool to flash, it's reading the device and file but it's gerring error. Any advice on this?
Click to expand...
Click to collapse
You could always try the S7 edge specific forums.
Not being sarcastic

root the chines root
i have sm-n9006 i cant root my phone
also have the secure download enadled in blue
any help ??
my phone is a chinses version ... which doesnt have the play store

Hello
Do you have your bootloader blocked, the new version of firmware enabled this option, you need to go to development options and enable the option of OEM, and that's it, you can flash whatever you want

Solution to “custom binary blocked by fpr lock” for galaxy a5 2016 – SM-A510FD

Hi,
Okay, I hope this method can help you, so you don’t have to go through the tedious process I went through to fix this fpr lock problem, I personally tried a lot of methods described in forums and finally was able to fix this problem, so I hope this works for you too and you don’t have to spend a lot of time looking for a solution to this problem.
I used this method on my galaxy a5 2016, but I think it will work on other Samsung phones as well if you download the right stock rom for it.
Warning: if you are a newbie, please read through this entire post once before attempting to try it out. It’ll only take a few minutes but at least you’ll know what you’re doing.
since i'm a new user i'm not allowed to post outside links so i'll put spaces between my links to be able to post them.
So I had the same problem as a lot of other guys, I had rooted my Galaxy A5 Sm-a510-fd through CF-Auto-Root, Everything was working fine, But Since I didn't know about OEM Unlocking & FRP Lock (Factory Reset Protection), I Logged Into my google account in my phone, and after restarting my phone after installing an app, my phone showed a red small text at the top left corner of my screen saying "custom binary blocked by fpr lock", now keep in mind I had enabled usb debugging and oem unlocking before but since I logged into my google account, apparently google had disabled the oem unlocking, hence this message.
Now I tried a few methods like a method where someone had said to go into download mode (Hold Volume down + Home + Power) and then pressing the volume down (cancel) instead of volume up (continue) and after the restart the phone for some reason wouldn't show this message again (weird), some had tried this in that forum with success but it didn’t work for me, so first try this see if it works for you, then I tried to flash a new stock rom but I got the same frp lock message in download mode as well, then I tried a few other method which didn’t work and I don’t even remember them (I’m a newbee, and I was confused by all the articles I had read and all the method I had tried so I don’t remember a lot of them, and a few of them may have worked but needed to remove the battery but in galaxy a5 battery isn’t removable), but the method which finally worked for me was this (It was posted in gsmhosting . com by zishhaider user):
1. Download (A510FXXU1AOL1 02.12.2015) from samsung-updates . com/device/?id=SM-A510F or from sammobile . com/firmwares website.
2. Remove .md5 at the end of stock rom you downloaded, extract the .tar file with 7zip to a folder, delete cm.bin and sboot.bin from this folder, open 7zip file manager from you installed program list in windows, navigate to the folder, choose all remaining files, click add, choose tar as archive format and and click ok to compress the files again into a tar format (a better method to re-pack these files into a tar ball is by using a software called unified android toolkit described at the end of this post).
3. Download and install the latest kies from Samsung (it will automatically install the latest usb drivers for your phone) and I recommend restarting your computer after installing kies.
4. Now go to download mode (Volume down + Home + Power >> Volume Up) , Download odin 3.10.7 or newer if available at the time of reading this post, right click on odin and run as administrator, now connect your phone to your computer with the usb cable preferably coming with your own phone, now if you have installed the drivers (from kies software) and if the cable is working and usb debugging is enabled, odin should detect your phone and show <ID:0/003> added in the message section (the number 3 isn't important, it depends on which usb port you use), now check the options tab to make sure only Auto Reboot and F. Reset Time are checked (by default these 2 are always checked, make sure Re-partition is unchecked). I recommend waiting a minute or two to make sure your phone and odin have recognized each other fully and usb drivers are fully installed.
5. Click on AP and browse to the location where you compressed the rom files and choose it, now to begin flashing this stock rom, just hit start.
6. When ODIN is done, you should see a box that will say reset or passed (depending on which version you have, you may see either or both.). At this point it is ok to remove your device.
ODIN has completed the flash, and by now, the device should be going through the reboot screen, if it works for you as it did for me you won't get the frp lock message again.
Any problems, try these few things: Update Drivers, and restart your PC; Different cables; Different USB ports.
Just a tip: If you are in download mode and you want to restart or turn off your phone for any reason and you have an unremovable battery like me, in download mode hold Volume down + Power for 10 to 20 seconds to restart your phone, now if you want to turn it off completely, after the restart hold Volume up + Home + Power to go to recovery and from there choose turn off.
-------------------------
After this process your phone should boot and the red little text saying “custom binary is locked by frp lock” should disappear. But since you flashed your phone after you removed cm.bin and sboot.bin your phone will be slow and you will aslo, still have to bypass the frp lock from google inside your phone, to do that I will give you a link to youtube from rootjunkey which explains it best how to bypass this frp lock inside the phone, or if you have the user and password of the google account you had previously logged in with to you phone, you can enter those and when asking to backup your previous apps choose "treat this phone as a new device" because you don’t want to install the apps just yet and you’ll have to flash your phone one more time with the complete stock (including cm.bin and sboot.bin). after entering your phone either by logging into your google account or bypassing the google acounot login screen, go to settings >> about >> software info and hit build number several times to enable developers options, then go to developers option and enable usb debugging and the damned oem unlock, and from now on before restarting or turning your phone off check to see the goddamned oem unlock box is on.
www . youtube . com/watch?v=JzywoFS_r9U
www . youtube . com/watch?v=DJ8_qbj1DPQ
Now after I did all these things I tried to flash the whole stock rom I had downloaded but I got the message “sw .rev binary check failed device 2 binary 1” and I think the reason I got this was beacase I had flashed many other recovery and roms before and I had screwed up my bootloader version and my phone didn’t recognize this rom as the right one for my phone, I downloaded a few more roms from my own country (Iran) and each time it either gave me this message or failed because it was stuck in flashing either hidden.img or sboot.bin or … . so what I did was a method I learned from someone in a forum (I don’t remember which forum), I’ll post a picture of that method and explain a little bit about the steps or modifications I made. And before using this method, download unified android toolkit, just google and download it, you’ll need it for this method.
link to the image:
s7.picofile . com/file/8250224492/Galaxy_S6_NAND_Write_Start_Fail_Fix.jpg
this software creates a folder in the root of your operating system drive (c Drive in my case) named Unified_Android_ToolKit, inside it you will find an input and an output folder, put the files you want to re-pack into tar files in the input folder, follow the instructions (99, 8, 1, 3) and your resulting files will be saved in output folder.
So the modifications I made to that method was:
The order I followed in flashing was as follows:
- AP: Boot/Recovery/System : these are the main system and recovery files and have the biggest size.
- CRC: Cashe/Hidden : This is some country code used for the region to flash the ROM against, XE is Europe, AU is Australia, and so on, this part can throw you off, its more then for tracking what region this is based of, in terms of localization and language support. And more importantly, for Kies to recognize the region and to determine if there's firmware update available. It is quite possible to have a CSC that can be limited to one country.
- CP: Modem
- BL: cm/sboot : Your bootloader
This is the order I followed and as you can see I chose all buttons and their corresponding files instead of choosing all of them with AP. Each one of these buttons re-writes the corresponding file into it’s previous partition in your phone.
Also I flashed boot.img first, restarted, flashed recovery.img, restarted, and so on, except for the cm.bin and sboot.bin which I repacked with unified android toolkit into one tar ball instead of 2 tar file, and flashed them together, to do this all you have to do is put these 2 together into the input folder and select 99, then 8, then 2, then yes.
finally I decided to try using Samsung smart switch (which I had tried but didn’t work before) to try to flash a stock rom once again to make sure everything is back to normal, but it still didn’t work and froze just like before, so I decided to use kies and it worked, even though smart switch is newer I believe kies is still better, so I recommend you use kies to update your firmware one more time using this Samsung tool, especially if the previous method still didn't fully work or if your baseband version or IMEI is unknown. To do that after enabling usb debugging, open kies, connect your phone to your computer, unlock your phone screen if it is locked and wait for kies to recognize your phone, if it said kies does not support your device or try smart switch just ignore it, it’s okay even if it doesn’t recognize your phone, just go to tools and choose firmware upgrade and initialization, now enter your model number (Upper-case), then serial number, both are on the box of your phone, sn is also behind your battery or at the back of your phone if your battery is unremovable, follow the instructions, at one point you’ll have to disconnect the cable, turn off your phone, go into download mode and conncet the cable again and then hit update to update the downloaded firmware. This time if everything goes right your phone may work even better and faster than before just like it did for me.
one last thing: I had screwd up my phone so badly that my baseband and IMEI was unknown and I couldn’t make any calls, and what’s worse I hadn’t backed up my efs folder, so I tried a few methods to solve this and finally decided to use kies, kies hadn’t worked before but this time it worked and restored everything to normal.
Now this time after i fixed my phone, I have backed up my efs folder, and my stock rom from clockworkmod recovery, and I have also set up a Microsoft/Samsung drive, google drive and dropbox account and installed some software to backup every contact, message, and app I have to the cloud in case sth like this happens again, I learned my lesson, I hope you do the same.
Developers, please correct any mistakes I may have made explaining this method, I am a newbie and these are what I learned in just 2 days of reading many forums and applying them to solve my own problem, so I may be wrong in some of these, so before people try this method out correct all the mistakes I may have made so people don’t brick their phones. Thank you
I hope this was helpful, thanks for reading, sign out.

quick question, when i try to flash the modified .tar rom a message appears saying: "custom binary(boot) blocked by frp lock"
but without i cant activate developer options and OEM unlock. i cant use my phone atm
edit: phone is a510f

After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.
---------- Post added at 09:09 AM ---------- Previous post was at 09:08 AM ----------
After removing the 2 files from tar, I was able to flash OK.
But after flashing, my phone is stuck in bootloop - it shows Samsung Galaxy A5 and restarts, continuosly.

Thanks, this helped my friend he is a n00b

This does not work with 6.0.1
Just for anybody who has that version, dont waste your time downloading 5.1.1, it wont work if you already in 6.0.1

Why should oem unlocking automatically turned off

This actually applies to all Samsung phones...
But, use the right firmware and flash it using Odin.
Side note:
To activate Developer options, tap Build number 7 times on About phone settings. Then, open Developer options and activate OEM Unlock.
You should ready to go flashing everything. Happy flashing!
AlokAk said:
Why should oem unlocking automatically turned off
Click to expand...
Click to collapse
OEM Unlock is turned off by default for Factory Reset Protection (FRP) feature to work properly.
Sent from my ASUS_Z00AD using XDA Labs

Is there any way by which i turned on OEM UNLOCKING permanentaly..
I have also rooted my A5 2016 by cff auto root.it rooted But after restarting it shows custom binary blocked by Frp lock. I have submitted this phone to samsung care. They fix it.
Now my phone is okk .
But no root access. Now I am not dare to root it by cff auto root
Is there any other way to Root my Galaxy A5 2016 Marshmallow (6.0.1) that after rooting it works without any problemm, if anyone could help me please.
Thanks in Advance

Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll

AlokAk said:
Which country's firmware i download for my galaxy A5 2016 ( SM-A510FD ) INDIA region.
On Sammobile website there is no firmware for india region.
Please tellll
Click to expand...
Click to collapse
You could try to find it on Updato.
Sent from my ASUS_Z00AD using XDA Labs

No firmware for India region infact it only shows four region in filter region section

samsung a5 2016 SM-A510FD firmware fail any [Q-call 9041634416 i help you better

orion7i7 said:
Hi,
Okay, I hope this method can help you.
Click to expand...
Click to collapse
tx You saved my phone life
It works also with other software not only old one

não da certo comigo
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???

Fwatech said:
no meu galaxy a5 deu essa mensagem mas coloco no modo download mas ele não aparece no ODIN pois não reconhece o cel pelo pc e agora ???
Click to expand...
Click to collapse
The same thing happened with my phone.
After this message "Custom recovery blocked by FRP lock", the boot does not go ahead and in the download mode is not recognized by the pc.
I can not solve this :crying:

danjercm said:
and in the download mode is not recognized by the pc.
Click to expand...
Click to collapse
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs

krasCGQ said:
1) Have you installed USB drivers?
2) Have you tried other cables?
3) Have you tried different OSes, Odin versions, etc...?
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Hi
thanks for answering
1) Yes, I installed the most up-to-date version of the samsung driver (SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0)
2) Yes, I tried 5 different original cables
3) I tried with 6 different versions of Odin, on windows 7, 8.1 and 10.
so I researched google, the only alternative is to do a procedure called JTAG, but still had hope of being able to solve without having to open the device
If anyone has a suggestion, I'll appreciate it.
Thanks

Many thanks
Me and my A5 want to thank you a lot. You saved his life I don't have to use my Wiko View :silly: anymore

Not simple is write combination firmware to the phone, then enable usb debugging and then just write firmware that not erase user data and cache and use free sw or adb command(this work not depend on software in the phone) to unlock the phone.
Simple software is here and the manual.
http://www.hardreset.info/FRP-Unlocker/

Thank you so much dude! I've searched the internet for 2 days and then this post came by so I decided to read and do it because I had nothing to lose and hell yeah it worked! THANKS!

Is it fixable? Bricked S6 won't boot or accept ROM flashes.

Previously, I've talked about how I bricked my G920T by using an apk to try to root my phone.
Then I tried to do a factory reset with the stock recovery but it wouldn't even go into the stock recovery. So I flashed TWRP and wiped the whole phone including the system partition.
Then I tried to flash a stock 6.0.1 firmware to the phone but doing so did not improve the situation as my phone still won't boot. Even worse, when I power my phone, all I see is the blue LED indicator, no Samsung logo, nothing.
Then I tried to flash a custom ROM like XtreStoLite but that didn't fix anything either.
When I use TWRP or the stock recovery, the error "failed to mount /efs (invalid argument)" comes up on the log. I tried using the ADB method to fix it but my phone would not get recognized by ADB probably because USB debugging isn't on by default.
I cannot shut down the phone without having it charged to a power source then holding down PWR+DOWN VOLUME+HOME until the screen shuts off.
When I enter download mode, I don't see the warning screen, I enter the download mode directly.

It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root

yasteellutch said:
It will warm you when you enter download. Or use TWRP and reboot into Download.Once in download flash the ROM using Odin. Get the latest one from SamFirm.
P.S. Next time root using CF Auto Root
Click to expand...
Click to collapse
It doesn't warn me when I enter download mode, that's one of the problems.
I tried flashing the official ROM using ODIN, it still won't boot because of the efs error.

1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it

If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.

Orginator said:
1) Download the latest SmartSwitch
2) Click on more -> Emergency software recovery and initialization
3) Go into Device initialization, enter your model name, search for it and proceed as advised by the assistant
That should fix everything, otherwise:
1) Download the latest official firmware for your model, the 4-File (or 3-File) Version
2) Use latest ODIN, check repartition in options
3) Select all the files and flash it
Click to expand...
Click to collapse
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
brenner650 said:
If EFS or DRK is corrupted, flashing roms, custom or not won`t help, it can be fixed via repair box maybe (Octoplus/Z3X)
Try to flash CF auto root for your model, if it still won`t boot, then find someone with a box to try to help you remotely or not.
But Smart Switch emergency initialization with phone sn would be the first thing I would try.
Click to expand...
Click to collapse
How can someone with a box help me remotely?

zheyizhu said:
Which mode should I be in when using SmartSwitch? No devices are shown when I have it plugged in during the bootup, and is so too in download mode but shows a not supported message.
Click to expand...
Click to collapse
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
zheyizhu said:
How can someone with a box help me remotely?
Click to expand...
Click to collapse
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.

brenner650 said:
Download mode offcourse. Nevermind the not supported message.
Follow instructions from link below, I made it for such occasions:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
Well if you know someone who have a box, it doesn`t have to be remotely.
If not, it is possible to fix it remotely, with help of usb hub (FlexiHub or similar), tunneling (TeamViewer or similar) and box software (you connect phone to your computer, the other guy connects box to his computer, both of you are connected through a gateway to a wonderfull thing called internet, and everybody is happy ) .
Same as on site, just with few more things in between the phone, and the box.
Click to expand...
Click to collapse
The S/N sticker on the back of the phone is long gone, is there any other way I can find it besides from going into settings because I can't do that?
EDIT: I am able to borrow a friend's serial and got the firmware installed.
The Samsung boot logo is back now, however, the device still won't boot. The efs error is still there but the download mode warning sign came back.
EDIT #2: Okay, I flashed TWRP now and ADB is working once again. Can I utilize this to fix the efs error?

"Custom Binary blocked by FRP lock" & Odin/PC won't recognize the device

"Custom Binary blocked by FRP lock" & Odin/PC won't recognize the device
Okay so,
My phone has been rooted for a year, I disabled OEM Unlock by accident, my antivirus was always telling me its unsecure with this feature on and to 'click here' to disable it.. I forgot how important this was to have enabled while rooted and ended disabled it and that night rebooting my device.
I get this error when trying to boot my device:
"Custom Binary blocked by FRP lock"
I have the original stock firmware, and Odin and want to reset the phone but when I plug this device in ( while in download mode ) > the windows PC doesn't recognize it (no new device sound or any change in devicemanager) and therefore odin isn't recognizing anything either - - I can grab my other 2nd-device and boot it into download mode, plug it into the same setup and boom > recognized and 'Ready!' Status in odin almost immediately so I don't think it's my PC or the cables -- I don't think 1st-device has usb debugging enabled either and I'm not sure how to proceed ...
any help is much appreciated ...

Try to use Smart Switch (from Samsung website), which also has the latest drivers, to recover your phone. (Google "how to recover with smart switch")

Alright,
Forgot to mention I tried Samsung Kies but cannot find the serial number on the device, I'll give Smart Switch a try this evening on my other PC and report back... hopefully that PC recognizes it, my tablet connects to this laptop but not the phone.. could USB debugging being disable cause this?
How close to bricked is this?
I'm such a fool!
Thanks for the feedback so far..

Hi boot tar flash odin frp lock of after stock rom flash

I went through this a few weeks back. I found my serial number (was a sticker originally on back of phone) and used smart switch to recover firmware. Then enabled developer options, oem unlock, flash TWRP thru ODIN etc etc.

So if I find the serial number, I save it .. good to know, thanks!
Hi boot tar flash odin frp lock of after stock rom flash
Click to expand...
Click to collapse
Can you elaborate just a bit?

zerotrick said:
Okay so,
My phone has been rooted for a year, I disabled OEM Unlock by accident, my antivirus was always telling me its unsecure with this feature on and to 'click here' to disable it.. I forgot how important this was to have enabled while rooted and ended disabled it and that night rebooting my device.
I get this error when trying to boot my device:
"Custom Binary blocked by FRP lock"
I have the original stock firmware, and Odin and want to reset the phone but when I plug this device in ( while in download mode ) > the windows PC doesn't recognize it (no new device sound or any change in devicemanager) and therefore odin isn't recognizing anything either - - I can grab my other 2nd-device and boot it into download mode, plug it into the same setup and boom > recognized and 'Ready!' Status in odin almost immediately so I don't think it's my PC or the cables -- I don't think 1st-device has usb debugging enabled either and I'm not sure how to proceed ...
any help is much appreciated ...
Click to expand...
Click to collapse
Hey man, im having the exact same issue with my S7 edge.
So I got my IMEI number, and with my number I went to imei. info / and I got my serial number through a warranty check through the site, you have to register to do it.
I used Smart Switch and I get an error when trying to use the emergency recovery "Model number cannot be initialized"
I'm also getting the error on my PC when trying to connect my device to odin saying that "USB device cannot recognize" and with that I cannot flash the stock firmware on the device.
So if you have gotten any solution to the FRP lock please let me know.

Serial number is engraved on back cover next to the imei number -,- @samuraichick0n about "Model number cannot be initialized" try to write it in diffrent forms eg. G935f or SM-G935f uppercase or lowercase.

Domino5 said:
Serial number is engraved on back cover next to the imei number -,- @samuraichick0n about "Model number cannot be initialized" try to write it in diffrent forms eg. G935f or SM-G935f uppercase or lowercase.
Click to expand...
Click to collapse
Thank you for the response. I will give this a go when I get home later today.

samuraichick0n said:
Thank you for the response. I will give this a go when I get home later today.
Click to expand...
Click to collapse
If smartswitch doesn't work you can download latest firmware for you model number and flash using odin, should solve your issue very quick

dusterphil said:
If smartswitch doesn't work you can download latest firmware for you model number and flash using odin, should solve your issue very quick
Click to expand...
Click to collapse
PC doesnt want to recognize my device, so Odin doesn't pick it up.

Try it with other usb cable. What is given together with the charger is incongruent, it happened to me, the same problem. (galaxy s6, s7)
And you need the newest odin. Excuse me my crappy English.

feri1969 said:
Try it with other usb cable. What is given together with the charger is incongruent, it happened to me, the same problem. (galaxy s6, s7)
And you need the newest odin. Excuse me my crappy English.
Click to expand...
Click to collapse
I've tried everything, and I still cant get the PC to pickup the phone to flash with Odin.

samuraichick0n said:
I've tried everything, and I still cant get the PC to pickup the phone to flash with Odin.
Click to expand...
Click to collapse
Tried a different PC?

*Detection* said:
Tried a different PC?
Click to expand...
Click to collapse
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.

samuraichick0n said:
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.
Click to expand...
Click to collapse
Hardware fault with the phone then

Need same kind of help
samuraichick0n said:
Yes, I've tried a different PC - "USB Device Malfunctioned /Device cannot be recognized"
Also a PSA: Smart Switch removed the recovery option for phones, you are ONLY able to get a recovery with the code from a previous backup.
Click to expand...
Click to collapse
Hi just wanted to no did you get it fixed and if so how I can’t find help anywhere. Thanks

ladyhypa said:
Hi just wanted to no did you get it fixed and if so how I can’t find help anywhere. Thanks
Click to expand...
Click to collapse
Hello, after exhausting all options I had to take the device to Samsung themselves - eventually they had to replace the motherboard on the phone to fix it.
So check if your phone is under warranty and take it in.

I fixed this when I first rooted by flashing the stock bootloader, firmware etc everything through odin

Thanks
samuraichick0n said:
Hello, after exhausting all options I had to take the device to Samsung themselves - eventually they had to replace the motherboard on the phone to fix it.
So check if your phone is under warranty and take it in.
Click to expand...
Click to collapse
Ok seems like what most people are saying but unfortunately mine is not under warranty but thanks for your reply anyway.

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