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!
Hi companions I turn to you because I have a problem with my LG L50 (d213c). I'm using google translator, I hope you understand my faults ...
what happens to my terminal is that this bricked (or at least for me) when I turn only displays the download mode ... so it when connected via USB to the PC. I tried to flash the KDZ by various programs and tools and these have the same problem ... at the time and is loading the firmware on the phone only advances up to 10% in the LG Support Tool after that asks me to connect the device because there were problems (?) and so ad infinitum. In the programs selected and the KDZ file is loaded ... to already be flashing process, just beginning says there was problem when this extracting the KDZ and ends the process right there ... download the KDZ in different PC lg-phone-firmware and even down from an earlier version from the same page but also corresponded to my region and operator, to rule that it was the file that were damaged, and yet still can not flash the terminal, add that I have the drivers installed.
*I hope someone can help me or guide to revive my LG, because imagine if it appears the download mode and recognizes the PC (at least until I try to flash xd) there must be way to save, thanks in advance any help.
Si consigo ayuda en español mucho mejor xD
xNeoooo said:
Hi companions I turn to you because I have a problem with my LG L50 (d213c). I'm using google translator, I hope you understand my faults ...
what happens to my terminal is that this bricked (or at least for me) when I turn only displays the download mode ... so it when connected via USB to the PC. I tried to flash the KDZ by various programs and tools and these have the same problem ... at the time and is loading the firmware on the phone only advances up to 10% in the LG Support Tool after that asks me to connect the device because there were problems (?) and so ad infinitum. In the programs selected and the KDZ file is loaded ... to already be flashing process, just beginning says there was problem when this extracting the KDZ and ends the process right there ... download the KDZ in different PC lg-phone-firmware and even down from an earlier version from the same page but also corresponded to my region and operator, to rule that it was the file that were damaged, and yet still can not flash the terminal, add that I have the drivers installed.
*I hope someone can help me or guide to revive my LG, because imagine if it appears the download mode and recognizes the PC (at least until I try to flash xd) there must be way to save, thanks in advance any help.
Si consigo ayuda en español mucho mejor xD
Click to expand...
Click to collapse
Hi,
Please try posting your query here Ask any Query Newbie Friendly with all relevant details, the experts there maybe able to assist you.
-Vatsal
So here it is after weeks of trying to root my VFD 500 I've decided to port TWRP to make it possible.
I have ONLY tried this on my own Vodafone Smart Turbo 7, no guarantees of success if you use on a different device. I am NOT a developer and I work 60+ hours a week, therefore I will not be updating this or offering support if your device bricks.
TWRP VERSION: 3.0.2
This might break OTA, so keep an original recovery (provided below).
METHOD
1. Download TWRP_VFD_500.ZIP and extract (You should have recovery.img, SuperSU.zip and MT6735M_Android_scatter.txt and recovery-original.img) Copy the SuperSU.zip to your phones SD card, KEEP the recovery-original.img safe for future use..
2. Turn off phone and run SP Flash Tool (I used V5.1644).
3. On SP Flash Tool click choose for Scatter-Loading file and select the MT6735M_Android_scatter.txt that you received in step 1.
4. In the list of partitions make sure that ONLY recovery is selected and that it says Download Only in the drop down menu above the partition list.
5. On the recovery partition line, where it says location, click and browse to the recovery.img provided in step 1 and click open.
6. Press the big green downward arrow.
7. Connect phone to USB cable and plug into computer. The bottom of the SP Flash Tool window will go yellow / red as it flashes the phone. After a few seconds you will be presented with a green tick signifying the end of the process, your phone screen SHOULD have remained off during the entire flash.
8. Turn phone on by pressing the +vol button and power at the same time, your phone should go into TWRP recovery.
9. In TWRP click install, browse to where you copied SuperSU.zip and select it. Follow instructions on screen to install.
10. Once installed reboot to system.
Enjoy! This is a one off from me, it worked on my phone. If like me you wish to remove all the bloatware and Google Apps you don't need you'll be able to do this using Apps2SD: All In One Tool [ROOT]..... I won't be writing a tutorial for this.
Best of luck, Steve.
TWRP VFD 500.zip
SP Flash Tools
Hey This Seems cool what is the likely hood of this bricking/bootlooping your device?
I can confirm that this does work, i have just installed this on a brand new Vodafone Smart Turbo 7 (VFD 500).
Thanks a lot for your time and effort for porting this.
I installed TWRP on a Vodafone Smart Turbo 7 (VFD 500) and it works! Thanks...
Would this work on VFD 502?
Hi WildsideUK.
Trying to follow your procedure for my sister's tcl vfd 500, using the current version of SP Flash Tool, version 5.18, I stop at step 6 with some doubts.
In the SP Flash Tool, in that moment, I can not find any "big green downward arrow" buttons.
The only button with some "green" is the "Download" button which has a green arrow icon.
Using that nothing happens.
Furthermore, by connecting the phone the bottom part of the SP Flash Tool does not change any color.
I do not know if I do something wrong.
[Update]
[past some experiment and several attempts]
Following the instructions of SP Flash Tool I tried to do the same procedure by removing the battery from the phone.
In this way the procedure worked and the program finished the procedure until confirmed with the green tick.
Wonderful.
Thank you
Hello community
Can someone please give me valid links and tutorials for unlock this phone, i´ve been here for more than 6 hours looking on how to do this, but there´s always a software or file missing. I can´t even install the USB drivers, or find a TWRP properly.
What a headache..
Thanks in advance
Hi
Does anybody have the files in the above post, the links is not working anymore.
Thanks
BravestarrZA said:
Hi
Does anybody have the files in the above post, the links is not working anymore.
Thanks
Click to expand...
Click to collapse
Hi, I too am looking for those files. Did you get them?
My best greetings
I found the files at this link and all went fine!
Archivos recovery+root Vodafone Smart Turbo 7
En esta Descarga tenéis a vuestra disposición todos los archivos requeridos para hacer root al teléfono móvil Vodafone Smart Turbo 7, dispositivo conocido también por el nombre de VFD500. Dichos ar…
www.ayudaroot.com
i managed to mess some stuff up and my g stylus 5g is stuck in edl mode. i desperately need a blankflash file for this devic. Can ANYONE help me?
This will both unbrick and download any files you might need
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
How to unbrick Motorola G50 5G 9008 EDL - ROM-Provider
unbrick is a process to repair a device that was bricked, with in Motorola G50 5G user face two type of brick- soft brick and hard brick.
romprovider.com
solved everything
I wouldn't suggest running scripts for another device, but I'm glad you got your phone unbricked, you can also root it using magisk and the files Smart Assistant downloads for your phone
Okay... Just out of curiosity... Couldn't I technically flash a non-oem locked flash file....
From what I've read either 1 of 2 things will happen. 1 you will be able to flash through qdl 9008 just fine. And maybe flash back to stock of the "new" device if the OEM didn't relock to the old firmware binary. Or 2 the blank flash works but in flashing but after aiming for firmware install it bricks and you will not be able to software or cable boot into qdl 9008 mode.
I have seen similar results so as to the flashing the new blank flash. You will NO LONGER have working qdl9008 mode without pinouts. Flash wisely.
This is where you can find your stock stuff for this device.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Well based upon what I've seen from this firmware(the -4 set) it literally looks like cricket took their apps, and disabled the rest for easy carrier unlocking support... It would definitely be risky I suppose but not as risky as one might think.
Im rather new to this whole ordeal, but is there any way to get a patch0.xml and rawprogram.xml or even possibly make them for this device? I want to use QFIL to reflash my rom because my bootloader is soft locked (able to boot into it, cannot unlock because the stupid oem unlock setting isnt checked in android but I can't get into android). Anything helps!
If it boots into fastboot, you would just need to flash the original firmware for the device
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Should be able tell the variant by running this command
Code:
fastboot getvar ro.carrier
fddm said:
If it boots into fastboot, you would just need to flash the original firmware for the device
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Should be able tell the variant by running this command
Code:
fastboot getvar ro.carrier
Click to expand...
Click to collapse
Would you be able to do this even with a locked bootloader?
Yes, as long as the firmware matches your variant. Flashing the wrong one will brick your device. If you use Windows, you can try flashing with the official LMSA tool, it will download the correct firmware and flash for you.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
fddm said:
Yes, as long as the firmware matches your variant. Flashing the wrong one will brick your device. If you use Windows, you can try flashing with the official LMSA tool, it will download the correct firmware and flash for you.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Click to expand...
Click to collapse
The official tool says "RSA detect that your device is flash locked. To avoid damage to the device caused by flashing, RSA recommends that you go to the customer center for help." When I run...
fastboot oem unlock <Unlock code>
it says...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.178s
I cannot boot into android
Sorry, I should have explained in better detail, my bad
Your right, I forgot Moto locks out most fastboot commands when the bootloader is locked, this wasn't always the case.
You'd have to remove the back cover and antennas to expose the motherboard then short test points to force it into edl mode. Same process as this
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
Your board might be different than the one in that thread, hard to say without knowing your variant. Then you have to find a blankflash that's compatible. Lolinet has a few, and some are uploaded to forums like in that thread. Asking on discord is you best bet if it's not already shared.
I was able to find out that I have a Retus device and found the right flash file. Once I'm in fastboot mode though the bootloader is still locked and I have the same issues. Is there any way to unlock it with EDL? Or at least flash an unlocked bootloader?
You'd need to put your phone into edl by removing the back cover/antennas and shorting edl test points. It will allow you to flash the blankflash which, if successful, will load fastboot in a state that will let you flash stock firmware(because the rest of the system is wiped). Afaict your edl test points should be the same as Boost variant in that thread I linked to.