Custom binary blocked by oem lock help!! - Samsung Galaxy A7 (2018) Guides, News, & Discussio

After flashing a gsi it stucked at bootloop. After a long time when i tried to reboot it it shows top corner of the boot screen custom binary blocked by oem lock then goes off. Cant boot in recovery.. What should i do? Please anyone help me:crying:? A750GN)

Omg... there is 1000 postst with this problem/solution...
Flash stock, conect to onternet, dont power off 7 days.... enable developer settings, enable OEM unlock...
Then try GSI again...
BR.

g0didit said:
Omg... there is 1000 postst with this problem/solution...
Flash stock, conect to onternet, dont power off 7 days.... enable developer settings, enable OEM unlock...
Then try GSI again...
BR.
Click to expand...
Click to collapse
Thanks bro!!!!!

Related

Command not allowed error

After I Upload b320 Stock rom to My Phone which I Upload it rom with bootloder key before, it took root.
When I tried to upload twrp recovery again, there was a mistake command not allowed. ı tried it two different pc and two different programme
I have same Problem.The Bootloader shows unlocked,but it's locked.Unlock again and works for me.
letschky said:
I have same Problem.The Bootloader shows unlocked,but it's locked.Unlock again and works for me.
Click to expand...
Click to collapse
while I am trying to relock bootlader method, I met a new mistake failed remote root type is risk
Is FRP unlocked?
no frp is locked
ok unlock it,this is the Problem
Go into Settings-Phoneinfo and press 7 times on Build Number.(This enable Developers Option)
Go back to Developer Options and enable OEM Unlock.
You can flash Twrp,does not work unlock your Bootloader again
letschky said:
ok unlock it,this is the Problem
Go into Settings-Phoneinfo and press 7 times on Build Number.(This enable Developers Option)
Go back to Developer Options and enable OEM Unlock.
You can flash Twrp,does not work unlock your Bootloader again
Click to expand...
Click to collapse
Thank you. İ fixed problem ?
I cannot turn on the enable OEM Unlock, the option is grey disabled. What can I do? Im in nougat, should I try rollback to 6.0?
I have same problem... Is it possible that only solution is rollback??
6marcus9 said:
I have same problem... Is it possible that only solution is rollback??
Click to expand...
Click to collapse
I rollback and fix it. It's looks like nougat or beta versions disable OEM unlock
6marcus9 said:
I have same problem... Is it possible that only solution is rollback??
Click to expand...
Click to collapse
I fix It. The solution is easy but in anyway you need wipe your device
The steps are below
1 switch your phone in bootloader mode
2 with fastboot enable OEM lock , after lock the phone will be wipe
3 wait boot and configuration
4 enable develop mode e now you can disable OEM protection (FRP)
5 now switch your phone in bootloader mode and with fastboot unlock OEM
6 after wipe your phone will be with bootloader unlock and Frp unlock
Good luck
Sent from my HUAWEI NXT-L29 using XDA-Developers Legacy app

Brick MHA-L09, bootloader unlock, oem lock.

have a serious problem, after unlocking the bootloader I have mistakenly called the lock oem option. Now my phone is unlocked Bootloader but OEM locked.
It does not fire, I only have access to Recovery and fastboot.
Is there a command to unlock oem?
Thanks
What do you mean by oem unlock?is it the one in developer settings?
What is the problem you are facing now? The phone doesn't boot?
gm007 said:
What do you mean by oem unlock?is it the one in developer settings?
What is the problem you are facing now? The phone doesn't boot?
Click to expand...
Click to collapse
Yes the developer. The phone does not start, I can access recovery, flashear recovery twrp, eRocovery, but it never does anything, it only stays in the first message where it says starting ...

What happens if I disable OEM-Unlock in developer settings?

