Database Info

Custom binary blocked by FRP lock

Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks

Hi. Have you got it fixed yet? You need to download and flash stock firmware for your model and flash it in odin. Once it's done you have to enable oem unlock before you flash twrp. Let it be enabled as long as you you have twrp, root or anything custom.
Skickat från min SM-A310F via Tapatalk

ok, I read this is the place for noobs, so, I too got myself into a FRP LOCK on my Galaxy Tab A6 sm-T280. I use the tablet strictly for flying my drone for surveillance around the rural location where I live. It was having some connectivity problems, so I rooted it to hopefully get enough horsepower to run the DJI Go app. That didn't work so I did a wipe/factory reset, had a problem with the password, and here I am.
I am researching, and gathering the required tools to fix it.
I finally found some guides that are basic enough for me to understand.
I found numerous sites to download the stock rom, but not sure which ones are safe. Suggestions? Also, I am not sure about the country code for the firmware. I am in the USA, and I don't see it listed anywhere. Does it matter? This android stuff is all new and confusing to this old man. I am determined to get this tablet fixed, and would appreciate any and all advice. Thanks, Gary
edit: Will this rom work? : T280XXUOAPL1 using XAA for theCSC? Is xaa the default/generic for U.S.A. ?

Is there a fix for this error yet?

S8 plus stuck in recovery with following message:
"Support SINGLE-SKU
Supported API: 3
dm-verity error
failed code : 0x02"
Is there a fix for this yet?
cheers
Matt

...? Elaborate?
What did you flash that lead to this?
dm-verity is what you usually get when you flash something incompatible, or when some insecure fw image is rejected.
Reflash the firmware using ODIN, and the latest FW package for your model / region. (in the AP box)
If you end up with DRK error afterwards, then you're boned. You need Samsung to help you out.
TL;DR: Careful when flashing stuff next time, always verify what you're flashing is for your device's model.

OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.

Comarrid92 said:
OP, did you found a solution to your problem? i'm asking because now i have the exact same problem as you do so i would really appreciate if you could tell me what you've done.
Click to expand...
Click to collapse
Took it back to Samsung and had to pay them £290 to fit a brand new board.
Out of warranty coz i rooted it.
only way out.
Gutted.
Matt

Guess the problem was that you didn't flash dm-verity bypass when u tried to root.

CoreyHUN said:
Guess the problem was that you didn't flash dm-verity bypass when u tried to root.
Click to expand...
Click to collapse
Wrong.
I did flash it, and it was rooted for about a week, but for some reason, i was bored, just potching around with my phone and decided to uncheck 'allow OEM' unlock, but forgot to re-check it before i restarted the phone...too late though...as Samsungs awesome security basically said...NO WAY...he's tinkering about with root triggered the efuse on the board and the ONLY way to fix that was a brand new board.
I'm not a newbie (hence my 371 thanks meter) when it comes to rooting phones....i've been on here since 2011 and rooted stacks of phones....HTC HD2, HTC Sensation, Desire HD, LG G2, LG G3, LG G4, HTC One-X, HTC One-x Plus, HTC Desire eye and a LOT more...Just made a silly mistake a week AFTER I rooted the phone.
I gotta be hnonest, I thought i'd miss root, but can hand on heart say....i'm not missing it one single bit.
My lovely Samsung still has 20 months warranty and i'm keeping it that way by not rooting.
LOVE my S8 Plus and to be honest, with Knox etc....I'd advise everyone not to root this EXPENSIVE beast of a phone!:good:
Matt

In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.

