[General Topics] orion7i7:
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.