I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
Turned it off once by accident but turned on again.. Nothing changed
I don't think anything changes unless u relock it via fastboot, which at that point as long as u can boot back into the OS, u can always unlock it again, relocking bootloader will format ur data and u will no long be rooted or have twrp installed
locking your bootloader with root etc installed can cause major problems so before doing that you should flash a stock firmware otherwise you will be locked out
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Need to find something to do. You bored
iElvis said:
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Click to expand...
Click to collapse
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Your cat will get knock up..........again!
Maik_ said:
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Click to expand...
Click to collapse
Just turning off Developer Options won't relock your bootloader. You can only do that manually in fastboot. But you'll also lose USB debugging, which means adb won't work anymore in case something goes wrong. (But leaving USB debugging on all the time isn't the best idea anyway.)
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
omer123137 said:
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
Click to expand...
Click to collapse
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
iElvis said:
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
Click to expand...
Click to collapse
I was finally able to solve this issue with flashing the official firmware with odin . now I will never touch the oem unlock button ever again :laugh: . but thank you for your reply .
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Toni Moon said:
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
Click to expand...
Click to collapse
I downloaded and flashed the official firmware with odin and it worked . thanks for the reply
I did this once on my OnePlus X, disabled oem unlocking in developer options. phone and recovery worked fine. I did a backup. Flashed a new rom to test it. The rom had AOSP recovery in the zip, overwriting twrp (opx has separate recovery partition). I flashed gapps affter the rom and the setup wizard was crashing so I could not boot in the home screen. Tried TWRP, its gone. Tried to boot to twrp via fastboot, oem locked. Had to do hard brick reset. Backup and data, gone.
TLDR, you should leave it on, unless you are on stock firmware.
After flash a rom you must flash twrp recovery again, restart in recovery and flash gapps and magisk
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Sinankhan.official said:
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Click to expand...
Click to collapse
This isn't a Samsung device.
Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
I restored the stock firmware using Odin, but now I see that the bootloader is still unlocked.
When try to lock it again the system says: "If OEM unlock is turned off, your phone will be reset to factory default settings after restart. This will erase all of your data... " etc.
My question is: will the firmware be still in place? I don't mind everything being wiped, because most of it will be restored anyway when I login to Google and Samsung again.
SamarSS123 said:
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
Click to expand...
Click to collapse
No

Did I just bricked my pixel?

I was playing with bootloader/flashing kernels etc. than I decided to lock bootloader, I entered the command in CMD, relocked the bootloader and instead of booting, I pressed "recovery mode" accidentally. Phone hasn't entered recovery, and Now the phone is not starting at all, just 0.1 seconds long flashing of google white screen and that's all. Can't enter recovery mode from fastboot menu, and cant boot either. Any suggestions will be helpful. Thanks in advance.
Have you tried reflashing a factory image?
Flipz77 said:
Have you tried reflashing a factory image?
Click to expand...
Click to collapse
how? Can I use CMD in fastboot mode? and the bootloader is locked also
nvm, I have unlocked bootloader and the phone booted normally. Thanks anyway
I wouldn't lock that bootloader again, you got lucky, do a search here on why it's not a good idea
Sent from my Pixel using XDA-Developers Legacy app
Hi Levan_i,
can you tell me how you have done the unlocking?
It seems to me that we have/had the same problem https://forum.xda-developers.com/pixel/help/bootloop-installing-factory-image-t3866332/post78149546#post78149546
ArchArch said:
Hi Levan_i,
can you tell me how you have done the unlocking?
It seems to me that we have/had the same problem https://forum.xda-developers.com/pixel/help/bootloop-installing-factory-image-t3866332/post78149546#post78149546
Click to expand...
Click to collapse
I have just entered "fastboot oem unlock" in CMD
Cant do that
Levan_i said:
I have just entered "fastboot oem unlock" in CMD
Click to expand...
Click to collapse
Says for me remote oem unlock isnt allowed
FalseFriendsGaming said:
Says for me remote oem unlock isnt allowed
Click to expand...
Click to collapse
You need to go to Settings -> System -> Advanced -> Developer options -> set OEM unlocking as enabled. Also, make sure you're using the latest platform-tools package.
Cant do that
post-mortem said:
You need to go to Settings -> System -> Advanced -> Developer options -> set OEM unlocking as enabled. Also, make sure you're using the latest platform-tools package.
Click to expand...
Click to collapse
I can't since I relocked my bootloader after rooting its crashing on startup and cant get to the lock screen

problem with installing rom

I'm having trouble on my A30.
I try to install any custom rom does not work, does not boot or install on the system
I've done everything! I can't disable OEM
Mine appears KG STATE: CHECKING IN DOWNLOAD MODE
I've changed everythin
Need help
Maguda said:
I'm having trouble on my A30.
I try to install any custom rom does not work, does not boot or install on the system
I've done everything! I can't disable OEM
Mine appears KG STATE: CHECKING IN DOWNLOAD MODE
I've changed everythin
Need help
Click to expand...
Click to collapse
So OEM lock is enabled? AFAIK you need to OEM unlock first die being able to flash a custom rom. Best to check in your device's forum how to unlock.

Categories

Resources