CoreyHUN said:
In some countries (like the EU ones) it is legal to modify the software on your phone, without voiding HW warranty, so if ur phone dies, and they can't prove that it is because the modification, they have to replace / repair it.
Click to expand...
Click to collapse
WRONG!
Hardware problems -> YES
Problems due to wrong use of your phone (i.e. root and phone won't do anything anymore): NO
And I do agree with Samsung: if you temper with the FW, and your phone doesn't do anything anymore -> IT'S YOUR OWN F...... FAULT ! ! !

Here's the nice big fat bill I got for repairing it.

Eeeuuurrreekkaaaaaa!
So after being presented with this error due to my own stupidity (trying to diagnose why MTP wasn't working on windows 10 and disabling Developer Options and not re-enabling OEM Unlock), I managed to get around it quite simply although at the cost of my data... BUT at least its not bricked.
The solution is simple;
1. Use SamFirm and download the latest firmware
2. Using Odin Load all the firmware options (BL, AP, CP and CSC) and in the options tab select all the checkboxes except "Flash Lock" and "T-Flash".
3. Press start and hold your breath.
Upon completion the phone may not reboot automatically so you will have to manually reboot using the Bixby, Volume Down and Power Buttons. Once rebooted you'll see it erasing the remaining userdata and finalising the re-partitioning process but a few minutes later you'll see the samsung logo and the welcome screen.
I hope this helps someone. Good Luck Peeps

I have the same problem guys but my odin isn't working the ID thing specifically the computer isn't recognising the phone.

samsung galaxy s7 custom binary blocked by frp lock

Greetings, ever since i tried rooting my phone, i knew something went wrong (i used cf autoroot).
So the first thing i noticed, i was asked to reset the phone or something similar to that, meaning i would lose all my data.
I tried to find a workaround as this had never happened to me before while rooting a phone, and someone had said that i was supposed to download twrp
and change some partition and then change it back. I dont remember what else he mentioned and what exactly i tried doing, i realised it was formatted either way and i had to start fresh. As i setup my phone i went and switched the oem unlock back to "off", as i did not wanna attempt to root again, but i hadn't realised that my phone was infact rooted sucessfully, leading me to my first error after restarting. "Custom binary blocked by frp lock", with absolutely no access to recovery mode at all anymore. Again, trying to find a workaround, i download some stockfirmware that i atleast had hoped was the right one for my phone, after a couple failed attempts of flashing with odin, ( i had gotten various different error messeges on download mode screen such as (REV Check fail device 7 binary 0 and others witch i cannot remember), now im getting a new error screen, stating that an error has occured while updating the device software. I cant flash twrp recovery as the frp lock is on, and the only thing i can guess is that im flashing the wrong firmware, but i cant find a matching code at all.
Its the following: sm-g930fzkadbt
IMEI: 35214310282955
on the back of the phone it says uk yateley, although the phone was purchased in germany.
Im not sure what to do anymore, any advice would be greatly appreciated.
PS: I have managed to get back to the old error screen with the custom binary info, this time with bootloop, by checking the deviceinfo box on odin

Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:

Elef244 said:
Thanks for your reply, just a question, will any btu update work? Should i download latest android version btu firmware?
(Also yes, it was stupid of me to try and do it quick but i had rooted 3 different samsung galaxy phones in the past without issues, either i did something wrong or it took something way too specific to do the job, perhaps the phone's unrootable, but thank you either way) :fingers-crossed:
Click to expand...
Click to collapse
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.

cooltt said:
You'll likely only find the last version of BTU think it was August 2019. It isn't updated officially anymore but it'll be fine to use.
Click to expand...
Click to collapse
I've found android 6 to android 8 with all the monthly updates, im just trying the latest of the latest though i dont remember my android version, ill try android 7 and 6 if that doesn't work, thanks again. I'll make sure to reply if this works or doesn't.

cooltt said:
Yep you've now learned the hard way not to mess about and read the proper guides.
Anyway "dbt" is just unbranded german firmware. Download UK "BTU" and flash with Odin, it's UK unbranded.
FRP lock means you'll need to unlock the phone with the google account and password that was on it before you started messing about with it.
If you don't know the google email and password you need to read up on how to bypass FRP lock and it's a nightmare.
Click to expand...
Click to collapse
OK so i thought it worked but i can only enter recovery mode now and download mode, but cant actually boot the system, it just boots up the battery screen whenever i plug the charger, and never shows the actual battery info, just the thunder icon. Formatting from recovery mode doesn't help either (Note whenever i launch recovery mode it says installing update, then says no command and brings me to the recovery menu) Any ideas?
PS: It fixed itself. Sorry for the pointless edit.

[FIXED] Need Help. Galaxy S8 G950FD. Can't flash stock ROM.

[EDIT: SOLVED THE ISSUE BY TRYING THE LATEST FIRMWARE. THANKS ANYWAY!]
I got this phone from a friend, no clue what he's done to it, but I get a "Only official released binaries are allowed to be flashed"
So I downloaded the stock rom and tried flashing it through ODIN, but I keep getting errors, and it will not let me flash anything. There seems to be no bootloader too, if that's possible, as I can't enter it. I'm now stuck on a screen that tells me "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software"
I haven't rooted a phone or messed around with a phone at this level since the Oneplus One days. Extremely rusty, please help me out.
(also, the phone has G950FD on the back, but download mode claimed it's G950F. it's a dual sim phone. Is this normal?)
(apologies if I'm repeating a threads already dealt with. Can't seem to find threads related, I've forgotten my ways around this forum)

Question Has anyone had any luck flashing unlocked firmware to this phone?

I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?

eddieofny said:
I have the T-Mobile variant (TMB firmware, A125U) and I would like to flash unlocked firmware (XAA, A125U1), but when I tried it failed. I tried flashing a combination file first but all the tutorials I was following were old and I had no success there either. I'm using the latest version of Odin and a good USB cable. Just the other day, I was able to flash TMB firmware without an issue, now I'm getting the Complete(Write) operation failed error. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Try with patched odin, not normal odin.

TheWorldYT said:
Try with patched odin, not normal odin.
Click to expand...
Click to collapse
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.

eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
Oh, you have to use BROM, which involves opening up phone. You can search a tutorial how to do BROM mode in your phone.

eddieofny said:
That's what I've been using. Odin will throw a generic "failed to partition" error, but on my phone display, I'll get an error about not being allowed to flash different software than what's already on the phone. I did some more research and came to the conclusion that I need to get the phone to change it's KG Status. It was stuck on Prenormal until I blocked Knox's connection to the internet with a firewall, at which point the KG Status changed to Checking. Still can't flash firmware though. The last thing I could think to try is to leave the phone on for 7 days and hope the KG Status will change again and show me the option for OEM Unlocking, which currently missing completely from my Developer Options. If there are any other solutions, I'd be happy to give them a try.
Click to expand...
Click to collapse
If the bit version of your phone is 3, flash the earliest bit 3 U package files. Then after flash bit 3 U1 package.
When flashing the U package just leave off the user data file. Must be using patched modded odin.
If you are bit 4, then you will be out of luck for a while.
I only know this because I ran into this same issue and that is how I resolved it on bit 3.