We A50 Flash File 8.1.0 Frp Hang On Logo Fix Customer Care Pac File 'LINK'

So, when you get the message 'Custom binary blocked by FRP lock' it means you have flashed a unauthorized binary file to the phone and the phone is preventing itself to boot since it has detected the modified file(s).

You are right. It's better to prevent it at first place. If You cant boot up your phone You need to reflash original firmware then boot up, switch oem unlocking and flash right twrp recovery for your phone.If problem occurs then You flash the wrong recovery file (not for Your phone model).

Whenever you get the "Custom Binaries Blocked by FRP Lock" in red letters at the top of the screen when you try to boot to recovery, Ben who previously answered is partially correct in saying you have flashed a(n invalid) file to the phone and the phone is preventing itself to boot since it has detected the modified file(s). This can happen when you are trying to establish Root or flash a ROM that is incorrect for your device. Typically sometimes flashing in the official firmware may help, yet sometimes it does not. When that happens what's needed is an "Unlock FRP" file that most often is specific to each device. This means you can't just use any unlock frp file and this is not the kind of FRP lock that has to do with Google Sign in stopping you from accessing the device functionality. In Binary Lock Mode the device does not load past the Logo screen. BE ADVISED! This will also fatory reset your device.

Custom Binaries Blocked by FRP Lock is not the same as the Factory Reset Protection (FRP) associated with the Google Account sign in. This one is an overload of codes or binaries due to flashing invalid or corrupted firmware into the device. So don't try the firmware that got you into the situation. I know of no way this can be fixed without using a PC with Odin3. If you are in Custom Binary Lock by FRP I may be of help but that is no guarantee your device can be returned to proper functionality. There are some I've been working on that I've been unable to correct so far. That being said let me tell you what I know of to possibly restore your device. If you may be familiar with using Odin3 it is common to use one file to flash the device. This goes into the AP section of Odin3. However, with binary lock this is not one of those times you can do so. If you are in Binary Lock you should not be able to Factory Reset or flash most files with Odin3 which will only initialize then fail.

I can not name one single file that will fix this and there seems to be a variety of ways for a fix. This all depends on where you are seeing the notification of "Custom Binary Blocked". Some people can make it to the Recovery Menu but cannot use it. It's about the same if you see the notice in Download mode. You can't seem to use it. Some see it on the splash screen and they are in a repeating Bootloop so also cannot use the device or flash it.

The files you will use in attempting to fix your device are specific to your device. Do not use any others. Do not try to downgrade your device from android version 8 or above to Android version 7. It doesn't work to begin with. You need to search for what's called repair firmware. This should be a 4File and not a single file. Any file you try to flash in must be a binary equivilant of what you have in your device. Here's the short version of how to find which binary your device is using. Here's the build number or firmware of one of my devices.

T580UE(U4)CSC1. The U4 in parentheses signifies the binary or bootloader. Repair Files also called Combination Files can be found here with samsung devices. They take hours to download. 4File firmware contains a BL, AP, CSC and a Home CSC file. Use Odin3 and place each file in their respective places. Be advised the CSC file will wipe all your application data. If you wish to keep your application data use the CSC Home File. Should flashing these files with Odin3 fail to work you need to search for the Binary Unlock files. One starts with the device model number then has U4 FRP Unlock. Mine was "SM T580 Binary 4 Unlock" or there's another one called "?? ???? U4 FRP Removal File" use your devices model number, not mine. Unless you're working with the T580. If none of that works you're one of the few I haven't been able to help. Good luck.

I haven't tried this on Huaweis only Samsungs, but the method should work. Most of the answers here are not helpful because they are not actually familiar with Binary Blocks and some are guessing. Ben up above is reading off his PC which doesn't explain it all. You cannot downgrade the device if you can't flash anything to it can you? Downgrading is not advised. What you need to fix your issue is a "Binary 4 FRP Unlock" file. I don't think Odin3 works with your device but you should be able to sideload it in via ADB. If that doesn't work for you there's another file you can look up called "Binary U 4". If neither one of those files work for you, I'm currently stuck on answering that as of yet.

Your symptoms aew one of four different ways that Custum Binary blocked by FRP Lock appears to any Android user having to deal with it. As far as I know this is not something that happens when ypu plug it in to charge it. It happens when trying to Root or flash a ROM to the device that is corrupted or flawed. Thus, the Custom Binary issue. Youls need either the Combination files or the repair files of an equivilant binary to fix this issue. To find your binary structure Assuming you have either the SM-G930 or the SM-G935. You'd need to look up the combination files here,

Some manufacturers will include a "flash-all" script as part of the downloaded factory image that will automatically flash everything for you. If this is the case, the script should be in the SDK Platform Tools folder along with the IMG files you extracted. 2b1af7f3a8